70-247 Series: Part 11

Upgrading to Orchestrator

To upgrade from Opalis Integration Server to Orchestrator 2012, you must be running Opalis Integration Server 6.3. The upgrade path involves exporting Opalis Policies and importing them into Orchestrator as Runbooks.

To migrate Opalis Policies to Orchestrator:

  1. Export the policy using Opalis Integration Server 6.3 (Actions -> Export)
  2. Import the policy using System Center Orchestrator (Actions -> Import)

Imported Runbooks must be modified and tested to be used in Orchestrator.

The following considerations must be made:

  • Opalis Policy Mode setting - Legacy mode is not supported
  • Multiple starting points - Not available in Orchestrator
  • Cycles - Not supported in Orchestrator, only supported in Opalis legacy mode
  • ROI is not supported
  • Some objects have been replaced/merged, e.g. Manage text file, Process Email, Filter Email, etc

Check-in and test the runbooks.

Next, we’re going to take a look at upgrading to Service Manager.

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

gPLink and gPOptions

gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se...
Read more