Skip to main content

UAG Basic Customization, Part 2

For information on how to change basic logon page settings please, refer to the first part of this post - UAG Basic Customization, Part 1.
Please, note that all file locations mentioned in this article are installation defaults and may differ from locations you have selected during the installation.
We can also customize basic properties of the UAG Portal pages (displayed after successful logon on trunks that use built-in Portal as a default application):   
  header & toolbar

footer
  • Under C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage\Data\Languages\ locate an appropriate language file, in our case en-US.xml, and copy it to C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage\Data\Languages\CustomUpdate\.
  • Open en-US.xml file in the \CustomUpdate folder using Notepad and perform the following edits (based on the above sample):
    1. <String id="12" _locID="12"> - desired title
    2. <String id="182" _locID="182"> - desired support contact
    3. <String id="1" _locID="1"> - desired corporate message
  • Save the changes in en-US.xml (remember to always use customization file under \CustomUpdate, and not the original one)
It may also be desirable to add hyperlinks to the following areas, for example to point: 1) to the Help Desk email address; 2) to the Corporate web site:


footer
  • Under C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage\Data\SiteMap\Footer\ locate file LeftFooter.sitemap and copy it to C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage\Data\SiteMap\Footer\CustomUpdate\
  • Edit siteMapNode url parameters as needed. Here's an example:

<?xml version="1.0" encoding="utf-8" ?>
<siteMap xmlns="http://schemas.microsoft.com/AspNet/SiteMap-File-1.0" enableLocalization="true">
    <siteMapNode url="" title=""  description="">
      <siteMapNode url="mailto:help@companyXYZ.com"                   title="$Resources:Resource, 182"
                   description="$Resources:Resource, 182"
                   imageUrl=""
                   displayMode="OnlyText"
                   target="_blank" />
      <siteMapNode url=""
                   title="|"
                   description=""
                   imageUrl=""
                   displayMode="OnlyText"
                   target=""
                   />
      <siteMapNode url="http://www.CompanyXYZ.com"                   title="$Resources:Resource,1"
                   description=""
                   imageUrl=""
                   displayMode="OnlyText"
                   target=""
                   selectable="false"
                     />
    </siteMapNode>
</siteMap>
Last but not least, there's "E-mail system administrator" button on the toolbar that can be hyperlink enabled:
toolbar

  • Under C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage\Data\SiteMap\ToolBar\ locate file Web.sitemap and copy it to C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage\Data\SiteMap\ToolBar\CustomUpdate\
  • Open Web.sitemap file in the \CustomUpdate folder using Notepad. Find the line that contains "mailto:" and change it to reflect an appropriate support contact information:
    • for example: <siteMapNode url="mailto:help@companyXYZ.com"
  • Save the changes in Web.sitemap (remember to always use customization file under \CustomUpdate, and not the original one)

Labels:

Comments

Post a Comment

Popular posts from this blog

Skype for Business and VTC Interoperability

Skype for Business (SfB) has a very, very strong potential, I have written about it in my previous post . I can't think of any other platform that shows as much promise in terms of bridging personal and business communications as well as unifying different modes and mediums. And all of this may have started with a strategic acquisition of Skype by Microsoft in 2011. That said, the road ahead is not without challenges. For example, interoperability with other platforms. Making SfB work with existing Video TeleConferencing (VTC) systems, many of which represent significant capital investments in organizations' infrastructure, could be of a particular importance. After reading statements like Skype for Business is based on Session Initiation Protocol (SIP) standards and supports H.264 (MPEG-4 video coding standard) one can come to a quick conclusion that integration and/or interoperability with other VTC solutions is easy or nearly automatic. Unfortunately, the industry is not
34 comments
Read more

WordPress displays weird characters

Sometimes after a database conversion (e.g. from MySQL to MariaDB) or due to encoding issues a situation might arise when WordPress is showing weird characters. A quick way of remedying the situation would involve examining the pages to discover a pattern (what characters are being substituted, in the example below the apostrophe was replaced by  ’ ) then running an queries against the database to reverse the effect. Here's a quick example (common tables that store content): UPDATE  wp_posts  SET  post_content =  REPLACE (post_content,  'Â' ,  '' )      UPDATE  wp_posts  SET  post_content =  REPLACE (post_content,  '’' ,  "'" )      UPDATE  wp_postmeta  SET  meta_value =  REPLACE (meta_value,  'Â' ,  '' )      UPDATE  wp_postmeta  SET  meta_value =  REPLACE (meta_value,  '’' ,  "'" )      Please, keep in mind that to permanently resolve the issue you would need to get to the root of the p
17 comments
Read more

Mail-enabled security groups in Office 365

Another update (11/19/2013):  further evolution of Office 365 services makes creation of distribution and security groups even easier, plus there's now an option of creating a dynamic distribution group (click here for more information):    Update (08/06/2012): a clear sign of Office 365 evolving along the same lines as other agile cloud services - small incremental features and minor new functionality are being delivered almost continuously and, unlike important major service updates,  without much fanfare. For example, there's no need to resort to using PowerShell to setup mail-enabled security groups anymore, it can now be done at creation using management portal:       Those managing Office 365 ( O365 ) tenant via the Microsoft Online Services Portal  ( MOS Portal ) interface would notice that there are two distinct group entities: Security Groups: can be created via MOS Portal (main portal page>Management>Security Groups) and used for assigning
1 comment
Read more