Spreading the word on vROps!

  Manually adding windows services to monitor via the Ops UI can be very high touch/time consuming and if you have a typical environment that has repeat footprint and duplicate monitoring requirements (multiple SQL and Backup server for example) adding the same set of services from a template can be a life saver. There's a few handy scripts in this one - described below : 1. A script to export all windows services and names to a .csv file (that you can then edit - backup server csv, domain controller csv, file server csv etc.) 2. Script to 'import' the required .csv for enabling 'service' monitoring for the required VM. Usage : 1. On a server you wish to 'template' - use the CSV export script to export all running services details into a file you can edit so that it only contains the required services that your SLA's (etc.) need for monitoring on a server. (SQL engine and SQL backup services for a SQL server etc.) - Save this as your 'SQL' monito...

  So....We've had this software in some form for almost 15 years - still with only a manual configuration backup method!... So I've created a script that can be automated to export the the working configuration on a regular cycle to help avoid those configuration 'oops' moments! The script had a few command line arguments described below -  1. Current (vR)Ops URL 2. Authentication Source (AD, vIDM etc) 3. Username 4. Password 5. Export password for extraction of config 6. Download path to save the export 7. Retention days (script will remove backup files older than this value) 8. Log file path Feel free to adjust this script as necessary! Source is in my GitHub repo - here