Starting to install the System Center Cloud Service Process Pack Beta #SCOM #SCSM
I spent some time today working on installation of the System Center Cloud Service Process Pack beta (available for download at: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27844. Since I already had a functional System Center 2012 RC environment I had high hopes that this would not take a long time for installation. I ran into a few challenges – I’m putting them out here so that others can learn from my lessons learned (and mistakes made). This installation is NOT complete at this point in time, but I’ve made it through some of the challenges so this blog is to share those so that others can get past them more quickly.
Installation for the System Center Cloud Service Process Pack Beta:
The first step takes place on the Service Manager server: Installing the “Cloud services process pack”
When attempting the installation, mine initially failed because I did not have the VMM Discovery Management Pack installed (it showed Red versus the screenshot shown below once this MP is added):
A discussion on this topic is currently available at: http://social.technet.microsoft.com/Forums/en/systemcenterservicemanager/thread/2d505f89-f7d5-4e3f-bd22-0ba80451e04d
Logically enough, I went to the Service Manager console, Administration and attempted to add the VMM Discovery Management Pack. What I found was that there were a variety of different management packs which that one was dependent upon to allow the import of the VMM Discovery Management Pack. In Operations Manager we can just download and install Management Packs through the OpsMgr console which goes out to a website to download and install them. In this case, we need to download the appropriate management pack dependencies and get these added.
Since we can’t add them directly from the Catalog – they need to be downloaded locally I decided to use an OpsMgr trick to get my Management Packs. In the OpsMgr Console, Administration, Download Management Packs, connect to the Catalog and select all management packs from the catalog as shown below:
Additionally I copied MP’s from SCVMM (c:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\ManagementPacks by default) and from OpsMgr installation media (ManagementPacks folder on the installation media) and from the Service Manager folder (C:\Program Files\Microsoft System Center\Service Manager 2012\Operations Manager 2012 Management Packs). Once these were copied into a single folder so they are easier to add dependent management packs. I attempted to add the discovery and it failed due to dependencies. Next I add the dependency from the folder, and removed the one that depended upon it to continue.
To find the dependent MP, copy the name (Microsoft.SystemCenter.DataWarehouse.Library as the example above) and search for it as a .MP file.
Once I got one to add, I restarted the process again until I could map out all of the required dependencies [this was NOT a quick process to work through, but it worked!]
One note on this – due to versioning differences I had to separately download the Windows Server Management Pack and extract it to get the required version (6.0.6958.0) as shown below.
Once the Management Pack was added, the installation of this piece of the System Center Service Pack Beta successfully completed.
Once it’s installed the next steps are done from the Administration pane, Cloud Services.
Create the Virtual Machine Manager connector:
- To create the VMM connection you really just need an account with permissions and the name of the SCVMM server in the environment.
Create the Operations Manager connector:
- In my environment creating the Operations Manager connector (CI): Currently failing with the error listed below.
Create the Orchestrator connector:
- The Orchestrator connector needs both the Orchestrator Web Service URL (default below of http:://<servername>:81/Orchestrator2012/Orchestrator.svc/)
- Ad the Web Console URL (default below of :82/">:82/">:82/">http://<servername>:82/) – Check IIS for this one
Orchestrator installation looked like it was going to be a breeze but I’m currently stuck on importing the cloud services runbooks as shown below.