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 ?

September 17, 2010 at 6:39 AM

kortex786 said…

I have the same problem.
Can you give us more detail on how to fix it please ?

September 17, 2010 at 6:40 AM

Jason Yoder, MCT said…

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

September 23, 2010 at 9:19 AM

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.

November 4, 2010 at 2:36 PM

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog