This post has been edited and updated for Orchestrator and can now be found on the Orchestrator blog: Quick Tip: Checking PowerShell Scripting Abilities on a Computer

You can find the Operator Console installation superflow here: http://download.microsoft.com/download/F/E/9/FE9A306D-BFCB-48D6-8748-922B0F1F0E68/SF_OpalisOpConsoleInstall.msi Just install this msi and it guides you through the installation of the Operator Console step by step.

When attempting to export a large structure of Policies and/or Global Resources (Variables, Counters, Schedules and Computer Groups), the following error is returned in the Opalis Integration Server Client: "Export operation failed. Please see the Opalis Client and Management Server logs for more information. Additional information: Export failure _com_error, Unspecified error, -2147467259" Exceptions like the following are recorded in the Management Server logs: 2011-01-04 10:03:28 [2632...

Just a heads up on a new Opalis development regarding amd64 support.  Opalis Integration Server 6.3 is officially supported on Windows 2008 64-bit versions. Previous Opalis versions are not supported on any 64-bit edition of Microsoft Windows, and although they may successfully function under a 64-bit environment, this has not been thoroughly tested and may result in unexpected errors and/or poor application performance. Note that Using x64 hardware does not necessarily require that a 64-bit...

When executing an Opalis Integration Server Policy that utilizes the Run .Net Script object, the following error may be returned in the Error Summary Text Published Data of the Run .Net Script object and the object status returns as failed: "Object reference not set to an instance of an object." This can occur if a statement within the code supplied in the Details tab of the Run .Net Script Opalis object is attempting to perform an action against an object that has not yet been instantiated...