At the moment I am on self generated certificates, so cant help any further, but in the blog these bits may be worth reviewing?
*RemoteApp programs must be digitally signed* using a Server Authentication certificate [Secure Sockets Layer (SSL) certificate]. The certificate Enhanced Key Usage section must contain ‘Server Authentication (1.3.6.1.5.5.7.3.1)’. More details about the types of certificates used to digitally sign RemoteApp programs can be found here http://technet.microsoft.com/en-us/library/cc754499.aspx ALSO "*Note: The certificate for digitally signing RemoteApp programs on each RD Session Host server and RD Connection Broker server should be the same."* On Fri, Sep 16, 2011 at 4:16 AM, David Lum <[email protected]> wrote: > I did. The WebSSO one looks like it should work for me but I am obviously > missing something. I have a wildcard cert (*.nwea.org), the RDS server use > it, and all RDS settings reference servers with FQDN of .nwea.org (even > though the servers are in the internal.nwea.org domain)**** > > ** ** > > Dave**** > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
