As you probably already know, by default, Microsoft Remote Desktop listens on port 3389. This is all good, but what if you are behind a firewall and wanted to allow port forwarding to be able to access multiple computers via RDP remotely but can’t because they are all running on the same port?
Well, if you’re crafty and have a decent Linux-based router like Mikrotik that will let you create packet mangling rules to change the destination port number, you can get around this, but in environments where you have little SOHO routers like Linksys or Belkin, typically this is where changing the port number that RDP listens on comes in handy. The only problem then is remembering whatever port you changed it to because then you have to specify it anytime you connect via RDP which can be a pain if you’ve got a bad memory. There are already a thousand and one articles out there to help you change the port number, this is a quick post for future reference for myself.
Continue reading “Remote Desktop Server – Registry Key to Change RDP Listening Port”
This is just a follow up to my experiences customizing the Ribbon UI icons in Server 2012 and where the path has taken me thus far. After many hours of research and development and a lot of head scratching, I’ve written several posts on how to disable the different icons in the Ribbon UI which requires the adding or editing of keys in the CommandStore section of the registry for Windows Explorer. For more information on how to disable the icons, see this post.
My whole goal as of late was to be able to add these registry items to the RDS server’s GPO to be able to deploy these settings to all 7 of my RDS servers but then I found out you can’t take ownership of the CommandStore subkeys with the local “SYSTEM” account. Yet another deliberate Microsoft setback meant to discourage people from editing the Ribbon UI, oh well, fuck ’em. I’ve encountered so many problems with this RDS server project it is unreal and this was just icing on the proverbial cake. Continue reading “Batch Script – Ribbon UI Customization: Take Ownership and Change Permissions of the CommandStore Subkeys in the Registry”
Boy do I sure feel like a dumbass sometimes. I researched and wrestled with this damn issue for a week or more only to find out that I had come across the answer to this problem about a dozen times but was looking in the wrong freaking spot. For whatever reason, when people were referring to disabling the mouse pointer shadow, I immediately thought of the place in windows System Properties > Advanced Tab > Performance > Settings > Visual Effects Tab > “Show shadows under mouse pointer” but that wasn’t fixing my problem and now I know why. Here’s the whole story.
I’ve got a mix of around 100 Neoware CA19, CA21, and HP T5145 thin clients, all with 128MB of flash running HP ThinPro build T3X31012 and rdesktop version 1.6.0 that I’ve been testing with on Server 2012 and this was a major problem. I was just about finished locking down this 7 server RDS deployment I’ve been working on and when I had my first few users start to log in to test everything, they had no mouse cursor, fucking awesome!
At first, I thought this may have been a VMware tools problem, so I had reinstalled it and had scoured all the forums there, trying various different little tweaks, registry keys, and what have you, but that was only the beginning. Then I tried adjusting the various RDP settings on the thin client with no luck. I tried all the different things on the various Windows forums and still no luck. I got to know all the ins and outs of HP’s thin client architecture, their use of the Manticore registry, config files and everything that goes along with it and how it all works.
Continue reading “Server 2012 – RDesktop: Fix Disappearing Mouse Cursor with Group Policy”
Trying to get UltraVNC (version 220.127.116.11) to run as a system service is a pain in the ass if you don’t follow a specific set of steps during the setup process. It appears that if you check the box to install it as a service during the initial installation wizard, you will encounter the annoying “Password Not Set” error and nothing works. I also had issues with running the MSI installer rather than the EXE, so stick with the executable if you’re in a rush. I don’t have time at the moment to write up a giant all-encompassing post with accompanying pictures and what have you so here’s what you gotta’ to do:
Continue reading “UltraVNC – Password Not Set: How to Install as a System Service”