Re: Terminal Server 2003 - Manager not visible or accessible

Thanks for your report, HTH.
There's an alternative solution to this problem:

Start regedit and navigate to this registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion
\Terminal Server\TSADMIN

Delete the "Placement" value and exit regedit.

The problem is that at some point the TSAdmin window position
settings were saved in a high-resolution session; with it running
in a low-resolution session, those values position it off the
viewable screen.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

ngqs2004@xxxxxxxxx wrote on 25 jun 2005 in
microsoft.public.windows.terminal_services:

> This may help someone else. When starting the T.S. Manager
> (tsadmin.exe) on Server 2003, running in application mode, the
> Terminal Server Manager icon shows on the taskbar but the
> application is not accessible or visible.
>
> Trying to end task from TaskManager returns the popup "This
> application cannot...because it is waiting for a response from
> you." (I don't have the exact msg anymore but the key is
> "waiting for a response from you".)
>
> In TaskMgr, Applications, double clicking on the application
> makes tsadmin.exe appear but you cannot gain focus. Clicking on
> the tsadmin.exe window returns an error beep, like there is a
> dialog box open somewhere. Rebooting does not solve the problem.
>
> An additional symptom was that Windows Update would not run, it
> appeared to be in some type of loop condition when loading the
> initial windows update page.
>
> I had to open a ticket w/ MS tech support. In an RDP session
> from another machine, using the same account, we were able to
> run T.S. Manager without problems. Running it this way
> unstuck/caused/allowed tsadmin.exe to appear correctly when run
> while logged on directly to the server.
>
> Tech supt was very helpful but did not have a cause or an answer
> as to why running from RDP fixed things. Windows update now runs
> correctly, SP1 installed fine.
>
> HTH.
.

Relevant Pages

  • NEW VIRUS ?
    ... MSOFT32.exe runs and takes up all CPU of the PC and it has spread very ... The infected PCs were trying to connect out ... A registry key exists in HKLM\SOFTWARE\MICROSOFT\WINDOWS\RUN ONCE. ... manually doing windows update on 150 PC s AHh! ...
    (microsoft.public.security.virus)
  • Re: Turning on Windows Update Administrativly
    ... >> Network policy settings prevent you from using Windows Update to download ... >> Windows Update to download and install updates. ... > Under the registry key ...
    (microsoft.public.windowsxp.security_admin)
  • Re: XP not allowed to access updates
    ... Please delete the following registry key. ... This may be resolved by uninstalling the third party firewall. ... Windows Update as an excluded site on the firewall/proxy. ... "Miles" wrote in message ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Code 8000FFFF
    ... Corrupted Windows Update Temporary folder ... Rename the Windows Update Softwaredistribution folder ... let's backup the registry key first. ...
    (microsoft.public.windowsupdate)
  • Re: 823559 update doesnt "take"
    ... Followed Maurice's suggestions....the WUTemp folder is ... Critical Update is ... Went to Regedit, ... Windows Update window...and it tells me yet again I need to ...
    (microsoft.public.windowsupdate)