You are browsing the archive for 2013 January.

SCOM 2012 SP1 : OMServer.msi returned error 1603

3:53 pm in Operations Manager by Christopher Keyaert

Hi all,

On Tuesday, I was at a customer location to install a new SCOM 2012 SP1 environment. I checked the requirement for SCOM 2012 SP1 on TechNet :
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_ManagementServer 

SCOM 2012 SP1 Management Server :

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  • Processor Architecture: must be x64
  • Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  • Windows Remote Management: Windows Remote Management must be enabled for the management server.
  • .NET Framework 4 is required.

The prerequisites check passed without any problem
image

But the installation failed
image

With the following error :

11:11:16]: Always: :LaunchMsi: Launching C:\Infront\SCOM2012SP1RTM\Setup\AMD64\Server\OMServer.msi
[11:14:16]: Always: :MsiInstallProduct finished for msi C:\Infront\SCOM2012SP1RTM\Setup\AMD64\Server\OMServer.msi.
[11:14:16]: Always: :LaunchMSI: Setting rollback to true
[11:14:16]: Error: :
LaunchMSI: MSI C:\Infront\SCOM2012SP1RTM\Setup\AMD64\Server\OMServer.msi returned error 1603
[11:14:16]: Error: :ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
[11:14:16]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Management Server
[11:14:16]: Info: :SetProgressScreen: FinishMinorStep.

I checked on Internet and found these 2 posts related to that error :
http://www.scom2k7.com/error-installing-scom-2012-omserver-msi-returned-error-1603/
http://thoughtsonopsmgr.blogspot.be/2013/01/om12-sp1-upgrade-beware-for-corrupt-iso.html

Everything was fine with the registry, I re-downloaded the source files from TechNet and also MSDN, started the installation again and it always failed with the same error message.

I decided to go back to TechNet and I checked the requirement for SCOM 2012 (Without SP1) : http://technet.microsoft.com/en-us/library/jj656649.aspx#BKMK_RBF_ManagementServer

SCOM 2012 Management Server :

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1.
  • Processor Architecture: must be x64.
  • Windows PowerShell version: Windows PowerShell version 2.0.
  • Windows Remote Management: Windows Remote Management must be enabled for the management server.
  • Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
  • Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4 are required. For more information, see the following documents:
    .NET Framework 3.5 SP1 redistributable package
    .NET Framework 4 redistributable package

OH OH OH .NET Framework 3.5 SP1 is required for SCOM 2012 and not for SCOM 2012 SP1 ????? Are you really sure of that ??? Let’s try to install it on the server. After a few clicks, it’s installed.
Capture

Let’s give a another try….. and….
image

BINGO, it was simply that !!! I had to install the .NET Framework 3.5 SP1. I already sent a mail to Microsoft and they will update the document on TechNet as soon as possible.

Cheers
Christopher

Orchestrator 2012: Runbook server in an untrusted AD Domain

3:46 pm in Orchestrator by Christopher Keyaert

Dear All,

In this post, I’ll explain you how to install an Orchestrator 2012 runbook server in an untrusted Active Directory domain.
Installing a runbook server in an untrusted AD domain is required when your integration pack or workflow activities are not able to manage several Active Directory domain/credentials and are using only the Orchestrator Service Account to run.

With this new runbook server installed, you will be able to start runbooks from your Runbook management server located in your primary domain and execute it directly on the runbook server hosted in the untrusted domain. You just need to ensure that the service account which is used by the runbook server in the untrusted domain has the necessary rights to execute the required actions in that untrusted active directory domain.

Let’s go for this implement J

Prerequisites:

Definition

I will define two “key words” that I’ll use for the rest of this post:

  • Primary domain: Active Directory domain where you have your Orchestrator 2012 infrastructure installed.
  • Untrusted domain: Active Directory domain that doesn’t have any AD trust with your Primary domain.

Infrastructure

  • An Orchestrator 2012 infrastructure installed in your primary domain.
  • A fresh new installed server in the untrusted domain on which we will install the runbook server role.

Service Accounts

  • In your primary domain, on your SQL server, Orchestrator 2012 SQL Instance, you have to create a SQL User Account that is DB_Owner of the Orchestrator database.
  • Ensure the SQL is in mixed mode and allows connection from AD and SQL accounts.
  • In the untrusted domain, you have to create a service account that is identical (Same SamAccoutName and Password) to the Orchestrator service account that is currently used by the Orchestrator 2012 infrastructure in you primary domain. If the service account used in your primary domain is SA_Orchestrator with the password: P@$$w0rd you have to create the service account SA_Orchestrator with the same password in the untrusted domain. This account must be local admin of the server on which you will install the Orchestrator Runbook server role.

     

Installation:

Logon the fresh new installed server in the untrusted domain and start the Orchestrator installer.

In the Standalone installation part, click on Runbook server.

Accept the licence terms and click on Next >.

Prerequisites check in progress

Specify the service account that you previously created in the non-trusted domain which is identical to the account used in the primary domain.

Click on Test.

Click on Next >.

Specify the SQL Instance (by using the IP address or the FQN if you have a DNS resolution between your AD domain) of the Orchestrator DB which is located in the primary domain.

Specify the SQL user account that you created in the prerequisite part.

Click on Test Database Connection.

Click on Next >.

Select the existing Orchestrator Database and click on Next >.

Specify the installation folder and click on Next >.

Select No, I am not willing to participate and click on Next >.

Review the information and click on Install.

Installation in process.

Installation completed

Click on Close.

You could confirmation that the installation succeeded by starting the System Center 2012 Orchestrator Deployment Manager in your primary domain.

In the Runbook Servers part, you will see the runbook server that you just installed in the untrusted domain.

   

Integration pack installation

 
   

Integration pack installation on a runbook server which is in an untrusted domain must be done domain manually.

For that, go to your Orchestrator Manager Server which is installed in your primary domain, copy the IPs that you want to install on your new runbook server in the untrusted domain.

The integration packs are location in the following folder:

C:\Program Files (x86)\Common Files\Microsoft System Center 2012\Orchestrator\Management Server\Components\Objects

One the IPs copied on the new runbook server, just double click on the file to install.

Ip Installation in progress.

Check in the Add/Remove programs if the IP is well installed.

 

You have new an Ochestrator Runbook server that is installed in another active directory domain that your Orchestrator Management server.
I hope that this post is helpful for your and fell free to post your comments 😉

 

Christopher