Disconnecting & Forcing Logoff

[Guest compsosinc@gmail.com]

1. Is there a way to disable a user's ability to disconnect (using the

X on the RDP connection) from a session and to force them to logoff

without following this procedure below:

 

http://terminal.servebeer.com/php/x_box_disable.php

 

For instance, can the "X" be disabled or if they click it, can their

session be "instantly" reconnected.

 

2. In our particular situation, our Terminal Server users (note, we

have 1 generic user account/machine that need identical settings) &

they do not need to use their local XP workstation for anything else.

Currently, if they have to reboot their workstations, they get the CTRL

+ALT+DEL to login to the domain. Once they login, a saved an .RDP file

in the User's Startup folder connects them to the Terminal Server. Not

sure of another way....

 

3. Once they connect to the TS, we would like a particular program to

open. Is this best configured in the Group Policy or in the TS Profile

of the User account? We have a Group Policy created to lockdown the TS

(in its own OU).

 

4. We only want (1) program shortcut icon on the desktop in case they

close the program and have to reopen it. Is it possible to prevent

deletion of this shortcut, OR if it is deleted, have only it on the

Start Menu (not using Classic) where it cannot be deleted? Then, if

they reconnect the desktop icons come back. We have read about Folder

Redirection, mandatory profiles, roaming profiles, default profiles,

etc but seem to need guidance on the best method to use.

 

Thanks so much

[Guest Vera Noest [MVP]]

Re: Disconnecting & Forcing Logoff

 

comments inline

 

compsosinc@gmail.com wrote on 04 mar 2008 in

microsoft.public.windows.terminal_services:

> 1. Is there a way to disable a user's ability to disconnect

> (using the X on the RDP connection) from a session and to force

> them to logoff without following this procedure below:

>

> http://terminal.servebeer.com/php/x_box_disable.php

>

> For instance, can the "X" be disabled or if they click it, can

> their session be "instantly" reconnected.

 

The AppScape Lockdown Utility disables the X-box

http://www.dabcc.com/ThinSol/Downloads/default.htm

 

The only other approach is to configure your server to immediately

reset disconnected sessions, but that can cause data loss if users

disconnect while they have unsaved data in the session.

> 2. In our particular situation, our Terminal Server users (note,

> we have 1 generic user account/machine that need identical

> settings) & they do not need to use their local XP workstation

> for anything else. Currently, if they have to reboot their

> workstations, they get the CTRL +ALT+DEL to login to the domain.

> Once they login, a saved an .RDP file in the User's Startup

> folder connects them to the Terminal Server. Not sure of another

> way....

 

A hardware or software thin client would be the other way to go.

Check Patrick's website:

http://www.sessioncomputing.com/thin-clients.htm

> 3. Once they connect to the TS, we would like a particular

> program to open. Is this best configured in the Group Policy or

> in the TS Profile of the User account? We have a Group Policy

> created to lockdown the TS (in its own OU).

 

A GPO is *always* best! You only have to make the configuration in

one place, and you are already setup for when you add a second TS.

> 4. We only want (1) program shortcut icon on the desktop in case

> they close the program and have to reopen it. Is it possible to

> prevent deletion of this shortcut, OR if it is deleted, have

> only it on the Start Menu (not using Classic) where it cannot be

> deleted? Then, if they reconnect the desktop icons come back. We

> have read about Folder Redirection, mandatory profiles, roaming

> profiles, default profiles, etc but seem to need guidance on the

> best method to use.

 

You can just put the shortcut on the All Users Desktop if it isn't

already there and make it read-only.

But note that if you define a Starting application, users will

never see the desktop, the session will logoff as soon as they exit

the application.

> Thanks so much

 

You're welcome!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

[Guest compsosinc@gmail.com]

Re: Disconnecting & Forcing Logoff

 

On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> comments inline

>

> compsos...@gmail.com wrote on 04 mar 2008 in

> microsoft.public.windows.terminal_services:

>

> > 1. Is there a way to disable a user's ability to disconnect

> > (using the X on the RDP connection) from a session and to force

> > them to logoff without following this procedure below:

>

> >http://terminal.servebeer.com/php/x_box_disable.php

>

> > For instance, can the "X" be disabled or if they click it, can

> > their session be "instantly" reconnected.

>

> The AppScape Lockdown Utility disables the X-boxhttp://www.dabcc.com/ThinSol/Downloads/default.htm

>

> The only other approach is to configure your server to immediately

> reset disconnected sessions, but that can cause data loss if users

> disconnect while they have unsaved data in the session.

>

> > 2. In our particular situation, our Terminal Server users (note,

> > we have 1 generic user account/machine that need identical

> > settings) & they do not need to use their local XP workstation

> > for anything else. Currently, if they have to reboot their

> > workstations, they get the CTRL +ALT+DEL to login to the domain.

> > Once they login, a saved an .RDP file in the User's Startup

> > folder connects them to the Terminal Server. Not sure of another

> > way....

>

> A hardware or software thin client would be the other way to go.

> Check Patrick's website:http://www.sessioncomputing.com/thin-clients.htm

>

> > 3. Once they connect to the TS, we would like a particular

> > program to open. Is this best configured in the Group Policy or

> > in the TS Profile of the User account? We have a Group Policy

> > created to lockdown the TS (in its own OU).

>

> A GPO is *always* best! You only have to make the configuration in

> one place, and you are already setup for when you add a second TS.

>

> > 4. We only want (1) program shortcut icon on the desktop in case

> > they close the program and have to reopen it. Is it possible to

> > prevent deletion of this shortcut, OR if it is deleted, have

> > only it on the Start Menu (not using Classic) where it cannot be

> > deleted? Then, if they reconnect the desktop icons come back. We

> > have read about Folder Redirection, mandatory profiles, roaming

> > profiles, default profiles, etc but seem to need guidance on the

> > best method to use.

>

> You can just put the shortcut on the All Users Desktop if it isn't

> already there and make it read-only.

> But note that if you define a Starting application, users will

> never see the desktop, the session will logoff as soon as they exit

> the application.

>

> > Thanks so much

>

> You're welcome!

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting:  http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

 

I guess we will tackle these issues one at a time...We just tried

putting shorcut icon for Wordpad, MS Word & Excel in the 'All Users'

folder on the TS and that does put the icons on the TS Session

desktop. However, the programs will not open and the icons do not show

the correct .ico file, there are no errors. We did not make them read-

only yet until we get the programs to open. We must have set somethig

in the GP that prohibits any desktop shortcuts from working? Also, we

though we read somewhere where we could populate the desktop using

Folder Redirection-this would prevent unwanted shortcuts from showing

up on the TS for the administrator?

[Guest compsosinc@gmail.com]

Re: Disconnecting & Forcing Logoff

 

On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> comments inline

>

> compsos...@gmail.com wrote on 04 mar 2008 in

> microsoft.public.windows.terminal_services:

>

> > 1. Is there a way to disable a user's ability to disconnect

> > (using the X on the RDP connection) from a session and to force

> > them to logoff without following this procedure below:

>

> >http://terminal.servebeer.com/php/x_box_disable.php

>

> > For instance, can the "X" be disabled or if they click it, can

> > their session be "instantly" reconnected.

>

> The AppScape Lockdown Utility disables the X-boxhttp://www.dabcc.com/ThinSol/Downloads/default.htm

>

> The only other approach is to configure your server to immediately

> reset disconnected sessions, but that can cause data loss if users

> disconnect while they have unsaved data in the session.

>

> > 2. In our particular situation, our Terminal Server users (note,

> > we have 1 generic user account/machine that need identical

> > settings) & they do not need to use their local XP workstation

> > for anything else. Currently, if they have to reboot their

> > workstations, they get the CTRL +ALT+DEL to login to the domain.

> > Once they login, a saved an .RDP file in the User's Startup

> > folder connects them to the Terminal Server. Not sure of another

> > way....

>

> A hardware or software thin client would be the other way to go.

> Check Patrick's website:http://www.sessioncomputing.com/thin-clients.htm

>

> > 3. Once they connect to the TS, we would like a particular

> > program to open. Is this best configured in the Group Policy or

> > in the TS Profile of the User account? We have a Group Policy

> > created to lockdown the TS (in its own OU).

>

> A GPO is *always* best! You only have to make the configuration in

> one place, and you are already setup for when you add a second TS.

>

> > 4. We only want (1) program shortcut icon on the desktop in case

> > they close the program and have to reopen it. Is it possible to

> > prevent deletion of this shortcut, OR if it is deleted, have

> > only it on the Start Menu (not using Classic) where it cannot be

> > deleted? Then, if they reconnect the desktop icons come back. We

> > have read about Folder Redirection, mandatory profiles, roaming

> > profiles, default profiles, etc but seem to need guidance on the

> > best method to use.

>

> You can just put the shortcut on the All Users Desktop if it isn't

> already there and make it read-only.

> But note that if you define a Starting application, users will

> never see the desktop, the session will logoff as soon as they exit

> the application.

>

> > Thanks so much

>

> You're welcome!

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting:  http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

 

Concerning resetting the connection when a user disconnects instead of

logging off. We are going to keep the X on the RDP connection. However

we are looking through the GP for resetting the disconnected session

under User Config> Admin Temp>Wind Comp> Term Serv> Sesssions: "set

time limit for disconnected sessions". Is this where --it explains

that this cannot be used with WindowsXP RDP??

[Guest compsosinc@gmail.com]

Re: Disconnecting & Forcing Logoff

 

On Mar 4, 4:20 pm, compsos...@gmail.com wrote:

> On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

>

>

>

>

>

> this.hem.utfors.se> wrote:

> > comments inline

>

> > compsos...@gmail.com wrote on 04 mar 2008 in

> > microsoft.public.windows.terminal_services:

>

> > > 1. Is there a way to disable a user's ability to disconnect

> > > (using the X on the RDP connection) from a session and to force

> > > them to logoff without following this procedure below:

>

> > >http://terminal.servebeer.com/php/x_box_disable.php

>

> > > For instance, can the "X" be disabled or if they click it, can

> > > their session be "instantly" reconnected.

>

> > The AppScape Lockdown Utility disables the X-boxhttp://www.dabcc.com/ThinSol/Downloads/default.htm

>

> > The only other approach is to configure your server to immediately

> > reset disconnected sessions, but that can cause data loss if users

> > disconnect while they have unsaved data in the session.

>

> > > 2. In our particular situation, our Terminal Server users (note,

> > > we have 1 generic user account/machine that need identical

> > > settings) & they do not need to use their local XP workstation

> > > for anything else. Currently, if they have to reboot their

> > > workstations, they get the CTRL +ALT+DEL to login to the domain.

> > > Once they login, a saved an .RDP file in the User's Startup

> > > folder connects them to the Terminal Server. Not sure of another

> > > way....

>

> > A hardware or software thin client would be the other way to go.

> > Check Patrick's website:http://www.sessioncomputing.com/thin-clients.htm

>

> > > 3. Once they connect to the TS, we would like a particular

> > > program to open. Is this best configured in the Group Policy or

> > > in the TS Profile of the User account? We have a Group Policy

> > > created to lockdown the TS (in its own OU).

>

> > A GPO is *always* best! You only have to make the configuration in

> > one place, and you are already setup for when you add a second TS.

>

> > > 4. We only want (1) program shortcut icon on the desktop in case

> > > they close the program and have to reopen it. Is it possible to

> > > prevent deletion of this shortcut, OR if it is deleted, have

> > > only it on the Start Menu (not using Classic) where it cannot be

> > > deleted? Then, if they reconnect the desktop icons come back. We

> > > have read about Folder Redirection, mandatory profiles, roaming

> > > profiles, default profiles, etc but seem to need guidance on the

> > > best method to use.

>

> > You can just put the shortcut on the All Users Desktop if it isn't

> > already there and make it read-only.

> > But note that if you define a Starting application, users will

> > never see the desktop, the session will logoff as soon as they exit

> > the application.

>

> > > Thanks so much

>

> > You're welcome!

> > _________________________________________________________

> > Vera Noest

> > MCSE, CCEA, Microsoft MVP - Terminal Server

> > TS troubleshooting:  http://ts.veranoest.net

> > ___ please respond in newsgroup, NOT by private email ___

>

> Concerning resetting the connection when a user disconnects instead of

> logging off. We are going to keep the X on the RDP connection. However

> we are looking through the GP for resetting the disconnected session

> under User Config> Admin Temp>Wind Comp> Term Serv> Sesssions:  "set

> time limit for disconnected sessions". Is this where --it explains

> that this cannot be used with WindowsXP RDP??- Hide quoted text -

>

> - Show quoted text -

 

We solved the icon problem ..was not a GP problem but another that

could probably only happen to us!

[Guest Vera Noest [MVP]]

Re: Disconnecting & Forcing Logoff

 

Sounds like a permission problem. Most likely, you own the

shortcuts, and users don't have execute rights.

Or the path is wrong.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

compsosinc@gmail.com wrote on 04 mar 2008 in

microsoft.public.windows.terminal_services:

> On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

> this.hem.utfors.se> wrote:

>> comments inline

>>

>> compsos...@gmail.com wrote on 04 mar 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > 1. Is there a way to disable a user's ability to disconnect

>> > (using the X on the RDP connection) from a session and to

>> > force them to logoff without following this procedure below:

>>

>> >http://terminal.servebeer.com/php/x_box_disable.php

>>

>> > For instance, can the "X" be disabled or if they click it,

>> > can their session be "instantly" reconnected.

>>

>> The AppScape Lockdown Utility disables the

>> X-boxhttp://www.dabcc.com/ThinS

> ol/Downloads/default.htm

>>

>> The only other approach is to configure your server to

>> immediately reset disconnected sessions, but that can cause

>> data loss if users disconnect while they have unsaved data in

>> the session.

>>

>> > 2. In our particular situation, our Terminal Server users

>> > (note, we have 1 generic user account/machine that need

>> > identical settings) & they do not need to use their local XP

>> > workstation for anything else. Currently, if they have to

>> > reboot their workstations, they get the CTRL +ALT+DEL to

>> > login to the domain. Once they login, a saved an .RDP file in

>> > the User's Startup folder connects them to the Terminal

>> > Server. Not sure of another way....

>>

>> A hardware or software thin client would be the other way to

>> go. Check Patrick's

>> website:http://www.sessioncomputing.com/thin-clients.htm

>>

>> > 3. Once they connect to the TS, we would like a particular

>> > program to open. Is this best configured in the Group Policy

>> > or in the TS Profile of the User account? We have a Group

>> > Policy created to lockdown the TS (in its own OU).

>>

>> A GPO is *always* best! You only have to make the configuration

>> in one place, and you are already setup for when you add a

>> second TS.

>>

>> > 4. We only want (1) program shortcut icon on the desktop in

>> > case they close the program and have to reopen it. Is it

>> > possible to prevent deletion of this shortcut, OR if it is

>> > deleted, have only it on the Start Menu (not using Classic)

>> > where it cannot be deleted? Then, if they reconnect the

>> > desktop icons come back. We have read about Folder

>> > Redirection, mandatory profiles, roaming profiles, default

>> > profiles, etc but seem to need guidance on the best method to

>> > use.

>>

>> You can just put the shortcut on the All Users Desktop if it

>> isn't already there and make it read-only.

>> But note that if you define a Starting application, users will

>> never see the desktop, the session will logoff as soon as they

>> exit the application.

>>

>> > Thanks so much

>>

>> You're welcome!

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting:  http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>

> I guess we will tackle these issues one at a time...We just

> tried putting shorcut icon for Wordpad, MS Word & Excel in the

> 'All Users' folder on the TS and that does put the icons on the

> TS Session desktop. However, the programs will not open and the

> icons do not show the correct .ico file, there are no errors. We

> did not make them read- only yet until we get the programs to

> open. We must have set somethig in the GP that prohibits any

> desktop shortcuts from working? Also, we though we read

> somewhere where we could populate the desktop using Folder

> Redirection-this would prevent unwanted shortcuts from showing

> up on the TS for the administrator?

[Guest Vera Noest [MVP]]

Re: Disconnecting & Forcing Logoff

 

The "explain" text says:

 

"Note: This setting does not apply to console sessions such as

Remote Desktop sessions with computers running Windows XP

Professional."

 

which means that the time-out settings don't work when you connect

*to* an XP host, or to the console session of a 2003 server.

For normal sessions to your TS, the time-out will work.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

compsosinc@gmail.com wrote on 04 mar 2008 in

microsoft.public.windows.terminal_services:

> On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

> this.hem.utfors.se> wrote:

>> comments inline

>>

>> compsos...@gmail.com wrote on 04 mar 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > 1. Is there a way to disable a user's ability to disconnect

>> > (using the X on the RDP connection) from a session and to

>> > force them to logoff without following this procedure below:

>>

>> >http://terminal.servebeer.com/php/x_box_disable.php

>>

>> > For instance, can the "X" be disabled or if they click it,

>> > can their session be "instantly" reconnected.

>>

>> The AppScape Lockdown Utility disables the

>> X-boxhttp://www.dabcc.com/ThinS

> ol/Downloads/default.htm

>>

>> The only other approach is to configure your server to

>> immediately reset disconnected sessions, but that can cause

>> data loss if users disconnect while they have unsaved data in

>> the session.

>>

>> > 2. In our particular situation, our Terminal Server users

>> > (note, we have 1 generic user account/machine that need

>> > identical settings) & they do not need to use their local XP

>> > workstation for anything else. Currently, if they have to

>> > reboot their workstations, they get the CTRL +ALT+DEL to

>> > login to the domain. Once they login, a saved an .RDP file in

>> > the User's Startup folder connects them to the Terminal

>> > Server. Not sure of another way....

>>

>> A hardware or software thin client would be the other way to

>> go. Check Patrick's

>> website:http://www.sessioncomputing.com/thin-clients.htm

>>

>> > 3. Once they connect to the TS, we would like a particular

>> > program to open. Is this best configured in the Group Policy

>> > or in the TS Profile of the User account? We have a Group

>> > Policy created to lockdown the TS (in its own OU).

>>

>> A GPO is *always* best! You only have to make the configuration

>> in one place, and you are already setup for when you add a

>> second TS.

>>

>> > 4. We only want (1) program shortcut icon on the desktop in

>> > case they close the program and have to reopen it. Is it

>> > possible to prevent deletion of this shortcut, OR if it is

>> > deleted, have only it on the Start Menu (not using Classic)

>> > where it cannot be deleted? Then, if they reconnect the

>> > desktop icons come back. We have read about Folder

>> > Redirection, mandatory profiles, roaming profiles, default

>> > profiles, etc but seem to need guidance on the best method to

>> > use.

>>

>> You can just put the shortcut on the All Users Desktop if it

>> isn't already there and make it read-only.

>> But note that if you define a Starting application, users will

>> never see the desktop, the session will logoff as soon as they

>> exit the application.

>>

>> > Thanks so much

>>

>> You're welcome!

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting:  http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>

> Concerning resetting the connection when a user disconnects

> instead of logging off. We are going to keep the X on the RDP

> connection. However we are looking through the GP for resetting

> the disconnected session under User Config> Admin Temp>Wind

> Comp> Term Serv> Sesssions: "set time limit for disconnected

> sessions". Is this where --it explains that this cannot be used

> with WindowsXP RDP??

[Guest compsosinc@gmail.com]

Re: Disconnecting & Forcing Logoff

 

On Mar 4, 4:56 pm, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> Sounds like a permission problem. Most likely, you own the

> shortcuts, and users don't have execute rights.

> Or the path is wrong.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting:  http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> compsos...@gmail.com wrote on 04 mar 2008 in

> microsoft.public.windows.terminal_services:

>

>

>

> > On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

> > this.hem.utfors.se> wrote:

> >> comments inline

>

> >> compsos...@gmail.com wrote on 04 mar 2008 in

> >> microsoft.public.windows.terminal_services:

>

> >> > 1. Is there a way to disable a user's ability to disconnect

> >> > (using the X on the RDP connection) from a session and to

> >> > force them to logoff without following this procedure below:

>

> >> >http://terminal.servebeer.com/php/x_box_disable.php

>

> >> > For instance, can the "X" be disabled or if they click it,

> >> > can their session be "instantly" reconnected.

>

> >> The AppScape Lockdown Utility disables the

> >> X-boxhttp://www.dabcc.com/ThinS

> > ol/Downloads/default.htm

>

> >> The only other approach is to configure your server to

> >> immediately reset disconnected sessions, but that can cause

> >> data loss if users disconnect while they have unsaved data in

> >> the session.

>

> >> > 2. In our particular situation, our Terminal Server users

> >> > (note, we have 1 generic user account/machine that need

> >> > identical settings) & they do not need to use their local XP

> >> > workstation for anything else. Currently, if they have to

> >> > reboot their workstations, they get the CTRL +ALT+DEL to

> >> > login to the domain. Once they login, a saved an .RDP file in

> >> > the User's Startup folder connects them to the Terminal

> >> > Server. Not sure of another way....

>

> >> A hardware or software thin client would be the other way to

> >> go. Check Patrick's

> >> website:http://www.sessioncomputing.com/thin-clients.htm

>

> >> > 3. Once they connect to the TS, we would like a particular

> >> > program to open. Is this best configured in the Group Policy

> >> > or in the TS Profile of the User account? We have a Group

> >> > Policy created to lockdown the TS (in its own OU).

>

> >> A GPO is *always* best! You only have to make the configuration

> >> in one place, and you are already setup for when you add a

> >> second TS.

>

> >> > 4. We only want (1) program shortcut icon on the desktop in

> >> > case they close the program and have to reopen it. Is it

> >> > possible to prevent deletion of this shortcut, OR if it is

> >> > deleted, have only it on the Start Menu (not using Classic)

> >> > where it cannot be deleted? Then, if they reconnect the

> >> > desktop icons come back. We have read about Folder

> >> > Redirection, mandatory profiles, roaming profiles, default

> >> > profiles, etc but seem to need guidance on the best method to

> >> > use.

>

> >> You can just put the shortcut on the All Users Desktop if it

> >> isn't already there and make it read-only.

> >> But note that if you define a Starting application, users will

> >> never see the desktop, the session will logoff as soon as they

> >> exit the application.

>

> >> > Thanks so much

>

> >> You're welcome!

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting:  http://ts.veranoest.net

> >> ___ please respond in newsgroup, NOT by private email ___

>

> > I guess we will tackle these issues one at a time...We just

> > tried putting shorcut icon for Wordpad, MS Word & Excel in the

> > 'All Users' folder on the TS and that does put the icons on the

> > TS Session desktop. However, the programs will not open and the

> > icons do not show the correct .ico file, there are no errors. We

> > did not make them read- only yet until we get the programs to

> > open. We must have set somethig in the GP that prohibits any

> > desktop shortcuts from working?  Also, we though we read

> > somewhere where we could populate the desktop using Folder

> > Redirection-this would prevent unwanted shortcuts from showing

> > up on the TS for the administrator?- Hide quoted text -

>

> - Show quoted text -

 

It was a permission problem....thanks

[Guest compsosinc@gmail.com]

Re: Disconnecting & Forcing Logoff

 

On Mar 4, 5:00 pm, "Vera Noest [MVP]" <vera.no...@remove-

this.hem.utfors.se> wrote:

> The "explain" text says:

>

> "Note: This setting does not apply to console sessions such as

> Remote Desktop sessions with computers running Windows XP

> Professional."

>

> which means that the time-out settings don't work when you connect

> *to* an XP host, or to the console session of a 2003 server.

> For normal sessions to your TS, the time-out will work.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting:  http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> compsos...@gmail.com wrote on 04 mar 2008 in

> microsoft.public.windows.terminal_services:

>

>

>

> > On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

> > this.hem.utfors.se> wrote:

> >> comments inline

>

> >> compsos...@gmail.com wrote on 04 mar 2008 in

> >> microsoft.public.windows.terminal_services:

>

> >> > 1. Is there a way to disable a user's ability to disconnect

> >> > (using the X on the RDP connection) from a session and to

> >> > force them to logoff without following this procedure below:

>

> >> >http://terminal.servebeer.com/php/x_box_disable.php

>

> >> > For instance, can the "X" be disabled or if they click it,

> >> > can their session be "instantly" reconnected.

>

> >> The AppScape Lockdown Utility disables the

> >> X-boxhttp://www.dabcc.com/ThinS

> > ol/Downloads/default.htm

>

> >> The only other approach is to configure your server to

> >> immediately reset disconnected sessions, but that can cause

> >> data loss if users disconnect while they have unsaved data in

> >> the session.

>

> >> > 2. In our particular situation, our Terminal Server users

> >> > (note, we have 1 generic user account/machine that need

> >> > identical settings) & they do not need to use their local XP

> >> > workstation for anything else. Currently, if they have to

> >> > reboot their workstations, they get the CTRL +ALT+DEL to

> >> > login to the domain. Once they login, a saved an .RDP file in

> >> > the User's Startup folder connects them to the Terminal

> >> > Server. Not sure of another way....

>

> >> A hardware or software thin client would be the other way to

> >> go. Check Patrick's

> >> website:http://www.sessioncomputing.com/thin-clients.htm

>

> >> > 3. Once they connect to the TS, we would like a particular

> >> > program to open. Is this best configured in the Group Policy

> >> > or in the TS Profile of the User account? We have a Group

> >> > Policy created to lockdown the TS (in its own OU).

>

> >> A GPO is *always* best! You only have to make the configuration

> >> in one place, and you are already setup for when you add a

> >> second TS.

>

> >> > 4. We only want (1) program shortcut icon on the desktop in

> >> > case they close the program and have to reopen it. Is it

> >> > possible to prevent deletion of this shortcut, OR if it is

> >> > deleted, have only it on the Start Menu (not using Classic)

> >> > where it cannot be deleted? Then, if they reconnect the

> >> > desktop icons come back. We have read about Folder

> >> > Redirection, mandatory profiles, roaming profiles, default

> >> > profiles, etc but seem to need guidance on the best method to

> >> > use.

>

> >> You can just put the shortcut on the All Users Desktop if it

> >> isn't already there and make it read-only.

> >> But note that if you define a Starting application, users will

> >> never see the desktop, the session will logoff as soon as they

> >> exit the application.

>

> >> > Thanks so much

>

> >> You're welcome!

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting:  http://ts.veranoest.net

> >> ___ please respond in newsgroup, NOT by private email ___

>

> > Concerning resetting the connection when a user disconnects

> > instead of logging off. We are going to keep the X on the RDP

> > connection. However we are looking through the GP for resetting

> > the disconnected session under User Config> Admin Temp>Wind

> > Comp> Term Serv> Sesssions:  "set time limit for disconnected

> > sessions". Is this where --it explains that this cannot be used

> > with WindowsXP RDP??- Hide quoted text -

>

> - Show quoted text -

 

Setting "read-only" for the Shortcut on the TS desktop within the "All

Users" folder is not preventing the user from deleting it. Should we

set Security permissions on the All Users\Desktop folder instead?

 

Also, in case we cannot figure out how to prevent them from deleting

the shortcut, we would like to provide a way for them to click on it

within the Start Menu -either as Pinned program or on the "All

Programs" list -- we have removed this in the GP however. I think if

we coud get Folder Redirection to work , or a default profile, it

would solve these issues. The last time we tried Folder Redirection we

messed it up and went back to the drawing board, but if it is the best

way to do this and give us the best flexibility with providing future

shortcuts/apps in the future we shold just learn the proper way to do

things. Currently the TS Users see just "Printers & Faxes", Windows

Security & Logoff on the Start Menu (non-classic). Please advise &

thanks...

[Guest Vera Noest [MVP]]

Re: Disconnecting & Forcing Logoff

 

Just configure redirection of the Start Menu and the Desktop to

custom folders, and make those read-only.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

compsosinc@gmail.com wrote on 04 mar 2008 in

microsoft.public.windows.terminal_services:

> On Mar 4, 5:00 pm, "Vera Noest [MVP]" <vera.no...@remove-

> this.hem.utfors.se> wrote:

>> The "explain" text says:

>>

>> "Note: This setting does not apply to console sessions such as

>> Remote Desktop sessions with computers running Windows XP

>> Professional."

>>

>> which means that the time-out settings don't work when you

>> connect *to* an XP host, or to the console session of a 2003

>> server. For normal sessions to your TS, the time-out will work.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting:  http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> compsos...@gmail.com wrote on 04 mar 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>

>>

>> > On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-

>> > this.hem.utfors.se> wrote:

>> >> comments inline

>>

>> >> compsos...@gmail.com wrote on 04 mar 2008 in

>> >> microsoft.public.windows.terminal_services:

>>

>> >> > 1. Is there a way to disable a user's ability to

>> >> > disconnect (using the X on the RDP connection) from a

>> >> > session and to force them to logoff without following this

>> >> > procedure below:

>>

>> >> >http://terminal.servebeer.com/php/x_box_disable.php

>>

>> >> > For instance, can the "X" be disabled or if they click it,

>> >> > can their session be "instantly" reconnected.

>>

>> >> The AppScape Lockdown Utility disables the

>> >> X-boxhttp://www.dabcc.com/ThinS

>> > ol/Downloads/default.htm

>>

>> >> The only other approach is to configure your server to

>> >> immediately reset disconnected sessions, but that can cause

>> >> data loss if users disconnect while they have unsaved data

>> >> in the session.

>>

>> >> > 2. In our particular situation, our Terminal Server users

>> >> > (note, we have 1 generic user account/machine that need

>> >> > identical settings) & they do not need to use their local

>> >> > XP workstation for anything else. Currently, if they have

>> >> > to reboot their workstations, they get the CTRL +ALT+DEL

>> >> > to login to the domain. Once they login, a saved an .RDP

>> >> > file in the User's Startup folder connects them to the

>> >> > Terminal Server. Not sure of another way....

>>

>> >> A hardware or software thin client would be the other way to

>> >> go. Check Patrick's

>> >> website:http://www.sessioncomputing.com/thin-clients.htm

>>

>> >> > 3. Once they connect to the TS, we would like a particular

>> >> > program to open. Is this best configured in the Group

>> >> > Policy or in the TS Profile of the User account? We have a

>> >> > Group Policy created to lockdown the TS (in its own OU).

>>

>> >> A GPO is *always* best! You only have to make the

>> >> configuration in one place, and you are already setup for

>> >> when you add a second TS.

>>

>> >> > 4. We only want (1) program shortcut icon on the desktop

>> >> > in case they close the program and have to reopen it. Is

>> >> > it possible to prevent deletion of this shortcut, OR if it

>> >> > is deleted, have only it on the Start Menu (not using

>> >> > Classic) where it cannot be deleted? Then, if they

>> >> > reconnect the desktop icons come back. We have read about

>> >> > Folder Redirection, mandatory profiles, roaming profiles,

>> >> > default profiles, etc but seem to need guidance on the

>> >> > best method to use.

>>

>> >> You can just put the shortcut on the All Users Desktop if it

>> >> isn't already there and make it read-only.

>> >> But note that if you define a Starting application, users

>> >> will never see the desktop, the session will logoff as soon

>> >> as they exit the application.

>>

>> >> > Thanks so much

>>

>> >> You're welcome!

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

>> >> TS troubleshooting:  http://ts.veranoest.net

>> >> ___ please respond in newsgroup, NOT by private email ___

>>

>> > Concerning resetting the connection when a user disconnects

>> > instead of logging off. We are going to keep the X on the RDP

>> > connection. However we are looking through the GP for

>> > resetting the disconnected session under User Config> Admin

>> > Temp>Wind Comp> Term Serv> Sesssions:  "set time limit for

>> > disconnected sessions". Is this where --it explains that this

>> > cannot be used with WindowsXP RDP??- Hide quoted text -

>>

>> - Show quoted text -

>

> Setting "read-only" for the Shortcut on the TS desktop within

> the "All Users" folder is not preventing the user from deleting

> it. Should we set Security permissions on the All Users\Desktop

> folder instead?

>

> Also, in case we cannot figure out how to prevent them from

> deleting the shortcut, we would like to provide a way for them

> to click on it within the Start Menu -either as Pinned program

> or on the "All Programs" list -- we have removed this in the GP

> however. I think if we coud get Folder Redirection to work , or

> a default profile, it would solve these issues. The last time we

> tried Folder Redirection we messed it up and went back to the

> drawing board, but if it is the best way to do this and give us

> the best flexibility with providing future shortcuts/apps in the

> future we shold just learn the proper way to do things.

> Currently the TS Users see just "Printers & Faxes", Windows

> Security & Logoff on the Start Menu (non-classic). Please advise

> & thanks...