Purpose: You have installed SCCM SP1 CU2, and now you need to update your Admin Consoles!
Updating the SCCM 2012 system with any major update that includes fixes to the Admin Console – generally means that you need to update all the Admin Consoles that you have in your environment to meet the version of your servers. In SP1 CU2, you can still use the old Admin Console after the update, so there is no rush to update all of the Admin Consoles.
Purpose: You have installed SCCM SP1 CU2, and now you need to update your agents!
Updating the SCCM 2012 system with any major update that includes fixes to the client-side – automatically 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 (unsupported for CU-updates).
- Setup Client Update as part of Software Updates.
- Enable Site-Wide client automatic installation (only major updates).
- Install the client manually to desired workstations.
Purpose: A new set of updates have been released for SCCM SP1 (CU2)
Since the dawn of the new Configuration Manager 2012 -version, it has been haunted by various bugs. Luckily there is a constant flow of Cumulative Updates available since the release of SP1. Next in the spotlight is the System Center 2012 Configuration Manager SP1 CU2.