get the statistics of client patches
WSUS 2016 Is port 8530 needs to be opened
Few weeks back we upgraded WSUS 2008 To 2016.
we have to environments Staging and prod.
I see that all the servers in prod reported to new WSUS 2016, but not the staging.I see that prod environment can telnet wsus server with port 8530 but not staging I thought that might be the cause. But I see that this was all working with WSUS 2008 without being able to telnet, what am I missing?
Error: Connection Error
Hi all,
This is the scenario... after a failed in-place update at the WSUS server, I've had to install a new brand VM with Windows 2012R2 with WSUS role.
The DB instancy is in another server (SQL2008R2) so, I've change the value "SQLServerName" at the registry to the SQLServer.
At the IIS, I've change the Wsus Pool the memory to 0 (it is the only service that will be running at the server), and the Queue Length from 1000, to 30000...
After installing KB3159706, run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
but... nothing worked for me... when I open the WSUS the red error connection appears...
Any idea if the problem could be for a certificate needed? or an API, or something else?
Thank you in advance!
Pablo.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()
WSUS Post-Configuration fails after an upgrade to 2012 R2 (System.Runtime.InteropServices.COMException (0x80070003))
Hello.
I recently upgraded my WSUS host (WID) from Server 2012 to 2012R2.
After upgrade is finished I found, that WSUS Post-deployment configuration failed with the following error:
--------
Log file is located at C:\Users\xxx\AppData\Local\Temp\tmp7AA1.tmp
Post install is starting
Fatal Error: The system cannot find the path specified.
--------
I tried to launch postinstall using Powershell and got the same result.
I also checked if UpdateServices-Services.xml is placed in C:\Windows\System32\ServerManager\ComponentConfiguration folder and contains correct path to WSUS files - everything was OK.
There is the full log:
2014-05-12 15:40:17 Postinstall started
2014-05-12 15:40:17 Detected role services: Api, UI, WidDatabase, Services
2014-05-12 15:40:17 Start: LoadSettingsFromParameters
2014-05-12 15:40:17 Content local is: False
2014-05-12 15:40:17 SQL instname is:
2014-05-12 15:40:17 End: LoadSettingsFromParameters
2014-05-12 15:40:18 Start: Run
2014-05-12 15:40:18 Fetching WsusAdministratorsSid from registry store
2014-05-12 15:40:18 Value is S-1-5-21-3606383621-533361507-1611783712-1001
2014-05-12 15:40:18 Fetching WsusReportersSid from registry store
2014-05-12 15:40:18 Value is S-1-5-21-3606383621-533361507-1611783712-1002
2014-05-12 15:40:18 Configuring content directory...
2014-05-12 15:40:18 Configuring groups...
2014-05-12 15:40:18 Starting group configuration for WSUS Administrators...
2014-05-12 15:40:18 Found group in regsitry, attempting to use it...
2014-05-12 15:40:20 Writing group to registry...
2014-05-12 15:40:20 Finished group creation
2014-05-12 15:40:20 Starting group configuration for WSUS Reporters...
2014-05-12 15:40:20 Found group in regsitry, attempting to use it...
2014-05-12 15:40:20 Writing group to registry...
2014-05-12 15:40:20 Finished group creation
2014-05-12 15:40:20 Configuring permissions...
2014-05-12 15:40:20 Fetching content directory...
2014-05-12 15:40:20 Fetching ContentDir from registry store
2014-05-12 15:40:20 Value is D:\WSUS
2014-05-12 15:40:20 Fetching group SIDs...
2014-05-12 15:40:20 Fetching WsusAdministratorsSid from registry store
2014-05-12 15:40:20 Value is S-1-5-21-3606383621-533361507-1611783712-1001
2014-05-12 15:40:20 Fetching WsusReportersSid from registry store
2014-05-12 15:40:20 Value is S-1-5-21-3606383621-533361507-1611783712-1002
2014-05-12 15:40:20 Creating group principals...
2014-05-12 15:40:20 Granting directory permissions...
2014-05-12 15:40:21 Granting permissions on content directory...
2014-05-12 15:41:24 Granting registry permissions...
2014-05-12 15:41:24 Granting registry permissions...
2014-05-12 15:41:24 Granting registry permissions...
2014-05-12 15:41:24 Configuring shares...
2014-05-12 15:41:24 Configuring network shares...
2014-05-12 15:41:24 Fetching content directory...
2014-05-12 15:41:24 Fetching ContentDir from registry store
2014-05-12 15:41:24 Value is D:\WSUS
2014-05-12 15:41:24 Fetching WSUS admin SID...
2014-05-12 15:41:24 Fetching WsusAdministratorsSid from registry store
2014-05-12 15:41:24 Value is S-1-5-21-3606383621-533361507-1611783712-1001
2014-05-12 15:41:24 Content directory is local, creating content shares...
2014-05-12 15:41:24 Creating share "UpdateServicesPackages" with path "D:\WSUS\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published
on this WSUS system."
2014-05-12 15:41:24 Deleting existing share...
2014-05-12 15:41:24 Creating share...
2014-05-12 15:41:24 Share successfully created
2014-05-12 15:41:24 Creating share "WsusContent" with path "D:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2014-05-12 15:41:24 Deleting existing share...
2014-05-12 15:41:24 Creating share...
2014-05-12 15:41:24 Share successfully created
2014-05-12 15:41:24 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2014-05-12 15:41:24 Deleting existing share...
2014-05-12 15:41:24 Creating share...
2014-05-12 15:41:24 Share successfully created
2014-05-12 15:41:24 Finished creating content shares
2014-05-12 15:41:24 Stopping service WSUSService
2014-05-12 15:41:25 Stopping service W3SVC
2014-05-12 15:41:27 Configuring WID database...
2014-05-12 15:41:27 Configuring the database...
2014-05-12 15:41:27 Establishing DB connection...
2014-05-12 15:41:27 Checking to see if database exists...
2014-05-12 15:41:27 Database exists
2014-05-12 15:41:27 Switching database to single user mode...
2014-05-12 15:41:30 Loading install type query...
2014-05-12 15:41:30 DECLARE @currentDBVersion int
DECLARE @scriptMajorVersion int = (9600)
DECLARE @scriptMinorVersion int = (16384)
DECLARE @databaseMajorVersion int
DECLARE @databaseMinorVersion int
DECLARE @databaseBuildNumber nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
SELECT 1
END
ELSE
BEGIN
SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
IF (@delimiterPosition = 0)
BEGIN
RAISERROR('Invalid schema version number', 16, 1) with nowait
return
END
SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
IF @currentDBVersion < 926
BEGIN
SELECT 3
END
ELSE
BEGIN
IF (@scriptMajorVersion > @databaseMajorVersion OR
(@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
BEGIN
SELECT 2
END
ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
@scriptMinorVersion = @databaseMinorVersion)
BEGIN
SELECT 0
END
ELSE
BEGIN
SELECT 4
END
END
END
2014-05-12 15:41:31 Install type is: Reinstall
2014-05-12 15:41:31 Creating logins...
2014-05-12 15:41:31 Fetching account info for S-1-5-20
2014-05-12 15:41:31 Found principal
2014-05-12 15:41:31 Found account
2014-05-12 15:41:31 Got binary SID
2014-05-12 15:41:31 Fetching WsusAdministratorsSid from registry store
2014-05-12 15:41:31 Value is S-1-5-21-3606383621-533361507-1611783712-1001
2014-05-12 15:41:31 Fetching account info for S-1-5-21-3606383621-533361507-1611783712-1001
2014-05-12 15:41:33 Found principal
2014-05-12 15:41:33 Found account
2014-05-12 15:41:33 Got binary SID
2014-05-12 15:41:33 Setting content location...
2014-05-12 15:41:33 Fetching ContentDir from registry store
2014-05-12 15:41:33 Value is D:\WSUS
2014-05-12 15:41:33 Swtching DB to multi-user mode......
2014-05-12 15:41:40 Finished setting multi-user mode
2014-05-12 15:41:40 Writing DB settings to registry...
2014-05-12 15:41:40 Marking PostInstall done for UpdateServices-WidDatabase in the registry...
2014-05-12 15:41:40 Starting service W3SVC
2014-05-12 15:41:40 Configuring IIS...
2014-05-12 15:41:40 Start: ConfigureWebsite
2014-05-12 15:41:41 System.Runtime.InteropServices.COMException (0x80070003): The system cannot find the path specified.
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.PropertyValueCollection.PopulateList()
at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
at Microsoft.UpdateServices.Administration.UseCustomWebSite..ctor()
at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Could anyone please help with this issue?
Thank you.
What is VMware, Inc. - Net - 10/17/2018 12:00:00 AM - 1.8.10.0 appearing in Windows Update
Hello,
Starting this morning 4/24/2019 I am seeing "VMware, Inc. - Net - 10/17/2018 12:00:00 AM - 1.8.10.0" appearing in Windows Update for the servers ... is it normal? what is this patch doing?
I did some research but could not found any information...
The date said 10/17/2018 but today's date is 04/24/2019!!!
Thanks,
Dom
Security / System Center Configuration Manager Current Branch / SQL
How to force restart of Windows 7 two weeks after approving an update?
Hi,
We deploy updates with WSUS and use Group policies for configuring windows update.
How we can force a restart of Windows 7 two weeks after approving an update?
The updates should primary be installed by the user by restarting Windows 7. If they dont restart their Computers for a long time, the updates should be force-installed and the computers should reboot automatically.
Thank you for your help!
Can We prevent the WSUS service on from being updated automatically?
Hello
Can We prevent the WSUS service on from being update automatically ?
If Yes How ?
W2016 WSUS Server no updates error 0x80244019
I'm running W2016 standard running WSUS v10.0.14393.3085 with on proxy on a dell poweredge r510, which is on an enterprise domain (my managed WSUS GPOs for clients and server in my OU).
Within WSUS, all clients within the computer and server groups (two separate GPOs w/ intranet, statistics, and alternative address as http://myservername.server.enterprise.com:8530) have been reporting and getting updates for some time (Synched from Microsoft Update), EXCEPT for the W2016 WSUS server itself (reports and tries to download only). When approved updates are pushed to all clients from this WSUS server, this server as a client, always results a download error 0x80244019 for its scheduled updates.
I have tried the wupdate troubleshooter, stop services to delete the Software Distribution folder, run sfc and dism tools successfully, extending the IIS limits as often recommended, ran a script to update the synch point,.and other troubleshooting steps.
Generally, the wupdate logs on this W2016 WSUS server show "Failed to connect to the DO service", GetDOManager() failed, DO download failed with error 80246008[Extended: 80040154], falling back to BITS, DownloadManager Downloading from http://myservername.server.enterprise.com:8530/c/msdownload/update/software/secu/2019/09/windows10.0-kb4512574-x64-express_b177e2c2174b489ceff667d52df7f4c8ce03a9f3.cab to C:\Windows\SoftwareDistribution\Download\2d9e284ea8b5dc47a58881030534a0ae\Windows10.0-KB4512574-x64-express.cab (full file). DownloadManager Error 0x80244019 occurred while downloading update; notifying dependent calls., DownloadManager The update's sandbox is in use.
In regard to the Wsus server as client logs, I don't understand the "Unknown( 10): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found)". Also, what and from where is the Wsus server trying to download and install that is different from the others?
Thanks
Differences in Wsus, PC and Server WU logs are:
Wsus Server as client:
2019/09/12 10:56:26.6109407 1036 7912 Agent Initializing Windows Update Agent
2019/09/12 10:56:26.6110934 1036 7912 DownloadManager Download manager restoring 0 downloads
2019/09/12 10:56:26.6112237 1036 7912 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2019/09/12 10:56:26.6338555 1036 7656 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019/09/12 10:56:26.6338680 1036 7656 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019/09/12 10:56:26.6340696 1036 7656 Shared Power status changed
2019/09/12 10:56:26.6401693 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:26.6401712 1036 11224 DownloadManager Power state change detected. Source now: AC
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 10): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 11): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 12): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 13): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 14): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
2019/09/12 10:56:48.6583863 1036 11224 Agent Obtained a network PDC reference for callID {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with No-Progress-Timeout set to 4294967295; ActivationID: 11.
2019/09/12 10:56:48.6653620 1036 11224 DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = F4A4BC25-72E3-4138-91AA-0BBE8787A39F]
2019/09/12 10:56:48.6653695 1036 11224 DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2019/09/12 10:56:48.6653704 1036 11224 DownloadManager Updates to download = 1
2019/09/12 10:56:48.6653718 1036 11224 Agent Title = 2019-09 Servicing Stack Update for Windows Server 2016 for x64-based Systems (KB4512574)
2019/09/12 10:56:48.6653779 1036 11224 Agent UpdateId = DF51B003-58D6-42D6-AD9E-D81ADAA1437E.200
2019/09/12 10:56:48.6653788 1036 11224 Agent Bundles 1 updates:
2019/09/12 10:56:48.6653844 1036 11224 Agent 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1.200
2019/09/12 10:56:48.6654551 1036 11224 DownloadManager No locked revisions found for update DF51B003-58D6-42D6-AD9E-D81ADAA1437E; locking the user-specified revision.
2019/09/12 10:56:48.6917724 1036 11224 DownloadManager No locked revisions found for update 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1; locking the user-specified revision.
2019/09/12 10:56:48.7121951 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category PerUpdate.
2019/09/12 10:56:48.7121970 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category Low.
2019/09/12 10:56:48.7121984 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category Normal.
2019/09/12 10:56:48.7121988 1036 11224 DownloadManager Regulation: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} - Loaded sequence number 65535 for regulation category High.
2019/09/12 10:56:48.7593079 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:48.9161840 1036 11224 DownloadManager Queueing update {0276DFC7-ACCD-45B2-B0D8-33F8A88250C1}.200 for download handler request generation.
2019/09/12 10:56:48.9250379 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 10): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 11): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 12): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 13): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
2019/09/12 10:56:49.0097850 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:49.0097915 1036 11224 Agent Released network PDC reference for callId {F4A4BC25-72E3-4138-91AA-0BBE8787A39F}; ActivationID: 11
2019/09/12 10:56:49.0097989 1036 11224 Agent Obtained a network PDC reference for callID {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with No-Progress-Timeout set to 4294967295; ActivationID: 16.
1600/12/31 19:00:00.0000000 1036 7912 Unknown( 14): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).
2019/09/12 10:56:49.0169418 1036 10580 Agent WU client calls back to download call {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with code Call progress and error 0
2019/09/12 10:56:49.0225203 1036 11224 DownloadManager * END * Begin Downloading Updates CallerId = UpdateOrchestrator
2019/09/12 10:56:49.0225268 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:49.0225347 1036 11224 Agent Obtained a network PDC reference for callID {6B4A26A7-EC8A-4366-804A-5005A33AC493} with No-Progress-Timeout set to 4294967295; ActivationID: 17.
2019/09/12 10:56:49.0259758 1036 11224 DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = 6B4A26A7-EC8A-4366-804A-5005A33AC493]
2019/09/12 10:56:49.0259828 1036 11224 DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
2019/09/12 10:56:49.0259842 1036 11224 DownloadManager Updates to download = 1
2019/09/12 10:56:49.0259851 1036 11224 Agent Title = 2019-09 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4516044)
2019/09/12 10:56:49.0259916 1036 11224 Agent UpdateId = 5BD21FF7-DD92-4CB4-A08A-E15994C99CAD.200
2019/09/12 10:56:49.0259921 1036 11224 Agent Bundles 1 updates:
2019/09/12 10:56:49.0259977 1036 11224 Agent B8FB5A48-445F-43FE-87E6-30AF9B0482D8.200
2019/09/12 10:56:49.0260582 1036 11224 DownloadManager No locked revisions found for update 5BD21FF7-DD92-4CB4-A08A-E15994C99CAD; locking the user-specified revision.
2019/09/12 10:56:49.0305503 1036 11104 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:49.0334440 1036 11224 DownloadManager No locked revisions found for update B8FB5A48-445F-43FE-87E6-30AF9B0482D8; locking the user-specified revision.
2019/09/12 10:56:49.0583900 1036 11104 DownloadManager Generating download request for update {0276DFC7-ACCD-45B2-B0D8-33F8A88250C1}.200
2019/09/12 10:56:49.0596416 1036 11104 DownloadManager Calling into handler 0x8 to generate download request for update 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1.200
2019/09/12 10:56:49.0596840 1036 11104 Handler Generating request for CBS update 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1 in sandbox C:\Windows\SoftwareDistribution\Download\2d9e284ea8b5dc47a58881030534a0ae
2019/09/12 10:56:49.0714944 1036 11104 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:49.0715079 1036 11104 Handler Selected payload type is Express
2019/09/12 10:56:49.0715610 1036 11104 Handler Detected download state is dsStart
2019/09/12 10:56:49.0715805 1036 11104 Handler Adding Windows10.0-KB4512574-x64-express.cab (entire file) to request list.
2019/09/12 10:56:49.2843768 1036 11104 Handler Saved state: cCompleteIterations: 0, pt: Express, nNextRequestID: 1.
2019/09/12 10:56:49.2843838 1036 11104 Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2019/09/12 10:56:49.6963948 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:49.7157637 1036 11224 DownloadManager Failed to connect to the DO service; (hr = 80040154)
2019/09/12 10:56:49.7157651 1036 11224 DownloadManager GetDOManager() failed, hr=80246008, hrExtended=80040154
2019/09/12 10:56:49.7157670 1036 11224 DownloadManager Failed creating DO job with hr 80246008
2019/09/12 10:56:49.7236690 1036 11224 DownloadManager DO download failed with error 80246008[Extended: 80040154], falling back to BITS and retrying with new Download Job.
2019/09/12 10:56:49.7339323 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:50.0735368 1036 11224 DownloadManager BITS job initialized: JobId = {39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD}
2019/09/12 10:56:50.1283929 1036 11224 DownloadManager Downloading from http://myservername.server.enterprise.com:8530/c/msdownload/update/software/secu/2019/09/windows10.0-kb4512574-x64-express_b177e2c2174b489ceff667d52df7f4c8ce03a9f3.cab to C:\Windows\SoftwareDistribution\Download\2d9e284ea8b5dc47a58881030534a0ae\Windows10.0-KB4512574-x64-express.cab (full file).
2019/09/12 10:56:50.1369493 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Express, nNextRequestID: 1.
2019/09/12 10:56:50.1501319 1036 11224 DownloadManager New download job {39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD} for UpdateId 0276DFC7-ACCD-45B2-B0D8-33F8A88250C1.200
2019/09/12 10:56:50.1900991 1036 11224 DownloadManager Download job 39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD resumed.
2019/09/12 10:56:50.1979517 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:50.2421252 1036 11224 DownloadManager UpdateId = {0276DFC7-ACCD-45B2-B0D8-33F8A88250C1}.200, Job ID = 39FA21EE-DCB0-4C9A-AEE3-6F83D5A485AD, xszResponseHeaders = HTTP/1.1 404 Not Found Date: Thu, 12 Sep 2019 14:56:50 GMT Content-Length: 0 Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET .
2019/09/12 10:56:50.2528209 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:50.2528292 1036 11224 Agent Released network PDC reference for callId {F4A4BC25-72E3-4138-91AA-0BBE8787A39F}; ActivationID: 16
2019/09/12 10:56:50.2528418 1036 11224 Agent Obtained a network PDC reference for callID {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with No-Progress-Timeout set to 4294967295; ActivationID: 18.
2019/09/12 10:56:50.2532267 1036 10580 Agent WU client calls back to download call {F4A4BC25-72E3-4138-91AA-0BBE8787A39F} with code Call progress and error 0
2019/09/12 10:56:50.2939647 1036 11224 DownloadManager Queueing update {B8FB5A48-445F-43FE-87E6-30AF9B0482D8}.200 for download handler request generation.
2019/09/12 10:56:50.8185462 1036 11224 Handler Loaded state: cCompleteIterations: 0, pt: Unknown, nNextRequestID: 0.
2019/09/12 10:56:50.9221381 1036 11224 Shared Effective power state: AC
2019/09/12 10:56:50.9221451 1036 11224 Agent Released network PDC reference for callId {6B4A26A7-EC8A-4366-804A-5005A33AC493}; ActivationID: 17
2019/09/12 10:56:50.9221539 1036 11224 Agent Obtained a network PDC reference for callID {6B4A26A7-EC8A-4366-804A-5005A33AC493} with No-Progress-Timeout set to 4294967295; ActivationID: 19.
2019/09/12 10:56:50.9225836 1036 10580 Agent WU client calls back to download call {6B4A26A7-EC8A-4366-804A-5005A33AC493} with code Call progress and error 0
2019/09/12 10:56:50.9761559 1036 11224 DownloadManager * END * Begin Downloading Updates CallerId = UpdateOrchestrator
PC Clients:
019/09/13 09:38:12.5750696 4168 2724 Agent Initializing Windows Update Agent
2019/09/13 09:38:12.5753639 4168 2724 DownloadManager Retrieved 1 persisted download jobs
2019/09/13 09:38:12.5753666 4168 2724 DownloadManager Restoring download no. 0
2019/09/13 09:38:12.5754460 4168 2724 DownloadManager JobId = {0E018B54-02A6-496A-A6BA-12CEF4FF7DA5}, ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}
2019/09/13 09:38:12.5762955 4168 2724 DownloadManager UpdateId = B4584583-B243-4D7B-8BBA-BD07BF83BEA1.200
2019/09/13 09:38:12.5763717 4168 2724 Reporter OS Product Type = 0x00000079
2019/09/13 09:38:12.6064019 4168 2724 DownloadManager Restored download job.
2019/09/13 09:38:12.6073285 4168 2724 DownloadManager Job 0E018B54-02A6-496A-A6BA-12CEF4FF7DA5 is not expired (calculated)
2019/09/13 09:38:12.6077997 4168 2724 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2019/09/13 09:38:12.7647717 4168 5600 DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2019/09/13 09:38:12.7709409 4168 5600 DownloadManager PurgeExpiredUpdates::Found 463 non expired updates.
2019/09/13 09:38:13.6763133 4168 5600 DownloadManager PurgeExpiredUpdates::Found 8 expired updates.
2019/09/13 09:38:13.6771823 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\a4bd801f0e536884769eb693a915067d.
2019/09/13 09:38:13.6951493 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\48753d529f3eb2734adb21e35d7eb758.
2019/09/13 09:38:13.9987529 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\86b10c9d5dc07d0f644277e691551232.
2019/09/13 09:38:14.0156075 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\3b8eab9088db939137cfd5ed911a5049.
2019/09/13 09:38:14.0178087 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\e73235a3433b5263a73b3eff91dc918c.
2019/09/13 09:38:14.0343858 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\f10978b1cc63e70018ca89391b3068a0.
2019/09/13 09:38:14.0370973 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\70cf8f64a467b1a627b7aac3acf986d0.
2019/09/13 09:38:14.0396303 4168 5600 DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\windows\SoftwareDistribution\Download\e3d5b790a8a94cf311f3b292f4992a89.
2019/09/13 09:39:47.3755734 4168 2724 Agent Adding timer:
2019/09/13 09:39:47.3758810 4168 2724 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-09-14 13:39:47, not idle-only, not network-only
2019/09/13 09:40:01.6109071 4168 5600 DownloadManager Received power state change notification: Old: <unknown>; New: AC.
2019/09/13 09:40:01.6110610 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category PerUpdate.
2019/09/13 09:40:01.6110663 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category Low.
2019/09/13 09:40:01.6110740 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category Normal.
2019/09/13 09:40:01.6111597 4168 5600 DownloadManager Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Loaded sequence number 65535 for regulation category High.
2019/09/13 09:40:01.7019756 4168 5600 DownloadManager Power state changed from <unknown> to AC.
2019/09/13 09:48:12.3570675 4168 8736 Agent Earliest future timer found:
2019/09/13 09:48:12.3570887 4168 8736 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-09-14 13:39:47, not idle-only, not network-only
2019/09/13 09:48:13.3584408 4168 2724 Misc CSusClientGlobal::DoServicePreShutdown
2019/09/13 09:48:13.3585729 4168 2724 IdleTimer Idle timer disabled in preparation for service shutdown
2019/09/13 09:48:13.3585874 4168 2724 Misc WUTaskManager uninit
2019/09/13 09:48:13.3585914 4168 2724 Agent Earliest future timer found:
2019/09/13 09:48:13.3586109 4168 2724 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-09-14 13:39:47, not idle-only, not network-only
2019/09/13 09:48:13.3655323 4168 2724 Misc CreateSessionStateChangeTrigger, TYPE:2, Enable:No
2019/09/13 09:48:13.3655711 4168 2724 Misc CreateSessionStateChangeTrigger, TYPE:4, Enable:No
2019/09/13 09:48:13.5914282 4168 2724 Misc Agent uninit
2019/09/13 09:48:13.5971769 4168 2724 Misc Reporter uninit
2019/09/13 09:48:13.5974957 4168 2724 Misc network cost manager uninit
2019/09/13 09:48:13.5975248 4168 2724 Misc Eventer uninit
2019/09/13 09:48:14.5984565 4168 2724 Misc ServiceManager uninit
2019/09/13 09:48:14.5985664 4168 2724 Misc PersistentTimeoutScheduler uninit
2019/09/13 09:48:14.5985681 4168 2724 Misc datastore uninit
2019/09/13 09:48:14.6468813 4168 2724 Misc setting cache uninit
2019/09/13 09:48:14.6468843 4168 2724 Misc security checker uninit
2019/09/13 09:48:14.6468883 4168 2724 Misc Test Hook uninit
2019/09/13 09:48:14.6468890 4168 2724 Misc IdleTimer uninit
2019/09/13 09:48:14.6472488 4168 2724 Shared * END * Service exit Exit code = 0x240001
Other Server as Client:
2019-09-13 11:08:23:007 936 1348 AU #############
2019-09-13 11:08:23:007 936 1348 AU ## START ## AU: Search for updates
2019-09-13 11:08:23:007 936 1348 AU #########
2019-09-13 11:08:23:021 936 1348 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D7A30D24-8564-4445-AD6A-1B5C7D910D74}]
2019-09-13 11:08:23:021 936 1978 Agent *************
2019-09-13 11:08:23:021 936 1978 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2019-09-13 11:08:23:021 936 1978 Agent *********
2019-09-13 11:08:23:021 936 1978 Agent * Online = Yes; Ignore download priority = No
2019-09-13 11:08:23:021 936 1978 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2019-09-13 11:08:23:021 936 1978 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019-09-13 11:08:23:021 936 1978 Agent * Search Scope = {Machine}
2019-09-13 11:08:23:021 936 1978 Setup Checking for agent SelfUpdate
2019-09-13 11:08:23:053 936 1978 Setup Client version: Core: 7.6.7601.24436 Aux: 7.6.7601.24436
2019-09-13 11:08:23:099 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2019-09-13 11:08:23:233 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:237 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPC502.tmp with dwProvFlags 0x00000080:
2019-09-13 11:08:23:292 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:330 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-09-13 11:08:23:340 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:344 936 1978 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2019-09-13 11:08:23:353 936 1978 Misc Microsoft signed: NA
2019-09-13 11:08:23:379 936 1978 Setup Determining whether a new setup handler needs to be downloaded
2019-09-13 11:08:23:380 936 1978 Setup SelfUpdate handler is not found. It will be downloaded
2019-09-13 11:08:23:380 936 1978 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2019-09-13 11:08:23:419 936 1978 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2019-09-13 11:08:23:420 936 1978 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2019-09-13 11:08:23:548 936 1978 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2019-09-13 11:08:23:549 936 1978 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2019-09-13 11:08:23:723 936 1978 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2019-09-13 11:08:23:724 936 1978 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2019-09-13 11:08:24:440 936 1978 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2019-09-13 11:08:24:440 936 1978 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://myservername.server.enterprise.com:8530/ClientWebService/client.asmx
2019-09-13 11:08:24:461 936 1978 PT WARNING: Cached cookie has expired or new PID is available
2019-09-13 11:08:24:466 936 1978 PT Initializing simple targeting cookie, clientId = b3f1d818-dacc-4bd0-9230-5118f418f423, target group = Servers, DNS name = imm-srv-01.univ.pitt.edu
2019-09-13 11:08:24:466 936 1978 PT Server URL =http://myservername.server.enterprise.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2019-09-13 11:09:57:227 936 1978 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2019-09-13 11:09:57:227 936 1978 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://myservername.server.enterprise.com:8530/ClientWebService/client.asmx
2019-09-13 11:09:57:601 936 1978 Agent * Added update {BFAF434D-585E-4666-8ECC-9D4526D0B60E}.200 to search result
2019-09-13 11:09:57:601 936 1978 Agent * Added update {2641EC1C-3A24-4D10-8392-F99E50A0BDF7}.200 to search result
2019-09-13 11:09:57:601 936 1978 Agent * Found 2 updates and 82 categories in search; evaluated appl. rules of 1295 out of 2754 deployed entities
2019-09-13 11:09:57:632 936 1978 Agent *********
2019-09-13 11:09:57:632 936 1978 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2019-09-13 11:09:57:632 936 1978 Agent *************
2019-09-13 11:09:57:635 936 1f04 AU >>## RESUMED ## AU: Search for updates [CallId = {D7A30D24-8564-4445-AD6A-1B5C7D910D74}]
2019-09-13 11:09:57:635 936 1f04 AU # 2 updates detected
2019-09-13 11:09:57:635 936 1f04 AU #########
2019-09-13 11:09:57:636 936 1f04 AU ## END ## AU: Search for updates [CallId = {D7A30D24-8564-4445-AD6A-1B5C7D910D74}]
2019-09-13 11:09:57:636 936 1f04 AU #############
2019-09-13 11:09:57:636 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:09:57:636 936 1f04 AU Featured notifications is disabled.
2019-09-13 11:09:57:637 936 1f04 AU AU setting next detection timeout to 2019-09-14 11:10:32
2019-09-13 11:09:57:637 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:09:57:639 936 1f04 AU Successfully wrote event for AU health state:0
2019-09-13 11:10:02:624 936 1978 Report REPORT EVENT: {44DB017A-8D90-4799-9D9A-AE7F54FFF4FB} 2019-09-13 11:09:57:623-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 2 updates.
2019-09-13 11:10:02:624 936 1978 Report REPORT EVENT: {21786D9B-15D2-455F-A47E-F6D49BEC30BE} 2019-09-13 11:09:57:631-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2019-09-13 11:16:27:663 936 1978 Report Uploading 2 events using cached cookie, reporting URL = http://myservername.server.enterprise.com:8530/ReportingWebService/ReportingWebService.asmx
2019-09-13 11:16:27:674 936 1978 Report Reporter successfully uploaded 2 events.
WSUS Product and Classifications Settings for Windows 10 1903 Enterprise
Finally approved to get rid of Windows 7 and do hardware refresh with Windows 10 1903 Enterprise on it. Bit late in the game. I am using WSUS for patching. WSUS product and classifications settings selection for Windows 10 1903 is very confusing. There's like a dozen Windows 10 Products you can pick from. I would like to hear from experts here what are the settings that I need to choose to receive the monthly updates plus the future upgrades.
Thanks,
WSUS 3.0SP2 error : Upstream synchronization failed with OutOfMemoryException
Hi,
Since august 14, I had a synchronization Failed with Microsoft Update from my upstreamWSUS 3.0SP2 on Windows server 2008 Enterprise SP2 (x86).
With error :
OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.String.Replace(String oldValue, String newValue)
at Microsoft.UpdateServices.Internal.XmlUpdateParser.Escape(String input)
at Microsoft.UpdateServices.Internal.XmlUpdateParser.UpdateToFragments(String publishedXml, Boolean escapeFragments, ArrayList languages)
at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, String xmlSdpBlob, Int32& localRevisionId)
at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ImportUpdateWithFileUrls(Int32 upstreamServerLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, String xmlSdpBlob, ServerSyncUrlData[] fileUrls, Boolean setCatalogSiteFlag, Guid updateId)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ImportSingleUpdate(ServerSyncUpdateData updateData, List`1 allFileUrls)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ImportMultipleUpdates(List`1 metadata, List`
I’ve noticed that the OOM exception arrived each time during the synchronization when the wsusservice.exe used more than 800MB of Memory Private bytes.
So I’ve tried this :
- Increase the Virtual address space with the dos command : bcdedit /set IncreaseUserVa 3072
- Re-index the WSUS database (SUSDB) by using the SQL script from The Scripting Guys: Re-index the WSUS Database. (SUSDB on SQL server 2008 installed on a dedicated server under Windows server 2008 R2)
- Install the Hotfix for Windows Server Update Services 3.0 SP2 KB4039929 (An update to improve the performance of update metadata processing on Windows Server Update Services)
- Try different configuration for Wsuspool in IIS 6.0 (even if the process w3wp.exe never get in High CPU and High Memory)
- Try different configuration of web.config of the webservice”serversyncwebservice”.
And the synchronization were always failed.
Finally, last Friday, I found an article “WSUS synchronization fails with SoapException” (https://support.microsoft.com/en-gb/help/4482416/wsus-synchronization-fails-with-soapexception)
I changed with powershell the value of RedirectorChangeNumber from “0” to “4002",
letMUUrl with the value "https://sws.update.microsoft.com".
and the next manual synchronization was succeded and my Upstream got new Updates.
Since this correction, the automatic synchronizations at night are always succeeded but I get new errors in the SoftwareDistribution.log like this :
2019-09-17 08:20:42.595 UTC Warning w3wp.5 SoapUtilities.CreateException ThrowException: actor = http://wsusrac.intra.groupama.fr/ReportingWebService/ReportingWebService.asmx, ID=2f43c384-af40-4488-af7b-3113bb44ae3d, ErrorCode=InvalidCookie, Message=, Client=?
2019-09-17 08:20:42.595 UTC Error w3wp.5 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
So, my question is : Are the parameters RedirectorChangeNumber to 4002 and MUUrl tohttps://sws.update.microsoft.comreally good for a UPstream WSUS 3.0SP2 on Windows server 2008 Enterprise SP2 (x86) ?
UPstream server version : 3.2.7600.307 (hotfix KB2720211 + KB2828185 + KB4484071 +KB4039929 )
help
You have two Windows Server Update Services (WSUS) servers named Server1 and Server2. Server01 synchronizes from Microsoft Update. Server2 synchronizes updates from Server1.Both servers are members of the same Active Directory domain. You configure Server1 to require SSL for all WSUS metadata by using a certificate issued by an enterprise root certification authority (CA). You need to ensure that Server2 synchronizes updates from Server1. What should you do on Server2? A. From the Update Services console, modify the Update Source and Proxy Server options. B. From a command prompt, run wsusutil.exe configuresslproxy server2 443. C. From a command prompt, run wsusutil.exe configuressl server1. D. From a command prompt, run wsusutil.exe configuresslproxy server1 443.
My friend and I did not understand because mopi I chose D as a response to your opinion what is the answer
WSUS downstream server is not synchronizing with upstream server
Hi All,
I have installed windows 2016 and deployed WSUS server role, connected to upstream server. When i tried to synchronizing it was getting an error stating that " One or more errors were found when trying to import updates into the data store, and the synchronization has failed. The next synchronization will try to import the updates that were not imported i this attempt."
I was able to synchronize with microsoft with out any issues.
10022 is the event id i got in the event log.
Could you please help us in this issue ?
The WSUS Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 600000 milliseconds: Restart the service. 7031
I am having problems my WSUS is not showing under server manager after update installation, I have uninstalled all the updates and went through most forums for tricks nothing works. the error shown is
The WSUS Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 600000 milliseconds: Restart the service. 7031
Update Services failed its initialization and stopped. 507
Weird 'Skype for Business Server' update showing-up for all Windows Server 2016 computers
In my Update Services MMC, I keep getting having this weird update showing-up as available for all myservers running Windows Server 2016.
The details are:
- Name: Update Rollup for Skype for Business Server 2015, SmartSetup (KB3061064).
- Description: This package fixes issues described in KBM3061064.
- Classification: Updates
- Products: Skype for Business Server 2015, SmartSetup
I say this is "weird" because we do not have any Skype for BusinessServers. , and don't have anything Skype-related installed on any of thisWindows Server 2016 machines.
It just seems to me like it should not apply to Windows-based servers that do not already have some piece ofSkype for Business Server installed? or is that unreasonable?
Unable to Find Resource Feature upgrade to windows 10
Wsus on Windows server 2016, is configured to "do not store update locally"
I've approved Feature upgrade to windows 10 (consumer edition) ver 1809 for some pc but they all fail with error:"Unable to find resource"
I've read same article that suggests to change (od add) on IIS mime type .esd to application/octet-stream. In my case the type was already present as application/vnd.ms-cab-compressed but the changes to application/octet-stream makes no effect.
Any idea of how can I solve it?
Thank you
Alessandro Belli
alex
Update automatically attempting install, but never approved, can't even find in WSUS
On our windows 10 systems in the start menu,
there is a software called "Canon Office Printer Utility" that is showing up automatically.
After reviewing event logs, it looks like windows update is installing this software.
The strange thing is this update has not been approved in WSUS,
nor can we find any reference to this update anywhere in WSUS or on the internet.
Here is what I keep seeing in the event viewer:
Windows update started downloading an update.
Event ID:44
Source: WindowsUpdateClient
From the details tab I get:
Update Title: 9WZDNCRFJ14L-34791E63.CanonOfficePrinterUtility
Update Guid: 9D98B2CD-86D6-4D93-B462-91439272468E
We actually have the store and all apps except our approved list blocked by default, so this app never actually installs.
Would love to figure out how/why this is attempting to install when it's not in our WSUS server or anywhere else.
I've gone into the "Device installation settings" and set the option:
"Do you want to automatically download manufacturers' apps and custom icons available for your devices?"
To "NO"
However this app re-tries to install every time I uninstall it.
Any help would be greatly appreciated!
Thanks!
Sep Updates fails on Server 2008 R2 and w7
Hi,
I have a problem with one Server 2008R2.
The server is part of group of 5 that are patched monthly for years.
I spent a good time for fixing but no luck...
Here is update log file and couple of screenshots. 3 updates fails. I tried one by one. The same result.
https://1drv.ms/u/s!Av7GxVRWTkZlgixHfIt1WggKoqgb?e=1TCj5E
I deleted/recreated softwaredistribution... nothing helps. Also, I have the same behaviour on Windows 7 machine (the same exact error). Tried to fix with diag utility. NO GO.
Please see the log and may be some advise.
Thx.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
WSUS Admin Web Page returning a 404 Error
Hi all,
We're running WSUS version: 10.0.14393.2969 on Windows Server 2016. When I try to access the client.asmx page, I get the following:
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /ClientWebService/client.asmx
If I run the wsusutil.exe checkhealth, my event logs show lots of errors:
- Self Update is not working
- The server is failing to download some updates (the main console page shows 0 updates needing files though?)
- The reporting web service is not working
- The API Remoting Web Service is not working
- The Server Synchronization web service is not working
- The client web service is not working
- The SimpleAuth Web Service is not working (This is not true though, if I go to http://<wsus server>/SimpleAuthWebService/SimpleAuth.asmx it returns the Simple Auth web page
- The DSS Authentication Web Service is not working
- The WSUS content directory is not accessible. System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)
Alot of systems are updating from this server properly though, however, we are having lots of clients that can not update either. Here's an example of an error log from a Windows Server 2016 system:
2019/08/30 13:19:19.8805580 936 6116 WebServices WS error: The operation did not complete within the time allotted.
2019/08/30 13:19:19.8805829 936 6116 WebServices WS error: The operation timed out
2019/08/30 13:19:19.8805894 936 6116 WebServices Web service call failed with hr = 8024401c.
I'm confused, because I can't seem to find the IIS logs for the WSUS website, the "Logs" icon is missing from the IIS admin console? Any ideas on how to proceed with troubleshooting this issue?
WSUS Installation
Hi Guys,
can any one please help on the configuration of WSUS server .Is it fine both ad and wsus in same server
Regards,
Jaswanth
Get Synchronization history method returns wrong synchronization dates in PowerShell
Hi,
I'm executing the following PowerShell script locally on a Windows Server 2012 R2 R2 machine that has a WSUS configured (version 6.3.9600.18838) on it:
#Load required assemblies[void][reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") $wsus =[Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer() $wsus#$wsus=Get-WsusServer $sub=$wsus.GetSubscription()#get synchronization data $sub.GetSynchronizationHistory()
The result of the script returns a list of all the synchronization history of the WSUS server.
I've compared the result of the script with the synchronizations view in the Update Services Manager and I noticed that the End Time and Start Time of the synchronizations are different.
For example :
the script result is:
Id : 6cfb61f9-f230-4834-8307-70e0e7aa0c8b
StartTime : 03/08/2017 11:12:43
EndTime : 03/08/2017 11:36:46
StartedManually : True
Result : Canceled
Error : UserCanceled
ErrorText :
UpdateErrors : {}
Id : 1f27a9ad-e700-4c57-a936-dbdc726611db
StartTime : 03/08/2017 11:09:22
EndTime : 03/08/2017 11:10:38
<g class="gr_ gr_147 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="147" id="147"><g class="gr_ gr_150 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace"
data-gr-id="150" id="150">StartedManually</g> :</g> True
<g class="gr_ gr_148 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="148" id="148">Result :</g> Succeeded
Error : NotApplicable
ErrorText :
UpdateErrors : {}
but in the <g class="gr_ gr_151 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="151" id="151">syncronizations</g> view, the Started Value is: 08/09/2017 14:09 and the Finished value is: 08/09/2017 14:10
Since I'm executing the script locally on the machine, there is no timezone difference that can explain the time mismatch.
Additionally, the time difference changes from synchronization to synchronization.
Please advise how can I solve this issue or maybe this could be a bug in the method.
Thank You.