<?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 Symantec client site proxy migration in Cloud Security</title>
    <link>https://community.cisco.com/t5/cloud-security/symantec-client-site-proxy-migration/m-p/2889372#M336</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We are looking to&amp;nbsp;migrate away from an existing Symantec/Messagelabs cloud solution, and are&amp;nbsp;trying to figure out the best approach for migrating the&amp;nbsp;existing proxy servers. These all run the Symantec Client Site Proxy service (effectively squid), and I'm wondering if it's possible to simply run the CWS connector in parallel on the same server - obviously different ports. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Would this work,&amp;nbsp;or should we plan for fresh servers to run the connector?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Anthony&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Mar 2019 01:39:18 GMT</pubDate>
    <dc:creator>anthony.ashwin1</dc:creator>
    <dc:date>2019-03-09T01:39:18Z</dc:date>
    <item>
      <title>Symantec client site proxy migration</title>
      <link>https://community.cisco.com/t5/cloud-security/symantec-client-site-proxy-migration/m-p/2889372#M336</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We are looking to&amp;nbsp;migrate away from an existing Symantec/Messagelabs cloud solution, and are&amp;nbsp;trying to figure out the best approach for migrating the&amp;nbsp;existing proxy servers. These all run the Symantec Client Site Proxy service (effectively squid), and I'm wondering if it's possible to simply run the CWS connector in parallel on the same server - obviously different ports. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Would this work,&amp;nbsp;or should we plan for fresh servers to run the connector?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Anthony&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 01:39:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/symantec-client-site-proxy-migration/m-p/2889372#M336</guid>
      <dc:creator>anthony.ashwin1</dc:creator>
      <dc:date>2019-03-09T01:39:18Z</dc:date>
    </item>
    <item>
      <title>Hi Anthony,</title>
      <link>https://community.cisco.com/t5/cloud-security/symantec-client-site-proxy-migration/m-p/2889373#M337</link>
      <description>&lt;P&gt;Hi Anthony,&lt;/P&gt;
&lt;P&gt;If you&amp;nbsp;already&amp;nbsp;purchased the CWS subscription or in Evalution stage.&amp;nbsp;Best way is, reach out to your assigned Cisco CWS SDM (Service delivery Manager) for deployment assistance.&lt;/P&gt;
&lt;P&gt;If you do not have&amp;nbsp;SDM contact , request the contact details&amp;nbsp;from your&amp;nbsp;Cisco Accounts team.&lt;/P&gt;
&lt;P&gt;You can also&amp;nbsp;share your CWS account name to my email id &amp;lt; asakthiv@cisco.com &amp;gt; .&amp;nbsp;I will&amp;nbsp;request your SDM to get in touch with you for CWS deployment &amp;nbsp;assistance.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks and Regards,&lt;/P&gt;
&lt;P&gt;Ashok Sakthivel.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 04:27:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/symantec-client-site-proxy-migration/m-p/2889373#M337</guid>
      <dc:creator>Ashok Sakthivel</dc:creator>
      <dc:date>2016-04-07T04:27:20Z</dc:date>
    </item>
  </channel>
</rss>

