Hi all,
I have two questions : the first one is easy, the second one is tricky.
1. I read 2012R2 is supported on vSphere 5.1U1.
But, I noticed that the create VM wizard do not display Windows 2012R2 in the OS list.
One can read Windows 2008 (32 bits), Windows 2008 (64 btis), Windows 2008R2 (64 bits) and Windows 2012 (64 bits).
So there is no specific entry for 2012R2 like for 2008R2. Is it ok ? Do I miss something like a patch to apply on my ESXi 5.1U1 to support 2012R2 ?
2. So here is my 2012R2 specific issue : the windows 2012R2 setup is unable to access to the share of the drivers (on a Windows 2012R2 share)
- I create a Windows 2012 VM
- I boot the VM on a Winpe 4.1 (Windows 2012R2) is image. I added to this winpe image the Vmware VM drivers using DISM.exe from Microsoft's ADK 8.1
- I launch setup.exe with a unattended.xml file. This file contains an entry for the path of the drivers
<DriverPaths>
</Credentials>
</PathAndCredentials>
</Credentials>
</PathAndCredentials>
</DriverPaths>
During the setup of Windows 2012R2, the access to the drivers on this Windows 2012R2 share fails.
The issue happens only on Windows 2012R2 VM, on Windows 2012 VM, with the same Vmware driver and same windows share, it's ok.
On a physical server, Windows 2012R2 setup succeed.
==> So it's not related to a credential issue to the windows share.
Here is an extract of the cbs_unattended.log from C:\Windows\Panther of a 2012R2 install
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Offline Image has 'PROCESSOR_ARCHITECTURE_AMD64' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 User has Administrator privileges. ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Offline SOFTWARE hive located at: E:\Windows\system32\config\SOFTWARE ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Loaded hive key name {bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/system32/config/SOFTWARE ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Found key '1' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Processing '1'... ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Path = '\\MyServer.mydomain\Distribution\Out-of-Box Drivers\Vmware' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Domain = 'mydomain' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Username = 'sOSDeployer' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Successfully read the password from the hive. ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Found key '2' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Processing '2'... ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Path = '\\MyServer.mydomain\Distribution\Out-of-Box Drivers\NULL' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Domain = 'mydomain' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Username = 'MyUser' ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Successfully read the password from the hive. ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Offline SYSTEM hive located at: E:\Windows\system32\config\SYSTEM ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Loaded hive key name {bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/system32/config/SYSTEM ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Searching for drivers at '\\MyServer.mydomain\Distribution\Out-of-Box Drivers\Vmware'... ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Making connection to share with username 'mydomain\myuser' and password 'password' ... ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Error DISM DISM Driver Manager: PID=1344 TID=488 Credentials failed when connecting to '\\MyServer.mydomain\Distribution\Out-of-Box Drivers\Vmware' ( HRESULT = 0x8007007F ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Searching for drivers at '\\MyServer.mydomain\Distribution\Out-of-Box Drivers\NULL'... ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Making connection to share with username 'mydomain\sOSDeployer' and password 'password' ... ( HRESULT = 0x0 ) - DriversCallback
2013-12-05 22:27:24, Error DISM DISM Driver Manager: PID=1344 TID=488 Credentials failed when connecting to '\\MyServer.mydomain\Distribution\Out-of-Box Drivers\NULL' ( HRESULT = 0x8007007F ) - DriversCallback
2013-12-05 22:27:24, Info DISM DISM Driver Manager: PID=1344 TID=488 Installed '0'
Here is an extrat of the cbs_unattended.log from Windows 2012
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found key '1' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Processing '1'... ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Path = '\\m065-ADK.pocx86.tstwinx.net\Distribution\Out-of-Box Drivers\Vmware' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Domain = 'pocx86' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Username = 'sOSDeployer' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Successfully read the password from the hive. ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found key '2' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Processing '2'... ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Path = '\\m065-ADK.pocx86.tstwinx.net\Distribution\Out-of-Box Drivers\NULL' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Domain = 'pocx86' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Username = 'sOSDeployer' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Successfully read the password from the hive. ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Offline SYSTEM hive located at: E:\Windows\system32\config\SYSTEM ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Loaded hive key name {bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/system32/config/SYSTEM ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Searching for drivers at '\\m065-ADK.pocx86.tstwinx.net\Distribution\Out-of-Box Drivers\Vmware'... ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Making connection to share with username 'pocx86\sOSDeployer' and password 'password' ... ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Credentials succeeded connecting to '\\m065-ADK.pocx86.tstwinx.net\Distribution\Out-of-Box Drivers\Vmware' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Locating INFs in '\\m065-ADK.pocx86.tstwinx.net\Distribution\Out-of-Box Drivers\Vmware' ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found directory Windows2008R22012 under search path ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:26, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found directory memctl under search path ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmmemctl.sys ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found directory mouse under search path ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmmouse.cat ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmmouse.inf ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmmouse.sys ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmmousever.dll ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmusbmouse.cat ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmusbmouse.inf ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmusbmouse.sys ( HRESULT = 0x0 ) - DriversCallback |
| 2013-12-12 16:02:27, Info | DISM DISM Driver Manager: PID=1368 TID=1296 Found file vmusbmousever.dll ( HRESULT = 0x0 ) - DriversCallback |
Thank you
regards
Hi Guys,
In fact, Windows 2012R2 setup cannot use credentials in the unattended.xml file to access drivers.
With credentials, windows setup will not access the share and will return an error : credentials failed. The reason is the developper forget to write the function in the code ![]()
It happens on every hardware or VM.
A workaroud is to mount the share containning the drivers with a net use before launching setup.
Now, I'm fighting against Microsoft to get a patch.:smileyangry:
MS is relunctant because it will modify the Windows 2012 R2 ISO image. The team is scared by regression issue, but this bug IS a regression.
I only hope to get a fix in the next Windows 2012R2 SP1 iso
Regards
In VMware G.O.S Compatibility Guide Windows 2012 is supported on ESXi 5.1 but Windows 2012 R2 is still not in support list.
VMware Compatibility Guide: Guest/Host Search
Best regards
Yours, Oscar![]()
I do not agree...
/Rubeck
Hi all,
For this issue I opened a case at Vmware support.
The guy told me it's normal there is only one entry for 2012 and 2012R2 in the VM setup wizard
But I'm still waiting an answer for my issue. I will update this discussion if I get information.
Any update on 2012 R2 not showing up?
Thank you.
Yes, any update on this? I'm wondering the same thing. Why the list says (in my case) esxi 5.1 U2 is supported for server 2012 R2, but it does not show up on the list of OS's. I'm guessing it'll be fine still, as VMWare Tools won't give it the R2 drivers, but I think the 2012 ones are probably going to be fine for R2 as well.
Thanks
I have W2k12R2 installed on ESXi 5.1U1. However, the first install was partially corrupted. Everything appeared to be fine under I tried to add server features and found that key powershell files were corrupted. I re-installed and things seem to be fine for now. If anything was corrupted again, I have not encountered them yet.
One thing you do have to do is set the bios EFI.
Do you have the 2012 R2 option for the OS in your drop down list? Or did you just choose the 2012 one?
Thanks
I just chose the 2012 option.
Hi,
Windows 2012R2 is not displayed in the list and it's ok according Vmware support.
My case is still under investigation by Microsoft. No new from Vmware support since one month.
Microsoft support asked for a network trace of the installation. And one can't see in the trace of the access to the network share of the drivers.
I workarounded it by installing the vmware tools thought setupcomplete.cmd.
I notice during all the tests Microsoft asked that if a network driver is missing, a message saying something "unable to access the network share with the credentials" may be displayed.
For instance if you use the Microsoft 2012R2 iso only without giving the vmnext3 drivers.
Nevertheless, Microsoft did not replicate in their labs yet. But they were using vsphere 5.5 instead of 5.1U1.
@mldmld
I went through the same thing. Called MS for support and spent an hour troubleshooting the install only to discover that some files were corrupted as stated above.
Again and as a test, create a new VM, set the bios to EFI, and do a new clean installation.
Running 5.1 U2 and no 2012R2 displayed here.
I beat on 2012R2 for weeks.
It kept giving me issues in VM.
It worked fine on a physical but was not happening in VMware. Turns out it was a corrupted .ISO!!?? Hard to believe since this .ISO worked just
fine on physical boxes. But sure enough,
downloaded a fresh .ISO and Presto!, everything worked as it should. Go figure.
Hi all,
I downloaded the iso again, and the contents of the 2012R2 iso changed between November 2013 and February 2014.
1. The name of the iso is not the same
02/05/2014 08:42 AM 4,477,562,880 SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-31419.ISO
11/04/2013 09:40 AM 4,297,373,696 SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-05182.ISO
And, with a windiff, I found 12 changed files !
-- C:\Distribution\Microsoft Sources\Windows2012R2 : C:\Distribution\Microsoft Sources\Windows2012R2 - November 2013-- includes left-only,right-only,differing files
.\sources\boot.wim different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\drvmain32.sdb different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\drvmain64.sdb different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\install.wim different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\sdbapiu.dll different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) 59dc30b8 2c20b4b6
.\sources\setupplatform.dll different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ebdb7395 5b737846
.\sources\setupplatform.exe different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\sysmain32.sdb different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\sysmain64.sdb different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\upgrade_bulk.xml different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
.\sources\wica.dll different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) dce97c85 af7a1eaf
.\sources\replacementmanifests\appxdeploymentserver-replacement.man different (C:\Distribution\Microsoft Sources\Windows2012R2 is more recent) ???????? ????????
-- 12 files listed
But infortunatelly, I still get the same error
2014-02-06 16:34:20, Info DISM DISM Driver Manager: PID=1632 TID=1612 Searching for drivers at '\\m065-adk.pocx86.tstwinx.net\distribution\Out-of-Box Drivers\Vmware'... ( HRESULT = 0x0 ) - DriversCallback
2014-02-06 16:34:20, Info DISM DISM Driver Manager: PID=1632 TID=1612 Making connection to share with username 'pocx86\sOSDeployer' and password 'xxxx' ... ( HRESULT = 0x0 ) - DriversCallback
2014-02-06 16:34:20, Error DISM DISM Driver Manager: PID=1632 TID=1612 Credentials failed when connecting to '\\m065-adk.pocx86.tstwinx.net\distribution\Out-of-Box Drivers\Vmware' ( HRESULT = 0x8007007F ) - DriversCallback
2014-02-06 16:34:20, Info DISM DISM Driver Manager: PID=1632 TID=1612 Searching for drivers at '\\m065-adk.pocx86.tstwinx.net\distribution\Out-of-Box Drivers\NULL'... ( HRESULT = 0x0 ) - DriversCallback
2014-02-06 16:34:20, Info DISM DISM Driver Manager: PID=1632 TID=1612 Making connection to share with username 'pocx86\sOSDeployer' and password 'xxxx' ... ( HRESULT = 0x0 ) - DriversCallback
2014-02-06 16:34:20, Error DISM DISM Driver Manager: PID=1632 TID=1612 Credentials failed when connecting to '\\m065-adk.pocx86.tstwinx.net\distribution\Out-of-Box Drivers\NULL' ( HRESULT = 0x8007007F ) - DriversCallback
2014-02-06 16:34:20, Info DISM DISM Driver Manager: PID=1632 TID=1612 Installed '0' drivers. ( HRESULT = 0x0 ) - DriversCallback
2014-02-06 16:34:20, Info DISM DISM Driver Manager: PID=1632 TID=1612 RETURN InstallDriversOffline (0) ( HRESULT = 0x0 ) - DriversCallback
Hi guys,
Microsoft support told me today that they replicate the issue with the same error code as me on Hyper-V.
Earlier, they tested, without replicating the issue on hyper-v / Dell Precision 690/Windows 2012.
But now, they replicate it with hyperV/Dell Precision t7500/Windows 2012 R2.
The support guy will try again the replicate it on Windows 2012 to verify. But earlier on this thread I wrote it was ok on 2012. So the issue is 2012R2 related.
The replication on Microsoft side will make the debuging easier.
Now they are debugging the kernel and setup.exe with the Debug and the Windows source code.
Best regards
ML
Hi Guys,
In fact, Windows 2012R2 setup cannot use credentials in the unattended.xml file to access drivers.
With credentials, windows setup will not access the share and will return an error : credentials failed. The reason is the developper forget to write the function in the code ![]()
It happens on every hardware or VM.
A workaroud is to mount the share containning the drivers with a net use before launching setup.
Now, I'm fighting against Microsoft to get a patch.:smileyangry:
MS is relunctant because it will modify the Windows 2012 R2 ISO image. The team is scared by regression issue, but this bug IS a regression.
I only hope to get a fix in the next Windows 2012R2 SP1 iso
Regards
Thanks for updating with this valuable info.... much appreciated.
/Rubeck
Hi guys
The patch is now available ! https://support.microsoft.com/kb/2989647/en-us
It has a prerequisite :https://support.microsoft.com/kb/2919355
I did not tested yet, but microsoft support told me to update all the images (standard, datacenter, core ...) in the install.wim 2012R2 file with the prerequisite + this fix using DISM /add-package.
So now, the question is answered.
MLD
