Archive for category Application Deployment

Deploy Adobe Acrobat Reader XI (11.0.03) Using SCCM 2012 SP1

There are several blogs on this topic; however, some seem to be lacking one or more details or may not show how to patch and customize Adobe Acrobat Reader XI. In this blog, I will show you how to patch, customize and deploy, via SCCM, Adobe Reader XI (11.0.03).

Pre-requisite: Make sure you have installed Adobe Customization Wizard XI

  1. Download the latest version of Acrobat Reader from Adobe’s FTP site.
    1. The direct FTP link is: ftp://ftp.adobe.com/pub/adobe/reader/win/11.x/11.0.03/en_US/
  2. We’re going to download the EXE file: AdbeRdr11003_en_US.exe
  3. Next, from an administrator command line, we’re going to extract the MSI from the EXE file using the following command: AdbeRdr11003_en_US.exe -nos_o”c:\SomeDirectory” -nos_ne
    1. Do not close this command line window as we’ll use it again.
    2. For this example I’m extracting the contents to C:\temp\Adobe XI (11.0.03) folder.

  4. Once we’ve extracted the source files from the EXE file, then let’s run (as an administrator) the Adobe Customization Wizard XI to create the MST file that we’re going to use to customize Adobe Reader XI.
    1. If the customization wizard isn’t run as an administrator, you won’t be able to save the package.
  5. Basically, we’re going to make changes in the the following sections:
    1. Personalization Options
    2. Installation Options
    3. Shortcuts
    4. WebMail Profiles
    5. Online and Adobe online services Features

  6. Once the customization options have been completed, proceed to click on Transform menu option then click on Generate Transform…
    1. Save the MST file in the same folder where the Adobe Reader MSI exists.
    2. For this example, we’re going to save this file as AcroRead.mst
  7. Next, click on File and then click on Save Package.
  8. Back to the command line and let’s create an Application Installation Point (AIP) in order to patch Acrobat Reader.
    1. In the folder where the MSI file was extracted, you’ll notice that file AdbeRdrUpd11003.msp is located there – that’s our patch file that we’ll be applying.
    2. For this example we’re going to create a new folder – C:\AdobeAIP
  9. From the command line, in step 3, we’re going to create the AIP with the following command: msiexec /a AcroRead.msi
    1. Once the wizard comes up, make sure to point it to the folder created in step 8.2
    2. Make sure you run this command from the folder in step 3.
    3. Take a look at the files extracted
  10. Change directory to folder C:\AdobeAIP
  11. Now we’re ready to patch the Acrobat Reader source files, let’s use the following command: msiexec /a AcroRead.msi /p “c:\temp\Adobe XI (11.0.03)\AdbeRdrUpd11003.msp”
    1. This will open a wizard window; make sure there are no error messages during this task.

  12. If the patching process was successful, then we should now have a patched Acrobat Reader XI installation as well as a customization file.
  13. From Step 3 folder (C:\temp\Adobe XI (11.0.03)), copy the MST file to the Step 6 folder (C:\AdobeAIP)
  14. At this time, folder C:\AdobeAIP should contain a patched Acrobat Reader  XI as well as the customization file. We’re going to use the contents of folder C:\AdobeAIP as our deployment files to create our SCCM 2012 deployment package.
  15. Copy all contents of C:\AdobeAIP to the share that SCCM uses to deploy applications in your environment.
  16. Let’s create a new application deployment package in SCCM. First, go to the Software Library section, and click on Application Management and then click on the Applications container to create the new package.
  17. Right click on the Applications container then click on Create Application option.
  18. Point to the network share where you copied the files in Step 15 and select the file AcroRead.msi
    1. You may get a warning message about not being able to verify the publisher of this MSI file, just click on Yes.
  19. In the General Information wizard screen, in the Installation program field, add the following:TRANSFORMS=”AcroRead.mst”
    1. This line should read: msiexec /i “AcroRead.msi” TRANSFORMS=”AcroRead.mst” /q

  20. Continue accepting defaults until the application wizard finishes.
  21. Now, you can deploy this new application to a selected number of computers or users.


Supersedence Notes
In my environment, I’m replacing, or superseding, and older version of Adobe Acrobat Reader. Here’s a quick screenshot on how it’s done.


36 Comments

SCCM 2012 and Microsoft App-V Client 4.6 SP1

Believe it or not I had such a hard time creating a SCCM 2012 packaged application for Microsoft App-V Client 4.6 SP1.

I found several promising links on this topic, but none went to the point or explained the process from start to finish. After researching this process, it looks like you can use the EXE or the MSI to create the packaged application.
The MSI way is supposed to be the desired way, and what most people recommend. However, not everything works as people document it, and certainly it didn’t work for me after several days of working on this.

Note: The main issue I had with the MSI installation was due to the VC++ 2005 Redistributable requirement. Although I was able to extract the VC++ 2005 MSI, and I was able to properly install it, somehow the setup.msi file would not recognize it as installed in the system! I spent way too many hours troubleshooting this issue and in the end, my productivity had slowed down due to this problem, so it was time for me to move on.

In the end, I opted for using the easier way – the EXE setup file. Using setup.exe takes care of all requirements for you, no need to create separate packages for them. Microsoft instructions on how to perform a silent install using the EXE file is found here. The documentation on what each installation paramater mean, is found here.

First off, I do not use an App-v publishing server, so make sure you read Microsoft’s information about installation parameters!

Here we go:

  1. The installation command line I use is: setup.exe /s /v”/qb-! SWICACHESIZE=\”6144\”
  2. The detection methods I use are based on registry keys: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\sftmime.com
  3. The other detection method I use is: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\sftmime.exe
Here are some screenshots:


This method has worked flawlessly in our environment, and I hope this helps someone out there.

Leave a comment

Deploy Pervasive SQL v10 SP3 Using SCCM 2012

Here are the steps to deploy Pervasive SQL v10 SP3 client to your Windows 7 machines using Microsoft’s SCCM 2012.

  1. Create an application package, and you’re going to use SetupWorkgroup_x86.exe
  2. Use the following installation parameters: SetupWorkgroup_x86 /s /v/qn
    1. Type it as shown above. There is no space in /v/qn
  3. For the Uninstall program, look at the screenshot below. You can leave it blank for now, but go back and the proper information once the wizard is complete.
  4. In the Detection Method section, you’re going to look for the MSI file PervasivePSQLv10WGE_x86.msi; this file is also located in the same folder as the setup file in step 1.
These steps worked in my environment.


Leave a comment

MS SQL Server 2008 R2 Native Client – Deployment

In order to deploy Microsft SQL Server 2008 Native Client, follow these steps.


  1. Download it from here
  2. Once you get the MSI, create an application in SCCM 2012
  3. In the Programs tab, you’re going to use the following syntax to execute the MSI: msiexec /i “sqlncli_x64.msi” /q IACCEPTSQLNCLILICENSETERMS=YES
  4. Done
Note: Any time you use the /q parameter you must include IACCEPTSQLNCLILICENSETERMS=YES to accept the terms. This parameter only works for the client, as the title of this document reads.


1 Comment