Hi all. We've suddenly found a small problem occuring with employees who use the SA2500 SSL VPN to access their PC's from home via RDP (not using Network Connect but instead using the links you can create under the Terminal Services section of the users landing page).
The issue is that they can successfully remote into their systems and work fine and when they're done disconnect from the session (not log off their PC). However, when they come into the office and log into their PC it's as if they logged off the PC when the finished the RDP session from home. Anything they left up and running when they disconnected is gone and they end up logging in as if they'd logged out.
In other words for all intents and puroses they were logged off the network.
This is obviously an issue for all of us and this only just started happening in the last two weeks. Yes, some things have been done in the SA2500 within the last two weeks. Some new roles have been created, new resource profiles and resource policies, etc. But I can't think of anything that would be causing this that was done, nor can I find anything when I look around.
Any thoughts?
Hi,
I don't believe there are any Juniper side settings to address that. What I've done in the past is to add a Shortcut to users desktops and educate them to lock their screen before exiting the session.
Right click on the Desktop
Choose New â>> Shortcuts
And then in the dialog box type the following
rundll32 user32.dll,LockWorkStation
Strange - but i think we would need to look into the terminal services logs to probably find out what could be happening. Also, i would suggest to open a JTAC ticket for a faster progress on this.
I don't believe that this is a Juniper issue. This sounds more like a local group policy. If I recall correctly there are group policies that can automatically disconnect and / or log off stale RDP sessions.
Here is an MS article on the subject: http://technet.microsoft.com/en-us/library/cc753112(WS.10).aspx
The article references Windows Server 2008, but I have configured these settings on client systems going as far back as Windows 2000 and XP.
Good luck.