Using FQDN rather than hostname when remote control connects to client
A no-brainer, use FQDN to Remote control so my helpdesk guys can remote to any machines, regardless of the domain. There are powershell scripts out there but they're very temperamental. I don't understand how this has never been design this way, very poor design choice with hostname. This would save a lot of headaches here and people would appreciate sccm remote control a bit more.