<?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 Updating Windows UF to 9.2.0.1 via SCCM - 1603 errors in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/681090#M13741</link>
    <description>&lt;P&gt;As title. I'm updating to UF 9.2.0.1 via SCCM, but a subset of targets are failing to install the update with the dreaded 1603 return code. The behavior is the same whether or not I run the msi as SYSTEM (i.e., via USE_LOCAL_SYSTEM) or not. All the existing forwarders being updated are newer - 8.2+, but mostly 9.1.x.&lt;/P&gt;&lt;P&gt;Oddly, if I manually run the same msiexec string with a DA account on the local system, the update usually succeeds. It's baking my noodle why it will work one way but not another. I have msiexec debug logging set up, but it's not giving me anything obvious to work with.&lt;/P&gt;&lt;P&gt;I can also usually get it to install if I uninstall the UF and gut the registry of all vestiges of UF, but that's not something I want to do on this many systems.&lt;/P&gt;&lt;P&gt;I've read a bunch of other threads with 1603 errors but none of them have been my issue, as far as I can tell.&lt;/P&gt;&lt;P&gt;Any ideas as to what the deal is?&lt;/P&gt;</description>
    <pubDate>Mon, 18 Mar 2024 19:22:45 GMT</pubDate>
    <dc:creator>whar_garbl</dc:creator>
    <dc:date>2024-03-18T19:22:45Z</dc:date>
    <item>
      <title>Updating Windows UF to 9.2.0.1 via SCCM - 1603 errors</title>
      <link>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/681090#M13741</link>
      <description>&lt;P&gt;As title. I'm updating to UF 9.2.0.1 via SCCM, but a subset of targets are failing to install the update with the dreaded 1603 return code. The behavior is the same whether or not I run the msi as SYSTEM (i.e., via USE_LOCAL_SYSTEM) or not. All the existing forwarders being updated are newer - 8.2+, but mostly 9.1.x.&lt;/P&gt;&lt;P&gt;Oddly, if I manually run the same msiexec string with a DA account on the local system, the update usually succeeds. It's baking my noodle why it will work one way but not another. I have msiexec debug logging set up, but it's not giving me anything obvious to work with.&lt;/P&gt;&lt;P&gt;I can also usually get it to install if I uninstall the UF and gut the registry of all vestiges of UF, but that's not something I want to do on this many systems.&lt;/P&gt;&lt;P&gt;I've read a bunch of other threads with 1603 errors but none of them have been my issue, as far as I can tell.&lt;/P&gt;&lt;P&gt;Any ideas as to what the deal is?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 19:22:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/681090#M13741</guid>
      <dc:creator>whar_garbl</dc:creator>
      <dc:date>2024-03-18T19:22:45Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Windows UF to 9.2.0.1 via SCCM - 1603 errors</title>
      <link>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/696983#M14144</link>
      <description>&lt;P&gt;Were you able to get a solution for this as we are also facing the same issue with multiple builds.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2024 18:38:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/696983#M14144</guid>
      <dc:creator>goelshruti119</dc:creator>
      <dc:date>2024-08-21T18:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Windows UF to 9.2.0.1 via SCCM - 1603 errors</title>
      <link>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/696986#M14145</link>
      <description>&lt;P&gt;What does you msiexec command look like that you're using to install the Splunk UF ?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2024 19:29:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/696986#M14145</guid>
      <dc:creator>nmohammed</dc:creator>
      <dc:date>2024-08-21T19:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Windows UF to 9.2.0.1 via SCCM - 1603 errors</title>
      <link>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/697786#M14154</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/192553"&gt;@nmohammed&lt;/a&gt;&amp;nbsp;&amp;nbsp;and&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/271381"&gt;@goelshruti119&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Please see the following reply for instructions on how to troubleshoot:&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Installation/Install-issue-on-Server-2016/m-p/540173/highlight/true#M7187" target="_blank" rel="noopener"&gt;https://community.splunk.com/t5/Installation/Install-issue-on-Server-2016/m-p/540173/highlight/true#...&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Jo.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2024 23:29:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Updating-Windows-UF-to-9-2-0-1-via-SCCM-1603-errors/m-p/697786#M14154</guid>
      <dc:creator>jho-splunk</dc:creator>
      <dc:date>2024-08-29T23:29:01Z</dc:date>
    </item>
  </channel>
</rss>

