<?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 Security Servers in a Cloud Pod Architecture in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656218#M71087</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that is correct. the SS's are paried to a CS, but once you've connected to the broker, it can channel the SITE B's desktop over the back channel and present it to the site A external client. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Apr 2015 15:58:06 GMT</pubDate>
    <dc:creator>JackMac4</dc:creator>
    <dc:date>2015-04-08T15:58:06Z</dc:date>
    <item>
      <title>View Security Servers in a Cloud Pod Architecture</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656217#M71086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe someone can help me clarifing a grey area in a Cloud Pod Architecture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that if I have POD-A in SITE-A and POD-B in SITE-B, thanks to Global Entitlement I can broker an internal user connecting from SITE-A to a Virtual Desktop in SITE-B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the same apply when users are connecting from the internet? Say I have a Security Server for SITE-A and another one for SITE-B, can I assume that a user connecting from the internet through SITE-A can be tunneled to a Virtual Desktop in SITE-B? In other words, is the Security Server in SITE-A capable of tunnelling connections to Virtual Desktops in SITE-B?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for you help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Apr 2015 09:31:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656217#M71086</guid>
      <dc:creator>caddo</dc:creator>
      <dc:date>2015-04-06T09:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: View Security Servers in a Cloud Pod Architecture</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656218#M71087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that is correct. the SS's are paried to a CS, but once you've connected to the broker, it can channel the SITE B's desktop over the back channel and present it to the site A external client. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Apr 2015 15:58:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656218#M71087</guid>
      <dc:creator>JackMac4</dc:creator>
      <dc:date>2015-04-08T15:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: View Security Servers in a Cloud Pod Architecture</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656219#M71088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jack,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is exatcly what I was expecting but thank you for confirming it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Apr 2015 16:13:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Security-Servers-in-a-Cloud-Pod-Architecture/m-p/2656219#M71088</guid>
      <dc:creator>caddo</dc:creator>
      <dc:date>2015-04-08T16:13:40Z</dc:date>
    </item>
  </channel>
</rss>

