I'm not sure this is accurate. It's my understanding that the threshold of 
(5) still requires physical servers, and does not include virtual 
machines. If you can point out a MS reference that states otherwise, I'd 
love to see it. 

This is a pain for our lab environments that we set up, which primarily 
run all virtual machines on ESX clusters. Typically we don't have 5 
physical Windows hosts in those environments, so the KMS activation issue 
and a threshold of (5) is always a problem.

Thanks

Chris Bodnar, MCSE
Systems Engineer
Distributed Systems Service Delivery - Intel Services
Guardian Life Insurance Company of America
Email: christopher_bod...@glic.com
Phone: 610-807-6459
Fax: 610-807-6003



From:   Malcolm Reitz <malcolm.re...@live.com>
To:     "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com>
Date:   10/13/2010 07:41 PM
Subject:        RE: KMS Best Practices



MS made some changes with the last update to KMS. The activation threshold 
for Server 2008/2008R2 has been moved down to 5 while remaining at 25 for 
other clients. Virtual machines now count towards the threshold, too. That 
said, with only 6 servers, Brian is correct in that MAK is the way to go 
for them. Are you going to have enough workstations to make this 
worthwhile?
 
I’d put the KMS on a server that will be around longest.
 
-Malcolm
 
From: Brian Desmond [mailto:br...@briandesmond.com] 
Sent: Wednesday, October 13, 2010 18:27
To: NT System Admin Issues
Subject: RE: KMS Best Practices
 
You’ll want to MAK the servers. You need 25 machines of a specific type 
(e.g. mapped to a specific KMS key) before the KMS activates against MS. 
 
Thanks,
Brian Desmond
br...@briandesmond.com
 
c   – 312.731.3132
 
From: Joseph L. Casale [mailto:jcas...@activenetwerx.com] 
Sent: Wednesday, October 13, 2010 7: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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


-----------------------------------------
This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law.  If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited.  If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments.  Thank you.
~ 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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Reply via email to