This issue is geared more towards MCTs getting ready to instruct 10135. In very rare cases, it may apply to production environments as well.
The situation is the first boot of the virtual machine 10135A-VAN-EX1.
When you open the Exchange Management Console and click Microsoft Exchange On-Premises (can-ex1.adatum.com), you receive the following message:
exception calling "GetComputerSite" with "0" argument(s): "The computer is not in a site." It was running the command ‘Discover-ExchangeServer –UseWIA $true –SuppressError $true’.
When opening the Exchange Management Shell, you are not able to connect with the error:
[van-ex1.adatum.com] Connecting to remote server failed with the following error message : WinRM cannot process the requet. The following error occured while using Kerberos authentication: There are currently no logon server availible to service the logon request.
A quick check of the DC showed that it did not have a static IP address. After examining the DNS logs, I manually set the VAN-DC1 IP address to 10.10.0.10/16 and DNS Server to 10.10.0.10.
You may want to do a reboot to make sure all the proper Exchange Services have started.
Comments
Can you develop how to fix it please ?
Can you give us more detail on how to fix it please ?
Also take a look at the Exchange Servers IP address. Make sure it does not have a conflict with any other IP address on the network.
Good Luck,
Jason
So for example if your Exchange Servers IP is 192.168.2.10, make sure 192.168.2.0/24 is listed as a subnet in Active Directory Sites and Services.