In the previous part of this series we have finished installing different parts of the System Center Service Manager 2012, including SQL Server, Management Server , Data Warehouse Server and the Self-Services Portal server. today we will discuss the different versions of Service Manager 2012 that has been released till the date of writing this article, we will discuss the new features in those versions and i will show how to upgrade your installation to the latest version and solution to problems i have personally faced during the upgrade.
System Center 2012 SP1 – Service Manager
What’s new in SM SP1 ? Reference “http://technet.microsoft.com/en-us/library/jj614408.aspx”
In System Center 2012 SP1, Service Manager provides bug fixes and new features. The following list summarizes the new functionality in Service Manager:
- Improved Operations Manager Integration An System Center 2012 – Operations Manager SP1 agent is automatically installed as part of Service Manager SP1. After Setup completes, you must manually configure the agent for use with the Operations Manager management server. The agent is compatible with System Center Operations Manager 2007 R2, System Center 2012 – Operations Manager, and System Center 2012 – Operations Manager SP1
- SQL Server 2012 Support All databases used by Service Manager are supported on all editions of SQL Server 2012.
- Windows Server 2012 and Windows 8 Support All Service Manager roles, except the Self-Service Portal SharePoint web parts, are supported on all editions of Windows Server 2012. Windows 8 is supported for the Service Manager console and for end-users accessing the Self-Service Portal.
Hardware and Software Requirements Reference “http://technet.microsoft.com/en-us/library/jj900197.aspx“
Hardware Requirements for System Center 2012 – Service Manager SP1
System Center 2012 – Service Manager SP1 will function on the same hardware that you used for System Center 2012 – Service Manager.
Software Requirements for System Center 2012 – Service Manager SP1
To upgrade to System Center 2012 Service Pack 1 (SP1) SP1, you must first apply Cumulative Update 2 for System Center 2012 – Service Manager.
System Center 2012 – Service Manager SP1 has the same software requirements for the Service Manager console that System Center Service Manager 2010 does, except for the new requirement of Microsoft SQL Server 2012 Analysis Management Objects (AMO). Microsoft SQL Server 2012 AMO is supported on SQL Server 2008 and SQL Server 2012. In addition, the Service Manager console can now be installed on computers running Windows 8 and Windows Server 2012.
The Service Manager and data warehouse management servers, along with the Self-Service Portal, is supported with Windows Server 2012.
Upgrade Order and Timing Reference “http://technet.microsoft.com/en-us/library/jj900197.aspx“
The order of your upgrades is important. Perform the upgrade steps in the following order:
- Backup your databases and your management packs. See the topics Backing Up Service Manager Databases and “Backing Up Unsealed Management Packs” in the Disaster Recovery Guide for System Center 2012 – Service Manager.
- Start with the data warehouse management server. You will be stopping the data warehouse jobs, and you will not be able to start them again until after you have completed the upgrade.
- After the upgrade to the data warehouse management server is complete, upgrade the initial Service Manager management server. If you created more than one Service Manager management server, the initial Service Manager management server is the first one that you created.
- Upgrade the Service Manager consoles and any additional Service Manager management servers.
- Restart the data warehouse jobs.
- Deploy the new Self-Service Portal.
The timing of your upgrades is also important. After you upgrade your data warehouse management server, you must both update the Service Manager management server and deploy the new Self-Service Portal. After you upgrade your initial Service Manager management server, you must be prepared to upgrade your Service Manager console or Service Manager consoles, additional Service Manager management servers, and Self-Service Portal at the same time.
The Upgrade Process
Now there are steps that needs to be done before proceeding with the upgrade, these steps should prevent problems during or post the upgrade process.
- Preventing MPSync Jobs From Failing
A problem with the upgrade process causes MPSync job to fail after the upgrade is complete. To prevent this problem from occurring before you upgrade, you must run the SQL script below on the DWRepository database to get the actual SQL scripts that drop and add a constraint on the primary key in fact tables in the DWRepository database to correct the problem. Additionally, transform and load jobs might also fail. This error can occur because of erroneous database grooming.
;WITH FactName AS ( select w.WarehouseEntityName from etl.WarehouseEntity w join etl.WarehouseEntityType t on w.WarehouseEntityTypeId = t.WarehouseEntityTypeId where t.WarehouseEntityTypeName = 'Fact' ),FactList AS ( SELECT PartitionName, p.WarehouseEntityName, RANK() OVER ( PARTITION BY p.WarehouseEntityName ORDER BY PartitionName ASC ) AS RK FROM etl.TablePartition p join FactName f on p.WarehouseEntityName = f.WarehouseEntityName ) , FactPKList AS ( SELECT f.WarehouseEntityName, a.TABLE_NAME, a.COLUMN_NAME, b.CONSTRAINT_NAME, f.RK, CASE WHEN b.CONSTRAINT_NAME = 'PK_' + f.WarehouseEntityName THEN 1 ELSE 0 END AS DefaultConstraints FROM FactList f JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE a ON f.PartitionName = a.TABLE_NAME JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS b ON a.CONSTRAINT_NAME = b.CONSTRAINT_NAME AND b.CONSTRAINT_TYPE = 'Primary key' ) , FactWithoutDefaultConstraints AS ( SELECT a.* FROM FactPKList a LEFT JOIN FactPKList b ON b.WarehouseEntityName = a.WarehouseEntityName AND b.DefaultConstraints = 1 WHERE b.WarehouseEntityName IS NULL AND a.RK = 1 ) , FactPKListStr AS ( SELECT DISTINCT f1.WarehouseEntityName, f1.TABLE_NAME, f1.CONSTRAINT_NAME, F.COLUMN_NAME AS PKList FROM FactWithoutDefaultConstraints f1 CROSS APPLY ( SELECT '[' + COLUMN_NAME + '],' FROM FactWithoutDefaultConstraints f2 WHERE f2.TABLE_NAME = f1.TABLE_NAME ORDER BY COLUMN_NAME FOR XML PATH('') ) AS F (COLUMN_NAME) ) SELECT 'ALTER TABLE [dbo].[' + f.TABLE_NAME + '] DROP CONSTRAINT [' + f.CONSTRAINT_NAME + ']' + CHAR(13) + CHAR(10) + 'ALTER TABLE [dbo].[' + f.TABLE_NAME + '] ADD CONSTRAINT [PK_' + f.WarehouseEntityName + '] PRIMARY KEY NONCLUSTERED (' + SUBSTRING(f.PKList, 1, LEN(f.PKList) -1) + ')' + CHAR(13) + CHAR(10) FROM FactPKListStr f
2. List the data warehouse jobs by using Windows PowerShell cmdlets.
Go to the Computer that hosts the Data Warehouse management Server, open the windows power shell and type in the following commands in order :
- Set-ExecutionPolicy –force RemoteSigned
- cd ‘C:\Program Files\Microsoft System Center 2012\Service Manager’
- Import-Module .\Microsoft.EnterpriseManagement.Warehouse.Cmdlets.psd1
A list of the data warehouse jobs appears. Use this list in the next Step
3. Disable data warehouse job schedules by using Windows PowerShell cmdlets.
Type each of the below commands separately, one after another “Replace the colored parameters”
- Disable-SCDWJobSchedule –JobName Extract_<data warehouse management group name>
- Disable-SCDWJobSchedule –JobName Extract_<Service Manager management group name>
- Disable-SCDWJobSchedule –JobName Transform.Common
- Disable-SCDWJobSchedule –JobName Load.Common
- Disable-SCDWJobSchedule –JobName DWMaintenance
- Disable-SCDWJobSchedule –JobName MPSyncJob
- Start-SCDWJob –JobName MPSyncJob
4. Confirm that the data warehouse jobs have stopped running
From the Service Manager console , go the Data warehouse tab, and click on Data warehouse Jobs, Confirm that the Jobs status is Not Started
5. Download and install Update Rollup 2 for System Center 2012 Service Manager on all Service Manager Components
And we are done with installing the Rollup update.
Download and install SQL 2012 analysis Management Objects on both the Management and the Data warehouse Servers.
You need to have at least Microsoft® SQL Server® 2008 R2 Native Client or Microsoft® SQL Server® 2008 R2 Native Client installed. since i had 2008 Native client installed i will upgrade it to 2008 R2.
Now when upgrading you might face an error with a Services start timeout “The System Center Management Configuration service could not log on with it’s current credentials.”, the upgrade process involves restarting some of the services, that’s when sometimes a timeout occurs leading to upgrade failure and you can see those error in the install logs:
CAStartServices: Attempting to start service. OMCFG
CAStartServices: StartService failed. Error Code: 0x8007041D.
ConfigureSDKConfigService: CAStartServices failed. Error Code: 0x8007041D. OMCFG
Error 0x8007041D indicates that the service did not respond to the start or control request in a timely fashion.
In my lab i faced the below error at the beginning of the installation process, while previously it hit me when it finished the upgrade while starting the services sadly i only have a snapshot for the error i recieved in this lab. anyways the following solution solved it for me in both cases.
This problem occurs because a .NET Framework 2.0 managed assembly that has an Authenticode signature takes longer than usual to load. The signature is always verified when the .NET Framework 2.0 managed assembly that has an Authenticode signature is loaded. In addition, the .NET Framework 2.0 managed assembly may take longer than usual to load because of various other settings. For example, the .NET Framework 2.0 managed assembly may take longer than usual to load because of the network configuration.
There are two workaround procedures that you can use to try to resolve the issue in which an upgrade to System Center 2012 – Service Manager fails as a result of Configuration service Startup timing out:
- Disable signature verification on the computer that is running Setup:
- On the computer that is running Setup, edit the Microsoft.Mom.ConfigServiceHost.exe.config file, which is located in the Program Files\Microsoft System Center\Service Manager folder.
- In the <runtime></runtime> section, add <generatePublisherEvidence enabled=”false”/>
- attempt the upgrade again.
2. To increase the service time-out setting
- On the computer that is running Setup, create the following registry value to increase the service time-out period:
- Restart the computer and retry the setup again.
We are done. Reference “How to Work Around Configuration Service Startup Issues”
As agreed we are going to start with the Data warehouse management Server according to the upgrade order.
Insert the Service Manager 2012 SP1 media and start the installation wizard
We have gone through the upgrade order and timing and taken our backups. i am going to check on both and proceed.
Repeat the above steps you did for the Data warehouse server on the management server, this includes installing the Cumulative Update, installing AMOs 2012, upgrading the SQL Server Natice Client to at least 2008 R2and upgrading to SP1
After Upgrading to System Center 2012 SP1
Now that we are done with the upgrade to SP1, it’s time to check that all services are running, start the Service Manager workflows and restart the data warehouse jobs.
1. Check Service Manager Servcies
from the Services console check Service Manager Services. start any if required.
From the Data warehouse management server type in the below command in order using the windows PowerShell
cd ‘C:\Program Files\Microsoft System Center 2012\Service Manager’
Enable-SCDWJobSchedule –JobName Extract_<data warehouse management group name>
Enable-SCDWJobSchedule –JobName Extract_<Service Manager management group name>
Enable-SCDWJobSchedule –JobName Transform.Common
Enable-SCDWJobSchedule –JobName Load.Common
Enable-SCDWJobSchedule –JobName DWMaintenance
Enable-SCDWJobSchedule –JobName MPSyncJob
Start-SCDWJob –JobName MPSyncJob
3.Stop and Then Start SSRS
That’s it for this article about upgrading Service Manager 2012 to SP1. hope that was helpful.