Skip to main content

UAG Pre-installation Checklist

Here's a quick pre-installation checklist I have developed for the UAG deployments. Of course, it may not cover all possible deployment scenarios. So, feel free to expand upon it as necessary.




Network:
  • Networking has been configured correctly
  • Static IPs assigned to all network interfaces
  • Static IPs to be assigned to each trunk (in load-balanced array this will be assigned to the VIP associated with the trunk) have been reserved
  • Connectivity to the Internet works
  • Connectivity to the internal network works
  • All internal networks (network ranges that UAG will be fronting/protecting) have been explicitly identified


Server(s):
  • All servers meet system requirements 
  • All available Windows updates have been installed
  • All servers are clean, with no additional (unnecessary) software installed
  • All servers have been properly named
  • If applicable (required for UAG array), all servers have been joined to the domain 
  • No previous versions of UAG, TMG, or SQL are installed on any of the servers
  • Windows firewall service is started, and set to start automatically on all servers

Accounts:
  • User account (domain account if UAG server is joint to the domain) and password to perform UAG installation have been identified (must have administrative permissions on the server)
  • User account and password that will be impersonated by UAG to retrieve data from Active Directory have been identified (must have permissions to traverse AD and read objects and their attributes). Similar provisions will apply to other authentication repositories. 
  • If SharePoint resources are to be published, user account and password to access SharePoint central admin (for AAM modification) has been identified.  



Media and Licenses:

  • UAG installation media (latest version with applicable service packs and updates) has been obtained and made available
  • UAG product key / license has been obtained and made available


Miscellaneous:
  • All required URLs (for trunks and applications to be published) have been identified
  • Means of creating/editing DNS records (for the URLs mentioned above) have been established
  • Valid digital certificates for each trunk and each application that will require the use of HTTPS (SSL/TLS) have been obtained and made available

NOTE: The certificates should match the FQDN names used in access URL (for example: if https://xxx.yyy.com is used to access UAG portal, then the certificate should be issued to xxx.yyy.com). To simplify operations the use of wildcard (*.yyy.com) certificate is recommended.
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