Purpose: You installed RTM version, and its now not up to date anymore, Aieee! Do something!
Let me begin by pointing out the obvious here: you do not need this update because of all the new features it gives, you need this update because of all the bug fixes it does! My god, that almost rhymed, I could start writing poetry. The post is divided into two parts: the first part containing the requirements that you need to do before you can move to the second part, which is the actual installation of the update. Do not step over the first part, you really do need to do all of these.
Bug fixes in Configuration Manager 2012 SP1
New features in Configuration Manager 2012 SP1 (Referenced)
- Deployment and upgrade support for Windows 8.
- Client support for Windows 8 and limited support for Mac OS X, Linux and Unix.
- Max OS X: Deploy Software, Collect Hardware Inventory, Manage Compliance Settings.
- Linux/Unix: Deploy Software, Collect Hardware Inventory.
- Support for “Metered Internet Connections” and “Always On Always Connectied” features of W8.
- Support for “Windows to GO” feature.
- Support for Windows Server 2012 and SQL Server 2012.
- Support for SCCM Automation by PowerShell cmdlets.
- New Distribution Point (Could Distribution Point, Windows Azure).
- Multiple software update points for a site which provides automatic redundancy for clients.
- Email alert subscriptions are now supported for all features, not just Endpoint Protection.
Alright, enough with the teasing, lets get down to business. There are several requirement tasks before the update, and several tasks after the update. Remember: It is always recommended that you take a database backup of your current environment, and test that the backup works by recovering it back to another SQL Server (as a test) before you start doing any DB changes (like this update). Should you do this, the Collation and the version of the SQL Server should be exactly the same on both of the servers.
SQL Server is at least Microsoft SQL Server 2008 R2 SP2. Check update from Installed Updates:
Download and Install Windows Management Framework 3.0
Download and Install WSUS 3.0 SP2
Download and Install Windows ADK (8.0)
Download SCCM 2012 SP1 Installation media (ie.) from your Volume Licensing.
Someting like this (in ISO): SW_DVD5_Sys_Ctr_2012w_SP1_Config_Mgr_EndPt_Protection_MultiLang
Nagivate to your downloaded SCCM SP1 Installation media. Run the following command to check what else you need to fix in your environment before you can start installing SCCM 2012 (all of the above would also be mentioned in this check, should you not have done them). The following commandline will work on a stand-alone primary site server. Should your hierarchy be something else, run the help switch (/?) to retrieve the correct commands.
- SMSSETUP\BIN\X64\prereqchk.exe /PRI /SQL (FQDN of your SQL server) /SDK (FQDN of your primary site)
- You can see the log of the action here c:\ConfigMgrPrereq.log
- Remove all the boot images from every distribution point.
- Shutdown any “third party” virus protection for the duration of the installation.
- Disable Delete Agent Client Oprations site maintenance task
- Check, that you have not altered the default root device collections (will be overwritten and made read only after the SP1 installation.
- Restart your server for additional Windows Updates and/or for the requirements installation at this point.
Great! You are just about ready to start. Hit the splash.hta in your SCCM 2012 SP1 installation media and press Install. You will need a license key for the software during the installation. You also probably need to download the additional installation files which the installer asks you to do. Download them to a local location of the server and reference that location when the installer asks for it and be prepared to spend an hour in this part of the SP1-installation.
|SCCM 2012 Version is:||5.00.7711.1000|
|SCCM 2012 SP1 Version is:||5.00.7804.1000|
You can see the SCCM 2012 server version you are running from the Admin Console by navigating here:
\Administration\Overview\Site Configuration\Sites (and take properties upon your site).
Hey you, dont quit just yet! Remember, there were some things you need to do before calling it a day (yeah be honest, it probably took you a day with all those progress bars and downloading).
- You disabled the maintenance task “Delete Aged Client Operations”, now its time to enable.
- You probably need to reintegrate MDT (if installed) with SCCM (Start Menu has shortcut)
- Turn on your third party virus protection, if you had it and shut it down in requirement tasks.
- You need to distribute the new generated boot image (WinPE 4.0) to your Distribution Points.
- You need to do new Task Sequence (or modify your old) to use the new boot image (WinPE 4.0)
- Naturally, you should test that the modified/new Task Sequence works now.
- Update All SCCM Admin Consoles with the SP1 Installation [Continue]
- Update All SCCM Clients with the SP1 client installation [Continue]