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

I appreciate your help, Patrick. I will work on pushing the "hacked"
mstsc.exe out to users right away. In the meantime, though, do you have any
thoughts on why my changes in 2003 Group Policy Management are not being
applied to the 2000 server (sitting in the container to which the modified
policy applies?) Thanks in advance...

dana

"Patrick Rouse" wrote:

> 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: Problems with Remote Desktop Connction to SBS
    ... the office and connecting over a VPN and on the server itself (you can ... You mentioned "Disconnect, but leave session running", I have ... As Sarah said, how did you disconnect? ... Please type the full error message word by word to the Newsgroup, ...
    (microsoft.public.windows.server.sbs)
  • Event ID: 12061
    ... >timed out and disconnected by the server. ... The IP address of the Macintosh workstation is ... The events security log reports the following when the ... The disconnect occurs when the machines are idle and ...
    (microsoft.public.win2000.macintosh)
  • Re: Account keeps locking out
    ... disconnect the mapping manually, also the printer (which was setup using the ... Does the user have manually mapped network drives? ... the server kept on locking him out. ... Client accesses the internet via the server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Account keeps locking out
    ... disconnect the mapping manually, also the printer (which was setup using ... and hen I remapped the printer and the drives, ... the server kept on locking him out. ... Client accesses the internet via the server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Prevented from adding users
    ... I have checked the default settings on my server 2003 and XP client. ... users from installing printer drivers" to disabled on the server and "point ... still get the sam message (GPO has bee refreshed by restarting XP clients). ... The policy setting applies only to non Print Administrators ...
    (microsoft.public.windowsxp.print_fax)