<?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: Best Way For Configuration of 5 PA-200 Before Shipping To Remote Location in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/best-way-for-configuration-of-5-pa-200-before-shipping-to-remote/m-p/99956#M44224</link>
    <description>&lt;P&gt;We pretty much configure and push everything in the Policies, Objects and Device tab using Panorama. &amp;nbsp;Then we manually configure the items in the Network tab, mostly because our remote sites aren't generally the same.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One thing I would suggest is to set up an emergency "back door" to the PA-200. &amp;nbsp;Just in case it doesn't come online or the site-to-site tunnel(if you're using one) doesn't come up. &amp;nbsp;You could give SSH or HTTPS access to the PA-200 and allow only your source IP. &amp;nbsp;You could also ship a laptop(with client VPN) and a cellular hot spot with it, so you can remote into the PA-200(assuming a tech or someone can plug it in).&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jul 2016 18:56:48 GMT</pubDate>
    <dc:creator>jambulo</dc:creator>
    <dc:date>2016-07-25T18:56:48Z</dc:date>
    <item>
      <title>Best Way For Configuration of 5 PA-200 Before Shipping To Remote Location</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-way-for-configuration-of-5-pa-200-before-shipping-to-remote/m-p/99530#M44190</link>
      <description>&lt;P&gt;The next big project, regarding Palo Alto, is deploying a total of 5 PA-200’s. 4 will be located in 3 different locations in Mexico. 1 Mexican location will have 2 PA-200’s setup in HA mode. The remaining PA-200 will be deployed in Managua, Nicaragua. They all will be configured with Wildfire, Threat Protection, URL Filtering and Global Protect. We of course want to manage these via Panorama.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am reaching out to see if Palo Alto has a Best Practice document available explaining how to configure these boxes using Panorama and then ship to remote locations as close as possible to “plug and play”. I can find nothing that really covers configuring locally to send to remotes locations.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 19:14:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-way-for-configuration-of-5-pa-200-before-shipping-to-remote/m-p/99530#M44190</guid>
      <dc:creator>Doug_Hogue</dc:creator>
      <dc:date>2016-07-22T19:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: Best Way For Configuration of 5 PA-200 Before Shipping To Remote Location</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-way-for-configuration-of-5-pa-200-before-shipping-to-remote/m-p/99956#M44224</link>
      <description>&lt;P&gt;We pretty much configure and push everything in the Policies, Objects and Device tab using Panorama. &amp;nbsp;Then we manually configure the items in the Network tab, mostly because our remote sites aren't generally the same.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One thing I would suggest is to set up an emergency "back door" to the PA-200. &amp;nbsp;Just in case it doesn't come online or the site-to-site tunnel(if you're using one) doesn't come up. &amp;nbsp;You could give SSH or HTTPS access to the PA-200 and allow only your source IP. &amp;nbsp;You could also ship a laptop(with client VPN) and a cellular hot spot with it, so you can remote into the PA-200(assuming a tech or someone can plug it in).&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2016 18:56:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-way-for-configuration-of-5-pa-200-before-shipping-to-remote/m-p/99956#M44224</guid>
      <dc:creator>jambulo</dc:creator>
      <dc:date>2016-07-25T18:56:48Z</dc:date>
    </item>
  </channel>
</rss>

