Doctor-Bob
asked on
Windows deployment server - booting from the capture image does not invoke the Capture Image Wizard
Hi,
REF: https://technet.microsoft.com/en-us/library/jj648426.aspx
I have:
1. installed the WDS role on WIN2012R2 in standalone mode,
2. installed Win7Pro on a reference machine (I have tried both a VM on an esx host and a physical box)
3. added a boot image from the install media used above (sources\boot.wim)
4. In the case of the physical machine, added the NIC drivers to the boot image created above
5. Created a capture image from this boot image as per https://technet.microsoft.com/en-us/library/jj648426.aspx#BKMK_CreateCustomInstall
6. ran sysprep.exe /oobe /generalize on the reference machine created in 2 above
7. Booted reference machine from NIC, choose the capture image and am presented with the attached screenshot, I have tried this multiple times using a VM & physical reference machine and using different install media, I must be doing something wrong at the capture image creation stage but Im sure Im following the documentation.
Thanks
bob
20150902_104758.jpg
REF: https://technet.microsoft.com/en-us/library/jj648426.aspx
I have:
1. installed the WDS role on WIN2012R2 in standalone mode,
2. installed Win7Pro on a reference machine (I have tried both a VM on an esx host and a physical box)
3. added a boot image from the install media used above (sources\boot.wim)
4. In the case of the physical machine, added the NIC drivers to the boot image created above
5. Created a capture image from this boot image as per https://technet.microsoft.com/en-us/library/jj648426.aspx#BKMK_CreateCustomInstall
6. ran sysprep.exe /oobe /generalize on the reference machine created in 2 above
7. Booted reference machine from NIC, choose the capture image and am presented with the attached screenshot, I have tried this multiple times using a VM & physical reference machine and using different install media, I must be doing something wrong at the capture image creation stage but Im sure Im following the documentation.
Thanks
bob
20150902_104758.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes yo_bee all seems to be working now, thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
<snip>
John Masson wrote:
Just ran into this problem with 2012R2 Datacenter. Spent a good part of the day screwing around with it.
Here's the solution that worked for me:
Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)Open a command line window with administrator privileges, you'll run the two DISM commands here
Mount the WIM file with the command
dism /mount-wim /wimfile: /mountdir: /index:1
Unmount the WIM file, committing changes (even though you didn't make any) with the command
dism /unmount-wim /mountdir: /commit
</snip>
This seems like a clunky workaround though, anyone know why this happens or if there is a more permanent fix?