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

WSUS and Windows Defender Definition Update Issue

July 8, 2019, 5:34 am
$
0
0

Hello,

I run the WSUS service and have someone with a Windows Server 2019 box that is running Windows Defender and when they run updates they are able to get all other Windows Updates but the Definition Updates for Defender constantly fail with 80248007. We have tried updating from Windows Update and from within Defender. 

On the WSUS Server, the Definition Updates are approved for Install, and I was able to view the logs on the 2019 Server and it appeared the updates were downloading then failing to install. I have had them manually install the definition updates and they work fine. We have tried everything I can think of like resetting windows updates, removing his box from the WSUS server, removing and reinstalling defender and they still fail. I have attempted to go through a number of different TechNet forums to help resolve this issue.

I am now at a loss of how to proceed with getting him fixed. Has anyone ever come across this? Are there any suggestions on how to fix?

Thanks,

Ryan

↧
Search

Disk cleanup spins on Windows Update screen after reboot

January 29, 2018, 7:16 am
$
0
0
I ran the Windows Disk Cleanup wizard on a 2008 R2 machine and cleaned up the WIndows Update files, Temporary files, and Recycle Bin.  After rebooting the machine, during start up it went through the motions as though Windows Updates had applied (i.e. "Configuring Windows Updates") it got to 100% and stayed there for hours.  I had to use psexec to go in, stop the process, got into the machine, rebooted a couple times and the problem no longer occurred.  Is this a common occurrence?  Were there some files that I missed or shouldn't have deleted to cause such a hang?  We're hoping to roll out a solution to clean up the Windows Update and SxS folders on 2008 R2 and are hoping Disk Cleanup will work for us, so hoping this is a one off.
↧
↧

How to perform SQL query over WID database using PowerShell ?

July 25, 2019, 5:21 am
$
0
0

Hi, I'm using PowerShell and would like to perform SQL query to WSUS server which is using WID database.

I connected to DB with this commands

[void][reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
$wsus=[Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer("WSUSSERVER",$false,"8530")
$db = $wsus.GetDatabaseConfiguration().CreateConnection()
$db.connect()

And what now ? How can I now query the DB using SQL ?
Please if you could provide an example how to do that - let's say an example how to get something fromvUpdate VIEW.

Thank you.


↧

2012r2 client that will not report in to Wsus (not yet reported)

July 26, 2019, 12:57 am
$
0
0

Hope someone can help i have a 2012r2 client that will not report in to Wsus (not yet reported)

Tried resetting the windows update components, renaming the software distribution folder, ran Bret's script (resetting components. and adams script https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly

group policys are correct and show the wsus.domain.local in the registry, and can ping and nslook up the server, firewall is off and on , no difference.

also rebooted and added and removed server from wsus. 

i will post the windows update log, see if anyone can decipher this for me

2019-07-26	07:15:34:615	 924	a20	Report	CWERReporter finished handling 1 events. (00000000)
2019-07-26	07:17:15:636	 924	a20	EP	Got WSUS Client/Server URL: "http://wsus.Domain.local:8530/ClientWebService/client.asmx"
2019-07-26	07:17:15:971	 924	a20	EP	Got WSUS Reporting URL: "http://wsus.Domain.local:8530/ReportingWebService/ReportingWebService.asmx"
2019-07-26	07:17:15:971	 924	a20	Report	OpenReportingWebServiceConnection, reporting URL = http://wsus.Domain.local:8530/ReportingWebService/ReportingWebService.asmx
2019-07-26	07:17:15:971	 924	a20	IdleTmr	WU operation (CLegacyEventUploader::HandleEvents) started; operation # 426; does use network; is at background priority
2019-07-26	07:17:15:971	 924	a20	Report	Uploading 1 events using cached cookie.
2019-07-26	07:17:15:979	 924	a20	Report	Reporter successfully uploaded 1 events.
2019-07-26	07:17:15:979	 924	a20	IdleTmr	WU operation (CLegacyEventUploader::HandleEvents, operation # 426) stopped; does use network; is at background priority
2019-07-26	07:20:23:978	 924	179c	AU	Triggering AU detection through DetectNow API
2019-07-26	07:20:23:978	 924	179c	AU	Triggering Online detection (non-interactive)
2019-07-26	07:20:23:978	 924	179c	AU	Adding timer: 
2019-07-26	07:20:23:978	 924	179c	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-07-26 06:20:23, not idle-only, not network-only
2019-07-26	07:20:24:005	 924	2a4	AU	#############
2019-07-26	07:20:24:005	 924	2a4	AU	## START ##  AU: Search for updates
2019-07-26	07:20:24:005	 924	2a4	AU	#########
2019-07-26	07:20:24:006	 924	2a4	EP	FATAL: EP: CSLSEndpointProvider::GetWUClientData - failed to get SLS data, error = 0x8024500C
2019-07-26	07:20:24:006	 924	2a4	EP	FATAL: EP: CSLSEndpointProvider::GetEndpointFromSLS - Failed to get client data, error = 0x8024500C
2019-07-26	07:20:24:006	 924	2a4	EP	FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x8024500C
2019-07-26	07:20:24:006	 924	2a4	Agent	WARNING: Failed to obtain the authorization cab URL for service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0
2019-07-26	07:20:24:006	 924	2a4	Agent	FATAL: Caller Service Recovery failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0X8024500C
2019-07-26	07:20:24:007	 924	2a4	IdleTmr	WU operation (CSearchCall::Init ID 10) started; operation # 429; does use network; is not at background priority
2019-07-26	07:20:24:007	 924	2a4	IdleTmr	Incremented idle timer priority operation counter to 2
2019-07-26	07:20:24:007	 924	2a4	Agent	*** START ***  Queueing Finding updates [CallerId = Windows Update Command Line  Id = 10]
2019-07-26	07:20:24:007	 924	2a4	AU	<<## SUBMITTED ## AU: Search for updates  [CallId = {B790B361-ECC8-4A4E-AB60-E5240DD8DF6A} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2019-07-26	07:20:24:007	 924	1700	Agent	***  END  ***  Queueing Finding updates [CallerId = Windows Update Command Line  Id = 10]
2019-07-26	07:20:24:007	 924	1700	Agent	*************
2019-07-26	07:20:24:007	 924	1700	Agent	** START **  Agent: Finding updates [CallerId = Windows Update Command Line  Id = 10]
2019-07-26	07:20:24:008	 924	1700	Agent	*********
2019-07-26	07:20:24:008	 924	1700	Agent	  * Online = Yes; Ignore download priority = No
2019-07-26	07:20:24:008	 924	1700	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-07-26	07:20:24:008	 924	1700	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019-07-26	07:20:24:008	 924	1700	Agent	  * Search Scope = {Machine & All Users}
2019-07-26	07:20:24:008	 924	1700	Agent	  * Caller SID for Applicability: S-1-5-18
2019-07-26	07:20:24:008	 924	1700	Agent	  * RegisterService is set
2019-07-26	07:20:24:008	 924	1700	EP	Got WSUS Client/Server URL: "http://wsus.Domain.local:8530/ClientWebService/client.asmx"
2019-07-26	07:20:28:826	 924	1700	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
2019-07-26	07:20:28:826	 924	1700	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus.Domain.local:8530/ClientWebService/client.asmx
2019-07-26	07:20:28:875	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:28:875	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:28:875	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:30:168	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 430; does use network; is at background priority
2019-07-26	07:20:30:575	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 430) stopped; does use network; is at background priority
2019-07-26	07:20:32:832	 924	a20	Report	WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2019-07-26	07:20:35:062	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:35:062	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:35:062	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:35:100	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 431; does use network; is at background priority
2019-07-26	07:20:35:386	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 431) stopped; does use network; is at background priority
2019-07-26	07:20:37:892	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:37:892	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:37:892	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:37:930	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 432; does use network; is at background priority
2019-07-26	07:20:38:168	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 432) stopped; does use network; is at background priority
2019-07-26	07:20:40:463	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:40:464	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:40:464	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:40:500	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 433; does use network; is at background priority
2019-07-26	07:20:40:733	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 433) stopped; does use network; is at background priority
2019-07-26	07:20:42:684	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:42:684	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:42:684	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:42:725	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 434; does use network; is at background priority
2019-07-26	07:20:42:976	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 434) stopped; does use network; is at background priority
2019-07-26	07:20:45:169	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:45:169	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:45:169	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:45:206	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 435; does use network; is at background priority
2019-07-26	07:20:45:404	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 435) stopped; does use network; is at background priority
2019-07-26	07:20:47:053	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:47:053	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:47:053	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:47:089	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 436; does use network; is at background priority
2019-07-26	07:20:47:307	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 436) stopped; does use network; is at background priority
2019-07-26	07:20:49:074	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:49:075	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:49:075	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:49:111	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 437; does use network; is at background priority
2019-07-26	07:20:49:371	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 437) stopped; does use network; is at background priority
2019-07-26	07:20:51:716	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:51:716	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:51:716	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:51:754	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 438; does use network; is at background priority
2019-07-26	07:20:51:972	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 438) stopped; does use network; is at background priority
2019-07-26	07:20:53:993	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:53:993	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:53:994	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:54:030	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 439; does use network; is at background priority
2019-07-26	07:20:54:261	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 439) stopped; does use network; is at background priority
2019-07-26	07:20:55:937	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:55:938	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:55:938	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:55:978	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 440; does use network; is at background priority
2019-07-26	07:20:56:201	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 440) stopped; does use network; is at background priority
2019-07-26	07:20:58:392	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:20:58:392	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:20:58:392	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:20:58:430	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 441; does use network; is at background priority
2019-07-26	07:20:58:680	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 441) stopped; does use network; is at background priority
2019-07-26	07:21:01:016	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:01:017	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:01:017	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:01:059	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 442; does use network; is at background priority
2019-07-26	07:21:01:379	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 442) stopped; does use network; is at background priority
2019-07-26	07:21:03:670	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:03:670	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:03:670	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:03:716	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 443; does use network; is at background priority
2019-07-26	07:21:03:964	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 443) stopped; does use network; is at background priority
2019-07-26	07:21:06:301	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:06:301	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:06:301	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:06:342	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 444; does use network; is at background priority
2019-07-26	07:21:06:638	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 444) stopped; does use network; is at background priority
2019-07-26	07:21:09:265	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:09:266	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:09:266	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:09:312	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 445; does use network; is at background priority
2019-07-26	07:21:09:540	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 445) stopped; does use network; is at background priority
2019-07-26	07:21:13:219	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:13:219	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:13:219	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:13:256	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 446; does use network; is at background priority
2019-07-26	07:21:13:655	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 446) stopped; does use network; is at background priority
2019-07-26	07:21:37:660	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:37:660	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:37:661	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:37:697	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 447; does use network; is at background priority
2019-07-26	07:21:37:953	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 447) stopped; does use network; is at background priority
2019-07-26	07:21:41:103	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:41:103	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:41:103	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:41:136	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 448; does use network; is at background priority
2019-07-26	07:21:41:848	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 448) stopped; does use network; is at background priority
2019-07-26	07:21:49:777	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:49:777	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:49:777	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:49:815	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 449; does use network; is at background priority
2019-07-26	07:21:50:070	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 449) stopped; does use network; is at background priority
2019-07-26	07:21:51:842	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:51:842	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:51:842	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:51:881	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 450; does use network; is at background priority
2019-07-26	07:21:52:502	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 450) stopped; does use network; is at background priority
2019-07-26	07:21:55:354	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:55:354	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:55:354	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:55:393	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 451; does use network; is at background priority
2019-07-26	07:21:55:617	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 451) stopped; does use network; is at background priority
2019-07-26	07:21:57:201	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:57:201	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:57:201	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:57:237	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 452; does use network; is at background priority
2019-07-26	07:21:57:451	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 452) stopped; does use network; is at background priority
2019-07-26	07:21:59:393	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:59:393	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:59:394	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:59:429	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 453; does use network; is at background priority
2019-07-26	07:21:59:494	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 453) stopped; does use network; is at background priority
2019-07-26	07:21:59:494	 924	1700	Agent	Reading cached app categories using lifetime 604800 seconds
2019-07-26	07:21:59:494	 924	1700	Agent	Read 0 cached app categories
2019-07-26	07:21:59:494	 924	1700	Agent	SyncUpdates adding 0 visited app categories
2019-07-26	07:21:59:530	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 454; does use network; is at background priority
2019-07-26	07:21:59:581	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 454) stopped; does use network; is at background priority
2019-07-26	07:21:59:581	 924	1700	PT	  + SyncUpdates round trips: 25
2019-07-26	07:23:03:174	 924	1700	PT	+++++++++++  PT: Synchronizing extended update info  +++++++++++
2019-07-26	07:23:03:174	 924	1700	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus.Domain.local:8530/ClientWebService/client.asmx
2019-07-26	07:23:03:211	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 455; does use network; is at background priority
2019-07-26	07:23:03:684	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 455) stopped; does use network; is at background priority
2019-07-26	07:23:03:685	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 456; does use network; is at background priority
2019-07-26	07:23:04:294	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 456) stopped; does use network; is at background priority
2019-07-26	07:23:04:294	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 457; does use network; is at background priority
2019-07-26	07:23:05:006	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 457) stopped; does use network; is at background priority
2019-07-26	07:23:05:006	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 458; does use network; is at background priority
2019-07-26	07:23:05:596	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 458) stopped; does use network; is at background priority
2019-07-26	07:23:05:596	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 459; does use network; is at background priority
2019-07-26	07:23:06:299	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 459) stopped; does use network; is at background priority
2019-07-26	07:23:06:300	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 460; does use network; is at background priority
2019-07-26	07:23:06:768	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 460) stopped; does use network; is at background priority
2019-07-26	07:23:06:768	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 461; does use network; is at background priority
2019-07-26	07:23:07:040	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 461) stopped; does use network; is at background priority
2019-07-26	07:23:07:040	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 462; does use network; is at background priority
2019-07-26	07:23:07:332	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 462) stopped; does use network; is at background priority
2019-07-26	07:23:07:332	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 463; does use network; is at background priority
2019-07-26	07:23:07:759	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 463) stopped; does use network; is at background priority
2019-07-26	07:23:07:759	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 464; does use network; is at background priority
2019-07-26	07:23:08:107	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 464) stopped; does use network; is at background priority
2019-07-26	07:23:08:107	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 465; does use network; is at background priority
2019-07-26	07:23:08:492	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 465) stopped; does use network; is at background priority
2019-07-26	07:23:08:492	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 466; does use network; is at background priority
2019-07-26	07:23:09:124	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 466) stopped; does use network; is at background priority
2019-07-26	07:23:09:124	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 467; does use network; is at background priority
2019-07-26	07:23:09:782	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 467) stopped; does use network; is at background priority
2019-07-26	07:23:09:782	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 468; does use network; is at background priority
2019-07-26	07:23:10:452	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 468) stopped; does use network; is at background priority
2019-07-26	07:23:10:452	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 469; does use network; is at background priority
2019-07-26	07:23:11:343	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 469) stopped; does use network; is at background priority
2019-07-26	07:23:11:343	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 470; does use network; is at background priority
2019-07-26	07:23:12:082	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 470) stopped; does use network; is at background priority
2019-07-26	07:23:12:082	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 471; does use network; is at background priority
2019-07-26	07:23:12:748	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 471) stopped; does use network; is at background priority
2019-07-26	07:23:12:749	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 472; does use network; is at background priority
2019-07-26	07:23:13:113	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 472) stopped; does use network; is at background priority
2019-07-26	07:23:13:113	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 473; does use network; is at background priority
2019-07-26	07:23:13:532	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 473) stopped; does use network; is at background priority
2019-07-26	07:23:13:532	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 474; does use network; is at background priority
2019-07-26	07:23:13:998	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 474) stopped; does use network; is at background priority
2019-07-26	07:23:13:998	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 475; does use network; is at background priority
2019-07-26	07:23:14:551	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 475) stopped; does use network; is at background priority
2019-07-26	07:23:14:551	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 476; does use network; is at background priority
2019-07-26	07:23:15:109	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 476) stopped; does use network; is at background priority
2019-07-26	07:23:15:109	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 477; does use network; is at background priority
2019-07-26	07:23:16:162	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 477) stopped; does use network; is at background priority
2019-07-26	07:23:16:162	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 478; does use network; is at background priority
2019-07-26	07:23:16:847	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 478) stopped; does use network; is at background priority
2019-07-26	07:23:16:847	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 479; does use network; is at background priority
2019-07-26	07:23:17:542	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 479) stopped; does use network; is at background priority
2019-07-26	07:23:17:542	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 480; does use network; is at background priority
2019-07-26	07:23:18:038	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 480) stopped; does use network; is at background priority
2019-07-26	07:23:18:038	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 481; does use network; is at background priority
2019-07-26	07:23:18:306	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 481) stopped; does use network; is at background priority
2019-07-26	07:23:18:306	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 482; does use network; is at background priority
2019-07-26	07:23:18:653	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 482) stopped; does use network; is at background priority
2019-07-26	07:23:18:653	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 483; does use network; is at background priority
2019-07-26	07:23:19:284	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 483) stopped; does use network; is at background priority
2019-07-26	07:23:19:284	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 484; does use network; is at background priority
2019-07-26	07:23:19:741	 924	1700	IdleTmr	WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 484) stopped; does use network; is at background priority


↧

Allow .Net Framework 3.5 installation on Windows 10 through WSUS

April 7, 2016, 2:32 pm
$
0
0

Hi all,

We have a single domain, with a WSUS 3.0 Server running on W2008R2.

We have domain-joined machines running Windows 10 Pro.

Those machines get their updates normally through that WSUS server, and the rest of them (W7, W8.1) too.

We have the products "Windows 10" and "Windows 10 Feature on Demand" checked on WSUS.

We have approved ".Net 3.5 Feature on Demand for X64" and ".Net 3.5 Feature on Demand for X86" on WSUS.

Our issue is: when a user goes to Programs and Features on Windows 10, and tries to activate .Net Framework 3.5, he receives error 0x800F081F.

A network capture shows the machine is trying to contact our WSUS server for this, not Windows Update.

My questions are:

  • Is there any way to allow users to install .Net Framework 3.5 on Windows 10 from WSUS?
  • Does it work on W2008R2-based WSUS? Or only on W2012R2?
  • Are those ".Net 3.5 Feature on Demand for XXX" updates the correct ones we have to approve to make it work?
  • Is going to Control Panel - Programs and Features and checking .Net Framework 3.5 the correct way to install it on Windows 10 through WSUS?
  • If .Net Framework 3.5 can't be deployed to Windows 10 through WSUS, how can we make it contact Windows Update for it? We have the GPO policy setting "contact Windows Update directly" set but it looks like Windows 10 ignores it (8.1 works though).

Thanks in advance, 

José


↧
↧

WSUS postinstall error

July 27, 2019, 5:58 am
$
0
0

i installed WSUS but when i tried to do the post installation steps

i got this error 

 CreateDefaultSubscription failed. Exception: System.Security.SecurityException: Request for principal permission failed.
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
The Zone of the assembly that failed was:
MyComputer
2019-07-27 15:47:16  StartServer encountered errors. Exception=Request for principal permission failed.
2019-07-27 15:47:16  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

 
↧

SCCM server 2012 device collection Patch updates change tracking

July 27, 2019, 7:32 pm
$
0
0

Hi

We are having SCCM server 2012 in our environment, someone changed/altered patch updates collection which caused unapproved servers reboot maintenance. 

We need to know who changed patch updates group changes:

Assets and Compliance >> Device Collections >> Patch Updates

is there any way to know who changed it? 

MD

↧

Download failure

July 28, 2019, 10:28 am
$
0
0

Server 2012 R2 Std

WSUS

WSUS stopped downloading updates. It was working for years. I made no change except usual server updates:

I have tried  "retry download" but it still fails.

How do I get downloading working again?

John Lenz

↧
Search

SQL superseding

July 16, 2019, 11:56 pm
$
0
0

Hi,

i am seraching for an SQL statement which shows me the updates which are supersed by the current update.

see the picture.

red: Update ID

blue: i want to know the update ID of thoses two updates

↧
↧

Strange SSL problem

July 29, 2019, 3:08 am
$
0
0

Hi,

We had WSUS on Windows Server 2016 some weeks ago with SSL which working fine.

We have reinstalled our server from scratch recently.

The only difference is that domain server name is not the FQDN used to access it (and used by SSL too).

Clients can connect to the server without error. WSUS console says that SSL certificate can't be verified.

All necessary config (wsusutil, iis) has been done.

The certificate is a commercial and fully recognized certificate (but we have imported CA root just in case).

The event log says error 12012 (API not functionning).

As the certificate is ok, we can't understand why console is not running.

I've tried accessing WSUS using Url https://FQDN:8531/WSUSAdmin, but I've got a blank page. Perhaps it's an error 500, but where can I find the logs ?

Have you some idea about this strange thing ?

Thanks for your help

↧

Server 2019, WSUS MMC Snap-in: Increase timeout?

March 19, 2019, 1:29 am
$
0
0

I have a brand new Windows 2019 running a basic WSUS install in a virtual machine with two Xeon 3.5 ghz vCPUs, 8 gig of memory.

It is a fully default WSUS install using the Windows Internal Database SQL server, and the default language and product options. I ran the synchronization. Nothing has been approved, no computers are joined. Everything is working normally.

I am unable to view the synchronization status because the Windows Internal Database SQL engine is taking too long to respond to the MMC snap-in.

How can the snap-in timeout be increased? I have thoroughly searched C:\Program Files\Update Services and I can not find any MMC configuration files where there is a timeout option that can be adjusted.

WSUS for Windows Server 2019 appears to be broken as designed.

,

Steps to reproduce:

1. Open WSUS MMC management snap-in. Open Task Manager, says 0-5% CPU load.

2. Click on Synchronizations in WSUS MMC.

3. It says at bottom "Loading synchronization history, 0% complete"

4. Windows task manager suddenly shows 50% CPU usage across the two vCPU's (really, just 100% load for 1 CPU).

5. After about 5 minutes pass, the MMC snap-in is unhappy and claims it can't reach WSUS. Task manager continues to show 50% CPU usage across the two vCPU's for several more minutes by SQLServr.exe.

6. WID-SQL server eventually finishes whatever it was doing, and Task Manager drops to about 0-5% system load.

7. Can't do anything with the MMC after the internal database has stopped chugging along for 7-10 minutes now. The only option available is to "Reset Server Node," which discards anything that has been retrieved so far. 

8. Go back to Step 2 and do this all over again several more times. No change.

9. Stop VM, increase memory from 8 gb to 16 gb, start VM. This memory increase has no effect. The WSUS MMC still times out trying to load the synchronization history.

,

Is there any way to increase the Server 2019 WSUS MMC snap-in timeout, or am I being indirectly forced by Microsoft to buy a full license for Microsoft SQL Server, because the Windows internal database is too slow and low performance, to respond to the MMC snap-in within 5 minutes?


↧

The update failed to download

July 30, 2019, 4:04 am
$
0
0

Hello,

I'm trying to download feature update to Windows 10,1903, downloading file stuck and give me "the update failed to download". even though that other files downloads without any issue but this file.

My WSUS server version: 3.2.7600.274

↧

W2008 - W2016

July 30, 2019, 5:08 am
$
0
0

Hi All,

We are going to upgrade some of our W2008 WSUS servers to W2016. All are downstream servers.

I would like to know if anyone has gone through this process before and what it entails. I envisage building a W2016 server and installing\configuring the WSUS role. Then synchronizing with the upstream server to populate the database. Ensure that any GPO's are pointing to the correct server etc.

Has anyone been through this process and can offer any advice.

Regards.

↧
↧

No contact to WSUS server when logged in as guest (Windows 10)

July 30, 2019, 6:38 am
$
0
0

We are making use of guest accounts as a means of getting a clean start each time the computer is logged in (this is at a library).  It works well; however, we've realized that the computers are not contacting the WSUS server (they automatically log on).  If I turn off autologon, they start to work.

I came across this link from 2013 about updates being disabled as guest, which makes sense if THEY are trying to run them; however, we are trying to have them run from a group policy that applies to the computer, not the user, so it seems that it should still work, regardless of what user is logged in.  The same policy applies fine to computers logged in with accounts that are not guest.

Any suggestions for sure of what could be causing this and if there is a solution?

Thank you

↧

Upgrading WSUS from 3.0 SP2 to 4.0 (Windows Server 2012) and re-enabling SSL

September 18, 2012, 5:48 pm
$
0
0

Hi all

Our WSUS 3.0 SP2 server was running on W2K8 R2, using a database on a remote SQL server and using SSL with 80/443 ports (not tcp/853n ports). Last week I upgraded the server to 2012. In order to upgrade, I had to uninstall WSUS on W2K8 R2, then run the OS upgrade, and add the "Windows Update Services" role. During the role installation, I was able tode-select WID (Windows Internal Database) and add the "Database" role service instead. I then was asked for the name/instance of the SQL server. After granting my current login sysadmin/securityadmin rights in the SQL server login, WSUS seemed to do some DB-maintenance and then was up and running - but [Edit 2012/09/19] on the default port and with no SSL[End Edit]. The certificate used previously (from AD) was still present in the computer certificate store, as expected.

I was unable to find much info on enabling SSL on WSUS 4.0, so I followed the advice given on the Deployment Guide for WSUS 3.0 SP2 (Section"Configuring SSL on the WSUS Server"), basically:

    • Start IIS Manager, stop the Default Web Site and change the bindings (i moved the port binding one up, e.g. 80 -> 81, 443 -> 444)
    • Edit the bindings of the WSUS Administration Site and assign 80 and 443 and select the still present certificate
    • Now WSUS is responding to clients but the Management Console fails. After running%ProgramFiles%\Update Services\wsusutil.exe configuressl <fqdn>
    • Reboot (since I was unable to find out how to restart the ClientServicingProxy as mentioned by the Deployment Guide). Now everything seems OK.

    Hope this is useful for others. Ideas or suggestions for streamlining are welcome.

    /Maurice


    ↧
    Search

    error 0x80248007 cannot update definitions for Windows Defender from WSUS server

    July 3, 2019, 1:43 pm
    $
    0
    0

    I cannot automatically install Windows Defender antivirus updates on my Server 2019 server.  The error is 0x80248007 and the associated KB is KB2267602 which is not found in the Microsoft Update Catalog (https://www.catalog.update.microsoft.com/Home.aspx)

    Our Server 2019 server receives updates from an internal WSUS server.

    I have tried the following to fix the problem without success:

    1. ran the Windows Update troubleshooter found under troubleshoot settings
    2. net start msiserver
    3. stopped Windows Update in services.msc and deleted contents of the Windows\SoftwareDistribution folder and then restarted Windows Update in services.msc
    4. installed the latest version of .NET Framework which was 4.8 and rebooted
    5. uninstalled Windows Defender using PowerShell, rebooted, reinstalled Windows Defender using PowerShell, rebooted

    Other Windows Updates seem to install OK as after I installed .NET Framework, there were two .NET Framework updates that installed successfully.

    The Windows Defender update appears to download but fails during the installation phase.  I do not know how to proceed.

    Is there something that needs to happen on the WSUS server?  Our WSUS admin says that other servers can download and install the Windows Defender definitions.

    ↧

    WSUS update source keeps changing

    July 30, 2019, 1:34 pm
    $
    0
    0

    We are running WSUS on Server 2016 and have SCCM 1802 (Current Branch).

    The update source in SCCM keeps changing to "Synchronize from another Windows Server Update Services" server. SCCM is configured (Software Update Component Properties) to "Synchronize from Microsoft Update" once per day.

    It appears to change every hour and I can see in the WCM.log that it has changed.

    I have rebooted the WSUS server but it still happens. Some threads point to the Microsoft Client Security Update Assistant service but our server does not have that.  I find no hourly tasks that are triggered at the times it happens.

    Thoughts?

    Skip

    ↧
    ↧

    Some WSUS clients are not displayed on WSUS console

    July 31, 2019, 12:57 am
    $
    0
    0

    Hi,

    we deployed WSUS on Windows Server 2019. The servers (as WSUS clients) get the settings for updates using GPOs in the domain.

    Although some servers have the identical settings, they will not listed in the WSUS console.

    What is the issue here?

    Best regards

    Birdal

    ↧

    Disable "Update Settings" on WSUS clients

    July 31, 2019, 1:03 am
    $
    0
    0

    Hi,

    we deployed WSUS on Windows Server 2019 and the the servers (as WSUS client) get the setting using GPO in the domain.

    We want disable using GPO all "Update Settings" (Change Active Hours, Restart Options, Advanced Options) under"SETTINGS > UPDATE & SECURITY" to avoid that any account change these settings.

    Unfortunately we could not find any GPO settings options in Administrative Templates.

    Any idea?

    Best regards

    Birdal

    ↧

    WSUS Downstream Server does not get approved updates as approved from Upstream Server

    July 31, 2019, 1:13 am
    $
    0
    0

    Hi,

    we deployed based on Windows Server 2019 zwei two WSUS server:

    SRVUPSTREAM

    SRVDOWNSTREAM

    We approve Windows Updates on Upstream Server. Normally these approved updates must be also automatically approved on Downstream Server. Unfortunately that is not so.

    We have not this issue in our previous WSUS infrastructure based on Windows Server 2012 R2.

    I this issue related to Windows Server 2019?

    Or something is cahnge in concept of Updatream / Downstream Server?

    Best regards

    Birdal

    ↧
    Viewing all 12874 articles
    Browse latest View live
    Search
    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>