<?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: 4.1.12 early adopters... in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40654#M29858</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone bitten it yet? I'm planning to upgrade to 4.1.12 on Tuesday morning but have 4.1.11 in the bin as reserve (we're on 4.1.8 atm). Should I just go to 4.1.11 and wait? The latest fixes are very appealing... don't want my pants to catch fire over it though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 03 May 2013 08:51:19 GMT</pubDate>
    <dc:creator>notes01</dc:creator>
    <dc:date>2013-05-03T08:51:19Z</dc:date>
    <item>
      <title>4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40651#M29855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Am I the only one who is adopting a "once bitten, twice shy" approach when it comes to 4.1.12?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The release notes claim that PAN have fixed the bugs I've been bitten by - the userID process problem, the App Override killing TCP sessions after 10 seconds and one other - but I'm wary of rushing out and just installing it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone run with 4.1.12 yet (and yes, I know it's only just come out)? If so, is it behaving?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Apr 2013 22:59:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40651#M29855</guid>
      <dc:creator>darren_g</dc:creator>
      <dc:date>2013-04-21T22:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40652#M29856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's the first issue I've seen... he's going from 4.0.5 to 4.1.12 though so it's kind of a big leap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/message/26615"&gt;https://live.paloaltonetworks.com/message/26615&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm still waiting for the DHCP fix we were promised before we go to 4.1.12+... it's slated to appear in 4.1.13.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Apr 2013 13:47:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40652#M29856</guid>
      <dc:creator>ericgearhart</dc:creator>
      <dc:date>2013-04-25T13:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40653#M29857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmmm, I think I'll hold off a while yet before I jump into the upgrade, then.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Apr 2013 22:51:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40653#M29857</guid>
      <dc:creator>darren_g</dc:creator>
      <dc:date>2013-04-25T22:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40654#M29858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone bitten it yet? I'm planning to upgrade to 4.1.12 on Tuesday morning but have 4.1.11 in the bin as reserve (we're on 4.1.8 atm). Should I just go to 4.1.11 and wait? The latest fixes are very appealing... don't want my pants to catch fire over it though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 May 2013 08:51:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40654#M29858</guid>
      <dc:creator>notes01</dc:creator>
      <dc:date>2013-05-03T08:51:19Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40655#M29859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;4.1.12 is ready and i suggest its installation. i've done the upgrade for a dozen of PA-200 clusters plus severla PA-2020 in the last week without any issue.&lt;/P&gt;&lt;P&gt;It solves a response pages not shown due to packet segmentation from the early 4.1.11&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 May 2013 20:42:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40655#M29859</guid>
      <dc:creator>NGS_SOC</dc:creator>
      <dc:date>2013-05-03T20:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40656#M29860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, I'll go for it then. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 May 2013 20:49:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40656#M29860</guid>
      <dc:creator>notes01</dc:creator>
      <dc:date>2013-05-05T20:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40657#M29861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, Panorama and two PA-5020s upgraded to 4.1.2 - the Panorama server took about 30 minutes and the 5020s only 5 minutes each. No issues so far, the (long-overdue) DNS name resolution in reports is very welcome.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 May 2013 13:32:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40657#M29861</guid>
      <dc:creator>notes01</dc:creator>
      <dc:date>2013-05-08T13:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: 4.1.12 early adopters...</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40658#M29862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One strangeness we are experiencing is that a couple of our inbound proxies are randomly throwing up occasional proxy errors since the upgrade. It could be nothing to do with the firewalls, we simply don't know, but the last time weird random sh^Htuff started happening was after we went to 4.1.6, which was a nightmare version. I'll report back if it gets better or worse.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit: Looks like a middleware server issue, 4.1.12 not at fault.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Andy Liddiard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 May 2013 11:52:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/4-1-12-early-adopters/m-p/40658#M29862</guid>
      <dc:creator>notes01</dc:creator>
      <dc:date>2013-05-10T11:52:33Z</dc:date>
    </item>
  </channel>
</rss>

