[Obituaryan]

Hi all,

Any help would be much appreciated.

I am busy finishing off quite a heavy lock down GP for a client and have come across something I have never had to do before.

Remove the RDP connection bar from all client PC's

I reckon I am probably going to have to use ADM scripting or the like, but am a bit clueless with this one.

So as previously stated any help or advice would be much appreciated

Obit~

[JUGGY]

You talking about the remote options tab in system properties?

Obituaryan said:

Hi all,

Any help would be much appreciated.

I am busy finishing off quite a heavy lock down GP for a client and have come across something I have never had to do before.

Remove the RDP connection bar from all client PC's

I reckon I am probably going to have to use ADM scripting or the like, but am a bit clueless with this one.

So as previously stated any help or advice would be much appreciated

Obit~

[Obituaryan]

Nope the bar along the top of a TS Session, the one that shows the IP, minimize, and close.

The reason for this is I want my users to log off and NOT disconnect their session by clicking the x

[cAv]

Remove as in hide it? There aren't exactly many options on that bar...anywho, why would you want to remove it permanently from the screen? I ask out of curiosity before saying weird as there may be a legit reason, I just can't think of one that makes sense though.

[Obituaryan]

cAv said:

Remove as in hide it? There aren't exactly many options on that bar...anywho, why would you want to remove it permanently from the screen? I ask out of curiosity before saying weird as there may be a legit reason, I just can't think of one that makes sense though.

My reasoning is in my post above.

The users keep disconnecting instead of logging off, I have 3 TS servers so with NLB the disconnects are a bit of an issue, as the policy is stipulating only 1 session may be open at a time, I am not running MS server 2003 Enterprise or MS server 2008, so I do not have the luxury of session broker, therefore this is the quick fix, and wont require a huge cappex expense by going from std to enterprise or even server 08.

[JUGGY]

Why don't you rather set you TS server to reset disconnected sessions after 5 minutes?

Obituaryan said:

My reasoning is in my post above.

The users keep disconnecting instead of logging off, I have 3 TS servers so with NLB the disconnects are a bit of an issue, as the policy is stipulating only 1 session may be open at a time, I am not running MS server 2003 Enterprise or MS server 2008, so I do not have the luxury of session broker, therefore this is the quick fix, and wont require a huge cappex expense by going from std to enterprise or even server 08.

[Obituaryan]

JUGGY said:

Why don't you rather set you TS server to reset disconnected sessions after 5 minutes?

Because than I would have users saying we can't log back in, while they wait the 5 minutes for the server to reset the disconnected sessions.

But thanks for the input. I was hoping to just remove the bar and be done with it :wacko:

[JUGGY]

It's all about communication I guess. Make it 1 minute and tell them all when they log out or disconnect they need to wait.

I ran 8 TS servers with our CRM software on it in an NLB cluster and had the timeouts set to 30 minutes of inactivity the session ends and 5 minutes after a disconnected session it's reset.

Obituaryan said:

Because than I would have users saying we can't log back in, while they wait the 5 minutes for the server to reset the disconnected sessions.

But thanks for the input. I was hoping to just remove the bar and be done with it :wacko:

[Obituaryan]

JUGGY said:

It's all about communication I guess. Make it 1 minute and tell them all when they log out or disconnect they need to wait.

I ran 8 TS servers with our CRM software on it in an NLB cluster and had the timeouts set to 30 minutes of inactivity the session ends and 5 minutes after a disconnected session it's reset.

Nice we using them for Syspro and Notes mainly.

Trying to move completely over to Thinclients and give the users as little room as possible to break stuff.

Where can I set the reset time for disconnected sessions? also what is the shortest period of time for this?

[JUGGY]

I think the shortest period is 1 minute.

If you goto Admin Tools->Terminal Services Configuration then goto properties of RDP-TCP and goto sessions tab.

You'll find all you need in there. It really does help.

I do this on my back office servers as well, sometimes these blimmin admin guys do exactly as your users are doing so I make life easy on all of us by implementing these timeouts.

You can actually set TS to spawn specific apps with specific parameters so as soon as theuser logs on the app they need is launched.

Obituaryan said:

Nice we using them for Syspro and Notes mainly.

Trying to move completely over to Thinclients and give the users as little room as possible to break stuff.

Where can I set the reset time for disconnected sessions? also what is the shortest period of time for this?

[Obituaryan]

JUGGY said:

I think the shortest period is 1 minute.

If you goto Admin Tools->Terminal Services Configuration then goto properties of RDP-TCP and goto sessions tab.

You'll find all you need in there. It really does help.

I do this on my back office servers as well, sometimes these blimmin admin guys do exactly as your users are doing so I make life easy on all of us by implementing these timeouts.

You can actually set TS to spawn specific apps with specific parameters so as soon as theuser logs on the app they need is launched.

Thanks bud, going to give it a shot today =)

I know about the app's launching, although I just create specific accounts that are app only, i.e. Syspro only and if they close syspro it logs them off =)

Haha I hate admins that "know too much "

Once again Thanks a mil :drunk:

[JUGGY]

Cool, hope it works out for you.

[cAv]

If the user disconnects and they log back on are you having a problem that it is making a whole new session? Reason I ask is we use 60 min idle before disconnect then 60 min there after before the user is logged off and we don't have an issue where they can't log back in, if they do it just connects to their previous session.

PS: Sorry for asking what the reasoning was previously, it wasn't there when I clicked reply, think you posted it between the time I clicked reply and when I actually posted.