Skip to main content

Posts

Showing posts with the label wsus

SCCM Server Groups

What Are Server Groups? Within SCCM Assets and Compliance you can create a collection containing Server Client membership. Once the 'Server Group' feature is enabled the properties of the collection will contain an additional option to declare that all members of the collection are part of a server group.   This means SCCM knows that the servers within this collection must be treated with specific logic and settings. In the example below the collection contains three nodes of a cluster and only one node may be Software Updated at a time. Once policy is received for the Software Update Group deployment an election is held in which one of the nodes will engage a lock state forcing the other nodes to wait until it has been released. The UpdatesDeployment.log details the 'Lock State'. Once the node has taken the lock (Lock State: 1) the server will then run the 'Node Drain Script' and continue if the script has an exit code of 0 zero or if the script times out (600 ...

SCCM SUP WSUS Pool keeps stopping or the server is unresponsive

SCCM SUP WSUS Pool keeps stopping or the server is unresponsive Scenario: Our WSUS/SUP had become unresponsive and the decision to reinstall the server role was made. After the Site server had been reinstalled  I became aware that Windows Defender updates were failing to update (3 days old) and even though the updates were sync'd, downloaded, and deployed in SCCM the client was still unable to receive them. Client Log analysis : ScanAgent.log ScanJob({999C9FFA-A463-4BE8-8771-67EE96D4140B}): CScanJob::OnScanComplete -Scan Failed with Error=0x80240440 ScanJob({999C9FFA-A463-4BE8-8771-67EE96D4140B}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80240440 Update Deployment.log Job error (0x80240440) received for assignment ({bf7a48e6-d220-4070-bb9b-ecc239107584}) action        UpdatesDeploymentAgent        Updates will not be made available        WUAHandle...

SCCM with WSUS in DMZ serving Internet Facing clients

SCCM with WSUS in DMZ serving Internet Facing clients Overview: This Blog will document at a high level my experience of implementing a 'Software Update Point' on a site server in our DMZ to serve SCCM clients (including Workgroup servers) on the Internet. It will explain the implementation process as well as expected behaviour by diving into the log files on both the site server and client. Please ask questions in the comments field; and I will update the main narrative in response. Architectural design overview One Primary site server on Internal network One Site system Server within DMZ Ports opened on firewall to allow servers to communicate. Configured with the following System roles: Management point Distribution point Software update point Work group servers within the DMZ/Internet facing clients only The Site system Server within DMZ had the WSUS role installed through 'Server Manager' console. Within IIS a webserver certificate was added to the binding port 853...

SCCM with WSUS in DMZ serving Internet Facing clients

SCCM with WSUS in DMZ serving Internet Facing clients Overview: This Blog will document at a high level my experience of implementing a 'Software Update Point' on a site server in our DMZ to serve SCCM clients (including Workgroup servers) on the Internet. It will explain the implementation process as well as expected behaviour by diving into the log files on both the site server and client. Please ask questions in the comments field; and I will update the main narrative in response. Architectural design overview One Primary site server on Internal network One Site system Server within DMZ Ports opened on firewall to allow servers to communicate. Configured with the following System roles: Management point Distribution point Software update point Work group servers within the DMZ/Internet facing clients only The Site system Server within DMZ had the WSUS role installed through 'Server Manager' console. Within IIS a webserver certificate was...