Purpose: You have installed SCCM SP1, 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 CU1, 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 CU1, 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: You have installed SCCM SP1, but its not up to date anymore, Aieee! Do something again!
So you thought you are safe now that the SP1 is installed and all your worries will go away? Wrong! SP1 created some new issues and did not fix all the original issues you might have had with the system. So I urge you to update SCCM 2012 SP1 to the following Comulative Update 1, which will help you to grow less grey hair. With all these different issues, there will most likely be updates more in the future, but do not wait for SP2 to appear, it could take a while.
Bug fixes in Configuration Manager 2012 SP1 CU1 (Includes download link)