<?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: Different behavior between Visual Studio versions in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331698#M2005</link>
    <description>&lt;P&gt;Hi @Fabio Farias​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think the Visual Studio 2022 may have different values in the Publisher’s signature, Product name, File description, or Company name fields, compared to previous versions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The digital signature might have changed for Visual Studio 2022. Even though it’s still signed by Microsoft&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Please validate the file properties of the Visual Studio 2022 executable&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Once you have verified the correct metadata for Visual Studio 2022, update the policy accordingly&lt;/LI&gt;&lt;LI&gt;In addition, you can test by broadening your matching conditions to see if the issue is resolved&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2024 11:34:47 GMT</pubDate>
    <dc:creator>M.Vora780263</dc:creator>
    <dc:date>2024-09-13T11:34:47Z</dc:date>
    <item>
      <title>Different behavior between Visual Studio versions</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331697#M2004</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our users are reporting that if they open Visual Studios 2017 or 2019 the confirmation pop-up shows up but not for Visual Studios 2022.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our configuration for VS in the policy is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Publisher's signature starts with {"Microsoft"} (case insensitive)&lt;/P&gt;&lt;P&gt;AND Product name contains "Visual Studio" (case insensitive)&lt;/P&gt;&lt;P&gt;AND File description is exactly "Visual Studio Installer" (case sensitive)&lt;/P&gt;&lt;P&gt;AND Company name starts with "Microsoft" (case insensitive)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any reason why this have a different behavior for version 2022?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the help. &lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:16:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331697#M2004</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-09-13T11:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: Different behavior between Visual Studio versions</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331698#M2005</link>
      <description>&lt;P&gt;Hi @Fabio Farias​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think the Visual Studio 2022 may have different values in the Publisher’s signature, Product name, File description, or Company name fields, compared to previous versions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The digital signature might have changed for Visual Studio 2022. Even though it’s still signed by Microsoft&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Please validate the file properties of the Visual Studio 2022 executable&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Once you have verified the correct metadata for Visual Studio 2022, update the policy accordingly&lt;/LI&gt;&lt;LI&gt;In addition, you can test by broadening your matching conditions to see if the issue is resolved&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:34:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331698#M2005</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2024-09-13T11:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: Different behavior between Visual Studio versions</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331699#M2006</link>
      <description>&lt;P&gt;Thank you. This solved our issue.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 16:28:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/different-behavior-between-visual-studio-versions/m-p/1331699#M2006</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-09-13T16:28:13Z</dc:date>
    </item>
  </channel>
</rss>

