Upgrading System Center Configuration Manager 2012 to Service Pack 1

After upgrading my test (Beta SP1) environment to SP1 went smoothly we rolled out SCCM 2012 SP1 to one of our customers (because of a running issue which should be solved in SP1).

It caused me some sweat but got it running eventually.
The scenario:
– Windows 2008 R2
– SQL 2008 R2
– SCCM 2012 CU2

Note: To install ConfigMgr 2012 SP1 with Windows Server 2012 and SQL 2012 SP1 see http://www.toolzz.com/?p=602

Here are the steps I took:
1. Install the WADK (Windows Assessment and Deployment Kit)
First of all there are some extra requirements to take for the upgrade. In SCCM 2012 SP1 you no longer use WAIK, we’re now on WADK.
– Go to http://go.microsoft.com/fwlink/?LinkID=252874and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

2. Installing the SCCM 2012 SP1 software.
– I Downloaded the SP1 software from the Microsoft TechNet Site. It’s a little bit confusing but
System Center 2012 Configuration Manager and Endpoint Protection with sp1 x86 x64″
and “System Center 2012 Configuration Manager and Endpoint Protection x86 x64” with the date of 12 December are both valid.
– Start the Splash.hta on the disk
– Choose the Install option
SCCM SP1 Setup
– Choose “Upgrade this Configuration Manager site” and choose Next
SCCM SP1 Update 1
-Just note that there are more languages available then prior to SP1. Choose Next to continue
SCCM SP1 Update 2
– Check the prerequisite check. Because we implemented step 1 already we can continue by clicking Begin Install.
SCCM SP1 Update 3_1
In my case the installation took about one hour. The SQL database which was running on a different server was automatically updated.

3. The console issue
After starting up the console I bumped into an issue which was not very clear:

After upgrading to SP1 my console disappeared from my management server.
SCCM 2012 SP1 Console
After some troubleshooting I tried starting up the console from the directory; but it could not connect to the server.
Console issue SCCM 2012 SP1
This was strange, but after some investigating I discovered that the Console is not automatically updated with SP1 which causes this issue.
– Restarting the SP1 Splash.HTA and running Install Configuration Manager console solved the issue for me!
Update Console SCCM 2012 SP1
Checked the installation and we are indeed running on SP1 !!
SCCM SP1 Update 4
Henk Hoogendoorn posted a blog on what features are updated in the SP1 HERE.

System Center 2012 SP1 Released

System Center 2012 Service Pack 1 has reached its “release-to-manufacturing” (RTM) milestone, Microsoft announced recently.
ScreenHunter_162 Dec. 21 08.33

RTM typically refers to feature-complete products, although the final “general availability” release of System Center 2012 SP1 is scheduled for early January.
The “release candidate” version of the product had been issued previously, but was just available to Microsoft’s Technology Adoption Program testers. The last public release announcement seems to have been a beta delivered in September.

The software is now available on the MSDN site for partners and customers with SA.
It’s available on http://msdn.microsoft.com/en-us/subscriptions/downloads/.

A list of what’s new in SP1 for System Center 2012:
1. There are new Monitoring Capabilities under APM functionality:
                         o Monitoring of Windows Services Built on the .NET Framework.
                         o Automatic Discovery of ASP.NET MVC3 and MVC4 Applications.
                         o New Transaction Types: MVC Pages and WCF Methods.
2. Enabled APM of SharePoint 2010.
3. Integration with Team Foundation Server 2010 and Team Foundation Server 2012.
4. New monitoring capability allows for opening of APM exception events from Visual Studio IDE as if the exception was captured during the IntelliTrace historical debugging session. Developers can stay within their familiar environment to examine complete exception call stack.
5. New Management Packs and Support for Windows Server 2012 and IIS 8.
6. The System Center 2012 Service Pack 1 (SP1) Beta version of Operations Manager can show you different perspectives of application health in one place—360 .NET Application Monitoring Dashboards. The 360 .NET Application Monitoring Dashboards displays information from Global Service Monitor, .NET Application Performance Monitoring, and Web Application Availability Monitoring to provide a summary of health and key metrics for 3-tier applications in a single view.
7. ACS support is now added for Dynamic Access Control – new feature in Windows Server 2012, where business data owners to easily classify and label data allowing access policies to be defined for data classes that are critical to business.
8. Support is added for CentOS, Debian, and Ubuntu Linux.

The arrival of SP1 for System Center 2012 is a big deal because it will add management support for Windows Server 2012 and Windows 8 and SQL 2012.

Without this service pack, there’s no management support for those operating systems in System Center 2012.


Why download management packs manually instead of from the catalog

When updating OpsMgr management packs the easiest way to do this is to show “Updates available for Installed Management Packs” in the console.

When doing this only the existing imported MP’s are updated.
If the MP is updated with new additional monitoring features it will not show up as needing an update. So if you use the console you will miss new ones.
Because of this I do not recommend using the console update feature but download the MSI from the catalog on the web at http://systemcenter.pinpoint.microsoft.com and extract them, if not you will end up missing MP’s you need.


Updating the Exchange 2010 Management Pack in OpsMgr 2007 and OpsMgr 2012

This is a step by step guide on how to update the Exchange Server 2010 management pack with System Center Operations Manager 2007 and 2012.

Installing a fresh installation of the Exchange 2010 MP see http://www.toolzz.com/?p=63

Operations Manager 2007 R2 requires a restart!
Operations Manager 2012 does not require a restart!
The Exchange Monitoring will have downtime during the upgrade of the correlation engine

This article is discusses how to update the Exchange 2010 management pack the proper way.

Step 1 – Checking the current version of the Exchange 2010 MP
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Choose the Management Packs node,
4. Type Exchange in the search box and check if it is an older version and not already updated.

Step 2 – Updating the Exchange correlation Engine
The correlation update must run on from the server where it is successfully installed. Most likely (and recommended) the Correlation Engine will be installed and updated on the root management server (emulator).

Do the following steps on the RMS Emulator
1. Download the MP software from the Microsoft site http://www.microsoft.com/downloads/details.aspx?FamilyID=7150bfed-64a4-42a4-97a2-07048cca5d23&displaylang=en
2. Choose the proper version (X64)
3. Launch the MSI Package and run the installation and follow the installation

4. As mentioned before
Operations Manager 2007 R2 requires a restart after that you can continue to step 3
Operations Manager 2012 continue to step 3.

Step 3 – Import the Exchange 2010 Management Pack
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Right-click the Management Packs node, and then click Import Management Packs.
4. The Import Management Packs wizard opens. Click Add, and then click Add from disk.
5. If prompted to connect to the online catalog, click No.
6. The Select Management Packs to import dialog box appears. Go to the directory where your management pack file is located as extracted in Step 1. By default, the location is C:\Program Files\System Center Management Packs.
7. Select both management pack files to import from that directory, and then click Open.
8. On the Select Management Packs page, the management packs that you selected for import are listed.

9. You will receive a prompt indicating that the management pack presents a security risk. This is due to the management pack’s use of agent proxying. Click Yes to allow the import.
10. The Import Management Packs page appears and shows the progress for each management pack. Each management pack is downloaded to a temporary directory, imported to Operations Manager, and then deleted from the temporary directory. If there is a problem at any stage of the import process, select the management pack in the list to view the status details. Click Close.
11. Check the C:\Program Files\Microsoft\Exchange Server\v14\Bin directory content if the update ran successfully

That’s all !
Because the configuration already took place during the initial installation of the MP the update does not require any adjustments.