Hi, I faced some weird stuff last day and want to verify if this is a known issue / behavior or maybe a bug. I was in the process of installating OpsMgr reporting. We have a seperate SQL 2008 R2 database server and a seperate SQL 2008 R2 Reporting Services server. The issue I had was on the seperate Reporting server. When I went through the OpsMgr Reporting installation wizard, I did not see the 'browse' button to specify the location on the OpsMgr Reporting installation. The installation path was preconfigured to install in 'c:\program files' and grayed out. I wanted the installation to be done on my D: drive. Running to previous installation documents I verified the 'Browse' button should be there. Further investigation I found that it was related to the fact that the server already had the OpsMgr agent installed, which comes automated during our deployment process with ConfigMgr. Ones I removed the agent the 'Browse' button appeared. Is this normal, if not is it worth mentioning as a bug on connect? Follow me through my blog and Twitter!

Hi If an OpsMgr component is already installled on a computer, then additional components have to be installed to the same location. Hence the browse button was greyed out when you looked to install reporting when there was already an agent installed. With the agent removed, you were free to choose the install location. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi Jannes, good to see you again. :-) I would also guess that the agent install had set the default install folder for you this way. I haven't tried to replicate it. I always pre-check if there are any SCOM agent/server software on a machine and remove it before I start any SCOM server install on that box. So just for the SCOM server side boxes. Learned a long time ago that not doing so could mess something up during install, not sure where I got it from the first time though :-). I would say that it sounds like a bug in the installer. Or at least a check inside of it that probably assumes that part of it is already installed (the agent) and that it needs to use those settings for this second piece of software.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient

Okay thanks for the feedback, seems to be 'normal' then. But to me it doesn't make sense to remove the 'Browse' button onces an agent is pre-installed. Or in other words that every OpsMgr component has to be installed in the same location. Specially because we are talking about two different types of components, the ones that are related within the OpsMgr setup it self at the ones that are just outside that same OpsMgr setup. Will mark it as answered, thanks again for the feedback. Follow me through my blog and Twitter!