QUESTION :
What is the difference between disconnect and log off/sign out from an RDC connection?
ANSWER :
as well. Unsaved changes made to open files will be lost.
The next time you log onto the remote computer or server, a new FRESH session is
created with the maximum free memory and a cleaned temporary storage.
So there is no harm to logoff from the server after logging off from the application
The application will stay active, as the eventscheduler communicates with the OS of
the app server.
Only when your user account is connected to application service in the services.msc,
your session may have to be kept active if your network restrictions/policy requires it.
For ending your RDC session, right-mouse-click on the Windows-button bottom-left,
go to 'Shut down or sign out', and choose 'Sign out'.
If your menu changes slowly, make sure your selection hovers over the 'Sign out'-option,
before confirming the selection. (to avoid accidentally shutting down the server...)
Disconnect
So i.e. when lunch time comes and tasks/queries are still to be done, you can
It is not advisable to use the disconnect by default, instead of the logoff.
If an application runs smoothly, it doesn't matter much and a disconnected session
will have little impact.
But when the application/environment is already slow, your temporary storage
and memory use will quickly make it even more slow.
The screenshot below shows that a user with a new RDC logon has a fresh
new growth of memory usage, while a disconnected user session is using
more memory for the temporary storage of its disconnected session.
Before disconnecting an RDC-session for continuing later on, it's best to
close all application sessions and file edit sessions that you don't need
to continue immediately after your RDC reconnect.
Disconnect vs SIgn Out on Windows RDC
Comments
Article is closed for comments.