you could take a look at Quest Management Extensions. it’s pretty cheap. if you’re running on HP servers, HP has a vmware mp that either uses ESX or the Gen8 servers’ new ILO to talk communicate with scom. but if […]

i wasn’t reading the MP name in the error carefully enough. for some reason the Import process did not make me reference “Microsoft.Windows.Server.Library.” i manually added it and now it builds.

now… to break it myself.

Thanks David. my script is going to run on the agents, so I was looking for a local way to find the management server name configured in the agent settings. it will be passed to an invoke-command later in the script.

Is it visible anywhere? A report? If not,  what’s it for?

the only issue i had with my upgrade to sp1 was one of the console upgrades (on a workstation) apparently did not go well. the install didn’t throw any errors, but afterwards i could not open dashboards with it. […]

i didn’t see any documentation on modifying a config file… where did you find that? in my case, i just created reverse dns entries for my network devices, and scom named them that way. of course, i don’t have […]

opened a ticket with MS. i really should have known… the same #$*! “biztalk 2006″ management pack that broke my 2007 to 2012 upgrade

<a […]

i like having it in the health explorer, like the out-of-the-box CPU diagnostic task. and i don’t mind using the command line method. i was really just curious if there was any reason not to do it that way. as an […]

thank you sir. i just found those. i created a new folder under the references and copied all the MPs there. oddly, a live MP i exported from my SP1 management group did not want the sp1 version of the […]

thanks for checking guys. my unofficial solution to this was to uninstall and reinstall the ops console from my PC three times. two didn’t do it.