If it were my choice, I wouldn't give the console to people who just need to use remote control.
If you need to audit, there's potentially this: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/08/08/inventorying-remote-assistance-requests-and-connections.aspx May or may not work depending upon your scenario; and would need to be updated slightly for CM12 (the mof edits were for CM07) That's a Remote Assistance Request, not RC.exe per se. But maybe that's a better choice anyway? Sherry Kissinger Microsoft MVP - ConfigMgr mofmas...@myitforum.com ________________________________ From: "Marcum, John" <jmar...@babc.com> To: "mssms@lists.myitforum.com" <mssms@lists.myitforum.com> Sent: Wednesday, September 18, 2013 12:54 PM Subject: RE: [mssms] ConfigMgr 2012 SP1 Console Connection Limit I "think" there's a way to audit even if you are not launching the session from the console but I am not sure. I seem to recall reading a blog about how to do that once. I don't think that there is a limit on concurrent sessions but I would not suggest deploying that many consoles. Keeping them updated is a total nightmare. Put it in Citrix instead. Better yet, use something like WebEx or Lync. We just bought Bomgar which seems pretty cool but would likely be expensive for that many users. ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Eric Morrison Sent: Wednesday, September 18, 2013 12:46 PM To: mssms@lists.myitforum.com Subject: [mssms] ConfigMgr 2012 SP1 Console Connection Limit 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 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
