I have reviewed the logs, and I see no problems with the way ZTIWindowsUpdate.wsf is handling the exclude list.
You imported the following items into your exclude list: Property WUMU_EXCLUDEKB001 is now = 2862330 Property WUMU_EXCLUDEKB002 is now = 2771431 Property WUMU_EXCLUDEKB003 is now = 2821895 Property WUMU_EXCLUDEKB004 is now = 2545698 Property WUMU_EXCLUDEKB005 is now = 2529073 Property WUMU_EXCLUDEKB006 is now = 2871690 However, Although the Windows Update Agent found 75 updates to install, only one of the updates was in the exclude list. Specifically, which update in the bdd.log file below were you expecting to be excluded? Perhaps you need to roll back your machine and try again. -k From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Thursday, March 27, 2014 11:16 AM To: [email protected] Subject: Re: [MDT-OSD] Fwd: [mssms] Excluding Windows Updates Michael, The log is attached. This is at a client site, so I scrubbed all identifiable information. After I looked at the log in more depth, it appears it is excluding the first update, but not any of the others. The section where it sets the WUMU_Exclude properties looks odd - it sets WUMU_ExcludeKB = <update> multiple times, once for each update. I think you will see what I mean when you look at the log. Thanks for any insight! Jeff On Thu, Mar 27, 2014 at 11:58 AM, Michael Niehaus <[email protected] <mailto:[email protected]> > wrote: 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]> [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Jeff Poling Sent: Thursday, March 27, 2014 7:16 AM To: [email protected] <mailto:[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-par t-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
