Archive for category Configuration manager 2012

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:
  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.


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\
  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

Use the asset tag on a DELL Latitude E6500 as the computer name


So I ran into an interesting bug with our DELL Latitude E6500 models and Microsoft’s SCCM 2012.

First off, in our environment we use the BIOS service tag information on all our DELL devices as the computer name in Windows 7. I’m able to get this information during the Task Sequence (TS) by means of using a VB script.

The script I mention above works on all our DELL computer and laptop models, with the exception of the DELL Latitude E6500 laptop models.

The Bug

On a DELL Latitude E6500, with the BIOS updated to the latest version, it looks like the BIOS asset tag information is somewhat misleading. If you view the information, you’ll see the asset tag information, but what you don’t see are the trailing spaces after the asset tag information. For instance, if the BIOS asset tag information on a laptop reads X1234, there are 5 trailing spaces after it, and these white spaces do not show!

Note: We use a tool called asset.exe, from DELL, to modify the asset information and the owner information in the BIOS. This tool works well on many of DELL computers and laptops.

SCCM 2012 and The Bug

During a SCCM Task Sequence (TS) job, we collect the asset information and we use this information as the Windows 7 computer account. The TS works perfectly until the last step: Setup is applying system settings – at this point, the TS fails with the message: Windows could not parse or process the unattend answer file for pass [specialize]

The TS fails completely and you’re left with a computer whose OS isn’t working.

SCCM logs give a hint on what went wrong. In case you don’t know, those logs can be retrieved from the broken machine and the logs (setupact.log and setuperr.log) are located at: C:\Windows\Panther\UnattendGC
In our case, both files showed the following error message:

2013-02-27 15:35:17, Error     [Shell Unattend] ComputerName: failed to set the computer name [hr=0x80070057][gle=0x00000057]
2013-02-27 15:42:30, Error    [windeploy.exe] Setup.exe failed, returning exit code [0x1f]
2013-02-27 15:42:30, Error     [windeploy.exe] Failure occured during online installation.  Online installation cannot complete at this time.; hr = 0x80004005
2013-02-27 15:43:42, Error     [windeploy.exe] Setup.exe failed, returning exit code [0x1f]
2013-02-27 15:43:42, Error     [windeploy.exe] Failure occured during online installation.  Online installation cannot complete at this time.; hr = 0x80004005

After reviewing this log, this pointed me to the VB script mentioned earlier and to the BIOS asset tag information. I knew the script was working properly, so I turned my attention to the BIOS asset tag information.
After several hours of toying around with asset.exe, I realized that there were blank spaces after the asset tag information – 5 spaces in total!

The Workaround (not a fix)

Basically, I used asset.exe and deleted the current asset tag and re-typed it, but this time I added 5 letters to the end. In other words, my command line looked like this:

asset.exe X1234ABCDE

X1234 is the asset tag information (a.k.a my Windows 7 computer name); however, ABCDE is the workaround to make sure those blank spaces don’t break the TS.

After the TS finished, then I logged on as a local administrator and renamed the computer name to X1234 – life is good again!

Note: During this entire troubleshooting process we updated the laptop BIOS, and this didn’t seem to fix the issue.

I hope this helps someone out there.

Leave a comment

SCCM 2012 – Software Center Options

The original information came from this source, I’m just adding a few more screenshots for my benefit.

The following script will allow you to change a particular setting found in SCCM 2012’s Software Center.

In Software Center, under the Options tab, and under the Computer maintenance heading, there is a setting – Automatically install or uninstall required software and restart the computer only outside of the specified business hours – that can be set to True (checked) or False (unchecked) by using this script.
Use the following code to obtain the current status of the option. This code you’ll use as the Discovery script.
$getStatus = Invoke-WmiMethod -Namespace "Root\ccm\ClientSDK" -Class CCM_ClientUXSettings -Name GetAutoInstallRequiredSoftwaretoNonBusinessHours -ComputerName $env:ComputerName -ErrorAction STOP

If ($getStatus.AutomaticallyInstallSoftware -eq "True")
Write-Host "Compliant"
Write-Host "Non-Compliant"
Here’s how you’ll add this code to a Configuration Items object.
Next, we’ll need to add the code to make the change or Remediation script
Invoke-WmiMethod -Namespace “Root\ccm\ClientSDK” -Class CCM_ClientUXSettings -Name SetAutoInstallRequiredSoftwaretoNonBusinessHours -ArgumentList @($TRUE) -ComputerName $env:ComputerName -ErrorAction STOP
Here’s how you’ll add this code to a Configuration Items object.
Next, we need to configure a Compliance Rule for the Configuration Item.
Now, as the final portion, we need to create a Configuration Baseline based on the Configuration Item created here and then deploy the Configuration Baseline.


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

Deploy AutoDesk DWG TrueView 2013 using SCCM 2012

These are the steps I took to deploy AutoDesk DWG TrueView 2013 using System Center Configuration Manager 2012 (SCCM 2012).

These steps are for deploying DWG TrueView 2013 x64 to Windows 7 Enterprise x64 machines. Make sure you download the correct version of DWG that meets your needs. Download link for DWG TrueView 2013 is here.

For starters, make sure you meet the application requirements.
  1. Microsoft .NET Framework 4 SP1 (or update 1)
  2. VC++ redistributables: 2005 SP1, 2008 SP1 and 2010 SP1
  3. DirectX
Now, since I’m using SCCM 2012, I created a Software Update Group (SUG) to deploy .NET 4 SP1 and all VC++ redistributables.
For .NET Framework 4 you can select the following Microsoft’s articles ID from All Software Updates node in SCCM: 2656405, 2656351(2 updates), 2604121 (3 updates), 2656405, 2487367, 982671 (this is the actual framework) and 2487367. You can add all these updates, put them in a SUG and deploy this to your clients before attempting to deploy DWG TrueView.

As for VC++ redistributables , some are already installed since the SCCM client requires some of these to work properly, so just check your client testing machine and deploy the one(s) missing.

Now, to create the application in SCCM 2012.

  1. In the Create Application Wizard, select Manually specify the application information
  2. In the General section, fill in the proper fields for this application
  3. In the Application Catalog section, fill in the proper fields for this application
  4. In Deployment Types section, click on Add
  5. In the Create Deployment Type Wizard, select Script Installer (Native), and make sure that Manually specify the deployment type information has been selected
  6. In General Information section, fill in the proper fields for this application
  7. In Content section, browse to the network location where you saved DWG TrueView installer files
  8. In the Installation program field, type: setup.exe /w /t /l /q setup.ini  (do not type any quotes!)
  9. In the Uninstall program field: I’m still trying to research how to create an uninstall command for DWG TrueView
  10. In the Detection Method section, click on Add Clause
  11. In Setting Type field, select Windows Installer
  12. In Product Code type: {5783F2D7-B028-0409-0100-0060B0CE6BBA}  (you get this product code from an MSI located in \x64\dwgviewr\dwgviewr.msi)
  13. In the User Experience section, for Installation behavior, select Install for system
  14. For Logon requirement, select Whether or not user is logged on
  15. The next sections can be customized to meet your needs
These steps worked for my environment.

To-do: I still need to figure out how to un-install DWG TrueView 2013. At this point, only the deployment works properly.

From step 8
From steps 11 and 12

Remove TrueView 2013 Desktop Shortcut

This is an optional step, so follow it if you want to remove the desktop shortcut created by setup.exe.

Previously in Step 8, we used setup.exe command line to create the application package. You’re going to create a batch file (INSTALL.CMD) and type its name in this field replacing the entire setup.exe command line.

Here’s how batch file INSTALL.CMD should look like:

REM Install DWG TrueView 2013
setup.exe /w /t /l /q setup.ini

REM Delete desktop shortcut created by SETUP.EXE for all users
del /q c:\users\public\desktop\dwgtru~1.lnk

Note: If a user is logged on while the application is being installed, the user will see the icon for a few seconds while setup.exe finishes and passes control back to the batch file.
There is a setup.ini file which contains CREATE_DESKTOP_SHORTCUT=YES – changing this line to NO did not work for me, that’s why I decided to use the batch file installation approach.

Leave a comment