Adobe Reader 9.1.3 integrated update problems
Hello again!
Following my previous post on this subject (which, as it turned out, was not a problem!!! [8|]), I've encountered a definite issue this time!!!
So, I've put together an admin install based on this post:
http://itninja.com/link/a-second-record-exists-for-this-alternative-name-here (see notes section, specifically notes by franks)
The scenario:
Our initial workstation image originally went out a few years back, so we've got lots of these still around our site (perhaps 1000). These were originally installed with Reader 8.x. In the meantime, a newer image went out with Reader 9.1.0.
As our users are allowed to have full admin rights over their workstations, they are able to update their Acrobat Reader's when the update window pops up, however, in reality, some users are always updating as soon as the update is made available, other's don't seem to update hardly at all (luckily, we push the Windows updates down so they don't get a choice with those!!!).
As we don't automatically re-image all users when a new image is created (it's more based on whenever they get a new PC, or experience big problems), this has led to a situation, where our workstations (approx. 2000), can have any version effectively of Adobe Reader - from 8.x to 9.1.x.
I built the integrated incremental update install (base 9.1.0 with 9.1.2 and 9.1.3) in the expectation (hope? [:(]) that this would basically update anything that is currently out there, i.e.
Reader 8.x - update to 9.1.3
Reader 9.1.0 > 9.1.2 - update to 9.1.3
Reader 9.1.3 - no update
Having tested this with SMS, it appears that our admin install version will happily update Reader 8.x (tried 8.1.0, 8.1.2, 8.1.6) fine, yet as soon as it encountered any 9.1.x, it fails with the error "Another version of this product is already installed...."
I would have presumed that a 'slip-streamed' 9.1.3 install would still be able to detect an earlier version of Reader 9 (9.1.0 > 9.1.2) and update it, as surely the Upgrade tables in the MSI's would support this - in fact, I've looked at the Upgrade tables in our 9.1.3 integrated admin install and they do have the ness. upgrade codes for 7/8/9.1.x, so I'm confused as to why this doesn't work.
I'm presuming that if I tinker around with the Upgrade tables, I should in effect be able to force this MSI to always upgrade a 9.1.x, but has anyone else suffered with this previously when using integrated updates in admin installs?
[:@]
S
Following my previous post on this subject (which, as it turned out, was not a problem!!! [8|]), I've encountered a definite issue this time!!!
So, I've put together an admin install based on this post:
http://itninja.com/link/a-second-record-exists-for-this-alternative-name-here (see notes section, specifically notes by franks)
The scenario:
Our initial workstation image originally went out a few years back, so we've got lots of these still around our site (perhaps 1000). These were originally installed with Reader 8.x. In the meantime, a newer image went out with Reader 9.1.0.
As our users are allowed to have full admin rights over their workstations, they are able to update their Acrobat Reader's when the update window pops up, however, in reality, some users are always updating as soon as the update is made available, other's don't seem to update hardly at all (luckily, we push the Windows updates down so they don't get a choice with those!!!).
As we don't automatically re-image all users when a new image is created (it's more based on whenever they get a new PC, or experience big problems), this has led to a situation, where our workstations (approx. 2000), can have any version effectively of Adobe Reader - from 8.x to 9.1.x.
I built the integrated incremental update install (base 9.1.0 with 9.1.2 and 9.1.3) in the expectation (hope? [:(]) that this would basically update anything that is currently out there, i.e.
Reader 8.x - update to 9.1.3
Reader 9.1.0 > 9.1.2 - update to 9.1.3
Reader 9.1.3 - no update
Having tested this with SMS, it appears that our admin install version will happily update Reader 8.x (tried 8.1.0, 8.1.2, 8.1.6) fine, yet as soon as it encountered any 9.1.x, it fails with the error "Another version of this product is already installed...."
I would have presumed that a 'slip-streamed' 9.1.3 install would still be able to detect an earlier version of Reader 9 (9.1.0 > 9.1.2) and update it, as surely the Upgrade tables in the MSI's would support this - in fact, I've looked at the Upgrade tables in our 9.1.3 integrated admin install and they do have the ness. upgrade codes for 7/8/9.1.x, so I'm confused as to why this doesn't work.
I'm presuming that if I tinker around with the Upgrade tables, I should in effect be able to force this MSI to always upgrade a 9.1.x, but has anyone else suffered with this previously when using integrated updates in admin installs?
[:@]
S
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
turbokitty
14 years ago
If you don't want to jerk around with that, you could always just create 3 collections, one with each patch version and then create queries that check which version is installed.
After the machine does a hardware inventory, they'll drop out of this collection and automatically appear in your 8.1.4 one.
SELECT SYS.ResourceID,SYS.ResourceType,SYS.Name,SYS.SMSUniqueIdentifier,SYS.ResourceDomainORWorkgroup,SYS.Client FROM SMS_R_System AS SYS WHERE SYS.ResourceID IN (SELECT ARP.ResourceID FROM SMS_G_System_ADD_REMOVE_PROGRAMS AS ARP WHERE ARP.DisplayName = "Adobe Reader 8.1.3" AND ARP.Version = "8.1.3")
After the machine does a hardware inventory, they'll drop out of this collection and automatically appear in your 8.1.4 one.
Posted by:
Bankeralle
14 years ago
I also have problems regarding update computers from adobe 9.0 to 9.3
I made the adobe 9.3 package this way
1. Run an admin install from the orginale adobe.msi
msiexec /a adobe.msi
To patch it up i ran an admin install from the allready adobe.msi which i got from number 1
2. msiexec /a adobe9.0.msi /p "patch 1.2"
3. msiexec /a "adobe9.2" /p patch1.3"
So i got a new adobe.msi which is now version 9.1.3
I make an new mst for this package using the adobe installtailor
When trying to upgrade now(from computers containing adobe 9.0) i get the following message: Another version of this product is already installed...."
Im using the cmdline
msiexec /i adobe9.3 TRANSFORMS=adobe9.3 /qb! ALLUSERS=2
The new adobe9.3 does not contain anyupgradecode from 9.0 to 9.3.
I tried to add the upgradecode to the mst. But if im not mistaken this have to be done to the msi(and i dont want to mess with an native msi right)?
Or is is still an native msi, since i have patched it?
The only way i have found out working is to reinstall previous version and reinstalling the new one!
Is this the only way to do it?
I made the adobe 9.3 package this way
1. Run an admin install from the orginale adobe.msi
msiexec /a adobe.msi
To patch it up i ran an admin install from the allready adobe.msi which i got from number 1
2. msiexec /a adobe9.0.msi /p "patch 1.2"
3. msiexec /a "adobe9.2" /p patch1.3"
So i got a new adobe.msi which is now version 9.1.3
I make an new mst for this package using the adobe installtailor
When trying to upgrade now(from computers containing adobe 9.0) i get the following message: Another version of this product is already installed...."
Im using the cmdline
msiexec /i adobe9.3 TRANSFORMS=adobe9.3 /qb! ALLUSERS=2
The new adobe9.3 does not contain anyupgradecode from 9.0 to 9.3.
I tried to add the upgradecode to the mst. But if im not mistaken this have to be done to the msi(and i dont want to mess with an native msi right)?
Or is is still an native msi, since i have patched it?
The only way i have found out working is to reinstall previous version and reinstalling the new one!
Is this the only way to do it?
Posted by:
anonymous_9363
14 years ago
Be careful with your detail when posting. Those version numbersin the first sentence are clearly incorrect.
Since you have patched 9.1.0 to 9.1.3, they're the same product, as far as the ProductCode is concerned, thus post #3 takes effect - you need to re-install:
EDIT:
Before posting back that the above doesn't work, check out the log (which you should ALWAYS take when testing packages, BTW) in %TEMP%. It will contain hints as to what may have gone wrong.
Since you have patched 9.1.0 to 9.1.3, they're the same product, as far as the ProductCode is concerned, thus post #3 takes effect - you need to re-install:
msiexec /i adobe9.3 TRANSFORMS=adobe9.3 /qb! ALLUSERS=2 REINSTALL=ALL REINSTALLMODE=omus /l*v %temp%\adobe9.3.logEDIT:
Before posting back that the above doesn't work, check out the log (which you should ALWAYS take when testing packages, BTW) in %TEMP%. It will contain hints as to what may have gone wrong.
Posted by:
Bankeralle
14 years ago
ORIGINAL: VBScab
Be careful with your detail when posting. Those version numbersin the first sentence are clearly incorrect.
Since you have patched 9.1.0 to 9.1.3, they're the same product, as far as the ProductCode is concerned, thus post #3 takes effect - you need to re-install:msiexec /i adobe9.3 TRANSFORMS=adobe9.3 /qb! ALLUSERS=2 REINSTALL=ALL REINSTALLMODE=omus /l*v %temp%\adobe9.3.log
Okay i understand, i thought maybe the productuctcode would change when i applied the patch, but obviously not
I will also start using logging more;-)
But i was wondring. What do you guys think is the best way to deploy adobe reader 9.1.3
Again lets say you have aleready installed adobe 9.1.0 on a dozen machines.
Is the best way to simply apply the patch, (then you first have to patch it to 9.1.1->9.1.2->9.1.3). I also read somewhere in the forum that it were problems deploying the patches silently. This would take a shorter time than reinstalling the product i guess, but if adoble launches a bunch og patches in the future(which i guess will happens-it obviously not as smart to do it this way)
Or would you say the best way it patch the msi up and reinstalling the product?
Thx again for all the answers
Posted by:
elgwhoppo
14 years ago
In my opinion, the best way is to use the MSP files that Adobe provides.
Check this TechNote for some more detail.
http://kb2.adobe.com/cps/498/cpsid_49880.html
Check this TechNote for some more detail.
http://kb2.adobe.com/cps/498/cpsid_49880.html
Posted by:
anonymous_9363
14 years ago
Having very recently experienced the glacial speed at which our AIP was patched for Acrobat Professional 9, I'd say the re-install would be an order of magnitude quicker. Thus, patch the AIP then re-install the clients from there.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.