Depends on a few things. Are you using SCCM 2012 or 2007? Are there any existing installations of previous versions on your clients?
With SCCM 2007 i was using a tasksequence with 3 steps.
- uninstall old versions (script) - WMI Query if any reader version lower than 10 is installed
- install 10.1 (package) - WMI Query if no reader is installed
- update 10.1.3 (package) - WMI Query if version 10 is installed and version not 10.1.3
You only need the latest patch, which is 10.1.4 by now.
the TS looks like this.
Step 1: uninstall old Reader Versions
WMI Query : (root\cimv2\sms)
if all of the conditions are true
Select * From SMS_installedSoftware Where ProductName Like '%Adobe%Reader%' And Not ProductVersion Like '10.%'
... running the following script
strComputer = "."
intRet = 0
Set sho = Wscript.CreateObject("Wscript.Shell")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2\sms")
Set colItems = objWMIService.ExecQuery("select * from SMS_InstalledSoftware where ProductName Like '%Adobe%Reader%' And Not ProductVersion Like '10.%'",,48)
For Each objItem in colItems
strVersion = objItem.ProductVersion
prodCode = objItem.ProductCode
strCommand = "C:\Windows\System32\msiexec.exe /X" & prodCode & " /norestart /q"
intRet = sho.run(strCommand,0,True)
If intRet = 3010 Then
intRet = 0
Step 2 : Install Adobe Reader 10
WMI Query : (root\cimv2\SMS)
if none of the condidions are true
Select * From SMS_installedSoftware Where ProductName Like '%Adobe%Reader%'
Step 3: Install Adobe Reader Update 10.1.4
WMI Query: (root\cimv2\SMS)
if all of the conditions are true
Select * From SMS_installedSoftware Where ProductName Like '%Adobe%Reader%' And ProductVersion Like '10.%' And ProductVersion != '10.1.4'
Thank you so much
Sorry for not getting back to you earlier but patching is always seems to be a back burner issue when the front burners are on fire!
I put the TS sequence together, the first part is a little hard to see if its working because i had already rolled out 10.0.1 AIP which i then patched to 10.1.0 as the base install. Now that i want to patch it to 10.1.4 i get this message;
"The upgrade patch cannot be installed by the Windows installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch"
I think i came across one of your post commenting on you not installing AIP anymore, in any case I've been deploying Reader since v7 and every version is still a nightmare for patching.
If you have any suggestions I would much appriciate it.
you can not patch AIP installations on your clients directly with the MSP file. AIPs are pretty useless now because you even cant apply the patch to the AIP that has been patched already with a former update. You could create a competely new AIP and apply 10.1.4. But think about the workload you have to go through for every single patch.
The best thing you can do is to add a step to your task sequence and detect any installation that is not version 10.1.4. and uninstall it.
In the next step install the 10.1.0 MSI with you transforms file. And as a third step install the 10.1.4 update.
Of course this will take a while this time, but saves you a lot of pain for all coming updates. You also need to remove the uninstall step for the next update (10.1.5?).
If you have configured SCCM as update point and do you patching with SCCM intead of WSUS, you can use the System Center Update Publisher to integrate the Adobe products into the update services.
Here is a good guide how to do that.
Always seem to find out too late that software developers changed their deplyment methods - so into the toilet for AIP
I looked at the video and Update Publisher but because we have a very small user base we decided against SCUP because then WSUS updates would need to be deployed through SCCM.
Just for completeness lets say i deploy 10.1.0 and patch to 10.1.4, but lets say adobe release 10.2.0 instead of 10.1.5;
Will i be able to patch the;
or would it be necessary to do the full path, ie.
Or is this possible?
All of this is described in the Admin Guide. In general, AIPs are more work than using SCCM and bootstrapper, but many admins use AIPs without a problem.
The patch methodology for AIPs have a few more restrictions than other ways, but in general quarterlies patch to the last full installer; that is, quarterly MSPs are applied over the last MSI (full installer).
Whenever the second number is incremented, there's a full installer. Thus, 10.1 was a full MSI. 10.2 would be a full MSI. 10.1.5 would be a quarterly MSP.
Start with the doc.