<?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: User-ID - Windows Server 2022 , not working in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577567#M115892</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/63327"&gt;@tnewton&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Just to add to what&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/11943"&gt;@kiwi&lt;/a&gt;&amp;nbsp;mentioned already, WinRM is also something that is likely locked down if your server administrators are doing any sort of hardening. When you're working with your server administrators make sure that you mention you're also attempting to do this from your firewall; if you simply ask if WinRM is enabled they might say yes because it is, but they have restrictions that would prevent your firewall from accessing the service. Take special note of the permissions required by the service account as well.&lt;/P&gt;</description>
    <pubDate>Sat, 17 Feb 2024 05:18:37 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-02-17T05:18:37Z</dc:date>
    <item>
      <title>User-ID - Windows Server 2022 , not working</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577439#M115873</link>
      <description>&lt;P&gt;We are running a Windows server 2022 and PA-3220.&amp;nbsp; I have the user-agent put on a seperate Win 2022 server.&amp;nbsp; The firewall when communicating with server is getting dropped code 5986.&amp;nbsp; Under my Server Monitoring it shows Connection refused(0).&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 01:23:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577439#M115873</guid>
      <dc:creator>tnewton</dc:creator>
      <dc:date>2024-02-16T01:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: User-ID - Windows Server 2022 , not working</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577487#M115880</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/63327"&gt;@tnewton&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There's not a lot to work with but &lt;SPAN&gt;I'm guessing that you are using WinRM over HTTPS as transport protocol but maybe the server is not listening to the port 5986 (b&lt;/SPAN&gt;y default, WinRM/HTTPS uses port 5986&lt;SPAN&gt;).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR style="box-sizing: border-box; color: #181818; font-family: -apple-system, 'system-ui', 'Segoe UI', Roboto, Helvetica, Arial, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;" /&gt;&lt;SPAN&gt;I would suggest you to review the article below and confirm with your AD admin if the service was already enabled with the respective port:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/user-id/map-ip-addresses-to-users/configure-server-monitoring-using-winrm" target="_blank" rel="noopener"&gt;Configure Server Monitoring Using WinRM&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;-Kim.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 10:10:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577487#M115880</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2024-02-16T10:10:19Z</dc:date>
    </item>
    <item>
      <title>Re: User-ID - Windows Server 2022 , not working</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577567#M115892</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/63327"&gt;@tnewton&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Just to add to what&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/11943"&gt;@kiwi&lt;/a&gt;&amp;nbsp;mentioned already, WinRM is also something that is likely locked down if your server administrators are doing any sort of hardening. When you're working with your server administrators make sure that you mention you're also attempting to do this from your firewall; if you simply ask if WinRM is enabled they might say yes because it is, but they have restrictions that would prevent your firewall from accessing the service. Take special note of the permissions required by the service account as well.&lt;/P&gt;</description>
      <pubDate>Sat, 17 Feb 2024 05:18:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/user-id-windows-server-2022-not-working/m-p/577567#M115892</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-02-17T05:18:37Z</dc:date>
    </item>
  </channel>
</rss>

