locked
Post SP1 issue with Generic Browser-Embedded Application (multiple servers) RRS feed

  • Question

  • One of the applications that we publish via UAG utilises the Generic Browser-Embedded Application (multiple servers) application type.

    The implementation is very similar to the following blog post by Ben Ari:

    http://blogs.technet.com/b/ben/archive/2009/04/04/configuring-a-clickonce-application-using-iag.aspx

    Since installing SP1, when the application is launched, UAG returns the following message to the user:

    "The destination specified in the URL cannot be verified."

    Interestingly enough, if we manually type the URL of the application that we were trying to launch (ie The URL that appears after the TARGET parameter) in the browser, the application works correctly.

    Has anybody else experienced this issue post SP1?

    Thursday, December 9, 2010 6:29 PM

Answers

  • Hi Benjies,

    I wrote the blog post quite a while ago (before UAG, in fact), and I was not aware that SP1 breaks it this way. I'll do some testing in my lab, but even if it indeed breaks this method, I'm not sure if I can help , as this is not an official solution. I'll check and see if I can do anything.


    Ben Ari
    Microsoft CSS UAG/IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Wednesday, December 22, 2010 11:58 PM
    Tuesday, December 14, 2010 12:36 AM
  • Hi Benjies, everyone.

    I have confirmed that UAG has a new function that blocks this publishing method, and this is no longer possible to do. If this functionality is important for you, please open a support case with Microsoft CSS, which will allow us to devote more resources to investigating this and possibly finding a solution.

     


    Ben Ari
    Microsoft CSS UAG/IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Thursday, December 23, 2010 1:04 AM
    Thursday, December 23, 2010 1:04 AM

All replies

  • I have been able to get the embedded application to launch correctly within a browser by appending the WhaleFirstActivation=true parameter to the end of the URL in the Application URL.

    Referring to Ben's blog, I changed the URL from:

    http://localhost1:6001/internalsite/redir.asp?TARGET=http://somehost/somepath/publish.htm

    to

    http://localhost1:6001/internalsite/redir.asp?TARGET=http://somehost/somepath/publish.htm?WhaleFirstActivation=true

    Unfortunately, this workaround is not ideal but we can live with it. For example, if a user closes the tunneled connection and then tries to relaunch the application from the portal, the launch is not successful and even worse, the application does not get tunneled. The fix is to this is to get the user to log out of the portal, log back in then relaunch the application.

    Friday, December 10, 2010 12:19 PM
  • Hi Benjies,

    I wrote the blog post quite a while ago (before UAG, in fact), and I was not aware that SP1 breaks it this way. I'll do some testing in my lab, but even if it indeed breaks this method, I'm not sure if I can help , as this is not an official solution. I'll check and see if I can do anything.


    Ben Ari
    Microsoft CSS UAG/IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Wednesday, December 22, 2010 11:58 PM
    Tuesday, December 14, 2010 12:36 AM
  • Hi Benjies, everyone.

    I have confirmed that UAG has a new function that blocks this publishing method, and this is no longer possible to do. If this functionality is important for you, please open a support case with Microsoft CSS, which will allow us to devote more resources to investigating this and possibly finding a solution.

     


    Ben Ari
    Microsoft CSS UAG/IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Thursday, December 23, 2010 1:04 AM
    Thursday, December 23, 2010 1:04 AM