I used the MSI Installer Wizard to successfully deploy another MSI before. This time I try to deploy a different application using an MSI (which does work because we have used it in a GPO in the past.). When I push the script it says:

Started: 06/04/2013 14:00:58
Finished: 06/04/2013 14:01:01
Elapsed Time: 3 second
Status: 1

Output Log

Running as: SYSTEM
Checking if registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\MSIWizard\2637' value 'MSIConfigHash' is equal to '1654214127' did not succeed: (0)
Installed: Desktop Capture .NET
Setting registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\MSIWizard\2637' value 'MSIConfigHash' equal to '1654214127' succeeded
Desktop Capture .NET installed with C:\Windows\System32\msiexec.exe /qn   /i dcsetup.msi
Checking if registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\MSIWizard\2637' value 'MSIConfigHash' is equal to '1654214127' succeeded

Activity Log

Checking if registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\MSIWizard\2637' value 'MSIConfigHash' is equal to '1654214127'
Setting registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\MSIWizard\2637' value 'MSIConfigHash' equal to '1654214127'
Checking if registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\MSIWizard\2637' value 'MSIConfigHash' is equal to '1654214127'


Can someone please help. I am trying to get this application to deploy through Kace. Although it works with a GPO I would like to use Kace for everything. Thanks

2 Comments   [ + ] Show Comments


  • Have you tried deploying the software using Distribution instead of Scripting?
  • I have tried both ways of pushing the software
Please log in to comment

Community Chosen Answer


Verify if the propery ALLUSERS is set to "1" in the package.

Answered 06/05/2013 by: terebent
Brown Belt

  • Where would I find the ALLUSERS property? I am not currently looking at Kace. Thanks
  • You have to edit the MSI and the you will find the ALLUSERS property in the Property table.
    • This is the only place I find ALLUSERS in the xml file for the msi:
      - <DirectoryList>
      - <Directory Name="%WINDIR%\System32\catroot2">
      <File Name="edb.chk" />
      - <Directory Name="C:\Users\All Users\Wave Systems Corp\Trusted Drive">
      <File Name="tdm_log_000001.txt" />
      - <Directory Name="C:\Users\All Users\Microsoft\Search\Data\Applications\Windows">
      <File Name="MSS.chk" />
      - <Directory Name="C:\Users\All Users\Dell\KACE">
      <File Name="amp.log" />
      - <Directory Name="%ALLUSERSPROFILE%\Wave Systems Corp\Trusted Drive">
      <File Name="tdm_log_000001.txt" />
      - <Directory Name="%ALLUSERSPROFILE%\Microsoft\Search\Data\Applications\Windows">
      <File Name="MSS.chk" />
      - <Directory Name="%ALLUSERSPROFILE%\Dell\KACE">
      <File Name="amp.log" />
  • Check the Property table in MSI. Or you can add the property ALLUSERS=1 in installation command line: msiexec /i nam.msi ALLUSERS=1 /QB!
  • looks to me like i set it up correctly yet it still does not install. this is the info i have for the install:
    1. Verify that “HKLM\SOFTWARE\Kace\MSIWizard\2637!MSIConfigHash†is equal to “464069388â€.

    1. Install “Desktop Capture .NET†with arguments “$(KBOX_SYS_DIR)\msiexec.exe /qn /norestart /l* â€Destop Capture.txt“ /i â€Desktop Capture.msi“ ALLUSERS=1 /QB! â€.
    2. Set “HKLM\SOFTWARE\Kace\MSIWizard\2637!MSIConfigHash†to “464069388â€.

    On Remediation Success:
    1. Log “Desktop Capture .NET installed with $(KBOX_SYS_DIR)\msiexec.exe /qn /norestart /l* â€Destop Capture.txt“ /i â€Desktop Capture.msi“ ALLUSERS=1 /QB! †to “outputâ€.

    On Remediation Failure
    1. Log “Desktop Capture .NET FAILED to install with $(KBOX_SYS_DIR)\msiexec.exe /qn /norestart /l* â€Destop Capture.txt“ /i â€Desktop Capture.msi“ ALLUSERS=1 /QB! †to “outputâ€.
  • What the log says? Is the installation succeeded or not?
Please log in to comment



Is this a per machine or per user installation? What is the value of ALLUSERS?

Answered 06/04/2013 by: SnowLyric
Second Degree Brown Belt

Please log in to comment

First off, when you doing the install, be sure to create a log file.  I always dump it into the C:\ on test installs. This will tell you what's happening with the install.  It is as simple as:

/L*v c:\suchandsuchlog.txt

Second, it doesn't seem like you are telling it to wait until complete before moving between steps.  What the Output Log is saying is that it is checking to see if it is installed  via registry, if not, it begins the install and immediately updates the registry.  Since the install if going to take longer than it takes to update the registry, it gets updated regardless.  Then, if the install screws up, the registry was already changed and program wasn't installed.

If you tell it to wait between steps, it usually won't update the registry until the install step is finished (if ever). 

As far as why it isn't installing, I'd need to see the log file.  But the ALLUSERS mentioned in other answers is a good idea, though


Answered 06/06/2013 by: gcarpenter
Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja