Quickbooks Pro 2011 Deployment failure
Hi I am trying to deploy the Quickbooks Pro 2011 into 200 machines. For silent installation I am using these swiches,
“setup.exe†/s /v CKBOX_GDS=0 AgreeToLicense=Yes MULTIUSERINSTALL=1 QB_LICENSENUM=xxxx-xxxx-xxxx-xxx QB_PRODUCTNUM=xxx-xxx /qn
If i run the above mentioned switches its instaling partially- but no error messages,
If I run the unattended, it only partially installs – but no error messages.
Database manager installs, but QB doesn’t. This means the main shortcut is not coming. The files are copied over, but it doesn’t show up in Add/Remove, and if I run the executable, it errors and instructs me to do a repair.
If I run the same msi, and manually put in the same options, it installs fine.
Any thoghts??
“setup.exe†/s /v CKBOX_GDS=0 AgreeToLicense=Yes MULTIUSERINSTALL=1 QB_LICENSENUM=xxxx-xxxx-xxxx-xxx QB_PRODUCTNUM=xxx-xxx /qn
If i run the above mentioned switches its instaling partially- but no error messages,
If I run the unattended, it only partially installs – but no error messages.
Database manager installs, but QB doesn’t. This means the main shortcut is not coming. The files are copied over, but it doesn’t show up in Add/Remove, and if I run the executable, it errors and instructs me to do a repair.
If I run the same msi, and manually put in the same options, it installs fine.
Any thoghts??
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
mahendraKumar
12 years ago
Posted by:
spartacus
12 years ago
ORIGINAL: srikanth.deep@hotmai
Hi I am trying to deploy the Quickbooks Pro 2011 into 200 machines. For silent installation I am using these swiches,
“setup.exe†/s /v CKBOX_GDS=0 AgreeToLicense=Yes MULTIUSERINSTALL=1 QB_LICENSENUM=xxxx-xxxx-xxxx-xxx QB_PRODUCTNUM=xxx-xxx /qn
If i run the above mentioned switches its instaling partially- but no error messages,
If I run the unattended, it only partially installs – but no error messages.
Database manager installs, but QB doesn’t. This means the main shortcut is not coming. The files are copied over, but it doesn’t show up in Add/Remove, and if I run the executable, it errors and instructs me to do a repair.
If I run the same msi, and manually put in the same options, it installs fine.
Any thoghts??
Did you try enclosing the parameters you are passing to the MSI in double quotes ?
In other words
setup.exe /s /v
Spartacus
Posted by:
anonymous_9363
12 years ago
You have 200 accountants?!? Your office parties must be fun...
The '/V' switch shows that the stub is passing parameters to MSIExec which in turn means that there must be an MSI. Use that.
You'll need to create a transform if you want to alter the 'AgreeToLicense' property unless it's a public property (i.e. all in upper-case). As it is, the property value you've used will be ignored, since it's not a public property. You can obviously include the other property values in that transform.
If you still have problems when the MSI/MST is executed silently, check for any Custom Actions that appear in the UI sequence but not in the ExecuteImmediate sequence. Copy any missing ones over.
Lastly, unless you have WI logging enabled using Group Policy, always specify a log file, using the '/V* [path_to_and_name_of_log_file]' switch as, without a log, troubleshooting will be total guesswork.
The '/V' switch shows that the stub is passing parameters to MSIExec which in turn means that there must be an MSI. Use that.
You'll need to create a transform if you want to alter the 'AgreeToLicense' property unless it's a public property (i.e. all in upper-case). As it is, the property value you've used will be ignored, since it's not a public property. You can obviously include the other property values in that transform.
If you still have problems when the MSI/MST is executed silently, check for any Custom Actions that appear in the UI sequence but not in the ExecuteImmediate sequence. Copy any missing ones over.
Lastly, unless you have WI logging enabled using Group Policy, always specify a log file, using the '/V* [path_to_and_name_of_log_file]' switch as, without a log, troubleshooting will be total guesswork.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.