Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client > Windows XP IT Pro Forums > Windows XP Service Pack 3 (SP3) > Console session and Remote Desktop issue

Answered Console session and Remote Desktop issue

    •  
      Thursday, May 01, 2008 4:36 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      After installing SP3 I can no longer connect to the Console session when using the Remote Desktop mmc.  It now creates and new RDP session which doesn't allow me to connect to the active Retrospect session.  It's still using the same Remote Desktop mmc version 5.2.3790.1830 and the other IT computer that doesn't have SP3 connects properly.  Does anybody have an idea what changed in SP3 that could cause these new sessions?
       

    Answers

    • Wednesday, May 07, 2008 4:55 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Thats the latest RTM version

       

      Please note that /console switch has been retired and replaced with /admin switch for connecting to the console session (via RDP).

       

      Thanks

      Shashank

       

       

    All Replies

    • Friday, May 02, 2008 2:01 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      They have changed the command line option from /console to /admin - I'm guessing this is why the Remote Desktops in the Admin Pack no longer connects to the console session.

       

      I posted a similar query on the forums yesterday, but I haven't had a response as yet.....

       

       

       

       
    • Tuesday, May 06, 2008 9:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I'm also seeing this issue after installing SP 3.

       

      MMC 3.0

      Remote Desktops Version: 5.2.3790.3959

       

      I called in to the fee based tech. support line and they were only interested in addressing this apparant bug if I was willing to pay for the call.

       
    • Tuesday, May 06, 2008 10:39 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Greetings Ys,

        First of which version of the sp 3 did you download? My guess is v3264, v3311 or perhaps ended up with the last refresh candidate. To check click on start run enter tge letters "winver" Any version prior to v5512 Will show which version it has installed. Even when RTM was avail v5593 was still being downloaded bu update. At least I am not sure which date they cut that one off was.

       

        Any version after v5512 RTM should just show Sp3 installed.

        Hopefully you have a restore disk. Just running it over your Sp3 installation may be the easy methoid.

      . Not a create new installation just instllaing it over your old Sp3 release candidate. Or as an alternative attempting a restore point if you had it enabled.

       

        Good news, bad news. Lets start with the bad

        The earlier versions included a date after RDConsole an date after stop runnning this program. The bad news is these versions are not supported except for help uninstalling. The reason is Microsofts Sp3 team has moved on in the code base, and the fixes in later versions have improvements

       *For example HD audio many people complained this needed to be in the Sp3.

        Whats not included SATA drivers.*

       

        If the uninstaller is not available from add/remove programs.

        You are going to have to run the program from the hidden folder.

         Start by clearing hide system files and folders.

         Two boxes next needs to be cleared. *hide system folders and files*

       

       Navigate to the c:\%windir%\ntsvcpackuninstal$ A folder in there should be an uninstaller.

       

        More bad news. Some versions have a problem with re-installing the defrag program. And leave a System MMc version that is higher then the sp2 on. And some consoles. *Only Defrags * will not work properly. If you are using a restore point then great

       

        The great news Microsoft has the RTW is availble now. No more experation dates! And update will recognized any Sp2 as an update target for Sp3 now

       

       
    • Wednesday, May 07, 2008 1:45 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      1stknight,

      I downloaded the version that has the file name WindowsXP-KB936929-SP3-x86-ENU.exe.  Winver says Build 2600.xpsp.080413-2111 : Service Pack 3.
       
    • Wednesday, May 07, 2008 4:55 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Thats the latest RTM version

       

      Please note that /console switch has been retired and replaced with /admin switch for connecting to the console session (via RDP).

       

      Thanks

      Shashank

       

       
    • Wednesday, May 07, 2008 6:09 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
       Shashank Bansal [MSFT] wrote:

      Please note that /console switch has been retired and replaced with /admin switch for connecting to the console session (via RDP).

       

      Thanks

      Shashank

       



      Yes, which is why I suspect the "Connect to console" option in tsmmc.msc is now broken.  Can you confirm?

      Thanks,
      Dave
       
    • Wednesday, May 07, 2008 6:17 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Just to chime in...  I am having the exact same issue.

       
    • Wednesday, May 07, 2008 6:27 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      One more thing....  Instead of backing out SP3, I backed up and replace the following files with old versions from an SP2 machine and my problem is fixed.  I know I don't have any new functionality that was added but at least I can manage my servers properly again...

       

      mstsc.exe

      mstscax.dll

      mstsmhst.dll

      mstsmmc.dll

       

      All files are in the system32 folder.  I'm not sure which one fixed it, I replaced the exe first and that did not fix it so I continued and ended up replacing those 4 and it works.

       
    • Friday, May 09, 2008 12:04 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      currently trying this gpo setting - user configuration / administrative templates / windows components / terminal components / terminal server / connnections / allow reconnection from original client only = Disabled

      we have this problem

      note that if its not configured that it states that it can be set via machine level therefore it is possible sp3 sets this to enabled by default???

      see how you get on

       

       
    • Monday, May 12, 2008 11:50 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      note that the gpo settings worked for us
       
    • Thursday, May 15, 2008 8:51 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      hmm this seem to work for a day but now is broken again. Anyone else been sucessful?

       

       
    • Tuesday, May 20, 2008 5:42 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       PhiREflY, how did you do this?

       

      i found the previous mstsc.exe and mstscax.dll, versions 6.0.6000, (modified date november of 2006) in the $NTUninstall directory for sp3, as well as in the system32 directory of an xp sp2 machine. if i copy and paste these into my sp3 machine's system32 directory, it overwrites the new sp3 files, version 6.0.6001, (modified 4-14-2008). just like you would expect. i can see the 11-2006 modified date and the 6.0.6000 file version.

       

       

       

      except about 5 seconds later the files magically flip back to version 6.0.6001 with a modified date of 4-14-2008.needless to say the console checkbox in Remote Desktops does not work with version 6.0.6001.

       

       
    • Tuesday, May 20, 2008 5:55 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      I didn't do anyhting special, I just renamed the files and quickly copied over the new files.  I did them 1 at a time starting with the exe.  I just double checked (I use it all day everyday) and the old and new files are still out there as I left them.  The new ones I added .old to and the old ones have the proper names.
       
    • Tuesday, May 20, 2008 7:09 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      doesn't windows use a system file checker? i just renamed mstsc.exe to mstsc.exe.old and 5 seconds later windows put a new copy of mstsc.exe version 6.0.6001 into the folder.

       

       
    • Monday, July 07, 2008 3:32 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      On Xp SP3 the way I got around the windows File checking code is to rename the older version of mstscax.dll to mstscax2.dll copy it to my windows system32 directory and then run regserver mstscax2.dll.  This actually just replaces all the COM registration to point to mstscax2.dll which is the older version, while windows file cheking still has the origninal mstscax.dll un touched.  If you ever get an update that changes mstsxax.dll you will need to re-register.

       

      This is currently not working on Vista for me, so I may have to hand modify the registry.

       

      John

       
    • Thursday, September 25, 2008 12:41 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      And likewise, we are also now broken. Why on earth would MS do this??? and where is their response/fix for this?!

      Unbelievable.

       
    • Thursday, September 25, 2008 1:09 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Tunatoons, could you describe what your problem is, please?  It is not clear what issue on this old thread you are referring to.  The version of Remote Desktop delivered with the final public release of SP3 works fine for me.  If you are using a beta or pre-release version of SP3 you might be having problems.

       

       
    • Friday, September 26, 2008 7:15 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      The issue is with the Remote DesktopS application.  Not remote desktop, the remote client bundled with Windows XP/Vista, but with Remote DesktopS (note the extra S at the end), which is included in the Windows Server 2003 Administration Tools package, which can be installed on XP and Vista.  It's not MSTSC.EXE, it's TSMMC.MSC.

       

      Remote Desktops allows you to program in a list of servers, your user name, password, and domain to log into.  I administer a number of servers, some of which are across the office, some are across town, and some are hundreds of miles away.

       

      Part of what I need to do is check on/reset a program which only runs in the console window. Up until I installed SP3 on my machine, I could connect to the console using remote desktops by selecting "Server XYZ (Console)" from my list.

       

      Now I can't do this.

       

      I'm not using any beta or pre-release SP3.

       

       

       
    • Saturday, September 27, 2008 4:05 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      WayneMc, thanks for the clear statement of the issue. A Google search found an instance where a user suggested replacing mstsmmc.dll (version 5.2.3790.3959) with the version from a Vista v86 installation (version 6.0.6001.18000).  I do not have the necessary kit to test that suggestion.  There might be an issue with registering the DLL.

       

      Alternatively, if tsmmc does its magic by maintaining lots of .rdp files behind the scenes (I don't actually know), all you need do is find the .rdp files that contain:

       

      connect to console:i:1

       

      and add the line:

       

      administrative session:i:1

       

      Then the .rdp files will work with either version of the TS client.

       
    • Tuesday, October 21, 2008 10:28 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      We wonna mstsc -console in XP SP3? Just do it...

       

      1. Find this old files ( i take them from 2003 sp2):

      - mstsmhst.dll ( 5.2.3790.3959)

      - mstsmmc.dll ( 5.2.3790.3959)

      - mstsc.exe ( 6.0.6000.16459)

      - mstscax.dll ( 6.0.6000.16459)

      - mstsc.exe.mui ( 6.0.6000.16459)

      - mstscax.dll.mui ( 6.0.6001.18000) - hmmm... its mb mistake in version, but still work.

       

      2. Rename c:\WINDOWS\system32\dllcache\lhmstscx.dll to any name

      Rename and copy mstscax.dll to c:\WINDOWS\system32\dllcache\lhmstscx.dll

      regsvr32 lhmstscx.dll

      Dont forget refuse from windows file protect

       

      3. Rename c:\WINDOWS\system32\mstscax.dll to any name

       

      4. Copy this files to c:\WINDOWS\system32\

      - mstsmhst.dll ( 5.2.3790.3959)

      - mstsmmc.dll ( 5.2.3790.3959)

      - mstsc.exe ( 6.0.6000.16459)

      - mstscax.dll ( 6.0.6000.16459)

      and use regsvr32 to mstscax.dll

       

      5. In c:\WINDOWS\system32\ru-ru\ or en-en rename this files to any

      mstsc.exe.mui

      mstscax.dll.mui

      and copy files with old version

       

      May be i forget something, but i think, whats primary is replace dll in dllchache and other folder... and i`am belive you know how to do it. Smile

       
    • Tuesday, April 14, 2009 7:21 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Here is what I did to fix the issue:

      1. Rename mstsc.exe and mstscax.dll under C:\WINDOWS\system32

      2. Copy the older version of the above two files from C:\WINDOWS\$NtServicePackUninstall$ to C:\WINDOWS\system32

      3. Regsvr32 mstscax.dll from command prompt under C:\WINDOWS\system32

      I think these two files mstsmhst.dll and mstsmmc.dll were not replaced by SP3 since they showing version 5.2.x as compare to 6.x.x for the other two files. I did not unregister any DLL prior to copying files nor I did replace any files under 'dllcache'.
       
    • Monday, January 24, 2011 8:31 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I use Proxy Networks (http://proxynetworks.com ) for my remote access and have not had any issues connecting, pre- or post- service pack. I like Windows as an operating system, but I am definitely not a fan of its remote connection features.