Integrating Opalis with SCVMM

Though I openly profess my love for Opalis, I got to say there are still much room for improvements and if you ask me … the first thing in my mind would be documentation.

Yes, we were given powerful orchestration objects that integrates with different management systems but what lacks is the documentation on how to set things up. Well, I am not going to whine alot here but to concentrate on just blogging on how to get Opalis to integrate with SCVMM.

Out of the box, the SCVMM Integration Packs offers a rich set of VMM functionalities ranging from creating VM to Remove VM as depicted below.

Now in my previous postings, I have shared with you on installing Opalis and deploying Integration Packs. This posting basically revolves around getting those Integration Packs to work and I am going to start with SCVMM, not that this is the first that I have tried but the first that actually gave me some time to crack my head and get it working !

Now in essence there are a couple of ways to integrate Opalis with SCVMM;

• Connect via WinRM (Remote)
• Connect locally (Requires VMM Console to be installed in the Action Servers)

Approach 1: Win RM

The first approach requires you to configure a couple of things on VMM Server as well as your Action Server.

• In your VMM Server, Open your command prompt and run the following command

winrm quickconfig

• Then launch Windows Powershell and run the following command

set-executionpolicy –ExecutionPolicy RemoteSigned

• Now for each of your Action Servers, run the following command in the command prompt

winrm quickconfig

• And followed by

WinRM set winrm/config/client @{TrustedHosts="RemoteHost"}

RemoteHost = FQDN of your VMM Server

• Once that is done, launch the Opalis client console and goto Options –> System Center Virtual Machine Manager

• In the Prerequisites configuration click Add and enter the necessary information.

• Computer Name = VMM Server name
• User: User Account which has administrator rights on VMM
• Domain:AD Domain
• Password: User Password
• VMM Server = VMM Server name

(Leave others as default)

• Now lets get it rolling …  to test whether your connection works drag an object from the VMM IP to the workbench and try to connect

• Now many of you might be wondering, how come my account does not have enough rights to access VMM (especially that account is the VMM admin !!!)
• Now let’s revisit the connection page again … this time remove the user credentials …

• And if we try things again … and this time it works … so much for entering the user credentials eh.

• Now I try to make a logical explanation behind this and yet I still can’t find any that makes sense … but hey … .as long as it works right !

Approach 2: Connecting Locally

• Unlike the previous approach, you just need to have VMM console installed in the Action Server and you are clear to go.
• You do not need to set WinRM configurations on your VMM as well as your Action Servers to do so.
• Nevertheless, the “rule” for setting up the connection settings to VMM still applies …

Hope this gets you guys rolling and have fun exploring Opalis-SCVMM !

 

Unable to load Active X Control in Self Service Portal–Request Software module

In Self Service Portal, when you try to request for a Software Request (Self Service Software Request) you will be prompted that Active X control cannot be loaded.

To resolve this, you need to install the PortalClient.msi file which is located in the installation CD

Once you have that install .. you are clear to go …

Service Level Management in Service Manager 2010 ? YEA ! You better believe it !!!

Noticed something different in my Incident Form? Yes, for those who have been playing with Service Manager 2010, you will surely noticed that … wait for it … wait for it … Yes ! an SLA component in the Incident form !!!

Many would be surprised that since when Service Manager has a SLA module?

Let me introduce SLA Management Pack for Service Manager from Cased Dimensions.

Like many SLA module, the SLA MP provides you to create the SLA policies to be attached to your Incidents, Change & Problems in Service Manager.

You can flexibly setup your working calendars for different business units to accurately measure your SLA against your official working hours in your organization.

Now with this Management Pack, Service Manager is ready to be join the big boys in  the ITSM realm … bring it on !!!

For more information about the SLA Management Pack for Service Manager, have a look at

http://www.caseddimensions.com/service_manager_SLA_management/

 

Installing Opalis Part 3 – Upgrading to Opalis 6.3

Let’s get straight into action shall we …

• Extract the Installation resource for Opalis 6.3
• Open the Management Server installation folder. By default, this is located in C:\Program Files\Opalis Software\Opalis Integration Server\Management Service. Browse to the Components\Objects folder.
• Copy the OpalisIntegrationServer_FoundationObjects.msi file provided in this release to the System Drive:\Program Files (x86)\Opalis Software\Opalis Integration Server\Management Service\Components\Objects directory. Replace the existing file.
• Uninstall the existing Foundation Objects via Add/Remove Programs
• Reinstall the Foundation Objects from the newly copied source.
• Run the OpalisIntegrationServer_ManagementService_630_PATCH.msp installer. Do not change any of the default values.

Now let’s deploy the Action Servers in our Opalis server

• Click Run, click Programs, click Opalis Software, click Opalis Integration Server, and then click Deployment Manager.

• In the Deployment Manager console, Right Click at Action Server and select Deploy New Action Server

• In the Service Information screen, enter the name of your Action Server and enter a user which will be the action account.
• 

• Proceed throughout the entire wizard setup by accepting the default values to kickstart the deployment

• After you deploy the clients from the Deployment Manager, copy the OpalisIntegrationServer_Client_630_PATCH.msp file included in this release to each client

CONGRATULATIONS !

YOU ARE NOW AT OPALIS v6.3

Installing Opalis Part 2 – Upgrading to Opalis 6.2.2 SP1

In Part I of my posting, I have shared with you on the steps to install Opalis 6.2.2.

In this part, I will share with you on the SIMPLE steps to upgrade to SP1

• Start off by extracting the installation source which is the \Opalis Integration Server 6.2.2 Service Pack 1_6.2.2.51310
• Execute the OpalisServicePack1.msi file
• Choose to unzip the installation files to a folder eg:C:\OpalisSP1
• Navigate to the installation folder of Opalis, eg:

C:\Program Files (x86)\Opalis Software\Opalis Integration Server\Management Service\Components\Objects

• Replace the existing OpalisIntegrationServer_FoundationObjects.msi file with the OpalisIntegrationServer_FoundationObjects.msi file provided in this service pack.
• In Add or Remove Programs, uninstall Opalis Integration Server - Foundation Objects.
• Run the OpalisIntegrationServer_FoundationObjects.msi installer. Do not change any of the default values on the installation screens.

Congrats, you have upgraded Opalis to SP1. As I said … Simple right

Installing Opalis Part I – Opalis 6.2.2

WARNING: This POST IS A LONG EXHAUSTIVE ONE AND YOU HAVE BEEN FOREWARNED

The recent release has created many waves throughout the entire System Center community and I wanted to share some of my experiences throughout my journey exploring Opalis since it joined the System Center familiy. And I would like to start my sharing with some postings on the installation steps for Opalis from 6.2.2 –> SP1 –> 6.3

Now in Part I, I will commence with the installation of Opalis 6.2.2, the very first version of Opalis since it joined the good old System Center family

• To kickstart things, my Opalis server runs on Windows 2008 R2 (x64) and has been installed with MS SQL Server 2008 SP1 (x64)
• You will also need Windows PowerShell 2.0 installed (to automate Operator Console installation)
• Once that is done, extract your installation resources
• The installation version would be \Opalis Integration Server 6.22_6.2.2.5229 as depicted in the picture below

• Kickstart Installation by executing the Setup.exe
• Click on Install Opalis Integration Server

• On the next screen, click on Install the Management Server

• Accept the Licensing Agreement and goes Next
• Proceed with defaults until you reach the Logon Information step. In this step, you need to provide a valid user account that will be used by the Opalis Management Service (basically that is your Service Account). Enter a valid user and proceed to commence installation of the Management Server.

• The next thing you need to do is to configure the datastore (which simply means configure the Opalis DB). Simply click Configure Datastore to commence the process

• The next screen will need your input the select which database will host the Opalis DB and since we LOVE Microsoft so much … I will choose MS SQL Server and proceed

• Now in the Server details, enter the DB server and the authentication method and proceed (In this case, my SQL is the same as the Opalis server and I have set to use Windows Authentication during the installation of SQL Server)

• Give the name for the Opalis DB and proceed to let installer do the rest.

• The next step is to import a license for Opalis. In the License Manager, click on Import. When prompted to Import license, enter the license key and the corresponding license file made available for you either as a customer or an evaluator. Once you are don, click Close

• The next thing that you want to do is to Install the client

• Accept the license terms and accept defaults and let the rest roll by itself.

AND YOU THOUGHT IT’S ALL DONE SO EASILY ??? THINK AGAIN … YOU HAVE JUST GONE THROUGH THE EASY PART.

• When I first started to install Opalis, I dreaded the way they forced us to install the Operator Console because unlike the always easy Microsoft Wizard based approach, we are tasked to “install” the Operator Console by a series of copy & paste of java object which is SIMPLY PAINFUL
• Even preparing the installation for Operator Console is a bitch simply because you need to manually prepare the pre-requisites which would be:
• Download JDK 6 Update 4 from http://java.sun.com/products/archive/
• Download JBoss Application Server 4.2.3.GA from http://jboss.org/jbossas/downloads/
• Then you have a very long list of Pre-Requisites of Java Objects that is scattered all over the internet which I am kind enough to download and made available for you at my SKYDRIVE folder at http://cid-8b468d6e5c4e0782.office.live.com/browse.aspx/Opalis%20Pre-Req
• Well, apparently things have changed when SP1 was rolled out where our lives are made abit easier where Microsoft provides us with an installation script to automate the installation steps.
• Extract the Installation Resources for the following \Opalis 6.2.2\Opalis Operator Console Installer Script 1.0_1.0.0.0001
• Run the OpalisOperatorConsoleInstaller.msi file
• Create a new folder C:\Libraries

Copy all the pre-requisites file that you have downloaded from my skydrive into this folder

• Install Java Development Kit 6 Update 4 by using the default settings.
• Set the JAVA_HOME system variable to the directory of the local Java Development Kit. By default, the location is C:\Program Files\Java(x86)\Jdk1.6.0_04.
• Add %JAVA_HOME%\bin to the Path Environment variable.
• Extract the contents of the JBoss Application Server 4.2.3.GA to the folder where the JBoss Application Server will run. Eg C:\JBoss.
• Launch the command prompt, change to the C:\Libraries folder and run the command

java -jar JAXWS2.1.2-20070917.jar.

• A license dialog box appears.Accept the Sun Microsystems, Inc. License Terms. The JAXWS2.1.2-20070917.jar file will be unpackaged.
• Confirm that the \Jaxws-ri\Lib folder was created.
• Click Start, click Programs, click Accessories, click the Windows PowerShell folder, and then click the Windows PowerShell item.
• At the Windows PowerShell prompt, type

set-executionpolicy RemoteSigned.

• Type the full path to the location where you installed the InstallOpConsole.ps1 file. For example, C:\OpConsoleInstaller\installOpConsole.ps1

• Follow the on-screen prompts. You will be asked to provide configuration information, for example:

a. The full path to the location of the \JBoss folder.

b. The full path to the location of the \OperatorConsole folder.

c. The full path to the location of the \Libraries folder.

d. The database type (Microsoft SQL Server or Oracle).

e. The name of the database server, for example, localhost.

f. The database authentication type (Windows authentication or SQL Server authentication). For SQL Server, provide the user name and password.

g. The name of the Opalis database.

h. The user authentication type (Stand-alone or Active Directory). For Active Directory, provide the Active Directory root DN, Domain Controller, Port, and SAM account name for the administrator group.

• When the Operator Console installation complete message appears, click Close
• Start JBoss by executing the following command in the <JBOSS>\bin folder:

run.bat -b 0.0.0.0

Ladies and Gentleman, you will know that the Operators Console installation is successful when you see the following:

Now I will end the rather exhaustive post on this Part I and will continue with the next Part where I will share how do you patch Opalis to SP1.

Note: I will only deploy my Action Servers & Integration Pack once I am done with the installation up to version 6.3

Till then …. STAY TUNED.

What else do I need to do to protect my SharePoint 2010 Server

I got hit with this problem when I was trying to create a Protection Group in DPM to protect our SharePoint 2010 server in our R&D lab. I have already did the necessary pre-requisites on the SharePoint server such as:

• ConfigureSharepoint.exe –enableSharepointProtection
  
• ConfigureSharepoint.exe EnableSPSearchProtection
  

However I still got hit with the error of not meeting the pre-requisites when I tried to create a new protection group for SharePoint

I went over to the SharePoint Server and noticed that DPM agent could not find the registry key that denotes the SharePoint version:

HKLM\SOFTWARE\Microsoft\Share Tools\Web Server Extensions\14.0\Version

I immediately go to the Regedit and yes indeed that the registry key value is not there. I manually added a new String Value and named it as Version and give the value as 14.0.0.4762.

Go back to DPM console and Voila ! it works !!!

Opalis 6.3 is released

I have been following on Opalis since it was bought over by Microsoft earlier this year and has been impressed by what it can do since. And with the recent release of Opalis, the version 6.3 now supports Opalis installation running on Windows Server 2008 R2 (Yes, unfortunately as at Opalis 6.22 SP1 we can only run them from Windows 2003 which some of my customers gives the evil grin smile). Another noteworthy addition is the introduction of Integration Packs to support Microsoft Sytem Center Suite of products namely:

• System Center Configuration Manager 2007 (which supports SCCM 2007, SCCM 2007 R2 & SCCM 2007 SP2)
  
• System Center Operations Manager 2007 (Support for OpsMgr 2007, OpsMgr 2007 R2 has already been there since Opalis 6.2.2 and as of installation on 6.3 I have not seen additional objects)
  
• System Center Data Protection Manager
  
• System Center Virtual Machine Manager
  
• System Center Service Manager 2010
  

Those who are interested can download the 180 day trial from

http://www.microsoft.com/systemcenter/en/us/opalis.aspx

I have been lucky enough the be able to participate in the BETA testing of version 6.3 and honestly I feel that the new IPs are extremely interesting to explore on. Honestly, Don't expect the IPs can do wonders and and able to automate/integrate with all the functionalities of the System Center products as its still V1.0.

As I am working on Opalis for quite some time, I do have some thoughts that I hope to share … stay tuned.