Fuego Installation Instructions For Mac

by

-->

Important

Welcome to Microsoft Defender for Endpoint, the new name for Microsoft Defender Advanced Threat Protection. Read more about this and other updates here. We'll be updating names in products and in the docs in the near future.

Mac OS Mojave (10.14) is compatible with AnyConnect 4.7.04056 and below For more details about the supported operating systems (Windows, Linux, Mac) of the Cisco AnyConnect Secure Mobility Client, refer to the article on Cisco AnyConnect Secure Mobility Client Supported Operating Systems and Requirements. Page 17 Step 5 Install front panel: insert bottom hinge first, then use your finger to depress top spring-hinge and release once aligned into position. Page 18 Step 6 Install the temperature gauge into the cooking lid. Page 19 Step 7 A: Place diffuser panel, cast iron grate, and grill lid in place. Please note that the grill grate should be.

This topic describes how to install, configure, update, and use Defender for Endpoint for Mac.

Caution

Running other third-party endpoint protection products alongside Defender for Endpoint for Mac is likely to lead to performance problems and unpredictable side effects. If non-Microsoft endpoint protection is an absolute requirement in your environment, you can still safely take advantage of MDATP for Mac EDR functionality after configuring MDATP for Mac antivirus functionality to run in Passive mode.

What’s new in the latest release

Tip

If you have any feedback that you would like to share, submit it by opening Microsoft Defender for Endpoint for Mac on your device and navigating to Help > Send feedback.

To get the latest features, including preview capabilities (such as endpoint detection and response for your Mac devices), configure your macOS device running Microsoft Defender for Endpoint to be an 'Insider' device.

How to install Microsoft Defender for Endpoint for Mac

Prerequisites

  • A Defender for Endpoint subscription and access to the Microsoft Defender Security Center portal
  • Beginner-level experience in macOS and BASH scripting
  • Administrative privileges on the device (in case of manual deployment)

Fuego Installation Instructions For Machine

Installation instructions

There are several methods and deployment tools that you can use to install and configure Defender for Endpoint for Mac.

  • Third-party management tools:

  • Command-line tool:

System requirements

The three most recent major releases of macOS are supported.

Important

On macOS 11 (Big Sur), Microsoft Defender for Endpoint requires additional configuration profiles. If you are an existing customer upgrading from earlier versions of macOS, make sure to deploy the additional configuration profiles listed on New configuration profiles for macOS Catalina and newer versions of macOS.

Important

Support for macOS 10.13 (High Sierra) will be discontinued on February 15th, 2021.

  • 11 (Big Sur), 10.15 (Catalina), 10.14 (Mojave), 10.13 (High Sierra)
  • Disk space: 1GB

Fuego Installation Instructions For Mac Metal Siding

Beta versions of macOS are not supported.

After you've enabled the service, you may need to configure your network or firewall to allow outbound connections between it and your endpoints.

Licensing requirements

Microsoft Defender for Endpoint for Mac requires one of the following Microsoft Volume Licensing offers:

  • Microsoft 365 E5 (M365 E5)
  • Microsoft 365 E5 Security
  • Microsoft 365 A5 (M365 A5)

Note

Eligible licensed users may use Microsoft Defender for Endpoint on up to five concurrent devices.Microsoft Defender for Endpoint is also available for purchase from a Cloud Solution Provider (CSP). When purchased via a CSP, it does not require Microsoft Volume Licensing offers listed.

Network connections

The following downloadable spreadsheet lists the services and their associated URLs that your network must be able to connect to. You should ensure that there are no firewall or network filtering rules that would deny access to these URLs, or you may need to create an allow rule specifically for them.

Spreadsheet of domains listDescription

Spreadsheet of specific DNS records for service locations, geographic locations, and OS.
Download the spreadsheet here: mdatp-urls.xlsx.

Microsoft Defender for Endpoint can discover a proxy server by using the following discovery methods:

  • Proxy autoconfig (PAC)
  • Web Proxy Autodiscovery Protocol (WPAD)
  • Manual static proxy configuration

If a proxy or firewall is blocking anonymous traffic, make sure that anonymous traffic is permitted in the previously listed URLs.

Warning

Authenticated proxies are not supported. Ensure that only PAC, WPAD, or a static proxy is being used.

SSL inspection and intercepting proxies are also not supported for security reasons. Configure an exception for SSL inspection and your proxy server to directly pass through data from Microsoft Defender for Endpoint for Mac to the relevant URLs without interception. Adding your interception certificate to the global store will not allow for interception.

To test that a connection is not blocked, open https://x.cp.wd.microsoft.com/api/report and https://cdn.x.cp.wd.microsoft.com/ping in a browser.

If you prefer the command line, you can also check the connection by running the following command in Terminal:

The output from this command should be similar to the following:

OK https://x.cp.wd.microsoft.com/api/report

OK https://cdn.x.cp.wd.microsoft.com/ping

Caution

We recommend that you keep System Integrity Protection (SIP) enabled on client devices. SIP is a built-in macOS security feature that prevents low-level tampering with the OS, and is enabled by default.

Once Microsoft Defender for Endpoint is installed, connectivity can be validated by running the following command in Terminal:

How to update Microsoft Defender for Endpoint for Mac

Microsoft regularly publishes software updates to improve performance, security, and to deliver new features. To update Microsoft Defender for Endpoint for Mac, a program named Microsoft AutoUpdate (MAU) is used. To learn more, see Deploy updates for Microsoft Defender for Endpoint for Mac.

How to configure Microsoft Defender for Endpoint for Mac

Guidance for how to configure the product in enterprise environments is available in Set preferences for Microsoft Defender for Endpoint for Mac.

macOS kernel and system extensions

In alignment with macOS evolution, we are preparing a Microsoft Defender for Endpoint for Mac update that leverages system extensions instead of kernel extensions. For relevant details, see What's new in Microsoft Defender for Endpoint for Mac.

Resources

  • For more information about logging, uninstalling, or other topics, see Resources for Microsoft Defender for Endpoint for Mac.

  • Privacy for Microsoft Defender for Endpoint for Mac.

All mastheads on this page are Evaluation mastheads and should only be used on Evaluation licenses of BigFix. If you have a Production licenses of BigFix, please contact your sales rep to obtain Production mastheads.

For previous non-Windows versions, please refer to the following text file:
support.bigfix.com/bes/install/besnonwindowsarchive.html.

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

AIX

AIX - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

AIX - Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BES Client package file to the IBM AIX computer.
  2. Copy the BESAgent to the IBM AIX computer.
  3. Run the following command: installp –agqYXd ./BESAgent-8.2.1409.0.ppc_aix53.pkg BESClient
  4. Copy the masthead file to /etc/opt/BESClient/actionsite.afxm.
  5. Run the following command: /etc/rc.d/rc2.d/SBESClientd start.

AIX - Fixlet Content

  1. To get the Fixlet content for the AIX BES Agent, you will need to subscribe your BES Server to the appropriate Fixlet site. To subscribe to a new Fixlet site, go to a computer with the BES Console installed.
  2. Download the AIX Evaluation masthead: (Note: This masthead is for Evaluation licenses only.)
  3. When prompted to open or save the file, click 'Open' and this will automatically open the BES Console.
  4. Log into the BES Console with your username/password.
  5. Once logged in, the BES Console will ask if you wish to subscribe to the Patches for AIX Fixlet site, click OK.
  6. Type in your private key password and click OK.
  7. After the BES Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.

CentOS

CentOS - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

CentOS - Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BigFix Client RPM file to the Red Hat computer.
  2. Install the RPM by running the command rpm -ivh <path to BigFix Client RPM>.
  3. Copy your actionsite masthead to the Linux BigFix Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:BigFix Installers). If the masthead is not named 'actionsite.afxm', rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: In BigFix 4.0 and later, the masthead file for each BigFix Server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.bigfix.com:52311/masthead/masthead.afxm).
  4. Start the BigFix Client by running the command: /etc/init.d/besclient start.

Debian

Debian - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

Debian - Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BigFix Client DEB package file to the Debian computer.
  2. Install the DEB by running the command dpkg -i <path to BigFix Client package>.
  3. Copy your actionsite masthead to the Linux BigFix Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:BigFix Installers). If the masthead is not named 'actionsite.afxm', rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: In BigFix 4.0 and later, the masthead file for each BigFix Server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.bigfix.com:52311/masthead/masthead.afxm).
  4. Start the BigFix Client by running the command: /etc/init.d/besclient start.

HP-UX

HP-UX - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

HP-UX - PA-RISC Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download and copy the corresponding BES Client package file to the HP-UX computer (the computer must be PA-RISC system). The file name will be in the format '(BESAgent-ww.xx.yy.zz.pa_risc_hpux11.0.depot' with variations, depending on the particular version of the agent downloaded.
    Note: Internet Explorer may incorrectly label the downloaded file as a .tar file. Mozilla and other browsers will download the file with the extension as .depot
  2. Run the following command:
    /usr/sbin/swinstall -s HOSTNAME:/path/BESAgent_filename BESAgent
    where HOSTNAME is the name of the system which the Agent is being installed, and /path/ is the path to the Agent installation source and BESAgent_filename is the name of the file you downloaded.
    For example:
    /usr/sbin/swinstall -s hpsystemb:/tmp/BESAgent-8.2.1409.0.pa_risc_hpux110.depot BESAgent
  3. Copy your actionsite masthead to the HP-UX BES Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BES Installation folders (by default they are placed under C:BES Installers). If the masthead is not named 'actionsite.afxm, rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: In BES 4.0 and later, the masthead file for each BES Server is downloadable at http://servername:port/masthead/masthead.afxm
  4. Start the BES Client by running the command /sbin/init.d/besclient start

HP-UX - Itanium Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download and copy the corresponding BES Client package file (BESAgent-8.2.1409.0.pa_risc_hpux110.depot) to the HP-UX computer (must be Itanium system).
  2. Run the following command:
    /usr/sbin/swinstall -x 'allow_incompatible=true' -s HOSTNAME:path/BESAgent-8.2.1409.0.pa_risc_hpux110.depot BESAgent
    where HOSTNAME is the name of the system which the Agent is being installed, and /path/ is the path to the Agent installation source
  3. Copy your actionsite masthead to the HP-UX BES Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BES Installation folders (by default they are placed under C:BES Installers). If the masthead is not named 'actionsite.afxm, rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: In BES 4.0 and later, the masthead file for each BES Server is downloadable at http://servername:port/masthead/masthead.afxm
  4. Start the BES Client by running the command /sbin/init.d/besclient start

HP-UX - Fixlet Content

  1. To get the Fixlet content for the HP-UX BES Agent, you will need to subscribe your BES Server to the appropriate Fixlet site. To subscribe to a new Fixlet site, go to a computer with the BES Console installed.
  2. Download the HP-UX Evaluation masthead. (Note: This masthead is for Evaluation licenses only.)
  3. When prompted to open or save the file, click 'Open' and this will automatically open the BES Console.
  4. Log into the BES Console with your username/password.
  5. Once logged in, the BES Console will ask if you wish to subscribe to the Patches for HP-UX Fixlet site, click OK.
  6. Type in your private key password and click OK.
  7. After the BES Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.
Mac

Mac OS X

Mac OS X - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

Mac OS X - Installation Instructions

For client versions up to 8.2.1175.0 (8.2 Patch 3) or all installations on OSX 10.4 and 10.5:

  1. Download the corresponding BES Client package file to the Mac computer.
  2. Open the disk image by double clicking the DMG file (eg: BESAgent-8.2.1310.0-BigFix_MacOSX.dmg) to mount it.
  3. Run the BESAgent Installer Builder. The Installer Builder will request the masthead file which is available by using the BESAdmin tool on the BES Server computer ('Export Masthead' functionality). The file must be named 'actionsite.afxm' for the installation to work properly.
  4. After running through the Installer Builder it will ask you where to save the Mac Installer dmg file you will use to install the MAC BESAgent.
  5. Once the disk image has been created, mount it and simply double click the PKG (eg: BESAgent-8.2.1310.0_MacOSX.pkg) to launch the installer.

For client versions 8.2.1310.0 (8.2 Patch 4) and higher on OSX 10.6 and later:

The distribution includes one DMG (mountable Disk Image file) that contains utilities and a separate PKG download for the install or upgrade package. The files are identified as 10.6 versions in the file names.
  1. Download the corresponding BES Client package file to the Mac computer.
  2. Copy the PKG file to any directory and copy the masthead file for your deployment into the same directory. Make sure the masthead file is named actionsite.afxm.
  3. You may optionally include a pre-defined settings file (clientsettings.cfg) in the install directory to create custom settings for the Mac client at installation time.
  4. Launch the PKG installer by double-clicking the PKG file (eg: BESAgent-8.2.1310.0-BigFix_MacOSX10.6.pkg) and run through the installer. The agent will start up after the installation completes as long as the masthead file is included in the install directory.

Mac OS X - Fixlet Content

  1. To get the Fixlet content for the Mac BES Agent, you will need to subscribe your BES Server to the appropriate Fixlet site. To subscribe to a new Fixlet site, go to a computer with the BES Console installed.
  2. Download the Mac Evaluation masthead. (Note: This masthead is for Evaluation licenses only.)
  3. When prompted to open or save the file, click 'Open' and this will automatically open the BES Console.
  4. Log into the BES Console with your username/password.
  5. Once logged in, the BES Console will ask if you wish to subscribe to the Patches for Mac OS X Fixlet site, click OK.
  6. Type in your private key password and click OK.
  7. After the BES Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.

Red Hat Enterprise Linux

Red Hat Enterprise Linux - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

Red Hat Enterprise Linux - Installation Instructions

    Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BigFix Client RPM file to the Red Hat computer.
  2. Install the RPM by running the command rpm -ivh <path to BigFix Client RPM>.
  3. Copy your actionsite masthead to the Linux BigFix Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:BigFix Installers). If the masthead is not named 'actionsite.afxm', rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: In BigFix 4.0 and later, the masthead file for each BigFix Server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.bigfix.com:52311/masthead/masthead.afxm).
  4. Start the BigFix Client by running the command: /etc/init.d/besclient start.

Red Hat Enterprise Linux - Fixlet Content

To get the Fixlet content for the Red Hat BigFix Agent, you will need to subscribe your BigFix Server to the appropriate Fixlet site. To subscribe to a new Fixlet site, go to a computer with the BigFix Console installed.
  1. Download the appropriate masthead:
    • RedHat Enterprise Evaluation masthead (Note: This masthead is for Evaluation licenses only.)
  2. When prompted to open or save the file, click 'Open' and this will automatically open the BigFix Console.
  3. Log into the BigFix Console with your username/password.
  4. Once logged in, the BigFix Console will ask if you wish to subscribe to the Patches for RedHat Linux Fixlet site, click OK.
  5. Type in your private key password and click OK.
    After the BigFix Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.
Note: For further information regarding Redhat Enterprise Linux please click here.

Solaris

Solaris - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

Solaris - Installation Instructions

Note: Beginning with IEM 9.2 the Client is controlled by the service manager. To start or stop the agent use the svcadm {enable|disable|restart} BESClient command.
Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BigFix Client package file to the Solaris computer.
  2. Copy your actionsite masthead to the Solaris BigFix Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:BigFix Installers). If the masthead is not named 'actionsite.afxm, rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: You may need to create the directory /etc/opt/BESClient/ if it does not already exist.
    Note: In BigFix 4.0 and later, the masthead file for each BigFix Server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.bigfix.com:52311/masthead/masthead.afxm).
  3. Install the PKG by running the command pkgadd -d <path to BigFix Client package file>.
  4. In 9.2 and above the BigFix Client will be started automatically by the Service Manager, on older versions run the command /etc/init.d/besclient start.

Note: Earlier revisions of Solaris (7 and 8) did not include functions required for proper running of the BES Client in the libC (SUNWlibC package) libraries. Ensure that the libC libraries have been patched to a sufficient level so that the BES Client will operate correctly.

For Solaris 8, the latest version of patch 108434 must be installed:
http://sunsolve.sun.com/search/document.do?assetkey=1-21-108434-20-1

Solaris - Fixlet Content

Fuego Installation Instructions For Mac 2017

  1. To get the Fixlet content for the Solaris BES Agent, you will need to subscribe your BES Server to the appropriate Fixlet site. To subscribe to a new Fixlet site, go to a computer with the BES Console installed.
  2. Download the Solaris Evaluation masthead. (Note: This masthead is for Evaluation licenses only.)
  3. When prompted to open or save the file, click 'Open' and this will automatically open the BES Console.
  4. Log into the BES Console with your username/password.
  5. Once logged in, the BES Console will ask if you wish to subscribe to the Patches for Solaris Fixlet site, click OK.
  6. Type in your private key password and click OK.
  7. After the BES Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.

SUSE Linux

SUSE Linux - Downloads

Fuego Installation Instructions For Mac Pro

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

Fuego Installation Instructions For Mac Catalina

SUSE Linux - Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BES Client RPM file to the SUSE computer.
  2. Install the RPM by running the command rpm -ivh <path to BES Client RPM>.
  3. Copy your actionsite masthead to the Linux BES Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BES Installation folders (by default they are placed under C:BES Installers). If the masthead is not named 'actionsite.afxm, rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.

    Note: In BigFix 4.0 and later, the masthead file for each BigFix Server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.bigfix.com:52311/masthead/masthead.afxm).

  4. Start the BigFix Client by running the command /etc/init.d/besclient start.

SUSE Linux - Fixlet Content

To get the Fixlet content for the SUSE BigFix Agent, you will need to subscribe your BigFix Server to the appropriate Fixlet site.
  1. To subscribe to a new Fixlet site, go to a computer with the BigFix Console installed.
  2. Download the appropriate masthead
    (Note: This masthead is for Evaluation licenses only.)
  3. When prompted to open or save the file, click 'Open' and this will automatically open the BigFix Console.
  4. Log into the BigFix Console with your username/password.
  5. Once logged in, the BigFix Console will ask if you wish to subscribe to the Patches for SUSE Linux Enterprise Fixlet site, click OK.
  6. Type in your private key password and click OK.
  7. After the BigFix Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.

Note: For further information regarding SUSE (32-bit) Content please click here.

Ubuntu

Fuego Installation Instructions For Mac Os

Ubuntu - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

Fuego Installation Instructions For Mac 2016


Ubuntu - Installation Instructions

Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
  1. Download the corresponding BigFix Client DEB package file to the Ubuntu computer.
  2. Install the DEB by running the command dpkg -i <path to BigFix Client package>.
  3. Copy your actionsite masthead to the Linux BigFix Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:BigFix Installers). If the masthead is not named 'actionsite.afxm', rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
    Note: In BigFix 4.0 and later, the masthead file for each BigFix Server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.bigfix.com:52311/masthead/masthead.afxm).
  4. Start the BigFix Client by running the command: /etc/init.d/besclient start.

VMWare ESX Server

VMWare ESX Server - Downloads

For the latest BigFix release information, visit http://support.bigfix.com/bes/release/.

VMWare ESX Server - Installation Instructions

For installation instructions see RedHat Linux

VMWare ESX Server - Fixlet Content

  1. To get the Fixlet content for the ESX BigFix Agent, you will need to subscribe your BigFix Server to the appropriate Fixlet site. To subscribe to a new Fixlet site, go to a computer with the BigFix Console installed.
  2. Download the ESX Evaluation masthead. (Note: This masthead is for Evaluation licenses only.)
  3. Copy your actionsite masthead to the ESX BigFix Client computer (the masthead contains configuration, license, and security information). The actionsite masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:BigFix Installers). If the masthead is not named 'actionsite.afxm', rename it to 'actionsite.afxm' and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
  4. When prompted to open or save the file, click 'Open' and this will automatically open the BigFix Console.
  5. Log into the BigFix Console with your username/password.
  6. Once logged in, the BigFix Console will ask if you wish to subscribe to the Patches for ESX Fixlet site, click OK.
  7. Type in your private key password and click OK.
  8. After the BigFix Console subscribes to the site, it should automatically start gathering new Fixlet messages from the site.

Note: Firewall ports must be opened.