David Lochhead
asked on
Installing MDT (8450) with WDS (ADK 1903) and updating deployment share error.
After installing WDS role then ADK then MDT I created a deployment share using the defaults in all three installs and when I try to update the deployment share I get this error :
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files\Windows AIK\Tools\PETools\x86\winp
WIM file mounted.
Exit code = -1073741819
DISM /Set-TargetPath failed, rc = -1073741819.
DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.
=== Completed processing platform x86 ===
=== Making sure the deployment share has the latest x64 tools ===
=== Processing LiteTouchPE (x64) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\DeploymentShare\Operati
WIM file mounted.
Exit code = -1073741819
DISM /Set-TargetPath failed, rc = -1073741819.
DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.
=== Completed processing platform x64 ===
It is on a dedicated Win 2016 ENT server and 64 bit versions used across the board. Nothing but the deployment share is created and no OS or task sequence has been created yet and rules and bootstrap.ini and customsettings.ini are untouched outside of the deployment share wizard.
Does anyone have any ideas ?
Thank you
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files\Windows AIK\Tools\PETools\x86\winp
WIM file mounted.
Exit code = -1073741819
DISM /Set-TargetPath failed, rc = -1073741819.
DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.
=== Completed processing platform x86 ===
=== Making sure the deployment share has the latest x64 tools ===
=== Processing LiteTouchPE (x64) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\DeploymentShare\Operati
WIM file mounted.
Exit code = -1073741819
DISM /Set-TargetPath failed, rc = -1073741819.
DISM was unable to set the system root (target path) for the Windows PE image, so the update process cannot continue.
=== Completed processing platform x64 ===
It is on a dedicated Win 2016 ENT server and 64 bit versions used across the board. Nothing but the deployment share is created and no OS or task sequence has been created yet and rules and bootstrap.ini and customsettings.ini are untouched outside of the deployment share wizard.
Does anyone have any ideas ?
Thank you
aravind anche
uninstall ADk and reinstall latest version and see it works
with the ADK you need the PE tools as well it is no longer there by default.
you should have deployment toolkit version 8456, adk 1903 and adk winpe 1903
you should have deployment toolkit version 8456, adk 1903 and adk winpe 1903
ASKER
I enabled the WDS role first and then rebooted , installed MDT without making a deployment share. Configured WDS with a boot.wim and install.wim from the OS DVD (1903). Then I installed the ADK PE addon by downloading the installers and running it locally rather than the install immediate option (3.37 GB total size). Then I copied over the two PE 1903 updated files.I created a deployment share with everything defaults except the image drive location. Once it was finished I tried updating the share (not with the recreate all disks option just the update share option) and I received the original error message.
Then I copied over the two PE 1903 updated files.
HUH, not needed, where did you copy these files?
I created a deployment share with everything defaults except the image drive location. You can change the location of the Deployment share itself. There is no option to change the image drive location
after creating your litetouch.wim You then add it to WDS
HUH, not needed, where did you copy these files?
I created a deployment share with everything defaults except the image drive location. You can change the location of the Deployment share itself. There is no option to change the image drive location
after creating your litetouch.wim You then add it to WDS
ASKER
From the Readme.txt from WSIM1903.ZIP from Microsoft as an update for Windows 10 1903 X 64 ADK :
Updating ImgMgr.exe and ImageCat.exe (manual):
==========================
3. Install the Windows 10 Version 1903 ADK if you have not already installed it; note down the path you are installing
the ADK to. If you already installed the ADK, locate its path by running the following from a command window
dir /s /b imgmgr.exe
4. Unzip the contents of the .zip archive by right clicking on it and selecting Extract All...
5. From an elevated command line, assuming that the ADK is installed in the default path of:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools
move into the root of the folder that contains the contents of the expanded zip and then run the following commands:
xcopy /Y imagecat.exe "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM\imagecat.exe"
xcopy /Y imgmgr.exe "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM\imgmgr.exe"
If the ADK was not installed in the default location, then please make sure to update the above paths appropriately based
on the path determined in Step 3.
Image location was incorrectly stated and it should be deployment share.
Updating ImgMgr.exe and ImageCat.exe (manual):
==========================
3. Install the Windows 10 Version 1903 ADK if you have not already installed it; note down the path you are installing
the ADK to. If you already installed the ADK, locate its path by running the following from a command window
dir /s /b imgmgr.exe
4. Unzip the contents of the .zip archive by right clicking on it and selecting Extract All...
5. From an elevated command line, assuming that the ADK is installed in the default path of:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools
move into the root of the folder that contains the contents of the expanded zip and then run the following commands:
xcopy /Y imagecat.exe "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM\imagecat.exe"
xcopy /Y imgmgr.exe "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM\imgmgr.exe"
If the ADK was not installed in the default location, then please make sure to update the above paths appropriately based
on the path determined in Step 3.
Image location was incorrectly stated and it should be deployment share.
ASKER
Is this the correct order ?
WDS role enabled
ADK install
MDT install
ADK PE install
ADK WSIM1903 xcopy
Configure WDS
Configure MDT with deployment share and OS (1903)
Update deployment share to generate WINPEX64 boot image
Import WINPEX64 boot image into WDS
Configure task sequence to capture reference image of 1903 with custom apps , etc
Configure task sequence to deploy captured image
WDS role enabled
ADK install
MDT install
ADK PE install
ADK WSIM1903 xcopy
Configure WDS
Configure MDT with deployment share and OS (1903)
Update deployment share to generate WINPEX64 boot image
Import WINPEX64 boot image into WDS
Configure task sequence to capture reference image of 1903 with custom apps , etc
Configure task sequence to deploy captured image
nothing wrong with it. you're missing the deployment share, import operating system which is required for the capture task sequence .. but should be fine.
ASKER
That is already listed after configuring WDS. I have a strange issue with the data drive permissions upon creation. A right click and new folder creates 4 folders immediately. It seems to be a well known issue with 2016 so I will start by deleting the data drive and creating another before doing the other steps. The environment is VMWare 6.5
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.