BMC Client Management - Technical Specifications Version 12.0
Legal Notices Copyright 1999, 2009 BMC Software, Inc. Copyright 1994-2014 Numara Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. FootPrints is the exclusive property of Numara Software, Inc. and is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other Numara Software trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. Cisco and Cisco NAC are registered trademarks or trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. IBM and IBM Domino are registered trademarks or trademarks of International Business Machines Corporation in the United States, other countries, or both. IT Infrastructure Library is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC. ITIL is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries. Linux is the registered trademark of Linus Torvalds. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation. Restricted rights legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address. BMC Software, Inc. 2101 CityWest Blvd, Houston TX 77042-2827, USA 713 918 8800 Customer Support: 800 537 1813 (United States and Canada) or contact your local support center
BMC Client Management - Technical Specifications TOC 3 Contents Prerequisites...4 Solution Overview...4 Hardware Requirements...4 Master, Database and Relays... 4 Console Requirements...7 Software Requirements...7 BMC Client Management Master Server... 7 BMC Client Management Database Server... 7 BMC Client Management Client and Relay... 8 BMC Client Management Console...9 Supported Directory Servers...9 Supported Browsers... 9 Supported Email Servers... 10 Supported Languages...10 Supported Configuration... 10 IPv6 Support... 10 Supported Virtualization...11 Bare Metal Hypervisors (Virtual Infrastructure Element)... 11 Default Ports...11 Further Reading...13 Glossary of Terms in BCM...15
4 BMC Client Management - Technical Specifications Prerequisites Prerequisites This document will provide a list of all supported platforms, usable databases and information regarding the specific prerequisites of each module in BMC Client Management. Solution Overview Automate desktop and server lifecycle management, support security/compliance initiatives and take command of IT assets with an integrated suite of products that delivers the power of an enterprise solution with the flexibility to add incremental functionality. BMC Client Management (BCM) allows administrators to easily take inventory of assets, install operating systems, deploy software and patches, assess vulnerabilities, manage power usage and support enduser desktop issues remotely, all from a centralized console. BCM employs ONE Agent, ONE Console and ONE database and provides all the functionality you need built-in, which includes a graphical view of your entire asset relationship, dashboards for easy reporting, indexed search capabilities, remote management for devices on the internet and at the center - Operational Rules - which are pre-built templates that enable you to granularly configure your network and customize the solution for your business. Hardware Requirements Master, Database and Relays This table discusses the recommended hardware per node count. It is important to understand that this document generalizes the hardware recommendations and the hardware requirements can be more or less for any given environment. When running in virtual environments, CPU, RAM, and NIC utilization on the host system can impact performance. Dedicated physical CPU, RAM, and NIC cards can improve performance. Evaluation or <500 nodes Master Server Each Relay 2,3 Dedicated DB 4 CPU: 1 Core: 2 Dedicated relay should not be required 1 Dedicated DB should not be required. Speed: Cache: RAM: Estimated Size: 2GHz 2MB 4GB 50GB
BMC Client Management - Technical Specifications Prerequisites 5 <20,000 nodes Master Server Each Relay 2,3 Dedicated DB 4 CPU: 1 1 2 Core: 4 4 4 Speed: 2GHz 2GHz 2GHz Cache: 8MB 8MB 8MB RAM: 8GB 8GB 16GB Disk Size: 65GB free space, 15k RPM 60GB 5 20GB or faster drives 5 <50,000 nodes Master Server Each Relay 2,3 Dedicated DB 4 CPU: 1 1 2 Core: 4 4 4 Speed: 2GHz 2GHz 3GHz Cache: 8MB 8MB 12MB RAM: 16GB 8GB 24GB Disk Size: 73GB free space, 15k RPM 60GB 5 50GB on an Oracle or or faster drives 5 PostgreSQL database on Linux <100,000 nodes Master Server Each Relay 2,3 Dedicated DB 4 CPU: 1 1 2 Core: 4 4 8 Speed: 2GHz 2GHz 3GHz Cache: 8MB 8MB 20MB RAM: 16GB 8GB 48GB
6 BMC Client Management - Technical Specifications Prerequisites Master Server Each Relay 2,3 Dedicated DB 4 Disk Size: 85GB free space, 15k RPM 60GB 5 100GB on an Oracle or or faster drives 5 PostgreSQL database on Linux <150,000 nodes Master Server Each Relay 2,3 Dedicated DB 4 CPU: 1 1 2 Core: 4 4 8 Speed: 2GHz 2GHz 3GHz Cache: 8MB 8MB 20MB RAM: 16GB 8GB 72GB Disk Size: 98GB free space, 15k RPM 60GB 5 150GB on an Oracle or or faster drives 5 PostgreSQL database on Linux <200,000 nodes Master Server Each Relay 2,3 Dedicated DB 4 CPU: 1 1 2 Core: 4 4 8 Speed: 2GHz 2GHz 3GHz Cache: 8MB 8MB 20MB RAM: 16GB 8GB 96GB Disk Size: 110GB free space, 15k 60GB 5 200GB on an Oracle or RPM or faster drives 5 PostgreSQL database on Linux 1. Required disk space varies based on size of deployed packages, patches and service packs. 2. Number of relays required will vary based upon network topology and other environmental factors. 3. These estimations are for infrastructures in which a Windows relay has a maximum of 2000 child nodes or 5000 for a Linux relay. If your infrastructure requires more nodes per relay contact BMC support for specific sizing. 4. Check with database vendor to identify any hardware limitations based upon version in use. Your licensed database version cannot utilize all hardware resources, for example, Microsoft SQL Express, Microsoft SQL Workgroup, Oracle Express. 5. The amount of required disk space is estimated for usage over 3 years if all space consuming functionalities are used. Individual estimations are as follows: patch management 18GB, software distribution 30GB, operating system distribution 5GB per image, other (temporary files, reports, and so on) 10GB.
BMC Client Management - Technical Specifications Prerequisites 7 Console Requirements Computers on which the Console is to be launched require at least 2 GB RAM. Software Requirements BMC Client Management Master Server The BMC Client Management master requires the Oracle Java Runtime Environment (JRE) version 1.7 or higher (provided with the installation program for Windows installations). Component Minimum Requirement 1,2,3,7,8 Windows Operating System Windows Server 2003 SP2 (32/64 bit) Windows Server 2003 R2 (32/64 bit) Windows Server 2008 SP2 (32/64 bit) Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2 Windows 7 (32/64 bit) Windows 8 (32/64 bit) Windows 8.1 (32/64 bit) Linux Operating Systems Linux RHEL 4.8, 5, 6 and 7 SUSE 10 and 11 CentOS 4.8, 5, 6 and 7 Debian 6.0 and 7.0 Ubuntu LTS (12.04, 14.04) BMC Client Management Database Server Component Minimum Requirement 1,2,3,5,6,7 Microsoft SQL Server Express, Standard and Enterprise editions (only supported for Windows masters) Microsoft SQL Server 2008 (32/64 bit) Microsoft SQL Server 2008 R2 (32/64 bit) Microsoft SQL Server 2012 (32/64 bit) Microsoft SQL Server 2014 (32/64 bit)
8 BMC Client Management - Technical Specifications Prerequisites Component Minimum Requirement 1,2,3,5,6,7 Oracle RDMBMS Oracle 9i: from 9.2.0.6 Oracle 10g: 10.0 and 10.1 (with client 9.2.0.6), 10.2 (patches might be required) Oracle 11g: 11.2.0.2 (with 10.2.0.4/5 or 11.2.0.2 client), 11.2.0.3 Note Refer to the Installation manuals for the complete list of pre-requisites. Postgres SQL (only supported for Linux masters) PostgreSQL 8 (8.4 minimum) PostgreSQL 9 BMC Client Management Client and Relay Component Minimum Requirement 1,2,3,4,7 Windows Operating System Windows Server 2003 SP2 (32/64 bit) Windows Server 2003 R2 (32/64 bit) Windows Server 2008 SP2 (32/64 bit) Windows Server 2008 R2 SP1 Windows XP (32/64 bit) Windows Server 2012 Windows Server 2012 R2 Windows Vista with SP1 (32/64 bit) Windows XP SP3 (32/64 bit) Windows XP Embedded SP3 (32/64 bit) Windows 7 (32/64 bit) Windows 7 Embedded (32/64 bit) Windows 8 (32/64 bit) Windows 8.1 (32/64 bit) Windows 8.1 Embedded Linux Operating Systems Linux RHEL 4.8, 5, 6 and 7 SUSE 10 and 11 CentOS 4.8, 5, 6 and 7 Debian 6.0 and 7.0 Ubuntu LTS (12.04, 14.04)
BMC Client Management - Technical Specifications Prerequisites 9 Component Minimum Requirement 1,2,3,4,7 Mac OS Intel Based Mac OS: v10.5 (Leopard) Intel Based Mac OS v10.6 (Snow Leopard) Intel Based Mac OS: v10.7 (Lion) Intel Based Mac OS v10.8 (Mountain Lion) Intel Based Mac OS v10.9 (Mavericks) 1. Minimum requirements do not include the total requirements for the server operating system or any other application(that is: MS SQL, MS IIS, antivirus, etc) installed on the same server. 2. If several BCM components (that is: BCM Master Server, database, or web server application) are installed together on a common server, the minimum requirements for each server component must be combined, and note 1 will also apply. 3. Actual requirements and product functionality might vary based on your system configuration and operating system. 4. Recommendation: >=512 Kbps connectivity from audited computer to BCM Relay. 5. Microsoft SQL Server must be case insensitive and have remote connections enabled 6. See BCM installation guide for detailed database pre-requisites. 7. Itanium 64-bit processes are not supported. 8. Windows XP 32- and 64-bit and Windows 7 32- and 64-bit are supported for evaluation and POCs only. Production installations should always use a server operating system. BMC Client Management Console The BMC Client Management console requires the Java Runtime Environment (JRE) version 1.7 (provided with the installation program) or higher. Supported Directory Servers Component Supported Platforms Microsoft Active Directory Microsoft Active Directory Services (ADS) 2003, 2008, 2012 Lotus Domino Lotus Domino 8.0, 8.5 Novell edirectory Novell edirectory 8.7, 8.8 Supported Browsers The BMC Client Management user interface and specifically the application kiosk MyApps requires one of the following browsers: Google Chrome (versions 24 and later) 1 Internet Explorer (versions 8 and later) Firefox (versions 18 and later) 1 Safari (version 6 and 7) 2 1. Requires the LocalLink Add-on to be installed if intranet shares are to be advertised in MyApps. 2. This browser does not support direct links to intranet shares in MyApps.
10 BMC Client Management - Technical Specifications Prerequisites Supported Email Servers Component Email Servers with support for SMTP Supported Platforms BMC Client Management requires SMTP for sending email notifications Secure SMTP (SSL) Authenticated SMTP Supported Languages Component Languages Supported Platforms English, French, German, Japanese, Spanish, Brazilian Portuguese Supported Configuration Core Functions Windows Mac Linux Discovery/Inventory x x x Applications Usage (Selfhealing and Blocking) x x 2 Software Deployment x x x OS Deployment x 1 Patch Management x x Remote Control x x Direct Access x x x USB & Port Security x Power Management x x x 1. The operating system for OSD must be listed in the supported Windows Operating Systems for the master server 2. Self-healing is only available on Windows Operating Systems IPv6 Support BMC Client Management supports Internet Protocol version 6 (IPv6) network addresses. You can install the BMC Client Management master and deploy BMC Client Management clients in an IPv6 configured network and make them accessible to clients on IPv4, IPv6, or both IPv4 and IPv6 (dual stack) configured hosts. IPv6 is an internet protocol that replaces IPv4. It expands the IP address space from 32-bit to 128-bit to significantly increase the number of available IP addresses. To comply with a United States of America federal mandate, the software products of government vendors must support operation on IPv6 networks.
BMC Client Management - Technical Specifications Prerequisites 11 IPv6 limitations The following limitations apply with regards to IPv6 support in BMC Client Management: Patch Managers cannot be installed on devices with IPv6 adresses, however, devices with IPv6 addresses can be patched. Operating systems cannot be deployed on devices with IPv6 addresses. Supported Virtualization Component Supported Platforms 1 Virtual Platform Support BMC Client Management (BCM) has been proven by BMC Software customers to function properly in virtualized data centers that use VMware ESXi, VMware Infrastructure and Microsoft Hyper-V Core Server 2008 R2. BCM is only supported in these environments if the product is installed on an approved OS platform, web server, and database. BCM might work properly on other virtualization products, but BMC Software has not tested them and verified that functionality. BMC Software has no documented statistics regarding the performance of BCM in these environments since the mix of outside vendors applications and hardware can have a direct impact on overall performance.additionally, should BMC Software believe that the virtualization layer is the root cause of an incident the customer will be required to contact the appropriate virtualization layer support provider to resolve the virtualization issue. Note, that BMC server components are not supported on VMware Server or VMware Workstation using the GSX engine in a production environment since it is not designed for hardware optimization. 1. The OSD Manager (functional agent module/role) is not supported on a virtual platform. It must be designated/reside on a physical host due to TFTP constraints with virtualization. Bare Metal Hypervisors (Virtual Infrastructure Element) Inventory Manager can discover bare metal hypervisors, detect their configuration and attached virtual machine, and allows for management of those virtual machines.this functionality is supported on: Component Supported Platforms VMWare vsphere, ESX and ESXi1 1 v3.5 and 4.x Microsoft Hyper-V 2008 1. The VMWare licensing policy limits the free version of VMware ESXi to read-only access by the VMWare vsphere SDK. To enable full functionality (that is, active management such as start/stop Virtual Machines) on a VMware ESXi host, the host must be licensed with vsphere Essentials. Default Ports Component Port/Description 1,2 Client Agent The general agent communication port as configured (default is 1610) Management Console The general console management port as configured (default is 1611) Bandwidth Throttling Bandwidth management port on relay servers (default is 1609)
12 BMC Client Management - Technical Specifications Prerequisites Component Port/Description 1,2 MyApps MyApps port on master server (default is 1612) Integration Port Port used for 3rd party integrations and set with specific SSL certificate (default is 1616) TCP Discovery TCP ports scanned for auto-discovery (default is 23,25,139) Multicast Traffic The multicast transfer agent listen port as configured (default is 2500) Active Directory LDAP LDAP port (default is 389) 1. Ports are configurable 2. Only the agent port is required, all other ports are optional.
BMC Client Management - Technical Specifications Further Reading 13 Further Reading BMC Client Management comes with a full set of documentation. Following you can find a suggested order of reference after this document, depending on your type of installation and which modules you purchased. Installation and getting started On site installation SaaS installation Description Database Reference and best practices This manual contains specific database installation and tuning instructions for use with BCM. If you have a dedicated database administrator you should point him to this manual before installing BCM. Windows/Linux installation SaaS installation First time installation instructions as well as upgrade instructions Asset Discovery * This manual guides you through the discovery of your network once the master and console is installed in preparation for the agent rollout. * If you don not want to follow the procedure explained in the OnDemand installation manual, you will find more options in this manual. Client Agent Rollout * This manual guides you through the first client and relay agent rollouts in your infrastructure. * If you don not want to follow the procedure explained in the OnDemand installation manual, you will find more options in this manual. User Interface and Basic Objects User Interface and Basic Objects This manual introduces you to the BCM console and its main objects that are always available, independent of which modules you purchased. Operational Rules Operational Rules The operational rules are a basic object as well, and always available. They are explained in a separate manual which does not only include use case procedures but also a reference of all operational rule steps.
14 BMC Client Management - Technical Specifications Further Reading BCM modules Depending on which modules you purchased, you might need to refer to different manuals as follows: Inventory Software Distribution Patch Management Remote Control Compliance Management Inventory Management Application Management Financial Asset Management Software Distribution Operating System Deployment Patch Management Remote Manager Compliance Manager Device Manager Power Manager Advanced use cases For advanced administrators and use cases additional manuals are available: Manual External Integrations Atrium Integration Diagnostic Tool Parameter Reference Technical Reference Customizing BCM WebAPI Operations for Integrating with BCM Chilli Reference Description This manual explains how to configure BCM for integration with BMC Remedyforce and BMC FootPrints Service Core. This manual explains how to configure BCM for integration with AtriumBMC FootPrints Service Core. This manual provides the BCM administrator with checks and verifications to investigate if something does not seem to work correctly and some general sanity checks. It also provides automatic repair operations where possible. This manual accompanies the other manuals and explains the available modules for the software, their parameters and the software s error codes. In this manual you will find information about logging in BCM as wel as some in depth technical information on more advanced subjects such as SSL, bandwidth management or autodiscovery. This manual provides information on advanced usage of BCM, for example, on customizing reports and the search, adding new languages to localization or adding custom operational rule steps. This is a reference of all REST functions that are implemented in BCM for data exchange. Chilli is a proprietary procedural programming language that comes with BCM and is heavily used in it, for example in the operational rule steps. It facilitates repetitive tasks and executes specific actions.
BMC Client Management - Technical Specifications Glossary of Terms in BCM 15 Glossary of Terms in BCM Master Server: Master Server Database: Super Master Server: Console: Relays: Client Agent: Secure Communications: Operational Rules: Agent-less Inventory: As part of the network topology, it is the primary server that connects to the database, answers requests from the Console, executes the appropriate database communications and receives and stores all information sent by the Client Agents. A database system in which each network or system component is modeled and operating in real-time, this database reacts to changes in the network and system components by updating and changing the corresponding objects in the database. Consolidates data from local Master Servers and enables configuration for distributed organizations with many independent business units and segregated IT teams. A Java -based graphical user interface that connects directly to the Master Server to display collected data, access reports, manage client devices remotely and configure the Master Server. Note: The Console can be installed on any device of your BCM architecture. Organizations requiring a distributed configuration for multiple locations can use this as an intermediate device to balance the network workload. One Relay per physical site is recommended with the maximum number of Agents per Relay limited to 2000 for a dedicated Relay and 500 for a Shared Device. The Agent that is installed on each target device receives data, instruction and also forwards data to with the Master Server. The Agent sends information about regularly defined intervals based on a predefined schedule of events or when polled by the Master Server. Communications between Consoles, Agents, Relays, Master Servers and Super Master Servers is set to HTTP using ports 1610-1612 by default. SSL can be enabled to secure communications and certificates may also be used for trusted authentication. Pre-built templates that enable allow you to granularly configure your network. BCM typically requires an agent to perform most functions, but basic hardware, software and configuration information about any asset connected to a network can also be remotely discovered
*458310* *458310* *458310* *458310* *458310*