Terminal Server not logging off

  • Thread starter Thread starter Jimmy Jones
  • Start date Start date
J

Jimmy Jones

Guest
I have configured the Group Policy setting for Terminal Services to start a
program on connection. This setting is supposed to logg the user off if the
application is closed thus preventing users from being able to access the
desktop, start menu, etc.

The program starts up at logon but if the usre closes the program they are
not logged off and worse they have access to the desktop and start menu.

For the program path and file name I have entered explorer.exe c:\Entry.htm

The working directory is c:\

The OS is Windows Server 2003 Standard Edition

The server is on a domain.

This was working when I had a different application and a different working
directory however I now need it to display this htm page instead.

Thanks in advance for any help.
 
Re: Terminal Server not logging off

Thanks for bringing up the issue.
Yes, explorer seems to be behaving differently than other apps when it is
part of logon program. We'll verify if there is any workaround for this and
update you.

--
Thanks,
Priya.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jimmy Jones" <JimmyJones@discussions.microsoft.com> wrote in message
news:A5BC99D2-84D9-45E1-9E84-2C2D68BD93B3@microsoft.com...
>I have configured the Group Policy setting for Terminal Services to start a
> program on connection. This setting is supposed to logg the user off if
> the
> application is closed thus preventing users from being able to access the
> desktop, start menu, etc.
>
> The program starts up at logon but if the usre closes the program they are
> not logged off and worse they have access to the desktop and start menu.
>
> For the program path and file name I have entered explorer.exe
> c:\Entry.htm
>
> The working directory is c:\
>
> The OS is Windows Server 2003 Standard Edition
>
> The server is on a domain.
>
> This was working when I had a different application and a different
> working
> directory however I now need it to display this htm page instead.
>
> Thanks in advance for any help.
 
Re: Terminal Server not logging off

This is by design. Explorer.exe as the starting application gives a
a full desktop, since explorer.exe is the default shell.

But even with other starting applications, defining a starting
application should *not* be used as a safety mechanism to keep
users out of your TS, at least not by itself. It is *very* simple
to start explorer (and thus a full desktop) from within nearly
every other application.
Defining a starting application is to be considered as a feature to
make life easier for end users who just need to run a single
application. To lockdown the TS, you still need to apply
restrictive GPOs and NTFS permission on the file system.
________________________________________________________
_
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmltbXkgSm9uZXM=?=
<JimmyJones@discussions.microsoft.com> wrote on 11 jan 2008 in
microsoft.public.windows.terminal_services:

> I have configured the Group Policy setting for Terminal Services
> to start a program on connection. This setting is supposed to
> logg the user off if the application is closed thus preventing
> users from being able to access the desktop, start menu, etc.
>
> The program starts up at logon but if the usre closes the
> program they are not logged off and worse they have access to
> the desktop and start menu.
>
> For the program path and file name I have entered explorer.exe
> c:\Entry.htm
>
> The working directory is c:\
>
> The OS is Windows Server 2003 Standard Edition
>
> The server is on a domain.
>
> This was working when I had a different application and a
> different working directory however I now need it to display
> this htm page instead.
>
> Thanks in advance for any help.
 
Re: Terminal Server not logging off

Also, you might want to use "iexplorer.exe" instead of "explorer.exe" in the
startup app, if you want to allow access only to the startup app and log
off.

"iexplorer.exe c:\Entry.htm"

--
Thanks,
Priya.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9A24ECFD3BD95veranoesthemutforsse@207.46.248.16...
> This is by design. Explorer.exe as the starting application gives a
> a full desktop, since explorer.exe is the default shell.
>
> But even with other starting applications, defining a starting
> application should *not* be used as a safety mechanism to keep
> users out of your TS, at least not by itself. It is *very* simple
> to start explorer (and thus a full desktop) from within nearly
> every other application.
> Defining a starting application is to be considered as a feature to
> make life easier for end users who just need to run a single
> application. To lockdown the TS, you still need to apply
> restrictive GPOs and NTFS permission on the file system.
> ________________________________________________________
> _
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?SmltbXkgSm9uZXM=?=
> <JimmyJones@discussions.microsoft.com> wrote on 11 jan 2008 in
> microsoft.public.windows.terminal_services:
>
>> I have configured the Group Policy setting for Terminal Services
>> to start a program on connection. This setting is supposed to
>> logg the user off if the application is closed thus preventing
>> users from being able to access the desktop, start menu, etc.
>>
>> The program starts up at logon but if the usre closes the
>> program they are not logged off and worse they have access to
>> the desktop and start menu.
>>
>> For the program path and file name I have entered explorer.exe
>> c:\Entry.htm
>>
>> The working directory is c:\
>>
>> The OS is Windows Server 2003 Standard Edition
>>
>> The server is on a domain.
>>
>> This was working when I had a different application and a
>> different working directory however I now need it to display
>> this htm page instead.
>>
>> Thanks in advance for any help.
>
 
Back
Top