Introduction

Installing and configuring Browsium software is easy to do using existing enterprise software deployment tools, but there’s a few more things customers need to manage the ongoing ownership of the software. The Browsium Client Management Server (BCMS) was created to help with the commonly required tasks customers faced with enterprise-wide deployments. In addition, deploying BCMS can now help streamline deployments by centralizing some of the tasks and mechanisms that used to require touching end point systems.

The central premise of BCMS is simple — it’s the tool organizations need to manage software licenses, enable/disable authorized clients and system settings all in one place. Think of BCMS as a licensing server, with a few added features to control the Browsium specific settings. BCMS was created to make life easier for customers when dealing with both large and small deployments — many of the issues may be different at scale, but customers consistently faced similar problems that could be addressed with the creation of this new management tool and console.

BCMS and Configuration Management

It’s important to understand that BCMS is not designed for Configuration Management — customers have spoken loud and clear that they want maximum flexibility with configuration locations. Browsium Ion and Catalyst will continue to offer the options customers have come to enjoy. Configurations can be kept on a server or deployed to the local file system. That all remains the same with BCMS.

BCMS role with Clients Explained

Browsium solutions are by their nature going to be client oriented. Making software to help deploy, manage and control the modern workspace of browser-based applications means the software needs to sit on the end user client machine to control and manage the settings and experience as required by the business. As such, the focus of software at Browsium has always been around the client side. The introduction of BCMS was done to remove some of the more organizational management tasks from the client end, saving time and making the overall process easier.

Once deployed, organizations will use BCMS for systems management of Browsium software. Clients will connect to the customer on-premises BCMS regularly to ensure they are still authorized and ensure they function properly. Customers have requested more control over which clients should continue to operate and those they can deprecate. BCMS provides that ability in a simple to use interface. Retiring older systems — or simply deactivating users who no longer require the software — is easier than ever.

During installation, or after if desired, clients simply need to be setup with the location of the BCMS. They will contact the BCMS to obtain licensing and register. That’s it. Nothing else needs to be deployed or configured for the system to operate. Clients will regularly ‘check in’ with the BCMS to ensure nothing has changed with licenses or authorization. Should the client connect and find they are no longer authorized, the software will disable itself automatically.

{width=“0.9194444444444444in” height=“0.9194444444444444in”}Section Two

Installation

In this section, you will learn:

• About the BCMS components

• Software requirements for BCMS

• How to Install BCMS

• How to configure command line switches for installation over a network