<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Hiding the UAG portal bar</title><link>http://blogs.technet.com/b/edgeaccessblog/archive/2011/01/04/hiding-the-uag-portal-bar.aspx</link><description>The UAG portal is designed to let you publish multiple applications using a single public hostname, but many customers need UAG to publish only a single application, or simply don’t want to have the portal visible to their users, and have the users redirected</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Hiding the UAG portal bar</title><link>http://blogs.technet.com/b/edgeaccessblog/archive/2011/01/04/hiding-the-uag-portal-bar.aspx#3389950</link><pubDate>Thu, 24 Feb 2011 18:58:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3389950</guid><dc:creator>Eric Raff</dc:creator><description>&lt;p&gt;Thanks for the post Ben. I have a follow up question for you on this.&lt;/p&gt;
&lt;p&gt;Our Intranet which is hosted in SharePoint 2010 is our &amp;quot;portal&amp;quot; (relative to the users perspective) as such we never want user to see the UAG portal page.&lt;/p&gt;
&lt;p&gt;In building the UAG Trunk, it does not look like I can have the trunks &amp;quot;Public host name&amp;quot; be the same thing as our intranets name.&lt;/p&gt;
&lt;p&gt;For example users access the intranet (internally) via intranet.example.com.&lt;/p&gt;
&lt;p&gt;We want to publish our intranet externally through UAG.&lt;/p&gt;
&lt;p&gt;I am constrained in UAG on the trunk setup that I MUST define a portal public host name which I make intranet.example.com&lt;/p&gt;
&lt;p&gt;However when I then try and publish the SharePoint 2010 application and set the public host name here, it reports: &amp;quot;AAM applications cannot be published when the host name matches the trunk host name, and the application path contains a forward slash &amp;#39;/&amp;#39;&amp;quot;&lt;/p&gt;
&lt;p&gt;Because of this scenario It appears that I MUST use an alternate name for my UAG Portal (uag.example.com) and then I can publish the SharePoint 2010 application using the intranet.example.com public name.&lt;/p&gt;
&lt;p&gt;If this is all true, then do you see any scenarios where the user could be sent to uag.example.com and be shown the UAG Portal page which is not desired at all. What if I simply did not setup a public DNS entry for uag.example.com to block anyone from ever getting there? Dangerous and &amp;quot;not supported&amp;quot;? :-)&lt;/p&gt;
&lt;p&gt;Thanks for you input.&lt;/p&gt;
&lt;p&gt;E.R.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3389950" width="1" height="1"&gt;</description></item></channel></rss>