I know the reccomended limit of Simultaneous Operations consoles is 50. That being said if I needed 100 consoles just to through out a number what would I do? Does the Web Console count against the 50 consoles. My problem is that I have number of groups that are using SCOM as a montoring tool. but I am afraid that I will slow down the environment by having over 50 consoles. How will it affect SCOM? Do Ineed to create multiple management groups or how can I expand the number of consoles past 50 I want to be able to provide the operations console preferably to these groups so they can view their alerts. Thanks

The maximum for a RMS is 50 consoles, you could place additional management servers to which another 50 consoles are connecting, so you have in total 100 consoles connecting. I don't know how the connections are counting to the web console, I think it's the same. Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

The maximum for a RMS is 50 consoles, you could place additional management server to which another 50 consoles are connecting, so you have in total 100 consoles connecting. I don't know how the connections are counting to the web console, I think it's the same. Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

Hi, Both the Operations console and the web console connect to the Data Access Service (SDK Service). This service only runs on the RMS, adding additional management servers is only useful to move the work of agent communications off the RMS. Adding an additional MS will not directly support more console connections. I think that web console connections are less burden on the RMS than the full console. The supported configuration state that the supported agent count is reduced with more console connections. From http://technet.microsoft.com/en-us/library/bb309428.aspx Agent managed ... computers per management group: 6,000 (with 50 open consoles); 10,000 (with 25 open consoles) So, from this you could presume that 100 consoles would further reduce the supported agent count. Though you would have to clarify that with Microsoft. Matt Matt White ( http://systemcenterblog.hardac.co.uk/ )

Thanks for the replies. I guess that is a good assumption about the agents vs. consoles. I guess I will see about getting an answer from microsoft. I work in a large enterprise with lots of application owners and it would be nice to know if I did not have a hard limit at 50 open consoles and there is some work araound. Thanks for the reply!

There never was a hard limit. in the beginning MS just said, the more hardware you add the more consoles you can support. i think the support limit is based on a test they ran. Btw don't think that application owners will have to console open 24x7. in my experience they just want alerts (email/tickets) and maybe a dashboard view for performance. So concurrent console usuage might be way lower than the number of application owners.Rob Korving http://jama00.wordpress.com/

There never was a hard limit. in the beginning MS just said, the more hardware you add the more consoles you can support. i think the support limit is based on a test they ran. Btw don't think that application owners will have to console open 24x7. in my experience they just want alerts (email/tickets) and maybe a dashboard view for performance (not a sdk session, but a reporting services(dw)). So concurrent console usuage might be way lower than the number of application owners. Rob Korving http://jama00.wordpress.com/

Like Rob mentions, there's not a hard limit. We have noticed a drop off in performance when there are more then 50 consoles in an environment with 6000 Agents and more than 25 consoles in a 10,000 Agent environment. To speak to your questions: 1. The 50/25 reccomendation is for total console connections (# Web Console users + # Desktop Console users) 2. I think 100 Consoles would be a strech for most environments and that would be outside of our supported limits. How many Agents are you monitoring? I suspect that multiple management groups would be the best solution for you, depending on how many Agents you have in your management group. Please refer to our Sizing Helper for offical guidance around console scalability http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=b0e059e9-9f19-47b9-8b01-e864aebf210cMichael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Thanks for the comments Michael. The key information i did not know was if the web console counted the same as the desktop console. I was going down the path of seperate management groups to solve this issue. We have currently around 3000 agents deployed, so at this point we should be alright, but we plan on bringing on another 3 to 4000 agents in the next year.