locked
SharePoint publishing using host-named site collections RRS feed

All replies

  • Hi Marcus,

    publishing AAM'ed sharepoint websites is supported by UAG.

    But keep in mind that a single trunk can only support a single domain name (e.g. http://customer1.contoso.com, http://customer2.contoso.com). If you like to publish http://www.customer3.com in addition you need to deploy a second UAG trunk...

    -Kai

    • Proposed as answer by Kai Wilke Sunday, September 11, 2011 6:18 AM
    • Unproposed as answer by MarcusB Sunday, September 11, 2011 3:39 PM
    Saturday, September 10, 2011 5:07 AM
  • Hi Kai,

    thx for the answer, but I'm not referring to AAM'ed sites. With host named site collections you don't/can't define AAM - or to put it differently, the vanity name is defined at the site collection level and not on the web application.

    I think have most of it under control now, only the 'open in explorer' (document collection) isn't working yet.

    Thx again - M.

    Sunday, September 11, 2011 3:48 PM
  • Hi Marcus,

    okay i think i understand your question now. Well, from an UAG point of view, this would be just a single web application and therefore could be covered using a single publishing rule. If you like to filter which user group gets access to which site collection then you'll get a hard time. If not, then id would be as easy as publishing a single SharePoint site.

    Regarding the "explorer view". This feature requieres that you've used the SharePoint application template for publishing. The resulting rule set of t he wizzards will inject some JScript code into the SharePoint site during initial access. This script code will setup the needed cookies for Windows Explorer to traverse UAG without to reauthenticate again. You can verify this functionality by collecting some fiddler traces - you should see a web request for "sharepoint.asp" in this case.

    -Kai

     

    Monday, September 12, 2011 1:39 AM