We have SMS 2003 installed and a group of users who use remote tools to open a console session to do some work on a program they use three days a week. SCCM 2007 does not allow this same functionality. The people in this group cannot be given local admin rights. I've read where that is the solution. I've also read there has to be a separate connection already open for them to use this and that is not a valid solution either (part of their procedure is to reboot the server, open the SMS Admin Console (in a Terminal Session) and then open Remote Tools on the server in question). As I stated in the beginning, this works fine in 2003, why was this changed? We are now looking at the possibility of purchasing a third party tool, which we would prefer to avoid due to the fact we are an ALL Microsoft shop.

The why doesn't really matter, it's not there and there is no option to allow logins via remote control unless there is an active console session. ConfigMgr 2012 does restore this functionality.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I disagree, Jason. The why would not matter had Microsoft not offered this functionality in the product SCCM replaces. To remove it without a replacement leaves the customer no choice but to purchase a third party product. This one feature is what is preventing us from moving forward with SCCM. WSUS still works, so that is not a concern, but this not working is.