MDT 2013 & Microsoft Update Catalog Updates

Question

Hiya,

I have two issues here, which I'm hoping someone maybe able to assist.

Firstly, could you kindly help me figure out why MDT doesn't seem to be pushing out packages through the Package folder, from what I gather it's possible to have an isolated deployment environment without the need of WSUS. I've read up about this function and in theory I should be able to use .MSU and/or .cab files. I understand it's manual, which is generally speaking not the best way. Just to add some context I've worked with an WSUS and have set this up in the past and it works like a dream, as long as you amend the customsetting.ini file.

My second issue relates to the first, I'm currently trying to use the Templates folder GPOPacks, and have managed to make my own script to apply the Local Group Policies, however, I would really appreciate it if someone could shed some light on why MDT isn't applying the Local Group Policies I've extracted using LGPO.exe. Again usually I would use Group Policies in an enterprise environment, but this environment is different and this isn't an option.

In my case, I've been asked to create a Zero Touch environment where updates / local group policies are injected into the image, the machines will be completely air gapped and will never touch the internet. Which I'm pretty advanced in terms of Network PXE booting, but the local Media approach doesn't like the Task Sequence.

Currently I'm using:

Operating System - Windows 10 / 11

MDT 2013 - Microsoft Deployment Workbench

Microsoft

Version: 6.3.8456.1000

And the Windows 11 ADK and Addon

Any help would be muchly appreciated.

Answer 1

Hi there,

As it seems that the MDT is not pushing your updates and isn't applying the Local Group Policies, it would be right to start your troubleshooting by analyzing the logs first.

Each MDT script automatically creates log files when running. The names of these log files match the name of the script.

The MDT log file format is designed to be read by CMTrace. Use this tool whenever possible to read the log files, because it makes finding errors much easier.

CMTrace https://learn.microsoft.com/en-us/mem/configmgr/core/support/cmtrace

Then based on your error code we can troubleshoot the issue. For example Error code 9903 means an Unexpected issue installing the updated Windows Update Agent. You can get the error code list from the below link.

Troubleshooting Reference for the Microsoft Deployment Toolkit https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshooting-reference

------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 2

Has anyone got any ideas why the following update doesn't work using MDT?

windows10.0-kb5012592-x64_ea2cbcc90d772b5c41410e88f96e6cad1608f45b.msu

I've tried to install it on -

OS Name - Microsoft Windows 11 Pro
Version - 10.0.22000 Build 22000

I can see the Servicing Stack 10.0.22000.469 is already installed, when you check this on the web it seems to be an old update, and has been replaced with kb5012592.

Any ideas would be apprecicated.