RemoteApp duplicate SessionWindows 2008 RemoteAPP client disconnects within a matter of minutesWindows 2008R2 RemoteAPP FailoverRemoteApp idle time before disconnectingConnecting RemoteApp to Existing SessionHow can I reconnect to a remoteapp session?How to configure a Remoteapp server to increase stabilityWeb site works fine on Terminal server, but has problems as a RemoteAppWindows 2012 R2 - RemoteApp - limit user instancesLet Windows RemoteApp open files (eg. .docx, .pdf) with client side applicationRemoteApp shortcut behaves like an RDP shortcut
If a problem only occurs randomly once in every N times on average, how many tests do I have to perform to be certain that it's now fixed?
How to prevent bad sectors?
What was this black-and-white film set in the Arctic or Antarctic where the monster/alien gets fried in the end?
Can non-English-speaking characters use wordplay specific to English?
Select row of data if next row contains zero
Is floating in space similar to falling under gravity?
If Sweden was to magically float away, at what altitude would it be visible from the southern hemisphere?
Is the world in Game of Thrones spherical or flat?
Are UK pensions taxed twice?
What does the behaviour of water on the skin of an aircraft in flight tell us?
Thousands and thousands of words
Do creatures all have the same statistics upon being reanimated via the Animate Dead spell?
What is the intuition behind uniform continuity?
Points within polygons in different projections
Why were the Night's Watch required to be celibate?
Possible nonclassical ion from a bicyclic system
Can a wire having a 610-670 THz (frequency of blue light) AC frequency supply, generate blue light?
How to capture more stars?
What are the benefits of cryosleep?
Why to use water tanks from Space shuttle in museum?
The deliberate use of misleading terminology
Smart people send dumb people to a new planet on a space craft that crashes into a body of water
Why would Lupin kill Pettigrew?
Looking after a wayward brother in mother's will
RemoteApp duplicate Session
Windows 2008 RemoteAPP client disconnects within a matter of minutesWindows 2008R2 RemoteAPP FailoverRemoteApp idle time before disconnectingConnecting RemoteApp to Existing SessionHow can I reconnect to a remoteapp session?How to configure a Remoteapp server to increase stabilityWeb site works fine on Terminal server, but has problems as a RemoteAppWindows 2012 R2 - RemoteApp - limit user instancesLet Windows RemoteApp open files (eg. .docx, .pdf) with client side applicationRemoteApp shortcut behaves like an RDP shortcut
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
We have implemented RemoteApp on Windows 2008 R2 to serve out a few programs,everything work fine except one issue,when a user connects to Server a new session opens and a instance of application runs and work correctly but when this session disconnects because of network fault and user reconnects to the server,another instance of app runs in addition of old instance that ran before,so we have to instance of out application that non of them work fine,session hangs and closes automatically,could somebody please help me to solve this problem! I just want to users connect to the existing session and existing instance that they opened before without any new instance
windows-server-2008 terminal-server remoteapp
edited Sep 23 '15 at 11:13
Christian Davén
2511312
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
add a comment |
We have implemented RemoteApp on Windows 2008 R2 to serve out a few programs,everything work fine except one issue,when a user connects to Server a new session opens and a instance of application runs and work correctly but when this session disconnects because of network fault and user reconnects to the server,another instance of app runs in addition of old instance that ran before,so we have to instance of out application that non of them work fine,session hangs and closes automatically,could somebody please help me to solve this problem! I just want to users connect to the existing session and existing instance that they opened before without any new instance
windows-server-2008 terminal-server remoteapp
edited Sep 23 '15 at 11:13
Christian Davén
2511312
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
add a comment |
We have implemented RemoteApp on Windows 2008 R2 to serve out a few programs,everything work fine except one issue,when a user connects to Server a new session opens and a instance of application runs and work correctly but when this session disconnects because of network fault and user reconnects to the server,another instance of app runs in addition of old instance that ran before,so we have to instance of out application that non of them work fine,session hangs and closes automatically,could somebody please help me to solve this problem! I just want to users connect to the existing session and existing instance that they opened before without any new instance
windows-server-2008 terminal-server remoteapp
edited Sep 23 '15 at 11:13
Christian Davén
2511312
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
We have implemented RemoteApp on Windows 2008 R2 to serve out a few programs,everything work fine except one issue,when a user connects to Server a new session opens and a instance of application runs and work correctly but when this session disconnects because of network fault and user reconnects to the server,another instance of app runs in addition of old instance that ran before,so we have to instance of out application that non of them work fine,session hangs and closes automatically,could somebody please help me to solve this problem! I just want to users connect to the existing session and existing instance that they opened before without any new instance
windows-server-2008 terminal-server remoteapp
windows-server-2008 terminal-server remoteapp
edited Sep 23 '15 at 11:13
Christian Davén
2511312
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
edited Sep 23 '15 at 11:13
Christian Davén
2511312
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
edited Sep 23 '15 at 11:13
Christian Davén
2511312
edited Sep 23 '15 at 11:13
Christian Davén
2511312
edited Sep 23 '15 at 11:13
Christian Davén
2511312
2511312
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
asked Aug 8 '14 at 12:46
amir.cscoamir.csco
174
174
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Assuming the apps themselves have nothing to do with it (shouldn't but still).
You are wanting to look at a couple of settings. You can set these via GPO as well, but assuming a single RemoteApp server, the GUI is easy enough.
In the Remote Desktop Session Host Configuration right click on RDP-Tcp and choose Properties.
In there click on the Sessions tab and verify the settings are what you want them to be:
Then close that screen but leave Remote Desktop Session Host Configuration open and verify that Restrict each user to a single session is set to Yes
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
|
show 1 more comment
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f618986%2fremoteapp-duplicate-session%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Assuming the apps themselves have nothing to do with it (shouldn't but still).
You are wanting to look at a couple of settings. You can set these via GPO as well, but assuming a single RemoteApp server, the GUI is easy enough.
In the Remote Desktop Session Host Configuration right click on RDP-Tcp and choose Properties.
In there click on the Sessions tab and verify the settings are what you want them to be:
Then close that screen but leave Remote Desktop Session Host Configuration open and verify that Restrict each user to a single session is set to Yes
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
|
show 1 more comment
Assuming the apps themselves have nothing to do with it (shouldn't but still).
You are wanting to look at a couple of settings. You can set these via GPO as well, but assuming a single RemoteApp server, the GUI is easy enough.
In the Remote Desktop Session Host Configuration right click on RDP-Tcp and choose Properties.
In there click on the Sessions tab and verify the settings are what you want them to be:
Then close that screen but leave Remote Desktop Session Host Configuration open and verify that Restrict each user to a single session is set to Yes
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
|
show 1 more comment
Assuming the apps themselves have nothing to do with it (shouldn't but still).
You are wanting to look at a couple of settings. You can set these via GPO as well, but assuming a single RemoteApp server, the GUI is easy enough.
In the Remote Desktop Session Host Configuration right click on RDP-Tcp and choose Properties.
In there click on the Sessions tab and verify the settings are what you want them to be:
Then close that screen but leave Remote Desktop Session Host Configuration open and verify that Restrict each user to a single session is set to Yes
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
Assuming the apps themselves have nothing to do with it (shouldn't but still).
You are wanting to look at a couple of settings. You can set these via GPO as well, but assuming a single RemoteApp server, the GUI is easy enough.
In the Remote Desktop Session Host Configuration right click on RDP-Tcp and choose Properties.
In there click on the Sessions tab and verify the settings are what you want them to be:
Then close that screen but leave Remote Desktop Session Host Configuration open and verify that Restrict each user to a single session is set to Yes
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
answered Aug 8 '14 at 13:03
TheCleanerTheCleaner
28.4k23108183
28.4k23108183
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
|
show 1 more comment
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Thank you TheCleaner but it wont solve my problem because i have tried it before,for solving this problem i assume two solution, first configure GPO to immediately log off the disconnected session, second configure RemoteApp to run application just when a user logs on not when he or she connects to a disconnected session that is log on currently, but i am not sure about second solution and i don't know how can i do this,
– amir.csco
Aug 8 '14 at 13:17
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
Best I can tell you is that the ABOVE works for every RemoteApp I've deployed. Users get disconnected, and they get reconnected to the same session. That's the first thing you need to verify, that they are reconnecting to the same RDP session, not necessarily that they are opening the same app instance. You can verify this is in the session manager. Your "2nd question" in your comment just now almost says that the application itself isn't very "Remoteapp" friendly. Is it a custom written in-house app?
– TheCleaner
Aug 8 '14 at 13:23
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
yes that's true i can verify that users connect to the same RDP session but not the same application instance that they ran before,its a custom application but absolutely not written in-house,it deveoped buy more than 30 programmer and its wildly used national-wide
– amir.csco
Aug 8 '14 at 13:36
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
Are you certain its the RDP session that gets disconnected and not the app itself? Meaning, do a normal RDP session, not a remoteapp. Then launch the app on the desktop. Now disconnect from the session (hit x and close it, don't logoff). Now reconnect via normal RDP. Is the app still running on the desktop?
– TheCleaner
Aug 8 '14 at 13:54
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
yes session disconnect because of temporary link failures on the WAN link between Clients and RemoteApp server,all i need is just a way to tell to windows that just launch the application only and only when a user logs on
– amir.csco
Aug 8 '14 at 18:51
|
show 1 more comment
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f618986%2fremoteapp-duplicate-session%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
