The OEM keys are managed separately.
*ASB *(Find me online via About.Me <http://about.me/Andrew.S.Baker/bio>) *Exploiting Technology for Business Advantage... * On Tue, Feb 15, 2011 at 10:04 AM, Ben Scott <mailvor...@gmail.com> wrote: > On Tue, Feb 15, 2011 at 9:49 AM, Damien Solodow > <damien.solo...@harrison.edu> wrote: > >> I am getting ready to purchase 35 new PCs with Windows 7 Professional. > >> I also have 15 PCs with XP covered by Software Assurance (SA) and > >> another 10 for which I will purchase Windows 7. I want to use a > >> common Windows 7 image on the machines > > > > Long story short though, you’ll probably want to use KMS. > > How does KMS interact with OEM Windows licenses and their keys, > though? This is a question that's been rattling around in the back of > my head for a while. For instance, if you've got 25 PCs covered by > volume license seats, and 35 PCs which came with Windows 7 OEM, will > the OEM licenses eat up volume license seats? Do you enter the OEM > keys into KMS? Do you have to manually enter the OEM keys when > imaging the OEM PCs? > > With XP, you just reimaged the OEM PCs from volume license media > with your volume license key and you were done; there's no > "activation" for XP. Obviously that doesn't fly for Win 7. > > -- Ben > > ~ 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
