Gebruiker onder een andere gebruiker afmelden.

[ÜberWicked]

Het volgende: (Afmelden van een andere gebruiker)



zou ik graag automatisch via een script willen verlopen.

Via google gezocht, maar dan vind ik alleen een screensaver (http://blog.case.edu/djc6...tomatically_log_off_users) om dit te doen.

Hebben jullie een ID om dit te doen.

[Outerspace]

En wanneer moet dit gebeuren? Ik snap niet wanneer dat script moet gaan werken, en op welke manier je dit script wil gaan uitvoeren (remote, lokaal) etc. Hoe heb jij dat in gedachte?

[ Voor 8% gewijzigd door Outerspace op 22-09-2006 11:43 ]

[ÜberWicked]

Wij hebben hier een computer en een handheld.
Op de computer logt iemand lokaal in.
De handheld logt via terminal server in op de computer.

Als de sessie van de handheld is vastgelopen, willen we dat er op het bureaublad van de lokale computer een icoon staat die ze op kunnen starten, zodat de sessie van de handheld hard uitgelogd word.

Nu herstarten we gewoon de hele computer om de handheld sessie te resetten.

We gebruiken geen terminal server, maar een patch die Windows XP SP2 in staat stelt meerdere sessies te draaien op terminal server niveau, maar zonder beheer tool.

[Viper®]

Meer info over concurrent remote desktops:
http://sig9.com/articles/concurrent-remote-desktop

Volgens mij kan je dit beter instellen in je Group policy

uitvoeren > gpedit.msc > computer configuration > administrative templates > windows components > terminal services:

interessante instellingen:

Keep-Alive Connections:

Specifies whether persistent connections are allowed.

After a terminal server client loses the connection to a terminal server, the session on the terminal server might remain active instead of changing to a disconnected state, even if the client is physically disconnected from the terminal server. If the client logs on to the same terminal server again, a new session might be established (if Terminal Services is configured to allow multiple sessions), and the original session might still be active.

You can use this setting to enable keep-alive connections and ensure that the session state is consistent with the client state. By default, keep-alive connections are disabled.

To configure keep-alive connections, enable the setting and set the Keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state.

If the status is set to Enabled, keep-alive connections are enabled.

If the status is set to Disabled, the default behavior is enforced.

If the status is set to Not Configured, keep-alive connections remain disabled by default.

Set time limit for disconnected sessions:

Specifies a time limit for disconnected Terminal Services sessions.

You can use this setting to specify the maximum amount of time that a disconnected session is kept active on the server. By default, Terminal Services allows users to disconnect from a remote session without logging off and ending the session.

When a session is in a disconnected state, running programs are kept active even though the user is no longer actively connected. By default, these disconnected sessions are maintained for an unlimited time on the server.

If the status is set to Enabled, disconnected sessions are deleted from the server after the specified amount of time. To enforce the default behavior that disconnected sessions are maintained for an unlimited time, select Never.

If the status is set to Disabled or Not Configured, time limits for disconnected sessions are not specified at the Group Policy level.

Note: This setting does not apply to console sessions such as Remote Desktop sessions with computers running Windows XP Professional. Also note that this setting appears in both Computer Configuration and User Configuration. If both settings are configured, the Computer Configuration setting overrides.

Sets a time limit for active but idle terminal services sessions:

Specifies a time limit for active but idle Terminal Services sessions.

You can use this setting to specify the maximum amount of time that an active session can be idle (that is, no user input) before it is automatically disconnected. By default, Terminal Services allows active sessions to remain idle for an unlimited time.

To use this setting, select Enabled, and then select the desired time limit in the Idle session limit drop-down list.

If the status is set to Enabled, active but idle sessions are automatically disconnected after the specified amount of time. The user receives a two-minute warning before the session ends, which allows the user to press a key or move the mouse to keep the session active.

If the status is set to Disabled or Not Configured, the time limit for active but idle sessions is not specified at the Group Policy level. However, an administrator can specify time limits for idle sessions in the Terminal Services Configuration tool.

Note: This setting appears in both Computer Configuration and User Configuration. If both settings are configured, the Computer Configuration setting overrides. Idle session limits do not apply to the console session. To specify that user sessions are terminated at time-out, enable the "Terminate session when time limits are reached" setting.

In jouw geval zou ik Keep-Alive enablen en een Time out voor disconnected (of idle) terminals zetten