Managing 3rd Party Updates in SCCM 2012 using SCUP

Managing 3rd Party Updates in SCCM 2012 using SCUP

This guide will show you how to deploy 3rd party updates alongside Microsoft Updates via SCCM using SCUP plus software update catalogs


Before SCCM may deploy 3rd party updates, we must first get them into SCCM.  Here’s how…

For the examples in this guide, we will be publishing Google Chrome 45.0.2454.85

1. Launch SCUP (Systems Center Updates Publisher) 2011 from the SCCM Primary Server

2. Update the Catalogs

Before importing anything, we must update the catalogs by importing them which takes about 10-15 minutes.  This doesn’t have to be done each time you publish, but suggest doing so if no one has done it in the past 24 hours.  This ensures that the source we select from has the latest updates.

           a. In the ribbon bar at the top, click on the “Import” button

           b. Place a check in the top-most checkbox to select all options, then click Next


           c. At the confirmation screen, click Next once more to confirm the selection and the import will begin. If prompted asking if you trust the publisher listed, select “Always Accept…” then click Accept


           d. Once the catalogs have been imported, click OK to return to the main screen

3. In the left column, browse to the folder of the updates publisher then locate the update you wish to publish to SCCM

4. Right click on the update and select “Publish”


Important Note: You can also add updates to Publications (Group of Updates) by right clicking the updates and choosing assign and creating a Publication group. You can publish these groups all at once.

5. The window which appears will have 3 primary choices: Automatic, Full Content, and Metadata Only. Since we want the update files to be downloaded and stored in SCCM alongside Microsoft updates so that it’s ready to deploy, select “Full Content” then click Next


6. Click Next in the “Publish Software Update” Wizard. A progress bar will appear as the update(s) are downloaded and added into SCCM.  During this process, you may be prompted with a Security Warning asking if you wish to accept this content.  If so, select “Always Accept…” then click “Accept”.  Note:  If the vendor does not digitally sign their content, you will have to do this every time you Publish or import the catalog


7. Once complete, the window will display how many updates were selected for publishing and how many were published with full content. If the numbers on both lines match, then the Publish was successful.  Click Close


Important Note:  If there are any issue during Publishing, the SCUP log may be checked which is located at %temp%\scup.log.

Handling the Update Within the SCCM Console

8. Launch the SCCM Console, browse to “Software Library” then expand the “Software Updates” folder

9. Right click “All Software Updates” at the top of the folder then choose “Synchronize Software Updates.” When prompted to verify that you want to run synchronization, choose “Yes”


Once the sync finishes, you should now see the new updates available within the SCCM Console and they will be available for deployment!  If you do not see the update after the synchronization completes, see the section named “Vendor Specific SCCM Configuration“ below.

Vendor Specific SCCM Configuration

The First Time you Publish an Update for a Manufacturer which you haven’t ever published from before, it may not appear after the initial synchronization.  Here’s how to resolve this issue…

  1. Using the steps in prior sections, publish the desired update and perform the Software Update Synchronization in the SCCM console
  1. Confirm that the synchronization is complete and that the update does not appear before continuing
  1. In the SCCM console, browse to the “Administration” section
  1. Expand “Site Configuration”, then select “Sites”
  1. Right click on the site in the main pane, select “Configure Site Components”, then “Software Update Point”


  1. Select the “Products” tab
  1. You should see the manufacturer of the update which failed to appear and perhaps the product name underneath it as shown below. Check both boxes for the manufacturer and product, click Apply, then OK.

           1j      1k

  1. Rerun the Software Updates synchronization as described in step #9 in the section above. Once it completed again, the update(s) will appear

Publishing Multiple Updates at Once with “Publications”

More coming soon…

How to Manually Create a Bootable USB Drive for SCCM OSD Deployment Using DiskPart

How to Manually Create a Bootable USB Drive for SCCM OSD Deployment Using DiskPart

  1. Insert USB stick (1g or larger) into computer. Note that the USB stick will be formatted during this procedure
  1. Open A Command Prompt – Click on Start, then Run and type “cmd” – Enter
  1. Start DiskPart – Type “diskpart” – Enter. The prompt should change to the below:


  1. Type “list disk” for a list of all the physical drives connected to the system. Find the number of the drive corresponding with your flash drive.  For the example below, it’s #5 (due to total size)


  1. Type “select disk X” – Enter (with X being the number of the disk)


Important –

Make sure you choose carefully as the next step will wipe the selected disk

  1. Type “clean” – Enter to wipe all data and partitions from disk


  1. Create Partition & Prep It – Enter the below steps to create a primary partition
    1. Type “create part pri” – Enter
    2. Type “select part 1” – Enter
    3. Type “format fs=ntfs quick” – Enter


  1. Make the drive bootable – Type “active” – Enter


  1. Exit diskpart by typing “exit” – Enter followed by typing “exit” – Enter again to exit the command prompt
  1. Extract all files & folders from your site’s bootable ISO file to the root of the newly created media – or – extract your site’s ISO file to a temporary folder and copy all files and folders to the root of the new media. Once done, the root of the USB drive should look similar to the below screenshot in Windows Explorer


Note:  Examples of applications which can extract ISO files are 7zip, UltraISO, MagicISO, WinRAR, and many others…

How to Create an Adobe Acrobat / Reader Installer Package Which is Up to Date + Includes Your Custom Configurations

How to Create an Adobe Acrobat / Reader Installer Package Which is Up to Date + Includes Your Custom Configurations

Adobe usually releases an MSI for a major product installation, then MSP files to update it.  This guide will show you how to integrate the updates into the installation files as well as be able to have all settings of Acrobat preconfigured upon installation or deployment.


  1. Download the following into a temp folder. (Example: C:\AcroSlip)
  • Adobe Acrobat Installation Files (MSI)
  • Adobe Customization Wizard
  • Latest .MSP Update for Acrobat
  1. Create a temporary folder on the root of a drive (Example: C:\AcroUpdate)
  1. Open command prompt as admin and go to C:\Acroslip
  1. Do an admin install of latest MSI you have downloaded from

     msiexec /a AdbeRdr1010_en_US.msi

When asked to select a path, choose the path created in step 2.

  1. Patch the admin install you just created.

     msiexec /a C:\AcroUpdate\AdbeRdr1010_en_US.msi /p AcrobatUpd1013.msp

  1. In the root of C:\AcroUpdate,check for a setup.ini file.  If it does not exist, create one in Notepad per instructions at the end of this document
  1. Install and run the Adobe Customization Wizard X and open the MSI file just created and updated in C:\AcroUpdate
  1. Make all customizations and changes.  Make sure to select the Silent Deployment and to Suppress Reboot
  1. Click Transform in the top menu bar and choose Generate Transform… name it Custom.mst
  1. Your new package may now be installed with either of the following lines depending on where it’s being deployed from:

     msiexec /i “AdbeRdr1010_en_US.msi” TRANSFORMS=”Custom.mst” /qn

     msiexec /i “AcroStan.msi” /q



Setup.ini Contents


RequireOS=Windows XP



CmdLine=/sl”1033″ /sall /rs




1033=English (United States)

1031=German (Germany)

1036=French (France)


[Windows XP]





[MSI Updater]



How to Manually Create a WIM File of a Pre-Configured Workstation

How to Manually Create a WIM File of  a Pre-Configured Workstation

 In SCCM and many other distribution applications, you may directly import a WIM file for deployment of an operating system or corporate image.  A WIM file is all of the mass data of a Windows OS and is found on all installation media as well.  Usually, it is a file named install.wim.  The below document will show you how to turn a workstation with an image you wish to deploy into a WIM file.


  • x1 – Windows 7 workstation configured to your specifications
  • x1 – Bootable WinPE USB Drive or Disc
  • x1 – External Hard Drive

Prepare Workstation

To be performed on the workstation whose configuration you want deployed

  1. Make all customizations and install all applications until you have the workstation exactly as you want it
  1. Disjoin the workstation from a domain if it is currently a member of one
  1. Optional – Create a backup before proceeding

Sys-prepping the Workstation

  1. On the workstation, run “c:\windows\system32\sysprep\sysprep.exe” Choose to enter “Audit Mode”, uncheck “Generalize”, choose “Reboot”, then click OK. The machine will reboot and come back up to the desktop without prompting for credentials.
  1. Make final changes you wish to perform. This may include deleting temporary local accounts and their matching local profiles.
  1. Once ready, run “c:\windows\system32\sysprep\sysprep.exe” again. This time, choose “Enter Out of Box Experience”, check “Generalize”, and choose “Shutdown.”  Click OK to proceed.

Capturing WIM File

  1. Plug in or insert your WinPe drive as well as the external USB drive. Turn on the computer and boot to the Windows PE USB drive or disc.  If you miss the prompt and it starts loading Windows, you must go through Windows Initial Configuration then start at step 4 again.  Once complete, you should be at a command prompt.
  1. Find out what devices have what driver letters and list them below. The easiest way to do this is to run a “dir” command on each drive letter and match its contents.
  • WinPE Media Drive Letter:
  • Workstation’s Hard Drive Letter:
  • External USB Drive Letter:

For the rest of this guide, we will assume that the WinPE media is E:, the Workstation Drive is D:, and the External USB Drive is F:

  1. Run the following command. Make sure you substitute the drive letters you noted appropriately

 “E:\imagex /compress fast /check /flags “Professional” /capture D: F:\install.wim “Windows 7 Professional” “Windows 7 Professional Custom”

 If entered correctly, the workstation’s OS will immediately start to compress into “install.wim” onto your External USB Drive. All custom or user specific files will not be included such as recycle bin files or page files.  After a few seconds, you will be given an estimate as to how much time is remaining for the capture.

  1. Once complete, you will be back at a command prompt. The install.wim file is now complete and created on your external drive.  Rebooting the workstation will start the Initial Windows Installation Wizard.

Examples of What Can You Do With a WIM File

  • Import into SCCM or other distribution application for deployment
  • Create Installation Media – Extract a Windows 7 OEM ISO to a temp folder. Once extracted, replace the install.wim in its “sources” folder with the install.wim you made.  You may then copy the extracted contents to a bootable USB drive or recreate an ISO file.
  • When Windows is installed from that custom installation now, it will have all of your changes and applications installed already!