Skip to Content

University Technology Services


Getting Started with IBM BigFix

Below are the steps local IT support must take in order to join the IBM BigFix community at USC.

Process for requesting BigFix

1. Order BigFix

To order BigFix, complete the following:

  1. Navigate to https://my.sc.edu and click on "Purchase computer software" under the "Personal" section.  
  2. Select "Security" -> "BigFix Subscription" -> "BigFix Patch Client Device (Client Subscription).  
  3. Enter the number of client licenses for your department / college and click "Continue".  
  4. Complete the form on the Purchase Details page and click "Continue".

This generates an order and a ticket that is routed to the BigFix Administrator within the Division of Information Technology.

2. Install BigFix Client

You will receive an email from the BigFix administrator with an introduction that includes the following:

  1. A link to a Microsoft OneDrive share containing the BigFix client installer for Windows (both an MSI and a standard Setup.exe) or OSX and instructions on how to install and configure the client on a “gold image”.
      1. BigFix Standard installer for Windows (Setup.exe)
      2. BigFix MSI Installer for Windows (BigFixAgent.msi)
      3. BigFix OSX Installer for Mac (BESAgent-9.5.xxx.x-BigFix_MacOSXxx.x.pkg)
      4. BigFix for Linux (IBM)
3. Setup Custom Site within the BigFix Console

The BigFix administrator will prepare a “custom site” for the requesting college/department that will act as a shared repository for devices and content. The naming scheme for the site is based on the conventions derived from the USC DS Active Directory. Devices and content within a departmental site are only accessible to operators authorized by the requesting network administrator and the BigFix administrator.

  1. The computers on which the BigFix client is installed will appear as a “subscribed computer” within the departments’ site based on a predefined set of criteria. These basic filters always include devices within the root of your organizations Active directory OU, and/or computer naming convention (eg. Coutsd, cocasl, comath etc.), and/or a "CID" (computer identifier) designated in the clientsettings.cfg.
4. Grant Administrator access to BigFix Console

An administrative role is created to match the site name and users are assigned the role by AD security group or LDAP user names. Members of this group will have authority over the devices within the site. These permissions may be granularly assigned, these details may be discussed with the BigFix administrator to provide a management environment that best fits the needs of the requestors department.

5. Setup BigFix Web Reports

An additional role is created by the BigFix Administrator for the BigFix Web Reports web site based on the above criteria. Web reports is a separate interface accessible from https://bigfix.uts.sc.edu., and is the place for creating and scheduling reports the results of which are based on analyses created within the BigFix environment.

6. IBM BigFix Console and Patch Management Introduction

The process concludes with an introduction to the BigFix console and a basic overview of the patch management and software distribution functionality conducted by the BigFix administrator or designated trainer. This introduction is presented via Bomgar, and conference call with a preference for administrators having access to the console on their own computers so they may step through the process with the instructor.

Learn more

IBM Video Resources