/build/static/layout/Breadcrumb_cap_w.png

Quickbooks 2018 Deployment.

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...


Asked 7 years ago 10387 views
3 Comments   [ + ] Show comments
  • Any progress on this? - janthenat 7 years ago
  • 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? - janthenat 7 years ago
  • 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? - jezzec 7 years ago

Answers (3)

Posted by: anonymous_142439 6 years ago
White Belt
1

Been using http://virtualapppack.com/?p=33 as a reference for the past couple versions Enterprise 2014-2016, but ran into the same issue as the OP with 2018 not accepting the properties that worked for the last 3 version. I ended up checking the commands in the QuickBooks_18.log during the full normal test install and saw that the 2018 installer passes a few more properties to the Quickbooks.msi file. After that it installs normally and activated fine as well.  Hope this helps someone.

Used Orca to place the following Properties (Had to add the last 5 properties to my MST to get 2018 Enterprise to work):

See Imgur Link: https://imgur.com/0mVLubW


Comments:
  • I am using Orca to modify the QB 2018 msi in order to roll it out via group policy. The installer runs successfully on Win7 and Win8 computers, and the app runs without issues. The installer runs on Win10 computers, but when the app is launched, I get a PS107 error, indicating a corrupt file. I am hoping the properties you discovered and added will resolve this, but I'm hoping you could assist me in deciphering them from the large paragraph as it is displayed on this page. Thank you in advance for any assistance you can provide. - Wyzguy 6 years ago
    • Try the link I added instead. Couldn't get the table to format the properties correctly. - anonymous_142439 6 years ago
      • What are those additional fields you are adding in such as LICENSENUMBER_BEL and INSTALLID_BEL, are those the license and product number? If so the previous tutorial for this from eddiejackson already has fields for that. - zero1 6 years ago
    • I have been gettinh the PS107 error on previous versions in windows 10 and find that he only way to resolve the error is to manually click ok each time it pops up until it stops (10+ times sometimes) and then open a sample company file once or twice, seems that after its been open for a bit and maybe aauto updates in the background that the next time QB is launched the ps107 error will not come back...though sometimes I have to go through the process twice...sort of defeats the purpose of auto deploying it, but then again, i have to log onto each computer once anyway to register the product (havent figured out how to automate that part yet). - ahuston@roguecc.edu 6 years ago
  • The PS107 error happens when the Quickbooks installer was not run as an administrator. I had this problem when using SCCM to install the program because it was running as system instead of administrator. I had to create a package that delivered the installation files and a batch file. I then had to set the batch file to run as administrator after it was delivered.
    msiexec /i"%~dp0\QuickBooks.msi" TRANSFORMS="QuickBooks.mst" /qb - mteehee 5 years ago
Posted by: anonymous_9363 7 years ago
Red Belt
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.
Posted by: RHuseby 6 years ago
White Belt
0
The answer from enigmaxp (https://imgur.com/0mVLubW) worked for me, the problem then was the SCCM uninstall not working. I finally got it to work with this as the uninstall command... (change version specific info to match your version)

msiexec.exe /X {48011BF6-E0BC-4B49-9DCA-C7144EF0C01E} UNIQUE_NAME="accountant" QBFULLNAME="QuickBooks Premier: Accountant Edition 2018" ADDREMOVE=1


 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ