Today I'm really pissed off.
The website of my #remote #desktop management application of choice has been blocked by our corporate's policies, therefore I can't download any more updates for it...
So this application is unsafer by a tiny bit every day new versions are not installed and I cannot guarantee, under my responsibility, that it is being stewarded (...updated, assessed...) correctly. So I can only remove it from my system.
Why don't I use a single RDP server and access all the others via console? Yes I do it for most of the job, but sometimes you've got to see what it feels like, you need to launch installers, applications and graphical tools that all the #Powershell of the world can't give you a feedback about.
Why don't I use #RDM by #Sysinternals? Because I can't do it properly, as some specific settings on our environment makes it unusable. Well, I could use it if I really wanted to script the remote servers creation phase, injecting the extra settings needed by the .rdp files, but...
Fuck you! I refuse
I will not do this. I will just keep a folder where I'll add a new .rdp file, manually crafted, every time I need to access one of my more than 700 supported Windows servers. It will take an insane amount of time, but this is how my company wants to spend their money, otherwise they would have provided me with the same capability they brought me away.
I was so pissed off that without realizing I built my menu-based RDM app from ground up in Powershell, and I'm going to share it on #Codeberg in the next days.
* List servers in a .csv file with some properties
* Pattern-search or filter the list by properties
* Connect to a server via mstsc
* Generate the .rdp for a server
* Add (or update) a server to the list
* Remove a server from the list
* Keeps track of last connection timestamp and connection count for each server
Select command: (<C>onnect, <G>enerate .rdp, <L>ist, <A>dd, <R>emove, e<X>it)?
