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

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.