Quantcast
Channel: WSUS forum
Viewing all 12874 articles
Browse latest View live

The "fill in the blank" Web Service is not working.

$
0
0

I am running a new deployment of WSUS 3 SP2 on a Windows 2008 R2 SP 1 server for evaluation purposes.  I have SSL enabled (using standard port 443) and clients are successfully reporting to the console.  From what I can tell, everything is working.

However in the event logs I constantly see this:

13042 Self-update is not working
12002 The Reporting Web Service is not working.
12012 The API Remoting Web Service is not working.
12032 The Server Synchronization Web Service is not working.
12022 The Client Web Service is not working.
12042 The SimpleAuth Web Service is not working.
12052 The DSS Authentication Web Service is not working

Now I have done many searchs on this and seen countless hits on this topic and numerous solutions (too many to list).  Most of the posts I have seen on this (if not all) are from the 2007 2008 time frame and I assuming for the most part these are Windows 2003 in nature.  None of the solutions I have seen work for me.  So I am wondering if this is a new problem (with similar symptoms, namely the events being generated) related to Windows 2008 R2.  Or if this is even a real problem - since I have clients successfully reporting to the console.

Does anyone have any suggestions, that might be current for 2011 and Windows 2008 R2, that I might use to help resolve this "problem"?

Thanks

Nelson


Windows update (self destruct) declined. Why wont it go away?

$
0
0

Hi; this 'self destruct button' has already cost me £80 and 10 days with out my p.c.

I was delighted and relieved to see that there was now an option to 'decline' your kind offer of destroying my p.c.

I have declined it many times but the menace is still lurking; ready to be actived by the unsuspecting.

How do I really; finally and once and for all get rid of the blasted 'self destruct button'. Please.

After this massive expensive mess you have got me into once, I'm reluctant to repeat the experience.

I look forward to using another O/S in the future. Steam machine will be my next one.... this one can go live in the shed.

I'll never forgive Microsoft for installing this f' self destruct on my desktop.

Cheers ,keep up the good work.

Dom

WSUS Server

Error Connecting to WSUS Server

$
0
0

We have a 2008 R2 server that also serves as our WSUS server. When I open WSUS, it comes up with the following message:

Error: Connection Error

An error occured trying to conect the WSUS server. This error can happen for a number of reasons. Check connectivity with the server.

I copied the error to the clipboard and have posted it below. I've tried rebooting but that didn't fix it. Other ideas?

----------------------------------------------------------

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.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   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.PooledStream.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.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)

Approve a list of KB updates in a CSV file for a specific group in WSUS By using PowerShell.

$
0
0

Dears,

could you help my with script to approve a list of KB updates in a CSV file for a specific group in WSUS By using PowerShell

Group name: SERVER2008-R2-SP1 Deployment

File path: C:\temp\Update.csv

Regards.

Critical Tenable Scan finding against WSUS Windows Internal Database on Server 2008 R2

$
0
0

I receive weekly scans from the client who uses a Tenable (Nessus) scanner and this week's finding included a CRITICAL finding against the WSUS' Windows Internal Database which is installed on a 2008 R2 Datacenter server.  The finding is as follows:

"Plugin Output: 

The following unsupported installations of Microsoft SQL Server were
detected :

  Installed version         : 9.00.5000.00 (2005 SP4 (KB 2463332)) Windows Internal Database (64-bit)
  Minimum supported version : This version is no longer supported."

Yet when I search for an update the latest version I can find is the one currently installed.  Has this version of Windows Internal Database reached its EOL?  If so, when will Microsoft release an update for the Windows Internal Database that can be applied to the server?

Performance issues after KB3159706

$
0
0

I'm facing severe performance issues on the WSUS server after deploying KB3159706 AND following all the steps in https://support.microsoft.com/en-us/kb/3159706 except for the web.config part as we do not use HTTPS.

The Windows Internal Database and IIS Worker Process are taking up almost 100% of CPU all the time and around 70% of RAM.

This server has always been very stable with less than 70% RAM and idle CPU most of the time.

I noticed also this warning in the even log (#12 - Unable to find schema for config section 'system.xaml.hosting/httpHandlers'. This section will be ignored.)

Please advise

Windows is unable to connect to the Automatic Updates - How to resolve this issue?

$
0
0

Recently, Microsoft has identified a possible issue with WSUS server and Windows update clients.
These issues would occur and reflect in event logs with following event ID: 

--------------

Event ID: 16

---------------

In the WindowsUpdate.log you may see the following entries:

“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”

While going through event logs under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operationalyou may find an error event ID: 25 as follows
===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 25
Task Category: Windows Update Agent
Level: Error
Keywords: Failure, Check for Updates
User: SYSTEM
Computer: <computer name>
Description: Windows Update failed to check for updates with error 0x800b0001.
======================================

Cause:

This can be due to a version mismatch between the Windows update agent and the WSUS server. WSUS needs to be at version 3.2.7600.251 or later in order to properly communicate with clients at version 7.6.7600.256 or later.

Resolution:
Meanwhile to resolve this issue, one of the most workable troubleshooting steps listed as follows:

NOTE:
However please make sure that the issue that you try to resolve should have error 0x800b0001 and event ID 25 as shown above.
Troubleshooting steps:
1. Check windowsupdate.log in order to understand what is causing this issue.
2. If you find following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
(To understand how to access and read the Windowsupdate.log file please refer to following link –
http://support.microsoft.com/kb/902093 )
Follow the steps:
3. Stop the Automatic Update service or run command: “net stop wuauserv”.
4. Open Regedit and browse to the following Registry Key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.
5. Save a copy of this WindowsUpdate key (File / Export or Right-click / Export).
6. Delete the following registry values:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\PingID.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AccountDo
mainSid.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId
7. Close Regedit.
8. Start the Automatic Update service or run command: “net start wuauserv”.
9. On client machine, force synchronization with the WSUS Server: “wuauclt /detectnow”.
10. Now check windows update and click “Check for new updates”.
11. If a message with green bar appears indicates that issue is resolved.
12. If a message with red bar appears indicates that issue is not resolved and proceed with
further troubleshooting.
13. In command prompt run the command: “netsh winhttp show proxy” – and check for
any proxy configuration. If proxy is not configured proceed as follows.
14. Stop WIN HTTP Proxy service and windows update service and register important DLLs required for the changes to take place with following commands:

net stop WinHttpAutoProxySvc
net stop wuauserv
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s.

15. In windows registry, for following Registry Key - take a backup: "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate."
16. Delete the following registry value.
"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId”
17. Run iisreset command in command prompt to restart all IIS related services and start windows update service.
18. On the client, do force synchronization with the WSUS Server by running command: “wuauclt /detectnow”.
19. After conducting the troubleshooting steps, we checked the event logs and found following success event on the client machine under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational:

===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 30
Task Category: Windows Update Agent
Level: Information
Keywords: Connection
User: SYSTEM
Computer: <computer name>
Description: Windows Update established connectivity.
===================================

Hence this issue is resolved. No further action is required.

21. If your issue is not resolved again then apply following update on the WSUS server machine Please be sure apply this update to WSUS SERVER MACHINE

http://support.microsoft.com/kb/2734608

28. Apply this update.

29. You must restart the computer after you apply this update.
30. Start synchronization on WSUS
31. Wait for the synchronization to succeed.
32. On the affected client, open cmd.exe in elevated mode
33. Type the following commands.

Net stop wuauserv

Net start wuauserv

34. The issue would be resolved once and for all.

 Microsoft has released this update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 (SP2)

 This update strengthens the WSUS communication channels.

 The Windows Update Agent (WUA) on computers that are managed by this WSUS server will be automatically upgraded as needed after you apply this update.

 WSUS must be in a known, good working state for this update to work. If WSUS is configured to synchronize updates from Microsoft Update, make sure that WSUS can synchronize updates. And, clients must be able to communicate with the WSUS server.

 This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

Any improvements or feedback on above troubleshooting steps is surely welcome.
Thank You.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Connection Error WSUS Console

$
0
0
Hi,

When opening the WSUS console i now get the following error -

An Error occurred trying to connect the WSUS server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

In the event logs we have the event id: 7053. I can supply the whole event if needed.

Does anyone know how i might be able to resolve this?

Thanks.

WSUS stopped working

$
0
0

Hi,

After running some MS patches on the WSUS server today, the WSUS service has stopped working. I have tried to reboot the server and also delete the<user profile>\application data\microsoft\mmc, but same problem.

Im not able to browse down the WSUS hierarchy at all

In the event log I get the error:

**************************

EventID 7053

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.IndexOutOfRangeException -- Index was outside the bounds of the array.

Source
Microsoft.UpdateServices.BaseApi

Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()
   at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)
   at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.set_UserSelectedCulture(String value)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.TrySetServerCulture(String culture)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.SetServerCulture()
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools..ctor(CultureInfo culture, IUpdateServer updateServer)
   at Microsoft.UpdateServices.UI.SnapIn.Common.ServerTools..ctor(ServerSummaryScopeNode serverSummaryScopeNode, SnapInTools snapInTools, IUpdateServer updateServer)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

****************************

If I try to reset the Server Node as it say in the MMC panel it gives me this error

************************'

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.NullReferenceException -- Object reference not set to an instance of an object.

Source
Microsoft.UpdateServices.UI.SnapIn

Stack Trace:
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ResetScopeNode()

**************************

Please advice


/Regards Andreas

Target group assignment via AD security group v. OU

$
0
0

Hi all - 

I am responsible for patching about 300 Windows servers. We patch in groups (dev/prod, etc) and currently assign the respective target groups via GPO based on the OU where the computer object resides. This has worked pretty well and is transparent (easy to see where a computer 'lives' just by looking in ADUC). 

As we have now been asked to modify the schedule and add more groups, this is no longer as easy to do with the OU-based approach. The GPOs/OUs need to stay as they are because they're used for more than just patching, and I'd like to avoid creating new sub-OUs under each leaf just for this. 

I was thinking of starting to use AD security groups for the computer objects, and assign the members to the WSUS target groups via new GPOs scoped only to the AD group.

My concern is that I'm adding a manual step (adding a computer to the group) rather than letting it just be picked up based on the OU, and the transparency is somewhat lost. 

Does anyone have any pro/con lists of using AD security groups? 

Still on WSUS 3.0 on a W2008 R2 server, if that matters, although I suspect it's irrelevant. 

Thanks!

Lanwench


Lanwench ** Do not fold, spindle or mutilate. Use only a #2 pencil. Fill in the box completely and erase any stray marks.

WU Client failed searching for update with error 0x8024000b

$
0
0

We have a few workstations that are no longer reporting to WSUS. I noticed the issue while trying to deploy the latest version of Java via SolarWinds Patch Manager back in April/May. We started troubleshooting Patch Manager, but the problem appears to be with the clients/WSUS. Our environment consists of W2K8 R2 servers and Windows 7 workstations. Can someone please take a look at the below windows update log entries from today to see what is going on?

Thanks,

Chad

2016-07-1803:00:10:9581240408AUForced install timer expired for AUInstallType = 4

2016-07-1803:00:10:9581240408AUUpdateDownloadProperties: 0 download(s) are still in progress.
2016-07-1803:00:10:9581240408AUSetting AU scheduled install time to 2016-07-19 07:00:00
2016-07-1803:00:10:9581240408AUSuccessfully wrote event for AU health state:0
2016-07-1811:24:00:67212408b8AUTriggering AU detection through DetectNow API
2016-07-1811:24:00:67212408b8AUPiggybacking on an AU detection already in progress
2016-07-1812:03:35:0161240408AUAU setting next sqm report timeout to 2016-07-19 16:03:35

2016-07-1814:15:32:7551240408AUInitiating Install-at-shutdown
2016-07-1814:15:32:7551240408Shutdwnuser declined update at shutdown
2016-07-1814:15:32:7551240408AUSuccessfully wrote event for AU health state:0
2016-07-1814:15:32:7551240408AUAU initiates service shutdown
2016-07-1814:15:32:7551240408AU###########  AU: Uninitializing Automatic Updates  ###########
2016-07-1814:15:32:7551240a0cAgent * WARNING: Failed to filter search results, error = 0x8024000B
2016-07-1814:15:32:8491240a0cAgent*********
2016-07-1814:15:32:8491240a0cAgent**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-07-1814:15:32:8491240a0cAgent*************
2016-07-1814:15:32:8491240a0cAgent*************
2016-07-1814:15:32:8491240a0cAgent** START **  Agent: Finding updates [CallerId = EminentWare Extension Pack - HARTIT\linder]
2016-07-1814:15:32:8491240a0cAgent*********
2016-07-1814:15:32:8491240a0cAgent * Include potentially superseded updates
2016-07-1814:15:32:8491240a0cAgent * Online = Yes; Ignore download priority = No
2016-07-1814:15:32:8491240a0cAgent * Criteria = "DeploymentAction=*"
2016-07-1814:15:32:8491240a0cAgent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2016-07-1814:15:32:8491240a0cAgent * Search Scope = {Machine}
2016-07-1814:15:35:0191240a0cAgent * WARNING: Exit code = 0x8024000B
2016-07-1814:15:35:0191240a0cAgent*********
2016-07-1814:15:35:0191240a0cAgent**  END  **  Agent: Finding updates [CallerId = EminentWare Extension Pack - HARTIT\linder]
2016-07-1814:15:35:0191240a0cAgent*************
2016-07-1814:15:35:0191240a0cAgentWARNING: WU client failed Searching for update with error 0x8024000b
2016-07-1814:15:35:0191240408AgentSending shutdown notification to client
2016-07-1814:15:35:1901240408Service*********
2016-07-1814:15:35:1901240408Service**  END  **  Service: Service exit [Exit code = 0x240001]
2016-07-1814:15:35:1901240408Service*************
2016-07-1814:18:52:1181292e04Misc===========  Logging initialized (build: 7.6.7601.19161, tz: -0400)  ===========
2016-07-1814:18:52:1181292e04Misc = Process: C:\Windows\system32\svchost.exe
2016-07-1814:18:52:1181292e04Misc = Module: c:\windows\system32\wuaueng.dll
2016-07-1814:18:52:1181292e04Service*************
2016-07-1814:18:52:1181292e04Service** START **  Service: Service startup
2016-07-1814:18:52:1181292e04Service*********
2016-07-1814:18:52:2271292e04Agent * WU client version 7.6.7601.19161
2016-07-1814:18:52:2271292e04Agent * Base directory: C:\Windows\SoftwareDistribution
2016-07-1814:18:52:2271292e04Agent * Access type: No proxy
2016-07-1814:18:52:2271292e04Agent * Network state: Connected
2016-07-1814:19:37:8301292e04ReportCWERReporter::Init succeeded
2016-07-1814:19:37:8301292e04Agent***********  Agent: Initializing Windows Update Agent  ***********
2016-07-1814:19:37:8301292e04Agent * Prerequisite roots succeeded.
2016-07-1814:19:37:8301292e04Agent***********  Agent: Initializing global settings cache  ***********
2016-07-1814:19:37:8301292e04Agent * WSUS server: http://util2:8530
2016-07-1814:19:37:8301292e04Agent * WSUS status server: http://util2:8530
2016-07-1814:19:37:8301292e04Agent * Target group: (Unassigned Computers)
2016-07-1814:19:37:8301292e04Agent * Windows Update access disabled: No
2016-07-1814:19:37:8451292e04DnldMgrDownload manager restoring 0 downloads
2016-07-1814:19:37:8611292e04AU###########  AU: Initializing Automatic Updates  ###########
2016-07-1814:19:37:8611292e04AUAU setting next detection timeout to 2016-07-18 18:19:37
2016-07-1814:19:37:8611292e04AU # WSUS server: http://util2:8530
2016-07-1814:19:37:8611292e04AU # Detection frequency: 12
2016-07-1814:19:37:8611292e04AU # Approval type: Scheduled (Policy)
2016-07-1814:19:37:8611292e04AU # Scheduled install day/time: Every day at 3:00
2016-07-1814:19:37:8611292e04AU # Auto-install minor updates: Yes (User preference)
2016-07-1814:19:37:8611292e04AU # Will interact with non-admins (Non-admins are elevated (User preference))
2016-07-1814:19:37:8611292e04AUSetting AU scheduled install time to 2016-07-19 07:00:00
2016-07-1814:19:37:9861292e04Report***********  Report: Initializing static reporting data  ***********
2016-07-1814:19:37:9861292e04Report * OS Version = 6.1.7601.1.0.65792
2016-07-1814:19:37:9861292e04Report * OS Product Type = 0x00000030
2016-07-1814:19:37:9861292e04Report * Computer Brand = Dell Inc.
2016-07-1814:19:37:9861292e04Report * Computer Model = OptiPlex 7010
2016-07-1814:19:37:9861292e04Report * Bios Revision = A12
2016-07-1814:19:37:9861292e04Report * Bios Name = BIOS Date: 01/10/13 08:20:54 Ver: A12.00 
2016-07-1814:19:37:9861292e04Report * Bios Release Date = 2013-01-10T00:00:00
2016-07-1814:19:37:9861292e04Report * Locale ID = 1033
2016-07-1814:19:38:1411292e04AUSuccessfully wrote event for AU health state:0
2016-07-1814:19:38:1411292e04AUInitializing featured updates
2016-07-1814:19:38:1411292e04AUFound 0 cached featured updates
2016-07-1814:19:38:1411292e04AUSuccessfully wrote event for AU health state:0
2016-07-1814:19:38:1411292e04AUSuccessfully wrote event for AU health state:0
2016-07-1814:19:38:1411292e04AUAU finished delayed initialization
2016-07-1814:19:38:1411292e04AU#############
2016-07-1814:19:38:1411292e04AU## START ##  AU: Search for updates
2016-07-1814:19:38:1411292e04AU#########
2016-07-1814:19:38:1731292e04AU<<## SUBMITTED ## AU: Search for updates [CallId = {D2DB9934-2E82-43B4-8EE8-A68BB47185A8}]
2016-07-1814:19:38:4221292fe8Agent*************
2016-07-1814:19:38:4221292fe8Agent** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-07-1814:19:38:4221292fe8Agent*********
2016-07-1814:19:38:4221292fe8Agent * Online = Yes; Ignore download priority = No
2016-07-1814:19:38:4221292fe8Agent * 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"
2016-07-1814:19:38:4221292fe8Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2016-07-1814:19:38:4221292fe8Agent * Search Scope = {Machine}
2016-07-1814:19:38:4531292fe8SetupChecking for agent SelfUpdate
2016-07-1814:19:38:4531292fe8SetupClient version: Core: 7.6.7601.19161  Aux: 7.6.7601.19161
2016-07-1814:19:38:5001292fe8MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2016-07-1814:19:38:6091292fe8MiscMicrosoft signed: NA
2016-07-1814:19:38:6091292fe8MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP3C44.tmp with dwProvFlags 0x00000080:
2016-07-1814:19:38:7021292fe8MiscMicrosoft signed: NA
2016-07-1814:19:38:7491292fe8MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2016-07-1814:19:38:7491292fe8MiscMicrosoft signed: NA
2016-07-1814:19:38:7491292fe8MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2016-07-1814:19:38:7651292fe8MiscMicrosoft signed: NA
2016-07-1814:19:38:9051292fe8SetupDetermining whether a new setup handler needs to be downloaded
2016-07-1814:19:38:9051292fe8SetupSelfUpdate handler is not found.  It will be downloaded
2016-07-1814:19:38:9051292fe8SetupEvaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.320"
2016-07-1814:19:40:0121292fe8SetupSetup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.320" is already installed.
2016-07-1814:19:40:0271292fe8SetupEvaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320"
2016-07-1814:19:40:0271292fe8SetupSetup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320" is already installed.
2016-07-1814:19:40:0271292fe8SetupEvaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320"
2016-07-1814:19:40:0431292fe8SetupSetup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320" is already installed.
2016-07-1814:19:40:0431292fe8SetupSelfUpdate check completed.  SelfUpdate is NOT required.
2016-07-1814:19:41:8191292fe8PT+++++++++++  PT: Synchronizing server updates  +++++++++++
2016-07-1814:19:41:8191292fe8PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://util2:8530/ClientWebService/client.asmx
2016-07-1814:19:41:8351292fe8PTWARNING: Cached cookie has expired or new PID is available
2016-07-1814:19:41:8351292fe8PTInitializing simple targeting cookie, clientId = e2046035-f8d8-4dd6-a011-804ce2a30c7e, target group = , DNS name = cricews.hartit.net
2016-07-1814:19:41:8351292fe8PT Server URL = http://util2:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-07-1814:21:43:7061292fe8PT+++++++++++  PT: Synchronizing extended update info  +++++++++++
2016-07-1814:21:43:7061292fe8PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://util2:8530/ClientWebService/client.asmx
2016-07-1814:21:43:7411292fe8PTInitializing simple targeting cookie, clientId = e2046035-f8d8-4dd6-a011-804ce2a30c7e, target group = , DNS name = cricews.hartit.net
2016-07-1814:21:43:7411292fe8PT Server URL = http://util2:8530/SimpleAuthWebService/SimpleAuth.asmx

WSUS computer list don't display windows 10 clients

$
0
0

Hello, i have installed on a fresh windows 2012r2 image WSUS.

In Computers -> All Computers i don't saw any machine until i have tried to join a windows 7 machine.

So i can't see windows 10 in that menù but windows 7 yes.

Both machine are in the same OU and yes the GPO are applicated correctly on both machine.

Any suggestions?

Regards.

Alessio

Server 2012 R2 Client not communicating with WSUS

$
0
0

I have a WSUS server on 2012 R2 with a variety of clients. Most of my servers are reporting fine but I have two 2012 R2 servers that are not getting updates from WSUS and are not reporting status. They show up in my Target group but do not report status. I've purged the Software distribution content and ran a bunch of other tests and so far nothing has resolved the issue. If I remove the policy and point this server to Microsoft directly updates work with no issue. I have purged the windowsupdate.log and pasted the contents of the fresh log below.

2016-07-13 11:53:03:595  944  70 Misc ===========  Logging initialized (build: 7.9.9600.18340, tz: -0400)  ===========
2016-07-13 11:53:03:595  944  70 Misc   = Process: C:\Windows\system32\svchost.exe
2016-07-13 11:53:03:595  944  70 Misc   = Module: c:\windows\system32\wuaueng.dll
2016-07-13 11:53:03:595  944  70 Service *************
2016-07-13 11:53:03:595  944  70 Service ** START **  Service: Service startup
2016-07-13 11:53:03:595  944  70 Service *********
2016-07-13 11:53:03:626  944  70 IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
2016-07-13 11:53:03:626  944  70 Agent   * WU client version 7.9.9600.18340
2016-07-13 11:53:03:626  944  70 Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2016-07-13 11:53:03:626  944  70 Agent   * Base directory: C:\Windows\SoftwareDistribution
2016-07-13 11:53:03:626  944  70 Agent   * Access type: No proxy
2016-07-13 11:53:03:626  944  70 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2016-07-13 11:53:03:626  944  70 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016-07-13 11:53:03:626  944  70 Agent   * Network state: Connected
2016-07-13 11:53:03:626  944  70 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2016-07-13 11:53:03:626  944  70 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2016-07-13 11:53:03:862  944  70 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2016-07-13 11:53:03:862  944  70 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2016-07-13 11:53:03:862  944  70 DtaStor Data store successfully created
2016-07-13 11:53:03:878  944  70 Agent WARNING: could not get the auth file name 0x80070002
2016-07-13 11:53:03:878  944  70 Agent WARNING: Service Recovery: Attempting to add pending registration for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 to the data store
2016-07-13 11:53:03:878  944  70 Agent ***********  Agent: Initializing global settings cache  ***********
2016-07-13 11:53:03:878  944  70 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2016-07-13 11:53:03:878  944  70 Agent   * WSUS server:http://vault101.domain.local:8530
2016-07-13 11:53:03:878  944  70 Agent   * WSUS status server:http://vault101.domain.local:8530
2016-07-13 11:53:03:878  944  70 Agent   * Target group: Servers
2016-07-13 11:53:03:878  944  70 Agent   * Windows Update access disabled: No
2016-07-13 11:53:03:878  944  70 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2016-07-13 11:53:03:878  944  70 WuTask WuTaskManager delay initialize completed successfully..
2016-07-13 11:53:03:893  944  70 Report WARNING: Failed to initialize event uploader for new server {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with hr = 80248014.
2016-07-13 11:53:03:893  944  70 Report WARNING: Failed to initialize event uploader for new server {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} with hr = 8024043d.
2016-07-13 11:53:03:893  944  70 Report CWERReporter::Init succeeded
2016-07-13 11:53:03:893  944  70 Agent ***********  Agent: Initializing Windows Update Agent  ***********
2016-07-13 11:53:03:893  944  70 DnldMgr Download manager restoring 0 downloads
2016-07-13 11:53:03:893  944  70 AU Adding timer:
2016-07-13 11:53:03:893  944  70 AU     Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-07-14 15:53:03, not idle-only, not network-only
2016-07-13 11:53:03:893  944  70 AU ###########  AU: Initializing Automatic Updates  ###########
2016-07-13 11:53:03:893  944  70 AU AIR Mode is disabled
2016-07-13 11:53:03:893  944  70 AU   # Policy Driven Provider:http://vault101.domain.local:8530
2016-07-13 11:53:03:893  944  70 AU   # Detection frequency: 12
2016-07-13 11:53:03:893  944  70 AU   # Target group: Servers
2016-07-13 11:53:03:893  944  70 AU   # Approval type: Scheduled (Policy)
2016-07-13 11:53:03:893  944  70 AU   # Auto-install minor updates: Yes (Policy)
2016-07-13 11:53:03:893  944  70 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2016-07-13 11:53:03:893  944  70 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2016-07-13 11:53:03:893  944  70 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2016-07-13 11:53:03:893  944  70 AU Adding timer:
2016-07-13 11:53:03:893  944  70 AU     Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2016-07-14 15:53:03, not idle-only, not network-only
2016-07-13 11:53:03:893  944  70 AU AU finished delayed initialization
2016-07-13 11:53:03:893  944  70 AU Currently AUX is enabled - so not show any WU Upgrade notifications.
2016-07-13 11:53:03:909  944  70 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2016-07-13 11:53:03:909  944  70 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2016-07-13 11:53:03:909  944  70 AU Adding timer:
2016-07-13 11:53:03:909  944  70 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2016-07-13 20:33:18, not idle-only, not network-only
2016-07-13 11:53:03:909  944 37c DnldMgr Asking handlers to reconcile their sandboxes
2016-07-13 11:53:13:377  944 1b4 IdleTmr Incremented idle timer priority operation counter to 1
2016-07-13 11:53:13:377 3348 8b0 Misc ===========  Logging initialized (build: 7.9.9600.18340, tz: -0400)  ===========
2016-07-13 11:53:13:377 3348 8b0 Misc   = Process: C:\Windows\explorer.exe
2016-07-13 11:53:13:377 3348 8b0 Misc   = Module: C:\Windows\system32\wucltux.dll
2016-07-13 11:53:13:377 3348 8b0 CltUI FATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2016-07-13 11:53:13:377 3348 8b0 CltUI WARNING: RegisterNetworkCostChangeNotification: Error 80004002
2016-07-13 11:53:14:815  944 1b4 AU Triggering AU detection through DetectNow API
2016-07-13 11:53:14:815  944 1b4 AU Triggering Online detection (interactive)
2016-07-13 11:53:14:815  944 1b4 AU Adding timer:
2016-07-13 11:53:14:815  944 1b4 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2016-07-13 15:53:14, not idle-only, not network-only
2016-07-13 11:53:14:815  944  70 AU #############
2016-07-13 11:53:14:815  944  70 AU ## START ##  AU: Search for updates
2016-07-13 11:53:14:815  944  70 AU #########
2016-07-13 11:53:14:815  944  70 SLS Retrieving SLS response from server...
2016-07-13 11:53:14:815  944  70 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=762&L=en-US&P=&PT=0x8&WUA=7.9.9600.18340
2016-07-13 11:53:14:972  944  70 Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab with dwProvFlags 0x00000080:
2016-07-13 11:53:14:987  944  70 Misc  Microsoft signed: NA
2016-07-13 11:53:14:987  944  70 Misc  Infrastructure signed: Yes
2016-07-13 11:53:14:987  944  70 Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP123.tmp with dwProvFlags 0x00000080:
2016-07-13 11:53:14:987  944  70 Misc  Microsoft signed: NA
2016-07-13 11:53:14:987  944  70 Misc  Infrastructure signed: Yes
2016-07-13 11:53:14:987  944  70 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "117cab2d-82b1-4b5a-a08c-4d62dbee7782"
2016-07-13 11:53:15:003  944  70 SLS Retrieving SLS response from server...
2016-07-13 11:53:15:003  944  70 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}/x64/6.3.9600.0/0?CH=762&L=en-US&P=&PT=0x8&WUA=7.9.9600.18340&AM=0&SCV=788
2016-07-13 11:53:15:034  944  70 Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\sls.cab with dwProvFlags 0x00000080:
2016-07-13 11:53:15:034  944  70 Misc  Microsoft signed: NA
2016-07-13 11:53:15:034  944  70 Misc  Infrastructure signed: Yes
2016-07-13 11:53:15:034  944  70 Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\TMP153.tmp with dwProvFlags 0x00000080:
2016-07-13 11:53:15:050  944  70 Misc  Microsoft signed: NA
2016-07-13 11:53:15:050  944  70 Misc  Infrastructure signed: Yes
2016-07-13 11:53:15:050  944  70 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2016-07-13 11:53:15:050  944  70 Agent Caller Service Recovery successfully opted in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782
2016-07-13 11:53:15:050  944  70 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
2016-07-13 11:53:15:050  944  70 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
2016-07-13 11:53:15:050  944  70 IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 10; does use network; is not at background priority
2016-07-13 11:53:15:050  944  70 IdleTmr Incremented idle timer priority operation counter to 2
2016-07-13 11:53:15:144  944  70 Report ***********  Report: Initializing static reporting data  ***********
2016-07-13 11:53:15:144  944  70 Report   * OS Version = 6.3.9600.0.0.197008
2016-07-13 11:53:15:144  944  70 Report   * OS Product Type = 0x00000008
2016-07-13 11:53:15:144  944  70 Report   * Computer Brand = Microsoft Corporation
2016-07-13 11:53:15:144  944  70 Report   * Computer Model = Virtual Machine
2016-07-13 11:53:15:144  944  70 Report   * Platform Role = 1
2016-07-13 11:53:15:159  944  70 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
2016-07-13 11:53:15:159  944  70 Report   * Bios Revision = Hyper-V UEFI Release v1.0
2016-07-13 11:53:15:159  944  70 Report   * Bios Name = Hyper-V UEFI Release v1.0
2016-07-13 11:53:15:159  944  70 Report   * Bios Release Date = 2012-11-26T00:00:00
2016-07-13 11:53:15:159  944  70 Report   * Bios Sku Number = None
2016-07-13 11:53:15:159  944  70 Report   * Bios Vendor = Microsoft Corporation
2016-07-13 11:53:15:159  944  70 Report   * Bios Family = Virtual Machine
2016-07-13 11:53:15:159  944  70 Report   * Bios Major Release = 1
2016-07-13 11:53:15:159  944  70 Report   * Bios Minor Release = 0
2016-07-13 11:53:15:159  944  70 Report   * Locale ID = 1033
2016-07-13 11:53:15:159  944  70 Handler Calculating current update level for this session
2016-07-13 11:53:16:643  944  70 Handler WARNING: UH: 0x80070002: OpenPackage failed for Package_for_KB3000483~31bf3856ad364e35~amd64~~6.3.1.8 in CCbs::CalculateCUL
2016-07-13 11:53:17:331  944  70 Handler UH: Current cumulative update level calculated: package identity Package_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8, display name KB3000850, support URLhttp://support.microsoft.com/?kbid=3000850, timestamp 01d1a24688fbd89b
2016-07-13 11:53:17:331  944  70 Handler Done calculating current update level for this session
2016-07-13 11:53:17:596  944  70 Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-07-13 11:53:17:596  944  70 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {F7E2B80D-92AE-48AD-9D30-F39A20791BBB} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2016-07-13 11:53:17:596  944  70 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
2016-07-13 11:53:17:596  944 180 Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-07-13 11:53:17:596  944 180 Agent *************
2016-07-13 11:53:17:596  944 180 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-07-13 11:53:17:596  944 180 Agent *********
2016-07-13 11:53:17:596  944 180 Agent   * Online = Yes; Ignore download priority = No
2016-07-13 11:53:17:596  944 180 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"
2016-07-13 11:53:17:596  944 180 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2016-07-13 11:53:17:596  944 180 Agent   * Search Scope = {Machine & All Users}
2016-07-13 11:53:17:596  944 180 Agent   * Caller SID for Applicability: S-1-5-21-4047250510-1688920447-2457254329-500
2016-07-13 11:53:17:596  944 180 Agent   * RegisterService is set
2016-07-13 11:53:17:596  944 180 EP Got WSUS Client/Server URL: "http://vault101.domain.local:8530/ClientWebService/client.asmx"
2016-07-13 11:53:17:596  944 180 Setup Checking for agent SelfUpdate
2016-07-13 11:53:17:596  944 180 Setup Client version: Core: 7.9.9600.18340  Aux: 7.9.9600.18340
2016-07-13 11:53:17:596  944 180 EP Got WSUS SelfUpdate URL: "http://vault101.domain.local:8530/selfupdate"
2016-07-13 11:53:17:612  944 180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2016-07-13 11:53:17:612  944 180 Misc  Microsoft signed: NA
2016-07-13 11:53:17:612  944 180 Misc  Infrastructure signed: Yes
2016-07-13 11:53:17:612  944 180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPB66.tmp with dwProvFlags 0x00000080:
2016-07-13 11:53:17:628  944 180 Misc  Microsoft signed: NA
2016-07-13 11:53:17:628  944 180 Misc  Infrastructure signed: Yes
2016-07-13 11:53:17:628  944 180 Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
2016-07-13 11:53:17:628  944 180 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2016-07-13 11:53:17:628  944 180 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
2016-07-13 11:53:17:925  944 180 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
2016-07-13 11:53:17:925  944 180 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =http://vault101.domain.local:8530/ClientWebService/client.asmx
2016-07-13 11:53:17:925  944 180 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 11; does use network; is at background priority
2016-07-13 11:53:17:940  944 180 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 11) stopped; does use network; is at background priority
2016-07-13 11:53:17:940  944 180 PT WARNING: Cached cookie has expired or new PID is available
2016-07-13 11:53:17:940  944 180 EP Got WSUS SimpleTargeting URL: "http://vault101.domain.local:8530"
2016-07-13 11:53:17:956  944 180 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 12; does use network; is at background priority
2016-07-13 11:53:17:956  944 180 PT Initializing simple targeting cookie, clientId = 99b06ea1-dace-4c38-90bf-ceb0921c0d85, target group = Servers, DNS name = dvr.domain.local
2016-07-13 11:53:17:956  944 180 PT   Server URL = http://vault101.domain.local:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-07-13 11:53:17:956  944 180 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 12) stopped; does use network; is at background priority
2016-07-13 11:53:17:956  944 180 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started; operation # 13; does use network; is at background priority
2016-07-13 11:53:17:956  944 180 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 13) stopped; does use network; is at background priority
2016-07-13 11:53:17:972  944 180 IdleTmr WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery) started; operation # 14; does use network; is at background priority
2016-07-13 11:53:17:972  944 180 IdleTmr WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery, operation # 14) stopped; does use network; is at background priority
2016-07-13 11:53:17:972  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:17:972  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:17:972  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:17:972  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 15; does use network; is at background priority
2016-07-13 11:53:17:987  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 15) stopped; does use network; is at background priority
2016-07-13 11:53:18:003  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:18:003  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:18:003  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:18:003  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 16; does use network; is at background priority
2016-07-13 11:53:18:003  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 16) stopped; does use network; is at background priority
2016-07-13 11:53:18:018  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:18:018  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:18:018  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:18:065  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 17; does use network; is at background priority
2016-07-13 11:53:18:065  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 17) stopped; does use network; is at background priority
2016-07-13 11:53:18:081  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:18:081  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:18:081  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:18:081  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 18; does use network; is at background priority
2016-07-13 11:53:18:097  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 18) stopped; does use network; is at background priority
2016-07-13 11:53:18:518  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:18:518  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:18:518  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:18:518  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 19; does use network; is at background priority
2016-07-13 11:53:18:534  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 19) stopped; does use network; is at background priority
2016-07-13 11:53:18:550  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:18:550  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:18:550  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:18:550  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 20; does use network; is at background priority
2016-07-13 11:53:18:550  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 20) stopped; does use network; is at background priority
2016-07-13 11:53:18:581  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:18:581  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:18:581  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:18:581  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 21; does use network; is at background priority
2016-07-13 11:53:18:596  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 21) stopped; does use network; is at background priority
2016-07-13 11:53:19:128  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:128  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:128  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:409  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 22; does use network; is at background priority
2016-07-13 11:53:19:425  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 22) stopped; does use network; is at background priority
2016-07-13 11:53:19:440  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:440  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:440  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:456  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 23; does use network; is at background priority
2016-07-13 11:53:19:456  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 23) stopped; does use network; is at background priority
2016-07-13 11:53:19:471  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:471  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:471  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:518  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 24; does use network; is at background priority
2016-07-13 11:53:19:518  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 24) stopped; does use network; is at background priority
2016-07-13 11:53:19:534  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:534  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:534  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:550  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 25; does use network; is at background priority
2016-07-13 11:53:19:550  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 25) stopped; does use network; is at background priority
2016-07-13 11:53:19:596  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:596  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:596  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:596  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 26; does use network; is at background priority
2016-07-13 11:53:19:612  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 26) stopped; does use network; is at background priority
2016-07-13 11:53:19:659  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:659  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:659  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:706  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 27; does use network; is at background priority
2016-07-13 11:53:19:721  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 27) stopped; does use network; is at background priority
2016-07-13 11:53:19:862  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:19:862  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:19:862  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:19:971  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 28; does use network; is at background priority
2016-07-13 11:53:20:018  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 28) stopped; does use network; is at background priority
2016-07-13 11:53:20:237  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:20:237  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:20:237  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:20:237  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 29; does use network; is at background priority
2016-07-13 11:53:20:268  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 29) stopped; does use network; is at background priority
2016-07-13 11:53:20:346  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:20:346  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:20:346  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:20:362  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 30; does use network; is at background priority
2016-07-13 11:53:20:471  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 30) stopped; does use network; is at background priority
2016-07-13 11:53:21:018  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:21:018  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:21:018  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:21:034  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 31; does use network; is at background priority
2016-07-13 11:53:21:081  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 31) stopped; does use network; is at background priority
2016-07-13 11:53:21:284  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:21:284  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:21:284  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:21:299  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 32; does use network; is at background priority
2016-07-13 11:53:21:346  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 32) stopped; does use network; is at background priority
2016-07-13 11:53:21:565  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:21:565  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:21:581  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:21:581  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 33; does use network; is at background priority
2016-07-13 11:53:21:612  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 33) stopped; does use network; is at background priority
2016-07-13 11:53:21:753  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:21:753  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:21:753  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:21:753  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 34; does use network; is at background priority
2016-07-13 11:53:21:800  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 34) stopped; does use network; is at background priority
2016-07-13 11:53:21:956  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:21:956  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:21:956  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:21:971  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 35; does use network; is at background priority
2016-07-13 11:53:22:003  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 35) stopped; does use network; is at background priority
2016-07-13 11:53:22:174  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:22:174  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:22:174  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:22:190  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 36; does use network; is at background priority
2016-07-13 11:53:22:206  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 36) stopped; does use network; is at background priority
2016-07-13 11:53:22:315  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:22:315  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:22:315  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:22:315  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 37; does use network; is at background priority
2016-07-13 11:53:22:362  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 37) stopped; does use network; is at background priority
2016-07-13 11:53:22:534  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:22:534  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:22:534  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:23:752  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 38; does use network; is at background priority
2016-07-13 11:53:23:768  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 38) stopped; does use network; is at background priority
2016-07-13 11:53:23:862  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:23:862  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:23:862  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:23:862  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 39; does use network; is at background priority
2016-07-13 11:53:23:909  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 39) stopped; does use network; is at background priority
2016-07-13 11:53:24:112  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:24:112  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:24:112  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:24:127  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 40; does use network; is at background priority
2016-07-13 11:53:24:159  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 40) stopped; does use network; is at background priority
2016-07-13 11:53:24:299  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:24:299  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:24:299  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:24:315  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 41; does use network; is at background priority
2016-07-13 11:53:24:346  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 41) stopped; does use network; is at background priority
2016-07-13 11:53:24:471  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:24:471  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:24:471  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:24:487  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 42; does use network; is at background priority
2016-07-13 11:53:24:534  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 42) stopped; does use network; is at background priority
2016-07-13 11:53:24:737  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:24:737  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:24:737  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:24:752  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 43; does use network; is at background priority
2016-07-13 11:53:24:784  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 43) stopped; does use network; is at background priority
2016-07-13 11:53:24:909  944 180 Agent Reading cached app categories using lifetime 604800 seconds
2016-07-13 11:53:24:909  944 180 Agent Read 0 cached app categories
2016-07-13 11:53:24:909  944 180 Agent SyncUpdates adding 0 visited app categories
2016-07-13 11:53:24:909  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 44; does use network; is at background priority
2016-07-13 11:53:24:924  944 180 WS WARNING: Nws Failure: errorCode=0x803d0013
2016-07-13 11:53:24:924  944 180 WS WARNING: The body of the received message contained a fault.
2016-07-13 11:53:24:924  944 180 WS WARNING: Soap fault info:
2016-07-13 11:53:24:924  944 180 WS WARNING: reason: Fault occurred
2016-07-13 11:53:24:924  944 180 WS WARNING: code: Server
2016-07-13 11:53:24:924  944 180 WS WARNING: detail: <detail><ErrorCode>InternalServerError</ErrorCode><Message></Message><ID>0d6fdc1e-4ad6-49c4-abd5-7048a9bfbbf1</ID><Method>"</detail">http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>
2016-07-13 11:53:24:924  944 180 WS FATAL: OnCallFailure failed with hr=0X80244007
2016-07-13 11:53:24:924  944 180 PT WARNING: PTError: 0x80244007
2016-07-13 11:53:24:924  944 180 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244007
2016-07-13 11:53:24:924  944 180 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 44) stopped; does use network; is at background priority
2016-07-13 11:53:24:924  944 180 PT   + SyncUpdates round trips: 30
2016-07-13 11:53:24:924  944 180 PT WARNING: Sync of Updates: 0x80244007
2016-07-13 11:53:24:924  944 180 PT WARNING: SyncServerUpdatesInternal failed: 0x80244007
2016-07-13 11:53:24:924  944 180 Agent   * WARNING: Failed to synchronize, error = 0x80244007
2016-07-13 11:53:24:940  944 180 Agent   * WARNING: Exit code = 0x80244007
2016-07-13 11:53:24:940  944 180 Agent *********
2016-07-13 11:53:24:940  944 180 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-07-13 11:53:24:940  944 180 Agent *************
2016-07-13 11:53:24:940  944 180 Agent WARNING: WU client failed Searching for update with error 0x80244007
2016-07-13 11:53:24:940  944 180 IdleTmr WU operation (CSearchCall::Init ID 1, operation # 10) stopped; does use network; is not at background priority
2016-07-13 11:53:24:940  944 180 IdleTmr Decremented idle timer priority operation counter to 1
2016-07-13 11:53:24:940  944 378 AU >>##  RESUMED  ## AU: Search for updates [CallId = {F7E2B80D-92AE-48AD-9D30-F39A20791BBB} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2016-07-13 11:53:24:940  944 378 AU   # WARNING: Search callback failed, result = 0x80244007
2016-07-13 11:53:24:940  944 378 AU #########
2016-07-13 11:53:24:940  944 378 AU ##  END  ##  AU: Search for updates  [CallId = {F7E2B80D-92AE-48AD-9D30-F39A20791BBB} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2016-07-13 11:53:24:940  944 378 AU #############
2016-07-13 11:53:24:940  944 378 AU All AU searches complete.
2016-07-13 11:53:24:940  944 378 AU   # WARNING: Failed to find updates with error code 80244007
2016-07-13 11:53:24:940  944 378 AU Adding timer:
2016-07-13 11:53:24:940  944 378 AU     Timer: 143FB093-8AA1-4DBC-A582-8806F8F4C1F7, Expires 2016-07-14 16:38:43, not idle-only, not network-only
2016-07-13 11:53:24:940  944 378 AU AU setting next detection timeout to 2016-07-13 20:53:24
2016-07-13 11:53:24:940  944 378 AU Adding timer:
2016-07-13 11:53:24:940  944 378 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2016-07-13 20:53:24, not idle-only, not network-only
2016-07-13 11:53:24:940  944 378 AU Currently AUX is enabled - so not show any WU Upgrade notifications.
2016-07-13 11:53:24:940  944 378 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2016-07-13 11:53:24:940  944 378 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037


Vincent Sprague

same old story - WSUS upstream/downstream servers

$
0
0

after going through dozens of sites I still can't find a proper solution for the following problem:

upstream server shows all downstream servers inside the wsus console;

downstream server a has a total of 69% installed/not applicable

downstream server b has a total of 76% installed/not applicable

downstream server c & d have 0% installed/not applicable

how do i get these informations of server c & d?

everything else works fine; approving, assigning, downloading content, reporting also!


WSUS can it manage update from W10 insider (channel slow & fast) ?

$
0
0

Hi everyone,

It's not very clear, i didn't found any informations that concern this updates W10 Insider with WSUS.

Regards,

Windows Server 2012 R2 WSUS support with SQL Always on?

$
0
0

Hi Team,

We are in a planning stage for WSUS deployment  for patching servers and client machines.

We have plan to host WSUS DB on SQL 2014 SP1 but i am stuck if WSUS DB supports 'Always On' (Always On Availability groups)? Any pointers will be appreciated.

Regards,

Windows 10 Updates not Installing Manually

$
0
0

My environment is configured with WSUS and I’m using Win 10 Pro, while I try to install windows update manually it’s not installing. After restart “we couldn't complete the updates undoing changes” and back to old version. May I know what might be the issue

Same thing is working in Non-Domain Machines. 


Regards, Hari Prasad.D

WSUS 3.0 - possible to manually approve patches for download, but *not* install?

$
0
0

Hi all - 

I'm exploring some new ways to deploy patches to Windows computers. We've been using approvals with deadlines to try to effect a maintenance window of sorts for patching on our servers. We review the patches, approve the ones we want, and then set different deadlines per WSUS target group. This has been a bit buggy in that there's little visibility within WSUS itself as to what's happening on the clients, updates/reports from the clients are slow to appear in the console, and a failed update may not get caught (and hence will install itself at a later time, outside of the window).

I'd like to use a third party tool (BatchPatch, which uses PSEXEC) to invoke the actual patch installation on the target computers, but retain the same review/approval process in WSUS beforehand, so that the updates are downloaded and waiting for installation. BatchPatch will allow me to run quick/realtime status checks on the servers, check pending reboots, and force reinstall, etc., as needed.

I don't care so much about the deadlines (i.e., if a deadline can't be used for a download only, but must involve actual installation, I don't want a deadline), but the approval is critical. 

Requirements:

a) The exact same group of updates must be approved / downloaded on all computers in all target groups (meaning we would run the approval once a month)

b) No updates may be installed outside of the scheduled maintenance window (which we will trigger manually)

Advice?

Thanks,

LW


Lanwench ** Do not fold, spindle or mutilate. Use only a #2 pencil. Fill in the box completely and erase any stray marks.

Updates not autoinstalling

$
0
0

Our WSUS deploys updates to our Domain joined servers. Setting is down with group policy, setting is "4 - Auto download and schedule the install".

Updates are downloaded but stay on "update is available". We then do a install manually but it would be nice if this went automatically. Now I have to click the install button on over a 100 servers

Viewing all 12874 articles
Browse latest View live