Is Microsoft Screwing Up Distribution of Remote Desktop Client v6.1?
I'm in the process now of tech editing my book on Server 2008, updating it to fit with RC1 and eventually RTM code. In working on the chapter on Terminal Services tonight, I discovered that TS Web Access no longer works with the Remote Desktop Client v6.0.
Instead, once you upgrade to RC1, any attempt to connect to a RemoteApp through a TS Web Access web site gives you an error "ActiveX control not installed". You're then directed to a Terminal Services Team Blog web site that is supposed to have more information about what happened. Instead, the web site provides you information on ... how to redirect the error message not to that web site.
What gives? Following on in the commentary of the blog post, it seems that RDC v6.1 is required in order to use TS Web Access at RC1 and greater. But Microsoft at present will only release the RDC v6.1 code as part of a Vista SP1 or an XP SP3 installation. No independent install is provided.
I've said it before that TS Web Access is one the greatest features of Terminal Services in Server 2008 -- and arguably one of the best new features of Server 2008 itself. But, if Microsoft lacks the ability to get us an independent installation of the client code we need, this fantastic feature will go the way of Microsoft Bob.
Are you experiencing similar problems with your Server 2008 testing? I'd be curious to hear your problems (and any solutions).

Email This!
Digg it!
Del.icio.us
Reddit!
Newsvine
Comments
Could you not download the Vista SP1 RC and use the 6.1 client from within that?
URL:
http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx
Cheers
Neil
www.spellings.net
Posted by: Neil Spellings | February 1, 2008 2:51 AM
We too are trying to prove Windows 2008 TS Web Access as the way forward for our remote users. However, we cannot demonstrate the functionality without having RDC 6.1!!!! Microsoft, if you are listening, please could you distribute this as a standalone app, as with previous versions!!!
Posted by: Mark Barter | March 26, 2008 7:58 AM
If you dig around on the Internet, you may find where one enterprising person has reverse engineered the v6.1 install out of the XP SP3 &/or Vista SP1 upgrade. I know I was doing some research of my own to try to figure out the same thing, and found something of the sort on the Internet. But, now I can't seem to find it again. I know its out there...
Posted by: Greg Shields | March 26, 2008 10:01 AM
I too find this absolutely ridiculous. I tested the Server 2008 RC and ran into that problem. I was thrilled I would be able to get rid of our old Citrix. I incorrectly assumed that it would be corrected when it went RTM.
I wouldn't be so irritated, but since Vista SP1 isn't widely available, and XP SP3 isn't even out yet, I'm very frustrated.
Is there any reason it can't be released separately? Personally, I see this slowing down adoption of RemoteApps.
Posted by: Ben Lambert | April 12, 2008 10:27 AM
AFAIK, no. This is just the way they've decided to release the update. MSTSC v6 had its own separate update, so I'm not sure why this one only arrives bundled...
Posted by: Greg Shields | April 12, 2008 12:12 PM
This is a puzzling scenario. My current working theory on 'Why?' is that it is related to NAP and its subcomponents. This is important as CAP/RAP's can require the health check. Then once XP SP3 gets released then the development team will swiftly pivot and release all the necessary individual parts so we can retrofit Windows 2003 servers with RDC 6.1 as well. Unfortunately the only official date for XP SP3 is sometime in Q2 which could still be awhile.
What's funny is that the launch slides are still saying RDC 6.0 and are available for download. A few weeks back in Columbus I had to bring this up to the presenter as he wasn't even aware of the change. The overall feel of this hasty launch is one of over-stretched development.
The features of Server 2008 are terrific, unfortunately, this RDC pain is diminishing adoption attempts for my clients. I can deal with known delayed timelines but I'd at least like an official release date estimate and the information that it will be available to Server 2003. The lack of information is frustrating.
Posted by: Dale Unroe | April 12, 2008 1:12 PM
I would tend to agree. The TS Web Access / TS Gateway combo does have a NAP integration, but its not a required component. So, its arguable that the bits could be "ripped out" into their own installer with the caveat that "NAP ain't in there".
This point is the same that others have made about their hesitation to move to Vista considering the unnecessarily excessive delay in getting the RSAT bits released. They never should have been a year late, and Microsoft is paying the price.
Thanks for the comment.
Posted by: Greg Shields | April 12, 2008 4:48 PM
I found this on another web site and it works for english windows xp:
http://memphistech.net/articles/webapp.htm
Posted by: Patrick | April 18, 2008 12:34 PM
This rocks! Thanks for the update. I just created a post to this end so others can find this great web site!
Posted by: Greg Shields | April 18, 2008 1:08 PM
A little update. That memphistech thing didn't quite work for my Windows Server 2003. The server would constantly revert back to the original RDP 6.0. I had to adjust the contents of the batch file that is apart of the download from the memphistech site. YMMV. And it may need to be adjusted on a per computer basis, but the following got the job done for me.
REM --- Start of Update.bat (originally copy.bat from memphistech)
del c:\windows\$ntservicepackuninstall$\mstsc.exe
del c:\windows\$ntuninstallkb925876$\mstsc.exe
del c:\windows\servicepackfiles\i386\mstsc.exe
del c:\windows\system32\mstsc.exe
del c:\windows\system32\dllcache\mstsc.exe
del c:\windows\lastgood\system32\mstsc.exe
del c:\windows\$ntservicepackuninstall$\mstscax.dll
del c:\windows\$ntuninstallkb925876$\mstscax.dll
del c:\windows\servicepackfiles\i386\mstscax.dll
del c:\windows\system32\mstscax.dll
del c:\windows\system32\dllcache\mstscax.dll
del c:\windows\lastgood\system32\mstscax.dll
copy mstsc.exe c:\windows\$ntservicepackuninstall$\mstsc.exe
copy mstsc.exe c:\windows\$ntuninstallkb925876$\mstsc.exe
copy mstsc.exe c:\windows\servicepackfiles\i386\mstsc.exe
copy mstsc.exe c:\windows\system32\mstsc.exe
copy mstsc.exe c:\windows\system32\dllcache\mstsc.exe
copy mstsc.exe c:\windows\lastgood\system32\mstsc.exe
copy mstscax.dll c:\windows\$ntservicepackuninstall$\mstscax.dll
copy mstscax.dll c:\windows\$ntuninstallkb925876$\mstscax.dll
copy mstscax.dll c:\windows\servicepackfiles\i386\mstscax.dll
copy mstscax.dll c:\windows\system32\mstscax.dll
copy mstscax.dll c:\windows\system32\dllcache\mstscax.dll
copy mstscax.dll c:\windows\lastgood\system32\mstscax.dll
xcopy *.* c:\windows\system32 /e /y
regsvr32 %systemroot%\system32\mstscax.dll /s
REM --- EOF
Good luck everyone.
Posted by: Richard Gard | May 28, 2008 8:59 PM
This is great! Thank you!
Posted by: Greg Shields | May 28, 2008 11:40 PM