|
There are several answers to your question.The DC MAK key will not activate a STD installation. When you install the MAK, the license 'model' will be converted to DC.As Sr says, the practical difference between DC and STD in a VM client is minimal. The things that matter between STD and DC are mostly effective at the host level, not the VM client level. (Number of VM clients licensed, AVMA, and so on.)It is easy to convert a STD license installation to a DC license. It is difficult (but not impossible) to convert the other way.If you have a volume license available, creating your VMs as STD instead of DC makes certain migration tasks easier. If you don't plan to migrate, there is no advantage.
This command can be useful if Windows didn’t activate due to a connection or server problem and you want to force it to retry. Slmgr.vbs /ato. And you’ll be given an activation ID if everything checks out. This allows you to activate Windows systems without Internet connections. And it seems to be five times on Windows Server 2008 R2.
Wil Tulaba wrote:Did you do a simple deploy from template, or did you do the 'customization' option as well. 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. Miwlgrl driver for mac free. 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..
|
There are several answers to your question.The DC MAK key will not activate a STD installation. When you install the MAK, the license 'model' will be converted to DC.As Sr says, the practical difference between DC and STD in a VM client is minimal. The things that matter between STD and DC are mostly effective at the host level, not the VM client level. (Number of VM clients licensed, AVMA, and so on.)It is easy to convert a STD license installation to a DC license. It is difficult (but not impossible) to convert the other way.If you have a volume license available, creating your VMs as STD instead of DC makes certain migration tasks easier. If you don't plan to migrate, there is no advantage.
This command can be useful if Windows didn’t activate due to a connection or server problem and you want to force it to retry. Slmgr.vbs /ato. And you’ll be given an activation ID if everything checks out. This allows you to activate Windows systems without Internet connections. And it seems to be five times on Windows Server 2008 R2.
Wil Tulaba wrote:Did you do a simple deploy from template, or did you do the 'customization' option as well. 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. Miwlgrl driver for mac free. 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..