One thing I ran into-one of my two KMS servers is a DC that runs 2008 R2 as a Hyper-V guest. Last winter/spring when I migrated our Hyper-V cluster servers from 2008 SP2 to 2008 R2, I had to upgrade the integration services on all of the vms, including this KMS DC.
At that time, the KMS had deactivated, but I didn't realize it until other servers wouldn't activate properly. Re-entering the key fixed it, but I always check now if the "hardware" changes on the virtual (or physical) KMS server for any reason. From: Joseph L. Casale [mailto:[email protected]] Sent: Wednesday, October 13, 2010 4:17 PM To: NT System Admin Issues Subject: KMS Best Practices Getting ready to roll out a bunch of new stuff at a shop as they now have their OVS keys. I am reading up on setting up a KMS and as trivial as this appears, are there any concerns by people who have set these up that might not be outlined in TechNet? At the place in question, they have ~6 servers and only two would likely be around permanently, the DC and Exchange server. Make sense to install those with a KMS key? Thanks! jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
