Category Archives: MDT

The MDT 2013u2’s “Litetouch OEM Task Sequence” does not partition UEFI drives using GPT

By | August 26, 2016
0 Comment
Share

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

SOLVED: Netmotion XG Mobility Client Install Driver Prompt

By | August 11, 2016
0 Comment
Share

SOLVED (08/11/2016): http://www.netmotionwireless.com/support/docs/MobilityXG/1100/help/mobilityhelp.htm#page/Mobility%20Server/setup.03.39.html The “NM_Options” property MUST be used, even when using the MmsAddress MSI property. So my final install string was this: ## <Perform Installation tasks here> Show-InstallationProgress -StatusMessage ‘Installing NetMotion XG Client. This may take some time. Please wait…’ Execute-Process -Path “msiexec.exe” -Parameters ” /norestart /quiet /package “”$dirFiles\Mobility_xg_client_11.01_Win7_x64_release.msi”” NM_ADDRESS_VALUE=x.x.x.x:x EQSI=””1″” NM_Options=””$dirFiles\options.inf”” REBOOT=ReallySuppress” Forum… Read More »

My edits for PSAppDeployToolkit’s Wrapper PS1

By | August 10, 2016
0 Comment
Share

http://psappdeploytoolkit.com/ ‘s wrapper is my new favorite wrapper for applications I add to MDT or SCCM.  As Johan & others have stated, the main reason to use wrappers is how mush it eases testing of creating packages.  Here are my 2 edits I make to all of my Deploy_Application.ps1 scripts. 1.Tell PSAppDeploy to copy the… Read More »

MDT does not like WIMs with 2 indexes!

By | July 27, 2016
1 Comment
Share

I like to capture my thick/hybrid WIM files with SCCM capture ISOs.  The big problem with this is that MDT doesn’t like WIM files with multiple indexes.  The symptom is that MDT appears to import the WIM, but NO OSes are added to the Deployment Workbench.  To fix this you must delete the 1st index… Read More »

“FAILURE ( 5624 ): -2147467259 0x80004005: Run DISM..” error when applying WIM

By | July 16, 2016
1 Comment
Share

Scenario: Deploying Windows 10 x64 with MDT2013U2 to CF-20A via LAN. Solution: This issue occurred, because an Update of the Media share was initiated at the same time of a deployment and the update was set to split the OS WIM to support UEFI.  Once Media update was complete, the deployment ran with no issue.