Configuration Manager Software Updates Management Forum

Adjust timeout for errors in provisioning updates

Wed, 25 Nov 2009 15:58:43 Z

I just started a large SCCM project a few weeks ago and have been trying to get a system down for software updates. Since I've made many mistakes in how I want to build my deployment packages, I've had to create several update lists, delete them and create them again. In the process of doing this, I've found that some updates error out for whatever reason; invalid certificate signature or network path not found. I haven't started troubleshooting these yet but one thing I am finding is that if it hits an update that is going to throw an error, it stays on this update for 10-15 minutes or more.

In the distmgr.log file, I'm seeing this: "Failed to process package UNH00013 after 75 retries, will retry 25 more times". What if I don't want it to retry 25 more times? I would think that 10 tries would be sufficient for me and if it still doesn't work in that timeframe, it's not going to.

Microsoft Updates suddenly stops at 50% of downloading.

Tue, 20 Oct 2009 13:54:58 Z

Hi.

We have a fully working environment with SCCM 2007. We update 150+ servers and approx 650 clients through CM and it usually works like a charm. This mounths updates worked fine too, no problem distributing them as usual with CM. BUT, i have now gotten 3 cases where all the updates except one has been downloaded to the client. The last update will not pass 50% of downloading no matter how long we wait. So, what i see in the Software Updates Installation progresswindow is now several updates with status "Preparing for installation" and one with status "Downloading 50%".

I have of course done some checking to solve the problem like checking logs, connectivity, errorreports etc .. ..
Usually when there is some kind of errors i find the answers in the logs but this time they are clean as far as i can see.
The strange thing is that all updates except one were downloaded smoothly as always and that´s on approx 650 clients.
The update that won´t be downloaded is Kb968389. Any known issues with that one ? Since that update won´t reach 100%
the other updates won´t be installed.

Any suggestions ? Have never experienced anything like this this before.
I´m a beginner at this (SCCM) but this far i really like it :)

Thanks in advance
Best regards
Stefan

(SCCM 2007, WSUS 3.0, Win XP Professional SP3)

Software Updates not Working on Outlook Web Access Server

Wed, 25 Nov 2009 17:09:19 Z

I can not get the Software Updates to work on the OWA Server.

WindowsUpdate Log
2009-11-25 09:30:09:310 984 57c PT WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2009-11-25 09:30:09:310 984 57c PT WARNING: PTError: 0x80244019
2009-11-25 09:30:09:310 984 57c PT WARNING: GetConfig_WithRecovery failed: 0x80244019
2009-11-25 09:30:09:310 984 57c PT WARNING: RefreshConfig failed: 0x80244019
2009-11-25 09:30:09:310 984 57c PT WARNING: RefreshPTState failed: 0x80244019
2009-11-25 09:30:09:310 984 57c PT WARNING: PTError: 0x80244019
2009-11-25 09:30:09:310 984 57c Report WARNING: Reporter failed to upload events with hr = 80244019.

It appears to be a proxy issue.

The Proxycfg file on the OWA server includes all Exchange Servers.

Thanks

Windows update stuck at 50% download with error WARNING: Failed to evaluate Installed rule....

Mon, 23 Nov 2009 17:41:17 Z

I had this issue previously but dropped teh thread due to reimaging the PC, but it is back to rear its ugly head... We currently have about a half dozen SCCM clients that are stuck when attempting to run windows updates pushed by SCCM/WSUS... From what I see all are stuck on update KB968389 and all are stuck downloading the update at 50%. All WindowsUdate.logs look the exact same

2009-11-23 09:37:08:968 1192 76c Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0600) ===========
2009-11-23 09:37:08:968 1192 76c Misc   = Process: C:\WINDOWS\System32\svchost.exe
2009-11-23 09:37:08:968 1192 76c Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-23 09:37:08:968 1192 76c Service *************
2009-11-23 09:37:08:968 1192 76c Service ** START ** Service: Service startup
2009-11-23 09:37:08:968 1192 76c Service *********
2009-11-23 09:37:10:015 1192 76c Agent   * WU client version 7.4.7600.226
2009-11-23 09:37:10:015 1192 76c Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-23 09:37:10:046 1192 76c Agent   * Access type: No proxy
2009-11-23 09:37:10:062 1192 76c Agent   * Network state: Connected
2009-11-23 09:38:03:924 1192 76c Agent *********** Agent: Initializing Windows Update Agent ***********
2009-11-23 09:38:03:924 1192 76c Agent *********** Agent: Initializing global settings cache ***********
2009-11-23 09:38:03:924 1192 76c Agent   * WSUS server: http://dln3003p.playlsi.com:8530
2009-11-23 09:38:03:924 1192 76c Agent   * WSUS status server: http://dln3003p.playlsi.com:8530
2009-11-23 09:38:03:924 1192 76c Agent   * Target group: Client Production
2009-11-23 09:38:03:924 1192 76c Agent   * Windows Update access disabled: No
2009-11-23 09:38:04:015 1192 76c DnldMgr Download manager restoring 0 downloads
2009-11-23 09:38:04:152 1192 76c DnldMgr Retrieved 8 persisted download jobs
2009-11-23 09:38:04:152 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 0] ***********
2009-11-23 09:38:04:152 1192 76c DnldMgr   * BITS JobId = {8D4AA409-8C32-4F80-B14D-EBCF21A14F91}
2009-11-23 09:38:04:152 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:04:743 1192 76c DnldMgr   * UpdateId = {FC3988E7-824B-47A5-A971-49F2B336E4C0}.103
2009-11-23 09:38:25:517 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:25:517 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 1] ***********
2009-11-23 09:38:25:517 1192 76c DnldMgr   * BITS JobId = {13D90522-4DB0-4EBF-9019-9A0D8C6F38F1}
2009-11-23 09:38:25:517 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:25:639 1192 76c DnldMgr   * UpdateId = {76FAE14C-542D-4530-82D7-C4D8CA0F5FE9}.100
2009-11-23 09:38:26:442 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:26:442 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 2] ***********
2009-11-23 09:38:26:442 1192 76c DnldMgr   * BITS JobId = {0C5F8950-82DE-4F32-8811-9C7075908C2A}
2009-11-23 09:38:26:442 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:26:700 1192 76c DnldMgr   * UpdateId = {FFA61BC5-FDE6-466A-8622-8FDBC971F73D}.103
2009-11-23 09:38:32:675 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:32:675 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 3] ***********
2009-11-23 09:38:32:675 1192 76c DnldMgr   * BITS JobId = {216ABF6D-2975-40B7-90A3-828EBBD20918}
2009-11-23 09:38:32:675 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:32:917 1192 76c DnldMgr   * UpdateId = {04EC635D-6C1B-408E-8ED7-BAC562A50929}.102
2009-11-23 09:38:33:948 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:33:948 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 4] ***********
2009-11-23 09:38:33:948 1192 76c DnldMgr   * BITS JobId = {3C599D7C-3DCE-41FA-AEBD-8A321B0E9C8A}
2009-11-23 09:38:33:948 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:34:024 1192 76c DnldMgr   * UpdateId = {3A769F99-AF69-4268-B78D-D6DFB38AE573}.100
2009-11-23 09:38:34:358 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:34:358 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 5] ***********
2009-11-23 09:38:34:358 1192 76c DnldMgr   * BITS JobId = {6DB28BD9-F53B-4EE1-86C7-6F361D73ECCE}
2009-11-23 09:38:34:358 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:34:434 1192 76c DnldMgr   * UpdateId = {96B876C1-0B99-4BC0-BE53-61D92D4D6C31}.100
2009-11-23 09:38:35:874 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:35:874 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 6] ***********
2009-11-23 09:38:35:874 1192 76c DnldMgr   * BITS JobId = {39BF85F6-4A86-420C-BEA7-D8263F493BC0}
2009-11-23 09:38:35:874 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:36:193 1192 76c DnldMgr   * UpdateId = {F9B10375-898C-4D12-8722-B2F7F6E81521}.101
2009-11-23 09:38:37:482 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:37:497 1192 76c DnldMgr *********** DnldMgr: Restoring download [no. 7] ***********
2009-11-23 09:38:37:497 1192 76c DnldMgr   * BITS JobId = {7B9F0BF8-3F31-48D3-BE5D-F51508204C8C}
2009-11-23 09:38:37:497 1192 76c DnldMgr   * ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}
2009-11-23 09:38:37:709 1192 76c DnldMgr   * UpdateId = {6AA00022-D784-4393-BDF6-F4E8B73D820B}.101
2009-11-23 09:38:39:210 1192 76c DnldMgr   * Restored download job.
2009-11-23 09:38:39:438 1192 76c AU ########### AU: Initializing Automatic Updates ###########
2009-11-23 09:38:39:438 1192 76c AU AU setting next sqm report timeout to 2009-11-23 15:38:39
2009-11-23 09:38:39:438 1192 76c AU   # WSUS server: http://dln3003p.playlsi.com:8530
2009-11-23 09:38:39:438 1192 76c AU   # Detection frequency: 4
2009-11-23 09:38:39:438 1192 76c AU   # Target group: Client Production
2009-11-23 09:38:39:438 1192 76c AU   # Approval type: Scheduled (Policy)
2009-11-23 09:38:39:438 1192 76c AU   # Scheduled install day/time: Thursday at 15:00
2009-11-23 09:38:39:438 1192 76c AU   # Auto-install minor updates: Yes (User preference)
2009-11-23 09:38:39:726 1192 76c AU Setting AU scheduled install time to 2009-11-26 21:00:00
2009-11-23 09:38:39:726 1192 76c AU Initializing featured updates
2009-11-23 09:38:39:877 1192 76c AU Found 0 cached featured updates
2009-11-23 09:38:39:877 1192 76c AU AU finished delayed initialization
2009-11-23 09:38:50:143 1192 76c Report *********** Report: Initializing static reporting data ***********
2009-11-23 09:38:50:143 1192 76c Report   * OS Version = 5.1.2600.3.0.65792
2009-11-23 09:38:50:158 1192 76c Report   * Computer Brand = Dell Inc.
2009-11-23 09:38:50:158 1192 76c Report   * Computer Model = Precision WorkStation 690
2009-11-23 09:38:50:280 1192 76c Report   * Bios Revision = A05
2009-11-23 09:38:50:280 1192 76c Report   * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A05
2009-11-23 09:38:50:280 1192 76c Report   * Bios Release Date = 2007-05-24T00:00:00
2009-11-23 09:38:50:280 1192 76c Report   * Locale ID = 1033
2009-11-23 09:39:12:889 1192 f60 PT WARNING: Cached cookie has expired or new PID is available
2009-11-23 09:39:12:889 1192 f60 PT Initializing simple targeting cookie, clientId = 3d137864-2ed1-4fe5-8944-8dd32124d949, target group = Client Production, DNS name = d0000000fs5wrf1.playlsi.com
2009-11-23 09:39:12:889 1192 f60 PT   Server URL = http://dln3003p.playlsi.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2009-11-23 09:39:13:147 1192 f60 Report Uploading 1 events using cached cookie, reporting URL = http://dln3003p.playlsi.com:8530/ReportingWebService/ReportingWebService.asmx
2009-11-23 09:39:13:147 1192 f60 Report Reporter successfully uploaded 1 events.
2009-11-23 09:40:30:346 1968 2c4 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0600) ===========
2009-11-23 09:40:30:361 1968 2c4 Misc   = Process: C:\WINDOWS\system32\CCM\CcmExec.exe
2009-11-23 09:40:30:361 1968 2c4 Misc   = Module: C:\WINDOWS\system32\wuapi.dll
2009-11-23 09:40:30:346 1968 2c4 COMAPI -------------
2009-11-23 09:40:30:361 1968 2c4 COMAPI -- START -- COMAPI: Search [ClientId = CcmExec]
2009-11-23 09:40:30:361 1968 2c4 COMAPI ---------
2009-11-23 09:40:30:740 1192 f60 Agent *************
2009-11-23 09:40:30:755 1968 2c4 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec]
2009-11-23 09:40:30:755 1192 f60 Agent ** START ** Agent: Finding updates [CallerId = CcmExec]
2009-11-23 09:40:30:755 1192 f60 Agent *********
2009-11-23 09:40:30:755 1192 f60 Agent   * Include potentially superseded updates
2009-11-23 09:40:30:755 1192 f60 Agent   * Online = No; Ignore download priority = Yes
2009-11-23 09:40:30:755 1192 f60 Agent   * Criteria = "(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"
2009-11-23 09:40:30:755 1192 f60 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2009-11-23 09:40:30:755 1192 f60 Agent   * Search Scope = {Machine}
2009-11-23 09:41:25:026 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {6A29F1FE-6717-464C-8BD0-DC487F177B37}.1, hr = 8004100E
2009-11-23 09:41:25:042 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {6A29F1FE-6717-464C-8BD0-DC487F177B37}.1, hr = 8004100E
2009-11-23 09:41:25:208 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {242BA0FE-6937-4794-AD51-AC04D083C328}.2, hr = 8004100E
2009-11-23 09:41:25:239 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {242BA0FE-6937-4794-AD51-AC04D083C328}.2, hr = 8004100E
2009-11-23 09:41:25:254 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {6234B3FD-B688-4C5C-B332-D2E8E9123542}.2, hr = 8004100E
2009-11-23 09:41:25:284 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {6234B3FD-B688-4C5C-B332-D2E8E9123542}.2, hr = 8004100E
2009-11-23 09:41:45:467 4328 1454 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0600) ===========
2009-11-23 09:41:45:467 4328 1454 Misc   = Process: C:\WINDOWS\system32\rundll32.exe
2009-11-23 09:41:45:467 4328 1454 Misc   = Module: C:\WINDOWS\system32\wuapi.dll
2009-11-23 09:41:45:467 4328 1454 ARP Connected to update session.
2009-11-23 09:41:45:467 4328 1454 ARP User is allowed to install published content.
2009-11-23 09:41:45:619 4328 1454 ARP Managed service found.
2009-11-23 09:43:40:427 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {84F28DFA-A700-44C8-AC4C-48877B7E0EAB}.1, hr = 8004100E
2009-11-23 09:43:40:427 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {84F28DFA-A700-44C8-AC4C-48877B7E0EAB}.1, hr = 8004100E
2009-11-23 09:43:40:458 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {490644F9-2EA7-4F44-88A7-F096BFC29284}.2, hr = 8004100E
2009-11-23 09:43:40:504 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {490644F9-2EA7-4F44-88A7-F096BFC29284}.2, hr = 8004100E
2009-11-23 09:43:40:535 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {455FF0F8-84A8-4C8C-B3E9-69AD9967CEF4}.1, hr = 8004100E
2009-11-23 09:43:40:535 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {455FF0F8-84A8-4C8C-B3E9-69AD9967CEF4}.1, hr = 8004100E
2009-11-23 09:43:40:612 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {C6C5BAF6-BE41-4FEF-9CA9-D34E9F0A7407}.1, hr = 8004100E
2009-11-23 09:43:40:612 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {C6C5BAF6-BE41-4FEF-9CA9-D34E9F0A7407}.1, hr = 8004100E
2009-11-23 09:43:40:612 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {BEB99EF6-ECD5-44D7-B9B9-B35C4E999090}.2, hr = 8004100E
2009-11-23 09:43:40:643 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {BEB99EF6-ECD5-44D7-B9B9-B35C4E999090}.2, hr = 8004100E
2009-11-23 09:43:40:643 1192 f60 Agent WARNING: Failed to evaluate Installed rule, updateId = {EB983DF6-DEFB-4BDF-8A9C-E2A3A5E27104}.2, hr = 8004100E
2009-11-23 09:43:40:674 1192 f60 Agent WARNING: Failed to evaluate Installable rule, updateId = {EB983DF6-DEFB-4BDF-8A9C-E2A3A5E27104}.2, hr = 8004100E

The length of the log files varies depending on how many updates are stuck behind the problem child. All logs have the same 8004100e code after the warning.

To resolve this issue I have tried several things;
1. manually ran the update that was stuck at 50%, rebooted teh system, and forced the client to run its Updates check through the SCCM applet in the control panel

No love

2. forced an uninstall of SCCM client, reinstalled SCCM client

No Love

3. deleted c:\windows\$hf_mig$ (and all other $nt...... folders), forced client to rerun updates check

No Love

4. updated Windows update Agent to 7.4 (latest version)

No Love

5. I stopped Bits, renamed the bits cache folder, restarted bits and refreshed the updates via sccm in control panel

No Love

6. ran the following VBscript to refresh the server compliance state
dim newCCMUpdatesStore
     set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")

newCCMUpdatesStore.RefreshServerComplianceState
wscript.echo "Ran RefreshServerComplianceState."

No Love

This update is running on about 80% of the clients that need it, so this issue is not killing off all systems updates so I am a little baffeled by this one.

Anyone with any bright ideas?

Does Software Updates send SP3 to only the comps that need it?

Wed, 25 Nov 2009 15:29:15 Z

I want to get our SP3 software update and send that to everything that doesn't have it. Should I make a collection that has that or does Software Updates have a way to install only on the computers that need it and ignore all the others?

What do some of my clients stay in the "Successfully installed updates" state?

Wed, 28 Oct 2009 15:45:03 Z

Reading my patching report, there are are a few clients that return a state of "Successfully Installed Update(s)". I would think that if a client successfully installed updates, it would soon after change to a "Compliant" state if the updates didn't require a reboot.

Anyone run into this?

Software Updates Scan Interval Question

Mon, 23 Nov 2009 15:45:48 Z

This might be an easier question to answer. I am trying to install updates to production servers in a collection. I can install updates and initiate reboots only in a defined maintenance window. My maintenance window in this case is 12 hour long, starting 9am to 9pm, which is usually enough to accommodate the required run time for the updates. I see that the clients install a batch of updates starting 9am and followed by a reboot. Everything is fine so far. Several hours later, the clients scan for updates again and find more required updates in the same deployment, but this time there is either no open maintenance window or the window is too small for the updates. The clients report a failed status in this case.

The scan schedule on Software Updates Client Agent Properties is set to every 1 day, which is the most frequent schedule possible.

What changes should I make so that the clients install all required updates in a deployment in the defined maintenance window?

Thanks.

Mayur

Error code 0x80072EFD in windowsupdate.log

Tue, 24 Nov 2009 09:55:13 Z

Hi,

Facing the same problem which was discussed in http://social.technet.microsoft.com/forums/en-US/configmgrsum/thread/1339b0e5-62c3-49a2-85b6-4d27e6d5b6ab/?prof=required.

I have deployed latest windows updates on around windows 500 XP/Vista systems & getting same error on around 80 systems. i have checked windows update.log & found some error which are related to proxy connection. now strange thing is on interne explorer, differet proxy IP/Port is set but in windows update.log it's tried to connect on different Proxy. Now my question is :

Why & from where it's using different Proxy in windows update.log.
Secondly when we are deploying updates from SCCM, will it check anything from Internet?
Proxycfg is showing direct access however proxy settings are set in Internet explorer.

Kindly help to correct this problem.

Dhiraj

Avoid download updates from Internet

Tue, 24 Nov 2009 12:45:10 Z

Can SCCM client\Windows Update Agent don't allow the user to check for updates or download updates from Internet by using Windows Update?

Of bulletins, articles and deployments

Wed, 25 Nov 2009 10:01:33 Z

Hi all,

I've got a question about deployments, deployment ID's and related articles;
When dragging and dropping updates from an Update List to an existing deployment, you'll get a short wizard containing a summary page. In that summary page you'll sometimes see that "targeted updates" contains more than just the updates you selected. In example; if you select a Windows XP update that has bulletin id MS09-99 and article id 12345, it's possible the same update is valid for server platforms. By dragging and dropping the XP update to a deployment, you might get (not always though) the server updates as well in the same deployment. Now I know SCCM only provides applicable updates to the machines, so XP machines won't bother with server updates, but isn't it awkward to see a certain update in multiple deployments? I mean, an update cannot be placed in more than one deployment, because SCCM will give an error.

This makes me wonder if my architecture is correct; I have multiple deployments, some being solely for workstations, some solely for servers. By having the above issue, it makes you wonder if you're doing it right.

Any advice is welcome!
Regards

SCUP 4.5 - Automatic Check for Updates - File Not Found Error

Thu, 16 Jul 2009 18:16:43 Z

Greetings,

I recently went from 4.0 to 4.5 and that seems to really have "broken" SCUP. When I launch SCUP with Automatic Check for Updates, it now pops up a Configure Proxy window. I've completed a full uninstall of SCUP and Install of SCUP 4.5 and still receive the "error". UpdatesPublisher.log reads...

========================================$$<Updates Publisher><Thu Jul 16 11:56:11.817 2009. ><thread=3>
Updates Publisher Snap-in Initialized.$$<Updates Publisher><Thu Jul 16 11:59:56.36 2009. ><thread=3>
Download file: ftp://ftp.dell.com/catalog/DellSDPCatalog.xml failed with message "The remote server returned an error: (550) File unavailable (e.g., file not found, no access)."$$<Updates Publisher><Thu Jul 16 12:0:23.958 2009. ><thread=6>
DownloadSignature: ftp://ftp.dell.com/catalog/DellSDPCatalog.xml was failed to download.$$<Updates Publisher><Thu Jul 16 12:0:23.958 2009. ><thread=6>

I am able to successfully perform a bulk import...

import : Starting Import Wizard at Thursday, July 16, 2009 12:10:22 PM$$<Updates Publisher><Thu Jul 16 12:10:22.755 2009. ><thread=3>
starting import from file: ftp://ftp.dell.com/catalog/DellSDPCatalog.cab$$<Updates Publisher><Thu Jul 16 12:11:2.989 2009. ><thread=10>
In import configuration the digitalsignature check for the file ftp://ftp.dell.com/catalog/DellSDPCatalog.cab is set to False$$<Updates Publisher><Thu Jul 16 12:11:4.224 2009. ><thread=10>
import : Importing from: DellSDPCatalog.xml$$<Updates Publisher><Thu Jul 16 12:11:5.442 2009. ><thread=10>

The only difference I see is that the "Auto" wants to download a XML file which does not exist whereas the Import downloads the CAB. How or where would one change that behavior or is this a "feature" in SCUP 4.5?

Thanks!

**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY

Wed, 25 Nov 2009 00:59:03 Z

I am getting this error in my secondary server "**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY" mpfdm.log file.

Please help.

Update 1 (8266a188-8f06-42ed-abd7-5e467e9aad81) finished installing (0x80070643), Reboot Required? No

Tue, 24 Nov 2009 11:00:15 Z

I am new to software update via SCCM. I created a package to include 12 updates. Not all but one update has failed on many computers. Following is generated in WUAhandler.log when I try to install this patch from client's machine.

Going to search using WSUS update source. WUAHandler 24/11/2009 5:24:56 PM 2412 (0x096C)
Synchronous searching started using filter: 'UpdateID = '8266a188-8f06-42ed-abd7-5e467e9aad81' AND DeploymentAction = *'... WUAHandler 24/11/2009 5:24:56 PM 2412 (0x096C)
Successfully completed synchronous searching of updates. WUAHandler 24/11/2009 6:08:20 PM 2412 (0x096C)
1. Update: 8266a188-8f06-42ed-abd7-5e467e9aad81, 102   BundledUpdates: 1 WUAHandler 24/11/2009 6:08:20 PM 2412 (0x096C)
       Update: d5ea2f40-4dc6-4a9f-917e-17b169221b0d, 102   BundledUpdates: 0 WUAHandler 24/11/2009 6:08:20 PM 2412 (0x096C)
1. Update (Missing): Update to .NET Framework 3.5 Service Pack 1 for the .NET Framework Assistant 1.0 x86 (KB963707) (8266a188-8f06-42ed-abd7-5e467e9aad81, 102) WUAHandler 24/11/2009 6:08:20 PM 2412 (0x096C)
Async installation of updates started. WUAHandler 24/11/2009 6:08:37 PM 2412 (0x096C)
Async searching of updates using WUAgent started. WUAHandler 24/11/2009 6:08:38 PM 2232 (0x08B8)
Successfully canceled running installation. WUAHandler 24/11/2009 6:28:45 PM 3032 (0x0BD8)
Async install completed. WUAHandler 24/11/2009 6:28:45 PM 2796 (0x0AEC)
Async searching completed. WUAHandler 24/11/2009 6:50:24 PM 3780 (0x0EC4)
Successfully completed scan. WUAHandler 24/11/2009 6:50:50 PM 204 (0x00CC)
Its a WSUS Update Source type ({CBB62789-1A14-4E90-8E96-39F2A8891FBC}), adding it. WUAHandler 24/11/2009 6:50:58 PM 204 (0x00CC)
Existing WUA Managed server was already set (http.com.au:8530), skipping Group Policy registration. WUAHandler 24/11/2009 6:51:03 PM 204 (0x00CC)
Added Update Source ({CBB62789-1A14-4E90-8E96-39F2A8891FBC}) of content type: 2 WUAHandler 24/11/2009 6:51:04 PM 204 (0x00CC)
Async searching of updates using WUAgent started. WUAHandler 24/11/2009 6:51:05 PM 204 (0x00CC)
Async searching completed. WUAHandler 24/11/2009 7:11:23 PM 952 (0x03B8)
Successfully completed scan. WUAHandler 24/11/2009 7:11:31 PM 3172 (0x0C64)
Going to search using WSUS update source. WUAHandler 24/11/2009 7:12:22 PM 2672 (0x0A70)
Synchronous searching started using filter: 'UpdateID = '8266a188-8f06-42ed-abd7-5e467e9aad81' AND DeploymentAction = *'... WUAHandler 24/11/2009 7:12:22 PM 2672 (0x0A70)
Successfully completed synchronous searching of updates. WUAHandler 24/11/2009 7:19:29 PM 2672 (0x0A70)
1. Update: 8266a188-8f06-42ed-abd7-5e467e9aad81, 102   BundledUpdates: 1 WUAHandler 24/11/2009 7:19:29 PM 2672 (0x0A70)
       Update: d5ea2f40-4dc6-4a9f-917e-17b169221b0d, 102   BundledUpdates: 0 WUAHandler 24/11/2009 7:19:29 PM 2672 (0x0A70)
1. Update (Missing): Update to .NET Framework 3.5 Service Pack 1 for the .NET Framework Assistant 1.0 x86 (KB963707) (8266a188-8f06-42ed-abd7-5e467e9aad81, 102) WUAHandler 24/11/2009 7:19:29 PM 2672 (0x0A70)
Async installation of updates started. WUAHandler 24/11/2009 7:19:32 PM 2672 (0x0A70)
Update 1 (8266a188-8f06-42ed-abd7-5e467e9aad81) finished installing (0x80070643), Reboot Required? No WUAHandler 24/11/2009 7:23:48 PM 3996 (0x0F9C)
Async install completed. WUAHandler 24/11/2009 7:23:48 PM 3420 (0x0D5C)
Installation job encountered some failures. Error = 0x80240022. WUAHandler 24/11/2009 7:23:49 PM 1632 (0x0660)
Installation of updates completed. WUAHandler 24/11/2009 7:23:49 PM 1632 (0x0660)

Please let me know if you need more information.

Thanks
kp

VPN and WSUS Server Challenges: 0x80040692

Wed, 18 Nov 2009 21:28:20 Z

Infrastructure: SCCM SP1 R2
SUP Points: Loaded on Primaries and several proxy secondaries

I believe I am having a problem with "roaming" functionality, VPN, and the WSUS Server Location. I'll try to explain the best I can:

A Client is typically located at a remote office with a proxy secondary site with a SUP point installed on it. Due to the "remoteness" of this site and the slow link, we have installed a remote SUP point on that secondary site. The client goes home, and VPNs in. The VPN IP Subnet is closest to our data center and is shared by VPN users, so the user does not recieve the same MP as it has previously had (no proxy this time). All client functionality works, except for the Software Update. Policies, Software Distribution and Inventoreis are all fine. Software Updates fail to deploy updates and fail compliance scans. The errors are listed below:

-Its a WSUS Update Source type ({XXXXX}), adding it.
-Enabling WUA Managed server policy to use server: http://PrimarySite.Domain.com:8530
-Waiting for 2 mins for Group Policy to notify of WUA policy change...
-Timed out waiting for Group Policy notification.
-Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://ProxyMPSecondarySite.Domain.com:8530 and Policy ENABLED
-Failed to Add Update Source for WUAgent of type (2) and id ({XXXXX}). Error = 0x80040692.

If the client brings the laptop back to any other office, the computer will identify the new server, brand policy, and begin scanning. The problem is I am having trouble with these clients at the remote site where they are not assigned to their primery. The "changing" of the server in local policy is somehow timing out, and therefore the scans failing.

Is this a bug which is fixable, or is this a known problem of having SUPs assigned at secondaries when Group Policy does not respond in a timely fashion? Is there a way to trick boundaries into avoiding the change? Or is there some other potential VPN related item (ports being blocked, etc.) that could be causing this?

I am open to all ideas - and have all of the logs.

Windows XP SP2 Workstations Do Not Recieve Updates From SCCM

Sun, 05 Apr 2009 17:46:58 Z

Hello!

I'm currently testing out SCCM and I'm having trouble deploying updates to Windows XP SP2 clients. In my testing enviroment, I created a test update with a deadline and assigned it to the appropriate group. On the client computer I performed the Machine Policy Retrieval & Evaluation Cycle, Software Updates Deployment Evaluation Cycle, and Software Updates Scan Cycle actions. In the WUAHandler it shows it points to my WSUS server then starts searching for updates and ends with "Successfully completed scan".

I noticed the update was not downloaded/installed even at the deadline I set. So I thought it was because the workstation was on SP2, so I upgraded it to SP3, still no luck. Then I thought maybe its the Windows Update Agent, so I updated the agent to the current version which seems to be 7.2.6001.788. Still no luck. What I don't understand is that my Vista workstations recieve updates fine, even with the same group policy I have setup for XP.

When browsing I came across that you don't have to configure group policy for the SUP but I configure it exactly how it showed it in the log, I even disabled the GPO just to test if it was an error on my part which it was not.

I currently have group policy set to:
Configure Automatic Updates: Disabled
Specify Intranet Microsoft update service location: Enabled
Allowed signed updates from intranet Microsoft update service location: Enabled

Does something need to be updated before I push updates to Windows XP SP2 workstations thats different from Vista?

Thanks,

Rick

System Center Updates Publisher Install Question

Tue, 19 May 2009 19:09:14 Z

I'm running Server 2008 x64 with SCCM R2, SQL 2005 SP2. I want to install the SCUP for SCCM, but the installer is unable to verify the database and instance.

I have ran the script to create the database and have used every naming standard I can think of when entering the name of the SQL server in the text field of the installer. The account I am using to install has DBO user mappings to the mscuptbd in SQL. However, I am unable to add the special SCCM user mapping to the database. I get an error stating 'add user mapping failed..... cannot use with special dbo' ...........Has anyone seen anything of this nature?

Thanks,

-M

SCUP MMC crash when pointing to MSP file

Tue, 05 May 2009 15:13:41 Z

I'm trying to create a SCUP patch entry where the patch in question is an MSP file. I can successfully enter all of the basic data. But the moment that I specify the patch and download URL (.msp file) and then click Next, I get an app crash.

If I enter an exe patchname and location, it all works fine. it's only when try and reference an msp file for the patch when it crashes.

I have the msp file on my c:\ drive, and I'm pointing to the proper Internet URL to download this patch - the exclamation points go away and all looks good. I'm not even entering any commandline switches yet and I get the crash.

I'm running an x64 Vista system. the error i get is below. Has this been seen before? am I missing a patch that can fix this?

Description:

Stopped working

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: mmc.exe

Problem Signature 02: 6.0.6001.18000

Problem Signature 03: 47918d09

Problem Signature 04: Microsoft.UpdateServices.Administration

Problem Signature 05: 3.1.6001.1

Problem Signature 06: 4797eee8

Problem Signature 07: 46d

Problem Signature 08: 14b

Problem Signature 09: SBSGNT3I1THQKAH3YXTPIOZMIO314FJD

OS Version: 6.0.6001.2.1.0.256.1

Locale ID: 1033

Need help with setting up maintenance window, please.

Mon, 23 Nov 2009 15:43:26 Z

We are setting up software distributions and I have my collection made, but I didn't see where I could set maintenance windows. I basically want it to be able to do Microsoft Patches during the day (to target all pc's including the ones people take home at 5) and then reboot at 10 pm and allow the reboot to only happen between 10 PM and 6 AM.

I have my Updates setup, but when I try to get them to a computer, I had it set to not reboot during the maintenance window, but I didn't see where the maintenance window was.

WSUS clients return to an old WSUS server

Fri, 20 Nov 2009 14:59:18 Z

Hello
I've reinstalled my WSUS 3.0 sp 1 server on w2k3 x64. Now my WSUS server uses 8530 port (it used standard 80 port before). I used GPO to apply changes for my domain. It worked but now I'm loosing each week several computers (they are not responding to the server and updates don't apply for them). When I check their WUServer in registry it is changet to an old one http://192.168.2.2 instead of http://192.168.2.2:8530.
Do you have any idea how to stop it?

Thanks

WSUS & SCCM 2007 on same server - correct port config?

Tue, 24 Nov 2009 14:07:22 Z

Hi people,

I'm just after a bit of clarification really, i have WSUS and SCCM 2007 installed on the same box(i know it's not good practice) for testing purposes and i have had a few issues with Syncin etc and i just wanted some clarification of what the port settings for them should be - they are both installed under the default port of *80 but i have been told that WSUS needs to go on a different port if SCCM2007 is running on the same server - is that correct? Wsus side of things is up, running and working with clients fine, but have issues with sccm2007 syncing from wsus and commumicating with clients. Any help greatly appreciated as always! Mike

WSUS instead of SUP

Thu, 12 Nov 2009 10:10:21 Z

Hi,

I have a question concerning the use of a WSUS server that is not a SUP. One of my admins wants to use his own WSUS server instead of our SUP. So he wants to create a gpo for his clients to use a local WSUS server. My concern was that the clients would not correctly report their update stati, but it seems ok.
Do you know if we might get any problem with this scenario?

Cheers
Sebastian

Windows 2008 R2 Still Equals Windows 7 Server in SUP Products Listing

Thu, 12 Nov 2009 21:28:18 Z

Is there any thought to changing the name of Windows 7 Server to Windows 2008 R2 in the Products listed in the Software Update Point configuration?

Orange County District Attorney

SCCM Updates stuck in Downloading State

Thu, 29 Oct 2009 16:57:28 Z

I am running SCCM 2007 with 800 clients. I have been sucessfully performing windows updates through SCCM without an issue for about 6 months. Recently I approved updates released in October but all the updates on the client PC's are stuck in a "Downloading" state. The times reach 38 hours on some machines.

I have tried to cancel the updates by removing them from the Advertisements and from the Deployment packages but they still try to run everyday on the client desktops. If I manually go to Windows Update and install the updates they work fine, but the SCCM deployment keeps trying none the less.

How can I do one or both of the following:

A) Cancel the updates so they no longer want to run on the clients
B) Fix the issue so the updates download properly.

The process that I use to approve and deploy updates:

Under Site Database -> Computer Management -> Software Updates
I select the updates I want to deploy and add them to a new update list. I place a check into the box to download the files associated to the updates.
Once the update list is built I select to deploy the updates, give it a name that represents the update period
I select a template that deploys but suppresses restart in the updates.
I select a deployment package, the same one I used for all my past updates
Download from the Internet
English
Schedule
Finish.

This has worked sucessfully for months.

Thank you for any help that can be offered.

Best practice to apply software updates on Critical production servers

Sat, 21 Nov 2009 04:28:29 Z

I would like to know if there is any best practice to apply software updates on critical production servers like AD, DHCP, DC, Hyper-V server? Some even said should patch manually.

ITMU packages not visible after SCCM upgrade

Tue, 20 Oct 2009 11:45:45 Z

SMS 2003 with ITMU was upgraded to SCCM (without ITMU uninstallation) and packages used in ITMU are now not visible under "Deployment Packages" folder. I know they are still there because when I right click on folder "Deployment Packages" >>> "Copy packages" >>> select DP >>> Next, they are in the list of packages I can copy to the distribution point. How can I remove these packages from all DP ? ITMU (and also the SCCM version) is now uninstalled.

Child Primary Software Updates not syncing

Mon, 23 Nov 2009 09:33:34 Z

Hi all,

I'm having some issues where any changes i make to Software Updates on the Central site, aren't being propogated down to one of my child primary sites.

I don't have any of my updated update lists, deployment adverts or deployment packages on the child primary. In the objreplmgr.log i get the following:

Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48769.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_0f744560-6676-4cf8-9772-66e279605675/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Failed to insert Object 8a2c010f-f4c0-4472-afd3-e5665a221430 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48769.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49256.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_faeb8b22-0784-4b20-8dd8-8a5a8113d7b6/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Failed to insert Object 87348921-6fe9-4335-afe1-a15ee54221a0 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49256.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49710.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:41 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_cc4a5533-335a-4a48-9a34-ac0dd2e8b627/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object 8ebbfa42-dbff-4acf-8f6f-5cc73ff83df3 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49710.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49268.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_4f7cd017-f489-4fa5-9849-30ed5ef5f5f2/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object 6b2a207f-b7e5-4a55-8fae-bce1f85b96a0 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49268.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48903.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_48eabf03-4c20-499c-ba18-b7de88096c40/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_b5064e0c-2c90-45a1-a064-2195815f2390/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_5e9db847-fbed-4b60-808d-90655e79dffa/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object fc7c3752-4c17-473c-8bff-75eed375fd61 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48903.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49744.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_cee202e0-51a1-4861-b5d2-f7aaf72c90f6/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object 42c1601b-a2b5-4e98-8a6e-9d030998435d from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49744.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48906.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_d3f643b0-834d-4e87-b249-4a919ce828a9/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object 92b32c22-785b-4cf1-898f-5258e75f7b3c from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48906.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49736.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_8f7c96bb-428c-4481-bf23-d2d49b46a2d6/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object f37b3173-1576-4847-a18a-c68285173a75 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49736.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48771.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_f376855b-5b78-40b9-addc-884fa62666bf/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object 643778a9-6472-4208-bb0f-f416d18a4752 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48771.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48660.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Waiting for changes for 29 minutes    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    3248 (0x0CB0)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_f4a8ece7-083d-4989-8a72-23dcd49eab26/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Failed to insert Object 528fab21-71c5-4cc5-923d-ffd710095da4 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48660.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49927.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:42 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_1d1c8db9-c1d1-4c84-86c3-3a45b5ae5a2a/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_42c1601b-a2b5-4e98-8a6e-9d030998435d/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_528fab21-71c5-4cc5-923d-ffd710095da4/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_92b32c22-785b-4cf1-898f-5258e75f7b3c/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_9bf01484-3c26-4b16-b846-54a057162f12/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_fc7c3752-4c17-473c-8bff-75eed375fd61/1(1)(1);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:45 AM    6216 (0x1848)
Failed to insert Object ScopeId_9CEB6DAB-6599-4149-9F23-531CF2D12C91/AuthList_5D29AF23-55DF-41C8-A792-181B2822B208 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49927.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:45 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48144.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:45 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_34b52415-a5ba-41e9-8072-9d2dee8b22a9/2(2)(1);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object ScopeId_9CEB6DAB-6599-4149-9F23-531CF2D12C91/AuthList_DB7C4E19-AE39-40A0-B8D2-1F60801891DA from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48144.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48796.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_0005db62-0126-46fa-9a35-6820e715b999/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_b24b2c6d-31a2-402e-9fd2-e61b9d05b8c1/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object 1d1c8db9-c1d1-4c84-86c3-3a45b5ae5a2a from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48796.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48841.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_21455a34-0669-494c-a6fd-4d1c1edc28d2/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object c896fbdd-74a2-441b-b50b-0c4cf7857700 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48841.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49251.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_a5f436d2-f24b-4cfe-b780-6f226f9d6a9b/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object 6eedc3bc-f93b-4572-8799-8ef43ce01a91 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49251.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48853.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_44a1ffdc-c937-4e7d-866c-e8cda216d8a0/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object 93cac5cc-ee42-4ace-ab08-b5ffe6df14a0 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48853.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48765.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_9054c29f-fdae-4dc3-9b2b-9f7c68cfede4/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object 695f384e-105f-462e-88fe-c88c46f542d0 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48765.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48599.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_b388d69f-3adf-4233-9893-201c5ad192c6/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Failed to insert Object 4e2c6078-e861-4274-8eba-5a012fb85f7c from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48599.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_51595.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:46 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_643778a9-6472-4208-bb0f-f416d18a4752/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_8a2c010f-f4c0-4472-afd3-e5665a221430/1(1)(1);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Failed to insert Object ScopeId_9CEB6DAB-6599-4149-9F23-531CF2D12C91/AuthList_220D0332-5A45-441F-A6F5-9F2BABB91C33 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_51595.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48822.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_4378b1c3-2e3c-426f-b401-a0ded1dad8a4/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Failed to insert Object 846a63ba-657d-4f4e-a3d2-afc40d8e4204 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48822.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48767.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_601e101d-9add-4632-9b7f-5bf5eed13237/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Failed to insert Object aef9dd15-f6e9-43c4-bd9a-e11f2c7fa684 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48767.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_35996.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:47 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_4378b1c3-2e3c-426f-b401-a0ded1dad8a4/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_f4a8ece7-083d-4989-8a72-23dcd49eab26/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:48 AM    6216 (0x1848)
Failed to insert Object 34b52415-a5ba-41e9-8072-9d2dee8b22a9 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_35996.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:48 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_51575.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:48 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_643778a9-6472-4208-bb0f-f416d18a4752/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_6eedc3bc-f93b-4572-8799-8ef43ce01a91/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_6b2a207f-b7e5-4a55-8fae-bce1f85b96a0/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_8a2c010f-f4c0-4472-afd3-e5665a221430/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_93cac5cc-ee42-4ace-ab08-b5ffe6df14a0/1(1)(1);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_c896fbdd-74a2-441b-b50b-0c4cf7857700/1(1)(1);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Failed to insert Object ScopeId_9CEB6DAB-6599-4149-9F23-531CF2D12C91/AuthList_F8B2EDA5-F134-4F85-83DF-EFFBC4EECD13 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_51575.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49232.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_408ac704-c231-4213-a820-a359ceb81cde/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Failed to insert Object 83a2e0b2-d2bd-4535-91ae-c087ab41de57 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_49232.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Processing replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48878.CID in retry.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Referenced configuration items are not available yet: http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_48eabf03-4c20-499c-ba18-b7de88096c40/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_b5064e0c-2c90-45a1-a064-2195815f2390/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_5e9db847-fbed-4b60-808d-90655e79dffa/1(1)(6);http://schemas.microsoft.com/systemsmanagementserver/Site_9CEB6DAB-6599-4149-9F23-531CF2D12C91/SUM_4378b1c3-2e3c-426f-b401-a0ded1dad8a4/1(1)(6);    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Failed to insert Object 9bf01484-3c26-4b16-b846-54a057162f12 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\Retry\0GL_48878.CID.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Waiting for changes for 59 minutes    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 10:33:51 AM    6216 (0x1848)
Wait timed out after 29 minutes while waiting for at least one trigger event.    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 11:03:36 AM    3248 (0x0CB0)
Waiting for changes for 29 minutes    SMS_OBJECT_REPLICATION_MANAGER    2009/11/23 11:03:42 AM    3248 (0x0CB0)

In the inboxes\objmgr.box\INCOMING\Retry there are a number of CID files which i presume are the files which need to be processed to fully sync with my central.

I've seen this thread - http://www.myitforum.com/articles/42/view.asp?id=11422 - and i originally did have a number of expired updates but have got rid of these and done a syncchild but with no success.

Does any one have any idea how to solve this issue? Is it a problem with WSUS maybe?

Any help is appreciated

Cheers
Nivor

How to generate Patch report SCCM SP1

Thu, 19 Nov 2009 07:55:28 Z

Hi,

I need to generate patch report from SCCM. Like

-------------------------------------------------------
Host name | IP address | MS08-067 |
---------------------------------------------------------
OFSS01 | 192.168.0.234 | YES

Thanks in Advance.
Shashidhar

Updates with no Maximum Severity Rating

Mon, 23 Nov 2009 12:44:54 Z

Hi,

I've created a Search Folder in my Config Manager console. The criteria for the search folder is to return updates with a Severity of 'Critical' or 'Important'. I used the list of updates it returned to create an Update List for deployment to my client PCs.

As a verification test, I decided to make a comparison between what updates Microsoft Update and my SUP offered the client PCs. I connected to the online version of Microsoft Update from a Config Manager client PC which had already succesfully recieved updates from my SUP. To my surprise, a six 'Important' updates showed up as available.

These were:

915597
890830
975364
976749 (MS advise this as a critical update)
974332
974431

I went back and checked the SUP again. The six updates I was missing all had shown up in the catalog of available updates the Active SUP had downloaded from Microsoft. However, on examination of the Update Details tab of each individual update, they do not show any value for 'Maximum Severity Rating'. This would explain why they did not meet my search criteria of 'Important' and 'Critical'.

I had been following guidelines for creating Update Lists from the book 'Mastering System Center Configuration Manager 2007 R2'. Is there a better approach for me to take in creating Update Lists given that the Severity Rating does not consistently appear on updates?

If my understanding of this issue is correct, I think the omission of this information has potential to land a lot of Admins in hot water.

Michael

SCUP 4.5 - Remove published Updates from Update Repository in SCCM

Fri, 30 Oct 2009 11:54:17 Z

Hi all,

I've created a new update in SCUP and published it inadvertently to SCCM (it was the wrong version).
Now it seems that there is no way to remove this update from the Update Repository of SCCM.
I want to remove the entire entry below "Software Updates - Update Repository - Critical Updates"

How can i clean up the Update Repository?
What's the standard practice to remove software updates imported by SCUP?
Do i have to modify the SCCM database directly?

Thanks in advance

best regards
Alex

Failure Code 12029 / Error Code -2147012867

Tue, 08 Jan 2008 11:47:08 Z

Hi,

I am trying to deploy software updates to 2 Windows 2000 Servers. Below are what I get:

1. Checking Status Message Viewer, I get Message ID 11423 and Failure Code of 12029 every 30 minutes.

2. Using Report Viewer, the Error Code shown is -2147012867

3. Checking the WindowsUpdate.Log, I see "WARNING: GetConfig failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200".

4. Checking on C:\Winnt\System32\Ccm\Cache, there was not a single file or folder inside.

5. Finally, a Message ID 11756 that says "Updates evaluation job completed with failure for assignment {51131A34-FDB4-4557-8B78-66AE988B440F}. The operating system reported error 2147942405: Access is denied" appears.

I have deployed successfully on Windows 2000 Professional computers (located on another Collection) and I keep wondering what I am doing wrong on the servers. They have separate Deployments although the settings (Date, Schedules, Restart, etc.) are the same.

I checked their Registry (both Windows 2000 Pro and Server) and all of them point to the same and correct Software Update Point and port number. The account that I am using is the same throughout - account that is a member of Domain Admins group and this group is a member of the servers' local admin group.

Please point me to the right direction to solve this.

Many thanks,

Jelo V

effective software updates deployment strategy

Mon, 23 Nov 2009 05:19:38 Z

Hi all!

I've been reading some articles & tutorials on software update deployment and still a bit confused on how to deploy & manage updates effectively.

My questions are:

# Under Computer Management > Software Updates section ...
What is the difference between Deployment Management and Deployment Packages ?
I understand that the packages contain the software updates needed, but so is the deployment management.
And what's the deal with Update Lists ?
How is it different that the Search Folders ?

# How to manage and deploy updates effectively?
AFAIK, the steps to deploy updates are:
- choose which updates
- right-click > Deploy Software Updates , it will auto-download the updates
- once done, it should automatically deploy the updates to the collection specified

But what to do for the next month?
How to find out which new updates that haven't been downloaded/deployed?
Instead of having an extra of 12 different entries under Deployment Management each year, can it be added to the existing deployment/package so it will automatically downloaded & added to the updates that are being deployed?

For example:
I have a deployment task named All MS approved Patches , which using a deployment package called All MS updates package .
A month later, there are 5 new updates.
How do I add those 5 to the existing deployment?
Same package? Same deployment task?

I really appreciate your input.

Ap

patch installing issue (Fails)

Fri, 20 Nov 2009 03:46:05 Z

Hi

most of the systems in our network is not getting new patch update, the patch has been downloaded to cache folder, but installation fails, not able to capture the reason for the same.

manual installation of the same patch is working fine.

the error in Wuahandler log as follows

Going to search using WSUS update source. WUAHandler 11/19/2009 12:43:37 PM 3476 (0x0D94)
Synchronous searching started using filter: 'UpdateID = '54173d00-6670-4e5c-a601-70ae316aa295' AND DeploymentAction = *'... WUAHandler 11/19/2009 12:43:37 PM 3476 (0x0D94)
Failed to run Search() on WUAgent. Error = 0x8024001e. WUAHandler 11/19/2009 12:51:43 PM 3476 (0x0D94)
Searching update (UpdateID = '54173d00-6670-4e5c-a601-70ae316aa295' AND DeploymentAction = *) from the WSUS cache failed. Error = 0x8024001e. WUAHandler 11/19/2009 12:51:43 PM 3476 (0x0D94)
Could not find update (54173d00-6670-4e5c-a601-70ae316aa295:101) in any of the registered update sources, skipping. WUAHandler 11/19/2009 12:51:43 PM 3476 (0x0D94)
No updates were actionable for installation. WUAHandler 11/19/2009 12:51:43 PM 3476 (0x0D94)
Failed to open to WMI namespace '\\.\ROOT\CIMV2\SMS' (8007045b) WUAHandler 11/19/2009 12:51:43 PM 3736 (0x0E98)
Failed to report current WUAgent version to HINV, continuing. Error = 0x8007045b. WUAHandler 11/19/2009 12:51:43 PM 3736 (0x0E98)
Failed to get proxy information, continuing without proxy info. Error = 0x80040219. WUAHandler 11/19/2009 12:51:43 PM 3736 (0x0E98)
Failed to set proxy configuration to WUA, continuing. Error = 0x80040219. WUAHandler 11/19/2009 12:51:43 PM 3736 (0x0E98)
Failed to run BeginSearch() on WUAgent. Error = 0x8007045b. WUAHandler 11/19/2009 12:51:43 PM 3736 (0x0E98)
Async searching of updates using WUAgent started. WUAHandler 11/19/2009 12:59:01 PM 3908 (0x0F44)
Async searching of updates using WUAgent started. WUAHandler 11/19/2009 1:28:03 PM 3296 (0x0CE0)
Async searching of updates using WUAgent started. WUAHandler 11/19/2009 1:46:54 PM 2096 (0x0830)
Async searching completed. WUAHandler 11/19/2009 2:26:08 PM 3896 (0x0F38)

EXEC Manager log

The user has logged off. execmgr 11/19/2009 1:38:39 PM 4424 (0x1148)
Program Software Updates Program is running when user loggs off execmgr 11/19/2009 1:38:41 PM 4424 (0x1148)
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a execmgr 11/19/2009 1:38:57 PM 2716 (0x0A9C)
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a execmgr 11/19/2009 1:38:57 PM 2716 (0x0A9C)
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a execmgr 11/19/2009 1:38:57 PM 2716 (0x0A9C)
Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A execmgr 11/19/2009 1:38:57 PM 2716 (0x0A9C)
Request in running or report status found for program Software Updates Program package {C2816BCE-7FB0-408F-ABC4-A3F2571BE5C5} execmgr 11/19/2009 1:46:40 PM 2112 (0x0840)
System restarted while program Software Updates Program is running execmgr 11/19/2009 1:46:40 PM 2112 (0x0840)
Resuming Update Program execmgr 11/19/2009 1:46:40 PM 2112 (0x0840)
Updates installation resumed after service restart. execmgr 11/19/2009 1:46:40 PM 2112 (0x0840)
Looking for MIF file to get program status execmgr 11/19/2009 3:15:01 PM 544 (0x0220)
Script for Package:{C2816BCE-7FB0-408F-ABC4-A3F2571BE5C5}, Program: Software Updates Program succeeded with exit code 0 execmgr 11/19/2009 3:15:01 PM 544 (0x0220)
Execution is complete for program Software Updates Program. The exit code is 0, the execution status is Success execmgr 11/19/2009 3:15:01 PM 544 (0x0220)
Mandatory execution requested for program Software Updates Program and advertisement {CA6171CA-7A37-447F-A67F-08E49882F23A} execmgr 11/19/2009 4:03:01 PM 2176 (0x0880)
Creating mandatory request for advert {CA6171CA-7A37-447F-A67F-08E49882F23A}, program Software Updates Program, package {CA6171CA-7A37-447F-A67F-08E49882F23A} execmgr 11/19/2009 4:03:01 PM 2176 (0x0880)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 11/19/2009 4:03:02 PM 2176 (0x0880)
Executing program in Admin context execmgr 11/19/2009 4:03:02 PM 2176 (0x0880)
Execution Manager timer has been fired. execmgr 11/19/2009 4:03:02 PM 2700 (0x0A8C)
Execution Request for package {CA6171CA-7A37-447F-A67F-08E49882F23A} program Software Updates Program state change from NotExist to NotifyExecution execmgr 11/19/2009 4:03:02 PM 2176 (0x0880)
Executing program as an update. execmgr 11/19/2009 4:03:03 PM 2176 (0x0880)
Executing Update Program execmgr 11/19/2009 4:03:03 PM 2176 (0x0880)
Updates Installation started for the passed command line execmgr 11/19/2009 4:03:03 PM 2176 (0x0880)
Request in running or report status found for program Software Updates Program package {CA6171CA-7A37-447F-A67F-08E49882F23A} execmgr 11/19/2009 4:21:11 PM 2416 (0x0970)
Service stopped while program Software Updates Program is running execmgr 11/19/2009 4:21:11 PM 2416 (0x0970)
Resuming Update Program execmgr 11/19/2009 4:21:11 PM 2416 (0x0970)
Updates installation resumed after service restart. execmgr 11/19/2009 4:21:12 PM 2416 (0x0970)

Please guide to take further steps in troubleshooting

Hide software update icon from taskbar

Sun, 22 Nov 2009 14:32:04 Z

When the software updates are available to the client, it will start displaying "software update" icon on the taskbar. Could I hide the software update icon from the taskbaR? I have already hide notification display. How can I install the updates without notify the user?

Software Updates requires restart or not

Sun, 22 Nov 2009 09:31:12 Z

Is there a way to check if the software updates require to restart before we deploy the software updates?

Software Updates Not Applying

Tue, 08 Sep 2009 22:37:16 Z

I have been trying for a while to deploy updates using the Software Updates node on SCCM.

I am using SCCM SP1 R2.
Ran Synchronization
Downloaded the update I wanted to test this with
Created a deployment package and assigned it to a collection with a valid SCCM client
Uninstalled the test update on the client machine, and manually run the "Software Updates Deployment Evaluation Cycle" multiple times, with no errors in the logs
Boundaries are properly defined (I tried it via subnet and Active Directory Site)
Schema is extended, and the SCCM client is working properly

I have done the following:

Ran a repair install on the SCCM client
Created multiple Deployment Templates
Reran Homepage Sync
Set a mandatory and non-mandatory update
Setting the GPO to use the FQDN of the SCCM/WSUS server with the appropriate port
Setting the GPO to Not Configured except for an Enabled setting on "Allow signed content from intranet Microsoft update service location"
Blocking inheritance from the higher WSUS GPO, and then running RSOP.msc from the local client to verify that only the Local Policy is being applied

All of the logs that I've looked at (WindowsUpdate.log, ScanAgent.log, StatusAgent.log, UpdatesDeployment.log, WUAHandler.log, etc) all do not have any errors. The only thing that is out of the ordinary is that the Deployment Status for all of the updates that I've tried show that it is Targeted, but the client status is shown as Unknown instead of reporting the status correctly back to the MP.

Need help to configure SUP/WSUS using sccm 2007 for our layout.

Thu, 30 Oct 2008 13:42:47 Z

Here is the senerio: Presently we have a WSUS standalone infrastrure that was used along side sms 2003 to patch.
We have recently installed Confi Mgr 2007 and now want to use SUP. We were planning on using a external win 2003 server as the SUP/WSUS.
First thing we would do is delete the GPO's in AD for the existing WSUS box. Then install WSUS/SUP on the
external server. Here is where it gets a little muddy for me, do we just need to install the WSUS admin console on each pri site , add the remote server(sup role) on each pri and be good to go or
do we need to install WSUS/SUP on each pri site system and setup each as an active SUP?

Our present layout is a Central site(MP, SLP, Reporting Point) with no clients reporting to it and 3 pri sites with anywhere from 5,000 to 7,0000 clients reporting to each site.
The servers are on windows 2003, the central being the beefest hw while the pri servers are a few years old

Thanks in advance for any tips.

Software Updates Deployment Status failed

Sat, 21 Nov 2009 04:17:57 Z

Hi,

I deployed a software update to a collection, but some of the clients have status of failed to install and general failure. Is there any indication on the status? Since the software update failed to install on some clients, will these clients try to install the updates again?

How can I increase the timeout period for WSUS sync between secondary sites and the primary?

Wed, 22 Jul 2009 23:01:58 Z

I'm getting Timeouts synchronizing between one secondary site and my primary site. The line to the secondary is very sloooooooooooow. The wsyncmgr.log shows:

Synchronizing WSUS server OCDAOCATT002 SMS_WSUS_SYNC_MANAGER 7/22/2009 2:10:10 PM 7532 (0x1D6C)
Synchronizing WSUS server ocdaocatt002.da.ocgov.com ... SMS_WSUS_SYNC_MANAGER 7/22/2009 2:10:11 PM 1832 (0x0728)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 7/22/2009 2:10:11 PM 1832 (0x0728)
sync: WSUS synchronizing categories SMS_WSUS_SYNC_MANAGER 7/22/2009 2:10:13 PM 1832 (0x0728)
sync: WSUS synchronizing other items, processed 22 out of 44 items (50%) SMS_WSUS_SYNC_MANAGER 7/22/2009 2:10:21 PM 1832 (0x0728)
Sync failed: LocalDBOtherError: SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.~~at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 7/22/2009 2:20:40 PM 7532 (0x1D6C)

Where can I tweak the Timeout for this operation?

Orange County District Attorney

Problems using Software Updates

Fri, 20 Nov 2009 18:02:39 Z

We are very, very new to this and have to have it working in 7 days. This seems to happen a lot.

We went through the processes of making our templates. I then made the Deployment Management and the Deployment Packages. It failed during the evaluation cycle with the same issue as the one in this post http://social.technet.microsoft.com/Forums/en/configmgrsum/thread/dd0df81c-d586-42ae-9440-f37643348746.

Our Sys Admin team made a different OU in AD to grant the things the specified in the aforementioned post and we still got the error. Our Sys Admin made a change and now I'm trying to get the policy to change and see if it will work on SCCM Reports. From what I read, I need to go to the Reports > "States 2 - Evaluation states for a deployment", but I don't see anything from after we made changes. So I'm not sure how to make the computer try to re-run the evaluation and then try to receive the updates.

In the ConfigMgr report, I see that the "State Name" is "Evaluation failed". It has a Message ID of 11756 and this is in the description: Updates evaluation job completed with failure for assignment {EDAA84A3-EAB1-4445-A2FC-051B99DD3B6D}. The operating system reported error -2147219822: Updates evaluation job completed with failure for assignment {EDAA84A3-EAB1-4445-A2FC-051B99DD3B6D}. The operating system reported error -2147219822:

The windowsupdate.log contains the following information:
2009-11-17 16:42:25-0600 292 274 CreateService for wuauserv succeeded
2009-11-17 16:56:35-0600 776 554 Service Main starts
2009-11-17 16:56:35-0600 776 554 Using BatchFlushAge = 4707.
2009-11-17 16:56:35-0600 776 554 Using SamplingValue = 597.
2009-11-17 16:56:35-0600 776 554 Successfully loaded event namespace dictionary.
2009-11-17 16:56:36-0600 776 554 Successfully loaded client event namespace descriptor.
2009-11-17 16:56:36-0600 776 554 Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2009-11-17 16:56:36-0600 776 554 Successfully initialized NT event logger.
2009-11-17 16:56:36-0600 776 554 Successfully initialized event uploader 0.
2009-11-17 16:56:36-0600 776 554 Successfully initialized event uploader 1.
2009-11-17 16:56:36-0600 776 554 WU client with version 5.4.3790.2180 successfully initialized
2009-11-17 16:56:36-0600 776 554 Service status is now SERVICE_RUNNING
2009-11-17 16:57:21-0600 776 554 start delayed initialization of WU client
2009-11-17 16:57:21-0600 2004 7d8 Trying to make out of proc datastore active
2009-11-17 16:57:23-0600 2004 7d8 Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 added
2009-11-17 16:57:24-0600 2004 7d8 Service 9482F4B4-E343-43B6-B170-9A65BC822C77 added
2009-11-17 16:57:24-0600 2004 7d8 Data store successfully created
2009-11-17 16:57:24-0600 2004 7d8 Out of proc datastore is now active
2009-11-17 16:57:24-0600 776 554 Client Call Recorder finished delayed initialization
2009-11-17 16:57:24-0600 776 554 AU is not configured yet, generating timeout to launch setup wizard
2009-11-17 16:57:24-0600 776 554 AU finished delayed initialization
2009-11-17 16:59:18-0600 776 30c Service received connect notification
2009-11-17 16:59:18-0600 776 554 AU received event of 3
2009-11-17 16:59:18-0600 776 30c Service received logon notification
2009-11-17 16:59:18-0600 776 554 AU received event of 3
2009-11-17 17:02:24-0600 2004 7d8 Out of proc datastore is shutting down
2009-11-17 17:02:25-0600 2004 7d8 Out of proc datastore is now inactive
2009-11-18 16:57:24-0600 776 554 AU received event of 1
2009-11-18 16:57:24-0600 1516 69c Trying to make out of proc datastore active
2009-11-18 16:57:24-0600 1516 69c Out of proc datastore is now active
2009-11-18 17:02:24-0600 1516 69c Out of proc datastore is shutting down
2009-11-18 17:02:25-0600 1516 69c Out of proc datastore is now inactive
2009-11-19 10:58:50-0600 776 554 AU received event of 3
2009-11-19 10:58:50-0600 776 554 Cleared the proxy cache.
2009-11-19 10:59:00-0600 776 554 Cleared the proxy cache.
2009-11-19 10:59:04-0600 776 554 AU received event of 1
2009-11-19 10:59:04-0600 776 554 Successfully launched client for directive 2
2009-11-19 10:59:09-0600 776 554 Cleared the proxy cache.
2009-11-19 11:01:31-0600 3604 e3c DownloadIsInternetAvailable SUCCEEDED
2009-11-19 11:01:31-0600 3604 e3c OpenCDMContextEx SUCCEEDED
2009-11-19 11:01:31-0600 776 4dc WU client succeeds CClientCallRecorder::BeginFindUpdates from CDM with call id {4DDFBCF8-CD04-46C0-A8C7-289CEEDA8649}
2009-11-19 11:01:31-0600 776 3c8 WU client executing call {4DDFBCF8-CD04-46C0-A8C7-289CEEDA8649} of type Search Call
2009-11-19 11:01:31-0600 3708 e80 Trying to make out of proc datastore active
2009-11-19 11:01:31-0600 3708 e80 Out of proc datastore is now active
2009-11-19 11:01:31-0600 776 3c8 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}
2009-11-19 11:01:31-0600 776 3c8 Checking for different Redirector at: http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
2009-11-19 11:01:38-0600 776 3c8 Successfully refreshed Redirector cab.
2009-11-19 11:01:38-0600 776 3c8 PT: Using server URL https://update.microsoft.com/ClientWebService/client.asmx
2009-11-19 11:01:38-0600 776 3c8 PT: Calling GetConfig on server
2009-11-19 11:01:38-0600 776 3c8 Add header for accept-encoding: xpress succeeded
2009-11-19 11:01:38-0600 776 3c8 DetectCompressionType returning type 0, hr=0x1
2009-11-19 11:01:38-0600 776 3c8 GetConfig: 0x8024400a
2009-11-19 11:01:38-0600 776 3c8 PT: Cannot recover from fault, origin=GetConfig, hr=0x8024400a
2009-11-19 11:01:38-0600 776 3c8 Sync of Updates: 0x8024400a
2009-11-19 11:01:38-0600 776 3c8 OS Version = 5.1.2600.2.0.65792
2009-11-19 11:01:38-0600 776 3c8 Computer Brand = LENOVO
2009-11-19 11:01:38-0600 776 3c8 Computer Model = 9964A5U
2009-11-19 11:01:38-0600 776 3c8 Bios Revision = 5CKT51AUS
2009-11-19 11:01:38-0600 776 3c8 Bios Name = Lenovo ThinkCentre BIOS Ver 5CKT51.0
2009-11-19 11:01:38-0600 776 3c8 Bios Release Date = 2009-07-23T00:00:00
2009-11-19 11:01:38-0600 776 3c8 Locale ID = 1033
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: iuengine.dll = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuapi.dll = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuauclt.exe = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuauclt1.exe = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuaucpl.cpl = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuaueng.dll = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuaueng1.dll = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wuauserv.dll = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 ClientVersion: wucltui.dll = 5.4.3790.2180
2009-11-19 11:01:38-0600 776 3c8 WU client failed Searching for update with error 0x8024400a
2009-11-19 11:01:38-0600 776 3c8 WU client calls back to search call CDM with code Call failed and error 0x8024400a
2009-11-19 11:01:38-0600 776 3c8 WU client completed and deleted call {4DDFBCF8-CD04-46C0-A8C7-289CEEDA8649}
2009-11-19 11:01:39-0600 3604 e3c Operation completed due to earlier error. (hr=8024400A)
2009-11-19 11:01:39-0600 3604 e3c Unable to complete asynchronous search successfully. (hr=8024400A)
2009-11-19 11:01:39-0600 776 7ec ISusInternal API failed CClientCallRecorder::DisconnectCall with error 0x8024000c
2009-11-19 11:01:39-0600 3604 e3c ISusInternal::DisconnectCall failed, hr=8024000C
2009-11-19 11:01:39-0600 3604 e3c CCdm::ExecuteSearch FAILED, hr=0x8024400a
2009-11-19 11:01:39-0600 3604 e3c CCdm::ExecuteSearchForOneDriverUpdate FAILED, hr=0x8024400a
2009-11-19 11:01:39-0600 3604 e3c CCdm::FindMatchingDriver FAILED, hr=0x8024400a
2009-11-19 11:01:39-0600 3604 e3c FindMatchingDriver FAILED, hr=0x8024400a
2009-11-19 11:01:43-0600 776 3c8 REPORT EVENT: {B782C6CC-F7C3-4ED2-8912-A72091AB3D90} 1 2009-11-19 11:01:38-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400a CDM Failure Software Synchronization Error: Agent failed detecting with reason: 0x8024400a
2009-11-19 11:01:44-0600 776 3c8 Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{8B902E36-7659-453D-901C-77CF8618AF4B}.bin for writing.
2009-11-19 11:01:44-0600 776 3c8 Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{F81BF291-76EC-4479-AF4C-7F1119DE8925}.bin for writing.
2009-11-19 11:02:02-0600 3604 e20 CancelCDMOperation SUCCEEDED
2009-11-19 11:02:24-0600 3604 e20 CloseCDMContext SUCCEEDED
2009-11-19 11:06:07-0600 1676 3d4 WUCheckForUpdatesAtShutdown failed, hr=8024A000
2009-11-19 11:06:39-0600 3708 e80 Out of proc datastore is shutting down
2009-11-19 11:06:40-0600 3708 e80 Out of proc datastore is now inactive
2009-11-19 11:07:10-0600 776 30c Service received SERVICE_CONTROL_STOP control
2009-11-19 11:07:10-0600 776 554 Exiting Service Main
2009-11-19 11:07:10-0600 2604 a30 Failed to show client UI, directive=2, hr=80010108
2009-11-19 11:07:10-0600 776 554 WUAUENG ServiceMain exits. Exit code is 0x240001
2009-11-19 11:09:02-0600 476 cbc WUAutoUpdateAtShutdown failed, hr=8024000C
2009-11-19 11:17:33-0600 888 6c0 AU is forbidden; setting AU approval type to 'disabled'.
2009-11-19 12:07:43:439 1328 784 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-19 12:07:43:439 1328 784 Misc   = Process: c:\b121d0a06665cd540b89\wusetup.exe
2009-11-19 12:07:43:439 1328 784 Setup *********** Setup: Checking whether self-update is required ***********
2009-11-19 12:07:43:439 1328 784 Setup   * Inf file: c:\b121d0a06665cd540b89\wusetup.inf
2009-11-19 12:07:43:471 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\cdm.dll: target version = 5.5.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:518 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wuapi.dll: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:533 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wuauclt.exe: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:564 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:564 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wuaueng.dll: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:627 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wucltui.dll: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:643 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wups.dll: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:643 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wups2.dll: target version = 0.0.0.0, required version = 7.1.6001.65
2009-11-19 12:07:43:658 1328 784 Setup FATAL: Update required for C:\WINDOWS\system32\wuweb.dll: target version = 5.4.3790.2180, required version = 7.1.6001.65
2009-11-19 12:07:43:658 1328 784 Setup   * IsUpdateRequired = Yes
2009-11-19 12:07:43:658 1328 784 Setup *************
2009-11-19 12:07:43:658 1328 784 Setup ** START ** Setup: Installing client binaries
2009-11-19 12:07:43:658 1328 784 Setup *********
2009-11-19 12:07:43:658 1328 784 Setup   * Download directory: c:\b121d0a06665cd540b89\
2009-11-19 12:07:43:658 1328 784 Setup   * Stop and start service: Yes
2009-11-19 12:07:44:064 1328 784 Setup Starting file operations for section cdm_Standalone
2009-11-19 12:07:44:627 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\cdm.dll to C:\WINDOWS\system32\cdm.dll.wusetup.3484718.new
2009-11-19 12:07:44:627 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\cdm.dll.wusetup.3484718.new to C:\WINDOWS\system32\cdm.dll
2009-11-19 12:07:44:627 1328 784 Setup File operations for section cdm_Standalone completed successfully
2009-11-19 12:07:44:627 1328 784 Setup Starting file operations for section wuapi_Standalone
2009-11-19 12:07:44:705 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wuapi.dll to C:\WINDOWS\system32\wuapi.dll.wusetup.3484796.new
2009-11-19 12:07:44:783 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wuapi.dll.wusetup.3484796.new to C:\WINDOWS\system32\wuapi.dll
2009-11-19 12:07:44:783 1328 784 Setup File operations for section wuapi_Standalone completed successfully
2009-11-19 12:07:44:783 1328 784 Setup Setup successfully copied MUI file c:\b121d0a06665cd540b89\wuapi.dll.mui_en to C:\WINDOWS\system32\wuapi.dll.mui
2009-11-19 12:07:44:783 1328 784 Setup Starting file operations for section wuauclt_Standalone
2009-11-19 12:07:44:846 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wuauclt.exe to C:\WINDOWS\system32\wuauclt.exe.wusetup.3484937.new
2009-11-19 12:07:44:846 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wuauclt.exe.wusetup.3484937.new to C:\WINDOWS\system32\wuauclt.exe
2009-11-19 12:07:44:846 1328 784 Setup File operations for section wuauclt_Standalone completed successfully
2009-11-19 12:07:44:846 1328 784 Setup Starting file operations for section wuaucpl_Standalone
2009-11-19 12:07:44:877 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wuaucpl.cpl to C:\WINDOWS\system32\wuaucpl.cpl.wusetup.3484968.new
2009-11-19 12:07:44:924 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wuaucpl.cpl.wusetup.3484968.new to C:\WINDOWS\system32\wuaucpl.cpl
2009-11-19 12:07:44:924 1328 784 Setup File operations for section wuaucpl_Standalone completed successfully
2009-11-19 12:07:44:924 1328 784 Setup Setup successfully copied MUI file c:\b121d0a06665cd540b89\wuaucpl.cpl.mui_en to C:\WINDOWS\system32\wuaucpl.cpl.mui
2009-11-19 12:07:44:924 1328 784 Setup Starting file operations for section wuaueng_Standalone
2009-11-19 12:07:45:002 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wuaueng.dll to C:\WINDOWS\system32\wuaueng.dll.wusetup.3485062.new
2009-11-19 12:07:45:018 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wuaueng.dll.wusetup.3485062.new to C:\WINDOWS\system32\wuaueng.dll
2009-11-19 12:07:45:018 1328 784 Setup File operations for section wuaueng_Standalone completed successfully
2009-11-19 12:07:45:018 1328 784 Setup Setup successfully copied MUI file c:\b121d0a06665cd540b89\wuaueng.dll.mui_en to C:\WINDOWS\system32\wuaueng.dll.mui
2009-11-19 12:07:45:018 1328 784 Setup Starting file operations for section wucltui_Standalone
2009-11-19 12:07:45:080 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wucltui.dll to C:\WINDOWS\system32\wucltui.dll.wusetup.3485125.new
2009-11-19 12:07:45:127 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wucltui.dll.wusetup.3485125.new to C:\WINDOWS\system32\wucltui.dll
2009-11-19 12:07:45:346 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\en\wuau.adm to C:\WINDOWS\INF\wuau.adm.wusetup.3485437.new
2009-11-19 12:07:45:346 1328 784 Setup Setup successfullly moved C:\WINDOWS\INF\wuau.adm.wusetup.3485437.new to C:\WINDOWS\INF\wuau.adm
2009-11-19 12:07:45:346 1328 784 Setup File operations for section wucltui_Standalone completed successfully
2009-11-19 12:07:45:346 1328 784 Setup Setup successfully copied MUI file c:\b121d0a06665cd540b89\wucltui.dll.mui_en to C:\WINDOWS\system32\wucltui.dll.mui
2009-11-19 12:07:45:346 1328 784 Setup Setup successfully moved MUI file C:\WINDOWS\HELP\wuauhelp.chm to C:\WINDOWS\HELP\wuauhelp.chm.wusetup.3485437.bak
2009-11-19 12:07:45:346 1328 784 Setup Setup successfully copied MUI help file c:\b121d0a06665cd540b89\wuauhelp.chm_en to C:\WINDOWS\HELP\wuauhelp.chm
2009-11-19 12:07:45:346 1328 784 Setup Starting file operations for section wups_Standalone
2009-11-19 12:07:45:377 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wups.dll to C:\WINDOWS\system32\wups.dll.wusetup.3485468.new
2009-11-19 12:07:45:471 1328 784 Setup File operations for section wups_Standalone completed successfully
2009-11-19 12:07:45:471 1328 784 Setup Starting file operations for section wups2_Standalone
2009-11-19 12:07:45:471 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wups2.dll to C:\WINDOWS\system32\wups2.dll.wusetup.3485562.new
2009-11-19 12:07:45:471 1328 784 Setup Setup found that target file C:\WINDOWS\system32\wups2.dll doesn't exist
2009-11-19 12:07:45:471 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wups2.dll.wusetup.3485562.new to C:\WINDOWS\system32\wups2.dll
2009-11-19 12:07:45:471 1328 784 Setup File operations for section wups2_Standalone completed successfully
2009-11-19 12:07:45:471 1328 784 Setup Starting file operations for section wuweb_Standalone
2009-11-19 12:07:45:471 1328 784 Setup Successfully copied source file c:\b121d0a06665cd540b89\wuweb.dll to C:\WINDOWS\system32\wuweb.dll.wusetup.3485562.new
2009-11-19 12:07:45:502 1328 784 Setup Setup successfullly moved C:\WINDOWS\system32\wuweb.dll.wusetup.3485562.new to C:\WINDOWS\system32\wuweb.dll
2009-11-19 12:07:45:502 1328 784 Setup File operations for section wuweb_Standalone completed successfully
2009-11-19 12:07:45:502 1328 784 Setup Starting registry operations for section cdm_Standalone
2009-11-19 12:07:45:502 1328 784 Setup Completed registration operations for section cdm_Standalone: status 0
2009-11-19 12:07:45:502 1328 784 Setup Starting registry operations for section wuapi_Standalone
2009-11-19 12:07:45:502 1328 784 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuapi.dll"
2009-11-19 12:07:45:643 1328 784 Setup Completed registration operations for section wuapi_Standalone: status 0
2009-11-19 12:07:45:643 1328 784 Setup Starting registry operations for section wuauclt_Standalone
2009-11-19 12:07:45:643 1328 784 Setup Completed registration operations for section wuauclt_Standalone: status 0
2009-11-19 12:07:45:643 1328 784 Setup Starting registry operations for section wuaucpl_Standalone
2009-11-19 12:07:45:643 1328 784 Setup Completed registration operations for section wuaucpl_Standalone: status 0
2009-11-19 12:07:45:643 1328 784 Setup Starting registry operations for section wuaueng_Standalone
2009-11-19 12:07:45:643 1328 784 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
2009-11-19 12:07:46:377 1328 784 Setup Completed registration operations for section wuaueng_Standalone: status 0
2009-11-19 12:07:46:377 1328 784 Setup Starting registry operations for section wucltui_Standalone
2009-11-19 12:07:46:377 1328 784 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wucltui.dll"
2009-11-19 12:07:46:408 1328 784 Setup Completed registration operations for section wucltui_Standalone: status 0
2009-11-19 12:07:46:408 1328 784 Setup Starting registry operations for section wups_Standalone
2009-11-19 12:07:46:408 1328 784 Setup Completed registration operations for section wups_Standalone: status 0
2009-11-19 12:07:46:408 1328 784 Setup Starting registry operations for section wups2_Standalone
2009-11-19 12:07:46:408 1328 784 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups2.dll"
2009-11-19 12:07:46:424 1328 784 Setup Completed registration operations for section wups2_Standalone: status 0
2009-11-19 12:07:46:424 1328 784 Setup Starting registry operations for section wuweb_Standalone
2009-11-19 12:07:46:424 1328 784 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuweb.dll"
2009-11-19 12:07:46:455 1328 784 Setup Completed registration operations for section wuweb_Standalone: status 0
2009-11-19 12:07:46:455 1328 784 Setup Processing registry operations completed. Deleting backup files.
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\cdm.dll.wusetup.3484718.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\wuapi.dll.wusetup.3484796.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\wuauclt.exe.wusetup.3484937.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\wuaucpl.cpl.wusetup.3484968.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\wuaueng.dll.wusetup.3485093.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\wucltui.dll.wusetup.3485171.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\INF\wuau.adm.wusetup.3485437.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\HELP\wuauhelp.chm.wusetup.3485437.bak
2009-11-19 12:07:46:455 1328 784 Setup Successfully deleted backup file C:\WINDOWS\system32\wuweb.dll.wusetup.3485562.bak
2009-11-19 12:07:46:486 1092 414 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-19 12:07:46:486 1092 414 Misc   = Process: C:\WINDOWS\System32\svchost.exe
2009-11-19 12:07:46:486 1092 414 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-19 12:07:46:486 1092 414 Service *************
2009-11-19 12:07:46:486 1092 414 Service ** START ** Service: Service startup
2009-11-19 12:07:46:486 1092 414 Service *********
2009-11-19 12:07:46:486 1092 414 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.1.6001.65\wups.dll"
2009-11-19 12:07:46:549 1092 414 Agent   * WU client version 7.1.6001.65
2009-11-19 12:07:46:549 1092 414 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-19 12:07:46:549 1092 414 Agent   * Access type: No proxy
2009-11-19 12:07:46:549 1092 414 Agent   * Network state: Connected
2009-11-19 12:07:49:455 1328 784 Setup *********
2009-11-19 12:07:49:455 1328 784 Setup ** END ** Setup: Installing client binaries
2009-11-19 12:07:49:455 1328 784 Setup *************
2009-11-19 12:07:49:455 1328 784 Setup wusetup has finished. Exit code is 0. Reboot is NOT needed
2009-11-19 12:08:31:564 1092 414 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-11-19 12:08:31:564 1092 414 Agent *********** Agent: Initializing global settings cache ***********
2009-11-19 12:08:31:564 1092 414 Agent   * WSUS server: http://clientupdate.int.chickasaw.net
2009-11-19 12:08:31:564 1092 414 Agent   * WSUS status server: http://clientupdate.int.chickasaw.net
2009-11-19 12:08:31:564 1092 414 Agent   * Target group: (Unassigned Computers)
2009-11-19 12:08:31:564 1092 414 Agent   * Windows Update access disabled: No
2009-11-19 12:08:33:408 1092 414 DnldMgr Download manager restoring 0 downloads
2009-11-19 12:08:33:439 1092 414 AU ########### AU: Initializing Automatic Updates ###########
2009-11-19 12:08:33:455 1092 414 AU   # AU disabled through Policy
2009-11-19 12:08:33:455 1092 414 AU AU finished delayed initialization
2009-11-19 12:08:33:455 1092 414 Report *********** Report: Initializing static reporting data ***********
2009-11-19 12:08:33:455 1092 414 Report   * OS Version = 5.1.2600.2.0.65792
2009-11-19 12:08:33:471 1092 414 Report   * Computer Brand = LENOVO
2009-11-19 12:08:33:471 1092 414 Report   * Computer Model = 9964A5U
2009-11-19 12:08:33:471 1092 414 Report   * Bios Revision = 5CKT51AUS
2009-11-19 12:08:33:471 1092 414 Report   * Bios Name = Lenovo ThinkCentre BIOS Ver 5CKT51.0
2009-11-19 12:08:33:471 1092 414 Report   * Bios Release Date = 2009-07-23T00:00:00
2009-11-19 12:08:33:471 1092 414 Report   * Locale ID = 1033
2009-11-19 12:11:58:205 1092 414 AU AU received policy change subscription event
2009-11-19 12:11:58:924 1092 414 AU AU received policy change subscription event
2009-11-19 12:11:59:455 1092 414 AU AU received policy change subscription event
2009-11-19 15:13:07:438 1092 414 AU AU received policy change subscription event
2009-11-19 15:23:07:905 1092 414 AU AU received policy change subscription event
2009-11-19 22:08:29:091 1092 414 AU AU received policy change subscription event
2009-11-19 23:42:06:373 1092 414 AU AU received policy change subscription event
2009-11-20 03:21:45:324 1092 414 AU ########### AU: Uninitializing Automatic Updates ###########
2009-11-20 03:21:45:339 1092 414 Service *********
2009-11-20 03:21:45:339 1092 414 Service ** END ** Service: Service exit [Exit code = 0x240001]
2009-11-20 03:21:45:339 1092 414 Service *************
2009-11-20 11:03:47:487 468 1a8 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-20 11:03:47:487 468 1a8 Misc   = Process: C:\WINDOWS\Explorer.EXE
2009-11-20 11:03:47:487 468 1a8 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-20 11:03:47:487 468 1a8 Shutdwn Install at shutdown: no updates to install
2009-11-20 11:03:47:487 468 1a8 Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=80240FFF
2009-11-20 11:03:53:178 692 500 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-20 11:03:53:178 692 500 Misc   = Process: \??\C:\WINDOWS\system32\winlogon.exe
2009-11-20 11:03:53:178 692 500 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-20 11:03:53:178 692 500 Shutdwn FATAL: WUAutoUpdateAtShutdown failed, hr=80240FFF
2009-11-20 11:04:53:031 1080 6d4 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-20 11:04:53:046 1080 6d4 Misc   = Process: C:\WINDOWS\System32\svchost.exe
2009-11-20 11:04:53:046 1080 6d4 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-20 11:04:53:031 1080 6d4 Service *************
2009-11-20 11:04:53:046 1080 6d4 Service ** START ** Service: Service startup
2009-11-20 11:04:53:046 1080 6d4 Service *********
2009-11-20 11:04:53:234 1080 6d4 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups.dll"
2009-11-20 11:04:54:421 1080 6d4 Agent   * WU client version 7.1.6001.65
2009-11-20 11:04:54:421 1080 6d4 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-20 11:04:54:468 1080 6d4 Agent   * Access type: No proxy
2009-11-20 11:04:54:468 1080 6d4 Agent   * Network state: Connected
2009-11-20 11:04:54:859 1080 6d4 Agent FATAL: fail to register class object 0x80004015
2009-11-20 11:04:54:859 1080 6d4 Agent FATAL: Client call recorder fails to init with error 0x80004015
2009-11-20 11:04:54:859 1080 6d4 Agent   * FATAL: Failed to initialize with error 0x80004015 from component Agent
2009-11-20 11:04:54:859 1080 6d4 Service FATAL: Failed to initialize WU client: 0x80004015
2009-11-20 11:04:54:906 1080 6d4 Service *********
2009-11-20 11:04:54:906 1080 6d4 Service ** END ** Service: Service exit [Exit code = 0x80004015]
2009-11-20 11:04:54:906 1080 6d4 Service *************
2009-11-20 11:23:44:774 1080 670 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-20 11:23:44:774 1080 670 Misc   = Process: C:\WINDOWS\System32\svchost.exe
2009-11-20 11:23:44:774 1080 670 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-20 11:23:44:774 1080 670 Service *************
2009-11-20 11:23:44:774 1080 670 Service ** START ** Service: Service startup
2009-11-20 11:23:44:774 1080 670 Service *********
2009-11-20 11:23:44:774 1080 670 Agent   * WU client version 7.1.6001.65
2009-11-20 11:23:44:774 1080 670 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-20 11:23:44:774 1080 670 Agent   * Access type: No proxy
2009-11-20 11:23:44:774 1080 670 Agent   * Network state: Connected
2009-11-20 11:23:44:774 1080 670 Agent FATAL: fail to register class object 0x80004015
2009-11-20 11:23:44:774 1080 670 Agent FATAL: Client call recorder fails to init with error 0x80004015
2009-11-20 11:23:44:774 1080 670 Agent   * FATAL: Failed to initialize with error 0x80004015 from component Agent
2009-11-20 11:23:44:774 1080 670 Service FATAL: Failed to initialize WU client: 0x80004015
2009-11-20 11:23:44:774 1080 670 Service *********
2009-11-20 11:23:44:774 1080 670 Service ** END ** Service: Service exit [Exit code = 0x80004015]
2009-11-20 11:23:44:774 1080 670 Service *************
2009-11-20 11:35:25:398 1080 468 Misc =========== Logging initialized (build: 7.1.6001.65, tz: -0600) ===========
2009-11-20 11:35:25:398 1080 468 Misc   = Process: C:\WINDOWS\System32\svchost.exe
2009-11-20 11:35:25:398 1080 468 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-20 11:35:25:398 1080 468 Service *************
2009-11-20 11:35:25:398 1080 468 Service ** START ** Service: Service startup
2009-11-20 11:35:25:398 1080 468 Service *********
2009-11-20 11:35:25:414 1080 468 Agent   * WU client version 7.1.6001.65
2009-11-20 11:35:25:414 1080 468 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-20 11:35:25:414 1080 468 Agent   * Access type: No proxy
2009-11-20 11:35:25:414 1080 468 Agent   * Network state: Connected
2009-11-20 11:36:10:510 1080 468 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-11-20 11:36:10:510 1080 468 Agent *********** Agent: Initializing global settings cache ***********
2009-11-20 11:36:10:510 1080 468 Agent   * WSUS server: http://clientupdate.int.chickasaw.net
2009-11-20 11:36:10:510 1080 468 Agent   * WSUS status server: http://clientupdate.int.chickasaw.net
2009-11-20 11:36:10:510 1080 468 Agent   * Target group: (Unassigned Computers)
2009-11-20 11:36:10:510 1080 468 Agent   * Windows Update access disabled: No
2009-11-20 11:36:11:651 1080 468 DnldMgr Download manager restoring 0 downloads
2009-11-20 11:36:11:682 1080 468 AU ########### AU: Initializing Automatic Updates ###########
2009-11-20 11:36:11:682 1080 468 AU   # AU disabled through Policy
2009-11-20 11:36:11:682 1080 468 AU AU finished delayed initialization
2009-11-20 11:36:11:682 1080 468 Report *********** Report: Initializing static reporting data ***********
2009-11-20 11:36:11:682 1080 468 Report   * OS Version = 5.1.2600.2.0.65792
2009-11-20 11:36:11:698 1080 468 Report   * Computer Brand = LENOVO
2009-11-20 11:36:11:698 1080 468 Report   * Computer Model = 9964A5U
2009-11-20 11:36:11:698 1080 468 Report   * Bios Revision = 5CKT51AUS
2009-11-20 11:36:11:698 1080 468 Report   * Bios Name = Lenovo ThinkCentre BIOS Ver 5CKT51.0
2009-11-20 11:36:11:698 1080 468 Report   * Bios Release Date = 2009-07-23T00:00:00
2009-11-20 11:36:11:698 1080 468 Report   * Locale ID = 1033
2009-11-20 11:45:59:939 1080 468 AU AU received policy change subscription event
2009-11-20 11:46:02:689 1080 468 AU AU received policy change subscription event
2009-11-20 11:46:18:409 1080 468 AU AU received policy change subscription event

Software updates stuck in state of "downloading updates". Errors found in windowsupdate.log

Thu, 19 Nov 2009 20:31:57 Z

I've been trying to roll out November updates to XP clients since patch tuesday. All of my clients are stuck in the "downloading updates" state. I've searched through tons of threads on here for that issue, and none seem to apply to my situation. The only errors/problems I can find are in my windowsupdate.log, and when googling the error I can't find any help in resolving it. Here's an excerpt from my log:

2009-11-19    14:03:27:877    872    8500    PT    WARNING: Cached cookie has expired or new PID is available
2009-11-19    14:03:27:877    872    8500    PT    Initializing simple targeting cookie, clientId = d8556c3a-eb55-4ce5-b30b-2725a97c3d79, target group = Servers, DNS name = rttmoccm.republictitle.local
2009-11-19    14:03:27:877    872    8500    PT    Server URL = http://rttmosus/SimpleAuthWebService/SimpleAuth.asmx
2009-11-19    14:03:27:908    872    8500    PT    WARNING: GetAuthorizationCookie failure, error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status code = 403
2009-11-19    14:03:27:908    872    8500    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x80244018
2009-11-19    14:03:27:908    872    8500    PT    WARNING: PopulateAuthCookies failed: 0x80244018
2009-11-19    14:03:27:908    872    8500    PT    WARNING: RefreshCookie failed: 0x80244018
2009-11-19    14:03:27:908    872    8500    PT    WARNING: RefreshPTState failed: 0x80244018
2009-11-19    14:03:27:908    872    8500    PT    WARNING: PTError: 0x80244018
2009-11-19    14:03:27:908    872    8500    Report    WARNING: Reporter failed to upload events with hr = 80244018.

Any help in resolving this issue would be greatly appreciated.

Thanks in advance!