Windows Server TechCenter > Windows Server Forums > Remote Desktop Services (Terminal Services) > TS Web Access not working - ActiveX not installed or enabled

Answered TS Web Access not working - ActiveX not installed or enabled

  • Saturday, January 12, 2008 4:45 PM
     
     

     

    I have set up a W2K8 RC1 server with IIS-TS-TSWeb access installed and configured. Remote app configured and tested as well. All works fine directly on the server itself but is not working for any client connections. I get an Active X error when accessing the TSwebaccess page telling me the actyive x is not installed or enabled. Heres what I tried so far:

     

    1. Upgraded windows xp machine to SP3, which is supposed to contain the updated RDC client, which it does. Tswebaccess still gives the active x Error

     

    2. Used another Windows XP machine and changed the error link to go to the microsoft site and download and install KB925876. Still does not work.

     

    3. Installed the Desktop Experince Role - did not correct

     

    Can someone help me? It does not good in our eval if no clients can connect. Im just trying to test out the published applications part of 2K8 RC1.

Answers

  • Tuesday, January 15, 2008 11:16 PM
    Owner
     
     Answered

    The TS ActiveX control (needed by TSWA) is disabled by default in XPSP3 as a security measure. You need to explicitly enable the Terminal Services activeX control in IE in order to use the activeX control (and hence TSWA).

    Click on Manage Add-Ons in IE to enable the TS ActiveX control.

     

    Are you using IE6 OR IE 7 to access TSWA?

    If you are unable to see/enable the Terminal Services ACtiveX control in IE7 on XPSP3 (we are investigating this known issue) as a workaround can you try deleting the following registry keys:

    HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}

    HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{4eb89ff4-7f78-4a0f-8b8d-2bf02e94e4b2}

     

    Once you delete these keys, the activeX control should be enabled in IE7.

     

     

All Replies

  • Tuesday, January 15, 2008 11:16 PM
    Owner
     
     Answered

    The TS ActiveX control (needed by TSWA) is disabled by default in XPSP3 as a security measure. You need to explicitly enable the Terminal Services activeX control in IE in order to use the activeX control (and hence TSWA).

    Click on Manage Add-Ons in IE to enable the TS ActiveX control.

     

    Are you using IE6 OR IE 7 to access TSWA?

    If you are unable to see/enable the Terminal Services ACtiveX control in IE7 on XPSP3 (we are investigating this known issue) as a workaround can you try deleting the following registry keys:

    HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}

    HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{4eb89ff4-7f78-4a0f-8b8d-2bf02e94e4b2}

     

    Once you delete these keys, the activeX control should be enabled in IE7.

     

     

  • Friday, January 30, 2009 11:15 PM
     
     

    This is a great fix, thank you. for my clients that did not have the add-on listed this works. i can also push out a .reg key to remove these through sms to automate the procedure.

     

    i have on question, for clients that do have the add-on listed but disabled. is there a way to enable it in a command line or other automated way besides asking the user to enable it? Thank you for your help.

  • Monday, February 02, 2009 6:38 PM
     
     
    sorry, but i figured this one out just recently. apparently deleting these 2 keys works on a system whether they can see the add-ons in manage add-ons or not. Also, if you disable the add-on again in manage add-ons after deleting these 2 keys, windows adds these keys back. Thanks for your help, this is very helpful.
  • Monday, March 30, 2009 5:04 PM
     
     
    Thank you very much, I almost had to dye my hair over this one. Removing the key fixed it instantly as it didn't show the TS active x option. Are you aware if there an easier way to enable this add on without having to change the registry? Like a command line or a script that can be ran? This is a very nice feature but in an enterprise environment I wouldn't trust my users in the registry given they don't even have access and help desk has plenty to deal with.
  • Thursday, April 30, 2009 11:43 AM
     
     
    Hi Jay R. Pielemeier,

    You have to register this dll "mstscax.dll" if the active x didn't show

    %windir%\system32\regsvr32 mstscax.dll
  • Sunday, May 17, 2009 6:44 AM
     
     
    Thanks, I will try that. I don't know what it is but I noticed that XP installs act different even if the configuration is the same. In some cases when I reimage the mashine I have trouble with it is working fine and then in other cases it won't at all or I have to apply the registry fix as listed above. I also noticed that it will function perfectly with any Vista or 7 installs without any tweaking. I also have an automation for the registry changes that can be deployed on clients to make things easier which I will post when I try to register the mstscax.dll that would sum up all available resolutions.
  • Wednesday, April 14, 2010 6:37 PM
     
     

    Sorry to bring up an old issue, but did your investigating find anything?  The reason I ask is that I encountered this issue on an WinXP-SP3 workstation today that was accessing a newly created 2k8 server.  Deleting the reg keys worked, but I'm wondering if a more "elegant" solution has been found.  Some of our end users are in remote locations and won't be able to edit the registry or run a .reg file.

    Thanks.

  • Wednesday, June 23, 2010 12:04 AM
     
     

    Thank You, this method really help!

  • Monday, November 01, 2010 8:03 PM
     
     

    Sorry to bring up an old issue, but did your investigating find anything?  The reason I ask is that I encountered this issue on an WinXP-SP3 workstation today that was accessing a newly created 2k8 server.  Deleting the reg keys worked, but I'm wondering if a more "elegant" solution has been found.  Some of our end users are in remote locations and won't be able to edit the registry or run a .reg file.

    Thanks.


    I second this request - seems silly to send end users to the registry to muck about and delete keys.  We have a number of peopel who are remote and don't have domain membership that still need to use RDP, so a group policy won't fix.

    Is there an easier way now? There should be, if there isn't is a patch being activly worked on?

    == John ==


    == John ==
  • Wednesday, November 24, 2010 3:41 PM
     
     
    Thanks a lot, it was quick fix and working fine.
  • Monday, January 24, 2011 10:16 PM
     
     

    I've found installing Remote Desktop Connection version 7 seems to help with this too.

    http://www.microsoft.com/downloads/en/details.aspx?FamilyId=72158b4e-b527-45e4-af24-d02938a95683&displaylang=en

  • Monday, March 21, 2011 5:09 PM
     
     

    Worked!!!

    Using IE 8 and RDC v6.176