Home
WebUI Administration Guide
Read this guide for information about installing and administering the WebUI.
WebUI and Distributed Server Architecture (DSA)
Understand how to work with WebUI in Distributed Server Architecture (DSA).

WebUI Administration Guide
Read this guide for information about installing and administering the WebUI.
- Introduction
  This guide is intended for BigFix Master Operators and those who administer an BigFix deployment. If you are looking for information about using the WebUI, see the BigFix WebUI User's Guide.
- Deployment Requirements
  This guide contains information and procedures for installing the WebUI on BigFix Platform V9.5.5 or later. The WebUI is supported on BigFix Platform V9.5.5 and later versions.
- WebUI Installation
  Use these procedures to install or upgrade the WebUI on BigFix Platform versions 9.5.5 or later. Before you start the procedure:
- Remove the WebUI Service
  Use this procedure to remove the WebUI from BigFix Platform.
- Provisioning Users
  Use permission settings in the WebUI and the BigFix Console to control access to the WebUI and its functions.
- Managing Application Updates
  You can manage application updates through Application Update Manager.
- Editing Dashboards
  Use the WebUI’s editing tools to customize the WebUI Overview and Executive Overview dashboards.
- Performance
  This chapter provides an introduction to some tools for managing performance problems you might encounter with the WebUI. For a detailed discussion of BigFix and WebUI performance topics and tools, including planning, monitoring, and maintenance, see the BigFix Capacity Planning Guide.
- Log Locations
  All WebUI logs are stored in one default location. Logs are stored on the WebUI Server in the following locations (unless changed by the server setting _WebUI_Logging_LogPath).
- WebUI Server Settings
  Create or modify server settings on your WebUI server to control advanced aspects of the WebUI. These settings are for advanced users only and can be used to help troubleshoot problems or adjust behaviors to optimize performance.
- SAML 2.0
  BigFix supports SAML 2.0. SAML authentication is an application login mechanism that uses a configured Identity Provider (IdP) to authenticate users.
- Troubleshooting
  Read this section for information about any known issues using the WebUI application.
- WebUI and Distributed Server Architecture (DSA)
  Understand how to work with WebUI in Distributed Server Architecture (DSA).
- Supported Patch Sites
  A subset of BigFix patch sites is supported in the WebUI.
- Support
  For more information about this product, see the following resources:

WebUI and Distributed Server Architecture (DSA)

Understand how to work with WebUI in Distributed Server Architecture (DSA).

WebUI and DSA

If you are using DSA to provide redundancy and you have your WebUI installed on the primary server, when it fails, you will have to use the secondary server to install a new instance of the WebUI that connects to the secondary server. If the WebUI is installed on a separate server, there is no need to uninstall and reinstall it.

In both cases, when you deploy the WebUI against a non-primary server, configure the client setting on the WebUI host machine to connect to the secondary server using the WebUI server setting _WebUIAppEnv_PLATFORM_HOST. This prevents the WebUI instance from defaulting to using the host name specified in the masthead.

Note: Multiple instances of the WebUI are not currently supported. If you are reinstalling the WebUI service on a machine, uninstall the WebUI service first.

DSA and SAML

BigFix supports SAML authentication in a DSA environment. In the event of a primary server failure, you will need to separately configure each BigFix instance you want to enable in SAML. For example, in Microsoft Active Directory Federation Services (ADFS), define SAML Assertion Consumer Endpoints for:

The primary WebUI server, the primary BES root server, and the primary Web Reports server (if you are using Web Reports).
The secondary WebUI server, the secondary BES root server, and the secondary Web Reports server (if you are using Web Reports).