WSUS Forum

Updates Will Not Install

Mon, 23 Nov 2009 14:56:32 Z

I administer WSUS 3.0 in a Win2003 domain. We have 75% XP workstations the remaining are Win2000 SP4.

In the latest application of updates the XP machines are showing on the WSUS console as needing 6 updates. Yet the workstations themselves do not show that any updates are needed. I have checked the updates on the WSUS console to see if there are some that are not approved. There are none.

I don't understand what is going on. How can you have updates required on a workstation yet do not show on the workstation and all updates approved for install??

Interference

Mon, 23 Nov 2009 15:10:06 Z

About 2 years ago I installed WSUS 2.0 in a Win2003 domain with a mix of XP and 2000 workstations. Ten servers were all Win2003 R2. The system worked well.

I left for about a year and recently returned. During my absence the new folks did not keep the servers and workstations updated. Many were 50-60 updates behind. They also installed management software specfically ScriptLogic and Spiceworks.

Recently the update process has been a nightmare. I am now using WSUS 3.0. I have group policy to use option 4 for the workstations to download and install automatically. The servers use option 3 to download and manual install. Some of the workstations mainly Win2000 work the way they should. Many of the XP machines do not. They are set for option 4 but work like they have been set to option 3. Two of the servers on the otherhand are set to option 3 but work like they use option 4 restarting without warning.

The final problem was the update on an Exchange server prevented the server from booting. We could only boot by pulling the network cable and then we could not get the key Exchanges services to start.

It is my opinion that there is some serious and very damaging interference going on by the new management software being used. But I don't know what to look at or what to do about getting the update service to run like it used to.

I need some ideas.

definition updates for forefront client security showing failed status on windows 7 clients

Thu, 19 Nov 2009 21:46:16 Z

we have ~9000 clients reporting to our wsus 3 sp2 server, of which only a few (17) are windows 7. what's curious is that 50% of those win7 computers are showing failed status for forefront client security definition updates. in researching this problem i've discovered that none of the win7 computers with failed status even have fcs installed... which begs the question; why are the definition updates even being attempted on this handful of systems?

Some updates not installing - no errors in console

Tue, 24 Nov 2009 21:49:18 Z

I have 3 XP clients that some updates are not installing on after I approved them over a week ago. 2 of the clients have the same 3 Office 2003 updates and all 3 clients have the same 2 XP updates. The WSUS console does not show any errors. The status simply shows "Not Installed".

I've never seen this before since if updates did not install, the clients showed them in the WSUS console as failing.

I can't think of how to proceed to find a solution as I've done everything I can think of. If you have any ideas on what to do next, please let me know.

JL

force reboot after x days

Wed, 25 Nov 2009 12:58:31 Z

Hi All,

i am working on re-configuring our WSUS setup & was wondering if its possible to do the following:

we currently auto schedule installation of updates (option 4) daily.

1) give users the ability to delay any reboots.
2) if users keep delaying the reboots, then after x days the reboot if forced.

is this possible with WSUS or do we need another product? (shavlik?)

Thanks

Kass

KB968930 failing to install

Tue, 24 Nov 2009 17:10:54 Z

I had 23 updates failing to install saying "Updates not configured properly, Reverting changes". From initial research into error logs and codes, it seems KB968930 is causing the failures. I found that on the client machines, if I select just this update, it will install OK. I can then install all other updates as well. It also works if I select all updates but this one first and install them, they go through. If I then install just KB968930 it work as well. Seems it doesn't like to be in a group of updates?

Anyway the thing is: The updates current status is Approved for Install. I am under the impression that if I now decline this update, will it not install itself (even if already downloaded locally to the client). Is that correct?

How can I best resolve this problem please?
Thanks in advance for the help,
Ryek

List of supported software

Wed, 25 Nov 2009 12:38:15 Z

Does anybody have a list with all te microsoft products that WSUS keeps up to date.

WSUS EVENT ID: 364

Wed, 25 Nov 2009 04:25:02 Z

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Synchronization
Event ID: 364
Date:  11/20/2009
Time:  2:28:49 PM
User:  N/A
Computer: MICROPRODUCT
Description:
Content file download failed. Reason: The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.
Source File: /msdownload/update/software/defu/2009/11/mpam-fe_bd_bfaab82af6344bba688fcadfd6c8d8fd669a8a43.exe Destination File: c:\WSUS\WsusContent\43\BFAAB82AF6344BBA688FCADFD6C8D8FD669A8A43.exe.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Since last month, I have been facing this issue. Thought the issue must be with the firewall but as I change the server's IP, WSUS will start downloading updates & the clients will also get updated. Again after 1 or 2 days, the event viewer will show up the above message again. All the updates will have red cross or the warning icons. What actually could be the reason for this ?

Clients connecting to WSUS are missing in WSUS MMC

Mon, 23 Nov 2009 07:58:32 Z

Dear all,

regarding to the MMC we've WSUS 3.1.6001.65 up and running on a W2K3 R2 DataCenter Edition w/ SP2. Updates are being downloaded and deployed throughout the environment successfully.

Unfortunately some of my servers which successfully connect to my WSUS and receive updates are not being displayed under the Computer nodes in the WSUS MMC. They are missing.

What can I do to add them to the WSUS MMC and their corresponding administrative groups?

Regards
Alex

iis windows closed when properties accessing in iis 6 on windows server 2003

Wed, 25 Nov 2009 16:52:59 Z

Hi,

i am running windows server 2003 on my machine. i have installed iis 6 on that server. problem is -- when i right click on web sites folder -> properties. then iis window closed.
i have deployed asp.net application also on the same application server. it is running fine. so i think it is not related to iis server. i also tried to access other computer iis on my machine. it is doing same (closed window if i click on properties on any website in iis). i have reinstall also iis but problem is same.

Thanks,
Gaurav

Superseded Updates question

Mon, 23 Nov 2009 20:45:52 Z

I am having a hard time understanding why we would need to keep superseded updates on our server, even if some of the updates are only on 80% of the clients. If an update is superseded then the new update should patch everything that the superseded update would of had, correct?

We have a lot of updates that have been approved for 3 - 4 months and have had enough time to patch to the computers that need patching, but are still sitting at 80 - 90%, is there any reason we need to keep these updates as approved. But, even if a computer needed a superseded update that was deleted prematurely, wouldn't the superseding patch once it applied, patch it up to 100%?

In my mind if we decline a superseded update, and say we put a new computer on the domain and it contacts WSUS, then it would just download the superseding update.

I hope my questions makes sense?

WSUS Updates Overview all showing with no status.

Tue, 26 May 2009 16:24:15 Z

I've noticed today on the WSUS console that under the Update Overview section, 2,574 updates are showing with no status.

All Updates
With Errors: 31
Needed: 145
Installed/Applicable is greyed out, and is zero.
No Status: 2574

On the Computer Overview section, they are showing up mostly correct.

All Computers
With Errors: 18
Needing Updates: 116
Installed/No Applicable: 272
No Status: 157

So what's going on with the WSUS server?

WSUS - Random offset getting MS updates

Tue, 24 Nov 2009 02:39:40 Z

By GPO I have set up the WU client to install whatever updates are ready at 3:00 PM every day. However it turns out that the patch was installed at 3:20 PM instead of being installed at 3:00 PM. I think this behaviour is expected by the WSUS design...

1.)Can someone clarify that and provide and provide a MS article where this is explained.
2.)I wonder if there is any way to determine/know when are the updates going to be installed? Would they every be experience a delay bigger than 1 hour on servers that have a regular peformance?

Thank you.

what will happen if WSUS is down and clients cannot find it over the network?

Wed, 25 Nov 2009 01:26:37 Z

Guys

what will happen if WSUS is down and clients cannot find it over the network? will all clients go to internet to get updates? or they just stop ?

thanks

in adv.

IE8 Deployed with WSUS

Mon, 02 Nov 2009 20:07:02 Z

IE 8 and 7 were deployed in our network by WSUS prior to my arrival. This was done by accident by a prior admin. Corporate has not authorized the move to IE 8. I would like to know the following:

1) Can IE8 be mass removed?
2) If IE8 cannot be mass removed and the subsequent updates have been declined can they be restored?

We have an audit coming up and network scans are showing vulnerable systems because of IE8 updates. IF I have no other choice but to install these I guess that is that.

Thanks.

WSUS 3.0 SP2 / XP Pro SP3 Update fails 0x80190194

Tue, 24 Nov 2009 02:12:06 Z

Hello,

I'm running WSUS 3.0 SP2 on a 2008 Server x64. I'm receiving the error 0x80190194 when I run the client diagnostic tool on the mentioned XP Workstation. Here is the relevant information. Server is located on alternate site http://servername:8530. Port 8530 is open. I can download the wuident.cab file by going to http://servername:8530/selfupdate/wuident.cab from the workstation. I have made sure the selfupdate virtual directory exists on my WSUS servers IIS website configuration.

I have also reset the windows update on the workstation. I have visited the windows update site directly to make sure I have the latest WU client installed. I CAN see updates from the MS Update page. I have run wuauclt /detectnow /resetauthorization.

Here are some log files:

From the workstation:
{33AF909F-6DA9-431D-B666-80D921CF7373}    2009-11-23 17:46:11:997-0600    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
{F44A1A1B-6911-4602-8C23-9B17007F4977}    2009-11-23 17:53:52:798-0600    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
{0BEEF43D-F0A0-49E6-9E58-D6808113FB03}    2009-11-23 17:53:52:798-0600    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
{A9776CB2-1EDC-46C4-8E6D-9C03F1A79A7E}    2009-11-23 17:56:24:211-0600    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
{E94D561C-CE46-40B8-8D7C-5F9805033072}    2009-11-23 17:56:24:211-0600    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.

Note above the Updatelog in c:\windows\softwaredistrubution shows the client seeing 0 updates? This client has over 25 updates to install. I've verified this.

when I use the diagnostic tool I get the message: WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL, &downloadBuffer) failed with hr=0x80190194

Yet, as I've stated I've ensured I can contact the WSUS server and download the .cab file.

Here are the AU registry settings from the client:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"="http://servername:8530"
"WUStatusServer"="http://servername:8530"
"TargetGroup"="MyGroup"
"TargetGroupEnabled"=dword:00000001
"ElevateNonAdmins"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"IncludeRecommendedUpdates"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000000
"RescheduleWaitTimeEnabled"=dword:00000001
"RescheduleWaitTime"=dword:00000004
"AUPowerManagement"=dword:00000001
"UseWUServer"=dword:00000001
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000004
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000012
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RebootRelaunchTimeout"=dword:00000018
"RebootWarningTimeoutEnabled"=dword:00000001
"RebootWarningTimeout"=dword:0000001e
"AutoInstallMinorUpdates"=dword:00000000
"DetectionFrequency"=dword:00000016
"DetectionFrequencyEnabled"=dword:00000001

Please note: servername and mygroup are not what is actually present, I've changed that because...I'm paranoid I guess.
I've also uninstalled and reinstalled the WSUS server and therefore recreated the WSUS website in IIS and then verified again that the \selfupdate directory existed and allows Anonymous Logon.

At this stage does anyone have any good guesses?

Error when WSUS try to import new updates from MU Catalog

Mon, 16 Nov 2009 17:26:46 Z

Hello,
I have WSUS 3, everything perfect one week ago, but now when I try to import updates from MU catalog, this error appears:

[Error number: 80131509]

The following are common causes and solutions for this issue:

If you use a proxy, be sure that it is the same proxy being used by your Windows Server Update Services (WSUS) server. Your WSUS server might not be configured correctly. Contact your WSUS administrator.

My company sends me every month a list with de updates that I have to install in the workstations, that's why I use the MU Catalog instead Synchronization.
I already check the proxy settings, all is correct.

update for root certificates [september2009] (kb931125)

Thu, 22 Oct 2009 09:37:34 Z

I m using WSUS for deploying updates, many of windows XP workstations keep asking to reinstall the root certificate kb931125, and the report in WSUS said it's either installed on some PCs or downloaded on the others.
any idea to solve the problem?

thank you.

Renaming the WSUS Server

Tue, 24 Nov 2009 18:10:14 Z

We support multiple environments that are both not connected to the Internet and not connected to one another. We would like to do the following:

1. Setup a WSUS server (virtual server) on an Internet connected network as a non-domain joined machine
2. Synch it with Microsoft
3. Make a copy of the virtual machine
4. Place a copy of that virtual machine on each of the disconnected networks (it will have a unique name on each network)
5. Set the WSUS server on each of the disconnected networks to not synch with Microsoft or an upstream server
6. Continue to get new updates on the Internet connected server
7. Export the new updates from the Internet connected server and then import into the WSUS servers on each network

Are there any issues we are going to run into doing this that cannot be resolved? Specifically around make a copy of the VM and then renaming.

Wsus errors 12002, 12012, 12032, 12022, 12032, 12042, 12052

Tue, 29 Sep 2009 20:18:51 Z

I am trying to run WSUS 3 SP2, but am having problems. I have clean loaded both 2003 Standard, as well as enterprise 2003 with all the latest service packs. I load WSUS SP2, and get everything working through the console. Everything works fine, until I reboot the server, as which time I get the 12002, 12012, 12032, 12022, 12042, and 12052 errors. Once I get those errors, I can't get into the admin console, althought the update services service is running. I can still see the the proper folder structure in IIS, and I have verified the IIS permissions on the folders. Any ideas?

WSUS can not see it`s computers

Tue, 24 Nov 2009 09:35:44 Z

Hi , i wish to recieve a help & thanks so so so much , after reinstalling the wsus server it works good except an important thing ( WSUS can not see the computers which was connected to it ) but WSUS can see & connect to the new computers to the wan

Update keeps installing itself

Tue, 14 Jul 2009 06:35:34 Z

The update: KB931125, keeps trying to install itself on my clients (already have 4 clients wit this). The attached report is from my test machine, where I am logged as the domain admin.
Every time I click install, nothing happens, and I get the same update in the ready to install list.

Anyone?

2009-07-13 14:59:28:818 1044 110 Report REPORT EVENT: {8AFD8234-DEFF-4A79-81B5-C841971B232D} 2009-07-13 14:59:23:818+0300 1 183 101 {D24FE7DE-266B-4260-BBF2-59824AF246CF} 101 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Root Certificates Update
2009-07-13 14:59:28:818 1044 110 Report REPORT EVENT: {63984E57-F348-46DF-B667-2B070F4FE245} 2009-07-13 14:59:26:880+0300 1 189 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions: - Update for Root Certificates [May 2009] (KB931125)

Como instalo la consola en un equipo XP

Sat, 14 Nov 2009 06:24:49 Z

Instalé la consola en un equipo con XP, pero al querer conectarme a un servidor que tiene el administrador del Wsus me dá error.

WSUS 3.0 SP1 Client Update Failure

Tue, 24 Nov 2009 06:28:12 Z

Dear Sirs,

i am now suffering a problem with WSUS while clients cannot get update from from the server, it is not a domain environment and firewall is turned off, local machine log is as below, what would the reason probably be? Thanks.

2009-11-24 14:03:43:781 1260 d20 Report Uploading 4 events using cached cookie, reporting URL = http://192.168.2.1/ReportingWebService/ReportingWebService.asmx
2009-11-24 14:03:43:781 1260 d20 PT WARNING: ReportEventBatch failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2009-11-24 14:03:43:781 1260 d20 PT WARNING: SOAP Fault: 0x00012c
2009-11-24 14:03:43:781 1260 d20 PT WARNING:     faultstring:Fault occurred
2009-11-24 14:03:43:781 1260 d20 PT WARNING:     ErrorCode:ConfigChanged(2)
2009-11-24 14:03:43:781 1260 d20 PT WARNING:     Message:(null)
2009-11-24 14:03:43:781 1260 d20 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
2009-11-24 14:03:43:781 1260 d20 PT WARNING:     ID:84f57ad5-46e6-47eb-b717-8772c5580c02
2009-11-24 14:03:43:781 1260 d20 Report WARNING: Reporter failed to upload events with hr = 8024400d.
2009-11-24 14:04:45:765 1260 6cc AU ########### AU: Uninitializing Automatic Updates ###########
2009-11-24 14:04:45:796 1260 6cc Service *********
2009-11-24 14:04:45:796 1260 6cc Service ** END ** Service: Service exit [Exit code = 0x240001]
2009-11-24 14:04:45:796 1260 6cc Service *************
2009-11-24 14:04:54:171 1260 dec Misc =========== Logging initialized (build: 7.1.6001.65, tz: +0800) ===========
2009-11-24 14:04:54:171 1260 dec Misc   = Process: C:\WINDOWS\System32\svchost.exe
2009-11-24 14:04:54:171 1260 dec Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-24 14:04:54:171 1260 dec Service *************
2009-11-24 14:04:54:171 1260 dec Service ** START ** Service: Service startup
2009-11-24 14:04:54:171 1260 dec Service *********
2009-11-24 14:04:54:171 1260 dec Agent   * WU client version 7.1.6001.65
2009-11-24 14:04:54:171 1260 dec Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-24 14:04:54:171 1260 dec Agent   * Access type: No proxy
2009-11-24 14:04:54:171 1260 dec Agent   * Network state: Connected
2009-11-24 14:05:05:281 1256 498 Misc =========== Logging initialized (build: 7.1.6001.65, tz: +0800) ===========
2009-11-24 14:05:05:281 1256 498 Misc   = Process: C:\WINDOWS\system32\wuauclt.exe
2009-11-24 14:05:05:281 1256 498 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-24 14:05:05:281 1256 498 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2009-11-24 14:05:05:281 1256 498 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2009-11-24 14:05:05:281 1260 d18 Agent WARNING: Failed to read the service id for re-registration 0x80070002
2009-11-24 14:05:05:281 1260 d18 Agent WARNING: Missing service entry in the backup data store; cleaning up
2009-11-24 14:05:05:281 1260 d18 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-11-24 14:05:05:281 1260 dec Agent Created new random SusClientId 59b7501b-b6f1-4bb8-ba71-45af11ca63cc. Old Id: none.
2009-11-24 14:05:05:281 1260 d18 Agent *********** Agent: Initializing global settings cache ***********
2009-11-24 14:05:05:281 1260 dec Report *********** Report: Initializing static reporting data ***********
2009-11-24 14:05:05:281 1260 d18 Agent   * WSUS server: http://192.168.2.1
2009-11-24 14:05:05:281 1260 dec Report   * OS Version = 5.1.2600.2.0.65792
2009-11-24 14:05:05:281 1260 d18 Agent   * WSUS status server: http://192.168.2.1
2009-11-24 14:05:05:281 1260 d18 Agent   * Target group: (Unassigned Computers)
2009-11-24 14:05:05:281 1260 d18 Agent   * Windows Update access disabled: No
2009-11-24 14:05:05:281 1260 d18 DnldMgr Download manager restoring 0 downloads
2009-11-24 14:05:05:281 1260 d18 AU ########### AU: Initializing Automatic Updates ###########
2009-11-24 14:05:05:281 1260 d18 AU   # WSUS server: http://192.168.2.1
2009-11-24 14:05:05:281 1260 d18 AU   # Detection frequency: 22
2009-11-24 14:05:05:281 1260 d18 AU   # Approval type: Scheduled (Policy)
2009-11-24 14:05:05:281 1260 d18 AU   # Scheduled install day/time: Every day at 13:00
2009-11-24 14:05:05:281 1260 d18 AU   # Auto-install minor updates: Yes (Policy)
2009-11-24 14:05:05:281 1260 d18 AU   # Will interact with non-admins (Non-admins are elevated)
2009-11-24 14:05:05:296 1260 d18 AU Setting AU scheduled install time to 2009-11-25 05:00:00
2009-11-24 14:05:05:296 1260 d18 AU AU finished delayed initialization
2009-11-24 14:05:05:296 1260 d18 AU Triggering AU detection through DetectNow API
2009-11-24 14:05:05:296 1260 d18 AU Triggering Online detection (non-interactive)
2009-11-24 14:05:05:328 1260 dec Report   * Computer Brand = Hewlett-Packard
2009-11-24 14:05:05:328 1260 dec Report   * Computer Model = HP xw4600 Workstation
2009-11-24 14:05:05:328 1260 dec Report   * Bios Revision = 786F3 v01.13
2009-11-24 14:05:05:328 1260 dec Report   * Bios Name = Default System BIOS
2009-11-24 14:05:05:328 1260 dec Report   * Bios Release Date = 2008-06-25T00:00:00
2009-11-24 14:05:05:328 1260 dec Report   * Locale ID = 1041
2009-11-24 14:05:05:328 1260 dec AU #############
2009-11-24 14:05:05:328 1260 dec AU ## START ## AU: Search for updates
2009-11-24 14:05:05:328 1260 dec AU #########
2009-11-24 14:05:05:328 1260 dec AU <<## SUBMITTED ## AU: Search for updates [CallId = {0B3DCFBD-1CFE-481E-B6D0-C50BA5C2E0ED}]
2009-11-24 14:05:05:328 1260 e3c Report WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{6B658B71-47BB-4432-BE2A-74C515685C3F}.bin for reading with hr = 80070002.
2009-11-24 14:05:05:328 1260 e3c Agent *************
2009-11-24 14:05:05:328 1260 e3c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-11-24 14:05:05:328 1260 e3c Agent *********
2009-11-24 14:05:05:328 1260 e3c Agent   * Online = Yes; Ignore download priority = No
2009-11-24 14:05:05:328 1260 e3c Agent   * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2009-11-24 14:05:05:328 1260 e3c Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-11-24 14:05:07:593 1260 e3c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2009-11-24 14:05:07:593 1260 e3c Misc Microsoft signed: Yes
2009-11-24 14:05:07:609 1260 e3c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2009-11-24 14:05:07:625 1260 e3c Misc Microsoft signed: Yes
2009-11-24 14:05:07:625 1260 e3c Setup *********** Setup: Checking whether self-update is required ***********
2009-11-24 14:05:07:625 1260 e3c Setup   * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0411\wuapi.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0804\wuapi.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0411\wuaucpl.cpl.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0804\wuaucpl.cpl.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0411\wuaueng.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0804\wuaueng.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0411\wucltui.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\MUI\FALLBACK\0804\wucltui.dll.mui: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.1.6001.65, required version = 7.1.6001.65
2009-11-24 14:05:07:625 1260 e3c Setup   * IsUpdateRequired = No
2009-11-24 14:05:07:687 1260 e3c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2009-11-24 14:05:07:687 1260 e3c PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.2.1/ClientWebService/client.asmx
2009-11-24 14:05:07:687 1260 e3c Agent Switching to hardware-verified ClientId.
2009-11-24 14:05:07:718 1260 e3c PT WARNING: Cached cookie has expired or new PID is available
2009-11-24 14:05:07:781 1260 e3c Agent Created new random SusClientId 1e062dd7-e23c-4295-bd35-0d9169432852. Old Id: 59b7501b-b6f1-4bb8-ba71-45af11ca63cc.
2009-11-24 14:05:07:781 1260 e3c PT Initializing simple targeting cookie, clientId = 1e062dd7-e23c-4295-bd35-0d9169432852, target group = , DNS name = sehcadroom-001
2009-11-24 14:05:07:781 1260 e3c PT   Server URL = http://192.168.2.1/SimpleAuthWebService/SimpleAuth.asmx
2009-11-24 14:06:02:937 1260 e3c PT WARNING: Exceeded max server round trips: 0x80244010
2009-11-24 14:06:02:937 1260 e3c PT WARNING: Sync of Updates: 0x80244010
2009-11-24 14:06:02:937 1260 e3c PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
2009-11-24 14:06:02:937 1260 e3c Agent   * WARNING: Failed to synchronize, error = 0x80244010
2009-11-24 14:06:02:953 1260 e3c Agent   * WARNING: Exit code = 0x80244010
2009-11-24 14:06:02:953 1260 e3c Agent *********
2009-11-24 14:06:02:953 1260 e3c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-11-24 14:06:02:953 1260 e3c Agent *************
2009-11-24 14:06:02:953 1260 e3c Agent WARNING: WU client failed Searching for update with error 0x80244010
2009-11-24 14:06:02:953 1260 550 AU >>## RESUMED ## AU: Search for updates [CallId = {0B3DCFBD-1CFE-481E-B6D0-C50BA5C2E0ED}]
2009-11-24 14:06:02:953 1260 550 AU   # WARNING: Search callback failed, result = 0x80244010
2009-11-24 14:06:02:953 1260 550 AU   # WARNING: Failed to find updates with error code 80244010
2009-11-24 14:06:02:953 1260 550 AU #########
2009-11-24 14:06:02:953 1260 550 AU ## END ## AU: Search for updates [CallId = {0B3DCFBD-1CFE-481E-B6D0-C50BA5C2E0ED}]
2009-11-24 14:06:02:953 1260 550 AU #############
2009-11-24 14:06:02:953 1260 550 AU AU setting next detection timeout to 2009-11-24 11:06:02
2009-11-24 14:06:02:953 1260 550 AU Setting AU scheduled install time to 2009-11-25 05:00:00
2009-11-24 14:06:07:953 1260 e3c Report REPORT EVENT: {353856AB-592F-4ED6-898F-6C7009804AC5} 2009-11-24 14:06:02:953+0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244010.

Best Regards,
Sariel Leung

WSUS Best Practices

Wed, 11 Nov 2009 09:39:39 Z

Hi,

I just setup WSUS on my server which means they now get the all the Microsoft updates from the server. I want to know what is the common thing to do if you have 20% on your users using notebook and travels occationally. If they go out for 2 weeks then they might be at risk if their OS is unpatched. So my question is this:

1. Is there a way I can have a toggle between WSUS and Microsoft server?
2. If not, have a secondary download location which is Microsoft? but the policy of which update to install will retain.
3. If answer to 1 and 2 is no, then what is the best solution for this scenario.

I am sure this is a common scenario, I just dont know what is the best solution for this.

Thanks in advanced!
Lex

WSUS Updates

Mon, 23 Nov 2009 20:55:02 Z

I just setup a WSUS server on a small network here at work. There is about 17 
Windows XP Pro pc's and 4 Widows 2003 Servers. I have all my approved updates 
installed and working. If I cleanup the WSUS database of declined updates and 
later on I bring a new PC or Server online that needs some of the updates I 
declined will the new box tell the WSUS server that it what updates it needs 
and the WSUS server will download them? Or do I have to start over anf 
download all the updates again?
-- 
Marty

DnldMgr Error 0x80072efd on clients

Wed, 01 Jul 2009 19:54:58 Z

I recently rebuilt our WSUS since it was storing the updates locally and running out of disk space. I built the new one using Windows Server 2008 (64-bit) and am storing the updates on a SQL 2005 cluster. Things seemed to be going well for a while, but then I noticed that few (if any) of the servers were showing a status of 100% (currently 2/119). Looking deeper, I checked the WindowsUpdate log on some of the hosts. Nearly all of them have this line:

DnldMgr Error 0x80072efd occurred while downloading update; notifying dependent calls.

They just loop all day in this state. When I RDP to one of the hosts, the WSUS client will show that it's Downloading Updates, but the progress never gets past 0%. That will eventually go away but then return later.

Searching for this error returned results stating that the client couldn't contact the WSUS server. I'm using the IP address of the WSUS host in the configuration, so that rules out DNS. Also not using SSL, so that rules out certificates. If I open IE and browse to the IP address of the WSUS host, it displays the page. So it's only the WSUS client that can't contact the host, or WSUS is returning something that the client doesn't like.

The application and system logs on the WSUS host don't lend much help. The application log gives me this useless information:

Client computers are installing updates with a higher than 25 percent failure rate. This is not normal.

The system log just has endless events like this:

The Windows Modules Installer service entered the running state.

Both have event ID 7036. Happens every 10 minutes...kind of like clockwork.

On the client side, I've tried all the tricks. Stopping the update service, deleting SoftwareDistribution, re-registering dlls, /resetauthorization /detectnow, etc, etc. None have shown a consistent pattern. I was also wishing that each of the 119 servers wouldn't need attention and I could fix this at the source (WSUS). At this point, I'll even log into each if I have to.

Other notes...

Disabled the firewall on the WSUS host. Uninstalled McAfee ViruScan. I see lots of happy 200 status in the W3C logs.

Any help to get WSUS back into a usable state is appreciated. Let me know if there are other logs/info you'd like to see.

Thanks!

The Windows Modules Installer service entered the stopped state.

WSUS 3.0 SP2 - Workaround KB972493 update shows as 'Needed.'

Wed, 02 Sep 2009 13:20:05 Z

I have recently observed my WSUS server reporting that some clients (Windows Server 2008 SP2) need the update "Windows Server Manager - Windows Server Update Services (WSUS) Dynamic Installer (KB972493)." The clients to not detect that they need this update, but the WSUS server label the client as needing the update regardless.

Similar behavior for the WSUS SP1 dynamic installer was seen in the past. See the Microsoft Discussion Forum public.windows.server.updates_services --- see the thread titled "WSUS 3.0 SP1 KB948014 shows needed even though roll is not install" for details.

Regardless, here is the workaround:

On the client machine, install the WSUS30-KB972455-x86.exe or WSUS30-KB972455-x64.exe, but select the "Administrator Console only" during the install. This will install the Update Services MMC on the machine, but not enable WSUS on the client itself. After this, clients the WSUS server should no longer show the KB972493 as 'Needed.'

WSUS Debug Tool Error

Mon, 19 Oct 2009 17:23:20 Z

When I try to run the Debug tool I get the following error:

C:\wsus server diag>wsusdebugtool.exe /Tool:PurgeUnneededfiles

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or ____
embly 'Microsoft.UpdateServices.Common, Version=2.0.0.0, Culture=neutral, Public
KeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find th
e file specified.
File name: 'Microsoft.UpdateServices.Common, Version=2.0.0.0, Culture=neutral, P
ublicKeyToken=31bf3856ad364e35'
at Microsoft.SoftwareDistribution.Tools.SusServerTool.Main(String[] args)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure lo
gging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus
ion!EnableLog].

I need to purge unneeded updates off of our WSUS Server Microsoft Corporation Version: 3.1.6001.65

Any suggestions would be greatly appreciated!

Client Can't update to WSUS after I have changed WSUS Server

Fri, 20 Nov 2009 12:12:10 Z

Hi
I have problem with WSUS since I have changed WSUS server. I changed the server because old server is not adequate to used as a server. But unfortunately I can show computer population in WSUS since I install new WSUS into new server. I have reconfigure GPM Object to new address but still not working.
As additional information I also check from client side, windows update still disable (it's mean Windows Update still managed by WSUS but connected to previous server. I have uninstalled WSUS from old server. What I must to do?
Thank you before.

kuyus

Service Packs not supported

Sun, 22 Nov 2009 20:48:59 Z

Hello

I Have wsus 2.0 in my organization and I want to know if micosoft take out updates to 2003 SP1 and 2000 pro sp3 and 2000 server sp3 and XP sp1?

Thanks

XP Pro slow startup caused by wuauclt.exe

Sat, 21 Nov 2009 14:14:07 Z

My computer takes a long time (10 min) to complete it's startup. I have traced the problem to heave disk access by
wuauclt.exe. The log shows six minutes being consumed by the operations listed in the log below.

2009-11-21 07:20:44:859 2020 8d4 Agent * Search Scope = {Machine}
2009-11-21 07:26:27:984 2020 8d4 Agent * Found 0 updates and 60 categories in search; evaluated appl. rules of 872 out of 2151 d

Perhaps someone could give me a hint what is going on.

Unable to unistall WSUS 3.0 SP2

Sun, 22 Nov 2009 10:53:44 Z

Hello All,

We are running on the Win2003 SBS R2 and have updated our HDD. Now in the server are 2x 350BG and 2x 2TB in RAID 1. WSUS is installed on "C:\Program Files\Update Services", the WUS folder in on D:\WSUS. Since some days WSUS is not running anymore (actually since we updated the HDDs to 2TB).

So I wanted to uninstall WSUS but are not able to do it and receive this error log files ... :

-- wsussetup.log --------------------------
2009-11-22 11:37:27 Success   MWUSSetup          Validating pre-requisites...
2009-11-22 11:37:29 Success   MWUSSetup          Removing Wsus...
2009-11-22 11:37:30 Success   CustomActions.Dll Successfully set propery of WSUS admin groups' full names
2009-11-22 11:37:31 Error     CustomActions.Dll ExecuteQueryGetMultipleResults: GetRows returned error (Error 0x800A0BCD)
2009-11-22 11:37:31 Error     CustomActions.Dll GetDatabaseLocation: Failed to execute SQL query EXEC dbo.sp_helpdb '%s' (Error 0x800A0BCD)
2009-11-22 11:37:31 Error     CustomActions.Dll SetWyukonInstallDirProperty: Failed to get installed location of SUSDB in WYukon (Error 0x800A0BCD)
2009-11-22 11:37:31 Error     CustomActions.Dll SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x800A0BCD)
2009-11-22 11:37:31 Error     MWUSSetup          RemoveWsus: MWUS Uninstall Failed (Error 0x80070643: Fatal error during installation.)
2009-11-22 11:37:31 Error     MWUSSetup          Wsus MSI uninstallation failed. (Error 0x80070643: Fatal error during installation.)
2009-11-22 11:37:31 Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2009-11-22 11:37:36 Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
2009-11-22 11:37:36 Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper. This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
2009-11-22 11:37:36 Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

-- WSUSSetupmsi_091122_1137.log --------------------------
=== Verbose logging started: 22/11/2009 11:37:29 Build type: SHIP UNICODE 3.01.4000.4042 Calling process: d:\a076593b86c3fb903c\WusSetup.exe ===
MSI (c) (08:6C) [11:37:29:556]: Resetting cached policy values
MSI (c) (08:6C) [11:37:29:556]: Machine policy value 'Debug' is 0
MSI (c) (08:6C) [11:37:29:556]: ******* RunEngine:
           ******* Product: {2C0D7E35-EE6E-4dc7-BA13-2C68AEDEB59D}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (08:6C) [11:37:29:556]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (08:6C) [11:37:29:556]: Grabbed execution mutex.
MSI (c) (08:6C) [11:37:29:634]: Cloaking enabled.
MSI (c) (08:6C) [11:37:29:634]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (08:6C) [11:37:29:634]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (60:AC) [11:37:29:650]: Grabbed execution mutex.
MSI (s) (60:A0) [11:37:29:650]: Resetting cached policy values
MSI (s) (60:A0) [11:37:29:650]: Machine policy value 'Debug' is 0
MSI (s) (60:A0) [11:37:29:650]: ******* RunEngine:
           ******* Product: {2C0D7E35-EE6E-4dc7-BA13-2C68AEDEB59D}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (60:A0) [11:37:29:650]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (60:A0) [11:37:29:713]: End dialog not enabled
MSI (s) (60:A0) [11:37:29:713]: Original package ==> C:\WINDOWS\Installer\b5bf14.msi
MSI (s) (60:A0) [11:37:29:713]: Package we're running from ==> C:\WINDOWS\Installer\b5bf14.msi
MSI (s) (60:A0) [11:37:29:744]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}'.
MSI (s) (60:A0) [11:37:29:744]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (60:A0) [11:37:29:744]: MSCOREE not loaded loading copy from system32
MSI (s) (60:A0) [11:37:29:759]: Machine policy value 'DisablePatch' is 0
MSI (s) (60:A0) [11:37:29:759]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (60:A0) [11:37:29:759]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (60:A0) [11:37:29:759]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (60:A0) [11:37:29:775]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}'.
MSI (s) (60:A0) [11:37:29:775]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (60:A0) [11:37:29:775]: Transforms are not secure.
MSI (s) (60:A0) [11:37:29:775]: Note: 1: 2205 2: 3: Control
MSI (s) (60:A0) [11:37:29:775]: Command Line: CUSTOMACTION_LOG=C:\Temp\1\WSUSCa_091122_1137.log DELETE_DATABASE=0 DELETE_CONTENT=0 PREREQUISITES_VALIDATED=1 SETUP_EXE=1 PROPERTIES_VALIDATED=1 REBOOT=ReallySuppress SUSSETUP_LOG=C:\Temp\1\WSUSSetup.log REMOVE=ALL CURRENTDIRECTORY=d:\a076593b86c3fb903c CLIENTUILEVEL=3 CLIENTPROCESSID=6664
MSI (s) (60:A0) [11:37:29:775]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{339A4CAA-4B57-4903-9CE9-3851C041F846}'.
MSI (s) (60:A0) [11:37:29:775]: Product Code passed to Engine.Initialize:           '{2C0D7E35-EE6E-4dc7-BA13-2C68AEDEB59D}'
MSI (s) (60:A0) [11:37:29:775]: Product Code from property table before transforms: '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}'
MSI (s) (60:A0) [11:37:29:775]: Product Code from property table after transforms: '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}'
MSI (s) (60:A0) [11:37:29:775]: Product registered: entering maintenance mode
MSI (s) (60:A0) [11:37:29:775]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (60:A0) [11:37:29:775]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (60:A0) [11:37:29:775]: Package name retrieved from configuration data: 'WUSSetup.msi'
MSI (s) (60:A0) [11:37:29:775]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (60:A0) [11:37:29:775]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2729
MSI (s) (60:A0) [11:37:29:806]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (60:A0) [11:37:29:806]: Machine policy value 'DisableMsi' is 1
MSI (s) (60:A0) [11:37:29:806]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (60:A0) [11:37:29:806]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (60:A0) [11:37:29:806]: Product {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D} is admin assigned: LocalSystem owns the publish key.
MSI (s) (60:A0) [11:37:29:806]: Product {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D} is managed.
MSI (s) (60:A0) [11:37:29:806]: Running product '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}' with elevated privileges: Product is assigned.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding CUSTOMACTION_LOG property. Its value is 'C:\Temp\1\WSUSCa_091122_1137.log'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding DELETE_DATABASE property. Its value is '0'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding DELETE_CONTENT property. Its value is '0'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Modifying PREREQUISITES_VALIDATED property. Its current value is '0'. Its new value: '1'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding SETUP_EXE property. Its value is '1'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Modifying PROPERTIES_VALIDATED property. Its current value is '0'. Its new value: '1'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding SUSSETUP_LOG property. Its value is 'C:\Temp\1\WSUSSetup.log'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding REMOVE property. Its value is 'ALL'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'd:\a076593b86c3fb903c'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (60:A0) [11:37:29:806]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '6664'.
MSI (s) (60:A0) [11:37:29:822]: TRANSFORMS property is now:
MSI (s) (60:A0) [11:37:29:822]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (60:A0) [11:37:29:822]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Application Data
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Favorites
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\NetHood
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: \\server\Users\remoteadmin\documents
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\PrintHood
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Recent
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\SendTo
MSI (s) (60:A0) [11:37:29:838]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Templates
MSI (s) (60:A0) [11:37:29:853]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Application Data
MSI (s) (60:A0) [11:37:29:853]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Local Settings\Application Data
MSI (s) (60:A0) [11:37:29:853]: SHELL32::SHGetFolderPath returned: \\server\Users\remoteadmin\documents\My Pictures
MSI (s) (60:A0) [11:37:29:853]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (60:A0) [11:37:29:853]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Desktop
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Start Menu\Programs\Administrative Tools
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Start Menu\Programs\Startup
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Start Menu\Programs
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Start Menu
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\remoteadmin\Desktop
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Templates
MSI (s) (60:A0) [11:37:29:869]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (60:A0) [11:37:29:869]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding ProductID property. Its value is '58737-421-4042182-04157'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Müller Sylvie'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'Groupe Immobilier Luxembourgeois'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding Installed property. Its value is '2009/08/07 06:05:54'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\WINDOWS\Installer\b5bf14.msi'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\WINDOWS\Installer\b5bf14.msi'.
MSI (s) (60:A0) [11:37:29:869]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (60:A0) [11:37:29:869]: Machine policy value 'DisableRollback' is 0
MSI (s) (60:A0) [11:37:29:869]: User policy value 'DisableRollback' is 0
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding MsiUISourceResOnly property. Its value is '1'.
=== Logging started: 22/11/2009 11:37:29 ===
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (60:A0) [11:37:29:869]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (60:A0) [11:37:29:869]: Doing action: INSTALL
MSI (s) (60:A0) [11:37:29:884]: Running ExecuteSequence
MSI (s) (60:A0) [11:37:29:884]: Doing action: AdminToolsFolder.F1208F91_6A95_447C_9096_15AC55F59830
Action start 11:37:29: INSTALL.
MSI (s) (60:A0) [11:37:29:884]: PROPERTY CHANGE: Adding AdminToolsFolder.F1208F91_6A95_447C_9096_15AC55F59830 property. Its value is 'C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\'.
Action start 11:37:29: AdminToolsFolder.F1208F91_6A95_447C_9096_15AC55F59830.
MSI (s) (60:A0) [11:37:29:884]: Doing action: AppSearch
Action ended 11:37:29: AdminToolsFolder.F1208F91_6A95_447C_9096_15AC55F59830. Return value 1.
Action start 11:37:29: AppSearch.
MSI (s) (60:A0) [11:37:29:884]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (60:A0) [11:37:29:900]: PROPERTY CHANGE: Adding OLD_VERSION property. Its value is '3.2.7600.226'.
MSI (s) (60:A0) [11:37:29:900]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (60:A0) [11:37:29:900]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (60:A0) [11:37:29:900]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (60:A0) [11:37:29:900]: PROPERTY CHANGE: Adding INSTALL_LANGUAGE property. Its value is 'ENU'.
MSI (s) (60:A0) [11:37:29:900]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (60:A0) [11:37:29:900]: PROPERTY CHANGE: Adding OLD_TYPE1 property. Its value is 'Microsoft.UpdateServices.UI.SnapIn.Common.SnapInManager, Microsoft.UpdateServices.UI.SnapIn, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
MSI (s) (60:A0) [11:37:29:900]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (60:A0) [11:37:29:900]: PROPERTY CHANGE: Adding OLD_TYPE2 property. Its value is 'Microsoft.UpdateServices.UI.SnapIn.Common.ExtensionSnapInManager, Microsoft.UpdateServices.UI.SnapIn, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
MSI (s) (60:A0) [11:37:29:900]: Skipping action: CA_Launch (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: CCPSearch (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: RMCCPSearch (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Doing action: ValidateProductID
Action ended 11:37:29: AppSearch. Return value 1.
Action start 11:37:29: ValidateProductID.
MSI (s) (60:A0) [11:37:29:900]: Skipping action: ValidatePID (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: ValidateUninstallParameters (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: ValidateInstallPrerequisites (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: SetSusSetupLog (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: SetCreateDatabase (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: ValidateInstallParameters (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Skipping action: SetCustomActionLog (condition is false)
MSI (s) (60:A0) [11:37:29:900]: Doing action: SetLocalizableProperties
Action ended 11:37:29: ValidateProductID. Return value 1.
MSI (s) (60:CC) [11:37:29:947]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI22.tmp, Entrypoint: SetLocalizableProperties
MSI (s) (60:D0) [11:37:29:947]: Generating random cookie.
MSI (s) (60:D0) [11:37:29:947]: Created Custom Action Server with PID 7352 (0x1CB8).
MSI (s) (60:3C) [11:37:29:963]: Running as a service.
MSI (s) (60:3C) [11:37:29:978]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding WUS_ADMINISTRATORS property. Its value is 'WSUS Administrators'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding WUSADMIN_DESCRIPTION property. Its value is 'WSUS Administrators can administer the Windows Server Update Services server.'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding WSUS_REPORTERS property. Its value is 'WSUS Reporters'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding WSUS_REPORTERS_DESCRIPTIONS property. Its value is 'WSUS Administrators who can only run reports on the Windows Server Update Services server.'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding CUSTOM_WEBSITE property. Its value is 'WSUS Administration'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding PACKAGES_SHARE_DESCRIPTION property. Its value is 'A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system.'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding CONTENT_SHARE_DESCRIPTION property. Its value is 'A network share to be used by Local Publishing to place published content on this WSUS system.'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding WSUSTEMP_SHARE_DESCRIPTION property. Its value is 'A network share used by Local Publishing from a Remote WSUS Console Instance.'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding ALLCOMP_TG_NAME property. Its value is 'All Computers'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding ALLCOMP_TG_DESC property. Its value is 'This target group provides default settings for all computer clients.'.
MSI (s) (60!00) [11:37:30:009]: PROPERTY CHANGE: Adding UNASSIGN_TG_NAME property. Its value is 'Unassigned Computers'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Adding UNASSIGN_TG_DESC property. Its value is 'Computers that are not members of a specific target group.'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Adding DSS_TG_NAME property. Its value is 'Downstream Servers'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Adding DSS_TG_DESC property. Its value is 'Downstream WSUS servers that are allowed to sync updates from this server.'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Modifying FIREWALL_RULE_NAME_PORT_HTTP property. Its current value is 'Update Services (HTTP)'. Its new value: 'Windows Server Update Services (HTTP)'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Modifying FIREWALL_RULE_NAME_PORT_HTTPS property. Its current value is 'Update Services (HTTPS)'. Its new value: 'Windows Server Update Services (HTTPS)'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Modifying FIREWALL_RULE_DESC_PORT_HTTP property. Its current value is 'An inbound rule for HTTP traffic for Update Services (WSUS) [TCP 8530]'. Its new value: 'An inbound rule for HTTP traffic for Windows Server Update Services (WSUS) [TCP 8530].'.
MSI (s) (60!00) [11:37:30:025]: PROPERTY CHANGE: Modifying FIREWALL_RULE_DESC_PORT_HTTPS property. Its current value is 'An inbound rule for HTTPS traffic for Update Services (WSUS) [TCP 8531]. This rule needs to be enabled only if WSUS server is configured to use SSL'. Its new value: 'An inbound rule for HTTPS traffic for Windows Server Update Services (WSUS) [TCP 8531]. This rule must be enabled if WSUS server is configured to use SSL. Otherwise, it should be disabled.'.
Action start 11:37:29: SetLocalizableProperties.
MSI (s) (60:A0) [11:37:30:025]: Doing action: SetCertServerDescProperty
Action ended 11:37:30: SetLocalizableProperties. Return value 1.
MSI (s) (60:A0) [11:37:30:025]: PROPERTY CHANGE: Adding CERT_SERVER_SET_DESCRIPTION property. Its value is 'Manages the certificates used by Windows Server Update Services (WSUS)'.
Action start 11:37:30: SetCertServerDescProperty.
MSI (s) (60:A0) [11:37:30:025]: Doing action: SetWSUSGroupFullNameProperties
Action ended 11:37:30: SetCertServerDescProperty. Return value 1.
MSI (s) (60:84) [11:37:30:025]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI23.tmp, Entrypoint: SetWSUSGroupFullNameProperties
MSI (s) (60!AC) [11:37:30:072]: PROPERTY CHANGE: Adding WSUS_REPORTERS_FULL property. Its value is 'GILNETWORK\WSUS Reporters'.
MSI (s) (60!AC) [11:37:30:072]: PROPERTY CHANGE: Adding WUS_ADMINISTRATORS_FULL property. Its value is 'GILNETWORK\WSUS Administrators'.
Action start 11:37:30: SetWSUSGroupFullNameProperties.
MSI (s) (60:A0) [11:37:30:072]: Doing action: SetUninstallProperties
Action ended 11:37:30: SetWSUSGroupFullNameProperties. Return value 1.
MSI (s) (60:58) [11:37:30:088]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI24.tmp, Entrypoint: SetUninstallProperties
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Adding CONTENT_DIR property. Its value is 'D:\WSUS'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Adding SQLINSTANCE_NAME property. Its value is '%computername%\MICROSOFT##SSEE'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Adding COMPLETE_SQLINSTANCE property. Its value is 'SERVER\MICROSOFT##SSEE'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Modifying NETWORKSERVICE_ACCOUNT property. Its current value is 'Administrator'. Its new value: 'NT AUTHORITY\NETWORK SERVICE'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Modifying ADMINISTRATORS property. Its current value is 'Administrators'. Its new value: 'BUILTIN\Administrators'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Modifying USERS property. Its current value is 'Users'. Its new value: 'BUILTIN\Users'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Modifying AUTHENTICATED_USERS property. Its current value is 'Authenticated Users'. Its new value: 'NT AUTHORITY\Authenticated Users'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Modifying WYUKON_INSTALL property. Its current value is '0'. Its new value: '1'.
MSI (s) (60!A8) [11:37:30:134]: PROPERTY CHANGE: Adding WYUKON_DIR property. Its value is 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL'.
Action start 11:37:30: SetUninstallProperties.
Action ended 11:37:31: SetUninstallProperties. Return value 3.
Action ended 11:37:31: INSTALL. Return value 3.
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
Property(S): ProductLanguage = 0
Property(S): ProductName = Windows Server Update Services 3.0 SP2
Property(S): ProductVersion = 3.2.7600.226
Property(S): UpgradeCode = {B90C2F98-D8EC-4AE9-ACE3-0E95F814D046}
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): ARPNOREMOVE = 0
Property(S): ARPNOREPAIR = 1
Property(S): ARPSYSTEMCOMPONENT = 0
Property(S): LIMITUI = 1
Property(S): PROMPTROLLBACKCOST = P
Property(S): WEBSITE_INDEX = 0
Property(S): InstallMode = Complete
Property(S): ADMIN_SITE_URL = http://Localhost/WSUSAdmin
Property(S): INSTALLLEVEL = 3
Property(S): LanguageOnlyText = &English only
Property(S): PIDKEY = R2D433DHG9DQ79WW3DXQ929DY
Property(S): PIDSKU = C11-02741
Property(S): OEMRelease = 0
Property(S): PIDTemplate = 58737<````=````=````=````=`````>@@@@@
Property(S): ProductArchitecture = 6
Property(S): UILanguageSelection = 1
Property(S): USESETUP = To install this product, please run wussetup.exe. For other installation options, refer to the Setup documentation
Property(S): ADMINISTRATORS = BUILTIN\Administrators
Property(S): USERS = BUILTIN\Users
Property(S): AUTHENTICATED_USERS = NT AUTHORITY\Authenticated Users
Property(S): NETWORKSERVICE_ACCOUNT = NT AUTHORITY\NETWORK SERVICE
Property(S): WSUSADMINISTRATORSSID = SID
Property(S): WSUS_REPORTERS_SID = SID
Property(S): WUS_INSTALLTYPE = 1
Property(S): DELETE_CONTENT_FOLDER = 0
Property(S): ARP_DISPLAY_NAME = [ProductName]
Property(S): PROPERTIES_VALIDATED = 1
Property(S): PREREQUISITES_VALIDATED = 1
Property(S): UPGRADE_30B2B = 0
Property(S): WEBSITE_BINDING = 8530
Property(S): SNAPINABT_DLL_PATH = SnapInAbout.dll
Property(S): FIREWALL_RULE_NAME_PORT_HTTP = Windows Server Update Services (HTTP)
Property(S): FIREWALL_RULE_NAME_PORT_HTTPS = Windows Server Update Services (HTTPS)
Property(S): FIREWALL_RULE_DESC_PORT_HTTP = An inbound rule for HTTP traffic for Windows Server Update Services (WSUS) [TCP 8530].
Property(S): FIREWALL_RULE_DESC_PORT_HTTPS = An inbound rule for HTTPS traffic for Windows Server Update Services (WSUS) [TCP 8531]. This rule must be enabled if WSUS server is configured to use SSL. Otherwise, it should be disabled.
Property(S): CERT_SERVER_DESC = Manages the certificates used by Windows Server Update Services (WSUS)
Property(S): ADD_PERMISSIONS = 1
Property(S): SQL_SERVER_REMOTE = **********
Property(S): HOST_ON_MU = 0
Property(S): WYUKON_INSTALL = 1
Property(S): SQL_QUERY = USE SUSDB
Property(S): WYUKON_SCHEMA_DIR = [TempFolder]
Property(S): DB_ONLY_UPGRADE = 0
Property(S): TARGETGROUP_TYPE_COMPUTERS = 0
Property(S): TARGETGROUP_TYPE_DSS = 1
Property(S): ALL_COMPUTERS_TARGET_GROUP_ID = A0A08746-4DBE-4a37-9ADF-9E7652C0B421
Property(S): UNASSIGNED_COMPUTERS_TARGET_GROUP_ID = B73CA6ED-5727-47f3-84DE-015E03F6A88A
Property(S): DSS_TARGET_GROUP_ID = D374F42A-9BE2-4163-A0FA-3C86A401B7A7
Property(S): MsiHiddenProperties = CLEANUP_DB;INHERIT_REMOVE_DIRS;MANAGE_RETAINDB_KEY;PACKAGES_COMPLETE_PATH;ROLLBACK_DB_SETUP;SQL_SERVER_REMOTE
Property(S): VersionNT = 502
Property(S): CERT_SERVER_SET_DESCRIPTION = Manages the certificates used by Windows Server Update Services (WSUS)
Property(S): OLD_VERSION = 3.2.7600.226
Property(S): INSTALL_LANGUAGE = ENU
Property(S): OLD_TYPE1 = Microsoft.UpdateServices.UI.SnapIn.Common.SnapInManager, Microsoft.UpdateServices.UI.SnapIn, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Property(S): OLD_TYPE2 = Microsoft.UpdateServices.UI.SnapIn.Common.ExtensionSnapInManager, Microsoft.UpdateServices.UI.SnapIn, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Property(S): SystemFolder = C:\WINDOWS\system32\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): SUSSETUP_LOG = C:\Temp\1\WSUSSetup.log
Property(S): CUSTOMACTION_LOG = C:\Temp\1\WSUSCa_091122_1137.log
Property(S): WUS_ADMINISTRATORS = WSUS Administrators
Property(S): WSUS_REPORTERS = WSUS Reporters
Property(S): DELETE_DATABASE = 0
Property(S): DELETE_CONTENT = 0
Property(S): SQLINSTANCE_NAME = %computername%\MICROSOFT##SSEE
Property(S): CONTENT_DIR = D:\WSUS
Property(S): ProductID = 58737-421-4042182-04157
Property(S): ServicePackLevel = 2
Property(S): AdminToolsFolder.F1208F91_6A95_447C_9096_15AC55F59830 = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): PackageCode = {339A4CAA-4B57-4903-9CE9-3851C041F846}
Property(S): ProductState = 5
Property(S): ProductToBeRegistered = 1
Property(S): SETUP_EXE = 1
Property(S): REBOOT = ReallySuppress
Property(S): REMOVE = ALL
Property(S): CURRENTDIRECTORY = d:\a076593b86c3fb903c
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 6664
Property(S): PRODUCTLANGUAGE = 1033
Property(S): VersionDatabase = 200
Property(S): VersionMsi = 3.01
Property(S): WindowsBuild = 3790
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 2
Property(S): MsiNTSuiteSmallBusiness = 1
Property(S): MsiNTSuiteSmallBusinessRestricted = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\remoteadmin\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\remoteadmin\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\remoteadmin\NetHood\
Property(S): PersonalFolder = \\server\Users\remoteadmin\documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\remoteadmin\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\remoteadmin\Recent\
Property(S): SendToFolder = C:\Documents and Settings\remoteadmin\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): LocalAppDataFolder = C:\Documents and Settings\remoteadmin\Local Settings\Application Data\
Property(S): MyPicturesFolder = \\server\Users\remoteadmin\documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 6
Property(S): PhysicalMemory = 2023
Property(S): VirtualMemory = 2959
Property(S): AdminUser = 1
Property(S): LogonUser = remoteadmin
Property(S): UserSID = S-1-5-21-3973933473-308436332-2607917741-1177
Property(S): UserLanguageID = 1033
Property(S): ComputerName = SERVER
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 11:37:31
Property(S): Date = 22/11/2009
Property(S): MsiNetAssemblySupport = 2.0.50727.3053
Property(S): MsiWin32AssemblySupport = 5.2.3790.3959
Property(S): RedirectedDllSupport = 2
Property(S): Privileged = 1
Property(S): USERNAME = Müller Sylvie
Property(S): COMPANYNAME = Groupe Immobilier Luxembourgeois
Property(S): Installed = 2009/08/07 06:05:54
Property(S): DATABASE = C:\WINDOWS\Installer\b5bf14.msi
Property(S): OriginalDatabase = C:\WINDOWS\Installer\b5bf14.msi
Property(S): UILevel = 2
Property(S): MsiUISourceResOnly = 1
Property(S): Preselected = 1
Property(S): ACTION = INSTALL
Property(S): WUSADMIN_DESCRIPTION = WSUS Administrators can administer the Windows Server Update Services server.
Property(S): WSUS_REPORTERS_DESCRIPTIONS = WSUS Administrators who can only run reports on the Windows Server Update Services server.
Property(S): CUSTOM_WEBSITE = WSUS Administration
Property(S): PACKAGES_SHARE_DESCRIPTION = A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system.
Property(S): CONTENT_SHARE_DESCRIPTION = A network share to be used by Local Publishing to place published content on this WSUS system.
Property(S): WSUSTEMP_SHARE_DESCRIPTION = A network share used by Local Publishing from a Remote WSUS Console Instance.
Property(S): ALLCOMP_TG_NAME = All Computers
Property(S): ALLCOMP_TG_DESC = This target group provides default settings for all computer clients.
Property(S): UNASSIGN_TG_NAME = Unassigned Computers
Property(S): UNASSIGN_TG_DESC = Computers that are not members of a specific target group.
Property(S): DSS_TG_NAME = Downstream Servers
Property(S): DSS_TG_DESC = Downstream WSUS servers that are allowed to sync updates from this server.
Property(S): WSUS_REPORTERS_FULL = GILNETWORK\WSUS Reporters
Property(S): WUS_ADMINISTRATORS_FULL = GILNETWORK\WSUS Administrators
Property(S): COMPLETE_SQLINSTANCE = SERVER\MICROSOFT##SSEE
Property(S): WYUKON_DIR = C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL
MSI (s) (60:A0) [11:37:31:494]: Note: 1: 1725
MSI (s) (60:A0) [11:37:31:509]: Product: Windows Server Update Services 3.0 SP2 -- Removal failed.

MSI (s) (60:A0) [11:37:31:525]: Cleaning up uninstalled install packages, if any exist
MSI (s) (60:A0) [11:37:31:525]: MainEngineThread is returning 1603
MSI (s) (60:AC) [11:37:31:525]: Destroying RemoteAPI object.
MSI (s) (60:D0) [11:37:31:525]: Custom Action Manager thread ending.
=== Logging stopped: 22/11/2009 11:37:31 ===
MSI (c) (08:6C) [11:37:31:541]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (08:6C) [11:37:31:541]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/11/2009 11:37:31 ===

Do you have any idear what's going on?

Windows Update Clients - Supported Configurations for WSUS 3.0 SP2

Fri, 20 Nov 2009 19:01:06 Z

I am sure this is an easy question, but despite my efforts digging into the product documentation - I cannot find the answers. The questions have to do with Supported configurations of WSUS 3.0 SP2:

1. Will a Windows 7 Client AND a Windows Server 2008 R2 client be able to connect to my WSUS SP1 Architecture to download and install patches?

2. Will a WSUS SP2 Server be able to connect as a child to a WSUS SP1 Parent server? (We use SCCM integration and may have to delay upgrading on our central site for change management reasons).

I would appreciate answers to either of these questions if you know!

Repeated WSUS 3.0 SP2 update failure on SBS2003 SP2 -- Database issue (Error 0x800A0E78)

Mon, 16 Nov 2009 23:07:05 Z

Ever since the rollout of WSUS 3.0 SP2 Windows autoupdate has tried to install it as a critical update and it has failed. Clearly I have a WSUS database problem and I do not know how to fix the database (recreate it or whatever is needed). I'd be most grateful for direction in this. Here is my WSUSSetup.log showing the failure and errors:

2009-11-16 11:51:23 Success   MWUSSetup          Validating pre-requisites...
2009-11-16 11:51:23 Error     MWUSSetup          Failed to determine if database is present (Error 0x800A0E78)
2009-11-16 11:51:23 Error     MWUSSetup          CUpgradeDriver::PerformPreSetupActions: Failed to execute SQL query SELECT HostOnMu from SUSDB..tbConfigurationA (Error 0x800A0E78)
2009-11-16 11:51:23 Error     MWUSSetup          CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x800A0E78)
2009-11-16 11:51:23 Error     MWUSSetup          CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
2009-11-16 11:51:37 Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
2009-11-16 11:51:37 Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper. This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
2009-11-16 11:51:37 Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x800A0E78)
2009-11-16 11:51:54 Success   MWUSSetup          Validating pre-requisites...
2009-11-16 11:51:55 Error     MWUSSetup          Failed to determine if database is present (Error 0x800A0E78)
2009-11-16 11:51:55 Error     MWUSSetup          CUpgradeDriver::PerformPreSetupActions: Failed to execute SQL query SELECT HostOnMu from SUSDB..tbConfigurationA (Error 0x800A0E78)
2009-11-16 11:51:55 Error     MWUSSetup          CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x800A0E78)
2009-11-16 11:51:55 Error     MWUSSetup          CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)

Thanks,
Patrick

WSUS and sysprep

Fri, 20 Nov 2009 13:58:22 Z

Is WSUS a supported role when syspreping a Server 2008? It's not listed in the documentation.

Thanks
Dave

Dave C

WSUS 3.0 SP2 and WSS 3.0 SP2 installation question.

Fri, 20 Nov 2009 12:53:27 Z

Hi,

A time ago I have installed WSUS 3.0 SP2. (under Windows 2003 Standard SP2 and IIS6)
(at the moment I'm not using host header values under IIS and server name is like A.company.xxx)
At the moment everything runs smoothly.
Under IIS "Default Web Site" (port:80) I see folders and files like "Selfupdate" and "WUTRACK.BIN" etc.
Also I have virtual site like "WSUS Administration" (port:8530 and SSL:8531)
I think that all this is neccecary to run WSUS correctly.

Now I have need, to install "Windows Sharepoint Services 3.0 SP2" to the same computer.
I have read that there could be so many problems installing WSS after WSUS.
So, can anyone give me some steps what should I take before starting WSS installation
or steps what should I do when I'm already installing WSS or POST installation steps?
My WSS installation should be single-server using "Windows Internal Database"

(My only tought was renaming "Default Web Site" to something like "blaah site" and assign it host header values like A and A.company.xx so
if WSS needs to play around with "Default Web Site" it doe's not affect my current WSUS configuration. But it was only idea. I have
no ideas does WSS installation creates new "Default Web Site" (where I can add host header values like B and B.company.xx), in that case
if it founds that there is no "Default Web Site" anymore or what? Or am I completly lost :)

rgds
Sven

KB968930 installation failure /KeyReg access permissions

Wed, 18 Nov 2009 13:57:49 Z

Hi all,
We just synchronised KB968930 on our WSUS server. Installation failures on our machines have been remediated by setting access pemissions on following keyreg:

hklm\software\microsoft\windows nt\currentversion\svchost

Existing access permission were set to Read for Administrators and SYSTEM. I've set it to Full Control and installation then was successfull.

By the way, why that keyreg have those access permissions? Any one else observed the same?
Should that setting prevent XP SP3 installation and show the widespread eror "Access is denied"?

This is for info sharing and discussion.

Cherif

Using ReportViewer with WSUS

Fri, 20 Nov 2009 12:12:22 Z

We have just installed WSUS 3.0 SP2 & ReportViewer Redistributable 2008 on Win Server 2003.
Everything works fine except for one small thing with ReportViewer. The language is set to English-US and thus the dates are reported in American format. The dates displayed in the main Computers window of WSUS are UK/European format so the settings for WSUS itself must be correct, and the Server regional settings are UK; it's only the report view that is US. I cannot find any setting within WSUS or the report view to change the language for the report display. Does anyone know if there is one ?

*** Additional info added 25/11/09 ***
On the 'Computer Status Summary Report'
Page 1 has Language en-US Last status reported 11/25/2009
Page 2 has Report Data Collected 25/11/2009

So even within 1 report it is displaying 2 different date formats, page 1=USA, page 2=UK.
How come ?

Groups show after migration, but not computer

Thu, 19 Nov 2009 10:19:06 Z

Good day.

I am in the process of migrating my WSUS 3.0 SP2 from a Windows Server 2003 R2 server with SQL 2005 SP3 to a Windows Server 2008 R2 server using SQL 2008 SP1.
The synch went through fine, the files are being updated as I write this post, the computer groups are all there, but there are no computer within those groups! Please note that I do NOT use policies for computers, computer are moved to groups manually.
Maybe I am being a little hasty, but don't want to wait for the whole process to complete before I realise that there is a problem.
I used this process on URL http://technet.microsoft.com/en-us/library/cc463370(WS.10).aspx