What Opalis scenario would *you* like to see built and run?

I’m very interested in building out scenario’s that you want to see.  So the easiest way to do this, is for you to tell me what you want to see!

Please post in the comments 🙂

Comments (13)
  1. Anonymous says:

    I want to see capacity management in the virtual environment, for example Vms running IIS web sites and SCOM raise alert in VMM with PRO integration that the demand for this VMs is high so Opalis will proviosn some new VMs to meet this demand and after a while when SCOM raise a new info that the traffic now goes low,, it will save them again

  2. Hi there!

    We use different CR- tools and all of them are posting approved changes to an exchange calendar with some information in a table.

    It would be great to see, if Opalis is able to get these appointments (every hour or with a monitor function) and sets the objects found in a specific field in SCOM maintenance mode for the scheduled time.

    Thanks, Patrick

  3. I would like to see a patch management scenario of servers, walking up a collection tree (Patch Grp A, B, C), increasing the number of servers to be patched while putting them into maintenance mode in SCOM R2 while they're being patched/rebooted, but only during a maintenance window as set in ConfigMgr.

    Oh… and why not throw in an SCSM alert while we're at it if the server doesn't sucessfully reboot after the patch.


  4. Jim Jankowski says:

    Exactly what Steve Beaumont said!!  With the added capability of pulling systems out of maintenance mode in SCOM R2 (in a specific order) when rebooting after patch verification is complete.

  5. Hello,

    I also would like a video to demonstrate the patch management of servers, and if possible with a flow of servers owner approval (may be simply by a email).

    EX : Everymonth the system sends a email to all the servers owners with the name of their servers, the number of patchs that needs to be installed and a planned date of installation. If no sign of the servers owner, the installation must go on, if the system receives a refusal email from the servers owner, the patch changes to pending for manual review.

    Thank you

  6. Sean Hayes says:

    Similar to Steve, I would love to see patching of servers, but specifically a cluster.  An example of patching one node, confirming it comes back up, failing over, patching other side, etc, would be very useful.

  7. Eric Egan says:

    I would like to make SCOM smarter. Can Opalis run a check on all active alerts we assign to Opalis in SCOM and recheck them every X minutes to see if they are still valid and if not close the alert.  Just right click the alert and assign to Opalis. Yes SCOM should do this but……

  8. David Young says:

    I am trying to migrate from alerting with Notifications via SCOM to using Opalis to monitor all the alerts making process decisions depending on the management pack or specific server. I am definitely struggling with this. I found monitoring a single Alert/Monitoring fairly easy but to be able to do a whole management pack or selection of servers is whole different story.   I am still very green and very excited with the product. I am look forward to more scenarios toward integration with SCOM.

  9. Matt White says:


    How about migrating to a new helpdesk system?  Using the integration packs, you could migrate from Remedy to Service Manager by synchronising the incidents from one to the other.


  10. I agree with the common theme of Server Patching (expecially for clusters).

    managing patching of nodes, failover, verification of patching, failback and notification of sucess

  11. Riaan Venter says:

    Yea hah, how far can we stretch this request? I'd like to decommission a Hyper-V Guest by means of filling in a sharepoint form or likewise, the workflow should follow something like this:

    1. Fill in sharepoint disconnection request with server name, shut down and final disconnection dates etc.

    2. Disconnection notification email gets sent to engineers.

    3. Customer Intranet is updated with the disconnection notification (sharepoint).

    4. Final DPM backup is taken.

    5. SCOM, SCCM etc. Agents are uninstalled from the machine

    6. Machine gets shut down

    7. Two days later a final disconnection notification is sent out, customer sharepoint is updated and the machine is deleted.

    9. Rename the SAN disk so it can be allocated to a new machine (am I getting a bit cocky with this one..?)

    An email notification (or some sort of notification) is to be sent out to the appropriate person after each step.



  12. Thomas Bäcklin says:

    In an environment with several SCCM hierarchies in different AD´s it would be great to have a workflow that can automatically copy software packages including collections, advertisments and rules.

    There should ofcourse be some stops on the way like when the packager is done with the application they can send it to the test environment but not to production, this step needs to be signed off by an administrator or similar.

    It would be great if this function also can copy Software Updates (update lists, deployment package, deployment templates and packages) between different hierarchies.

    Options for DP assignment is also desirable.



  13. Owen C says:

    I would like to be able to reach out and issue telnet commands to network devices.

    This would include doing tasks such as regularly scheduled backups of net work router and switch configurations.  There are also devices like our APC MasterSwitch units that if we have a telnet interface we can control the unit from it.

Comments are closed.

Skip to main content