inebriates

Hat tip to /u/astromek over at /r/scom for the link. The guy (or lady) is truly a king among men...or women. http://scug.be/dieter/2012/07/25/scom-install-both-scom2007r2-and-scom2012-console/ A big thanks to Dieter at SCUG.be for clarifying the process and an angry scowl at Microsoft for making things so obfuscated and difficult. When having side-by-side environments is a supported scenario, having side-by-side clients should be a much simpler process. In case the post ever goes away, here's the text:

Hi guys, thanks in advance for your help. I'm in a situation where I have inherited a badly designed/maintained/admined Opsman 2007 environment. Permissions are insane...alerts are bonkers...just about everything is crazy. One of my first tasks is to stand up a new 2012 R2 environment and start anew, but it needs to be side-by-side the old environment for 12 months and all of the agents need to be dual homed. If there's any historical data that needs to get pulled we'll just run a report from the old data warehouse. They do not want to migrate any old data, management packs, or anything else. It's all a fresh start. No problem, I can do that. I have my testlab and prod environments set up and working fine. Agent is deployed to about 20 servers each, dual-homed, and we're good to go. With one exception: the damn admin console on our local machines. Each time I try to install the 2012 admin console on my local machine it fails, because it detects the one that's already there. I've dug through Google and Technet and not found this anywhere, so it's either incredibly easy and I'm making it harder than it needs to be or it's not as simple as it should be. Any help you can provide would be much appreciated! Thanks!