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

Updating computer's AD Security Group membership without rebooting

I found the following to be very useful - From the elevated command prompt execute “ klist –li 0x3e7 ” to view the logon session of the computer account . To purge them, simply execute “ klist –li 0x3e7 purge ”. A typical use case might involve targeting GPOs based on computer's group membership. When you add computer to the group in order to test the application of policies you can reboot it or, alternatively, run the above mentioned to clear logon sessions, then do “ gpupdate /force ” and check. In a spirit of giving credit where credit is due, I found a few references to this, but the one I learned it from was  http://setspn.blogspot.com/2010/10/updating-servers-security-group.html
4 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 (me...
17 comments
Read more
  AI Agents as Trusted IoT/Software Defined Devices 🤖 Your Newest Endpoint Isn’t a Laptop; It’s an AI Agent. Are You Ready to Secure It? Dive into the next frontier of cybersecurity. Autonomous AI agents are no longer just code; they are powerful actors in our digital ecosystems. Treating them as simple software leaves a massive security gap. Our latest report introduces a new paradigm: The AI Agent as a Software-Defined Device. Discover the essential framework for securing the agentic future: ➡️ The Agent-as-Device Model: Learn why abstracting agents as software-defined devices, similar to IoT endpoints, is the key to managing their complexity and risk. Secure the “hardware” (host), “software” (agent logic), and “network” (communications). ➡️ A Digital Passport for AI: Move beyond static API keys. Explore how Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs) create a cryptographic root of trust, giving every agent a verifiable identity and provable permissions. ➡️...
Post a Comment
Read more