Hello Everyone,
I'm currently at a client doing a ConfigMgr 2007 to ConfigMgr 2012 SP1 migration. Currently in their 2007 environment, they use the built-in remote control features of ConfigMgr to connect to different machines throughout the organization for support scenarios and different testing situations. The way they are handling this currently is RC.EXE and the required DLLs sequenced up in an App-V package and made available to all users via RAP (Run Advertised Programs). The only problem with this, is they can't centrally audit who is connecting to what machine, etc. In 2012, they want to be able to do this, so I suggested setting up RBAC for remote tools users and we sequence the new ConfigMgr 2012 SP1 console. They like this idea, but then I found out that they have roughly 1,200 different people that use the remote tools feature to connect to different machines throughout the organization. Apparently the RC.exe workaround will work in 2012 still, but just in case we decide to allow that many people to use the console for remote tools purposes, what is the concurrent connection limit, if any? If there is not a hard limit, are there any guidelines to support a large number of simultaneous connections with the ConfigMgr console? Even though 1,200 people may use this feature, only around 30-50 at any given time will probably be connected. Thanks! Eric Morrison
