RE: Windows Mobile 6 TS Idle Timeout Issue

Sorry, not the faintest idea, I don't use nor manage PDAs.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?U1BC?= <SPB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 23 aug
2007:

When logged in via Remote Desktop from a local XP box the issue
does NOT exist... When at 19 minutes of idle time the session
did NOT disconnect.

So I guess I am to assume it is on the client side... any
suggestions?

"Vera Noest [MVP]" wrote:

Have you verified hat the GPO is actually applied, with
resultant set of policies (RSoP)?
Does this also happen when you connect to the TS from a XP
client?
_________________________________________________________ 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?U1BC?= <SPB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 22
aug 2007 in microsoft.public.windows.terminal_services:

I just logged into the 2 of the sites using the previously
mentioned application and I have confirmed the session
disconnects at exactly the 10 minute point of idle time.

"SPB" wrote:

I am running several sites that use PDAs for a Point of Sale
Application.

That said I am using a WM6 RDP client to connect to a
Windows 2003 Server TS Server.

Although I have:

1. Set Idle Session Limits to the Maximum (Never) through
the Group Policy Editor
2. Disabled Screen Savers through the Group Policy Editor
3. Enabled KeepAliveEnable in the Registry
4. Set the KeepAliveInterval to 1000 in the Registry
5. Set the KeepAliveTime to 7200000 in the Registry

The clients still disconnect after 10 minutes (or sooner) of
idletime.

If the user is using the handheld "terminal" consistently
everything is fine, however if left idle the RDP client
disconnects.

I need the RDP client to stay "permanently" connected to the
TS Server... this is the ideal situation.

I've been looking for a solution for sometime any advice
would be appreciated.
.

Relevant Pages

  • Re: Access problems against a ts w2k3 with a different user to validated in XP
    ... I upgraded de rdp client and function correctly. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... but I start the session ...
    (microsoft.public.windows.terminal_services)
  • Re: Publish Terminal Server on Internet
    ... Windows Server 2003 TS. ... terminal server, ... From an XP client anywhere on the internet open the RDP Client ...
    (microsoft.public.windows.terminal_services)
  • Re: user sessions remain in disconnect state forever...
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... 216783 - You cannot completely disconnect a Terminal Server ... I have configured user session time limits etc... ...
    (microsoft.public.windows.terminal_services)
  • Re: Single Sign-On
    ... > Users can save their username and password in their rdp client, ... > MCSE, CCEA, Microsoft MVP - Terminal Server ... >> be able to log on to their workstations and launch an RDP file ...
    (microsoft.public.windows.terminal_services)
  • Re: blank desktop
    ... Ensure that you have plenty of disk and meory free on the server - you may be running out of resources perhaps due to a memory leak. ... Often we have to reboot the Terminal server, ... The client can connect and login, but get a blank desktop. ... We have to disconnect him manually for him to get his full desktop. ...
    (microsoft.public.windows.terminal_services)
Loading