An impasse over carriage rights fees may result in a blackout of Comcast SportsNet Chicago for Dish Network subscribers beginning next month, potentially cutting off Chicago Bulls and Blackh...
. We just released Remote Control 5. 1. One of the toughest to build (for us), but most interesting additions to this version is the ability to jump into a remote desktop session. What does this mean? Lets say you have a user that is logged into your terminal server, and you need to help them with something. Usually you would need to use the Microsoft Shadow program: If you have ever used it, you know it is a pain to use. Especially if you have a user on the phone waiting for help. With Remote Control 5. 1, you can connect to the machine, and just pick the user account from a drop down list: Even better, on Windows 7, XP, or Vista machines you can see those remote desktop sessions too. This is not even possible with the tools provided by MS. We also had to work real hard to fix an issue that has been around for a while. If you have fast user switching enabled on XP: Sometimes you would get a blank screen when connecting to the machine. The same is true on 2003 (and XP) if you use Remote Desktop to connect to it with the /console flag.
By right clicking on the user, you will be presented with the following options: Select Shadow and you will be presented with a Shadowing options box. As mentioned earlier, you have the option of viewing, controlling and prompting for user consent. For this example we are going view and request the users permission to shadow their screen. Once the request has been sent, you will see the Remote Desktop Connection loading box. The requester will see this box until the end user actions the request. If the end user refuses the connection, you will see the above error. When the user selects yes, you will then be able to view their screen. As you can see from the screenshot, we are now viewing the user's screen. If we try and access the User's session with out their permission, we are presented with the following error message. This is an out of the box feature and to disable it, you will need to apply a Group policy. The Group Policy that needs to be changed is located under Administrative Templates>Windows components>Remote Desktop Services>Remote Session Host>Connections.
or you can request it. It also depends what other tools you have - do you have SCCM? No sadly nothing that advanced. The PowerShell connections work fine to connect to the workstations and shadow. bbigford This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Sep 8, 2019 at 14:29 UTC Flextechs is an IT service provider. jonesc wrote: No sadly nothing that advanced. The PowerShell connections work fine to connect to the workstations and shadow. Have you considered getting some actual remote software at this point? There's some affordable options out there, especially at smaller scale. In Server Manager, RDS Collections, Full Desktop, right click the User and shadow Wow that's a great find Will that work to a domain joined windows 10 workstation? That will connect to any workstation using RDS not for a user logged in directly to a server. Thanks Justin does that script work for connecting to workstations stand alone on the domain?