<?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 MSIEXEC issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357875#M99462</link>
    <description>&lt;P&gt;We are experiencing some issue with this, Luckily these users are in test mode but in a couple of days they will be deployed to live.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you see below this is the alert, Do you think its o.k. To create an exception rule for this. What are your thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TESTMODE: The current application 'C:\WINNT\system32\services.exe' (as user NT AUTHORITY\SYSTEM) is trying to execute the new application 'C:\WINNT\system32\msiexec.exe'. The user would have been prompted as to the action to take&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 09:24:37 GMT</pubDate>
    <dc:creator>jameswestley</dc:creator>
    <dc:date>2019-03-10T09:24:37Z</dc:date>
    <item>
      <title>MSIEXEC issue</title>
      <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357875#M99462</link>
      <description>&lt;P&gt;We are experiencing some issue with this, Luckily these users are in test mode but in a couple of days they will be deployed to live.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you see below this is the alert, Do you think its o.k. To create an exception rule for this. What are your thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TESTMODE: The current application 'C:\WINNT\system32\services.exe' (as user NT AUTHORITY\SYSTEM) is trying to execute the new application 'C:\WINNT\system32\msiexec.exe'. The user would have been prompted as to the action to take&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:24:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357875#M99462</guid>
      <dc:creator>jameswestley</dc:creator>
      <dc:date>2019-03-10T09:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: MSIEXEC issue</title>
      <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357876#M99464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess upgrading to  4.0.3 will resolve the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Apr 2005 13:04:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357876#M99464</guid>
      <dc:creator>a-vazquez</dc:creator>
      <dc:date>2005-04-25T13:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: MSIEXEC issue</title>
      <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357877#M99465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what a stupid answer..em why ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2005 11:50:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357877#M99465</guid>
      <dc:creator>jameswestley</dc:creator>
      <dc:date>2005-04-27T11:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: MSIEXEC issue</title>
      <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357878#M99466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is caused when a user logs on and a Windows Installer installed product tries to verify the installation (it's profile specific).  Whatever the product is, it's configured to look for the installation files using the msiexec and that's what triggers the installation alert.  Unfortunately it's a pretty broad exception you'd have to make to allow it.  You might want to look at the app that's causing it first before making an exception.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Apr 2005 18:09:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357878#M99466</guid>
      <dc:creator>tsteger1</dc:creator>
      <dc:date>2005-04-28T18:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: MSIEXEC issue</title>
      <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357879#M99467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;James,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if you ever got an answer to this message, and if not what you eventually tried.  We are seeing the same message on all our clients several times a day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rusty&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Dec 2005 19:13:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357879#M99467</guid>
      <dc:creator>rspoon17</dc:creator>
      <dc:date>2005-12-13T19:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: MSIEXEC issue</title>
      <link>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357880#M99468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CSA 4.5 fix this problem with a rule that give services.exe access to the system directory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greg Owens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Dec 2005 21:28:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/msiexec-issue/m-p/357880#M99468</guid>
      <dc:creator>owensgl</dc:creator>
      <dc:date>2005-12-14T21:28:26Z</dc:date>
    </item>
  </channel>
</rss>

