RSS

Category Archives: SCCM

Injecting Drivers into a Boot Image

This will be a very quick post on injecting drivers into a boot image in SCCM 2012 R2 SP1.

Couple notes:

1. I’m using SCCM 2012 R2 SP1

2. I’m injecting VMware drivers into an boot image.

 

Inject drivers to the boot image

1. Open the SCCM console and navigate to drivers.

2. Search for the drivers you want -> select them -> right click -> edit -> boot images.

add drivers

3. A menu will appear called “Add or Remove Drivers to Boot images”. Select the boot image you want to add drivers to via check box. I would also recommend un-checking “Update Distribution points when finished”. Hit ok and let the drivers get added.
add drivers to boot image

4. Navigate to “boot images” in the sccm console -> right click your boot image -> update distribution points. This will take a while.
update distros

5. Hit next a bunch and let the update happen.

6. You should be finished.

 

Feel free to ask questions\comment, but please do not spam this blog. Its very annoying.

 
Leave a comment

Posted by on June 17, 2014 in SCCM

 

Tags: , ,

Secunia CSI 5 Integration with SCCM 2012

This post will be about integrating Secunia CSI 5 with SCCM 2012. Secunia CSI when integrated, will help automate patch detection and installation.

Prerequisites:

  1.  A SCCM Site Server with the Software Update Point role installed.
  2. Download Secunia CSI 5.

Install Secunia CSI 5

  1. Connect to your SCCM VM.
  2. Double click the installation file you received from Secunia. The first page of the installation will appear.
  3. Accept the license agreement.
  4. Choose install location and hit “Install”.
  5. The installation will finish.
  6. A menu will appear asking “Would you like to launch Secunia CSI now?”, hit “Yes”.

Configuring Secunia

  1. Login into Secunia using the Username and password they sent you. The main screen will appear after the login.
  2. Expand the “Patch” section on the left. Click on “WSUS Configuration”, then click on “Configure Upstream Sever”.
  3. A menu named “CSI WSUS Configuration Wizard” will appear. Enter the name of your WSUS Server, then enter the WSUS server port number(this may vary depending on your settings). If you have WSUS configured to accept SSL connections check the box next to “Use SSL Connection”. Hit the “Connect” button below, and if the connection was successful you will see a box with a green check in it. Hit “Next”.
  4. For the next step click “Automatically create and install certificate”. This will(should) put “WSUS Self Signed Certificates” in your “Trusted Root Certificates” and “Trusted Publishers” stores. A green check box will display when the certificates are successfully installed.
  5. Open the Certificates manager on the local computer. There should be a “WSUS Publishers Self-signed” Certificate in the stores of “Trusted Root” and “Trusted Publishers”.

  6. Export this self signed certificate in “Base-64 encoding” for future use.
  7. For “Step 3” in the “WSUS Configuration Wizard”, choose “Use SCCM to Distribute packages” and hit the “Close” button. We will configure Group Policy manually.

Group Policy for Secunia

  1. Open “Group Policy Management”. Decide where you would like to store your GPO. Right click on the folder location you chose and click “Create a GPO in this domain, and Link it here…”.
  2. A menu named “New GPO” will appear. Give the GPO a name and select “none” for “Source Starter GPO”. Hit “OK” when your finished.
  3. The GPO will be created. Right click on your new GPO and hit “Edit”.
  4. Under “Computer Configuration” expand “Policies” —> “Administrative Templates” —> “Windows Components” and click on the “Windows update” folder.
  5. Edit the last option named “Allow signed updates from an intranet Microsoft update service location”. A   menu will pop up, select “Enabled” and hit “Apply” + “Ok”.
  6. Un-expand all menus on the left hand side.
  7. Expand “Computer Configuration” —> “Policies” —> “Windows Settings” —> “Public Key Policies”. Import the Certificate that you exported in the last section to the “Trusted Root and Trusted Publishers” stores.

  8. The GPO should now be setup correctly.

Please leave any comments, questions or concerns!

 
Leave a comment

Posted by on September 10, 2012 in SCCM, Secunia CSI 5

 

SCCM Packages – ChemBioOffice

This is a short blog post about silently installing a program that uses Windows Installer or .msi files. The end goal of this post will be to install a program silently or unattended on a target machine. This will allow us to automate the install on new lab machines that we recieve. For this blog we will be installing “ChemBioOffice” as our example program.

Overview

  1. Figure out the silent install mechanism.
  2. Create and test a silent install script.
  3. Figure out the silent license activation mechanism.
  4. Add license configuration to install script and test.

Notes & Sites of reference:

Manual installation

First, I will install the ChemBioOffice program manually to to familiarize myself with the application and its installer.This will also tell us where the application will install to by default.

  1. If you are installing on a Virtual Machine, it is a great idea to make a snapshot before you continue.This will enable us to quickly try the silent install multiple times if needed, without having to uninstall the program each time. Sometimes uninstallers don’t remove everything. This can affect the silent install package and make you think it is working when really, the silent install package created is dependent on something that the previous installer left behind. Better to start with a clean image each test.
  2. Double click the “cbdu1202.exe” and the setup will start. The first menu will ask you to “have your serial number ready”, hit “OK” to continue.
  3. Immediatily after hitting “OK”, setup will start extracting files.
  4. The setup wizard will appear, followed by the “CambridgeSoft Software Activation” screen. Fill this out and click “Activate over internet”.
  5. The message box “Software Activation Complete” will appear, click “OK” to continue.
  6. Next, the  ChemBioOffice install wizard should appear. Click “Next”.
  7. Accept the license agreement and click “Next”.
  8. On the “Setup Type” screen, leave the defaults and click “Next”.
  9. On the “Select Features – CambridgeSoft” screen, uncheck the box next to “E-Notebook 12.0”, then click “Next”.
  10. On the “Select Features -Third Party” screen, uncheck the “MNova NMR Lite” option and click “Next”.
  11. On the “Ready to Install” screen, click “Install”.
  12. The installation will begin and should look similar to the following image.
  13. When finished the “Installation Complete” screen will appear, click “Finish”.
  14. Check which directory the “ChemBioOffice” program installed to.
  15. Open your “ChemBioDraw” application to see if it works. It should look similar to the screen below.

Get Licensing Information

  1. To silently register ChemBioOffice licensing information, CambridgeSoft requires that you email support fora custom registry file. At the end of the silent installation of ChemBioOffice you will import the registry file. Email Cambridge support at “activate@cambridgesoft.com” for your activation file.
  2. Save this file to your “C:\workingtemp\ChemBioOffice” folder and name it “importChemLicense.reg”

Preparing your Source Directory

  1. Make a new folder called “ChemBioMedia” at “C:\workingtemp\ChemBioMedia”.
  2. Extract the “cbdu1202.exe” file, using 7zip to C:\workingtemp\ChemBioMedia.
  3. The ChemBioMedia folder should look like this after you extract the setup file.
  4. The file tree for this folder will look like this, the objects bolded and in Italics are the files that we need.

C:\workingtemp\ChemBioMedia

  • \_images
  • \Cambridgesoft
    • \Activation
    • \ChemOffice
      • CambridgeSoft_ChemBioDraw_Ultra_12.0.msi
      • CambridgeSoft_ChemDraw_ActiveX_Enterprise_Constant_12.0.msi
    • \ENotebook
    • SharedAddIn
      • SharedAddIn.msi
  • \DatatManagement Server Setup
  • \SQLInstaller
  • \ThirdParty
  • install.exe
  • install.ini

  1. Now to make life easy copy the following code into a batch file and run it. This will put all the neccessary installer files into “C:\workingtemp\ChemBioOffice”.
    REM Copy FIles
    mkdir "C:\workingtemp\ChemBioOffice"
    xcopy /y "C:\workingtemp\ChemBioMedia\Cambridgesoft\ChemOffice\CambridgeSoft_ChemBioDraw_Ultra_12.0.msi" "C:\workingtemp\ChemBioOffice\"
    xcopy /y "C:\workingtemp\ChemBioMedia\Cambridgesoft\ChemOffice\CambridgeSoft_ChemDraw_ActiveX_Enterprise_Constant_12.0.msi" "C:\workingtemp\ChemBioOffice\"
    xcopy /y "C:\workingtemp\ChemBioMedia\Cambridgesoft\SharedAddIn\SharedAddIn.msi" "C:\workingtemp\ChemBioOffice\"
  2. Note: For my installation I needed to install only 3 parts of the ChemBioOffice. These 3 parts are; ChemBioDraw Ultra 12.0, ChemDraw ActiveX Enterprise and SharedAddIn. These and the registry file should be the only 4 things in your “C:\workingtemp\ChemBioOffice” folder.
  3. Your folder will look like this.

Creating a Batch File

  1. Navigate to your “C:\workingtemp\ChemBioOffice” folder.
  2. Create a new text document in this folder and name it  “Install_ChemBioOffice.cmd”. The ending “.cmd” will make this a batch file.
  3. Copy and paste the following commands into your batch file.
    REM Installing ChemBioOffice
    REM Main Install
    start /wait msiexec /i CambridgeSoft_ChemBioDraw_Ultra_12.0.msi /qb
    start /wait msiexec /i CambridgeSoft_ChemDraw_ActiveX_Enterprise_Constant_12.0.msi /qb
    start /wait msiexec /i SharedAddIn.msi /qb
    REM Licensing
    REGEDIT /s importChemLicense.reg

At this point your batch file should be ready to test.

Testing the batch file

  1. Navigate to “C:\workingtemp\ChemBioOffice”.
  2. Open a command prompt as “Administrator” and type the following command to change directories.
    cd C:\workingtemp\ChemBioOffice
  3. Now that we are in the correct directory type in the batch file name we are using.
    Install_ChemBioOffice.cmd
  4. Hit Enter and the installation will begin, it will look similar to the following image.
  5. Next, the application should start just as it did after the manual installation we did earlier.

If there are any problems\concerns\questions with this post, please leave a comment!

 
3 Comments

Posted by on March 16, 2012 in ChemBioOffice, SCCM

 

Tags: , , , ,