UAG Basic Customization, Part 1

In one of my previous posts I have referenced a couple of good resources on the subject of UAG customization:

TechNet resource "Customizing Forefront UAG" is a good starting point, and there’s a book that was just published that covers this very topic – “Mastering Microsoft Forefront UAG 2010 Customization” by Erez Ben-Ari.

Much is possible when it comes to customizing and extending UAG, and this is when you would need to refer to those materials mentioned above and to study them carefully; but in some cases only basic customization may be desired, like changing default logon page (say edit the title and add a standard security banner). This post aims to cover those basic changes. So, let's say we want our default logon page to look somewhat like this:

And here are the things we would need to do:

Please, note that all file locations mentioned in this article are installation defaults and may differ from locations you have selected during the installation.

Under C:\Program Files\Microsoft Forefront Unified Access Gateway\von\InternalSite\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\InternalSite\Languages\CustomUpdate.
Open en-US.xml file in the \CustomUpdate folder using Notepad and perform the following edits (based on the above sample):

<String id="2" _locID="2"> - desired title
<String id="4" _locID="4"> - desired system security message
<String id="5" _locID="5"> - desired support information
<String id="1" _locID="1"> - desired password self-service information

To change the default message displayed when users log off modify the following:

<String id=3" _locID"3"> - desired LogOff message (for example: Thank you for using Company XYZ Remote Access Portal)

Save the changes in en-US.xml (remember to always use customization file under \CustomUpdate, and not the original one)

Comments

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

Drumbeat - Sales and Technical Resources for Office 365

Drumbeat - provides information as well as technical and sales resources for Office 365. From partnering with Microsoft, to building up your sales and technical readiness, to adopting proven methodologies for successful deployment - you will find lots of good information and many helpful links there. Here's a quick sample of topics covered: The Customer Decision Framework is Microsoft's selling methodology designed to help partners sell Office 365 to their customers. Office 365 FastTrack is Microsoft's new, 3-step pilot and deployment methodology designed so customers experience service value early in the sales cycle with a smooth path to advance from a pilot to deployment.

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

Technocrat

Search This Blog