Previously I showed how I used SCCM Compliance Settings and Boundary Groups to apply BITS settings. This time I have a discovery and remediation script that can be used with enforce a specific state on a service. If you want to make sure a client’s App-V service stays up or Windows Defender is disabled because you are using another security suite, this could be of help. The script uses variables so someone could easily set the state of the service and start type to what they want. Continue reading “SCCM Compliance Settings Scripts to Alter Service State”
Author: Michael Schultz
Using ConfigMgr Compliance Settings and a Boundary Group to Apply BITS Settings
The solution here makes use of a boundary group to determine if a SCCM client should use BITS to control content transfers and compliance settings set the BITS settings. With SCCM build 1610, the boundary group IDs a client is associated with are store in WMI. Using PowerShell, we are able to look at the boundary group ID and use it to help set BITS settings. Fair warning with this solution. While the boundary group ID is currently stored in WMI, I have been informed by Microsoft that this information isn’t meant to be customer facing and may go away in future SCCM builds, but it is something that is current available. Continue reading “Using ConfigMgr Compliance Settings and a Boundary Group to Apply BITS Settings”