Discussion on:

Connect securely to Windows Vista Remote Desktop

How well does this technique work for the Remote Desktop demands of your environment? Does it overcome security concerns that have been an obstacle for you in the past?

This article is very good for use on my SBS2003 machine, but what about the XP machines ? will this enhanced security be migrated to XP Pro? Have our friends in Redmond given any hints?

I have users who work from home in the evening. I have a obscure port number routed to each of their workstations through the firewall. If I could put this security on their workstation and then setup their home computer for the security settings that would be awesome.

You can't use this on XP on the host/server side, but you can use XP on the client side as shown in article.

Microsoft will not be adding more features to XP other than security updates. They need to be able to make a case for moving to Vista.

You have to also remember that Vista is just Windows 2003 codebase with all the GUI *rap added. That is one reaons this is accessable on VISTA, it was already on Windows 2003 Server Code.

Redmond could not get a brand new code base out the door for Vista

I don't get the Certificate screen on my client but it connects anyway.

Is there a way to force manuall certificate installation on the client prior to the connection (My host is a vista machine also) ?

Or

I have the same error: I don't get the Certificate screen on my client but it connects anyway. Does anybody have any solution?

Thank you in advance

As to clients, can I run remote desktop client on Home Basic? Does it ship with it? If yes and no, can I copy mstsc.exe from my XP Pro machine and run it on Vista Basic? (Same questiona re: Vista Home Premium.) My host is Windows 2003 Server Enterprise/SP2. It works now with Windows 2000 Pro and XP Pro clients.

Have they made this any easier? There are few documents to assist in helping with remote printing off a RDT connection

you just check off a few check marks and it should work.

It is just as easy as stated; a couple of check boxes when you connect. I use it regularly and it doesn't get any easier!

..If only they could figure out a way to retrieve those papers printed over the internet! (but I guess thats why there is also options to make local drives / clipboard / printers / plug & play deveices / etc available in your RDP session)

I just returned from the TS2 session in Las Vegas on server 2008. It appears they have made printing as easy as using Simplified Printing. For all of you stating it is as easy as placing a check in the Printer" checkbox in resources, I have not found that to be true at all. I still use Tricerats Simplified Printing and cannot wait for the release of svr 2oo8. It also provides the ability to RDP the application instead of the whole desktop. This is great for certain applications but I will need to test it with aps that aren't designed to work with Remote Desktop"

A very important note about enabling FIPS compliance here: Doing so will cause some https websites to not function in IE. The reason is that the server that the website resides on might not support FIPS. IIS based servers will, but some others that use SSL 3.0 might not... For instance, my vonage account won't load in IE, nor will my cable companies online billing. They don't use FIPS compliant algorithms.

Article was useful
BUT
I found out the hard way that when you enable FIPS, the Microsoft Windows Home Server will stop backing up the computer.
Have not heard from MS if/when they will support FIPS for the just released WHS, but you might make a note of this.

Article was useful
BUT
I found out the hard way that when you enable FIPS, the Microsoft Windows Home Server will stop backing up the computer.
Have not heard from MS if/when they will support FIPS for the just released WHS, but you might make a note of this.

Can someone please explain how to connect win2k3 sp2 server using RDP 6.0 along with smartcard certification authentication from a WinXP client? Assuming I already have install RDP 6.0 client on my winxp system and Enterprise root CA is installed on the same W2k3 server to which i'm making a rdp connection.

Thanx in advance
SC

After setting all the settings shown here, I did a GPUPDATE /target:computer and then restarted my PC for good messure but when I run RSOP.MSC it still shows the "System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing policy" still shows as disabled, any one else having the same problem?

Has this been updated for Win7?

Hi George,

I had followed these steps to successfully configure RDP. As you noted, the certificate expires every six months. The issue I am having while renewing it is that in Figure Y, I do not see "Local Computer" at all. I have tried both normal-user and administrator accounts for both machines. Please help!

Thanks,

Alok