Purpose: Gather SCCM client cache sizes from your environment
I used to have a situation where many people did many things with great enthusiasm. Sounds familiar? This resulted in a non standard environment. To make sure that all SCCM Clients have the same CACHE SIZE, we need to first gather that CACHE SIZE with SCCM before we can create any Device Collections to hunt down wrong SCCM client cache sizes. Wrong CACHE SIZES can occur when SCCM clients are installed with different parameters or altered manually.
Purpose: Create a Device Collection which gathers workstations without SCCM client
In an SCCM controlled environment, a system without SCCM client is malfunctioning. Therefore you must be able to monitor that all the systems in your environment actually have the SCCM client. A fully operational SCCM and a workstation without SCCM client will mean that the workstation is not receiving any application updates, any OS updates and might even download OS updates them directly from MS without any restrictions (depending on other settings outside SCCM in your environment). So you really ought to fix these.
Purpose: Get all Workstations with Windows XP (WQL)
You are in a need to gather all Windows XP workstations with or without a SCCM client. You will first need to create a Device Collection: all Windows XP workstations with or without SCCM client (limiting collection: All Systems). Then create the: all Windows XP workstations without SCCM client (limiting collection: all XP workstations with or without client).
Purpose: You have installed SCCM SP1, and now you need to update your agents!
Updating the SCCM 2012 system with any major update that includes fixes to the client-side – generally means that you need to update all the clients that you have in your environment to meet the version of your servers. This can be done using different methods. The following methods are at least supported by Microsoft as a weapon of choice. In this post, I will only cover the method that I selected.
Methods of updating the SCCM 2012 clients:
- Install new client as an application / package.
- Use built-in tool of Client pushing.
- Setup Client Update as part of Software Updates.
- Enable Site-Wide client automatic installation.
- Install the client manually to desired workstations.