Well that was easy. I've just started diving into MP Authoring. Solutions like your MP give me renewed energy to try and learn this stuff because it is very clear how much MPs can simplify the SCOM life.
Thank you for your help! Thanks, Geoff From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Thursday, April 16, 2015 12:42 PM To: [email protected] Subject: [msmom] RE: Decommission: SCOM 2007 in Multi-Home Uninstall doesn't work from SCOM 2007 - by design. The agent is no longer a SCOM 2007 agent. Use something like this: http://blogs.technet.com/b/kevinholman/archive/2014/01/29/using-the-agent-scripting-objects-on-a-scom-2012-agent.aspx From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Thursday, April 16, 2015 2:12 PM To: [email protected]<mailto:[email protected]> Subject: [msmom] Decommission: SCOM 2007 in Multi-Home We started fresh with our SCOM 2012 environment because we had lots of issues with our 2007 setup. All agents are now multi-homed and all MPs/Monitors/Rules/etc. have been recreated on the new 2012 side. I want to decommission the 2007 server, but I am running into an issue where, so far, not a single uninstall has worked within the SCOM 2007 console. They all give a generic error (Error Code: 80070643). Automatic Update service is running as well as no WMI issues seem to be apparent. However, it looks like it might be a waste of time trying to troubleshoot uninstalling via the console, but wanted to ask others opinions regarding the agent uninstall from 2007 console. Is that uninstall merely removing the management group entry on the agent side? Or is there more to it beyond that Management Group entry in Control Panel > Microsoft Management Agent? I did see a few scripts online that allow you to remove the management group you specify, but I want to make sure this wouldn't cause future issues down the road. We have no desire to keep the 2007 environment in place (or retain any historical data) due to its misconfigurations and issues throughout the years. Is there an easier way than troubleshooting the 300+ servers one at a time? I was hoping this would work, but didn't want to make any assumptions: https://gallery.technet.microsoft.com/Remove-a-Management-group-336c849a/view/Discussions#content Thank you. Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
