I would find it strange if you could add an OEM key to a volume license install (I know you could with XP, but XP never had any kind of anti-piracy capabilities to speak of, while both Vista and Win7 do). You aren't supposed to be able to install OEM licenses yourself with a volume account, rather you should be transitioning your OEM licenses into your volume account thereby adding those license counts to your total available volume licenses. This should not matter whether it is EA, eOpen, etc. Tim
-----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Tuesday, August 25, 2009 12:41 PM To: NT System Admin Issues Subject: Re: Windows 7 Technet or MSDN media and Product keys On Tue, Aug 25, 2009 at 9:53 AM, Don Guyer<[email protected]> wrote: > Don't you get a "special" key to use for software licensed through > eOpen? For Vista, at least, and if you're not using a license server: you get a Product Key that works more-or-less like a retail or OEM key does. During install, you get prompted to enter a PK. You can skip that, in which case it prompts you for the edition of Vista you want to install. (It can derive that from the PK if you enter one). Once the install is finished, you have to activate. If you didn't enter a PK during install, you have to enter it then. If it doesn't match the edition you installed, it refuses it. You've got... 30 days, I think, to enter a key and finish activation before it starts shutting things off. The interesting part was that the eOpen install image has rejected OEM keys when I've tried them. From what TVK says, it sounds like the MVLS/Technet keys may be interchangable. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
