DC products can span all aspects of your document workflow, including the desktop, the cloud, and mobile devices.
The important thing is to keep a clean copy of the 11.0.0 Adobe Reader base release on your SCCM server or another area that’s easy to get to.
The reason for this is that all of the quarterly Adobe Reader releases are cumulative and can be applied to the 11.0.0 Adobe Reader base release directly using the . Out-of-Cycle (11.0.08 for example) patches should be applied to the last quarterly update as you will see below.
Track release schedules and their respective versions will be different, but both the Continuous and Classic tracks share an identical methodology.
The new strategy is designed to provide better granularity, support more frequent releases, and aid in troubleshooting by providing build information.
The Adobe Reader XI Update Cycle For Example: If you are updating Adobe Reader from 11.0.03 to 11.0.04 you can see in the graphic above that this is a quarterly release being updated to another quarterly release.
So at this point you can apply the 11.0.04 quarterly update to the Adobe Reader 11.0.0 base release to create an SCCM 2012 Application.
Despite the user of the year identifier, major versions have a lifespan which is likely much longer than a year.
SCCM Administrators can use the following path to download the latest Windows XI version of Adobe Reader.
What services are visible in the user interface varies by the purchased track and license type.
Use the Customization Wizard or registry/plist configuration to remove unwanted items from the user interface.
Because those cloud components are regularly updated to work with the latest version of the desktop product, both tracks should also be regularly updated.