Before you can enjoy the new features of SP1 you indeed need to install it. But I bet you already knew that 
In this article I will give you a quick overview of the installation process and the preparation steps. I will probably add some more information to this post later with some real-world experience – at the time of writing this is limited to my two lab and demo environments. Also, if YOU have other suggestions or want to report YOUR experience with SP1, feel free to comment. I will then upgrade the post with that additional information to make it even more valuable for other readers.
Helpful Links
http://technet.microsoft.com/en-us/library/jj900186.aspx
http://technet.microsoft.com/en-us/library/jj900202.aspx
http://technet.microsoft.com/en-us/library/jj628205.aspx
http://technet.microsoft.com/library/hh519636.aspx
http://scomandplus.blogspot.ca/search?updated-min=2012-01-01T00:00:00-08:00&updated-max=2013-01-01T00:00:00-08:00&max-results=8
Step 1 – Preparation
First we have to prepare for rollback in case anything breaks during SP1 installation. So make sure you backup the following components before you start the installation:
- Service Manager Database
- Service Manager Data Warehouse Databases
- All unsealed Management Packs (manual export from the console or by using a PowerShell Script)
- Encryption Keys (SecureStorageBackup.exe in the “Tools” folder from the installation source)
- Optional: VM Snapshots of the Service Manager Servers
To install SP1 your Service Manager environment must have Update Rollup 2 or higher installed. If this is not the case, install the latest Update Rollup before you continue with your SP1 deployment. I suggest upgrading the Service Manager components in the following order:
- Data Warehouse Management Server
- Initial Management Server
- Additional Management Servers
- Web Content/SharePoint Web Part Servers
- Standalone Consoles
Some other tips that can be useful for a successful upgrade process:
- Restart all Servers that will be updated with SP1 before starting the upgrade process
- Check the Windows Event Logs for any errors and fix these issues
- Make sure that there are no open consoles or SSP connections
- Run the installation process from a local source (copy the source to the destination server)
- Run Setup.exe from an elevated PowerShell or Command Prompt to make sure you don’t run into any trouble because of the User Account Control (UAC) mechanism
One mentioned Technet Article under “Helpful Links” says, that you should disable the Data Warehouse Jobs before upgrading to SP1. If have not done this for my test lab and it worked like a charm. But it makes sense to follow this procedure. Make sure you start the jobs again after all components are updated.
Step 2 – Installation
Installing the Service Pack is straightforward and behaves more or less the same for all Service Manager components. Below are some screenshots of a SP1 Installation on a Data Warehouse Management Server.
Step 3 – Verification
When all components are updated some verification steps can help to proof a correct SP1 installation. When the console starts you should see “Service Pack 1” in the splash screen.
When the console is started you can again check the actual build by using “About Service Manager” from the “Help” menu.
All Service Manager Servers are updated with some new files that are living in the Service Manager installation directory. Check if the files (not all of them) are available in Version 7.5.2905.0
Now you are ready to benefit from the corrected, optimized and also brand new Service Pack 1 features.
Have fun!
Marcel
marcelzehner.ch 
I need to rename my SCSM server and want to do so before I update to SP1. I tried to perform that but the service refuses to stat. I found and changed some registry keys on the SCSM server to the new name but that did not help as well.
I wonder if there is something on the Database that expects connections from a specific server.
Can you help with that?
Thanks.
Hey
Renaming is not supported afaik. You must install a new (additional) MS with the correct name, then transfer the workflow role to the new Server and remove the old one.
Cheers
Marcel
I see. . . But things can be worst. . . I need to migrate this SCSM to a new Domain, and think that that won’t be possible. . . Can I “export” or “transfer” the contents of a database to another one on the new Domain?
Thanks.
You can export/import everything from the CMDB, including all relations etc., but this will cost you some time 🙂 the question is, what exactly you (really) need to migrate and what could be recreated by configuring connectors.
Cheers
Marcel
If there is a way that I can export ate least the “Open” and “In Progress” incidents and import on a new environment at the new Domain, that would suffice, I think. However if we can export all the incidents, that would be perfect!
Hi Marcel,
Would you be able to put up any bug fixes or improvements you have seen with the system since installing it? Other than whats on the microsoft website. wont be using any of the new features and want to know if anything else is fixed or improved to warrent to work.
hi what happen if the same Service manager server have installed self service portal??
I have the following components installed in the same machine:
– Service Manager Management Server
– Service Manager Self Service Portal
– Server Manager Console
After I upgraded the Service Manager Management Server, I found that trying to upgrade the Self Service Portal or Service Manager Console will receive the error message of “Self Service Portal was installed” and “Service Manager Console was installed”.
When I ran the Service Manager Console, I found that it is automatically upgraded to SP1. I have no idea how to check whether the Self Service Portal is also upgraded to SP1 but I supposed it was also implicitly upgraded to SP1.
I’ve upgraded without issue but I have found now all Datawarehouse Jobs in the Console are running regardless if they are enabled or not? Is this normal behaviour? Will they eventually stop
Hey
Check the Job and Job Schedule Status using PowerShell and change as needed.
– Get-SCDWJob
– Get-SCDWJobSchedule
Cheers
Marcel
Hi Marcel – Did you have to do this at all?
Prerequisites and Preparation
To get ready for SP1, we upgraded our test environment about ten times to ensure we understood the impact of the upgrade and could validate that both core ticketing and the DW/reporting components all worked as expected after the fix. This meant building out SM and connecting it to our production OM to simulate load and configuration as close as possible. Granted, we started the testing with early RC builds, but even with RTM SP1 bits, we’d recommended at least a couple of full tests.
One area we noticed right away is that some of our custom PowerShell commands stopped working on SP1 upgrade. This was traced back to a missed reference change. This fix will be in a future Cumulative Update (CU), but in the meantime if you are leveraging PowerShell in your SM implementation, you’ll need to do the following. The MonitoringHost.exe.config file in C:\Program Files\Microsoft System Center 2012\Service Manager needs to be updated to reflect the latest PowerShell version. See below for what our MonitoringHost.exe.config looks like after being updated to 7.0.5000.0:
http://blogs.technet.com/b/wincat/archive/2013/01/22/upgrading-to-system-center-2012-sp1-service-manager-scsm-at-microsoft.aspx
Hey Marcel,
We are looking to upgrade to SP1, however we were told by our consultants that we needed to un-install the Self-Service Portal before doing this upgrade. Could you please confirm?
Thank you
Hey
True, you must remove the SSP when it is installed on a MS and re-install it on a non-MS server.
Cheers
Marcel
How do you uninstall the SSP from the MS ? And how do you check the “version” of the SSP is non-SP1 or SP1 ?
Hi,
We have recently just attempted an upgrade to SCSM 2012 SP1. The DW went ok but hit an issue with the MS. It told us the T drive on the SQL box did not have 1 GB Free disk space. Unfortunately the drive in question is only a 1GB drive with 988MB Free! The folder on this drive are mount points to where the databases are stored (which has plenty free space)
Is this a case that Microsoft SCSM 2012 SP1 is not mount point aware??
Of course an easy solution would be to increase the size of the drive, if it was a cluster server with extra complexity on the actual disks 😦
Errors:
08:00:11:SQL Server scsmserver\SCSM dont have enough free disk space
08:00:11:The SQL server T drive does not have a minimum of 1GB free space. Clear some space and retry.
08:00:11:*** Pre-Upgrade checks failed ***
Has anyone heard of this before?
Thanks,
Rich
Since heard back from MS Support that this is a known OS Issue, they recommend 3GB of free space on the mount point drive but over 1GB to pass the pre req. Nothing in the pipeline to fix the issue anytime soon.
Hi Marcel
Thank you for the greate Blog, i could update to SP1 without any problem by folowwing your Blog
Andy
Hi Marcel.
I have 98 Consoles to upgrade and want to use SCCM to push SP1 out.
Is there a command script to upgrade or should I uninstall Console and reinstall SP1.
Thanks
Gavin
Hi Marcel
I have found the command line and tested it
Setup.exe /Silent /Upgrade:Console /AcceptEula:YES
Regards
Gavin
Hey Gavin
Thanks for sharing!
Cheers
Marcel
Marcel
I have upgraded to SP1 but I cannot get Powershell to work either from Console or external to console. It will not allow me to Import Snapins.
Any Ideas.
Gavin
Marcel, many thanks. #Legend