Yea, wow.  164 updates. Wow, that's a lot. I never thought that machines
would need that much.

 

Modify the ZTIWindowsUPdate.wsf script to increase the const
MSIT_WU_REBOOT_MAX value to something larger like 10.

 

Is this a deployment or for image capture?

 

MDT ZTIWindowsUpdate.wsf has a hardcoded limit on the number of reboots it
will perform, that's to prevent the script from getting into an infinite
loop.  Seven seemed like a reasonable number when I coded it, but you my
friend are pushing the limit here. Alternatively you could push some the
larger more complex packages to ZTIApplications *before*
ZTIWindowsUPdate.wsf like .NET Framework 3.5, 4.5, etc.

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Benjamin Monrad
Sent: Thursday, December 19, 2013 9:30 AM
To: mdtosd
Subject: [MDT-OSD] ZTIWindowsUpdate.wsf failing after first reboot?

 

Hi all,

I am setting up a new Build and Capture in CM2012 SP1 CU2, trying to use
ZTIWindowsUpdate.wsf because I really liked the way it was working for us on
CM2007.

 

The first time we are running the step, it is finding applicable updates and
it chugs away through installing them, mostly with success, but then it dies
after the first reboot.

The step is running on a fresh install of x64-Win7-ENT wSP1, no other apps
installed at this point.

 

Here is where it completes installations with some individual update
failures but ultimately the script exits with Success, just before
rebooting:

Process completed with exit code 0    InstallSoftware    12/18/2013 8:02:56
PM    2320 (0x0910)
Property InstalledUpdates163 is now = 8886aac9-057f-4577-9e89-036c5ed4e2b0
InstallSoftware    12/18/2013 8:02:56 PM    2320 (0x0910)
Property InstalledUpdates164 is now = c61a0d00-3e51-48ac-b0af-1d3e02b9e5d3
InstallSoftware    12/18/2013 8:02:56 PM    2320 (0x0910)
    5eb03bea-4f70-4136-9529-3ba5015aee9a  result(4 / HR = 80070643 ) :
Microsoft .NET Framework 4.5.1 for Windows 7 x64-based Systems (KB2858725)
InstallSoftware    12/18/2013 8:02:56 PM    2320 (0x0910)
Failure, Please run again!    InstallSoftware    12/18/2013 8:02:56 PM
2320 (0x0910)
Property SMSTSRetryRequested is now = true    InstallSoftware    12/18/2013
8:02:56 PM    2320 (0x0910)
Property SMSTSRebootRequested is now = true    InstallSoftware    12/18/2013
8:02:56 PM    2320 (0x0910)
ztiwindowsupdate processing completed successfully.    InstallSoftware
12/18/2013 8:02:56 PM    2320 (0x0910)
Command line returned 0    InstallSoftware    12/18/2013 8:02:56 PM    2320
(0x0910)
Process completed with exit code 0    TSManager    12/18/2013 8:02:56 PM
1888 (0x0760)
!---------------------------------------------------------------------------
-----------------!    TSManager    12/18/2013 8:02:56 PM    1888 (0x0760)
Successfully completed the action (ZTI Windows Update (1)) with the exit
win32 code 0    TSManager    12/18/2013 8:02:56 PM    1888 (0x0760)

After the reboot, when the step picks up again, it dies with this:
Microsoft Deployment Toolkit version: 6.1.2369.0    InstallSoftware
12/18/2013 8:04:22 PM    2356 (0x0934)
The task sequencer log is located at C:\Windows\CCM\Logs\SMSTSLog\SMSTS.LOG.
For task sequence failures, please consult this log.    InstallSoftware
12/18/2013 8:04:22 PM    2356 (0x0934)
Begin Windows Update. Reboot=[]  Retry=[]  Count = 7    InstallSoftware
12/18/2013 8:04:22 PM    2356 (0x0934)
Property MSIT_WU_Count is now = 8    InstallSoftware    12/18/2013 8:04:22
PM    2356 (0x0934)
FAILURE ( 9902 ): ZTIWindowsUpdate has run and failed too many times. Count
= 8    InstallSoftware    12/18/2013 8:04:22 PM    2356 (0x0934)
Command line returned 9902    InstallSoftware    12/18/2013 8:04:22 PM
2356 (0x0934)
Process completed with exit code 9902    TSManager    12/18/2013 8:04:22 PM
1872 (0x0750)
!---------------------------------------------------------------------------
-----------------!    TSManager    12/18/2013 8:04:22 PM    1872 (0x0750)
Failed to run the action: ZTI Windows Update (1). 
The specified directory partition already exists. (Error: 000026AE; Source:
Windows)    TSManager    12/18/2013 8:04:22 PM    1872 (0x0750)

Any ideas? Thanks!


Reply via email to