/build/static/layout/Breadcrumb_cap_w.png

Quickbooks 2004 HELP!

Is there a way to script a Quickbooks installation through SMS 2003 that will delete the intuit printer AND license the software?



I have been trying to repackage it into an MSI from a Ghost Package. However when I run the program on a test machine it doesn't pop up.


HELP!

0 Comments   [ + ] Show comments

Answers (4)

Posted by: jmcfadyen 17 years ago
5th Degree Black Belt
0
i did some older version of their software.

I did notice back then they stored the serial numbers in plain text in the registry under HKCU\software\intuit

At the time I wasn't packaging with MSI so I recall having to dodgy up the HKCU registry for all users.

but now they are msi so what are you doing with ghost packager ?
Posted by: vjmeh 17 years ago
Senior Yellow Belt
0
I work at a community college that unforunately has a very strained IT budget. We have been using Qbooks 2004 Pro and there are no plans to upgrade anytime soon. At this point my only option is to repackage via MSI. We have a ghost package that installs the software.
Posted by: vjmeh 17 years ago
Senior Yellow Belt
0
UPDATE!


I was able to run the install using the installshield setup.exe /r command to record to setup.iss.


So I have solved half of my dilemma. It's using an Installshield 6.3 Setup. I browsed the setup.iss file and saw the serial in the file. I also noticed a setup.inx file. Apparently if I can decompile this and remove the intuit printer install my only hurdle will be somehow slipstreaming the Release 11 update.


If I can solve the intuit printer problem I wonder if I can run the setup script in SMS and have it run the Release 11 update AFTER the initial install. My only issue beyond that is Quickbooks autoupdate feature built in the software. This is where I wonder if I should take the long tedious route of capturing the installation into an MSI so that all changes are covered.
Posted by: vjmeh 17 years ago
Senior Yellow Belt
0
After much hassle I finally captured an MSI of Quickbooks. The only caveat is that the end user must be in the Power Users or Administrator Group to run. Nonetheless the nightmare is over...I HOPE!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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