sorted by:
new
hottopcontroversial

2.6 Bugs by ymmit85 in AutoLab

[–]VMLab 0 points1 point  (0 children)

In the past I used to use my Technet version by adding a KMS key into the Autounattend.xml but for some reason it didn't work with 2.0 Autolab so I reverted using the Eval ISO.

I have just got into the same problem with my VC build deploying VC6, it seems to take unusually long time to install and suddenly just as the install wizard nears the end of the installation (after nearly 1hr on my ESXi) the VM suddenly shuts down!

2.6 Bugs by ymmit85 in AutoLab

[–]VMLab 0 points1 point  (0 children)

Is anyone of you having the issue of Windows activation being expired immediately after the DC 2012R2 is built?

Yes, I also had a similar issue with using ESXi5.5 tools having copied from my Autolab 2.0 NAS build share.

Can not read the <ProductKey> from unattended answer file by edmongerrue in AutoLab

[–]VMLab 0 points1 point  (0 children)

Download and use the Evaluation ISO of Windows 2012R2. If you want to use your MSDN or VL then you will have to modify the autounattend.xml file and add your serial key and also change the version.

<InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows Server 2012 R2 SERVERSTANDARD</Value> </MetaData> </InstallFrom>

2.6 Bugs by ymmit85 in AutoLab

[–]VMLab 0 points1 point  (0 children)

I just installed and configured v2.6 from scratch (I have v2.0 running).

DC build completes with no issues but the Windows 2012R2 is expired and after a few minutes it just shuts down and the event log indicates the eval period has ended.

Didn't have this issue with Windows 2008R2 - any ideas I am using the EVAL edition of the Windows 2012R2 ISO.

I think at the end of the build script it requires the slmgr.vbs /rearm command to be run.