In order to provide a more consistent experience with the System Center product family, we've moved the Orchestrator blog to another blog at http://blogs.technet.com/b/orchestrator. Be sure to go there for all the latest info!
Here's another new Opalis KB article you might want to be aware of. With this issue, when navigating to one or more specific policies using the Opalis Integration Server Client, the client becomes unresponsive for a long period of time before recovering or does not recover at all.
When viewing the process (OISClient.exe) in Task Manager, the process may show 100% CPU usage. In addition, when viewing the OpalisManagementService.exe process on the Opalis Integration Server Management Server computer, it also may show 100% CPU usage.
Closing the Opalis Integration Server Client gracefully (if possible) stops the CPU usage of the Client and allows the OpalisManagementService.exe process to cease consuming 100% CPU and return to normal consumption. Terminating the OISClient.exe process from Task Manager stops the CPU usage of the Client but OpalisManagementService.exe may continue to consume 100% CPU unless it is also terminated using Task Manager.
To read all about the cause and how to fix it see the new KB article below:
KB2104676 - Opalis Integration Server Client becomes unresponsive when navigating to one or more specific policies