Anybody working yet with QB 2018, I'm attempting to deploy it. I've deployed QB 2015-17 by Extracting the .exe & modifying the .msi to not require the LaunchCondition 

msiexec.exe /i "path to QuickBooks.msi" /t AGREETOLICENSE=Yes QB_LICENSENUM=0000-0000-0000-00 QB_PRODUCTNUM=000-000 INSTALLDESKTOPICONS=0 /norestart

Very Similar to this approach.
http://eddiejackson.net/wp/?p=4508 

Again this approach has worked for the past 3 years, however now when i run the MSI it fails at the license key. But yet when I manually run the setup.exe for the install with the same key it works fine. Weird that this approach no longer works...


3 Comments   [ + ] Show Comments

Comments

  • Any progress on this?
  • Also, VBScab, how is it known that the MSI contains no reference to those properties? How do we determine which properties are available in this MSI?
  • I am having this same issue, but only on Windows 10. This works just fine on windows 7. Sadly our environment is almost entirely windows 10 at this point. I have confirmed that the QB_XXXX properties are still valid.

    Did you ever find a solution?
Please log in to comment

Answers

0
This may be loosely connected to the fact that the MSI contains no reference whatsoever to either of those crucial public  'QB_xxx' properties.

Install it to a VM with logging. That should show you the new property names.
Answered 09/21/2017 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity