Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, February 7, 2018 12:49 PM
Hi,
I have a user that works from home in the morning and remote controlls his desktop in the office, after doing what he needs to do he then disconnects (clicks the close cross on the top bar) so that everything he needs stays open and running, he then gets into the office an hour or so later and finds that everything has been closed and it is as if he has logged out.
Currently running Windows 10 Enterprise 1607 on both devices, and both are patched up to Jan 2018.
EDIT: All Group Policies regarding remote desktop service are set to not configured
All replies (7)
Wednesday, February 7, 2018 2:57 PM
I have the same problemi.
Instead of Windows 10, I am connecting to a Windows Server 2012 server to launch a script that sends all invoices to our customers.
Before I was used to enter the desktop, open our erp, launch the script and close the connection by pressing the cross on remote desktop top bar.
The server, meanwhile, was sending all invoices.
Now if I close the session, the user log off and stop what was doing, so I have to maintain RDP connection open and NEVER (I say never) close the connection, cause the user will log off and stop sending Emails.
Any ideas?
Wednesday, February 7, 2018 4:42 PM
there is a group policy Set time limit for disconnected sessions, see:
Disconnecting from Remote Desktop causes the computer to log off user
Monday, February 12, 2018 9:14 AM | 1 vote
It's not a problem of timeout.
The problem occurs when I click on the "X" on the topbar.
If I leave the session open It works and never disconnect
Monday, February 12, 2018 4:01 PM
As I said in my post "All Group Policies regarding remote desktop service are set to not configured".
If you disable or do not configure this policy setting, this policy setting is not specified at the Group Policy level. by default, Remote Desktop Services disconnected sessions are maintained for an unlimited amount of time.
Tuesday, February 13, 2018 3:32 PM
As I said in my post "All Group Policies regarding remote desktop service are set to not configured".
If you disable or do not configure this policy setting, this policy setting is not specified at the Group Policy level. by default, Remote Desktop Services disconnected sessions are maintained for an unlimited amount of time.
Quote Above...
Tuesday, December 3, 2019 12:48 PM
After reading all these comments it does not seem like anyone has an answer to this issue. We have the same issue, we have some monitoring software that runs, if my remote desktop connection gets closed it by the looks of it closes the session. If I log in a few seconds after closing I can still see everything run.
The server is a Windows Server 2016 that has been hardened to the CIS standards after going into the Remote Desktop Services\Remote Desktop Session Host\Session Time Limits and configuring everything in there it is still not keeping the session open. Any idea what could be causing this?
Tuesday, December 3, 2019 1:19 PM
Executing UFT Scripts on a remote machine
I am attempting to execute UFT test cases on a remote machine but it only seems to work when I have an RDP connection open to the remote machine. If I have to open an RDP connection anyway, I might as well go ahead and kick them off directly on the machine.
We are tightly integrated with ALM/QC and I have my automated tests in a test set. I would like to open QC (on my laptop), navigate to the test set, Run Test Set, and enter the name of the remote machine (a dedicated "test runner" machine). This machine has both QC and UFT installed and options selected to "allow other HP product to run test".
Unfortunately I get errors saying it can't connect to the remote machine. If I first open an RDP session to this machine, it seems to work.
One of our goals is to have automated testers create the UFT tests and add them to the designated test set. Then non-technical users can kick them off from QC at will without needing to really know anything about UFT. We just would like to give them the name of the "test runner" machine to enter in the correct field and come back later to see the results. Having lots of manual testers RDP into the 'test runner' first is impractical for a variety of reasons.
Any help or suggestions would be app