WSUS V3 does not "see" Windows 7 updates

May 7, 2013, 11:27 pm

≫ Next: Synchronize from Microsoft updates An http error occurred

≪ Previous: SUS Client rebooting the Server system

Hi all,

We had a WSUS server working like a charm. Now this server crashed so I needed to get WSUS going again. I have WSUS running again on a Windows 2008R2 Server with WSUS 3.2.7600 running. I selected Windows 7 in Products and Classifications. However. Afted I did a succesfull sync. I am only getting xp/Vista/winserver updates. I do get some windows 7 updates but only the ones that apply not only to Windows 7.

I tried to deselect windows 7 and select again and resync. But it didn't work.

Can someone please help?

↧

Synchronize from Microsoft updates An http error occurred

February 3, 2013, 9:29 pm

≫ Next: New server - Need to Move WSUS from 2003 to 2008R2

≪ Previous: WSUS V3 does not "see" Windows 7 updates

Unable to sync with upstream server... using

Synchronize from Microsoft updates

Result: An http error occurred

WebException: The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="%2fmicrosoftupdate%2fv6%2ferrorinformation.aspx%3ferror%3d15">here</a>.</h2>
</body></html>

--.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

Please advise....

↧

New server - Need to Move WSUS from 2003 to 2008R2

April 28, 2013, 7:30 am

≫ Next: Windows Update Changing from WSUS server to Microsoft randomly

≪ Previous: Synchronize from Microsoft updates An http error occurred

Hi All

I will be replacing a W2K3 SP2 server that currently has WSUS on it with a W2K8R2 server. There is already a WSUS GPO so when I join the W2K8R2 to the domain and dcpromo it I will have all the policies I need (I think). How do I migrate the WSUS database. I assume I will need to download a newer version for W2K8R2. The W2K3 has 3.2. When the snap in runs it says there is a connection error so I am not sure about the existing setup (did not do it). The XP clients do appear to be updated. The Windows 7 are not.

Also, what role does SQL play in WSUS. The only SQL we have on the W2K8 now is SQL 2005 (32 bit) that was installed by Symantec Backup Exec when it was installed.

Can you give me some direction of how I should proceed?

Thanks.

↧

Windows Update Changing from WSUS server to Microsoft randomly

May 8, 2013, 10:24 am

≫ Next: Unable to Uninstall WSUS 3.0 sp2 from 2008 SBS

≪ Previous: New server - Need to Move WSUS from 2003 to 2008R2

I have a GPO set to direct client computers and servers to connect to WSUS server. Some machines connect/update/report without issue. 40% Connect once or twice and never update.

WSUS is setup on 2008R2. Client machines are Windows XP and 7. More concerned about the Windows 7 machines.

When I run a gpupdate /force the Windows Update dialogue box says "You receive updates: Managed by your system administrator." As soon as I hit "Check for updates" the setting changes to "You receive updates: "For Windows and other products from Microsoft Update" and then starts grabbing updates from microsoft update.

Here is the windowsupdate.log

https://dl.dropboxusercontent.com/u/2738438/update.txt

↧

Unable to Uninstall WSUS 3.0 sp2 from 2008 SBS

May 8, 2013, 1:40 pm

≫ Next: WSUS 3.0 SP2 issues

≪ Previous: Windows Update Changing from WSUS server to Microsoft randomly

So I am working with a Microsoft Windows Small buisness server 2011 standard version 6.1.7601 Service Pack 1 Build 7601

Recently we noticed that WSUS was not able to start WSUS and attempted to remove it from the server in order to re-install it.

I recieved the message below:

"Attempt to un-install Windows Server Update Services failed with error code 0x0x80070643. Fatal Error during instillation."

I followed the instructions found in :blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx stopping after step 5. Becasue I didnt see any references to the "MICROSOFT##SSEE"in the cleanup tool.

After reading a few more posts I attempted to follow : davidvielmetter.com/tricks/wsus-wont-uninstall-or-re-install/

I downloaded the WSUS 3.0 SP2 installer and ran thru the instillation. I installed it on a seperate hardrive than before and attempted to lauch the IIS website it created.

I get a Internet explorer cannot display the webpage.

Figuring that I would attempt to uninstall it one more time I get the message listed below.

"Attempt to un-install Windows Server Update Services failed with error code 0x80004005. Error HRESULT_FAIL has been returned from a call to a COM component."

I would like to get this back up and running and feel that it has gotten away from me. I want to remove the old instillation to clean up the server in preperation of a fresh instillation later on.

Is there a way to manually remove the WSUS role from SBS server ?

↧

WSUS 3.0 SP2 issues

May 8, 2013, 1:13 pm

≫ Next: Downstream wsus not updating from upstream server

≪ Previous: Unable to Uninstall WSUS 3.0 sp2 from 2008 SBS

Hi,

My Windows Server 2003 SP2 didn't have the audit tab on its disks and was messed up. It was probably related to why I had issues installing some patches on it. I had to take ownership of the C: drive in order to try and fix it because it was a major flag showing up on my scans. I think that messed something up on it and I can't get WSUS to work.

Can anyone help?

Thanks,

ClashDragon

↧

Downstream wsus not updating from upstream server

May 8, 2013, 4:55 pm

≫ Next: Synchronization fail in all downstream server, 4 layers of WSUS server - Can it be fixed?

≪ Previous: WSUS 3.0 SP2 issues

my down strem server does not synchronize with my upstream server. it does synchronize with microsoft web site and downloads updates

↧

Synchronization fail in all downstream server, 4 layers of WSUS server - Can it be fixed?

April 25, 2013, 6:56 pm

≫ Next: How to "prune" or "delete" updates I mistakenly asked for when initially setting up WSUS 2012?

≪ Previous: Downstream wsus not updating from upstream server

Hello support friends. Following is a diagram of our WSUS setup. Other than the top server RPAWSUS01 and RPAWSUS02, the rest are in different geographic location. This was done not to kill the network when updates are approved once a month. Rough total clients serverd by each server is given below. Clients are targetted using AD group policy.

A rough estimate of number of clients that each server is supporting is as follows.

RPAWSUS01 = 215 Clinets, (Primary server, has one downstream server called RPAWSUS02)
RPAWSUS02 = 3815 Clients, (Downstram server in replica mode to RPAWSUS01, has two downstream server called LIVWSUS01 and CRGWSUS01)

LIVWSUS01 = 3891 Clients, am server in replica mode to RPAWSUS02, has 6 downstream server)
FRFWSUS01 = 588 Clients,(Downstream server in replica mode to LIVWSUS01)
FRFCHCWSUS01 = 259 Clients,(Downstream server in replica mode to LIVWSUS01)
BNKWSUS01 =837 Clients, (Downstream server in replica mode to LIVWSUS01)
CTNWSUS01 = 1036 Clients, (Downstream server in replica mode to LIVWSUS01)
CMDWSUS01 = 188 Clients, (Downstream server in replica mode to LIVWSUS01)
BOWWSUS01 = 230 Clients, (Downstream server in replica mode to LIVWSUS01)

CRGWSUS01 = 1530 Clients, (Downstream server in replica mode to RPAWSUS02, has 2 downstream server)
TCHWSUS01 = 434 Clients, (Downstream server in replica mode to CRGWSUS01)
BALWSUS01 = 126 Clients, (Downstream server in replica mode to CRGWSUS01)

Updates that are approved automatically to all clients when they arrive are Critical Updates. We also approve all Security Updates, Updates and Deffinition Updates once a month once they have passed the trial groups. Our environement is set as Prod 1 and Prod 2. 3rd week of the month updats are approved for Prod 1, and next week Prod 2 gets the same set of updates approved.

On the primary server RPAWSUS01 following is the status:
Unapproved updates: 51
Approved updates: 9428
Declined Updates: 25122
Computers: 215
Computer Groups: 62

Issue: In server RPAWSUS02 the status is as follows,
Unapproved updates: 23438
Approved updates: 9428
Declined Updates: 2098
Computers: 3815
Computer Groups: 62

Similar disparity exists in all the downstream servers. None of the dowstream servers finish sync, they his 99% and time out. But, when I approve an update during the 3rd and 4th patching week, the clients sitting at different geographical location are being offered the approved updates.

I have same error as follows in all the downstream servers, except the primary server RPAWSUS01

SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ReadOneRow()
   at Microsoft.UpdateServices.Internal.DataAccess.HideUpdatesForReplicaSync(String xmlUpdateIds)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessHiddenUpdates(Guid[] hiddenUpdates)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ReplicaSync()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

The system of servers worked for a month in terms of syncing etc. I understand, possibly by mistake theDrivers Classification was ticked in the primary server. Metadata info possibly bloated its DB. Since then, I belive this sync issue started.

We normally synchronize the following classification: Critical Updates, Definition Updates, Feature Packs, Security Updates, Service Packs, Update Rollups and Updates.

Servers are all Vmware guests with specs as follows:

Windows Server 2008 R2 Standard with SP1 (64 bit)
4 CPU assigned at 2.53 GHz
12 GB RAM
C Drive for OS
D Drive for WSUS contents (300 GB, among wihich about 95% is filled up)

I understand this is a large number of servers, but I think one fix may fix all the rest of the servers. Can someone kindly point me to a start? I have run WSUS DB indexer script from the Scripting Guys mainly when the systems were all put in place. It still runs OK, but now when I try to run the WSUS Clenup wizard, it never actually starts or seems to timeout.

I am happy to provide more logs etc, but I need to know which servers to start looking at primarily.

Thanks

↧

How to "prune" or "delete" updates I mistakenly asked for when initially setting up WSUS 2012?

May 8, 2013, 11:56 pm

≫ Next: wsus installation

≪ Previous: Synchronization fail in all downstream server, 4 layers of WSUS server - Can it be fixed?

We only run Windows 8/Server 2012/Office 2013. I am 100% sure that these are the only installations we have on our corporate network (of 15 machines :-)). When I initially installed WSUS as part of our domain creation, I mistakenly selected Office 2010 in addition to Office 2013.

So I now have a whole boatload of updates for Office 2010 (and none of them marked as "needed") in my list.

I'd like for these updates to "go away", but don't want to decline them "just in case" we ever decide to have a machine or 2 run the older office version.

What are my options? I looked at pruning (at least I think that's the name), but am not totally sure if that's what I want, and what the side effects might be.

Thank you in advance for any help...

↧

wsus installation

May 9, 2013, 8:14 am

≫ Next: How to deploy KB923845 - Background Intelligent Transfer Service (BITS) 2.5 to clients?

≪ Previous: How to "prune" or "delete" updates I mistakenly asked for when initially setting up WSUS 2012?

can we install administration console of wsus in win 7

↧

How to deploy KB923845 - Background Intelligent Transfer Service (BITS) 2.5 to clients?

April 30, 2013, 7:37 am

≫ Next: KB2813170 Update Won't Take

≪ Previous: wsus installation

Dears,

We want to deploy KB923845 - Background Intelligent Transfer Service (BITS) 2.5 to clients because SCCM installation on XP SP2 X64 fails and needs this update.

It seems that this update is not in WSUS so we can approve it for install to clients.

If it is available in WSUS please let me know which products and Classsifications should be marked,

If we cannot apprve in WSUS kindly advise a way.

↧

KB2813170 Update Won't Take

May 9, 2013, 7:05 am

≫ Next: Windows XP SP3 wuauclt Errors

≪ Previous: How to deploy KB923845 - Background Intelligent Transfer Service (BITS) 2.5 to clients?

I've been struggling with this for a while and thought I would ask a question here to see if anyone can help me. I have one Windows 2003 server that will not quit reporting that it needs update KB2813170.

The update installs just fine without any error and I always get a message that the update has been applied. However, the server almost immediately reports that it needs the update again and I can't get it to stop notifying me that it needs that update.

I have tried uninstalling in the control panel and reinstalling. I have downloaded the update from the Windows Update Catalog and tried it that way too. I've stopped the update services on the server and deleted the files in C:\Windows\SoftwareDistribution folder, restarted and then re-applied the update. In each case, the update appears to complete and finish as expected but the server soon starts reporting that it needs the update again. I'm caught up in this loop and can't think of anything else to try.

Does anyone have any ideas on what I should try next?

Thanks.

Mike

"MC"

↧

Windows XP SP3 wuauclt Errors

May 9, 2013, 9:32 am

≫ Next: ContentSyncAgent not responding

≪ Previous: KB2813170 Update Won't Take

Hi,

We've built a new downstream WSUS server and have moved some devices on an existing WSUS server to test it. When I moved the devices I created new GUUID, Cleared out the SoftwareDistribution folder and ran numers wuauclt /resetauthorization /detectnow

The devices show on the new WSUS server in the Workstations group and there are no missing updates. What's troubling me is the errors on the clients in C:\windows\WindowsUpdate.log

2013-05-09	08:45:10:593	1496	350	Misc	===========  Logging initialized (build: 7.6.7600.256, tz: +0100)  ===========
2013-05-09	08:45:10:593	1496	350	Misc	  = Process: C:\WINDOWS\System32\svchost.exe
2013-05-09	08:45:10:593	1496	350	Misc	  = Module: C:\WINDOWS\system32\wuaueng.dll
2013-05-09	08:45:10:578	1496	350	Service	*************
2013-05-09	08:45:10:593	1496	350	Service	** START **  Service: Service startup
2013-05-09	08:45:10:593	1496	350	Service	*********
2013-05-09	08:45:11:078	1496	350	Agent	  * WU client version 7.6.7600.256
2013-05-09	08:45:11:078	1496	350	Agent	  * Base directory: C:\WINDOWS\SoftwareDistribution
2013-05-09	08:45:11:078	1496	350	Agent	  * Access type: No proxy
2013-05-09	08:45:11:078	1496	350	Agent	  * Network state: Connected
2013-05-09	08:45:29:296	1496	2e4	Agent	***********  Agent: Initializing Windows Update Agent  ***********
2013-05-09	08:45:29:296	1496	2e4	Agent	***********  Agent: Initializing global settings cache  ***********
2013-05-09	08:45:29:296	1496	2e4	Agent	  * WSUS server: http://WUSERVER:8530
2013-05-09	08:45:29:296	1496	2e4	Agent	  * WSUS status server: http://WUSERVER:8530
2013-05-09	08:45:29:296	1496	2e4	Agent	  * Target group: Workstations
2013-05-09	08:45:29:296	1496	2e4	Agent	  * Windows Update access disabled: No
2013-05-09	08:45:29:343	1496	2e4	DnldMgr	Download manager restoring 0 downloads
2013-05-09	08:45:29:546	 576	9cc	Misc	===========  Logging initialized (build: 7.6.7600.256, tz: +0100)  ===========
2013-05-09	08:45:29:546	 576	9cc	Misc	  = Process: C:\Program Files\LogMeIn\x86\LogMeIn.exe
2013-05-09	08:45:29:546	 576	9cc	Misc	  = Module: C:\WINDOWS\system32\wuapi.dll
2013-05-09	08:45:29:546	 576	9cc	COMAPI	-------------
2013-05-09	08:45:29:546	 576	9cc	COMAPI	-- START --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:45:29:546	 576	9cc	COMAPI	---------
2013-05-09	08:45:29:562	 576	9cc	COMAPI	<<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:45:33:890	1496	350	Report	***********  Report: Initializing static reporting data  ***********
2013-05-09	08:45:33:890	1496	350	Report	  * OS Version = 5.1.2600.3.0.65792
2013-05-09	08:45:33:968	1496	350	Report	  * Computer Brand = Hewlett-Packard
2013-05-09	08:45:33:968	1496	350	Report	  * Computer Model = HP ProBook 6560b
2013-05-09	08:45:34:000	1496	350	Report	  * Bios Revision = 68SCE Ver. F.04
2013-05-09	08:45:34:000	1496	350	Report	  * Bios Name = Default System BIOS
2013-05-09	08:45:34:000	1496	350	Report	  * Bios Release Date = 2011-05-10T00:00:00
2013-05-09	08:45:34:000	1496	350	Report	  * Locale ID = 2057
2013-05-09	08:45:35:859	1496	c30	Agent	*************
2013-05-09	08:45:35:859	1496	c30	Agent	** START **  Agent: Finding updates [CallerId = ]
2013-05-09	08:45:35:859	1496	c30	Agent	*********
2013-05-09	08:45:35:859	1496	c30	Agent	  * Online = Yes; Ignore download priority = No
2013-05-09	08:45:35:859	1496	c30	Agent	  * Criteria = "IsInstalled = 0 AND IsHidden = 0"
2013-05-09	08:45:35:859	1496	c30	Agent	  * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2013-05-09	08:45:35:859	1496	c30	Agent	  * Search Scope = {Machine}
2013-05-09	08:45:49:796	1496	578	Misc	===========  Logging initialized (build: 7.6.7600.256, tz: +0100)  ===========
2013-05-09	08:45:49:796	1496	578	Misc	  = Process: C:\WINDOWS\System32\svchost.exe
2013-05-09	08:45:49:796	1496	578	Misc	  = Module: C:\WINDOWS\system32\wuapi.dll
2013-05-09	08:45:49:796	1496	578	COMAPI	-------------
2013-05-09	08:45:49:796	1496	578	COMAPI	-- START --  COMAPI: Search [ClientId = Windows System Health Agent Search]
2013-05-09	08:45:49:796	1496	578	COMAPI	---------
2013-05-09	08:45:49:796	1496	578	COMAPI	<<-- SUBMITTED -- COMAPI: Search [ClientId = Windows System Health Agent Search]
2013-05-09	08:45:50:609	1496	c30	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2013-05-09	08:45:50:609	1496	c30	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WUSERVER:8530/ClientWebService/client.asmx
2013-05-09	08:45:50:687	1496	c30	PT	WARNING: Cached cookie has expired or new PID is available
2013-05-09	08:45:50:687	1496	c30	PT	Initializing simple targeting cookie, clientId = a60ddbaf-a114-4a03-a962-cc427585b48d, target group = Workstations, DNS name = l040680.business.ukho.gov.uk
2013-05-09	08:45:50:687	1496	c30	PT	  Server URL = http://WUSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: PTError: 0x80244019
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: GetCookie_WithRecovery failed : 0x80244019
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: RefreshCookie failed: 0x80244019
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: RefreshPTState failed: 0x80244019
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: Sync of Updates: 0x80244019
2013-05-09	08:45:51:890	1496	c30	PT	WARNING: SyncServerUpdatesInternal failed: 0x80244019
2013-05-09	08:45:51:890	1496	c30	Agent	  * WARNING: Failed to synchronize, error = 0x80244019
2013-05-09	08:45:52:156	1496	c30	Agent	  * WARNING: Exit code = 0x80244019
2013-05-09	08:45:52:156	1496	c30	Agent	*********
2013-05-09	08:45:52:156	1496	c30	Agent	**  END  **  Agent: Finding updates [CallerId = ]
2013-05-09	08:45:52:156	1496	c30	Agent	*************
2013-05-09	08:45:52:156	1496	c30	Agent	WARNING: WU client failed Searching for update with error 0x80244019
2013-05-09	08:45:52:171	1496	c30	Agent	*************
2013-05-09	08:45:52:171	1496	c30	Agent	** START **  Agent: Finding updates [CallerId = Windows System Health Agent Search]
2013-05-09	08:45:52:171	1496	c30	Agent	*********
2013-05-09	08:45:52:171	1496	c30	Agent	  * Include potentially superseded updates
2013-05-09	08:45:52:171	1496	c30	Agent	  * Online = No; Ignore download priority = No
2013-05-09	08:45:52:171	1496	c30	Agent	  * Criteria = "IsInstalled=0 and CategoryIDs contains '0fa1201d-4330-4fa8-8ae9-b877473b6441'"
2013-05-09	08:45:52:171	1496	c30	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-05-09	08:45:52:171	1496	c30	Agent	  * Search Scope = {Machine}
2013-05-09	08:45:52:187	 576	fdc	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:45:52:187	 576	fdc	COMAPI	  - Updates found = 0
2013-05-09	08:45:52:187	 576	fdc	COMAPI	  - WARNING: Exit code = 0x00000000, Result code = 0x80244019
2013-05-09	08:45:52:187	 576	fdc	COMAPI	---------
2013-05-09	08:45:52:187	 576	fdc	COMAPI	--  END  --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:45:52:187	 576	fdc	COMAPI	-------------
2013-05-09	08:45:52:187	 576	9cc	COMAPI	WARNING: Operation failed due to earlier error, hr=80244019
2013-05-09	08:45:52:187	 576	9cc	COMAPI	FATAL: Unable to complete asynchronous search. (hr=80244019)
2013-05-09	08:45:59:093	1496	350	AU	###########  AU: Initializing Automatic Updates  ###########
2013-05-09	08:45:59:187	1496	350	AU	AU setting next sqm report timeout to 2013-05-09 07:45:59
2013-05-09	08:46:42:609	1496	350	AU	  # WSUS server: http://WUSERVER:8530
2013-05-09	08:46:42:609	1496	350	AU	  # Detection frequency: 22
2013-05-09	08:46:42:609	1496	350	AU	  # Target group: Workstations
2013-05-09	08:46:42:609	1496	350	AU	  # Approval type: Scheduled (User preference)
2013-05-09	08:46:42:609	1496	350	AU	  # Scheduled install day/time: Every day at 3:00
2013-05-09	08:46:42:609	1496	350	AU	  # Auto-install minor updates: Yes (Policy)
2013-05-09	08:46:42:609	 576	9cc	COMAPI	-------------
2013-05-09	08:46:42:609	 576	9cc	COMAPI	-- START --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:46:42:609	 576	9cc	COMAPI	---------
2013-05-09	08:46:42:625	 576	9cc	COMAPI	<<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:46:42:640	1496	350	AU	Initializing featured updates
2013-05-09	08:46:42:656	1496	350	AU	Found 0 cached featured updates
2013-05-09	08:46:42:656	1496	350	AU	AU finished delayed initialization
2013-05-09	08:46:42:656	1496	350	AU	#############
2013-05-09	08:46:42:656	1496	350	AU	## START ##  AU: Search for updates
2013-05-09	08:46:42:656	1496	350	AU	#########
2013-05-09	08:46:42:656	1496	350	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {BA22A6F1-C73B-4A1A-8DCE-89CAD3B5F20F}]
2013-05-09	08:46:52:640	1496	350	AU	Forced install timer expired for scheduled install
2013-05-09	08:46:52:640	1496	350	AU	UpdateDownloadProperties: 0 download(s) are still in progress.
2013-05-09	08:46:52:640	1496	350	AU	Setting AU scheduled install time to 2013-05-10 02:00:00
2013-05-09	08:46:52:890	1496	350	AU	AU received policy change subscription event
2013-05-09	08:49:04:996	1496	c30	Agent	  * Found 0 updates and 1 categories in search; evaluated appl. rules of 722 out of 1965 deployed entities
2013-05-09	08:49:04:996	1496	c30	Agent	*********
2013-05-09	08:49:04:996	1496	c30	Agent	**  END  **  Agent: Finding updates [CallerId = Windows System Health Agent Search]
2013-05-09	08:49:04:996	1496	c30	Agent	*************
2013-05-09	08:49:05:012	1496	c30	Agent	*************
2013-05-09	08:49:05:012	1496	c30	Agent	** START **  Agent: Finding updates [CallerId = ]
2013-05-09	08:49:05:012	1496	c30	Agent	*********
2013-05-09	08:49:05:012	1496	c30	Agent	  * Online = Yes; Ignore download priority = No
2013-05-09	08:49:05:012	1496	c30	Agent	  * Criteria = "IsInstalled = 0 AND IsHidden = 0"
2013-05-09	08:49:05:012	1496	c30	Agent	  * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2013-05-09	08:49:05:012	1496	c30	Agent	  * Search Scope = {Machine}
2013-05-09	08:49:05:028	1496	264	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = Windows System Health Agent Search]
2013-05-09	08:49:05:028	1496	264	COMAPI	  - Updates found = 0
2013-05-09	08:49:05:028	1496	264	COMAPI	---------
2013-05-09	08:49:05:028	1496	264	COMAPI	--  END  --  COMAPI: Search [ClientId = Windows System Health Agent Search]
2013-05-09	08:49:05:028	1496	264	COMAPI	-------------
2013-05-09	08:49:17:691	1496	c30	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2013-05-09	08:49:17:691	1496	c30	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WUSERVER:8530/ClientWebService/client.asmx
2013-05-09	08:49:17:707	1496	c30	PT	WARNING: Cached cookie has expired or new PID is available
2013-05-09	08:49:17:707	1496	c30	PT	Initializing simple targeting cookie, clientId = a60ddbaf-a114-4a03-a962-cc427585b48d, target group = Workstations, DNS name = l040680.business.ukho.gov.uk
2013-05-09	08:49:17:707	1496	c30	PT	  Server URL = http://WUSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: PTError: 0x80244019
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: GetCookie_WithRecovery failed : 0x80244019
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: RefreshCookie failed: 0x80244019
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: RefreshPTState failed: 0x80244019
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: Sync of Updates: 0x80244019
2013-05-09	08:49:17:738	1496	c30	PT	WARNING: SyncServerUpdatesInternal failed: 0x80244019
2013-05-09	08:49:17:738	1496	c30	Agent	  * WARNING: Failed to synchronize, error = 0x80244019
2013-05-09	08:49:17:738	1496	c30	Agent	  * WARNING: Exit code = 0x80244019
2013-05-09	08:49:17:738	1496	c30	Agent	*********
2013-05-09	08:49:17:738	1496	c30	Agent	**  END  **  Agent: Finding updates [CallerId = ]
2013-05-09	08:49:17:738	1496	c30	Agent	*************
2013-05-09	08:49:17:738	1496	c30	Agent	WARNING: WU client failed Searching for update with error 0x80244019
2013-05-09	08:49:17:754	1496	c30	Agent	*************
2013-05-09	08:49:17:754	1496	c30	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-05-09	08:49:17:754	1496	c30	Agent	*********
2013-05-09	08:49:17:754	1496	c30	Agent	  * Online = No; Ignore download priority = No
2013-05-09	08:49:17:754	1496	c30	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"
2013-05-09	08:49:17:754	1496	c30	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-05-09	08:49:17:754	1496	c30	Agent	  * Search Scope = {Machine}
2013-05-09	08:49:17:769	 576	1264	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:49:17:769	 576	1264	COMAPI	  - Updates found = 0
2013-05-09	08:49:17:769	 576	1264	COMAPI	  - WARNING: Exit code = 0x00000000, Result code = 0x80244019
2013-05-09	08:49:17:769	 576	1264	COMAPI	---------
2013-05-09	08:49:17:769	 576	1264	COMAPI	--  END  --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:49:17:769	 576	1264	COMAPI	-------------
2013-05-09	08:49:17:769	 576	9cc	COMAPI	WARNING: Operation failed due to earlier error, hr=80244019
2013-05-09	08:49:17:769	 576	9cc	COMAPI	FATAL: Unable to complete asynchronous search. (hr=80244019)
2013-05-09	08:49:17:785	 576	9cc	COMAPI	-------------
2013-05-09	08:49:17:785	 576	9cc	COMAPI	-- START --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:49:17:785	 576	9cc	COMAPI	---------
2013-05-09	08:49:17:785	 576	9cc	COMAPI	<<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:00:430	1496	c30	Agent	  * Found 0 updates and 72 categories in search; evaluated appl. rules of 1166 out of 3079 deployed entities
2013-05-09	08:50:00:430	1496	c30	Agent	*********
2013-05-09	08:50:00:430	1496	c30	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-05-09	08:50:00:430	1496	c30	Agent	*************
2013-05-09	08:50:00:445	1496	c30	Agent	*************
2013-05-09	08:50:00:445	1496	f78	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {BA22A6F1-C73B-4A1A-8DCE-89CAD3B5F20F}]
2013-05-09	08:50:00:445	1496	c30	Agent	** START **  Agent: Finding updates [CallerId = ]
2013-05-09	08:50:00:445	1496	f78	AU	  # 0 updates detected
2013-05-09	08:50:00:445	1496	c30	Agent	*********
2013-05-09	08:50:00:445	1496	c30	Agent	  * Online = Yes; Ignore download priority = No
2013-05-09	08:50:00:445	1496	f78	AU	#########
2013-05-09	08:50:00:445	1496	c30	Agent	  * Criteria = "IsInstalled = 0 AND IsHidden = 0"
2013-05-09	08:50:00:445	1496	f78	AU	##  END  ##  AU: Search for updates [CallId = {00000000-0000-0000-0000-000000000000}]
2013-05-09	08:50:00:445	1496	c30	Agent	  * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2013-05-09	08:50:00:445	1496	f78	AU	#############
2013-05-09	08:50:00:445	1496	c30	Agent	  * Search Scope = {Machine}
2013-05-09	08:50:00:445	1496	f78	AU	Featured notifications is disabled.
2013-05-09	08:50:00:445	1496	f78	AU	Setting AU scheduled install time to 2013-05-10 02:00:00
2013-05-09	08:50:01:039	1496	c30	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2013-05-09	08:50:01:039	1496	c30	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WUSERVER:8530/ClientWebService/client.asmx
2013-05-09	08:50:01:070	1496	c30	PT	WARNING: Cached cookie has expired or new PID is available
2013-05-09	08:50:01:070	1496	c30	PT	Initializing simple targeting cookie, clientId = a60ddbaf-a114-4a03-a962-cc427585b48d, target group = Workstations, DNS name = l040680.business.ukho.gov.uk
2013-05-09	08:50:01:070	1496	c30	PT	  Server URL = http://WUSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: PTError: 0x80244019
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: GetCookie_WithRecovery failed : 0x80244019
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: RefreshCookie failed: 0x80244019
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: RefreshPTState failed: 0x80244019
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: Sync of Updates: 0x80244019
2013-05-09	08:50:01:085	1496	c30	PT	WARNING: SyncServerUpdatesInternal failed: 0x80244019
2013-05-09	08:50:01:085	1496	c30	Agent	  * WARNING: Failed to synchronize, error = 0x80244019
2013-05-09	08:50:01:085	1496	c30	Agent	  * WARNING: Exit code = 0x80244019
2013-05-09	08:50:01:085	1496	c30	Agent	*********
2013-05-09	08:50:01:085	1496	c30	Agent	**  END  **  Agent: Finding updates [CallerId = ]
2013-05-09	08:50:01:085	1496	c30	Agent	*************
2013-05-09	08:50:01:085	1496	c30	Agent	WARNING: WU client failed Searching for update with error 0x80244019
2013-05-09	08:50:01:101	1496	c30	Report	REPORT EVENT: {61B71C5B-2B6D-42ED-9F16-0F0896A3A9BA}	2013-05-09 08:45:52:156+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80244019		Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244019.
2013-05-09	08:50:01:117	 576	1664	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:01:117	 576	1664	COMAPI	  - Updates found = 0
2013-05-09	08:50:01:117	 576	1664	COMAPI	  - WARNING: Exit code = 0x00000000, Result code = 0x80244019
2013-05-09	08:50:01:117	 576	1664	COMAPI	---------
2013-05-09	08:50:01:117	 576	1664	COMAPI	--  END  --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:01:117	 576	1664	COMAPI	-------------
2013-05-09	08:50:01:117	 576	9cc	COMAPI	WARNING: Operation failed due to earlier error, hr=80244019
2013-05-09	08:50:01:117	 576	9cc	COMAPI	FATAL: Unable to complete asynchronous search. (hr=80244019)
2013-05-09	08:50:01:117	 576	9cc	COMAPI	-------------
2013-05-09	08:50:01:117	 576	9cc	COMAPI	-- START --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:01:117	 576	9cc	COMAPI	---------
2013-05-09	08:50:01:117	 576	9cc	COMAPI	<<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:01:179	1496	c30	Report	REPORT EVENT: {519599DA-5F92-4453-9C13-8FCA70E64FAB}	2013-05-09 08:46:42:656+0100	1	202	102	{00000000-0000-0000-0000-000000000000}	0	0	AutomaticUpdates	Success	Content Install	Reboot completed.
2013-05-09	08:50:01:179	1496	c30	Report	REPORT EVENT: {5A5DD7BD-2155-4CB2-8C96-52E785655C44}	2013-05-09 08:49:17:738+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80244019		Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244019.
2013-05-09	08:50:01:179	1496	c30	Agent	*************
2013-05-09	08:50:01:179	1496	c30	Agent	** START **  Agent: Finding updates [CallerId = ]
2013-05-09	08:50:01:179	1496	c30	Agent	*********
2013-05-09	08:50:01:179	1496	c30	Agent	  * Online = Yes; Ignore download priority = No
2013-05-09	08:50:01:179	1496	c30	Agent	  * Criteria = "IsInstalled = 0 AND IsHidden = 0"
2013-05-09	08:50:01:179	1496	c30	Agent	  * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2013-05-09	08:50:01:179	1496	c30	Agent	  * Search Scope = {Machine}
2013-05-09	08:50:01:882	1496	c30	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2013-05-09	08:50:01:882	1496	c30	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WUSERVER:8530/ClientWebService/client.asmx
2013-05-09	08:50:01:897	1496	c30	PT	WARNING: Cached cookie has expired or new PID is available
2013-05-09	08:50:01:897	1496	c30	PT	Initializing simple targeting cookie, clientId = a60ddbaf-a114-4a03-a962-cc427585b48d, target group = Workstations, DNS name = l040680.business.ukho.gov.uk
2013-05-09	08:50:01:897	1496	c30	PT	  Server URL = http://WUSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: PTError: 0x80244019
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: GetCookie_WithRecovery failed : 0x80244019
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: RefreshCookie failed: 0x80244019
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: RefreshPTState failed: 0x80244019
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: Sync of Updates: 0x80244019
2013-05-09	08:50:01:913	1496	c30	PT	WARNING: SyncServerUpdatesInternal failed: 0x80244019
2013-05-09	08:50:01:913	1496	c30	Agent	  * WARNING: Failed to synchronize, error = 0x80244019
2013-05-09	08:50:01:913	1496	c30	Agent	  * WARNING: Exit code = 0x80244019
2013-05-09	08:50:01:913	1496	c30	Agent	*********
2013-05-09	08:50:01:913	1496	c30	Agent	**  END  **  Agent: Finding updates [CallerId = ]
2013-05-09	08:50:01:913	1496	c30	Agent	*************
2013-05-09	08:50:01:913	1496	c30	Agent	WARNING: WU client failed Searching for update with error 0x80244019
2013-05-09	08:50:01:944	 576	1664	COMAPI	>>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:01:944	 576	1664	COMAPI	  - Updates found = 0
2013-05-09	08:50:01:944	 576	1664	COMAPI	  - WARNING: Exit code = 0x00000000, Result code = 0x80244019
2013-05-09	08:50:01:944	 576	1664	COMAPI	---------
2013-05-09	08:50:01:944	 576	1664	COMAPI	--  END  --  COMAPI: Search [ClientId = <NULL>]
2013-05-09	08:50:01:944	 576	1664	COMAPI	-------------
2013-05-09	08:50:01:944	 576	9cc	COMAPI	WARNING: Operation failed due to earlier error, hr=80244019
2013-05-09	08:50:01:944	 576	9cc	COMAPI	FATAL: Unable to complete asynchronous search. (hr=80244019)
2013-05-09	08:50:06:082	1496	c30	Report	REPORT EVENT: {D10F6F91-A6A3-4084-BA9F-F1D9ACAF27C1}	2013-05-09 08:50:01:085+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80244019		Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244019.
2013-05-09	08:50:06:082	1496	c30	Report	REPORT EVENT: {E328415C-3E54-42F8-9CC1-B5D1394AA640}	2013-05-09 08:50:01:913+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80244019		Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244019.

I've googled and searched the error code "0x80244019" loads, it's given me some things to try:

- The Group Policy has the correct address and the :8530 ports at the end. I've double checked the registry keys on the client (HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer& WUStatusServer)

- Check that the file exists on the WSUS Server. File is located in C:\Program Files\Update Services\WebServices\ClientWebService\client.asmx and IIS browses to the correct place when you right click ClientWebService and click Explore. You can also browse to the file via IE on the clients

- The clients do NOT have a Firewall enabled

Does anyone have any suggestions as to what else I can try to eliminate the errors/warnings?

↧

ContentSyncAgent not responding

July 2, 2010, 3:31 am

≫ Next: TargetGroup WSUS

≪ Previous: Windows XP SP3 wuauclt Errors

Hi,

i'm using WSUS 3.2.7600.226 on a Windows 2008 SBS-Server.

After installation everything worked fine for abaout a year. Now the download is not working anymore. Download-Status says 153 Updates missing files and 3995 of 4978 MB downloaded.

The Manager says ContentSyncAgent not responding (in german)

It ist not possible to restart the wsus services, they keep saying "will be restarted" So I have to restart the server.

After restarting the server the download works for 2-300 MB or 1-2 hours and then the agent hangs again.

When restarting the server the display says "stopping windows update services" for 15 minutes

There are no 364-errors in the eventlog.

Last entries in teh logfile say:
Auftrag abgebrochen. Benutzer: NT-AUTORITÄT\SYSTEM, Auftrag: WU Client Download, Auftrags-ID: {1ad838de-2822-47c3-b7c0-b28bcd00cd3f}, Besitzer: NT-AUTORITÄT\SYSTEM, Dateianzahl: 0

Thanks for any suggestions.

Rgds. F.Rapp

↧

TargetGroup WSUS

July 9, 2010, 8:54 am

≫ Next: Windows Server Update Event ID: 364 - Content file download failed. Reason: File cert verification failure

≪ Previous: ContentSyncAgent not responding

Buenas, me gustaria saber como agrego Sub Grupos en WSUS, cual seria la nomenclatura a utilizar. En estos momentos tengo PCS, lo que deseo es dentro de PCS crear otro Grupo y saber como lo coloco en la Politica de dominio.

Gracias de antemano

↧

Windows Server Update Event ID: 364 - Content file download failed. Reason: File cert verification failure

August 11, 2010, 10:26 am

≫ Next: Why update outlook

≪ Previous: TargetGroup WSUS

My WSUS server is having trouble downloading Windows 2008 updates. I receive similar errors to the the following whenever I try to retry the download:

Event ID: 364

Source: Windows Server Update

Category: Synchronization

Description:Content file download failed. Reason: File cert verification failure. Source File: /msdownload/update/software/secu/2010/07/windows6.0-kb981852-x64_4d074b16f8de591447daf21184358c43e7a81ca6.cab Destination File: e:\WSUS\WsusContent\A6\4D074B16F8DE591447DAF21184358C43E7A81CA6.cab.

↧

Why update outlook

September 14, 2010, 9:08 pm

≫ Next: wsus not download forefront update to client

≪ Previous: Windows Server Update Event ID: 364 - Content file download failed. Reason: File cert verification failure

I've been looking for an answer to this for at least 5 years with no success. I have installed many, many versions of MS Office on lots of pcs. I have always excluded Outlook; I don't like it, I don't need the extra bells and whistles and I'm happy with Outlook Express. BUT Windows update has ALWAYS told me that I have an installed copy of Outlook which MUST be updated (mostly the junk mail stuff). What's worse, it chides me every time I refuse to update this non-existent facility.

Why do I have to suffer this ridiculous nuisance?

Current pcs are mostly XP with two Vistas and I refuse to move to Office 2007 as none of my family can understand the icon-based menus.

↧

wsus not download forefront update to client

September 16, 2010, 1:23 am

≫ Next: Windows Update fails on Windows Server 2008 R2 Error 80244018

≪ Previous: Why update outlook

wsus not download forefront update to client

↧

Windows Update fails on Windows Server 2008 R2 Error 80244018

September 9, 2010, 7:47 am

≫ Next: Migration of WSUS (not exactly same as others I have read here)

≪ Previous: wsus not download forefront update to client

I trying to do a manual update of the server and received the error code 80244018. It looks like the server is unable to download the updates.

I tried to paste the windows update log in here but it was too big. Even after I emptied it out and ran the update. I can email it if needs be.

Any help would be appreciated.

Stephen

↧

Migration of WSUS (not exactly same as others I have read here)

May 10, 2013, 8:30 am

≫ Next: Reboot behavior - WSUS Clients

≪ Previous: Windows Update fails on Windows Server 2008 R2 Error 80244018

Currently running version 3.2.7600.226 on a 2003 server. Want to bring up a new server running 2012 and have WSUS run on/from there. (We make changes to our WSUS VERY infrequently and usually just set up new workstations and pull down updates from it, so rather careful/hesitant here to avoid breaking something.)

Concerns:

1) About 300 clients currently find WSUS at the current server name; would like to avoid having to change the server name in all of them, if we're going to keep running WSUS the same way we do now...

2) We think old server may have lots of old obsolete update material in it; how to clear out what's no longer needed before copying to a new location?

3) Our WSUS has been running for some years, back to when we were on an old NT domain (before we ever had AD). All of the workstations are set up as "client side targeting" where everything was done from the client. I understand that it is also possible to run WSUS another way, where all parameters are driven from Group Policy on the server. (I have already done a little bit of work with Group Policy on a server, when we used it to enforce a new login password policy.) Was thinking that this might be a good time to change over from running WSUS the old way to this new way, using GPO and AD from the server. (If we were to do a change like this, then # 1) above may not really apply, because it would be worth it to visit all the workstations (if we had to), to get the benefits of being able to change clients' setups from the server in the future if we could.)

Can anyone point me to a procedure that would help us do what I've described above?

Help is MUCH appreciated, from one who is still learning GPO and AD, not to mention how to make changes to a WSUS install. Thanks again!

↧