I'm not sure this is the right place to put this topic, but i try. I have an enviroment, were i'm going to upgrade from server 2003 to Server 2008 R2. Because of this, i want to set up a kms host, so both my Server 2008 R2 and my future Windows 7 clients can activate in this. I have succesfully installed the KMS key on my Server 2008 R2, but when i install a new server 2008 R2, it don't activate. I know i need at least 5 servers to begin activate, but on my KMS host, it don't even make a count.

Feb 14, 2010  For other Windows Server 2008 R2 computers, you should type the KMS client setup key. A KMS key can be used on 6 computers. This means you can setup up.

I'm sure the default KMS port is pen(1688) because i can telnet through it from client to host. Monopoly mac download. I also know that my KMS is working, because i get the right error message when trying to activate manually(because of not enough counts) So my problem is, that my KMS host don't make a count, when a new server is installed. My KMS host makes the right DNS SRV record on the right port, but then i experiences that i suddently have multipel DNS SRV records in my dns. All the servers i install after, are making there own SRV record. Which i understand, is not the meaning. Only the KMS host should make this Record, right??

Am i right, that because of this, my KMS host don't make the right counts? And what can i do to fix this issue.

Hope somebody can help me. Hi, I believe that you typed the same KMS key on these Windows Server 2008 R2 computers. Please understand that you only need 1 KMS host. You should only type your KMS key on one Windows Server 2008 R2 computer. For other Windows Server 2008 R2 computers, you should type the KMS client setup key. A KMS key can be used on 6 computers. This means you can setup up to 6 KMS hosts for high availability.

They will not be counted and they will have their own SRV records. Now please run slmgr.vbs -ipk on the other Windows Server 2008 R2 computers. And then remember to delete any unnecessary SRV resource records from DNS and restart the computers.