<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>blimvisible Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>blimvisible Tracker</description>
    <pubDate>Fri, 24 Nov 2023 01:18:57 GMT</pubDate>
    <dc:date>2023-11-24T01:18:57Z</dc:date>
    <item>
      <title>Re: Using PowerShell to Deploy VMware Unified Access Gateway</title>
      <link>https://communities.vmware.com/t5/Horizon-Documents/Using-PowerShell-to-Deploy-VMware-Unified-Access-Gateway/tac-p/2783033#M204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a configuration setting one could add to the .INI file to set the Access Point's time zone? Setting the time zone seems to still requires opening a console window in an otherwise fully automated deployment process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Dec 2016 14:17:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Documents/Using-PowerShell-to-Deploy-VMware-Unified-Access-Gateway/tac-p/2783033#M204</guid>
      <dc:creator>blimvisible</dc:creator>
      <dc:date>2016-12-21T14:17:39Z</dc:date>
    </item>
  </channel>
</rss>

