RemoteApp disconnects

Hi,
I have Server A running 2008 R2 which is hosting the RD Web Access and Connection Broker roles.
I have Server B running 2008 R2 running the RDS Session Host role and RemoteApp.
I published WordPad and and an internal application to RD Web Access.
When my test user account logs onto RD Web Access, I can launch the Wordpad application fine 100% of the time. However, if I try launch the internal application it doesn't show. I noticed that my RDP connection status changes to disconnected. If I then launch
Wordpad, the connection becomes active again and also displays the internal application fine.
Any idea's on how to troubleshoot this?

take a look at the hotfix recommendations from this post
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ce44eb88-cbad-493a-a87d-a6494bc69a86/w7-sp1-rdc-updates-to-either-80-or-81-cause-lockups-when-running-applications-rds-server-2012-r2?forum=winserverTS

Similar Messages

RDS 2012 R2 - RemoteApp Disconnected

Hi RDS 2012 R2 Experts,
I would like some guidance here if possible
My setup is a follow.
1x 2012r2 with the following role, Broker, Web access, Gateway and License called RDS01
2x 2012r2 Session Host called RSH01 an RSH02
1x wildcard cert
I would like to my users to be able to either internal and external to use the same link, remote.mydomain.com since my internal domain is mydomain.local
What i have done so far.
Created a DNS Zone called remote.mydomain.com and added the following records there.
REMOTE, it points to web access server IP 192.168.1.31 ( same server for Gateway and Broker )
2x RDSFarm, one record points to RSH01 and the other to RSH02, 192.168.1.32 and 33
Gateway, the record points to 192.168.1.31 ( same servers as broker and web access)
Broker, the record points to 192.168.1.31 ( same servers as web access and gateway)
i have set the gateway manager the following
Edited the deployment RD Gateway to remote.mydomain.com
Installed the wildcert for all the roles, *.mydomain.com in all 4 roles
created Manage Local computer groups and added both RSH01 and 02, RDSFarm record, remote record, gateway record and broker record
linked the allowed resources with the policy and users ( also tried allow users to connect to any resources )
configure the gateway in the RD Gateway farm
Configured the IIS to
auto redirect
and the DefaultTSGAteway under Pages to remote.mydomain.com
Also I used the Set-PublishName (http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80) to change it to broker.mydomain.com
Now, the issue I have is, when users either internally or externally try to launch a RemoteApp they get the error.
RemoteApp Disconnected
This computer cant connect to the remote computer.
Try connecting again.
To overcome this error I did the following:
Set-PublishName to RDSFarm.mydomain.com ( it is using the round robin to get to the session host servers)
There is two problem with this setup.
I no longer can shadow the users under Connections in the broker ( it seems to be bypassed )
I get certificate mismatch due the servers names
What I would like to achieve is to fix both problems above.
Thanks for any advice in advance.
N0tl3_Bouya

Hi,
Thank you for posting in Windows Server Forum.
Initially check that you have applied external used FQDN of server under Server name in RD Gateway Deployment properties and used Bypass RD Gateway for local address.
Please try to perform the steps
• Create a new DNS zone, .COM to allow split-brain DNS (so that internal clients can resolve external names internally)
• Create a relevant DNS entry in the aforementioned zone to point to the RDS environment’s internal IP address
• Create a relevant DNS entry in external DNS to point to the firewall which is publishing RDS’s external IP address
• Use the following script to change the FQDN of the RDP files provided by RD Web Access / RemoteApp and Desktop connection feed
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
In addition, for shadow related issue you can use the server in administrative mode use mstsc /shadow command and check the result.
Detailed walkthrough on Remote Control (Shadowing), reintroduced in Windows Server 2012 R2
Hope it helps!
Thanks.
Dharmesh Solanki

RemoteApp Disconnected - Server 2012 R2

I have a single 2012 R2 Standard server setup with all the RDS roles (RD Gateway, Broker, Session Host, Licensing, etc). I am able to publish apps and connect just fine only if the clients have the following setting: Local Policies > Security Options
> Network security: LAN Manager authentication level - SEND NTLM response only. The default for windows clients is "Send LM & NTLM - use NTLMv2 sessions security if negotiated". In the past, I have just applied this setting to all the clients
via GPO. However, this server will have primarily external users that are not a part of this domain. What setting(s) can I changed on the RDS server to prevent me from having to make any changes on the client's computers?

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check that you have configures RD Gateway setting properly. You need to configure RD RAP and RD CAP properties. After creating the RD RAP, add the user groups that you defined in the RD CAP. Also, create a new RD Gateway-managed computer group
that contains both the NetBIOS names and the fully qualified domain names (FQDNs) of the RD Session Host servers or the RD Session Host server farm that hosts the RemoteApp programs.
As you are using RD Gateway, you need to open TCP port 443 and UDP port 3391 and forward them to your RD Gateway server. Because when external client launches RemoteApp they will connect to RD Gateway via above port, then RD Gateway connect to your internal
RDSH server using TCP and UCP port 3389.
Please check below articles for reference.
Checklist: Make RemoteApp Programs Available from the Internet
http://technet.microsoft.com/en-us/library/cc772415.aspx
In addition also suggest you to update client RDP version to RDP 8.1 for better feature and accessibility.
Hope it helps!
Thanks.
Dharmesh Solanki

RDP Session Disconnect/Reconnect when RemoteApp is in Not Responding State (Server 2012)

Some of our applications running in our RDS environment tend to enter the Not Responding state while they're waiting for something in the background to happen (open a window, perform a calculation, etc.). When this happens we notice that the RemoteApp session
will quickly disconnect and then reconnect. This causes an issue with dialog boxes. For example, printing to PDF. A lot of time the dialog box for specifying where to save the PDF is in the background because RemoteApp disconnected and reconnected
causing the program your printing from to become the window of focus. This makes user think the program is truly not responding when in reality the dialog box is hidden and waiting for them. They then need to click the icon on the taskbar to access the
dialog window.
To my knowledge we never had this issue with Server 2008 R2. Any help with this is greatly appreciated!
Scott

Hi Scott,
Is the server 2012 R2?
Please confirm in the logs that a disconnect/reconnect is occurring. On the client you would look at TerminalServices-ActiveXCore and on the server side you would look at TerminalServices-LocalSessionManager.
When this happened you had a continuous ping to the server and it did not lose any pings?
Having solid pings is a good sign, but you can still have a network problem that will cause the connection to drop. You may want to update the NIC driver and firmware to the latest version recommended by your server manufacturer.
Additionally you should consider any routers/switches/etc. that are between the clients and the server as potentially suspect. For example, I have seen where a NAT router would drop a connection periodically, then the connection would be re-established
and not have issues (until the next time). One way to test would be to swap in a different make and model router/switch and see if the problem still exists.
Thanks.
-TP

RDS 2012 R2 RemoteApp Server Name Mismatch

Hi All,
I wonder if someone can scratch my head on this.
Brand new RDS 2012 R2 deployment.
RDS01 with Connection Broker and Session Host Roles installed
RDS02 with Web Access and Gateway roles installed
one ssl certificate with one domain remote.mycompany.com
the certificate have been imported to all the servers via the Edit Deployment
the local domain is mycompany.local
the problem that i am having is that when i launch RemoteApp after login in the remote.mycompany.com externally, i get Certificate mismatch, because it is contact the local name of the Session host server RDS01.
What i tried so far.
Used the Set-PublishName (http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80) without success
Try to configure RDS01 certificate via (http://ryanmangansitblog.wordpress.com/2013/03/10/configuring-rds-2012-certificates-and-sso/)
Check Any resources ( http://social.technet.microsoft.com/Forums/en-US/d1b0ebe4-9e53-47ff-8c75-43fd91ff538a/windows-2012-rds-certificate-mismatch?forum=winserverTS)
Has anybody out there could shade me some knowledge in how to rectify the mismatch name warning.
Thanks
Elton

Hi -TP,
Answering your queries.
1_the Set-RDPublishedName was successful, restarted the servers, refreshed the RDWeb page externally, tried to connect unsuccessfully.
2_I am using externally windows 8 and internally 7 fully updated
3_it had the green successful message.
After, set-rdpublishedname command, i get an erro when try to connecting saying, RemoteApp Disconnected.
Error:
Remote desktop cant connect to the computer "remote.mycompany.com"
1)Your user account is not listed in the RD Gateway Permission ( not true, it was set for domain users and my test user is under that group)
2)you might have specified the remote computer in netbios format or ip
Do you reckon i am having this problem because the RDS01 with Connection Broker and Session Host Roles installed?
Cheers
Elton

Certificate error when connecting to RemoteApp outside of private network

I have a server running Windows Server 2012 R2. It is configured as an all-in-one RDS server - all roles are installed on it. We've configured it primarily to use an application as a RemoteApp - the application is hosted at a different site, and this RDS
server is at that site. We have a site to site VPN set up, so that it is all a part of our domain. The issue I'm having seems related to the fact that our internal network is .local, but the certificate only has a single .com name, so that we can access it
from the Internet.
Everything works, though what I'm trying to clear up is a certificate error. When connecting to the RemoteApp from outside of our private network, we get the error "The server name on the certificate is incorrect." This occurs after entering
credentials. The public name of the server (rds.contoso.com) is different from the private name (server.contoso.local). We can proceed through the error and connect (though we'd like to fix it).
I implemented a fix that I found elsewhere to try to fix this. This was to add a custom RDP setting like so:
Set-RDSessionCollectionConfiguration –CollectionName QuickSessionCollection -CustomRdpProperty "use redirection server name:i:1`nalternate full address:s:rds.contoso.com"
That seemed to make some progress, then we got another error. I made a change to the RD RAP in RD Gateway Manager - by default, it allowed access to Domain Computers (which rds.contoso.com did not exist as a domain computer). I modified it to allow
access to the rds.contoso.com name.
I now receive a different error message and that's where I'm stuck. The heading on the message is RemoteApp Disconnected. The text of the error is 'Remote Desktop can't find the computer "rds.contoso.com". This might mean that
"rds.contoso.com" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.'
Any thoughts on what I can do next? When I roll back the changes I've made, I'm again able to connect fine, I just have the certificate error again.

Hi,
1. For changing the published FQDN I recommend you use Set-RDPublishedName cmdlet instead setting a custom rdp property on the collection:
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
2. As you mentioned before you need to edit the RD RAP so that the FQDN that you are using is permitted, or set it to Allow users to connect to any network resource.
3. On your internal network (internal to the RDG), you need to create a DNS A record for the published FQDN (rds.contoso.com) that points to your server's private ip address.
I'm not sure how you have things configured right now in terms of network and DNS so it is tough to give you instructions on how to fix. Let me explain a bit. Normally with a VPN you would not need RD Gateway, although it is okay
if you want to use it. If you have things configured properly an external client will normally connect to the RDG using the FQDN specified for RDG, then the RDG will connect to the published FQDN for the RDS deployment.
In your case these two FQDNs would be the same, only when the client does a DNS lookup it should get the ip address that you want users to connect to for the RDG whereas when the RDG does a DNS lookup it should get the private ip address of the server.
Exactly how you need to configure your DNS entries will depend on your VPN and networking configuration.
Please give it a try using the information provided above and reply back here with your results and any further questions you may have.
Thanks.
-TP

Remoteapp rdweb connection problem

I've published some apps with RemoteApp from my 2012 R2 RDS server. I don't have a Gateway server installed. I have a number of Windows 7 desktops which I'm connecting from, using IE9, IE10, IE11. When I use web access by going to
<RDS Server IP>/rdweb from some of the PCs and launch a RemoteApp application it works fine. However, from a number of my other desktops I get an error popup "RemoteApp Disconnected. The remote computer could not be found."  At
first I thought it might be IE version, but I have two different IE9 desktops and one works and the other doesn't. Same for IE 10. I know that IE11 has some problems with rdweb. I have compared the different desktops and can't find a reason
why some are working and some are not. I've checked firewall settings, IE settings, DNS entries, AD Computer objects, network settings and as far as I can determine the machines are configured identically. Cleared the IE caches on both. Logging
in with the same user. I'm at my wits end why some of these machines (which are all identical Dell 745s) will not connect.   All the postings I've seen about this error have said it is caused by bad Gateway server configurations, but I'm
not using a Gateway server, and that doesn't explain why some of my machines work fine.   Any help in troubleshooting this would be appreciated.

Hi,
1. On the problem PCs, when you click to launch a RemoteApp there should be a prompt with a name listed for Remote computer. Are you able to ping this name from the problem computers? Is the same ip address being returned as on the working
PCs?
2. Are you able to open Remote Desktop Connection from a problem PC and connect to the name that shows on the prompt?
3. Does the prompt show Gateway server with a name next to it? Based on what you have said Gateway server should
not show up in the prompt when launching a RemoteApp.
4. Please verify that mstsc.exe version 6.3.9600 is on the client PCs. 6.3.9600 is the RDP 8.1 Client which is what you should be using with Server 2012 R2.
5. If you have any third-party security/antivirus/antimalware/etc. installed on the problem PCs please try completely
uninstalling it on one of them and them test again to see if the problem still exists.
6. On the problem PCs please make sure they have the same subnet mask, default gateway, dns servers, etc. as the PCs that are working. From what you have written I believe you have already checked this but I wanted to mention it because I have seen
people check a ton of stuff and then realize the PC was on a different subnet or other basic networking issue.
7. On the server, please check the incoming Remote Desktop rules in Windows Firewall with Advanced Security (wf.msc) to make sure their Scope is set to Any remote ip address.
IE 9/10/11 works fine with 2012 RD Web.
Thanks.
-TP

TSGateway RD CAP/RAP corrupt

Server 2008 r2 running RDS & remoteapp, was functioning fine until a session was hung & i reset it thru RDS manager.
After the reboot of the server, user access has been denied "RemoteApp Disconnected" error msg.
THe RD CAP now has no user groups & i cannot add the user group back, or any other group for that matter.
THe RD CAP & RAP have become corrupt, I cannot add a user group to the Policy. I have deleted the RAP & CAP but still cannot add user groups on re-creation.
Is ther a way to reset the RD CAP/RAP?

I came across your post while having the same issue with a customers RD Gateway, a bit late for you but hopefully this helps someone else.
Rename the rap.xml at the following location and attempt the reconnect with your local RD Gateway.
%windir%\System32\tsgateway\rap.xml
Rebuild your RAP as needed once your reconnected
Thanks,
Chris Harvey
Thanks, Chris Harvey

RemoteApps still reconnecting to disconnected sessions, disableconnectionsharing:i:1 changes nothing.

I have a scenario where multiple users run a 2008R2 remoteapp, and they all use the same windows credentials. Multiple sessions is enabled, and I have it set to immediate logoff when the remoteapp is disconnected, and set to 1 minute logoff (the
minimum) when any remote desktop sessions are disconnected. In the remoteapp manager I have disableconnectionsharing:i:1 keyed in the custom rdp settings box, and I have this set in the icons as well.
With all this in place, users should never be rejoining anyone else's sessions. I thought it was all working fine until users started complaining that they were rejoining other people's sessions, and feared that users could possibly rejoin to their own.
I tested a bunch of scenarios and I can make it happen. If User1 x's out of his session, logs off, or closes the app, it logs out the session just fine and can never be rejoined. But, if he loses his internet, or for some reason the connection
is severed such as someone pulled his ethernet cable out, it will put the session into a disconnected state. This disconnected session is supposed to log itself off after 1 minute, but doesn't always. I can't make this happen myself, but I've seen
sessions that are there and they never go away. But the real problem is, when there is a disconnected session still left there, User2 logs in and it joins to User1's session for him. Even though I have disableconnectionsharing:i:1 in the rdp settings,
and in the rdp icon itself, it still reconnects the existing session every time. What am I missing here?

I've done a lot more testing, and on multiple servers, so it's not just this one server. In the local policy under Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session
Time Limits, I have the following;
Set time limit for disconnected sessions - "Enabled" End a disconnected session "1 minute"
Terminate session when time limits are reached "Enabled"
Set time limit for logoff of RemoteApp sessions "Enabled" "Immediately"
These settings work well, and they usually log off the sessions within one minute. It's not perfect 100% of the time, I've seen sessions that never end before, but it's good enough. Let's just say it works 99% of the time. The problem isn't
that sessions don't close, the problem is that you can rejoin ANY disconnected session even though the icons are set to always start a new session. The session time limits should keep this to a minimum since the users only have a 1 minute window to reconnect
to a disconnected session, but it is still 1 minute, and a reconnect will happen eventually given the amount of people that connect to this server.
My rdp icon (edited with notepad) has the setting disableconnectionsharing:i:1
The server's custom rdp settings has disableconnectionsharing:i:1
If there is a disconnected session lingering out there, it may be only for a minute, but if anyone connects to the server within that time, it ALWAYS takes over that existing session. It is my understanding from Microsoft, 3rd parties, and forums, that
this disableconnectionsharing setting is supposed to eliminate this issue. That's it's whole purpose. But it does not actually do anything. It changes nothing. What is it used for then?
Maybe I'm using the wrong setting. If so, what is the proper setting so that when you log in remotely, it will always start a new session?
Dave

RDS and Gateway issues: Cannot get remoteapps to run without opening port 3389 on firewall

I am testing the setup of a small RDweb server to host QuickBooks for some remote sales users (4 users). For the most part, I have everything installed on one virtual server (using 2012r2 "Quick Start" session host deployment with the additional
Licensing and Gateway server roles added to the same server).
Everything works excellent with one exception. External clients cannot launch published apps without having port 3389 open on the firewall, even with the gateway role installed and the 'Deployment Properties' set to use the gateway. They can properly connect
to the RDweb site and view the published apps. The only way it works is open the firewall port (at which time I can disable the gateway or leave it configured and it works either way). Internally, everything works accordingly. I have followed the steps outlined
on many sites and have combed though the forum here to no avail.
Error received (summarized but is a well documented error):
remote desktop can't connect to the remote computer: 1- Your user account is not listed (it actually is) or 2- You might have specified the remote computer in NetBios format . . etc.
This is an existing SBS 2011 environment with additional virtual servers setup to host QuickBooks as outlined below:
Current setup:
Used Quick Start to install Remote Desktop Services in hosted sessions mode
Installed the additional roles for Licensing and Gateway server on same server
Configured wild card public certificates on all four services (Connection Broker(2), Web Access and Gateway)
Configured internal DNS to properly lookup our external FQDN of this server (ex. quickbooks.contoso.com points to quickbooks.contoso.local
One thing I noticed (just now) when I launch a published app and the firewall has port 3389 closed, a dialog box pops up directly after launching the app that warns about running a RemoteApp program and mentions the Remote Computer and the Gateway Server
as both the same (which it is); however, I would have assumed one would have listed the internal server's name while, instead, both are listed as the external FQDN. Either way, internal DNS should still allow it to properly route . . no? I don't know . . I'm
sure I am just missing something in a routing configurations somewhere. The gateway service is not properly looking up the RDweb service and then seeming not routing the encapsulated RDP session through HTTPS. . .. is my guess . .
I was reading about the "set published name" commandlet; however, I am not experiencing a certificate name mismatch; however, the certificate name does show up as *.contoso.com versus the actual name. I may just be grasping as straws now . . :)

Ok, while I was in the server and looking over the BPA scans: "The Remote Desktop Gateway (RD Gateway) server Secure Sockets Layer (SSL) certificate may not have a valid certificate subject name." This may be due to it showing up as *.companyname.com
versus quickbooks.companyname.com. Anyhow. .. on to the list of actions above:
Changed RD RAP from "Select Active Directory" group to "Allow any network resource" and tested with port 3389 closed on firewall:
Worked. Initially it did not as I had used a custom shortcut created from earlier; however, after logging into the RDweb site again, the application loaded fine now (after the RD RAP change)
No error message appeared; however, I did notice that for a split second, the word Error did appear in the browser's tab title, but only very shortly. The app launch does take a bit longer too now (about 10-15 seconds, up from about 4 seconds with the port
open). This, I could care less about so long as we are properly forwarding the traffic through the gateway.
As for log entries, I had spend quite a bit of time in there and only had minor issues with loading user profile setting taking too long and policy settings preventing the redirection of USB devices. Looking again, no issues still. Just a bunch of informational
entries where I would connect before (and disconnect) but only with the port on the firewall open; otherwise, there was not an entry corrolating to when I would receive an error before. Now though, I am connecting after the RD RAP change and logs are showing
connections even with the port closed. These are in "operational", the "admin" log only shows the update to the RD RAP configuration.
Yes, the LAN's DNS server does relay the lookup information for my public FQDN as the local LAN address. No need for a local host record.
I have now added a new rule in our firewall to allow and forward UDP port 3391 traffic to the internal server hosting remote services
Thank you very much for your assistance on this matter. The RD RAP rule was default built during the creation of this services. Why is the resource not cross-referencing AD security groups? I could have sworn I created a group for that . . .

How to add Short cut to DISCONNECT and LOGOFF

We have an App that requires Remote Desktop Services
Having installed & configured it.
We asked the software company to setup App. This work fine in Desktop session i.e users login via mstsc and get presented with a desktop. But unfortunately not as a Published App.
Users will only run this one App on the Terminal Server (I was hoping the published App would work to keep things simple!
So if we have to use a Desktop I need to place a couple of items on the Taskbar
(1) Sign-Out
(2) Lock
(2) Close / Disconnect
I have taken away the Server Manager - yikes why would anyone think users should be able to access that!
anyone know what functions / programs to call or if this can be done with scripts ?
ChrisS

Hi,
To be clear, the application is not compatible with RemoteApp?
For sign out, you can create a shortcut to logoff.exe
For Lock, you can create a shortcut to rundll32 user32,LockWorkStation
For disconnect, you can create a shortcut to tsdiscon.exe
If you must use a full desktop you can lock things down/simplify using group policy settings as well as make it so that the user is automatically logged out when the application closes. One way is to have a custom windows program that runs automatically
at log on, launches the application, waits for the application to close, and then runs logoff.exe. This custom windows program can be hidden to the end user. It is pretty easy/quick to write if you know a little programming. Another alternative
would be a script that does the same thing.
-TP

Slowness when connecting to RemoteApp configured in Windows 2008 R2 Server using RDP file

Dear All,
When connecting to a RemoteApp configured in Windows 2008 R2 with less privileged user it takes ~20 seconds to connect.
Initial connection to
application takes about 20-30 seconds and once loaded, subsequent RemoteApp connection takes
2-3 seconds. i.e. if there is a disconnected session available in the server it connects quickly otherwise it takes long time.
I am seeing this issue with Windows 2008 Server, when I connect to a Windows 2012 Server RemoteApp gets
connected quickly. Also if I try with higher privileged user (like RemoteAdmin) connection is quick. The user I am trying is having lot of group policies set to limit user access to file system, desktop and registries.
If I keep UAC settings to minimal level connection happens quickly(i.e. solves this issue). But I am
not supposed to change the server UAC setting. It seems this has something to do with the list of group policies set for the user.
Any suggestion to avoid this first time connection delay for less privileged users for connecting to RemoteApp (in Windows 2008 Server).
Thanks
Bachuu

Hi Bachu,
Thank you for posting in Windows Server Forum.
First of all, if you are using RD Gateway serve then I would like you to
uncheck the “Bypass RD Gateway server for local address” under RemoteApp Manager Checkbox and notify the result.
Configure Remote Desktop Gateway Settings
Also like you to update the RDP client version to RDP 8.1 and then check the result. In addition,
I will suggest you to check that you have proper certificate in place. You can enable certificate revocation checking on RD Gateway client. Might due to this, you are facing issue. Please notify that you find any certificate related warning. Refer below article
for information.
How to Enable Certificate Revocation Checking on a Remote Desktop Gateway Client
Hope it helps!
Thanks.
Dharmesh Solanki

IOS RD Client not working for RemoteApp

This worked great for us, up through the past few releases. Nothing changed on the configuration of our server (2008 R2 SP1), but now we get log errors of "Server Error in '/RDWeb/Feed' Application" and "The resource cannot be found. Description:
HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly."
As noted, our RDS server is a single 2008 R2 SP1 server (fully patched) using RemoteApp. Logging in via the RemoteApp RDWeb site works perfectly fine, but via iOS it only shows 3 of the 12 published applications (all 3 will launch). It
USED to show them all. There does not seem to be any logic behind why it will show just those 3 and not the others, in terms of path, user groups, etc.. Some of the error(s) I'm seeing in the iOS log are as follows:
Requested URL: /rdweb/feed/rdweb/feed/webfeed.aspx
(Not sure why iOS is repeating the path, but the webfeed.aspx is located in C:\Windows\Web\RDWeb\Feed)
Also,
[2014-Jul-11 15:53:17] RDP (0): Exception caught: Exception in file '/Users/build/jenkins/workspace/rc-ios-develop/protocols/RDP/librdp/librdp/private/tlsendpoint_securetransport.cpp' at line 136
    User Message : TLS1_ALERT_ACCESS_DENIED
[2014-Jul-11 15:53:17] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Jul-11 15:53:17] RDP (0): correlation id: 48e2bf22-021e-114b-b675-cda011ce0000
[2014-Jul-11 15:53:17] RDP (0): Resolved 'siteurl.com' to 'serverIP' using NameResolveMethod_Unknown(0)
[2014-Jul-11 15:53:17] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Jul-11 15:53:17] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Jul-11 15:53:18] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Jul-11 15:53:18] RDP (0): Server supports RAIL
[2014-Jul-11 15:53:19] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Jul-11 15:53:38] RDP (0): Error message: Server set error condition: ''
[2014-Jul-11 15:53:38] RDP (0): Disconnect initiated by server
[2014-Jul-11 15:53:38] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Jul-11 15:53:43] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Jul-11 15:53:43] RDP (0): Exception caught: Exception in file '/Users/build/jenkins/workspace/rc-ios-develop/protocols/RDP/librdp/librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -9806
Also, FYI, the account with which I am trying to log in has full admin rights on the computer and in the domain.
Please help!
Thanks,
Mike

Hi Mike,
Thank you for posting in Windows Server Forum.
Cause:
The problem occurs if the URL that is specified in the Microsoft Internet Information Services (IIS) metabase contains a trailing backslash.
To resolve this problem, remove the trailing backslash in the IIS metabase for the URL that is specified for the affected Web application. Please check below Kb article (KB article is old but you can refer and check whether it resolved your issue).
KB 894670
Hope it helps!
Thanks.
Dharmesh Solanki

RemoteApp 2012 - Optimize connectivity

Dear gents,
Here is the setup:
Session-based deployment
RDCB01.domain.local - Connection Broker
RDGW01.domain.local - RDWEB + RDGW roles located in DMZ.
DC01.domain.local - TS License server
FILE01.domain.local - central HOME drive and PROFILE (folder redirection) store.
Two RemoteApp Collections:
RDSH01-04-.domain.local (RD_FARM_01.domain.local)
RDSH10-16.domain.local (RD_FARM_02.domain.local)
I`m using a TLS certificate remote.domain.com from a public PKI for:
RDCB - Publishing
RDWEB
RDGW
And a self-signed TLS certificate *.domain.local (customer has no internal PKI) for:
RDCB - SSO
RDSH - Remote Desktop Connections
There are client-side GPOs in place, as per the documentation, to allow the credential delegation to the RDCB and RDGW servers and the self-signed certificate enrollment.
On RDGW I`m allowing only HTTP on default port, to limit the network firewall requirements.
Full folder redirection is in place to a network storage on FILE01.domain.local
Questions:
#1 An active RemoteApp intermittently disconnects and immediately reconnects (x minutes of inactivity), causing some discomfort for the users. There are no Active session timeouts and I have the GPO setting for Keep-Alive set to 10 minutes.
#2 The thing that puzzles me is long (~15 seconds) wait till I can see that the RDSH server initiates the user logon process. I can`t find errors on either RDCB or RDGW eventlog, of something being wrong. All I can see is successful handshakes. The reason why
I wondering if this is *ok*, is `cause my colleague has built an analog and it takes around 5 seconds to start to load. In both cases we are talking of decent infrastructure, good connectivity on national scale and access is via Web-interface.
#3 What do I need in order to allow the UDP support on RDGW network-wise?
UDP_3391 FROM:INTERNET_ANY TO: remote.domain.com
UDP_3391 FROM:remote.domain.com TO: RDGW01.domain.local
UDP_3391 FROM: RDGW01.domain.local TO: ???

UDP info:
http://blogs.msdn.com/b/rds/archive/2013/04/09/get-the-best-rdp-8-0-experience-when-connecting-to-windows-7-what-you-need-to-know.aspx
you need to ensure you setup the GPOs properly to use the added UDP enhancements after you configure your firewalls.
also ensure users are using the latest RDP Client on their workstations to get the best functionality.
regarding keepalive settings, you need to ensure the timeouts on the RDSH go hand in hand with your keepalive settings on your switches/firewalls for RDP traffic to ensure they're not getting cut off, this is really sensitive.

RDS 2012 - Hide Server Resources in RemoteApp

Hello RDS experts! I am struggling with what should be a simple solution with RemoteApp. Here is my challenge:
I am sharing Internet Explorer from an RDS server to users. I have a number of web applications that users cannot access either because of browser incompatibility or browser security settings, so I want to funnel them through RD Gateway
and RDS to a Remote App.
I have the Gateway configured corrected and the internal RDS server as well, but I'm struggling with getting the correct user experience.
The users are going to need to save files and I want them to be able to save the files back on their remote machines without any hassle. I understand from previous forum posts that mapping their remote drive "as the C: drive" just doesn't
really work, but there's got to be something that I can do to hide the server drives.
I have tried the below articles:
http://support.microsoft.com/kb/231289
http://social.technet.microsoft.com/forums/en-US/75f72254-7ea0-43ce-91d9-ea2e333f7052/saving-files-from-a-remote-app-appv
http://blogs.msdn.com/b/rds/archive/2011/05/26/how-to-restrict-users-from-accessing-local-drives-of-an-rd-session-host-server-while-using-remoteapp-programs.aspx
None of these seem to work with 2012 R2...or maybe it's just specific to the "Save As.." menu coming from IE. Maybe if I had a full blown Windows Explorer (or now "File Explorer") then it would work right.
Can anybody shed any light on this, please be specific to the 2012 R2 implementation? Or is there an easier way to do it? I looked at user profile disks, but that seems like a bad option for me because I want the users to have their files once
they are offline and disconnected from me...
Please help!!

Okay, I made some progress. I can now hide the Network, Library, and Favorites links on the left-pane using the registry instructions below:
http://discussions.citrix.com/topic/266828-disable-librariesfavourites-in-opensave-dialog-for-applications/
I have attached a picture of my current "Save As..." dialog. I would like to get rid of the "Folders" view here.
None of those 3 articles addressed how to do that. As I mentioned, the goal is simply to direct the users to save files on their local disk. I am fine with pointing them towards using the mapped disks from their pseudo-RDP session.
Also note this question only applies to RemoteApp sessions. I am doing a full blown RDP desktop.
Thanks for your continued help!

RemoteApp disconnects

Similar Messages

Maybe you are looking for