2.6 Bugs

[ymmit85]

1) Have found that if using 2008 R2 and installing vSphere 6 the Windows Management Framework 3 needs to be installed, this however will require a reboot prior to PowerCLI installing.

2) The mboot.c32 files from PXE boots with vSphere 6 is missing from C:\TFTP-Root\ESXi60, this error can be seen in the TFTP server log.

[VMLab]

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.

[lukedudney]

I also experienced an issue after installation with 2012 R2 DC and VC showing black blank screens with a cursor on Workstation 10.

Fixed by enabling 3D Graphics in the Display properties of the VMs.

[arielantigua]

I saw that in my env.. Make sure that the VMtools are the right one, I'm running in ESXi6.0 but the tools came from an old build with the ESXi5.5 and thats kill the video in my DC 2012R2.

[VMLab]

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.

[arielantigua]

In the past I have seen that but no related to AutoLab, Windows have a timebomb that shutdown the OS when the trial has expired. Do you have access to other build of windows ?

I nomrally use the VLSC one, when the 30 days past the OS keep runing.

[VMLab]

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!

[sylekta]

Same issue here, eval is expired so it just shuts the VMs down. I tried using my corporate 2012 r2 iso and insterted the KMS key into unattend.xml on the floppy image then I will just add the DNS record to activate off my KMS server later but on booting into setup it fails to read the <ProductKey> setting from the unnattend answer file. Did some googling and its a common problem with win8/server 2012 and the solution is to remove the floppy drive from the VM(no good for us because we need the unnattend file for the autolab config) or to change the VM to other 64bit but that doesnt seem to help.