RDS Web 2008 R2

Hello,
I am trying to publish a link via RDS web 2008 R2.
This is not a farm.
I follow the steps to publish calculator but when i open the RDSweb, the remoteapp Programs is empty.
Thanks for help

Hi,
Thank you for posting in Windows Server Forum.
Is there any update regarding your case. Have you check TPs suggestion?
In addition please go through beneath article and check the result.
Windows 7 / Windows Server 2008 R2: RemoteApp and Desktop Connection
http://blogs.technet.com/b/askperf/archive/2009/10/14/windows-7-windows-server-2008-r2-remoteapp-and-desktop-connection.aspx
Also to resolve this problem, add the RD Web Access machine account to the Windows Authorization Access Group on the domain controller.
You cannot view the "RemoteApp" programs that are on a RD Session Host server that is running Windows Server 2008 R2 by using RD Web Access
http://support.microsoft.com/kb/978322
Hope it helps!
Thanks.
Dharmesh Solanki

Similar Messages

  • Event ID: 1280 Server 2012 RDS - web app fail on second session host

    Hello there
    Topography
    SBS 2011 (domain controller)
    Two VM’s:
    VM1 – All RDS rolls: RD Gateway , Connection broker, Licensing and RD access installed and acting as a session host with an active collection for RD web apps. A CA trusted certificate is installed.
    VM2 – Session host with a second collection for RD web apps
    Problem
    I have a single app installed on both session hosts (the apps require their own servers). Both appear on the RDWeb site available for use.  I can run the app hosted on VM1 no problem, but when I try to open the second app hosted on VM2 I get
    two issues:
    An error is returned
    “Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address and the certificate subject name do not match. Contact your network administrator for assistance".
    When viewing the certificate, it actually shows the CA cert installed on the
    SBS server for RWW, not the cert on VM1. This has me puzzled
    Secondly on VM 2, I get
    Event ID: 1280 Warning Microsoft Windows TerminalServcies-session broker client
    Remote Desktop Services failed to join the Connection Broker on server sever-vm1.local.
    Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.
    When I run the app internally it seems to load but then disappears.
    Some further config info if it is relevant:
    I have port 4043 (443 used) as the only port directed to the gateway
    Am I missing something simple? DNS? Port forwarding issue on the router?  Its my first deployment of this nature with RDS 2012
    Regards
    MIS5000

    Hi,
    Thank you for posting in Windows Server Forum.
    Firstly please check the RDP version you are using. I suggest you to update to RDP 8.1 for better feature and functionality. Now other thing verify that you have the RD Gateway certificate name matches the external FQDN of the RD Gateway Server. Also please
    check that certificate is added under local computer\personal store and must be signed by trusted root authority. 
    Please check below article for more detail.
    TS Gateway Certificates Part III: Connection Time Issues related to TS Gateway Certificates
    http://blogs.msdn.com/b/rds/archive/2008/12/18/ts-gateway-certificates-part-iii-connection-time-issues-related-to-ts-gateway-certificates.aspx
    In regards to resolve other issue (Event ID 1280), identify and fix any connectivity problems between the RD Session Host server and the RD Connection Broker by doing the following:
    • Check network connectivity to the RD Connection Broker.
    • Start the Remote Desktop Connection Broker service. 
    • Add the RD Session Host server to the Session Broker Computers group.
    More information.
    Event ID 1280 — RD Connection Broker Communication
    http://technet.microsoft.com/en-us/library/ee890889(v=ws.10).aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • RDS Web access 2012 empty

    Hi,
    the RDS web became empty,
    I enabled logging in %systemroot%\web\rdweb\Web.config and the log being created in %systemroot%\web\rdweb\App_Data says:
    w3wp.exe Warning
    0 2014/10/24 16:37:58 [Warning] 35 Could not retrieve workspace info from the store, falling back to Web.config
    w3wp.exe Warning
    0 2014/10/24 16:37:59 [Warning] 53 Could not retrieve workspace info from the store, falling back to Web.config
    w3wp.exe Warning
    0 2014/10/24 16:38:02 [Warning] 44 Could not retrieve workspace info from the store, falling back to Web.config
    any Ideas?

    ok, so I solved it by just deploying the web access on another server

  • Opening ports in windows Web 2008?

    Is there a way to open ports in windows web 2008?
    i tried on firewall and didn't work.
    can someone help please

    Start here
    http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Configure-Windows-2008-Advanced-Firewall-NETSH-CLI.html

  • In Place Upgrade RDS sever 2008 R2 to 2012 R2

    Hi
    I have a single RDS server 2008 R2 running the roles of RDGM, RDLM, RDSHC, RDWAC an Remoteapp manager. I want to do a in place upgrade to Server 2012 R2. Is this a supported path? Are there any step by step guides available?
    Thanks
    Gus

    Hi Gus,
    Sorry for the delay.
    As TP suggested. Only RDG and RDL are supported for upgrading or migration. Other role are supported or upgrading or migration due to architecture changed.
    Regarding the guide for setting up RDS 2012, please refer to the following:
    Deploying the RDS Quick Start deployment type in Windows Server 2012 (for Session Virtualization)
    http://social.technet.microsoft.com/wiki/contents/articles/10421.deploying-the-rds-quick-start-deployment-type-in-windows-server-2012-for-session-virtualization.aspx
    Deploying the RDS Standard Deployment Type in Windows Server 2012 (for Session Virtualization)
    http://social.technet.microsoft.com/wiki/contents/articles/12180.deploying-the-rds-standard-deployment-type-in-windows-server-2012-for-session-virtualization.aspx
    Migration Guide for RDS WS2008 R2 RDSH Farm to WS2012 RDS Deployments
    http://social.technet.microsoft.com/wiki/contents/articles/17021.migration-guide-for-rds-ws2008-r2-rdsh-farm-to-ws2012-rds-deployments.aspx
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Adding favicon.ico to 2012 RDS Web page

    Trying to add a custom favicon.ico to our 2012 RDS Web Access.   I've tried putting it in C:\inetpub\wwwroot and C:\Windows\Web\RDWeb with no sucess.   Any ideas?

    Hello!
    I have same problem.
    I would like change favicon.ico in RD Web Access 2012R2, but i cannot do it. (I try
    https://msdn.microsoft.com/en-us/library/ms537656(v=vs.85).aspx#Create_the_Correct_Size_Icon
    http://www.html-kit.com/support/favicon/favicon-quick-guide/
    http://stackoverflow.com/questions/6296038/favicon-not-showing
    http://stackoverflow.com/questions/9963584/how-to-add-favicon-ico-in-asp-net-site)
    everything does not work.
    How can i change favicon in RD Web Access 2012R2?
    Thank you in advance!

  • Problems with Win 7 64 bits printer configuration on RDS Web Access

    hey All,
    I have a scenario with RDS 2012 with Session host in 2008 R2 SP1, and on clients with windows XP SP3 and win 7 SP1 32 bits, printer configuration looks ok  but in windows 7 64 bits it looks like a truncated configuration , i have been tested every solution
    that was reported before, like changing GPO, install Drivers in the clients and in the server, changed display resolution (to print in video) and nothing works, is any issue or incompatibility reported in this cases ?
    Thanks in advance
    Breno Andrade

    Hi,
    Thanks for posting in Windows Server Forum.
    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.
    If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. 
    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. 
    Thanks for your Support & understanding.
    Regards.
    Dharmesh Solanki

  • Win Srv 2008 R2 DC interfering with Win Srv 2012 R2 RDS RemoteApp functionality during program opening by any user

    I have a small LAN with a Win 2008 R2 SRV as DC, File Server and App Server for QuickBooks and QB POS, and a VMware 5.1 host that has three utility servers running on it. One of these three is a Win 2012 R2 SRV config'd with these RDS roles (RD Session Host,
    RD Connection Broker, RD Web Access, RD Licensing and RD Gateway) installed as a single server solution, simply because we're only servicing a few users. RDS roles were installed and configured before installing the MS Office 2013 and QuickBooks apps. I created a
    simple Collection and setup the RemoteApps for access.
    Initially I had only installed the RD Session Host, Connection Broker and Web Access. Installed the Apps, restricted access to only the RemoteApps and tested their ability to open via an internal connection from within the LAN in browser, minus the SSL errors
    and .local address everything worked fine when a user authenticated. I installed the Licensing component and activated it and the internal LAN connectivity continued to function. I then installed my single SSL cert and configured it for use in each requiring
    RDS role, opened port 443 thru my firewall to the RDS server and then began testing connectivity from external browser, at this point I initially encountered rights errors with my RDP users group, they were being denied logon access, it seemed
    the Win 2008 R2 DC is mixed in the middle of the auth cycle of course so I straightened out that problem via GPO. I then again attempted to login via external source and now could login and obtain access to the RDS Web Access page showing my RemoteApps
    BUT now when I click on an App to open it as either a user or Admin it attempts to Auth the process thru the Win 2008 R2 DC instead of directly to where the App is run from on the 2012 RDS server and gives me this error...
    RemoteApp Error: Windows cannot start the RemoteApp program. The following RemoteApp program is not in the list of authorized programs:
    Further details can be added to this but has anyone encountered this problem with a similar setup?
    Thanks
    NeoPaladine

    Yes, but thanks for bouncing all of the ideas.
    I saw that I was receiving Event Error 201 each time a failed RemoteApp load would occur, followed the trail for that and found the following that fixed it!
    http://blogs.technet.com/b/networking/archive/2010/01/14/remote-desktop-gateway-client-fails-authentication-with-your-user-account-is-not-authorized-to-access-the-rd-gateway.aspx
    Specifically this step:
    Solution 1
    Register the NPS server in Active Directory:
    In Server Manager, browse to the following location:
    Roles\Network Policy and Access Services\NPS (Local).
    Right click on the NPS (Local) node and choose Register server in Active Directory.
    Click OK to authorize the server when prompted.
    Once I registered as above the RemoteApp's loaded perfectly both internally and externally when requested.
    Thanks for leading me in the right direction!
    Brent
    NeoPaladine

  • RD Web access SSO - remote desktop doesn't work

    Hi,
    This is my first post in here, and I hope you gays can help me out.
    I am currently experiencing some issues with RD Web SSO not working as I would like it to work.  I have found countless articles and guides describing how to get it to work, but no guide have yet helped me.
    The problem is that when I log in on the web access and open a published application everything works fine I wait 5 sec and the application pups up, but when I try to open "Remote Desktop" then I get a new log in box where I must enter my log in credentials
    again (after entering my credentials everything work great.)
    The problems I am currently facing is produced in a demo environment configured as follows:
    1x DC server (DC01) also the lic server
    2x RDS server (RDS01/02)
    1x RDS Connection broker (RDCM01)   I have created a farm named "farm01.mydomain.com"
    1x RDS Web access server (RDWA01)
    1x RDS Gateway (RDSGW01)
    (All the Servers are installed with Windows server 2008 (R2) SP1, and have the latest update.)
    I am publishing my demo environment on the internet, i have created a domain name for my gateway and my web access and they are both accessible from the web (rdwa.mydomain.com and rdsgw.mydomaim,com). I also have secured everything with an SSL wildcard certificate
    ( my external and intern domain names are the same so I am using one SSl certificate) that is trusted on the web.
    when I  log in on the web access server trough (IE9 or IE8 ) from another network(wan) and I open a published application (calculator), it pop ups in just a few seconds. But when I try to open my Remote desktop I get a login box where I must enter my
    username and password one more time.. after that remote desktop opens and everything works great.
    My laptop is a Windows 7 professional with RDP 7 and IE 9, and is not member of a domain (just a workstation), I have tested it from multiple workstations and networks(Also win 7 and RDP7) but even there I have the same problem.
    Thinks that I have tried tell now:
    I have created a kerberos account as mentioned on
    MSDN
    I have checked my group permissions as mentioned
    here
    And many more blogs and forums
    I have tried multiple settings on RDCM, RDWA, RDSGW and RDS server
    Right now I am out of ideas, and I hope you gays can help me out..
    thanks in advance,
    Pouyan

    Thnx for you advise,
    Did you go into your RemoteApp Deployment settings and change the server name to the farm name "farm01.mydomain.com?"
    Yes
    Also in the Session Broker's RemoteApp and Desktop Connection Properties window change the Connection ID to the farm name as well.
    actually I couldn't find out what to put on the connection ID so I had left it just default, but after changing it to the farm name it still doesn't work
    Did you sign you apps with the cert used on your RDS servers?
    yes, I am using a wildcard ssl certificate to sign all the servers/apps with.
    there is
    something that
    strikes me, when I log on the web access and click on a published application (that is hosted from the same RDS servers) then I get a information box. when I click on the "details" button I see on the bottom "use the following credentials to connect" and my
    domain and username are published there. But when I click on the "Remote desktop" icon and do the same I can't see this information!!
    Also I don't think that its an SSL problem, because after log in again it works perfect without any warning.

  • RDS Farm certificate confusion

    Can someone clear up for me what exactly is needed for certificates in a RDS 2012 R2 farm environment? Yes I've read posts and documentation, but I am still unclear on a few things:
    Do the session hosts in a farm need their own public certificate even though everything is being passed through the connection broker?
    I have
    RDGW.internal.net (rdgw.external.com) - RDS gateway and RDS Web -- public certificate for rdgw.external.com
    RDCB.internal.net - RDS connection broker, RDS Licensing -- public cert for rdcb.internal.net
    RDSH1.internal.net - RDS host 1 -- certificate assigned from internal AD CA
    RDSH2.internal.net - RDS host 2 -- certificate assigned from internal AD CA
    The two public certs were installed through the session collection interface, and come up as trusted.
    Trying to connect from outside, I get an error 0x607 from RDSH1.internal.net.
    I am using free StartSSL certs to test. These aren't wildcard, and don't have Sub Alt names assigned. When everything is working, I'll request regular ones from our public CA. But I don't want to purchase one until I am sure what is needed and everything
    is working.
    Eventviewer on RDS1 and RDCB not showing anything helpful.
    B

    Hi,
    Thank you for posting in Windows Server Forum.
    In Windows 2012, you connect to the Connection Broker and it routes you to the collection by using the collection name.  
    The certificates you deploy need to have a subject name or subject alternate name that matches the name of the server that the user is connecting to. The certificate for RDWeb needs to contain the FQDN of the URL, based on the name the users connect to.  If
    you have users connecting externally, this needs to be an external name (needs to match what they connect to).  If you have users connecting internally to RDweb, the name needs to match the internal name.  For Single Sign On, again the subject name
    needs to match the servers in the collection.
    Please check below articles for RDS certificate requirement.
    1. Minimum Certificate Requirements for Typical RDS implementation
    2. Certificate Requirements for Windows 2008 R2 and Windows 2012 Remote Desktop Services
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Change DPI scaling inside RDP session (2008 R2 / 2012 R2)

    We have two servers:
    Server 2012 R2 RDS 
    Server 2008 R2 RDS
    Users are constantly reporting being unable to change their screen resolution. After some digging, the reason they're trying to change the resolution is because their text is too small to see. DPI scaling is obviously the answer, but when users go into the
    setting it is greyed out and cannot be changed.
    Now, for Server 2008 R2, I've found this link:
    http://support.microsoft.com/kb/2726399/en-us
    Does this hotfix actually do what I suspect/hope/blindly-pray it will do? Does it re-enable the DPI options if connected via RDP? The article doesn't actually say what it does, just that it will "fix" the issue.
    Next, for Server 2012 R2, I've found this link:
    http://blogs.msdn.com/b/rds/archive/2012/06/13/remote-desktop-services-what-s-new-in-windows-server-2012-release-candidate.aspx
    The second last section mentions "Support for Changing DPI in Remote Sessoins." Having logged into this RDS server, this is not the case, the setting is greyed out just like in Server 2008 R2.
    What needs to be done to get this working on both platforms? My end result is I want users to log in and be able to go into the preferences, move the DPI slider to their desired text size and fix their problem without resorting to workarounds like decreasing
    the resolution of their local PC to increase the apparent size of text.
    If this isn't possible, is there a way to configure RDS to run at a lower resolution permanently but to stretch to fit any screen resolution? Right now, if you drop the resolution on an RDP session, it just takes up part of the user's screen. In the newest
    RDP clients, I notice the Smart Sizing option, but it apparently isn't "smart" enough to stretch higher than the base resolution of the session.
    I've looked through literally years of forum posts and articles and nothing seems to point at a user-friendly fix such as take the slider, choose your size, done.

    Hi,
    For Windows Server 2008 R2, you may need to apply the Hotfix in your post.
    The DPI adjustment is not available in a Remote Session (RDP)
    http://support.microsoft.com/kb/2544872
    You cannot change the DPI setting through a Remote Desktop session on a computer that is running Windows 7 or Windows Server 2008 R2
    http://support.microsoft.com/kb/2726399/en-us
    However, when I remote to a Windows 8, Windows Server 2012 and Windows Server 2012 R2 machine, I have no such issue.
    Please check if your clients have the latest update for RDP installed.
    Resolution and Scaling Level Updates in RDP 8.1
    http://blogs.msdn.com/b/rds/archive/2013/12/16/resolution-and-scaling-level-updates-in-rdp-8-1.aspx
    Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1
    http://support.microsoft.com/kb/2592687
    Remote Desktop Protocol 8.1 Update for Windows 7 SP1 released to web
    http://blogs.msdn.com/b/rds/archive/2013/11/12/remote-desktop-protocol-8-1-update-for-windows-7-sp1-released-to-web.aspx
    Hope this helps.
    Jeremy Wu
    TechNet Community Support

  • Please Help! RDS not working over the internet

    Hello Everyone,
    I recently set up a new server that is running Server 2008 R2 and need to get RDS setup so that I can connect to the server using a remote desktop connection over the internet.
    I can access the web access site over the internet and login as expected but it does not allow me to connect via remote desktop to the server using its FQDN. It just gives me the typical can't connect message. I have verified that connecting via remote desktop
    using the RDS web access site works within my local network.
    So far I have done the following:
    - Added the server to the domain and assigned a static IP address that is public on the internet (associated dns record also added by my ISP)
    - Added all of the RDS roles except for virtualization host and added appropriate settings throughout the wizard
    - Configured and added a self-signed ssl cert
    - Added the server as a web access server
    - Disabled Firewall and Security software on the server for testing purposes
    That said, can anybody shed some light on what I may have missed? When entering the computer name over the internet, do I have to add a port or anything like that? It's odd that I can connected to the web access page which is hosted on the server I am trying
    to connect to via remote desktop but I cannot actually use remote desktop.
    This is my first time attempting to use RDS so maybe I just missed an important step somewhere.
    Any help with this would be greatly appreciated!

    I added the certificate to the PC I'm trying to connect from and I'm still getting the same error.
    This is what I'm seeing below, I figure pictures speak louder than words in this case.
    Under the Remote Desktop link:
    Connect to:
    Remote Desktop size:
    Options
    Devices and resources (followed by checkboxes for them)
    Additional Options
    Remote computer sounds:
    Apply keyboard shortcuts:
    Performance:
    When I click connect a warning comes up saying unknown publisher and when I click connect I get the error again.
    That said, I went into RD Session Host Server Settings and under the RD Session Host Server tab I checked a box that says "Show a remote desktop connection to this RD Session Host server in RD Web Access" and now under the
    remoteapp programs link on the RDWeb there is an icon for Remote Desktop. When I click the icon it automatically tried to connect me to the server and lists the publisher and remote computer as the same rather than giving me a warning.
    Additionally, in the RD Session Host Server Settings it does say the server name as the FQDN RDP port 3389 under "connection settings" in the same tab.
    edit: I am going to put together some pictures so you can see exactly what I'm seeing on the RDWeb and will post again with a link once I have them up.

  • Server 2012 R2 RDS- Only want the Session Host, Connection Broker and Licensing Server!

    Hi all,
    Wondering if anyone has experience with implementing Remote Desktop Services (RDS) on Windows Server 2012 R2.
    I am doing an RDS design for a platform where we only need an RDS Session Host, Licensing Server and Connection Broker. We do not need web access as these servers will simply be jump boxes internally!
    However, implementing this correctly in our test environment has proved to be tricky. The options are:
    Use the Server Manager and do a traditional install via Roles and Features ( specifically add the Session Host, Licensing Server and Connection Broker). The installation process seems to go through ok in this scenario but when I head over to the Remote
    Desktop Services section of the Server Manager I simply get the message 'An RDS Deployment does not exist in the server pool. To create a deployment head to Roles and Features'.
    Use the specific ‘Remote Desktop Services installation’ option on the Server Manager and do a Session Based Desktop deployment and Quick Start. This installation process seems to go through correctly and the Remote Desktop Section seems to be working
    correctly via the Server Manager. However this process is ‘hard locked’ i.e. it installs the session host, web access and connection broker. I can then remove the web access component later from Roles/ Features.
    Is there a best practice (if any) for installation? i.e. Will there be any issues down the line if I remove RDS Web Access from my server while following method 2?
    There is a complete lack of documentation from Microsoft here so not sure what to do! Just need a basic RDS session based deployment.

    Hi,
    As I know from server 2012\R2 the best deployment skill is to perform via “Remote Desktop Services” installation mode with Standard deployment and don’t let single role to install. Because when we install through RDS mode, there are specific extra tools and
    services activated along with that deployment which you can’t find with single role installation. And that is for sure, when we install RDS role as of this, by default we will get install RDCB, RDSH and RDWA role installed.
    Sorry don’t have any option to try to remove that role as that role basically needed for RemoteApp and Desktop purpose. But if you want then you can try it with help of “Remove-RDServer”Powershell command.
    https://technet.microsoft.com/en-us/library/jj215506.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • RDS Gateway 2012, RemoteApp Displays "A Revocation check could not be performed for the Certificate" via RDWEB

    I have searched through the forums and there are a number of posts that are similar but all the checks they list seem to not apply to this one.
    My current setup is as follows
    All Servers are 2012 R2
    1 x DC server
    1 x RDS Gateway server with RDS Web installed
    1 x Session Host Server
    Certificate supplied by godaddy with 5 names. (included is the name of the RDS Gateway/Web server in the certificate, the internal name of the session host server is not included as the internal names are differnet to the external)
    My tests are as follows
    Navigating to the RDSWEB page from a machine inside the same network (windows 7 sp1) but not on the same domain is fine no errors and logging in and launching any published application is fine with no errors.
    However logging in on another machine that is external from the network (windows 7 sp1) is ok up to the point of launching any of the published apps I get the error about ""A Revocation check could not be performed for the Certificate". this
    prompts twice but does allow you to continue and login and use the app till the next time. If I view the certificate from the warning message all appears to be ok with all certs in the chain.
    I have imported the root and intermediate certs to each of the gateway/rdsweb server and session host server into the computer cert store just to be on the safe side. This has not helped, I have also run the following command from both windows 7 machines
    with no errors on either
    certutil -f –urlfetch -verify c:\export.cer
    I cant seem to see where this is failing and I am beginning to think there is something wrong with godaddy cert itself somehow.
    If I skip rdsweb and just use MSTSC with the gateway server settings then I can login to any machine on the network with no errors so this is only related to launching published apps on the 2012 R2 RDWEB or session host servers.
    Any help appreciated

    Hi,
    1. Please make sure the client PCs have mstsc.exe (6.3.9600) installed.
    2. If you are seeing a name mismatch error, you can set the published name via this cmdlet:
    Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
    http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
    To be clear, the above cmdlet changes the name that shows up next to Remote computer on the prompt you see when launching a RemoteApp.  You should have a DNS A record on your internal network pointing to the private ip address of your RDCB server. 
    Additionally, in RD Gateway Manager, Properties of your RD RAP, Network Resource tab, you should select Allow users to connect to any network resource or if you choose to use RD Gateway Managed group you will need to add all of the appropriate names to the
    group.
    For example, when launching a RemoteApp you would see something like Remote computer: rdcb.domain.com and Gateway server: gateway.domain.com .  Both of these names need to be on your GoDaddy certificate.
    Please verify the above and reply back so that we may assist you further if needed.  It is possible you have an issue with the revocation check but I would like you to make sure that the above is in place first.
    Thanks.
    -TP
    Thanks for the response.
    To be clear I am only seeing a name mismatch and revocation error if I assign a self signed cert to the session host as advised earlier in the thread by "Dharmesh Solanki", if I remove this and assign the 3rd party certificate I then
    just get the revocation error , I have already ran the powershell to change the FQDN's but this has not resolved the issue although the RDP connection details now match the external url for RDWEB when looking at one of the remoteapp files. The workspace
    ID still shows an internal name though inside this same file. 
    RD Gateway is already set to connect any resource, when connecting using remote app both names (RDCB/RDGateway) show as being correct and are contained within the same UCC certificate. I also already have a DNS entry for the Connection broker pointing to
    the internal ip.
    Do you know if the I need the internal name of the session host servers contained within the same UCC certificate seeing as they are different fqdn's than what I am using for external access ? I resigned the UCC certificate and included the internal name
    of the session host server to see if this would help but for some reason I am still seeing the revocation error. I will check on a windows 8 client pc this evening to see if this gets any further as the majority of the testing has been done on windows 7 sp1
    client pc's
    Thanks

  • Windows 2008 R2 Terminal & Windows 2003 RDP Client

    Hi
    I have Terminal Server Windows Server 2008 r2 and Terminal Server Licensing Windows Server 2012 with RDS CAL installed and activated.
    I have the clients with Windows Server 2008, Windows Server 2003, Windows 7 and HP Neoware thin client CA21 with SO 5.0. On my client 2008, Windows 7 able to connect RDP but on the clients Windows Server 2003, and HP Neoware thin client CA21, when connect
    to RDP to Terminal Server 2008 r2 receive the error. "Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again".
    My question is, How to Fix this error? and able to connect RDP from my clients 2003 and HP thin client to Terminal Server.
    Thanks

    Hi,
    Thank you for posting in Windows Server Forum.
    Which version of RDP client you are using for your client systems?
    Please update to the latest available RDP client for machine.
    On RDS Server 2008 R2, please check following setting and verify. (Part 1 from below article) 
    1. Start the System tool. To start the System tool, click Start > Control Panel > System Icon and then click OK.
    2. Under Control Panel Home, click Remote settings. 
    3. Click the Remote tab. Under Remote Desktop, Select either option depending on your security requirements: 
       Select the option “Allow connections from computers from computers running any version of Remote Desktop (less secure)”
    4. Click OK and verify.
    Apart the issue may occur if a certificate on the terminal server is corrupted. Please try to
    delete the registry key for “X509 certificate” to verify. (Part 4 from below article) 
    You can get all above step by step guide from following article.
    Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
    http://support.microsoft.com/kb/2477176
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

Maybe you are looking for