Skip to main content

Unable to get Exchange 2010 Console to log into its On-Premises Server

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

kortex786 said…
I encounter the same problem.
Can you develop how to fix it please ?
kortex786 said…
I have the same problem.
Can you give us more detail on how to fix it please ?
Kortex786

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
Unknown said…
Make sure that your Exchange Server's subnet is listed in Active Directory Sites and Services.

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.

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the