Silent Install of PDF Converter Professional 6
Having an issue with a SCCM silent install, if deployed over an older (5, 5.2) version.
The install stops, and times out, so, I removed the /qb to see what was happening, and, this message is popping up: "An older version of Nuance PDF Professional or Nuance PDF Create! is already installed on this computer. If you want to upgrade select OK button. To cancel installation select Cancel.".
I need to set the MST to force an install over the older version, rather than ask for a choice (which, in System context, the user will never see).
I found in the Property table the property "CHKUPGRADE" that was set to "1", I tried setting that to "0", but, now I get a prompt for the location of the original installation source MSI (which, no longer exists).
Soooo...don't know if there is a better way to do this, and, if I put the older versions' MSI files in the same folder as the new version, will it just find them, and, uninstall, if that has to happen?
Thanks!
The install stops, and times out, so, I removed the /qb to see what was happening, and, this message is popping up: "An older version of Nuance PDF Professional or Nuance PDF Create! is already installed on this computer. If you want to upgrade select OK button. To cancel installation select Cancel.".
I need to set the MST to force an install over the older version, rather than ask for a choice (which, in System context, the user will never see).
I found in the Property table the property "CHKUPGRADE" that was set to "1", I tried setting that to "0", but, now I get a prompt for the location of the original installation source MSI (which, no longer exists).
Soooo...don't know if there is a better way to do this, and, if I put the older versions' MSI files in the same folder as the new version, will it just find them, and, uninstall, if that has to happen?
Thanks!
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
gmouse
14 years ago
Thanks, Dnmech, but...not quite sure how to do that, or, where to put it. I'm pretty rank amateur at this, but, have done some MST's a few times.
I'm using a Task Sequence in SCCM to do the install and some other things, so, I thought about just using some uninstall tasks, and just uninstall the other versions, if they exist (or not, I guess?).
I'm using a Task Sequence in SCCM to do the install and some other things, so, I thought about just using some uninstall tasks, and just uninstall the other versions, if they exist (or not, I guess?).
Posted by:
dnmech
14 years ago
U just need to browse the older msi in the Upgrades section (in Installation Expert).If u r using wise package studio.It will automatically take the upgrade code. So when u will install the new msi with mst, it will uninstall the older version and install itself. .
Try this, if it works.
Cheers!
Try this, if it works.
Cheers!
Posted by:
gmouse
14 years ago
I will amaze you with how newbie I am...<G>
Following the instructions, you do an Admin Install (setup.exe /a) of the product to a folder or share, making desired install settings (nothing about upgrading or uninstalling, just usability settings), and this creates the MST.
I'm using Orca to view and edit the newer product's MSI as transformed by the MST, but, don't have a packaging product (could use Admin Studio-SCCM Edition, I guess).
Here is the older (version 5.2, there is also a 5.0) product's UPGRADE table:
UpgradeCode
VersionMin
VersionMax
Language
Attributes
Remove
ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA}
5.20.0000
99.99.9999
514
NEWPRODUCTFOUND2
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A}
2.00.0000
5.20.0000
256
OLDCONVFOUND1
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A}
5.20.0000
99.99.9999
514
NEWCONVFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E}
1.00.0000
5.20.0000
256
UPGRADEFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E}
5.20.0000
99.99.9999
514
NEWPRODUCTFOUND1
{FD2DDC5A-FCA4-44F3-BCBE-F43F0C988330}
1.00.0000
2.00.0000
256
OLDCONVFOUND2
Here is the newer one (6.0):
UpgradeCode
VersionMin
VersionMax
Language
Attributes
Remove
ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA}
6.00.0000
99.99.9999
514
NEWPRODUCTFOUND2
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A}
2.00.0000
6.00.0000
256
OLDCONVFOUND1
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A}
6.00.0000
99.99.9999
514
NEWCONVFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E}
1.00.0000
6.00.0000
256
UPGRADEFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E}
6.00.0000
99.99.9999
514
NEWPRODUCTFOUND1
{FD2DDC5A-FCA4-44F3-BCBE-F43F0C988330}
1.00.0000
2.00.0000
256
OLDCONVFOUND2
Is it as simple as copying a row from the old table to the new one?
Thanks...REALLY do appreciate this!
Following the instructions, you do an Admin Install (setup.exe /a) of the product to a folder or share, making desired install settings (nothing about upgrading or uninstalling, just usability settings), and this creates the MST.
I'm using Orca to view and edit the newer product's MSI as transformed by the MST, but, don't have a packaging product (could use Admin Studio-SCCM Edition, I guess).
Here is the older (version 5.2, there is also a 5.0) product's UPGRADE table:
Here is the newer one (6.0):
Is it as simple as copying a row from the old table to the new one?
Thanks...REALLY do appreciate this!
Posted by:
gmouse
14 years ago
Hmm...looked PERFECT (just like the table, or a spreadsheet) when I posted...<G>
Here's raw text from notepad:
Old (5.2):
UpgradeCode VersionMin VersionMax Language Attributes Remove ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA} 5.20.0000 99.99.9999 514 NEWPRODUCTFOUND2
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 2.00.0000 5.20.0000 256 OLDCONVFOUND1
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 5.20.0000 99.99.9999 514 NEWCONVFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 1.00.0000 5.20.0000 256 UPGRADEFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 5.20.0000 99.99.9999 514 NEWPRODUCTFOUND1
{FD2DDC5A-FCA4-44F3-BCBE-F43F0C988330} 1.00.0000 2.00.0000 256 OLDCONVFOUND2
New (6.0):
UpgradeCode VersionMin VersionMax Language Attributes Remove ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA} 6.00.0000 99.99.9999 514 NEWPRODUCTFOUND2
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 2.00.0000 6.00.0000 256 OLDCONVFOUND1
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 6.00.0000 99.99.9999 514 NEWCONVFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 1.00.0000 6.00.0000 256 UPGRADEFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 6.00.0000 99.99.9999 514 NEWPRODUCTFOUND1
{FD2DDC5A-FCA4-44F3-BCBE-F43F0C988330} 1.00.0000 2.00.0000 256 OLDCONVFOUND2
Here's raw text from notepad:
Old (5.2):
UpgradeCode VersionMin VersionMax Language Attributes Remove ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA} 5.20.0000 99.99.9999 514 NEWPRODUCTFOUND2
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 2.00.0000 5.20.0000 256 OLDCONVFOUND1
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 5.20.0000 99.99.9999 514 NEWCONVFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 1.00.0000 5.20.0000 256 UPGRADEFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 5.20.0000 99.99.9999 514 NEWPRODUCTFOUND1
{FD2DDC5A-FCA4-44F3-BCBE-F43F0C988330} 1.00.0000 2.00.0000 256 OLDCONVFOUND2
New (6.0):
UpgradeCode VersionMin VersionMax Language Attributes Remove ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA} 6.00.0000 99.99.9999 514 NEWPRODUCTFOUND2
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 2.00.0000 6.00.0000 256 OLDCONVFOUND1
{5BE975EB-80F1-4557-AD9D-4C5B50DD397A} 6.00.0000 99.99.9999 514 NEWCONVFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 1.00.0000 6.00.0000 256 UPGRADEFOUND1
{68E4090E-5068-4430-A6BA-688E8D0D2A4E} 6.00.0000 99.99.9999 514 NEWPRODUCTFOUND1
{FD2DDC5A-FCA4-44F3-BCBE-F43F0C988330} 1.00.0000 2.00.0000 256 OLDCONVFOUND2
Posted by:
dnmech
14 years ago
I am nt well versed with Orca [8|]. But i can try.
In the new msi add a row in the Upgrade coloumn, which looks like
UpgradeCode VersionMin VersionMax Language Attributes Remove ActionProperty
{4C2C815B-A858-4584-863A-AE6E634E2FFA} 5.20.0000 6.00.0000 256 OLDCONVFOUND1
Try this.
In the new msi add a row in the Upgrade coloumn, which looks like
UpgradeCode VersionMin VersionMax Language Attributes Remove ActionProperty
Posted by:
gmouse
14 years ago
One last question, before I try this...
The older versions were installed with SCCM, also, but, are no longer available on the servers. When I did a manual test of installing the new version, when it got to the point of wanting to uninstall the old one, it also wanted to go to the previous location (the actual install source, as stored in the Registry).
If I put the old product's MSI's in the same folder as the new product, is there some way to tell the program to point to that new location, rather than take the Registry's location as the first choice?
Thanks so much for all your help and ideas! I will try them later today, and, post the results.
The older versions were installed with SCCM, also, but, are no longer available on the servers. When I did a manual test of installing the new version, when it got to the point of wanting to uninstall the old one, it also wanted to go to the previous location (the actual install source, as stored in the Registry).
If I put the old product's MSI's in the same folder as the new product, is there some way to tell the program to point to that new location, rather than take the Registry's location as the first choice?
Thanks so much for all your help and ideas! I will try them later today, and, post the results.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.