MSExchangeSA and IS is not starting automatic at reboot after upgrading the server from SP1 to SP2

Question

I am running a 2 node DAG with separate Hub & CAS servers
I have already upgraded the Hub CAS server and they are fine
Exchange running on Windows 2008 R2 SP1
All are in VM-Ware ESXi 5.0
After I upgrade the mailbox server to SP2 the SA and IS service not starting automatic after reboot
If I run "net time /set" command and then restart ADtopology server, the IS and SA starts fine
But again after reboot they do not start
Also I get the below event in the app log when the IS & SA fails to start
Log Name:      Application
Source:        MSExchangeIS
Date:          05/22/2012 5:15:03 AM
Event ID:      5003
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Unable to initialize the Information Store service because the clocks on the client and server are skewed. This may be caused by a time change either on the client or on the server, and may require a restart of that computer. Verify that your domain is correctly
configured and  is currently online.
If I check the Registry for time resource it is taking from the DC
I manually compared the time between DC and Exchange and it is fine
Since the Exchange mailbox is virtual, I checked the time sync on VM-Ware tools and it is "unchecked"
Checked for group policy and do not find any specific to time sync.
Confirmed that Windows Time service is running
Suspecting a Operating system issue, tried to upgrade the other DAG
Even that node is displaying the same symptom and Issues
Tried to install RU1 on both nodes and that too did not fix the issue.
Checked with VM-Ware engineer and he said that every thing from VM-Ware end is fine
Is Anyone have come across the issue before ?

Answer 1

Exchange 2010: Unable to initialize the Information Store
Problem: 
Unable to initialize the Information Store service because  the clocks on the client and server are skewed.   This may be caused by a time change either in the client or the server,  and may require a reboot of that computer.   Verify that
your domain is properly configured and  is currently online.
Solution: 
Open a cmd prompt from the Exchange Server as administrator (right mouse click on the command prompt shortcut and select “Run as Administrator”)
Run this command
Net time \\ADServerName /Set
Restart the Microsoft Exchange Active Directory Topology Service
*Important!! You have to restart the Microsoft Exchange Active Directory Topology Service or this fix will not work..  I tried just starting the Information Store service after running the command it it still failed..
This worked for me and all is well on my exchange server.
- See more at: http://www.mountainvistatech.com/2012/06/04/exchange-2010-unable-to-initialize-the-information-store/#sthash.SwQpgQEM.dpuf