In the task sequence, we’ll introduce a new variable named “TargetGroup”. As of now, this variable isn’t recognized by MDT
In my LAB setup, I’ve also incorporated the “WSUSServer” variable, which is familiar to those using MDT. Typically, this variable is set within the customSetting.ini. However, I chose not to do so to avoid affecting my other task sequences.
To proceed, you’ll need to modify the ZTIWindowsUpdate.wsf script, which can be found in the “script” directory of your deployment share. If the environment item “WSUSTargetGroup” is not empty, the script will write to the Windows registry, setting the WSUS Target Group accordingly.
If oEnvironment.Item("WSUSTargetGroup") <> "" then
oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetGroup", oEnvironment.Item("WSUSTargetGroup"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetGroupEnabled", 00000001, "REG_DWORD"
End if
Learn how to install .NET Framework 3.5.1 during MDT deployments without an internet connection by configuring the WindowsSource variable in the customsettings.ini file. This guide provides step-by-step instructions.
Learn how to skip locale and time zone selection during MDT deployments by configuring the customsettings.ini file. This guide provides step-by-step instructions for streamlining your deployment process.
Learn how to pre-select or make applications mandatory in MDT by configuring the customsettings.ini file. This guide provides step-by-step instructions for managing application installations during deployment.
0 Comments