{"action":"opened","issue":{"url":"https://api.github.com/repos/MicrosoftDocs/SCCMdocs/issues/584","repository_url":"https://api.github.com/repos/MicrosoftDocs/SCCMdocs","labels_url":"https://api.github.com/repos/MicrosoftDocs/SCCMdocs/issues/584/labels{/name}","comments_url":"https://api.github.com/repos/MicrosoftDocs/SCCMdocs/issues/584/comments","events_url":"https://api.github.com/repos/MicrosoftDocs/SCCMdocs/issues/584/events","html_url":"https://github.com/MicrosoftDocs/SCCMdocs/issues/584","id":329935754,"node_id":"MDU6SXNzdWUzMjk5MzU3NTQ=","number":584,"title":"Bug or Vague/Poor Documentation","user":{"login":"RyanHath","id":40000233,"node_id":"MDQ6VXNlcjQwMDAwMjMz","avatar_url":"https://avatars0.githubusercontent.com/u/40000233?v=4","gravatar_id":"","url":"https://api.github.com/users/RyanHath","html_url":"https://github.com/RyanHath","followers_url":"https://api.github.com/users/RyanHath/followers","following_url":"https://api.github.com/users/RyanHath/following{/other_user}","gists_url":"https://api.github.com/users/RyanHath/gists{/gist_id}","starred_url":"https://api.github.com/users/RyanHath/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RyanHath/subscriptions","organizations_url":"https://api.github.com/users/RyanHath/orgs","repos_url":"https://api.github.com/users/RyanHath/repos","events_url":"https://api.github.com/users/RyanHath/events{/privacy}","received_events_url":"https://api.github.com/users/RyanHath/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-06T16:08:28Z","updated_at":"2018-06-06T16:08:28Z","closed_at":null,"author_association":"NONE","body":"We also use SCEP as our AV, which as you know the definitions are updates. I have my collections that are marked as Server Groups for Clusters, where I deploy regular monthly patches to, not SCEP definitions. I have an ADR that runs for SCEP defs, and deploys to my “All Desktop and Server Clients” collection, which is of course not marked as a server group.\n\n\tMy collections marked as server groups have simple PS scripts for drain/resume\n-\tDrain Script &gt; Suspend-ClusterNode -drain\n-\tResume Script &gt; Resume-ClusterNode -Failback Immediate\n\nWhat I’ve noticed is that every day when the ADR runs, and the definitions updates are applied its running the Drain/Resume scripts on the Server Group nodes. When I implemented these server groups my understand is they would only be treated as server groups on deployments deployed directly to the collections marked as server groups.\n\n“When you deploy software updates to a collection that has server group settings configured, Configuration Manager determines how many computers in the collection can install the software updates at any given time and makes the same number of deployment locks available. Only computers that get a deployment lock will start software update installation. When a deployment lock is available, a computer gets the deployment lock, installs the software updates, and then releases the deployment lock when software updates installation successfully completes. Then, the deployment lock becomes available for other computers. If a computer is unable to release a deployment lock, you can manually release all server group deployment locks for the collection.”\n\n\n---\n#### Document Details\n\n⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*\n\n* ID: 9f3de375-7539-a500-f8e2-07eb5bf76b08\n* Version Independent ID: c660dece-e914-d49a-2a3c-a8de166f88b7\n* Content: [Service a server group - Configuration Manager](https://docs.microsoft.com/en-us/sccm/sum/deploy-use/service-a-server-group#feedback)\n* Content Source: [sccm/sum/deploy-use/service-a-server-group.md](https://github.com/Microsoft/SCCMdocs/blob/master/sccm/sum/deploy-use/service-a-server-group.md)\n* Product: **configuration-manager**\n* GitHub Login: @aczechowski\n* Microsoft Alias: **aaroncz**"}}
{"actor":{"display_login":"RyanHath"}}