Update 2017.04.07 -> Added instruction to remove conditions on ComputerName wizard pane to force it to appear regardless of TS selected. Advantages: No more do you need to worry about the Deployed OS detecting the flash drive. Dis-Advantages: Some editing of built-in scripts is required. Deployments take slightly longer, because share is copied local before… Read More »
1. Add a step in Task Sequence to create a “.tag” file named after the OsdComputerName, which will be later used to determine the deployment duration. Command Line: cmd /c echo. > “Z:\Logs\%OsdComputerName%.tag” 2. Add a Task Sequence step to sync time with Deployment Server during the State Restore phase. Command Line: cmd /c net time \\192.168.56.1… Read More »
At the end of running “Update Media” for the 1st run or on any run with the “-force” argument passed, an update script can be called via the “LitetouchPE.xml” file. Here are the dynamic vars exposed that can be called via a custom script. ADKPath | C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit CONTENT |… Read More »
After the Litetouch OEM TS runs and the content is staged, on next boot up, no UEFI supported drives are found. To fix this, you must correct the litetouch oem task sequence. Before: After: Copy the corrected “Format and Partition..” steps from your deployment TS. Thanks goes to: https://social.technet.microsoft.com/Forums/en-US/db958f0d-b64c-4557-be79-cace90613493/litetouch-oem-task-sequence-uefi-support?forum=win10itprosetup -BG
When a computer takes longer than MDT likes to locate the Media share to complete the Deployment, this error is presented. It will retry to locate the deployment when OK is clicked, but if this happens on a unit quite a bit, use this workaround. Add the following code to your Scripts\Litetouch.wsf ‘//—————————————————————————- ‘// Set… Read More »
