Building a Software Package installation for Adobe Reader 10.1.1

The key component here was to install Adobe Reader and not have it check for updates automatically.

Applied to Distribute Adobe Reader from www.adobe.com

Downloaded Adobe Reader from:

http://get.adobe.com/reader/enterprise/

Downloaded Adobe Customization Wizard from: http://www.adobe.com/products/acrobat/deployment.html

Run the Customization Wizard and open the extracted acroread.msi.

• Installation Options:
  • Make Reader the default PDF viewer
  • Installation = Silently (no interface)
  • Reboot = Suppress Reboot
• Shortcuts
  • Remove Desktop Shortcut
• EULA
  • Suppress display of EULA
• Online and Acrobat.com Features
  • Disable Help -> Purchase Adobe Acrobat
  • Disable Help -> Digital Editions
  • Disable Product Improvement Program
  • Disable all Acrobat.com Access
• Registry
  • HKLM\SOFTWARE\Adobe\Adobe ARM\1.0\ARM
    • iCheckReader=dword:00000000
  • This was to set the update mode:
    • 0 = Manual: Do not download or install updates automatically
    • 1: Not used
    • 2 = Semi Automatic: Automatically download updates, but let me choose when to install
    • 3 = Automatic: Automatically install updates.
  • Information taken from page 15 and 16 of the following:  http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Reader_Updater.pdf

Generate Transform to create mst file (don’t “Save Package”, as this would modify the msi)

Close – When prompted to Save changes to AcroRead, select NO.

The SCCM Program (command line) is then just:

msiexec.exe /i AcroRead.msi TRANSFORMS="My_AcroRdr_10.mst" /qn

Sweet Batch File Tricks

If you are creating batch (.bat or .cmd) files you will run into an issue where you want to be able to determine the relative location of that script and then affect those other files.

A batch file uses %0 as the parameter for the batch file name.  Using %~ we can expand parameters.  Thus, when we combine a few parameters together we can create a way to read the current directory that the script is stored in.

%~dp0

d=drive letter
p=path

Thus, if the file c:\folder1\folder2\script.cmd exists and has the following contents:
echo %~dp0

We will get the following output:
c:\folder1\folder2\

Pay attention to the fact that the output contains the trailing backslash "\".  This is important because if you are going to reference another file in that directory you'll need to not use an additional "\".

If script.cmd is used to call script2.cmd in the same directory and also call script3.cmd in a subdirectory it would look something like this.
Example:

set scriptlocation=%~dp0
call %scriptlocation%script2.cmd
call %scriptlocation%folder3\script3.cmd


For an in-depth explanation:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/percent.mspx?mfr=true

Boot Images in SCCM 2007

The question comes up all the time.  What boot image do I need to use to boot properly for OSD in SCCM 2007.  Here's the definitive answer.

http://sccmftw.wordpress....x86-or-x64-boot-image/ 

• An x86 Boot Image can deploy the following: 
• 32bit image 
• 64bit image 
• 32bit Install Package 
• Can't deploy 64bit Install Package 

• An x64 Boot Image can deploy the following: 
• 64bit Image 
• 64bit Install Package 
• Can't deploy anything 32bit based