<?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 WMI On server 2022 for USER-ID in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/wmi-on-server-2022-for-user-id/m-p/476429#M103572</link>
    <description>&lt;P&gt;Hi There,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a pair of PA-3220s. User-ID was working swimmingly. Recently upgraded our DCs to Windows Server 2022 and WMI is routinely failing and showing "Not connected" under server monitor.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Doing some reading on WMI and Server 2022, and it sounds like Microsoft did something under the hood in 2022 that required updates or changes from 3rd parties to use that information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else stumbled on this and have it working?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Mar 2022 19:41:15 GMT</pubDate>
    <dc:creator>kaumell</dc:creator>
    <dc:date>2022-03-28T19:41:15Z</dc:date>
    <item>
      <title>WMI On server 2022 for USER-ID</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wmi-on-server-2022-for-user-id/m-p/476429#M103572</link>
      <description>&lt;P&gt;Hi There,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a pair of PA-3220s. User-ID was working swimmingly. Recently upgraded our DCs to Windows Server 2022 and WMI is routinely failing and showing "Not connected" under server monitor.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Doing some reading on WMI and Server 2022, and it sounds like Microsoft did something under the hood in 2022 that required updates or changes from 3rd parties to use that information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else stumbled on this and have it working?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 19:41:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wmi-on-server-2022-for-user-id/m-p/476429#M103572</guid>
      <dc:creator>kaumell</dc:creator>
      <dc:date>2022-03-28T19:41:15Z</dc:date>
    </item>
    <item>
      <title>Re: WMI On server 2022 for USER-ID</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wmi-on-server-2022-for-user-id/m-p/476486#M103578</link>
      <description>&lt;P&gt;Yes, MS pushed out updates that disabled WMI a few months ago (wasn't suppose to happen until later this year). So you have to change the transport protocol from WMI to WINRM-HTTPS and have a valid security certificate now, to get PANOS userID to work. We are pulling userID from the Windows agent and GP at the moment, so I disabled PANOS userID... haven't gotten back to make it work yet.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Mar 2022 22:53:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wmi-on-server-2022-for-user-id/m-p/476486#M103578</guid>
      <dc:creator>Adrian_Jensen</dc:creator>
      <dc:date>2022-03-28T22:53:27Z</dc:date>
    </item>
  </channel>
</rss>

