Recently, on a professional services engagement, we encountered a situation, where the Customization Wizard was failing to successfully apply SYSPREP to Windows 2012 Servers. Because our main objective and my time was focused on other areas, we could not take time to resolve the underlying the root cause, so we needed a work-around. This led us to applying SYSPREP manually, which I had not done in a long time. Here are the details that we applied toward using SYSPREP manually in a VM template
Our main concern is if we deploy two VMs from a template or VM that already has a SID, then an issue may occur if we try to add both new VMs to the domain. The following error may occur when adding the second VM.
To fix this in the second VM, you can use these steps:
1 – Open RUN and enter sysprep
View original post 192 more words
First of all assume that your KMS is functional, having Office 2013 key installed. Also the client is able to reach the KMS server on port 1688, and the setting in your internal DNS system is correct.
You can check registry on the client for this:
Here are the two commands you can try specify the KMS server and do manual activation.
cscript ospp.vbs /sethst:fqdn_of_your_kms_server
cscript ospp.vbs /act
For Windows activation, the commands are like this:
- cscript slmgr.vbs /skms fqdn_of_your_kms_server
- cscript slmgr.vbs /ato
Further, you may want to try uninstalling the product key on a client and then reinstalling it.
slmgr /upk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
then slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Reference page from Microsoft: http://technet.microsoft.com/en-us/library/ee624355(v=office.15).aspx
This is a brilliant way to fix the issue.
Also there are two other blogs and a Microsoft thread about the same:
In our environment, we have full implementation of KMS host with the new Windows 8 and Windows Server 2012 keys, (I would write about how run this upgrade later). Somehow, when we tried to activated a deployed Windows Server 2012, we got the following error log: event ID 8200 and 1014 with error code 0x80072EE2.
Verified that the firewall port 1688 and DNS records are all fine in where this server is located, and through a few research, I found this thread in TechNet, although the discussion was in 2009, it seems still applicable.
I got the new client setup key from here:
then ran the following commands:
I guess the root cause could be someone tried to activate this server incorrectly before we started working on it, or that was not from a volume license copy. I would give credit to cybercoaster in Microsoft forum. Thanks,
Another link might be useful: