Hello together, I started a thread s while ago asking about scripts etc. I am not at a point where I don't know if I should go the way of Powershell or VBScript to get rid of my batch monitoring scripts. Powershell hasn't been installed on all of my Servers yet and I wasn't planning to do it etc. Can someone tell me what the advantages and/or disadvantages might be here? Regards, M.

If PowerShell is not installed, VBScript will be the best option I think. I have put together quite a few samples and tutorials over the last three years to help with this. See these for a start Taken from http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/19269/Default.aspx Scripting-related Articles and Posts o OpsMgr: Writing and debugging OpsMgr 2007 scripts outside of a live Mgmt Group o SCF Scripting Series Part 1 - Converting MOM 2005 Scripts to OpsMgr / SCE 2007 o SCF Scripting Series Part 2 - Custom Performance Objects o Scripting Series (Part 3): Debugging Runtime Scripts for OpsMgr and SCE o Using the Property Bag with Custom Scripting in Operations Manager 2007 <—This is the big article on the PropertyBag and custom Performance data' o How to create a Script-based 2-State Monitor <—This pdf illustrates how to get your OpsMgr scripts into a monitor o Scripting Tip: Valid Event ID ranges when using the MOMScriptAPI.LogScriptEvent method o Scripting Tip: Making sure your script is executing with the proper credentials Sample Downloads (to go with the articles above) Remember to login to get to the Downloads (registration and download is free) o SCF Scripting Series Mgmt Pack - Part 1 o SCF Scripting Series Mgmt Pack - Part 2 o Script: Registry Value Check for use in a 2-state monitor in OpsMgr 2007 o Script: Windows Service Configuration Script (Service Startup) for 2-State Monitor for OpsMgr / Essentials 2007 o Script: File Version Check Script for 2-State Monitor o Script: Windows Process Monitor for use in a 2-state monitor in OpsMgr 2007 o Script: File Count Monitoring for OpsMgr 2007 o Script: Query Value from SQL Database (for 2-state monitor) o Script: Query Value from SQL Database and Log Event o SQL Database Backup Monitoring (for 2-state monitor) o Monitor File Age for Multiple Files (for 2-state monitor) o Windows Script Host Version Check o Local Port Monitor o Windows Service Recovery Monitor o String match (full line) in text file o Top CPU Processes to OpsMgr Event Log Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com

For both i can't really think of a disadvantage. It's more preference for either of them. For the reason you mention i find myself using vbs a lot more often than ps, but i suppose when you run a w2k8 (r2) environment you probably would use powershell a lot more.Rob Korving http://jama00.wordpress.com/