none
UAG trunk Hostname = Public Published Website name RRS feed

  • Question

  • Hi,

    More of an observation really....

    I have created a new HTTPS and HTTP trunk, called one www.company.com the other secure.company.com

    Then, published a Sharepoint site per trunk, and the site's FQDN and Hostheader name is www.company.com and secure.company.com respectively.

    UAG did not complain on Activation.

     

    So suddenly it seems that the trunk FQDN name can be the same as the published website FQDN....I am sure it gave me errors last week.

     

     

    • Edited by D Wind Thursday, May 20, 2010 10:29 AM
    Tuesday, May 4, 2010 7:43 AM

Answers

  • Hi,
      Any application can share the trunk public host namespace as long as the path configured in the webserver tab does not overlap any of the paths required by UAG.  For example publishing sharepoint with a path of /team/site1 would work but publishing sharepoint with a path of / would not.  The / path overlaps the paths used by UAG and so would cause an error dialog to be displayed.

    There are several paths but the primary ones are as follows:
    /internalsite
    /secure*
    /FileSharing*
    /rpc
    /CertifiedEndpointEnrollment

    From a more general prespective, when publishing applications using aplication specific hostname , exchange, and sharepoint publishing the same applies and the paths used by these applications can not overlap but the external hostname may.  If the paths need to overlap multiple external hostnames must be used.

    Regards,
    Dan Herzog
    Microsoft CSS IAG/UAG Support

    • Proposed as answer by djh-msftModerator Friday, May 21, 2010 1:27 AM
    • Marked as answer by D Wind Friday, May 21, 2010 4:45 AM
    Friday, May 21, 2010 1:26 AM
    Moderator

All replies

  • Glad things are working out!
    Ben Ari
    Microsoft CSS IAG Support
    Sammamish, WA
    • Marked as answer by Erez Benari Wednesday, May 12, 2010 6:54 PM
    • Unmarked as answer by D Wind Thursday, May 20, 2010 10:20 AM
    Wednesday, May 12, 2010 6:54 PM
  • Ben, can you please confirm that this is a supported configuration?

    Trunk Public Hostname: www.company.com

    MOSS application published on that same trunk with a Public name of www.company.com

    it also just so happens that this MOSS app is the initial application, with a UAG webpart inside. 

     

    All this time I was under the impression that we needed a distinct trunk public hostname from any published application.

    Thursday, May 20, 2010 10:20 AM
  • Hi,
      Any application can share the trunk public host namespace as long as the path configured in the webserver tab does not overlap any of the paths required by UAG.  For example publishing sharepoint with a path of /team/site1 would work but publishing sharepoint with a path of / would not.  The / path overlaps the paths used by UAG and so would cause an error dialog to be displayed.

    There are several paths but the primary ones are as follows:
    /internalsite
    /secure*
    /FileSharing*
    /rpc
    /CertifiedEndpointEnrollment

    From a more general prespective, when publishing applications using aplication specific hostname , exchange, and sharepoint publishing the same applies and the paths used by these applications can not overlap but the external hostname may.  If the paths need to overlap multiple external hostnames must be used.

    Regards,
    Dan Herzog
    Microsoft CSS IAG/UAG Support

    • Proposed as answer by djh-msftModerator Friday, May 21, 2010 1:27 AM
    • Marked as answer by D Wind Friday, May 21, 2010 4:45 AM
    Friday, May 21, 2010 1:26 AM
    Moderator
  • great explanation, thank you djh
    Friday, May 21, 2010 4:34 AM
  • Just one last comment...you wrote: "If the paths need to overlap multiple external hostnames must be used"

    Thats what we did, however....there might be another issue with that which I posted on: 

    http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/thread/2bb5f3ef-f0a3-4ba0-a66f-88d4706381a1
    Friday, May 21, 2010 2:59 PM
  • Hi,

    We are using exact setup in our environment, so portal trunk uses same public hostname than Application.

    We we are testing this setup, let's call our portal hostname is www.company.com and application's public hostname is www.company.com

    We have deployed Sharepoint application, which is configured like following:

    Public hostname: www.company.com/pages/default.aspx .

    It somehow redirects user again to login portal while it should redirect user to Sharepoint application.

    We are using different IP's on external and internal DNS but same hostname.

    Any suggestions?

    -Snendis

     

     

    Monday, September 6, 2010 2:57 PM