none
ZTIWindowsUpdate Failing

    Question

  • I have been getting the error "ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: Object doesn't support this property or method (438)" when I use any task sequence with the Windows Update step enabled. This occurs when deploying any image, Windows XP, Server 2008(R2), Windows 7, or Windows 8.

    I have updated to MDT 2012 Update 1 (6.1.2373.0). I have updated the WAIK to version 2.0(?) (not sure of the version number but, it is using the Windows 8 PE).

    The troubleshooting information I have found to date states that this issue is related to the WSUS server not having the hotfix (KB2734608) installed to provide support for Windows 8/Server 2012. All WSUS 3.0 servers in the update environment have had this hotfix applied, restarted, and resync'd.

    Even after all this has been done, I still am getting the same 438 error message when the task sequence gets to the Windows Update steps. The machine properly detects that it needs updates, downloads them to the target computer, then errors out when they try to install. Without fail, every machine that fails during the task sequence, will check in with the update server, download and install their required updates just like any other machine on the network. They just will not do this during the task sequence.

    All of these issues did not occur until the current update of MDT 2012 was applied. Any ideas of what is happening here and what I might do to fix it?

    Monday, March 04, 2013 10:26 PM

Answers

  • Yup, that worked fine. : )

    Are you trying to create a new image or updating an existing one?  I noticed the log had two date sets (2012-04-16, which worked correctly) and the one from today (2013-03-05, which is having issues).

    In any case, digging into the log, I see issues downloading EULA files.  Your Scan Cycle appears to work fine (meaning the WSUS database is being talked to and the meta-data exists), but as soon as it tries to download something, it throws a BITS error and 0x80244019 code.  Each pass looks the same (Finds updates, tries to download, fails).

    This looks like a WSUS content problem more than an MDT problem.  According to another TechNet forum for WSUS (http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/299d83c9-d859-4d62-9a04-a0f8830118a5/), you may want to run a wsusutil reset on your WSUS server and ensure that everything downloads properly.  You probably have more patching issues than just imaging currently and haven't realized it yet.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked as answer by Jacob Brixey Friday, March 08, 2013 4:41 PM
    Wednesday, March 06, 2013 12:12 AM
    Answerer

All replies

  • I'd start by checking out the %windir%\WindowsUpdate.log on the machine to see if maybe there is more information or the error is coming from a specific update.  If it's a specific update, you could exclude it in your CustomSettings.ini (via WUMU_ExcludeKB001=KBxxxxx;).  Also look at your ZTIWindowsUpdate.log to see if there is more info.  Andrew has a good blog post on all this (http://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/).

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, March 05, 2013 1:46 AM
    Answerer
  • The script is failing when it makes a call to the Windows Update Agent... somewhere... not sure where.

    On a machine that has the problem, can you copy down the \\mdtserver\deploymentshare$\scripts\* folder locally and run the following command:

    cscript.exe <path>\scripts\ZTIWindowsUpdate.wsf /debug:true /debugcapture

    The /debug:true and /DebugCapture will prevent the script from writing the "friendly": "ZTIWindowsUpdate: Object doesn't support this property or method (438)" error message, and instead it will immediately crash the script and write out to the console the line number within ZTIWindowsUpdate.wsf where it crashed. That will help debug the problem, and suggest a work around.

    Additionally. the WindowsUpdate.log file will help diagnose the problem.


    Keith Garner - Microsoft PM

    Tuesday, March 05, 2013 5:42 AM
    Moderator
  • Thanks for your input! I have done as you have suggested and copied the scripts folder to the local machine and run the ZTIWindowsUpdate.wsf file in debug.

    The following is returned:

    ZTIWindowsUpdate.wsf(402, 6) Microsoft VBScript runtime error: Object doesn't support this property or method: 'UpdateResult.GetUpdateResult'

    I would attach the WindowsUpdate.log file, but haven't been able to sort out how to do that yet. Pasting the contents into the body of the post would be extreme as it is a few hundred lines.
    Tuesday, March 05, 2013 11:13 PM
  • You can use DropBox, Google Drive, SkyDrive... whatever lets you upload something and allow to share with others.  Just provide the "open" link here when you have it so we can look at the logs.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, March 05, 2013 11:20 PM
    Answerer
  • This should do the trick, let me know if it does not.

    https://docs.google.com/file/d/0B6-NQJxl2hfielpodFpDdHhTOVk/edit?usp=sharing

    Tuesday, March 05, 2013 11:27 PM
  • Yup, that worked fine. : )

    Are you trying to create a new image or updating an existing one?  I noticed the log had two date sets (2012-04-16, which worked correctly) and the one from today (2013-03-05, which is having issues).

    In any case, digging into the log, I see issues downloading EULA files.  Your Scan Cycle appears to work fine (meaning the WSUS database is being talked to and the meta-data exists), but as soon as it tries to download something, it throws a BITS error and 0x80244019 code.  Each pass looks the same (Finds updates, tries to download, fails).

    This looks like a WSUS content problem more than an MDT problem.  According to another TechNet forum for WSUS (http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/299d83c9-d859-4d62-9a04-a0f8830118a5/), you may want to run a wsusutil reset on your WSUS server and ensure that everything downloads properly.  You probably have more patching issues than just imaging currently and haven't realized it yet.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked as answer by Jacob Brixey Friday, March 08, 2013 4:41 PM
    Wednesday, March 06, 2013 12:12 AM
    Answerer
  • DC,

    Thanks for taking a look at the log.

    It turns out it was the server that was having the problem. Removal and re-installation of the WSUS role did not fix the issue. I had to rebuild the OS, update, re-install the WSUS role, update the role, then reapply the KB2734608 hotfix. Once the WSUS server resynchronized and downloaded all the content, patching during task sequence resumed normally.

    Thanks for your help!

    Friday, March 08, 2013 4:44 PM
  • I had this, and only after a couple of cycles of running ztiwindowsupdate.wsf, going to wsus server and looking which updates failed and dis-approving those updates, and re-running, have finally found a couple of updates that do not work well as express update files and some i don't really need (malicious software tool etc.).
    Wednesday, July 31, 2013 11:56 AM
  • Avi, note that instead of dis-approving (since you might want them to be used later or for other machines) them in WSUS, you can skip specific Updates by specifying them for exclusion in the CustomSettings.ini:

    WUMU_ExcludeKB001=KB12345
    WUMU_ExcludeKB002=KB23456


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Thursday, August 01, 2013 1:27 AM
    Answerer
  • Thanks David.
    Thursday, August 01, 2013 7:48 AM
  • There's a bug in the ZTIWindowsUpdate.wsf, still in MDT 2013 - see http://keithga.wordpress.com/2013/09/12/ztiwindowsupdate-wsf-errors/ for full details.

    Basically line 403 says

         "  result(" & UpdateResult.GetUpdateResult(item).ResultCode & ") : " & UpdatesToDownload.Item(item).Title, MSIT_LogType

    and it should be

         "  result(" & UpdateResult.GetProgress.GetUpdateResult(item).ResultCode & ") : " & UpdatesToDownload.Item(item).Title, MSIT_LogType

    This means at least that the script won't crash, the WSUS state is another matter :-)

    Tuesday, March 18, 2014 6:42 PM
  • Hi Paul,

    Thanks for the update and the share.

    Wednesday, March 19, 2014 9:30 AM