Skip to main content

UAG Backup

Every organization should have disaster recovery and continuity of operations plans that commensurate with its risk reduction goals and its overall risk management profile. And of course UAG infrastructure should be an integral part of such plans, subject to associated backup and recovery procedures. However, this post doesn't have much to do with these fundamental things. Instead, it aims to cover the very basics of UAG configuration settings backup or import/export. Here's where one would configure automatic backups (that will be performed automatically every time new configuration is activated):
 

Please, note that all file locations mentioned in this article are installation defaults and may differ from locations you have selected during the installation.
  • The password must be at least 8 characters long and backup default location is C:\Program files\Microsoft Forefront Unified Access Gateway\Backup\. It could be a good idea to periodically backup the content of this directory either via a backup software or a script.
  • To perform manual import/export via GUI simply select "File > Import" or "File > Export", supply required parameters and click on "Export":
  • To perform import/export via command line navigate to C:\Program Files\Microsoft Forefront Unified Access Gateway\utils\ConfigMgr\ and run one of the following commands:
    • configmgrutil export filename.xml password [comment]
    • configmgrutil import filename.xml password 
  • For more detailed information please, refer to the following TechNet article.
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