RE: Windows Server 2003 GPM/Windows 2000 TS GPO issue

In a situation where disconnects could cause data, I'd recommend looking into
purchasing a program to publish the application in a seamless window, so it
works as if it's a local program.

The least expensive one I know of is WTSPortal by Terminal-Services.net.
Other more elaborate programs include Provision Networks Management
Framework, Tarantella Secure Global Desktop Terminal Server Edition, Citrix
Presentation Server, DAT Panther Server...

You can disable the disconnect X on the client:
http://terminal.servebeer.com/php/x_box_disable.php

--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com


"Dana Porter" wrote:

> Hello,
>
> I am trying to lock down a Windows 2000 server (running terminal services,
> application mode.) Specifically, I need to make it so that users are forced
> to log off, rather than simply disconnect (we have an issue with multiple
> printer virtual ports and a legacy database application lock issue that we
> can resolve by not allowing users to just disconnect.) I've finally figured
> out that this cannot be done, which means that I've had to move to just
> changing the disconnect/multiple connection behavior of the server itself. I
> used the Windows 2003 Group Policy Management MMC snapin for Windows XP, to
> manage this Windows 2000 server, and the registry changes are there, but
> after several days there is no change in behavior on the server (it has been
> rebooted twice in the last three days, and would have received the new
> computer policy settings by now.)
>
> Here are the changes (the times are short, for testing purposes):
>
> terminalserver
> Data collected on: 8/22/2005 4:01:00 PM
>
> Administrative Templates
> Windows Components/Terminal Services
> Policy Setting
> Remove Disconnect option from Shut Down dialog Enabled
> Restrict Terminal Services users to a single remote session Enabled
>
> Windows Components/Terminal Services/Sessions
> Policy Setting
> Set time limit for disconnected sessions Enabled
> End a disconnected session 1 minute
>
> Policy Setting
> Sets a time limit for active but idle Terminal Services sessions Enabled
> Idle session limit: 5 minutes
>
> Any help is greatly appreciated.
> dana
.

Relevant Pages

  • Re: Log on Interactively
    ... The server is a Windows 2003 Enterprise Edition Server ... I added the Remote Desktop Users group to the permissions tab with the User ... I then added the Terminal Services User group that I had ...
    (microsoft.public.windows.terminal_services)
  • Re: Please Help!
    ... Windows 2000 Terminal Services Licensing FAQ ... Q. What licenses are required to run Terminal Services in Windows ... required to run applications on a Windows 2000 Server via Terminal ...
    (microsoft.public.win2000.termserv.apps)
  • RE: Terminal Server Migration Windows NT to Windows 2003
    ... Microsoft Online Partner Support ... Terminal Server Migration Windows NT to Windows 2003 ... |> Frequently Asked Questions About Terminal Services ...
    (microsoft.public.windows.server.migration)
  • Re: Terminal Services Licensing --- An opinion
    ... Jeffrey Randow (Windows Networking MVP) ... >express an opinion about Terminal Services Licensing. ... >the CALs for the Server Operating system. ...
    (microsoft.public.windows.server.general)
  • Re: Blue Screen of Death when server failover
    ... http://support.microsoft.com?kbid=257956 "Error Message Appears When You Restart ... Windows After Installation of Nero CD-Recording Software" ... Printing with Hewlett-Packard DesignJet Printer Driver from a Terminal Services ... Win32k.sys When Users Log Off from a Server Running Terminal Services" ...
    (microsoft.public.win2000.advanced_server)