Hi I have: a 2008 R2 KMS server which is publishing its service record in DNS entered Windows 7 key into it deployed about 100+ Windows 7 systems There are currently 2 problems that I need to solve. All clients doesn't seem to automatically locate the KMS server when they are joined to the domain. I have confirmed that the service record is present and pointing to the correct server. When I force it by typing in "slmgr.vbs /ato" it successfully talks to the KMS server and activates the system. More of a problem though is the fact that the clients are not automatically refreshing their registration with the KMS server. According to the documentation, the client should talk to the KMS server on a regular interval (on a daily basis) and renew its registration. The count for "Volume activation expiration" should be reset to 180 days if I understood it correctly. But when I use "slmgr.vbs /dli" and check my clients some of them are down to 70 or less which means that they haven't contact the KMS server for a long time. I'm now seeing my count on the KMS server go down. The only way I can get the clients to register with the KMS server and get "Volume activation expiration" back to 180 days is to manually run "slmgr.vbs /ato". What is wrong? Regards Rickard

Hello Rickard, The clients should attempt to contact the KMS host every 7 days to renew the licenses. On a kms client with the issue, from an elevated CMD prompt run slmgr /dlv and report back the output on the KMS host open an elevated CMD prompt and also run slmgr /dlv ( if you get a dialog box, the text of the output can be copied using Ctrl+C) blot out any specific information that may be sensitve. Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en