none
MDT 2012 upd 1 and Windows / Component updates RRS feed

  • Question

  • I am trying to create a deployment for Win 7 x64 in MDT 2012, and it is going quite well.  My problem is with the Windows Update passes -- for some reason it misses many Office and Component updates until I go to deploy.  Then it takes another hour to grab and install those.  I don't understand why it does not grab them during the TS process.

    I am doing a staged capture in a VM environment, starting with a zero-touch capture that includes Office 2010 and all the updates.  This is my thin image and it takes about 5.5 hours through capture.  Then I take this thin image, add standard apps that cannot be silently installed, customize desktop options that cannot be easily automated (another huge pain, but another topic), and, I was hoping, install all the updates for Office 2010 and other non-OS components.

    In the first TS, I run the updates pre-installation, use the TS step to install Office, and run them again post-installation.  It does pick up a few, but then the logs say the system is fully updated and goes on to the next step.

    In the second TS, I use the post-installation update step.  One of the apps I use installs SQL components, and the TS picks up on this and installs several updates it finds.  Then it decides the machine is up to date and moves on, skipping about 40 updates as of this writing.

    As a test, I inserted a reboot step between app installation and the post-install Update step, but it still ignored the Office updates.  Research on the issue turned up the idea that at some point ZTIWindowsUpdate turns on the extra updates, and also several suggestions that this is how it is supposed to work (and why the standard TS is designed this way).

    I rolled my VM back to the suspended point and I'm running WU manually at the console.  I had to enable "Microsoft Update" manually, and now it is happily pulling down the updates.  I just hope there's enough smarts left in the VM to run to  the task to completion.

    I'm hoping that some whiz with the process can enlighten us on how to force ZTIWindowsUpdate to search for critical updates for all Microsoft components, not just the OS ones.

    UPDATE:

    Digging into the code and logs, it seems that a certain condition is not occurring to trigger the Microsoft Update service; bFoundMU must be true for this to happen.  A ServiceID hard coded is not being matched--the reason escapes me.  Near as I can tell, after a magic reboot it finally finds a match for this ServiceID.  Hopefully this snippet does not get munged...

        On Error Resume Next
                Item = oFSO.GetFileVersion ( ees("%SystemRoot%\System32\WUAUENG.DLL" ) )
                oLogging.CreateEntry "Ready to Opt-In to Microsoft Update: WUA Version: " & Item , LogTypeInfo
                Set ServiceManager = nothing
                Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
            On Error Goto 0

            If ServiceManager is nothing then
                oLogging.CreateEntry "Failed to Create Object: Microsoft.Update.ServiceManager" , LogTypeWarning
            Else
                bFoundMU = False
                For each Item in ServiceManager.Services
                    WScript.Echo "Registered Update Service: " & Item.ServiceID & "   " & Item.Name
                    If Item.ServiceID = "7971f918-a847-4430-9279-4a52d1efe18d" then
                        bFoundMU = True
                    End if
                Next

                oLogging.CreateEntry "Microsoft Update Service:  Enabled = " & bFoundMU, LogTypeInfo
                If not bFoundMU then
                    On Error Resume Next
                        Err.clear
                        ServiceManager.ClientApplicationID = "My App"
                        If Err.Number <> 0 then
                            oLogging.CreateEntry "There was an error getting Windows Update to opt into Microsoft Update. Please verify you are running the latest version of Windows Update Agent." , LogTypeWarning
                        End if

    The logs look virtually identical between the two runs.  This is getting way deeper than I understand the update process or about service IDs.

    UPDATE 2:

    Digging further, it seems that the the condition of bFoundMU has no bearing on whether or not MU is used, but possibly the existence of muauth.cab.  From the deploy log where it actually started, bFoundMU is still false, but at that point the Office updates started to come in:

    <![LOG[Property MSIT_WU_Count is now = 1]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Archive NoAUtoUpdate State: Was [<empty>].]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property NoAutoUpdate_Previous is now = <empty>]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.5.7601.17514]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ Status: 3]LOG]!><time="11:05:35.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    __bunch of skipped updates__
    <![LOG[  SKIP  - 258b6ca1-a8ec-4dfa-b619-fb8cecac6e2e - Turkish Language Pack - Windows 7 Service Pack 1 for x64-based Systems (KB2483139) - 56 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 48f7e3b7-2c8f-4900-ae32-f3d8f29c988d - Microsoft SQL Server 2005 Express Edition Service Pack 4 (KB2463332) - 55 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - d68e0cb2-9501-405e-af9c-156f352d6735 - Security Update for Microsoft Visual C++ 2010 Redistributable Package (KB2467173) - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 719584bc-2208-4bc9-a650-d3d6347eb32e - Security Update for Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (KB2565063) - 9 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - eb7a169f-6bca-4e00-a52a-623c063c162d - Update for Office File Validation 2010 (KB2553065), 32-bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - f51a0e5b-24a9-4be1-8b36-0f22f99949e7 - Security Update for Microsoft SharePoint Workspace 2010 (KB2566445), 32-Bit Edition - 17 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 35eb79df-cb34-491c-ab0a-34b63f32b45c - Update for Microsoft Office 2010 (KB2553092), 32-Bit Edition - 9 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - a6309b2e-7ee4-4b02-8ce9-cf39796a2411 - Update for Microsoft OneNote 2010 (KB2553290) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - f5202a56-ff34-401d-a040-f97c7f70891c - Update for Microsoft Office 2010 (KB2553310) 32-Bit Edition - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 33a4aa0a-cb01-4326-85f4-4a7d33d8782b - Update for Microsoft Outlook Social Connector 2010 (KB2553406) 32-Bit Edition - 1 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - aae5e2c7-3498-4f43-af66-aec06a59713f - Microsoft Silverlight (KB2636927) - 12 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - c8077d6d-00c2-421b-89f6-30828574519a - Update for Microsoft Office 2010 (KB2767886) 32-Bit Edition - 271 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 9c5e43a3-3ae9-434d-b105-a9d7902d5f9f - Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition - 395 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - b8fcacb4-add0-4cc9-8551-675b59965798 - Update for Microsoft Office 2010 (KB2825640) 32-Bit Edition - 18 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 5923c276-0628-4ba4-be3d-e56aa029a14b - Security Update for Microsoft Office 2010 (KB2687423) 32-Bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 79b27019-3090-4309-bfdc-c8be9b21ab96 - Update for Microsoft Access 2010 (KB2553446) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">

    After the subsequent reboot, bFoundMU was set to true.

    Thursday, April 24, 2014 8:12 PM

Answers

  • I don't understand your question. You say that you are not getting Office Updates, yet the attached logs show that you *are* getting Office Updates.

    What is your current status. Do you have a ztiwindowsupdate.log file that cleanly reproduces the problem (if any)?


    Keith Garner - keithga.wordpress.com

    (See my latest update, posted as an answer to my own question)

    My problem was that the Office updates were not applied during the initial build of the image, and I believe this is due to the presence of muauth.cab in my first distribution share.  I don't know how it got there, or why it wasn't present in the second one, but it seems that if it is not present then the script will download and activate MU and grab the other components.  I will test this theory tonight and report back.

    I have confirmed that the task sequence works as expected when muauth.cab was removed from deploymentshare1\tools.  Now my task sequence downloads windows updates in the preinstall task, installs Office, and installs Office components in the postinstall task.

    At some point in wrestling with the proxy (and/or trying to avoid external downloads) I must have installed something that placed muauth.cab and wuredist.cab in the tools folder of my deployment share. 

    If someone would care to elaborate about the logic behind the ZTIWindowsupdate.wsf code and/or its interaction with that cab file, I would gladly mark that as an answer.  Otherwise I'm happy that this is working as expected now. 

     

    • Marked as answer by BigPurpleDick Tuesday, April 29, 2014 7:15 PM
    Tuesday, April 29, 2014 7:15 PM

All replies

  • I don't understand your question. You say that you are not getting Office Updates, yet the attached logs show that you *are* getting Office Updates.

    What is your current status. Do you have a ztiwindowsupdate.log file that cleanly reproduces the problem (if any)?


    Keith Garner - keithga.wordpress.com

    Monday, April 28, 2014 5:33 PM
    Moderator
  • Another detail I neglected to mention is that I am using two separate deployment shares, one for building the deploy image and the other for actual deployments.  I think I found another clue in the log, muauth.cab:

    <![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">

    The next stanza in ZTIWindowsUpdate.wsf is this:

    If oEnvironment.Item("WsusServer") = "" then

                              iResult = oUtility.FindFile("muauth.cab", strCabPath)

                            If iResult <> Success then
                                '// "" will force a internet search for cab file
                                strCabPath = ""
                            End if

                            oLogging.CreateEntry " about to begin add service ["+ strCabPath +"]", LogTypeInfo
                        
                            Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",6,strCabPath)
                            oLogging.CreateEntry " Status: " & NewUpdateService.RegistrationState, LogTypeInfo
                        End if

    Indeed, the muauth.cab file was present in my first one, but not the deployment one.  As the log says, since there is no muauth.cab file, the code will then go download it. 

    I don't know how, when, or why this happened (why is it in my first DS and not my second?), but a simple test this evening will confirm my suspicion that if the file is not present it will update as expected.

    Monday, April 28, 2014 8:20 PM
  • I don't understand your question. You say that you are not getting Office Updates, yet the attached logs show that you *are* getting Office Updates.

    What is your current status. Do you have a ztiwindowsupdate.log file that cleanly reproduces the problem (if any)?


    Keith Garner - keithga.wordpress.com

    (See my latest update, posted as an answer to my own question)

    My problem was that the Office updates were not applied during the initial build of the image, and I believe this is due to the presence of muauth.cab in my first distribution share.  I don't know how it got there, or why it wasn't present in the second one, but it seems that if it is not present then the script will download and activate MU and grab the other components.  I will test this theory tonight and report back.

    Monday, April 28, 2014 8:25 PM
  • I don't understand your question. You say that you are not getting Office Updates, yet the attached logs show that you *are* getting Office Updates.

    What is your current status. Do you have a ztiwindowsupdate.log file that cleanly reproduces the problem (if any)?


    Keith Garner - keithga.wordpress.com

    (See my latest update, posted as an answer to my own question)

    My problem was that the Office updates were not applied during the initial build of the image, and I believe this is due to the presence of muauth.cab in my first distribution share.  I don't know how it got there, or why it wasn't present in the second one, but it seems that if it is not present then the script will download and activate MU and grab the other components.  I will test this theory tonight and report back.

    I have confirmed that the task sequence works as expected when muauth.cab was removed from deploymentshare1\tools.  Now my task sequence downloads windows updates in the preinstall task, installs Office, and installs Office components in the postinstall task.

    At some point in wrestling with the proxy (and/or trying to avoid external downloads) I must have installed something that placed muauth.cab and wuredist.cab in the tools folder of my deployment share. 

    If someone would care to elaborate about the logic behind the ZTIWindowsupdate.wsf code and/or its interaction with that cab file, I would gladly mark that as an answer.  Otherwise I'm happy that this is working as expected now. 

     

    • Marked as answer by BigPurpleDick Tuesday, April 29, 2014 7:15 PM
    Tuesday, April 29, 2014 7:15 PM