Resolving SQL connection issues with MDT. Errors ZTI Error opening SQL Connection. Unable to establish Database connection using [CSETTINGS]

MDT typically uses letter "Z" to map a drive. What occurs when an application necessitates the use of the Z:\ drive during the process of deploying an image through MDT? The deployment typically fails unless the MDT mapping is moved to another letter, lets make that change to MDT.

Failure Deploying Applications with SCCM\MECM with Error 0x87d01106 and 0x80070005

Windows ADK PE for Windows 11 22H2 fails to install. Clicking on the Windows PE tab crashes MMC generating the following errors Could not find a part of the path 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs', unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the path specified.

Can Windows 10 and a suite of applications, including Office, be automated without fancy deployment tools? The short answer: yes, but it’s not pretty. There are problems that MDT and SCCM simply make disappear. I’m not thrilled about dealing with these issues. Manual prep takes way more time, is less functional, and only starts to make sense if you have more than a handful of Windows clients to deploy.

During MDT or ConfiMgr deployment of Windows 10, press Shift+F10 whilst Windows detects devices. A command prompt with System Privileges will pop up, allowing all sorts of shenanigans and without being logged by SIEM, those agents won't be running yet. Also, during Windows 10 upgrades, Bitlocker drive encryption is disabled, allowing the same attack. This is an old issue raised some 3 to 4 years ago.... Well, today on my test rig during a 1909 deployment, I was just curious,