Hello,
I am trying to set up a KMS server on one of our two domain controllers. Both machines are identical running Server 2003 R2 but are hosting 2 seperate domains and are on two different subnets (one being 192.168.168.1 the other 192.168.0.1). I have the KMS server setup on the 192.168.168.1 server. I cannot successfully get the two servers to add eachother in DNS, and I cannot get clients on the 192.168.0.1 to see the KMS server. I have read through the Microsoft documents endlessly and have tried adding the registry key they suggested but to no avail. Any ideas on what I’m doing wrong?
Given the criteria of not having a impact on the users work flow a domain rename/forest redesign is not advisable. I would just do the manual upgrades
There’s 3 servers. 1 is the NJ forest, one is the NY forest, and the other is a spare server thats not even been designated a use yet and is newer than the other 2 servers but not by much (and if you have any suggestions for it whether it be domain migration or redoing things for redundancy please don’t hold back).
My original estimates were wrong about the number of users on each forest. Also, we only needed and have 40 upgrade licenses. 25 will never be reached on each forest. I’m thinking if I don’t do something drastic with this restrictive network setup we have going on, I should just go ahead and use the MAK keys and get the upgrades rolling this week.
Yep there it is in black on white. Clearly aimed at enterprises.
“KMS requires a minimum number of computers in a network environment. You must have at least five (5) computers to activate computers running Windows Server 2008 or Windows Server 2008 R2 and at least twenty-five (25) computers to activate computers running Windows Vista or Windows 7.”
But you have 60 computers with appox 30 in each forest which meets the 25 minimum workstastion requirement. It appears its the server side that is lacking.
How many servers do you have?
Regular activation is looking better all the time.
So it looks like the only solution here is a domain rename since the problem is most likely the Netbios names. Would you agree?