If I remove the registry keys the SCCM client tries to run the installer and fails at the DetermineContextForAllProducts step. If the registry keys are present the installer fails at the DetermineContextForAllProducts installation step both as run by the SCCM client and manually by me.If I go back and remove the registry keys again, and re-run the installer from cmd.exe it works! LOL WUT? Same installer, same installation arguments (copy and pasted right out of AppEnforce.log), run from a Run As Administrator cmd.exe prompt and it fails with the same error at the same step. I doubled check the NTFS permissions for those keys and SYSTEM has Full Control which seems to disprove this answer indicating that the 0x80004005. Now things get interesting! I remove the keys expecting success, run the Client Application Deployment and Evaluation Cycle and I get the same disappointing results. With a combination of ProcMon and manually searching through the registry I managed to locate the following keys that seem to be related. Return value 3.Ī little Google-fu and I find this posting over at Splunk's Community Support but I'm not terribly confident in correctness of the answers however the failing installer step is GetInstalledSplunkSettings so maybe I should go digging through the registry to see if stale Product or Installer keys are erroneously causing the installer to try to uninstall nonexistent instances of UniversalForwarder. GetPreviousSettings: Info: Leave GetPreviousSettings: 0x80004005.ĬustomAction GetPreviousSettings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)Īction ended 14:20:23: GetPreviousSettings. GetPreviousSettings: Error 0x80004005: Failed to GetInstalledSplunkSettings. The only thing I did was change the install string to include the following arguments: msiexec.exe /lv splunkinstall.log /i "splunkforwarder-6.2.1-245427-圆4-release.msi" AGREETOLICENSE=YES DEPLOYMENT_SERVER="" /quiet /norestart /qnĭue to the inclusion of the /lv switch I can go to the C:\Windows\CCMcache folder and view the installation log: GetPreviousSettings: Error: DetermineContextForAllProducts failed witht: 0圆5b. I uploaded the MSI file (splunkforwarder-6.2.1-245427-圆4-release.msi) to the SCCM Site Server and let the Detection Method be auto-filled from the MSI. The Deployment Type itself is pretty straight forward. I am attempting to deploy the Splunk UniversalForwarder as an SCCM application using an MSI Deployment Type to a small group of testing servers and am encountering an uncharacteristically confusing issue with the MSI installer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |