I am trying to install this Event Management System via KACE managed installation. It is a single .MSI file that after it installs it needs a server and database name to be entered upon first open. After you enter that info it saves them in two REG keys. I have located those keys so I figured I could create a BAT file to install the program and then do a REG ADD to create those keys. If i have the MSI and the BAT file on the local machine and double-click on the BAT file it runs perfectly. I zipped them together and created a managed install in KACE. When KACE installs it, it installs the program but does not create the REG keys. When ran locally it creates the main REG location during the program install, but when installed via KACE it does not create that REG location until I open the program for the first time. Then I decided to see if i could modify the MSI to create the database and server REG keys during the install. I opened it with ORCA and added everything in and when I run it locally it installs and populates the server and database REG keys so there is no post-install setup needed. When I have KACE install this new MSI, it installs but does not create those REG keys. I am looking for any ideas/help as I have a department that wants to mass deploy this software.

Thanks in advance!

 

Seth

Answer Summary:
I finally go this to work. I ended up just uploading the stock MSI and created a managed install and then using the MSI Installer wizard to create a scripted install that installed the managed install and then created the needed REG keys. I appreciate everyone's help/feedback on this! Seth
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1

Seth,

Redownload the MSI you modified from the K1000 under the software inventory record you uploaded it to.  Open that file with ORCA and make sure that the changes are there.  I have seen where a file with the same name may not upload correctly over another.  Re-upload the file with a different filename and try the Managed installation again.  

Alternatively you could use an Online Kscript to isntall as a particular user.  

Brandon

Answered 12/07/2012 by: WhitzEnd
Seventh Degree Black Belt

Please log in to comment

Answers

0

Could it be creating the keys in the 64 bit vs the 32 bit registry hive

http://social.msdn.microsoft.com/Forums/en/netfx64bit/thread/da055767-0f69-4f07-b8e7-f3dce19f7ecb

Answered 12/08/2012 by: jdornan
Red Belt

  • That is a good point. Check the Wow6432Node section to confirm.
  • it does not appear to be putting anything in that location.
Please log in to comment
0

I'm guessing that the registry data is being written to HKCU rather than HKLM? Have you tried with an HKLM entry instead? Most well-written apps will check HKCU first and then HKLM.

Also, WI will handle registry data perfectly well, there should never be a need to resort to command file hacks using REG (or whatever).

Answered 12/10/2012 by: VBScab
Red Belt

  • When I manually install the program it creates the reg keys in HKCU and no other location.
  • I found that the reg keys from my managed install are getting created in HK_USERS\.DEFAULT\Software\Dean Evans and Associates\ instead of HKCU\Software\Dean Evans and Associates\. Must be due to it being run as 'SYSTEM' via KACE. Any ideas?
  • Could you share the reg add command you are using? I would like to see where it is pointing too. This definitely sounds like the issue.
  • REG ADD "HKCU\Software\Dean Evans and Associates\Version 43" /v Database /t REG_SZ /d EMS /f

    The above is run in my BAT file after the installation of EMS. I believe it is not working because KACE installs as 'SYSTEM' so I think it is putting the REG keys under the HKCU for the 'SYSTEM' account.
  • Yes, HKCU installs for the current user only which would be system
Please log in to comment
0

Try to install as a users A check that you have needed keys and then log in as a user B and check for those key again. If they are not there then it a per user install. And you will need to selfheal your application. If you are installing as a system "or cmd windows as a system and install" your per user components will not be available to a user. Google selfheal i think there are 5 different ways you can triger a selfheal. Shortcut, activesetup, com object, and few more.

Answered 12/10/2012 by: ogeccut
Black Belt

  • I will give this a try and let everyone know what I find. Thanks!
Please log in to comment
Answer this question or Comment on this question for clarity