Remote Desktop Services (Terminal Services) Team Blog

PingBack from http://smokingun.wordpress.com/2008/06/26/rdc-61-client-for-windows-xp-sp2/

PingBack from http://www.ipmer.com/2008/06/rdp-client-61-for-xp-sp2.html

Hi. I downloaded this because the previous 6.0 RDP client stopped saving credentials within the RDP files themselves. As a result, automatic logins to different servers on different ports within the same domain using different credentials are broken because MSTSC uses the last cached credentials. I don't want to have to reconfig hosts files to fake domains just to enable auto login. Is it possible with this release to set up separate user/pass combinations for autologin to different hosts/ports within the same domain?

Hi, My XP is now SP3, but the RDC crashes when it is trying to connect. It worked fine a couple weeks ago (with SP3). I've tried connecting to 2 different computers. In the error signature it says AppName:mstsc.exe AppVer:6.0.6001.18000 ModName:mstscax.dll

Stuck on what I can do to fix it, any help is appreciated. If I need to get help elsewhere, please suggest. Thanks.

Looks like Microsoft listened. The RDC v6.1 is required for clients to work with TS Web Access. Originally, Microsoft only made this update available through the XP SP3 upgrade. But enough people balked that they announced a standalone download back on

I opened a support case with Microsoft today re: Windows XP x64 and Windows 2003 x64 clients with no futher information.  However, I did get a chance to waste an hour and thirty minutes of my time waiting on the phone.

Thanks for this, as it will make my TS2008 deploy go even smoother than it has been already.  One question though:  Using this update to XPSP2 clients, is .NET Framework 3.0 SP1 still required for Easy Print?

Previously, it was my understanding that XPSP3 and .NET Framework 3.0 SP1 were required.

Dan:

> One question though:  Using this

> update to XPSP2 clients, is .NET

> Framework 3.0 SP1 still required

> for Easy Print?

I believe you need the version of .NET included with XP SP3 or Vista SP1 (can't remember what version that is)

> Previously, it was my

> understanding that XPSP3 and .NET

> Framework 3.0 SP1 were required.

As long as you have the right version of .NET, EasyPrint will work with the XP SP2 (two) package.

Would someone from MSFT care to comment on the request for RDC 6.1 on Windows Server 2003, please?

/Jan Jensen

Really, really need 2003 version - any news at all?

Does Microsoft support MS Server 2003?

PNRP 2.1 for MSServer 2003 - missing

RDP 6.1 for MSServer 2003 - missing

Is there any way to always trust a computer you are connecting to, instead of have the "Do you trust the computer you are connecting to" dialog popup everytime.  It is very annoying to users that are using the ActiveX control to connect to one server frequently.

Your second option would be perfect if that checkbox existed.

Server - 2003

Client - XP or Vista (in general)

http://www.flickr.com/photos/29452822@N03/2753709169/

I could not email the UI so I posted it online.  This is the dialog I receive in Vista.  It is very similar to the ones I receive in other OS

THE NEED for RDC6.1 on Windows 2003.

I need the RDC 6.1 for Windows 2003 because I can't publish Windows 2008 Terminal Server Applications through my IAG server unless the 6.1 client is installed.

I need 6.1 for server 2003 because of ts easy print feature!

I need the rdp 6.1 client in order to use easy print when connecting from server 2003 to server 2003

To termserv:

"Please add a brief description of the usage scenario for you/your business for these features."

Excuse me? Why do I have to explain anything??

According to http://support.microsoft.com/lifecycle/?p1=3198 , Windows 2003 *should* be supported to at least 2010. I have paid for Windows 2003 and I want to get the promised support. I think that class-action suit is needed.

The reason MSFT asked why this was needed is because 2003 is not a client operating system, and any development work needs some justification. For future reference the way to respond to a question like this and actually get what you want is to state the "business" case for adding support for this feature, not "so I can use this feature on Server 2003".  Games are not installed on 2003 and I don't hear an uproar about that.

Explain to Microsoft what business value this has instead of complaining and you have a "chance" to get what you want. An example would be "we use Server 2003 as the Client OS for a group of 50 developers that create software X.  While they run their development tools locally, these employees run their line of business applications via 2008 Terminal Server RemoteApp, and they need to be able to print to their local prin devices without installing the drivers on the Terminal Server, because their printer's driver is known to be unstable on TS, or because it is the company's policy to not install 3rd party printer drivers on TS."

Saying "because I want" is not sufficient, even if you are a paying customer.  It's not too much to ask that you explain what value this adds for you business.

Patrick Rouse

Microsoft MVP - Terminal Server

http://blogs.inside.quest.com/provision

Someone has already posted a way to install version 6.1 of mstsc.exe on 2003, so what is the issue?  Mine would be the need for a supported configuration.

As for your threat of a law suit, I think you're completely out of line, and acting in an unprofessional manner.  If you formulated a proper argument and presented it in a tactful manner you would have already received a response from MSFT. instead i've see a bunch of techies complaining "I want, I want, I want..." without ever articulating  the reason for the request.

I agree that this client should be available for 2003, but I have no need for it. I am not going to ask MSFT to spend dev time that they could be applying elsewhere when no one has properly articulated why their business requires this functionality.

If anyone wants to spend the time, I'd be happy to relay their requirement directly to the  MSFT Terminal Services Team.  I can be contacted at Myfirstname.Mylastname@quest.com.

Patrick Rouse

Microsoft MVP - Terminal Server

http://blogs.inside.quest.com/provision

What about running on WinFLP?  Doesn't seem to work... WinFLP supports multiple end-users, and the added benefits of 6.1 would be most excellent.  Is this anticipated?

We have several dozen HP thin clients offsite, both at users' homes and at teleworking locations.  The thin clients are HP T5530's running Windows CE 6.  Unfortunately our rollout of Windows Server 2008 Terminal Services is severely hampered by the lack of Terminal Server Gateway support in the Remote Desktop client available on Windows CE 6.0 - we need the Terminal Server Gateway role is load-balancing.

Is there a RDP client available for Windows CE 6.0 that supports the Terminal Sever Gateway role?

If not are there any plans to release one?  If so is there an ETA?  Is there a workaround/hotfix that I can try?

Slightly O/T:  Assuming that there is no client and there are no plans to make one is it possible to upgrade the HP T5530 from Windows CE 6.0 to Windows XPe?  I know that this is slightly outside the remit of Terminal Services but I would assume that the terminal services team has experience with thin clients so I thought I'd ask...

We can just about afford to buy higher-capacity flash cards and RAM to get Windows XPe running but replacing all out T5530's, some of which were bought just a couple of months ago, makes Windows Server 2008 terminal services financially untennable no matter how much I like it!  :)

Many thanks,

1) Whether you need the latest RDC client (RDC6.1) on Windows Server 2003 because you have end users using Windows Server 2003 as a client OS?

---

We have this situation, many of our developers  use server 2003 as clients; some need access to tsrweb site.  MS seriously you updated 2003 for 6.0, and skip it for 6.1, while pumping it out on XP-sp2 and sp3? Why in gods name would you not bother with 2003.  It's sort of sad we even have to ask, and yes both x32 and x64 is needed.

Hi

How about TS Web Access support for windows CE. We have HP thin client 5530 and would like to run ts web access against 2008 terminal server

Is there a way to package and distribute the 6.1 ActiveX in .CAB file so that users of our site have access to the new features without the need to install the whole app?

Hello

We would need RDP 6.1 for Win2003 to make a Connection from a Win2003 / Citrix Environment to Win2008/RDP 6.1 Terminal Gateway Platform where our subcontract order processing Application is Hosted.

Doesn't work with RDP 6.0. Only with RDP 6.1 from a WinXP Client.

So, it would be really great for us if RDP 6.1 would be released for Win2003.

I have found an easy way to get around this for now.

Delete the mstscax.dll, mstsc.exe file for version 6.0 and replace them with the 5.0 files.

They are stored in windows/system32 folder.

Fixed my problems instantly.

We bought new boxes for Windows and use old Windows 2003 boxes as workstations and to administer the new boxes. We would like to use NLA but we need RDC 6.1

Same as everybody else around here...  I need to get RDP'd to 08 from 03 and I think its a croc of crap that M$ hasn't released this when so many of us NEED it.  Not just some bunch of techies saying I want; No, we're saying rather clearly that we need it and now we're being ignored.  This is B$ M$.

It's pretty simple to setup. You need to first install a printer to your local machine. Then set that machine up to share that printer. Then on the remote machine find the shared printer and add it to the remote machines printer list. This is how I do it for my <a=href"http://techbranch.com">computers and networks repair company, TechBranch of Tampa</a>.

We would like 6.1 for 2003 purely for the performance increase.  I have anywhere from 40-60 users connecting to 2 W2k3 Terminal servers and from my remote users I am getting some extreme issues when scrolling graphics and other issues, even with things set to the lowest settings in the RDP client on the client computers.

That's all well and good, but being a non-profit that has moved to Terminal Services for costs savings and such, I don't have any budget to buy any new products, so your advertisement doesn't work for me.

I'm trying to use easy print with a RDP connection. But my 2008 Server (Web edition) always use printer's drivers and not easy print driver. My computer configuration is ok because if I connect the same computer to another 2008 Server, Easy print is use. Why ? I must install something more on my server ?

So why not just copy the MSTSC.exe and MSTSCAX.DLL from a windows xp box that is running 6.1 and overwrite the files on the 2003 server?  I don't know if causes and issue, but it looks like it worked OK when I did it.

Hi, CredSSP (which is required for NLA) is not available on Win 2003. For information on how to enable it on XP SP3 please see: http://support.microsoft.com/kb/951608

Thanks,

~Olga

sorry, but unfortunately there is no unofficial way to do this either on WS03 or XP x64 since CredSSP is not at all available on those OS's.

After install KB952155 and connect to a remote windows 2003, I could see garbled codes in windows task manager. The steps are as following:

1. Select all the available columns in menu View;

2. Drag the horizontal scroll bar to the right most;

3. Drag scroll bar back to the left most.

Then you could see unreadable codes in column Image Name.

And I met the same problem in my own application, the column header's text was unreadable. The problem happened only when remotely connect from XP to 2003 by using RDC 6.1.

How can I fix this problem? Thanks.

We need 6.1 on 2003 so we can connect to 2008 servers in Admin mode from the 2003 boxes.  Our 80+ users are required to RDP to the 2003 boxes and then RDP from there to client sites - this is done to prevent them from seeing clients' passwords (app running on 2003 box reads and supplies passwords).

I tried copying the files from an XP client to the 2003 server, only to have Windows File Protection immediately overwrite the files with older ones.  Then, I booted in Safe Mode and replaced the ones in dllcache as well.  No luck, it didn't work at all - the client wouldn't even start.

Where is link to a way to make this work?

Is it possible to set incoming RDP sessions to a Windows XP Pro SP3 system with CredSSP enabled to require NLA?

Quote from: Wednesday, December 10, 2008 7:45 PM by Patrick Rouse:  "Microsoft is not going to add the RDP 6.1 protocol stack to version 5 operating systems, i.e. XP and 2003, so you can either run 2008 Terminal Services and XP SP2+ clients with RDP 6.1 clients, or use an add-on product from companies like Quest or Citrix.

"RDP 6.1 provides a 40% decrease in bandwidth over 6.0 and 5.x, and Quest's EOP provides a 500% to 100% decrease in bandwidth consumption, which is designed specifically for WAN/Internet connected users."

---

I studied pretty much this whole post and there are very valid "business cases" where support for RDP 6.1 in WS2003 is needed.  The Microsoft guy, above, says that we can get a 40% decrease in bandwidth just by using the newer version.  And there are several paying customers who are asking for this to be made to work.  

Customer's request... "Please make RDP6.1 work in Windows Server 2003, for many obvious reasons."

Microsoft's response... "No."

My response... my company is anxiously porting over from anything Microsoft to Open Source solutions, such as Linux where developers do heed the needs of their users, and due to the fact that Microsoft is apparently motivated only by making more money from people rather than supporting their products and enhancing those that they "produce".

We are getting our base of thousands of users accustomed to the Linux GUI so that when we port over to Linux they will be familiar with it, which is the ONLY barrier from us moving to 100% free software, including the OS.

I also notice that when questions are posted in Ubuntu forums, the techies always respond with a solution and never tell the customer that they have to buy software as the only solution.

Go open source.

You can apply the RDP 6.1 client for Windows XP on Windows 2003.  Download the 6.1 client, right click on the .exe file, properties, change the compatibility mode to XP, click OK, then run it.  -ken

I work for a large IT company. We are a Microsoft partner. For our hosted services division we've been using TS, Propalms TSE, and Citrix along with UniPrint for easy universal printing. Currently I am beginning a test to see if Windows 2008R2 can provide both the secure web published applications layer we get from citrix and proplams and also a truly univeral remote printing solutions. A few days ago I began by installing a new Windows 2008R2 server and almost immediately ran into a brick wall. The RDC6.1 that is supposed to be configured and working on my XP SP3 desktop does not so I get nowhere when trying to connect to the new server rdweb interface. So after that failure, I decided to try it from the 2K3 64 server which is the Virtual Center Server for our vmware development. Of course I get the same problem. Now of course I could upgrade my workstation to Windows 7 or try to fix RDC6.1 on my XP workstation or I could use an alternate system for administration but the fact that I am only a few hours into this proof of concept and I've already ran into what I feel should be a pretty simple solution, is leaving me with, once again, a real bad feeling about this new product. So I went looking for a solution and I found this forum. I've read through the entire forum. I noticed some of the early posts were from 2008?????? And this still has not been resolved? I thought the new 2008R2 Terminal services changes were put in place to try and regain some market share from citrix and propalm and uniprint and other third party vendors who historically provided products that either out performed microsoft offerings or had additonal required features that microsoft was too short sited to include. But as I am reading through these posts I'm finding microsoft personnel suggesting third party products to solve issues that should have been address by microsoft in the first place ????  ???? ?????? ???? I am absolutely dumb founded. How does this happen? So what do I do from here? Well, I'll have to finish my testing and if ( HUGE IF ) everything else works as advertised, I'll need to add a huge caveat that in order for this new platform to be viable for our over 2000 hosted clients, they'll all need to be running one of the particular OS version that microsoft decided would require RDC6.1 . Do you realize that I can install Propalms connection manager and/or citrix client and/or Uniprint on MORE VERSION OF WINDOWS THAN IS SUPPORTED BY RDC6.1 . Not to mention all the non-windows client support these other vendors offer. Way to go guys. You really put citrix in their place with this new release! Excellent work, as always.

@Corbett

Still doesn't cover x64 NT5.x OSes (XP x64, Server 2003 x64).