Is it possible to manually install RDP client 6.1 for platforms that aren’t directly supported?

Posted on

Is it possible to manually install RDP client 6.1 for platforms that aren’t directly supported? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, rdp, , , .

I have some clients that need RDP client 6.1 in order to utilize the new easy print driver.
However, the installer doesn’t allow it to install on several platforms such as Windows Home Server or Windows Server 2003 because they are not XP. The version check prevents it going further. I’m reasonably confident that it should actually run however and want to try it.

Has anyone done this before? what I should really ask is… what files should I manually copy (backing up originals first)… just the exe or are there lots of dependant dll’s that need upgrading too?

Or… is there an inexpensive or free alternative to something like tricerat’s screwdrivers?
I did look into screwdrivers but felt that it was well overpriced.

Solution :

Yep this is do-able. You just need to change the compatability mode for the installer to ‘Windows XP’. No guarantee that you’re not digging yourself into a hole with this, though, as future patches to your 2003 server are going to be layering on top of an unsupported state.

If you’re having issues connecting from 2003 to newer RDP servers, there are settings you can alter on the newer RDP hosts that will allow them to accept older clients that run lower levels of channel security. This would be the supported solution, if that’s your issue.

Is the installer an MSI? If so, you can remove the version checking by using the Orca tool. I’ve used it to strip the prerequisite for some applications that wouldn’t recognise that DirectX 10 is, in fact, newer than DirectX 3.

As far as alternatives go, we use ThinPrint (or .Print as it’s also known). It’s around the same price as screwdrivers though, if I remember correctly.

I’m pretty sure I did this by just copying the files that would have been installed. As a test you can copy them to a dir like c:temp.

Leave a Reply

Your email address will not be published.