Each time I restart this exchange server, the Information Store and System Attendant don't start. If It try to manually start the services, I get the follow errors:Event ID 5003:Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online. Event ID 1005: Unexpected error The clocks on the client and server machines are skewed. ID no: 80090324 Microsoft Exchange System Attendant occurred.The clocks on the domain controllers and the exchange server are set to the same time zones. As well, all three clocks are in sync down to the second. Any ideas on what's causing this and how to fix it?

Make sure the clock in your system tray shows the same time/date for both the Exchange server and the domain controllers.Also check this out http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_2003_Active_Directory/Q_22648594.htmlRaj

Run this Command from the Exchange Server Net time \\ADServerName /Set and confirm the action, and then you need to restart the service Microsoft Exchange Active Directory Topology Service and confirm you are not getting the Error 4001 in the event Viewer.

I've now seen this error twice to two separate installs of Exchange 2010 after installing SP1 RU3. Both environments run Windows 2003 Domain Controllers with Windows 2008 R2 hosting the Exchange 2010 installs and both are using three member DAGs. After about 25 minutes of sitting idle the IS and SA can be started manually. We have a ticket open with Microsoft, but we have not heard anything back yet.

I started seeing this problem after I installed the CAS role on the mailbox server. The mailbox server is in a two-node DAG as well. Often I'd find adjusting the time manually by a small amount then restarting the MSExchangeADTopology service would fix it... at least until the next reboot.