We recently setup a SCCM environment with a central site and 4 secondary sites. Upon our initial deployment, we were told that it would be best to limit access to the SCCM console to minimize the overhead on our Central site. My questions to the experts here is. What is the limit for MMC connections to the central site? We have a number of Help Desk folks scattered about behind the Secondary Sites, and we know they will be connecting via MMC to the central site for console access. How many should this be limited to for remote assistance? What is the actual connection process for remote tools? Would remote tools broker connections through the primary server or from the console PC to target PC? Meaning what does the traffic look like. If help desk person A is at a secondary site. They open a MMC console to the primary server and initiate a remote tools session with a client, does that traffic funnel back through the central site, or is it just for the initial connection? We are at wits end trying to figure this out, and need any help that can be offered up. Thanks!

Sherry / Ron, I have a question for you. I just performed an SMS to SCCM upgrade for a customer (my 8th installation so far), and at the insistence of the Project Manager, Ron's Web tool v.3.21 was installed for Help Desk use, published on a Citrix server. We quickly started hearing complaints from the Help Desk about Remote Control performance issues. I then had the SCCM admin console published on the Citrix server, and RC performance was great. So the out-of-the-box Microsoft solution (SCCM admin console) works fine, while the web tool has performance issues. My opinion is that we should stick with standard Microsoft tools. What would Microsoft say if I called them with this issue? What recourse do we have to get the performance issues with the web tool worked out? ps. Ron, I'm also an electrical engineer who found himself in I.T., and I also have a passion for Camaros... mine was an '80 which I unfortunately gave up. Thanks, Nick.