Hi all, I have a Windows 2008 sp2 server with Exchange 2007 installed on it. But what I noticed is that every 60 days the server would go through the Vailidation and that in turns cause Exchange to freeze for about 1-2mins. There are several events in the logs that says the windows license is vailidated. We have a KMS running but I think this box is going to MS to vailidate the license. Is there a way to change that? Log Name: Application Source: Microsoft-Windows-Winlogon Date: 16/04/2010 9:53:50 AM Event ID: 4101 Task Category: None Level: Information Keywords: Classic User: N/A Computer: servername.domain.local Description: Windows license validated. Log Name: Application Source: CertificateServicesClient Date: 16/04/2010 9:53:50 AM Event ID: 1 Task Category: None Level: Information Keywords: User: N/A Computer: servername.domain.local Description: Certificate Services Client has been started successfully Log Name: Application Source: Desktop Windows Manager Date: 16/04/2010 9:53:50 AM Event ID: 9003 Task Category: None Level: Information Keywords: Classic User: N/A Computer: servername.domain.local Description: The Desktop Window Manager was unable to start because a composited theme is not in use

Open a CMD window using right-click "Run as Administrator" and run the following command to show your licence information: cscript slmgr.vbs -dli This should tell you which KMS server your machine is using. Tony

Hi Tony, Just had a look and it is looking at the our internal KMS server. We presently have 2 KMS server and it is looking at the new KMS. The renewal interval is set to 10080mins Activation interval: 120mins. What I noticed is that 2x HT/CAS is looking at the old KMS while 2x Mailbox server is looking at the new KMS. Just wondering if it has anything to do with the interval on the old KMS server.

The values you show are the defaults. Are they different on the other (old) KMS server? Either way, it doesn't right to me that Exchange freezes for between 1 and 2 minutes during the license renewal process. The entire interaction between the client and KMS server doesn't amount to more than 250 bytes in either direction. In other words the overhead on the client should barely noticeable. When you say that Exchange freezes, what are the symptoms? Tony

Both KMS server settings are the same. The symptoms is on the clients. Outlook would freeze and when the user tries to send Outlook would hang. It's kinda hard because there's nothing in the logs that indicate something is wrong. I'm looking at the diagnostic logging and not sure which one to turn on.