<?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>topic Re: View 5 Transfer server placement in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333401#M5448</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Installation Requirements for View Transfer Server&lt;BR /&gt;You must install View Transfer Server as a Windows application in a virtual machine that meets specific&lt;BR /&gt;requirements.&lt;BR /&gt;1. It must be managed by the same vCenter Server instance as the local desktops that it will manage.&lt;BR /&gt;2. It does not have to be part of a domain.&lt;BR /&gt;3. It must use a static IP address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Dec 2011 06:24:31 GMT</pubDate>
    <dc:creator>uday_s</dc:creator>
    <dc:date>2011-12-07T06:24:31Z</dc:date>
    <item>
      <title>View 5 Transfer server placement</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333400#M5447</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Running a pilot VDI arrangement, in which I have 2 connection servers internally; one dedicated for internal access, the other paired with a Security Server on a DMZ.&amp;nbsp; Everything is operating fine.&amp;nbsp; I'd like to deploy a transfer server for local mode access, but the deployment guide doesn't give an indication where it would fit best in a topology.&amp;nbsp; I'm suspecting it would be in the same DMZ network as the Security Server?&amp;nbsp; Or does it really matter, as the Connection Server will be doing all of the coordinating?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Dec 2011 17:40:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333400#M5447</guid>
      <dc:creator>sketchy00</dc:creator>
      <dc:date>2011-12-06T17:40:57Z</dc:date>
    </item>
    <item>
      <title>Re: View 5 Transfer server placement</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333401#M5448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Installation Requirements for View Transfer Server&lt;BR /&gt;You must install View Transfer Server as a Windows application in a virtual machine that meets specific&lt;BR /&gt;requirements.&lt;BR /&gt;1. It must be managed by the same vCenter Server instance as the local desktops that it will manage.&lt;BR /&gt;2. It does not have to be part of a domain.&lt;BR /&gt;3. It must use a static IP address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Dec 2011 06:24:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333401#M5448</guid>
      <dc:creator>uday_s</dc:creator>
      <dc:date>2011-12-07T06:24:31Z</dc:date>
    </item>
    <item>
      <title>Re: View 5 Transfer server placement</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333402#M5449</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Well, it sounds as if having the transfer server sitting in the DMZ is the best approach.&amp;nbsp; I'll go ahead and proceed with that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Dec 2011 17:17:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-5-Transfer-server-placement/m-p/333402#M5449</guid>
      <dc:creator>sketchy00</dc:creator>
      <dc:date>2011-12-07T17:17:49Z</dc:date>
    </item>
  </channel>
</rss>

