Keith/Michael/Aaron, Thank you again for your assistance on this! I am indebted to all of you who faithfully assist on these lists.
Jeff On Thu, Sep 12, 2013 at 6:23 PM, Keith Garner <keith.gar...@hotmail.com>wrote: > Shamed into posting (Probably my bug anyways).**** > > ** ** > > http://keithga.wordpress.com/2013/09/12/ztiwindowsupdate-wsf-errors**** > > ** ** > > ** ** > > ** ** > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Daniel Ratliff > *Sent:* Thursday, September 12, 2013 2:47 PM > > *To:* mdtosd@lists.myitforum.com > *Subject:* RE: [MDT-OSD] ZTIWindowsUpdate.wsf**** > > ** ** > > So who wants to blog this one? J**** > > ** ** > > *Daniel Ratliff* > > ** ** > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Michael Niehaus > *Sent:* Thursday, September 12, 2013 5:42 PM > > *To:* mdtosd@lists.myitforum.com > *Subject:* RE: [MDT-OSD] ZTIWindowsUpdate.wsf**** > > ** ** > > Thanks for confirming that it worked – because the failure only happened > when the WU agent had an issue with one of the updates, this error handling > logic (which should just log the error with that update and move on to the > next one) wasn’t typically executed, and simulating that situation is > exceedingly difficult.**** > > ** ** > > So the proposed fix was just a good theory J (As for where you could > find that information, it was internal only. Microsoft Support could have > found the issue from the existing bug. Aaron and I could have found it in > our e-mail J)**** > > ** ** > > Thanks,**** > > -Michael**** > > ** ** > > *From:* listsad...@lists.myitforum.com > [mailto:listsad...@lists.myitforum.com] *On Behalf Of *Chris Nackers > *Sent:* Friday, September 13, 2013 3:37 AM > *To:* mdtosd@lists.myitforum.com > *Subject:* RE: [MDT-OSD] ZTIWindowsUpdate.wsf**** > > ** ** > > Awesome, thanks for confirming the fix, I’ll bookmark that in case I ever > run into it..**** > > ** ** > > Thanks Aaron for the fix!**** > > ** ** > > *Chris Nackers* > > *Microsoft MVP – Enterprise Client Management* > > Email: ch...@nackersconsulting.com**** > > *Nackers Consulting Services, LLC* > > ** ** > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Jeff Poling > > *Sent:* Thursday, September 12, 2013 10:31 AM > *To:* > mdtosd@lists.myitforum.com > *Subject:* Re: [MDT-OSD] ZTIWindowsUpdate.wsf**** > > ** ** > > Aaron,**** > > **** > > As I just posted, the fix you provided below corrected the issue. Thanks!! > **** > > **** > > As a follow up, I am curious. . . aside from posting to this list, is > there anywhere else I could have found the information you provided? I > spent a good amount of time researching, experimenting, etc. and never ran > across what you sent.**** > > **** > > Thanks again!**** > > **** > > Jeff**** > > ** ** > > On Wed, Sep 11, 2013 at 5:16 PM, Aaron Czechowski < > aaron.czechow...@microsoft.com> wrote:**** > > I’ve seen this (not personally, but a few reports). When manually running > the script on an affected system (Cscript.exe <path>\ZTIWindowsUpdate.wsf > /debug:true /debugcapture) it returned a more informative error: Runtime > error: Object doesn't support this property or method: > 'UpdateResult.GetUpdateresult'**** > > **** > > The script was tweaked with the following, which resolved the issue.**** > > **** > > Change line 403 from:**** > > **** > > oLogging.CreateEntry " Failed to download: " & > UpdatesToDownload.Item(item).Identity.UpdateID & _**** > > " result(" & UpdateResult.GetUpdateResult(item).ResultCode & ") : " & > UpdatesToDownload.Item(item).Title, MSIT_LogType**** > > **** > > To the following:**** > > **** > > oLogging.CreateEntry " Failed to download: " & > UpdatesToDownload.Item(item).Identity.UpdateID & _**** > > " result(" & UpdateResult.GetProgress.GetUpdateResult(item).ResultCode & > ") : " & UpdatesToDownload.Item(item).Title, MSIT_LogType**** > > **** > > (basically add “.GetProgress”)**** > > **** > > We do have a bug filed on this but not currently planned for the next > release.**** > > **** > > Aaron**** > > **** > > **** > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Jeff Poling > *Sent:* Wednesday, September 11, 2013 1:12 PM > *To:* mdtosd@lists.myITforum.com > *Subject:* [MDT-OSD] ZTIWindowsUpdate.wsf**** > > **** > > I am having issues with ZTIWindowsUpdate.wsf from MDT 2012 SP1 in a > ConfigMgr 2012 task sequence. The WSUSServer property is set in the > CustomSettings.ini. The task sequence is failing with the following:**** > > **** > > Unhandled error returned by ZTIWindowsUpdate: Object doesn't support this > property or method (438).**** > > **** > > If I look in the WindowsUpdate.log file on the PC, it shows that a > particular update failed to download:**** > > **** > > 2013-09-11 14:28:51:102 956 c8c > DnldMgr WARNING: BITS job > {4759CE33-BC46-40D6-8D0D-98571632DA66} failed, updateId = > {44D4BC60-4F06-4336-BCB5-CFEC48DE4A21}.101, hr = 0x80190194, > BG_ERROR_CONTEXT = 5**** > > 2013-09-11 14:28:51:102 956 c8c > DnldMgr Progress failure bytes total = 1290871, bytes > transferred = 72713**** > > 2013-09-11 14:28:51:102 956 c8c > DnldMgr Failed job file: URL = > http://myupdateserver/Content/ED/E9D5FD1F4E2AD662B0EE19E920C2A3CC5701DAED.psf, > local path = > C:\Windows\SoftwareDistribution\Download\cf102f1219cf1765c144149048219125\e9d5fd1f4e2ad662b0ee19e920c2a3cc5701daed-1 > **** > > 2013-09-11 14:28:51:118 956 c8c > DnldMgr Error 0x80244019 occurred while downloading update; > notifying dependent calls.**** > > **** > > I determined that the failing update was KB2506212. I added a > WUMU_ExcludeKB001=2506212 to the Default section in customsettings.ini.*** > * > > **** > > Prior to the ztiwindowsupdate.wsf step in the TS, I do a Use Toolkit > Package and a Gather; however, based on what I see in the logs, the Gather > never sets the WUMU_ExcludeKB property. It is set eaerlier in the task > sequence, but not when I need it for running the ZTIWindowsUpdate script.* > *** > > **** > > The customsettings.ini does have additional sections for different cities > based on defaultgateways.**** > > **** > > So, a number of questions:**** > > 1. Has anyone seen the windows update failure that I am seeing?**** > > 2. To exclude the update that is a problem, where does the WUMU_ExcludeKB > need to be in the customsettings.ini?**** > > **** > > Thank you.**** > > **** > > Jeff Poling**** > > ** ** > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information.* > *** > >
