Copy link to clipboard
Copied
We originally deployed Acrobat Pro 10.0.3. We created an AIP using 10.0 and the 10.0.3 MSP file. Now that 10.1 is out, we would like to update our machines. I was reading the enterprise guide and from my initial understanding, it seems we need to deploy Acrobat to every user--we can't just push out an update. Is this correct? Is there no way to simply push out the MSP file to have the machines update to the latest version? Thanks!
Copy link to clipboard
Copied
Here's a follow up question, with my current work flow and understanding:
Acrobat is installed to machines via GPO pointing to an AIP.
When there is a patch, the patch is applied to a fresh 10.0 AIP, the old AIP is replaced, and the GPO is set to 'redeploy'. This in effect uninstalls the previous instance of the software, and installs the new version in it's place.
It works, but requires keeping or making a new 10.0 AIP to patch each time (a minor annoynce), the time to completely uninstall and reinstall Acrobat, and the network traffic to completely reinstall a 1+ GB application to every machine that has Acrobat installed.
Some people put out command lines that would install a msp to a previous installation. Can this command line be integrated into the same GPO, such that the patch is applied via GPO to those machines it is already applied to?
If not, what method is being used to run this command line on all pertinant machines, given that there is no guarantee that each machine will be online or available at any given instance (even better, it is possible, say if it were a laptop, that the machine may not be online for a month or more).
Using the first 'Full Reinstallation from a patched AIP' method is ugly, but works as a 'set it and forget it' method. Can the 'command line patch' be set up in a 'set it and forget it' manner as well?
Reading through the Enterprise Deployment Guide, using the AIP is the only method mentioned in the GPO section. So, anyone 'moving away from an AIP model', how do you accomplish this (or 'how do you accomplish this without additional software such as SCCM, which would be a whole new ball of wax with it's own problems, at least from what I've already read in this thread, and a huge overhead to implement to take care of the very few applications we would need it for).
Thanks for the input!
Copy link to clipboard
Copied
Brape, Cumulative. So, I just need the 10.0.0 MSI and the lastest Quarterly which is currently 10.1.1 if I understand that correctly. I plan on only updating quarterly as it is a pita right now.
Can you also post the vbs script to uninstall 10.1.0 or any version. I can do the uninstalls via bat file but I'm no good at vbs.
xxpluckyxx, We have ~ 600 users so SCCM is extremely helpful in deploying apps. I also use it for reporting and quick software/hardware inventory querys. Depending on the number of users you work with, you might want to give it a try in a test lab.
Copy link to clipboard
Copied
Hi rdw,
you got that right, 10.1.1 is the only update you need right now. The next quarterly update will replace this one.
Here is the uninstall script.
if Wscript.Arguments.Count = 1 Then
Set sho = Wscript.CreateObject("Wscript.Shell")
strCommand = "C:\Windows\System32\msiexec.exe /X" & Wscript.Arguments(0) & " /norestart /qn"
intRet = sho.run(strCommand,0,True)
If intRet = 3010 Then
intRet = 0
End If
Else
intRet = 0
End If
wscript.quit(intRet)
Copy link to clipboard
Copied
It is interesting what I read in this forum.
A little question only: Has anyone ever installed acrobat 9.1.0 on an standalone machine where automatic updates are available? I have done this and then I searched for available updates. And in deed the updater found some updates (9.1.1) and I installed them sucessfully (the system told me at least)! After a reboot of the machine I checked the version of the installed version of acrobat. Result: installed version is still 9.1.0?!!! Adobe is declaring update 9.1.1 as security update. Can somebody tell me how to install a security update over version 9.1.0 if even the installer can’t?
Copy link to clipboard
Copied
Download the update from ftp://ftp.adobe.com/pub/adobe/acrobat/win/9.x/ and install it yourself.
Ben
Copy link to clipboard
Copied
Sorry, in my posting I mistook 9.x with 10.x. But the question leaves the same...
Copy link to clipboard
Copied
Does anyone have a good working uninstall script? One which will uninstall all version of Adobe Pro 10.x and all previous version 9.x too.
I tried the one Brape33 posted above but I don't understand on how it would work as I don't see how it could tell what to uninstall.
It also appears that Adobe Pro version 10.0.0, 10.0.1, 10.1.0 and 10.1.1 all have the same GUID listed in the registry for UNINSTALL.
That might be the reason why my transform which is setup to uninstall all previous installations does not uninstall my 10.1.0 installs.
I googled and ran across this which is about 60% successful. 60% isn't good enough. In addition no log file to determine why some are not uninstalling.
strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colSoftware = objWMIService.ExecQuery _
("Select * from Win32_Product Where Name LIKE 'Adobe Acrobat%'")
For Each objSoftware in colSoftware
objSoftware.Uninstall()
Next
Thoughts? Thanks.
Copy link to clipboard
Copied
Hi rdw556
Using Wise Script this is really no problem. With Wise Script I read HKLM\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-1033-F400-7760-000000000005} and get the value of DisplayVersion. If this value equals 10.1.0 the respective MSI will be uninstalled (msiexec.exe /x [AC76BA86-1033-F400-7760-000000000005]). The script shows like
Get Registry Key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-1033-F400-7760-000000000005} place in Variable ACROBATX
If ACROBATX Equals "10.0.3" then
Execute %sys32%\msiexec.exe /x {AC76BA86-1033-F400-7760-000000000005} /qb! (Wait)
end
This can be done for each version of acrobat. Btw 9.x will be uninstalled by the installer himselve during the installation of 10.x
Hope this will help.
Copy link to clipboard
Copied
Another reason to get Wise though me and one other would have to learn how to properly use it.... and this isn't our primary job. lol.
Any way that can be done in normal VBS scripting?
On a simlary note, any website showing all previous GUID's for Adobe Pro from 9 to now?
Copy link to clipboard
Copied
Hi rdw556
The similar VB-Script to the described Wise Script above could be as follows:
const HKEY_LOCAL_MACHINE = &H80000002
strComputer = "."
'Wscript-Objects
Set StdOut = WScript.StdOut
Set WshShell = WScript.CreateObject("WScript.Shell")
'Registry via WMI
Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv")
'Variables
strKeyPath = "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-1033-F400-7760-000000000005}"
strValueName = "DisplayVersion"
'The key is written to strValue
oReg.GetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
'Check and Uninstall
If strValue = "10.1.1" Then
Return = WshShell.run("msiexec /x {AC76BA86-1033-F400-7760-000000000005} /qb",1,True)
Else
StdOut.WriteLine "no installed software found!"
End If
This should uninstall acrobat X (10.1.1) if installed. Please copy the script lines in a text file and rename it to .vbs.
Regards
Copy link to clipboard
Copied
Hi rdw,
the script i posted is easy to use. You just have to bypass the Product ID of the software you want to uninstall. Usage is like "cscript uninstall.vbs {GUID}". The benefit is that you don't have to create a new package, or updating your distribution points, when you are using SCCM. Just create one package with a unlimited number of uninstall programs for several products. In SCCM you have also the ability of task sequences to run WMI queries on your local machines. So you can test for any installed version with the Win32Reg_AddRemovePrograms class and if the condition is met run the appropriate uninstall.
Copy link to clipboard
Copied
I've read all the replies and am still totally confused! We've pushed 10.0.0 and installed successfully using SCCM on test machines. In our Oracle environment we HAVE to have patch 10.1.1 installed. What I want to do is create SCCM advertisement to push patch but run the 10.0.0 install first. Seems this would be easy enough in SCCM but it doesn't work. So, I can push 10.0.0 in one advertisement. I created the SCCM advertisement for the patch using the .MSP but it is not installing on the machines. I can't find the kink and do not have admin rights to our SCCM server to see logs. Questions:
Can I use SCCM to push an MSP?
What logs do I need to ask for to find the problem?
Thanks,
Julie
Copy link to clipboard
Copied
Hi Julie,
it's pretty easy to deploy with SCCM, as long it's a clean installation without any previous version on the machine. You need to create 2 packages in you SCCM environment. First one the base msi of version 10.0.0 with your customization. Create a second package with the latest patch, in this case the mst for version 10.1.1. Make sure you get the right language version for your product, or the installation will fail. The installation call for the patch is "msiexec /p mstname /norestart /qn" and if you want to write a log file "msiexec /p 'mstname' /L*v 'pathtolog\logfilename' /norestart /qn".
Next create a task sequence with 2 steps, for the installation of the msi and the mst. Of course you could also put the mst into the same folder as the msi an slipstream it during the installation. But you would have to update the distribution points every time a new patch arrives. I prefer the single package method because it will reduce the network traffic in the WAN.
Copy link to clipboard
Copied
Ah! Thanks for the info brape33. We did find the 10.0.0 does remove any previous installation automatically. If I understand your installation call for the patch mine will look like "msiexec /p AcrobatUpd1011.msp /norestart /qn" correct?
Copy link to clipboard
Copied
Hi Julie,
yes, that's the correct comand line.
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more