Can you send the BDD.LOG? That might show what was going on. >From your description, it might be that the CustomSettings.ini lines aren't >set up right, but it's hard to guess, much easier to confirm with logs.
Thanks, -Michael From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Thursday, March 27, 2014 7:16 AM To: [email protected] Subject: [MDT-OSD] Fwd: [mssms] Excluding Windows Updates I sent this to the ConfigMgr list, but I am hoping someone on this list also has some experience fixing this issue: I have an MDT-integrated OSD task sequence in ConfigMgr 2012 that uses the ztiWindowsUpdate.wsf script from MDT 2012 SP1 (the customer does not use software updates in ConfigMgr). I am attempting to exclude the Windows Updates that require multiple reboots. So far, I have added the WUMU_ExcludeKB001= lines to the customsettings.ini but the updates still get marked for INSTALL and not SKIP. I also tried adding the WUMU_ExcludeKB001 as a task sequence variable per this recommendation: http://ccmexec.com/2013/09/tips-when-building-images-with-configmgr-2012-part-2/ That did not work either. How do I get these updates excluded? It seems like the settings are not being read from customsettings.ini. . . Has anyone seen this before? Thanks, Jeff
