Beep boop - this is a robot. A new show has been posted to TWiT…
What are your thoughts about today’s show? We’d love to hear from you!
With regards to the RDP file, this is a common file used in most businesses. It contains the connection information and the settings required, plus the certificate, of the server the user needs to connect to in order for them to perform their duties.
In our case, we have a server farm and the RDP file is configured to send the user over the broker, not directly to one of the individual servers. Using the remote desktop tool to go to the broker won’t work as the user can’t log onto the broker and the individual servers on the farm won’t allow direct connections. Getting the users to enter the couple of hundred characters of configuration information into the command line every time they want to access the server in order to do their work just isn’t realistic.
Also, which monitors it should use (one, two, all, the left 2, the right 2 etc.
90% of our users have to use the terminal server farm in order to do their work.
The access to local devices is also critical - Hello and card readers in order for the user to legitimate themselves on the server; local printers so they can print, when they are in home office (their local printer isn’t accessible to the server on the company network); file access in order to upload files or download files.
That said, we have had .rdp files on the block list for emails for over a decade, because it is such a obvious method for getting access to the local system.
1 Like