I am excited about the chatter that has been going on regards to the “Single Server Maintenance Mode App”. As promised I am ready to release an “Alpha” version (also called 0.3a) – (0.1a and 0.2a were internal only releases)
I am unaware about my rights regards to the distribiton of the Operations Manager Powershell Module, so to get this version to work – you need to do some manual work. This is still a very early version of the product, so it contains alot of bugs and errors – the known issues are listed here on the page.
Before we start, make sure that the users executing the app have all the correct rights within SCOM, and that you have the correct network setup to allow access to SCOM.
All SCOM releated ports can be found here.
Read more for installation instructions and the download file.
First of all you need to make a portable version of the Operations Manager Powershell Module. Since this app uses some Powershell to comunicate with SCOM, this is very essential to the software. Lucky for us, Stholo has made a blog post on how to make this fairly easy. The guide can be found here. After you create the portable version of OpsMgr Powershell, create a folder where you want your Maintenance Mode app to be on your server – copy and paste the module into this location (%folderdirectory%/modules/OperationsManager) your dll files and psd1 files must be placed inside this location. In this version the location is hardcoded. This could be a subject to change in future releases.
Inside the root directory of your app, you must now create a simple text file (.txt) named config.txt. Inside this file you must specify the FQDN of your management server (example: scom-1.contoso.com).
Note: The app communicates on port 5724 with the selected SCOM management server
Your folder should now look like this:
and inside your modules folder is a operationsmanager folder, with your portable Operations Manager Powershell module. So far so good. Now you can zip this all together, and distribute it to the servers you want to this this application out with.
This App will only work with SCOM 2012 and later versions
Your config.txt file should look like this (with your own SCOM Management Server FQDN)
Note: Currently this app is only working with Powershell Version 5
!!Please keep in mind that this is an alpha version, and it does contain bugs!!
Currently known issue (updated as more come in)
- DMZ servers, where local users has not access within SCOM (working on a password prompt in these cases)
- Reason/Duration text is not auto cleared when you press a button (working on this for a later version)
- Delay when opening maintenance.exe on some systems (delay connecting to the management group
- Cross-Domain authentication on some domains
Upcoming features (updated as more requests come in)
- Configuration module to set ps module & scom server instead of a text file
- A button to see the current reason for the maintenance
- A complete MSI file to distribute/install through SCCM
- Easier error handling
- Support for earlier versions of Powershell
- Change txt to ini/cfg file
A special thanks goes out to my co-workers Morten & Louis.
This SOFTWARE PRODUCT is provided by THE PROVIDER “as is” and “with all faults.” THE PROVIDER makes no representations or warranties of any kind concerning the safety, suitability, lack of viruses, inaccuracies, typographical errors, or other harmful components of this SOFTWARE PRODUCT. There are inherent dangers in the use of any software, and you are solely responsible for determining whether this SOFTWARE PRODUCT is compatible with your equipment and other software installed on your equipment. You are also solely responsible for the protection of your equipment and backup of your data, and THE PROVIDER will not be liable for any damages you may suffer in connection with using, modifying, or distributing this SOFTWARE PRODUCT.