-1

I've been using hyper-v to create my base images for deployment to workstations. I create them on a Dell PowerEdge 2900 server running Windows Server enterprise 2008.

The Dell OEM key does not activate the guest O/S.

The server was originally purchased without an operating system. The O/S was purchased separately and is in a Microsoft VLSC account, so it does not have a COA with a virtual key (which dell indicates would be one solution)

Are there any other options?

Force Flow
  • 1,155
  • 5
  • 23
  • 45
  • Why do you need to active the Guest OS? – Chris S Jul 11 '12 at 20:06
  • Because windows updates don't function without being activated. I keep my base images for a long period of time, and just update them periodically, rather than re-create them from scratch. – Force Flow Jul 11 '12 at 20:17
  • Which OEM key are you referring to? If the server was purchased without an OS, it shouldn't have come with one. – NathanG Jul 11 '12 at 21:07
  • I am not up to date with server 2008 and win7 OEM, but back in the days of XP and Dell computers it worked as follows: 1) Dell OEM installs activated via a recognised key the the BIOS. This only works on the bare metal. An install via a Dell OEM CD/DVD would not activate in a VM. (Since the VM would be emulating its own BIOS and not a specific signed Dell BIOS). 2) I was told that OEM licences where connected to a specific computer and that use if OEM versions of windows in virtual environments was NOT allowed. I am not sure this is 100% true (but I am sure that is what I was told). – Hennes Jul 11 '12 at 23:08
  • @NathanG: Exactly. I don't have a virtual key, nor does there seem to be a way to obtain it after the fact. – Force Flow Jul 12 '12 at 01:05
  • @Hennes: A special DMI string in the BIOS is what is typically needed, however I've never been successful in implementing it in a virtual machine. – Force Flow Jul 12 '12 at 01:08
  • I haven't worked with Windows in some time, but would WDS resolve this issue? Then you don't need to use or maintain base images (in an operational sense), correct? – Aaron Copley Jul 12 '12 at 14:19
  • @AaronCopley You still need a valid product key. WDS can push out fat images (captured and redeployed) or thin images (stock OS images customized via unattend.xml or SCCM or other mgmt tools). Either way, he would still need a product key that works. – MDMarra Jul 12 '12 at 15:59
  • @MDMarra Sorry, I thought the concern is that the OEM key works on the target hardware but not on the Hyper-V guest. I get it now. – Aaron Copley Jul 12 '12 at 16:14
  • That's correct. The Dell OEM keys work on the target hardware, but not in a guest OS in Hyper-V. This is the problem I'm trying to solve. – Force Flow Jul 13 '12 at 03:00
  • Right. So you'll need a VLK, MAK, or KMS key, not an OEM one. – MDMarra Jul 13 '12 at 09:42
  • I called Microsoft, and after getting bounced around between 5 different departments, I finally got an answer (thought not the one I was hoping for). The stand-alone VLSC server 2008 license does not provide any activation capabilities for guest OSes. – Force Flow Jul 19 '12 at 19:58

3 Answers3

10

To address the title of your question, you don't.

To address the content of your question, get a non-OEM key that doesn't violate the EULA.

MDMarra
  • 100,183
  • 32
  • 195
  • 326
  • I called Microsoft, and after getting bounced around between 5 different departments, I finally got an answer (thought not the one I was hoping for). The stand-alone VLSC server 2008 license does not provide any activation capabilities for guest OSes. – Force Flow Jul 19 '12 at 19:58
  • Right. I was suggesting that you make a purchase that would allow you to use the product in a way that complies with the EULA. – MDMarra Jul 19 '12 at 19:59
5

If you bought your licenses via some sort of Microsoft Volume Licensing agreement, then your keys should be available within the VLSC portal. Presumably, you got the ISO for Windows from there - just go to the Product Keys area and use those to activate your system.

The documentation you describe is for using the license and media that would have come with the system if you bought Windows with the server - so it isn't really applicable to the situation.

Edit: It seems like there's some serious confusion about how licensing works. I'd recommend you find someone who can help you with the basics. I'll also add that licensing is hard, so there's only so far we can help you here. But at bottom, you have to license at least two instances of Windows - the Hyper-V host, and each guest. Consider them to be separate devices - each must have a proper license, and its appropriate key.

(And I see someone mentioned Win7 earlier. You're not trying to activate Win7 with a Server license, are you? That won't work at all.)

Community
  • 1
NathanG
  • 1,326
  • 10
  • 14
0

Use the key for Windows 2008 server found in the VLSC portal. Hyper-v is the thing inside the host emulating a computer that is running you guest OS. To activate the guest OS do as you would with a regular system and use the windows 2008 key.

Jonatan B
  • 25
  • 1
  • 5