Jan 06, 2014 Automatic virtual machine activation is an easy to miss, but really handy feature in Windows Server 2012 R2. One of the primary reasons why people buy. I am trying to activate MS Server 2012 R2 Standard and I'm having issues. I have installed the software from the ISO file I downloaded from the volume licensing site.

Wil Tulaba wrote: Did you do a simple deploy from template, or did you do the 'customization' option as well. Ibm Os2 Warp Server V4 52 Cp2 7z. The reason I ask, is because if you do just the deploy without the customization it can duplicate the SID and a few other things in the registry like reporting to a Windows Update Server as the same server as well.

I'm wondering if that could potentially have an effect on windows activation as well. I am trying Bill's suggestion by doing a Sysprep. That should resolve all that. I will let you know if it works. IRJ wrote: Well, I marked the actual correct answer.

The IP address I gave this server was in use by an old appliance that I didnt even know about. It seemed to go online and work fine, but I couldnt join the domain and do certain things. I changed the IP and everything started working. I am about 99.9% sure that's why it wouldnt activate. I went back to some of my old notes dealing with a XenServer template I did a while back and there was a note about not adding any virtual network interfaces to the template and to do those after deploying it.

Maybe that could help alleviate any future problems? Bill Kindle wrote: IRJ wrote: Well, I marked the actual correct answer. The IP address I gave this server was in use by an old appliance that I didnt even know about. It seemed to go online and work fine, but I couldnt join the domain and do certain things. I changed the IP and everything started working.

I am about 99.9% sure that's why it wouldnt activate. I went back to some of my old notes dealing with a XenServer template I did a while back and there was a note about not adding any virtual network interfaces to the template and to do those after deploying it. Maybe that could help alleviate any future problems? What you said about sysprepping made me re-think the way I do my templates.

I learned that all you had to do in VMWare was create a template with no sysprepping needed. I have been doing it this way for a long time now. What I found out was that when you create a machine from template, It gets customized for you by VMWare.

It basically does the same thing as a sysprep.