@Sam. In other words, maybe re-think your approach?
Btw, we have two primaries (and a CAS, don't start.) for up-to 200'000 clients and just two SUPs (one for each primary). With failover and NLB you just add more things to break on something which is not that critical. Rather make sure your MPs are a bit more HA. From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 13. November 2013 00:40 To: [email protected] Subject: RE: [mssms] WSUS content on Failover cluster That's not how it works. WSUS is not a fallback location for updates - either it is your primary source or no source - anything else is unsupported and won't work the way that you are describing. Same with using auto-approve rules or manually approving/declining any updates within WSUS itself: totally unsupported and not recommended. J From: [email protected] [mailto:[email protected]] On Behalf Of Sam George Sent: Tuesday, November 12, 2013 4:50 PM To: [email protected] Subject: RE: [mssms] WSUS content on Failover cluster No of clients -200K Why do we care about WSUSContent - We approve pathes through WSUS and CM, so if CM failes clients will get updated from WSUS. Also we have drivers and SCEP updates which are auto approved in WSUS. _____ From: [email protected] To: [email protected] Subject: RE: [mssms] WSUS content on Failover cluster Date: Tue, 12 Nov 2013 22:24:49 +0000 Actually, the real question is why do you care about the WSUSContent folder at all? When integrated into ConfigMgr, the only thing in this folder are EULAs and the infrastructure updates (like Windows Installer 3.1). Updates themselves are *not* stored in this folder so why go through any of this? J From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Tuesday, November 12, 2013 4:18 PM To: [email protected] Subject: RE: [mssms] WSUS content on Failover cluster Next question would be how many clients? From: [email protected] [mailto:[email protected]] On Behalf Of Sam George Sent: Dienstag, 12. November 2013 23:07 To: [email protected] Subject: RE: [mssms] WSUS content on Failover cluster Its with Configmgr 2012. _____ From: [email protected] To: [email protected] Subject: RE: [mssms] WSUS content on Failover cluster Date: Tue, 12 Nov 2013 22:01:15 +0000 Is this for a stand-alone WSUS implementation or for integration into ConfigMgr? J From: [email protected] [mailto:[email protected]] On Behalf Of Sam George Sent: Tuesday, November 12, 2013 2:07 PM To: [email protected] Subject: [mssms] WSUS content on Failover cluster HI All, We are planning to setup a Cluster file share for WSUS content. Setup: - 1. Two WSUS 6.2 server (Server 2012) which will be on NLB and will be pointing to the same SUSDB and content which will be on file Cluster. When there a failover we see that some updates fail to get downloaded. 2013-11-11 21:08:57.254 UTC Info WsusService.5 EventLogEventReporter.ReportEvent EventId=364,Type=Error,Category=Synchronization,Message=Content file download failed. Reason: Error calling [kernel32.dll]:CreateDirectory(\FILE01\WSUSContent\7B) Source File: Destination File: . 2013-11-11 21:08:57.270 UTC Info WsusService.5 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileDownloadFailed for Item: 306fe2df-3d83-46fd-8c5c-d8268c2ca2e6 2013-11-11 21:08:57.317 UTC Info WsusService.5 ContentSyncAgent.WakeUpWorkerThreadProc Processing Item: 1c0fdc5a-d176-4638-887b-ddf205d1008f, State: 10 2013-11-11 21:08:57.317 UTC Error WsusService.5 ContentSyncAgent.WakeUpWorkerThreadProc File 20569144.cab: ActualState: 10; Step: Start; Message: System.ApplicationException: Error calling [kernel32.dll]:CreateDirectory(\FILE01\WSUSContent\27) at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.CreateDown loadPath(String fileContentPath, Byte[] fileDigest, String fileName, Boolean createDirectory, Boolean forBITS) at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.WakeUpWorkerThreadProc( ) at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.WakeUpWorkerThreadProc( ) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() 2013-11-11 21:08:57.317 UTC Info WsusService.5 EventLogEventReporter.ReportEvent EventId=364,Type=Error,Category=Synchronization,Message=Content file download failed. Reason: Error calling But after sometime it seems it downloaded the file 2013-11-11 21:08:56.442 UTC Info WsusService.5 ContentSyncAgent.WakeUpWorkerThreadProc Processing Item: e8dd4048-1f70-430c-9371-544184c452cc, State: 10 2013-11-11 21:08:56.442 UTC Info WsusService.5 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileDownloadFailed for Item: e8dd4048-1f70-430c-9371-544184c452cc 2013-11-11 21:14:37.052 UTC Info WsusService.24 ContentSyncAgent.WakeUpWorkerThreadProc Processing Item: e8dd4048-1f70-430c-9371-544184c452cc, State: 10 2013-11-11 21:14:37.068 UTC Info WsusService.24 ContentSyncAgent.Download Item: e8dd4048-1f70-430c-9371-544184c452cc has been submitted to BITS for Download 2013-11-11 21:14:47.050 UTC Info WsusService.24 ContentSyncAgent.ProcessBITSNotificationQueue ContentSyncAgent recieved Transferred Event for Item: e8dd4048-1f70-430c-9371-544184c452cc 2013-11-11 21:14:47.050 UTC Info WsusService.24 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileDownloaded for Item: e8dd4048-1f70-430c-9371-544184c452cc 2013-11-11 21:14:47.956 UTC Info WsusService.24 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileVerified for Item: e8dd4048-1f70-430c-9371-544184c452cc Queries:- 1. Do we know after how long WSUS will re-try to download these updates? 2. Is there a way we can trigger these updates. 3. Any know issues when clients are trying to download the content from the WSUS content on Failover cluster. Regards, /SAM
