<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: MSTSC: Microsoft Terminal Services Client 6.0 Now Available for Download</title>
	<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/</link>
	<description>ls /usr/lolcat</description>
	<pubDate>Wed, 20 Aug 2008 02:11:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Andrés(Mosko)</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-543</link>
		<dc:creator>Andrés(Mosko)</dc:creator>
		<pubDate>Sat, 20 Oct 2007 16:29:31 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-543</guid>
		<description>Thanks a lot.....works fine on Vista......you r the best....
gracias por este software que necesitaba!!!!</description>
		<content:encoded><![CDATA[<p>Thanks a lot.....works fine on Vista......you r the best....<br />
gracias por este software que necesitaba!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DLL Files Guy</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-542</link>
		<dc:creator>DLL Files Guy</dc:creator>
		<pubDate>Fri, 27 Jul 2007 05:40:47 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-542</guid>
		<description>Thanks... this article is just what i been looking for.

Big thanks

NC Tech Support Team
-Brian Nailer</description>
		<content:encoded><![CDATA[<p>Thanks... this article is just what i been looking for.</p>
<p>Big thanks</p>
<p>NC Tech Support Team<br />
-Brian Nailer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Titus</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-541</link>
		<dc:creator>Titus</dc:creator>
		<pubDate>Wed, 20 Jun 2007 19:19:43 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-541</guid>
		<description>yes
it cutely works on command prompt
&#38;gt; mstsc
Give the machine ip address and login</description>
		<content:encoded><![CDATA[<p>yes<br />
it cutely works on command prompt<br />
&#38;gt; mstsc<br />
Give the machine ip address and login</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bitmap</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-540</link>
		<dc:creator>bitmap</dc:creator>
		<pubDate>Tue, 12 Jun 2007 04:35:30 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-540</guid>
		<description>RDP console:
Add a line to the .rdp file that says "connect to console:i:1" (no quotes)


Also for those that do not want WinXP SP2 mucking up their systems, but still want to use the new MSTSC client...

Installing MSTSC 6.0 (Remote Desktop) on Windows XP SP1

Since it is not officially supported, and the installer croaks under SP1,
I had to hack my way around it a bit, and discovered that the programmers
actually did code the program, and even their installer to work under SP1
maybe even with no SP, but the installer's package manager itself was doing
the check for SP2 before the actuall program installer gets run...

I PROVIDE NO WARRANTY THAT THIS WILL NOT BREAK YOUR ENTIRE SYSTEM, EAT ALL YOUR POTATO CHIPS, OR DRINK YOUR BEER.

1. make a backup copy of mstsc.exe and mstscax.dll from your windows\system32
put them somewhere safe (you can still run them separately after the 6.0 install)

2. delete mstsc.exe and mstscax.dll from your windows\system32 and windows\system32\dllcache.
both files must be deleted from both locations very quickly, or the Windows File Protection
will notice, and copy them back again.
You will get an warning window about unrecognized files, just click Cancel.

3. run the MSTSC6 installer for XP (downloaded from http://support.microsoft.com/kb/925876)
Watch closely to see where it is unpacking the files, usually the root
of some drive, with a really long directory name like 04d6787f2a5930bc357d631f3a.
When you get the error message about your SP level, DO NOT close the window!

4. Find the directory where it unpacked everything (EX: C:4d6787f2a5930bc357d631f3a)
If you can't find it, search all local drives for LHMSTSC.exe

5. Copy the directory SP2GDR to somewhere safe, like \temp.

6. Close the error message window. The really long-named directory will be deleted.

7. copy the single file from SP2GDR\ip to SP2GDR\

8. using Windows Explorer, from SP2GDR, right click on lhtsc.inf and select Install.

TA DA!</description>
		<content:encoded><![CDATA[<p>RDP console:<br />
Add a line to the .rdp file that says "connect to console:i:1" (no quotes)</p>
<p>Also for those that do not want WinXP SP2 mucking up their systems, but still want to use the new MSTSC client...</p>
<p>Installing MSTSC 6.0 (Remote Desktop) on Windows XP SP1</p>
<p>Since it is not officially supported, and the installer croaks under SP1,<br />
I had to hack my way around it a bit, and discovered that the programmers<br />
actually did code the program, and even their installer to work under SP1<br />
maybe even with no SP, but the installer's package manager itself was doing<br />
the check for SP2 before the actuall program installer gets run...</p>
<p>I PROVIDE NO WARRANTY THAT THIS WILL NOT BREAK YOUR ENTIRE SYSTEM, EAT ALL YOUR POTATO CHIPS, OR DRINK YOUR BEER.</p>
<p>1. make a backup copy of mstsc.exe and mstscax.dll from your windows\system32<br />
put them somewhere safe (you can still run them separately after the 6.0 install)</p>
<p>2. delete mstsc.exe and mstscax.dll from your windows\system32 and windows\system32\dllcache.<br />
both files must be deleted from both locations very quickly, or the Windows File Protection<br />
will notice, and copy them back again.<br />
You will get an warning window about unrecognized files, just click Cancel.</p>
<p>3. run the MSTSC6 installer for XP (downloaded from <a href="http://support.microsoft.com/kb/925876" rel="nofollow">http://support.microsoft.com/kb/925876</a>)<br />
Watch closely to see where it is unpacking the files, usually the root<br />
of some drive, with a really long directory name like 04d6787f2a5930bc357d631f3a.<br />
When you get the error message about your SP level, DO NOT close the window!</p>
<p>4. Find the directory where it unpacked everything (EX: C:4d6787f2a5930bc357d631f3a)<br />
If you can't find it, search all local drives for LHMSTSC.exe</p>
<p>5. Copy the directory SP2GDR to somewhere safe, like \temp.</p>
<p>6. Close the error message window. The really long-named directory will be deleted.</p>
<p>7. copy the single file from SP2GDR\ip to SP2GDR\</p>
<p>8. using Windows Explorer, from SP2GDR, right click on lhtsc.inf and select Install.</p>
<p>TA DA!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jafxi</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-539</link>
		<dc:creator>jafxi</dc:creator>
		<pubDate>Sun, 08 Apr 2007 17:04:07 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-539</guid>
		<description>If you create a *.bat file with the command "mstsc [RDP file name] /console" it works just as well as having a RDP file that connects directly to the console, but I don't think there is a way to specify a console connection in the RDP itself.</description>
		<content:encoded><![CDATA[<p>If you create a *.bat file with the command "mstsc [RDP file name] /console" it works just as well as having a RDP file that connects directly to the console, but I don't think there is a way to specify a console connection in the RDP itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clifford</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-538</link>
		<dc:creator>Clifford</dc:creator>
		<pubDate>Wed, 14 Mar 2007 15:41:39 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-538</guid>
		<description>I hail from the North, Sonoma I call home.  Grew up in Glen Ellen just as the area began the slow loss of its ruaral nature.</description>
		<content:encoded><![CDATA[<p>I hail from the North, Sonoma I call home.  Grew up in Glen Ellen just as the area began the slow loss of its ruaral nature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-537</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Mon, 12 Mar 2007 16:37:44 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-537</guid>
		<description>Oh sweet, I didn't know you could save it. I'll have to check that out.

Thanks for the welcome! I've lived here for over a year now and I'm really starting to love it. I'm assuming you're in the area as well. What part?</description>
		<content:encoded><![CDATA[<p>Oh sweet, I didn't know you could save it. I'll have to check that out.</p>
<p>Thanks for the welcome! I've lived here for over a year now and I'm really starting to love it. I'm assuming you're in the area as well. What part?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clifford</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-536</link>
		<dc:creator>Clifford</dc:creator>
		<pubDate>Sun, 11 Mar 2007 16:36:43 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-536</guid>
		<description>Hi Chrissy,
Yes, /console works on the command line.  But I've never gotten it to work inside an .rdp file.

I'll have to check out your cajun recipes website.

I don't know how long you've been in The City, but welcome to the Bay Area.</description>
		<content:encoded><![CDATA[<p>Hi Chrissy,<br />
Yes, /console works on the command line.  But I've never gotten it to work inside an .rdp file.</p>
<p>I'll have to check out your cajun recipes website.</p>
<p>I don't know how long you've been in The City, but welcome to the Bay Area.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-535</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Sun, 11 Mar 2007 01:18:27 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-535</guid>
		<description>Hey sage,
You can also do that with the XP/2003 MSTSC. Just use mstsc /console or mstsc -console

Cute favicon btw ;)

Chrissy</description>
		<content:encoded><![CDATA[<p>Hey sage,<br />
You can also do that with the XP/2003 MSTSC. Just use mstsc /console or mstsc -console</p>
<p>Cute favicon btw <img src='http://blog.netnerds.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /><br />
Chrissy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sage Computing</title>
		<link>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-534</link>
		<dc:creator>Sage Computing</dc:creator>
		<pubDate>Sat, 10 Mar 2007 23:44:54 +0000</pubDate>
		<guid>http://blog.netnerds.net/2006/12/rdp-microsoft-terminal-services-client-mstsc-60-now-available-for-download/#comment-534</guid>
		<description>Hey, I'm stoked that you picked up my favicon.ico from my website.</description>
		<content:encoded><![CDATA[<p>Hey, I'm stoked that you picked up my favicon.ico from my website.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
