I configured a 2nd KMS server for activating Win7 clients. The 1st KMS server has been working just fine and we have well over 150 Win7 registrants(max50 shown, of course), and just wanted to add some redundancy as our network infrastructure grows. A 2nd KMS server has been installed/configured/activated and I've verified that the _TCP-entry has properly propagated thru DNS. However, when I run slmgr.vbs /dli on the 2nd KMS server, all looks good, except that the “Current count” remains at 0. Are there any further steps req'd to get these two KMS server to sync up ?thx, ~~Robb

Hello Pitarobb, The two KMS hosts do not talk to each other. The existing KMS clients cache the host they communicated with last and attempt to communicate with that host to renew, if they fail to communicate with the KMS host they used last, they check DNS for the KMS hosts records. So right now all your clients are using the KMS host that have cached. You can turn off the cache, slmgr /ckhc Disable KMS host caching You could take the first KMS host off the net ( block port 1688 on the first KMS host for period of time) so when clients go to renew, they query DNS and find the 2nd KMS host. Thanks, Darrell Gorter [MSFT] 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

So, if I undertstand correctly, the current configuration is somewhat(?) ideal and no further modifications are req'd ? I'm not looking to permanantly demote the 1st KMS server nor 'draw outside the lines' and if this is the expected results, then I'm OK with that. Probably not a bad idea to temporarily block access to the 1st KMS server for a sanity-check to see if clients report into KMS server #2 tho, eh ? thx much !thx, ~~Robb

Hello Pitarobb, Correct, it's working as expected, as far as we can tell. To build up a count on the second server, it may best to block access on the 1st one for a period of time and ensures the second server is working. Thanks, Darrell Gorter [MSFT] 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

so far...so good 2nd KMS server now reporting 11 clients...will wait until it reach the magic #25 before opening back up TCP-1688 on 1st KMS server thx again for your insightthx, ~~Robb