Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
System Requirements of DSM HEAT Desktop and Server Management Booklet Release 2015.2 (Build: 7.3.0.3181) Latest Update: 11/10/2015 Table of Contents Detailed System Requirements 3 Depot 4 Database Server with the DSM Database (DSMDB) 6 Management Point with Business Logic 8 Management Point without Business Logic 11 Hints for using different Windows Server versions for Management Points 13 Managed Computers 15 Administrator Workstation 16 Test Computer 16 Notes on AddOns and HEAT Integration 17 Third Party Support 18 Linux 18 Mac OS 18 Citrix Support 18 Virtualization Management 20 DSM Patch Management 21 System Requirements for the Management Point Server 21 System Requirements for the Client Computer 23 HEAT Remote 24 Copyrights and Trademarks 26 2 Detailed System Requirements The system requirements for the DSM infrastructure components include the operating system, the hardware, software, net work and the configuration. The following table contains the operating systems supported by the main DSM components: l l l l l l l Depot (file server) Database server Management Point with Business Logic Management Point without Business Logic Managed Computer Administrator workstation Test computer 3 Depot DSM modules require a shared directory on the file server. Both the DSM program files and the DSM packages (the so called repository) are placed on this depot. Every user account needs Full control on the depot share. The actual file system permissions must be configured as follows: Read access for all users Read and Write access for administrators The share on the server on which you install HEAT DSM must not be changed at a later time. The first depot of an DSM environment is the central depot, where the program files are installed and updated. Other depots are the region depots, site depots or local depots. You can also use Network Attached Storages (NAS) shares for such depots which support the Common Internet File System (CIFS) protocol. You can also use "hidden shares". Make sure that "normal users" also have read access to the share. Supported Operating Systems l l l l l l l l l Windows Server 2003 (SP1 or higher) / Windows Server 2003 R2 Windows Server 2008 / Windows Server 2008 R2 Windows Server 2012 / Windows Server 2012 R2 Windows 10 Server * Windows XP Professional x86 (SP3) / Windows XP Professional x64 (SP2) Windows Vista Windows 7 Windows 8 / Windows 8.1 Windows 10 Current service packs are recommended. MS Client operating systems only support a limited number of parallel inbound connections. * supported experimentally: Windows 10 Server support is not part of the standard Quality Assurance and can be subject to future changes. When using Windows 10, any feedback is highly appreciated. 4 Hardware The depot requires at least: The manufacturer's requirements apply for the OS. Software If SMB is used, no additional software is needed. If the share is located on a NAS file server, please contact the Support for details. If HTTP depot is used: IIS 6.0 (or higher) activate WebDAV 5 Database Server with the DSM Database (DSMDB) The DSM Database (DSMDB) belongs to the management applications Business Logic Server and Business Logic Proxy. Other management applications such as Extended Reporting also use the DSMDB. In principle, it is possible to install the database system for the Management Database and the other components of the Management Point all on the same server. However, on larger networks we recommend using a second server for the database. Please note that two different Management Points cannot use the same database. Supported database systems MS SQL Server 2005 incl. Express MS SQL Server 2008 incl. Express MS SQL Server 2008 R2 incl. Express MS SQL Server 2012 Server incl. Express MS SQL Server 2014 Server incl. Express Current service packs are recommended. Special features such as Database Mirroring, AlwaysOn or Availability Groups are not part of the standard Quality Assurance . Their functionality can therefore not be guaranteed when used with HEAT DSM. Supported Operating Systems l l l Windows Server 2003 (SP1 or higher) / Windows Server 2003 R2 Windows Server 2008 / Windows Server 2008 R2 Windows Server 2012 / Windows Server 2012 R2 Hardware The manufacturer's requirements apply for the OS and database systems. Microsoft SQL Express If you are working in a small environment or if you are only testing, you can install SQL 2012 Express. You can use the database system in test environments or smaller environments up to 2000 clients. If you have activated Extended Reporting and DSM Inventory, the number of the managed clients is reduced by about a third.In productive environments or if you are using Business Logic Proxies (BLPs), we recommend applying database systems with full functionality. SQL 2012 Express (SP2, 32 and 64 bit) is provided on the DSM product DVD. 6 Network The following requirement must be satisfied: Management Point servers and database server for a single Management Point must be linked via a LAN. Configuration For the configuration of the database systems, the manufacturer's requirements apply. In addition, the following requirements must also be satisfied for use together with the Management Point: It is absolutely essential that Windows and SQL authentication is enabled in your database server’s security settings. To do this on the SQL Server, select the option SQL-Server and Windows in the Enterprise Manager (Security tab in the server’s properties dialog box). This setting is the SQL Server default setting. For the client NamedPipes and TCPIP protocol must be enabled The service SQL Server Browser must be started The setting Allow Remote Connection in the server’s security settings has to be active SQL Server should not be used with the Case-sensitive option. Otherwise problems may occur when importing data or searching for data in the DSMC! The name of the used database must not be master and it must not contain a dash sign. You can create several databases in one database system. User Accounts When creating the Management Point, a database user is required who will be assigned read and write permissions for the database. This database user must already exist before the Management Point is created. The Management Point stores this user and uses it for all database accesses. If the database is to be created automatically when the Management Point is being created, the Management Point Wizard also needs a database user who has permission to create a database. This user is used only once and is not stored. 7 Management Point with Business Logic The Management Point used by various management applications is installed on this server. In this context, Business Logic applications represent the central services for the access to the data of the DSM Database (DSMDB). The first Management Point of an DSM environment is the Central Management Point; this is where the Business Logic Server is installed together with the DSM Database (DSMDB). Other Management Points are referred to as Management Point only. In distributed environments, these Management Point may also have Business Logic applications. You cannot use a Management Point server with an underscore in its name. Business Logic Applications For management applications with business logic a server operating system is absolutely required. This applies for the following management applications: l l l l Business Logic Server (BLS) Business Logic Proxy (BLP) Relay Proxy Auxiliary Service BLS and BLP need to have a database as a prerequisite. The Relay Proxy instead uses the database of the BLS and therefore does not need an own database. The same applies to the Auxiliary Service. The individual components of the Management Point must be installed directly on the Management Point server. The only exception here is the database which is generally installed on a separate database server. It is only in the case of very small networks that we recommend also installing the database on the Management Point server. The system requirements for the database server can be found in the online documentation under Planning > System Requirements > Database Server. 8 Supported Operating Systems For Business Logic applications one of the following server operating systems is absolutely required: l l l l l l l Windows Server 2003 Standard, Enterprise, Datacenter (SP1 or higher) Windows Server 2003 R2 Standard, Enterprise, Datacenter Windows Server 2008 Standard, Enterprise, Datacenter Windows Server 2008 R2 Standard, Enterprise, Datacenter Windows Server 2012 Standard, Datacenter Windows Server 2012 R2 Standard, Datacenter Windows 10 Server * Current service packs are recommended. * supported experimentally: Windows 10 Server support is not part of the standard Quality Assurance and can be subject to future changes. When using Windows 10, any feedback is highly appreciated. Hardware The Management Point server requires at least: The manufacturer's requirements apply for the OS and database systems. The minimum RAM size for a Business Logic Server or Business Logic Proxy should be 2 GB. The required disk capacity on the Management Point server depends on the installed management applications. These have different requirements which need to be added when combining several applications. The requirements are listed in the system requirements of the individual application. Software l l l l IIS 6.0 (or higher, except for the Auxiliary Service) .NetFramework 3.5 (SP1) Power Shell 2.0 (for Auxiliary Service, only when using the Virtualization feature) A suitable database system (only when using the Management Point server as database server) The Internet Information Services (IIS) are a prerequisite for transmitting data between Management Points and managed computers via HTTP. 9 Network Management applications are set up and configured using the DSM infrastructure. As a result, the requirements for the DSM infrastructure apply to the Management Points as well. The following requirements must also be satisfied: When using several Management Points, the servers for the various Management Points on the LAN or WAN must be linked to each other. Management Point servers and database servers for a single Management Point must be linked via a LAN. All database and web servers in the DSM environment must be synchronized in time. Configuration When using Windows Server 2003, 2008, and 2012 specific configuration requirements apply (see Hints for using different Windows Server versions for Management Points). 10 Management Point without Business Logic For Management Points which contain specific management applications only, a computer with a client operating system may also be used. Management Applications You may install the following management applications on Management Points which are installed on a client OS: l l l l l l l OSD Proxy Client Proxy Service Installation Service (SIS) Distribution Service Event Dispatcher Transport Layer Patch Management Service Supported Operating Systems l l l l l l l l l l l l l Windows Server 2003 Standard, Enterprise, Datacenter (SP1 or higher) Windows Server 2003 R2 Standard, Enterprise, Datacenter Windows Server 2008 Standard, Enterprise, Datacenter Windows Server 2008 R2 Standard, Enterprise, Datacenter, Core* Windows Server 2012 Standard, Datacenter, Core* Windows Server 2012 R2 Standard, Datacenter, Core* Windows 10 Server * Windows XP Professional x86 (SP3) Windows XP Professional x64 (SP2) Windows Vista Ultimate, Enterprise, Business Windows 7 Professional, Enterprise, Ultimate Windows 8 / 8.1 Professional, Enterprise Windows 10 Professional, Enterprise (incl. LTSB and WTG), Education * supported experimentally: Windows 10 Server and Core support is not part of the standard Quality Assurance and can be subject to future changes. When using Windows 10 or Core, any feedback is highly appreciated. Hardware The manufacturer's requirements apply for the OS. 11 Software This software is required on all Management Points: l .NetFramework 3.5 SP1 This software is only required for OSD Proxy, Client Proxy and Event Dispatcher: l IIS 6.0 (or higher) 12 Hints for using different Windows Server versions for Management Points Windows Server 2008 (R2) and 2012 (R2) Depending on the management applications which are installed on a Windows Server 2008/2012, certain features and roles must be installed on the server. The following figure schematically shows which features and roles are required by a Management Point, on which Business Logic applications are running (BLS, BLP, Relay Proxy, Auxiliary Service): When installing a Management Point you will be supported by DSM regarding the required prerequisites. DSM automatically checks, whether the prerequisites are met to install the desired management applications on the Management Point. DSM indicates any missing software, features and roles on the server. 13 Windows Server 2003 This chapter contains the restrictions and peculiarities when installing Management Points on MS Windows Server 2003. Authentication for the IIS Database In order to perform the required authentication, the Management Point (MP) needs to query the domain controller (DC) to check a user's AD permissions. For this task, the MP needs a user account with sufficient network permissions (READ access to the Global Catalog per "GetRootDSE" as a minimum). The MP will use the first available user account from the following list: 1. SIS account of the site that contains the master depot of the Management Points' site structure context object. 2. Distribution Service account of the site that contains the master depot of the Management Points’ site structure context object. 3. DSM Runtime Service account of the site that contains the master depot of the Management Points’ site structure context object. 4. IIS account. 14 Managed Computers Computers that are to be managed with DSM modules and have the DSM Client installed. Supported Operating Systems l l l l l l l l l l l l l l l l Windows XP Professional x86 (SP3) Windows XP Professional x64 (SP2) Windows Vista Ultimate, Enterprise, Business Windows 7 Professional, Enterprise, Ultimate Windows Embedded Standard 7 SP1 Windows 8 Professional, Enterprise, Windows To Go Windows 8.1 Professional, Enterprise, Windows To Go Windows 10 Professional, Enterprise (incl. LTSB and WTG), Education Windows Thin PC Windows Server 2003 Standard, Enterprise, Datacenter (SP1 or higher) Windows Server 2003 R2 Standard, Enterprise, Datacenter Windows Server 2008 Standard, Enterprise, Datacenter, Core Windows Server 2008 R2 Standard, Enterprise, Datacenter, Hyper-V, Core Windows Server 2012 Standard, Datacenter, Hyper-V, Core Windows Server 2012 R2 Standard, Datacenter, Hyper-V, Core Windows 10 Server * * supported experimentally: Windows 10 Server support is not part of the standard Quality Assurance and can be subject to future changes. When using Windows 10, any feedback is highly appreciated. Current service packs are recommended In DSM, a managed computer is clearly identified based on its hardware information (e.g. SMBIOS GUID and Initial MAC Address). An exception are "computers" on USB sticks with Windows To Go operating system, which are offered for Windows 8/8.1. Since there is no identification of such computer objects based on the hardware, SID and FQDN of the operating system are used instead. Thus, a unique identification is possible even if the USB stick is connected to different computers. In the Basic Inventory Windows To Go is reported as Installed Operating System Flavor. Hardware The manufacturer's requirements apply for the OS. Configuration A computer that is to be managed by the DSM modules must be able to communicate with the Management Point via HTTP. 15 Administrator Workstation The administration of your DSM environment is done via the DSM Console (DSMC). To administer your DSM environment in the DSMC you will need an administrator workstation. You can operate the DSMC directly on the Management Point server or from any workstations that fulfill the requirements below. Software The following MUST be running on the workstation: Internet Explorer Version 7.x or higher Current Service Packs are recommended Configuration Management Point websites that are opened in the Internet Explorer need to be registered in the Local Intranet zone of the Internet Properties. In this case, the default settings are presumably kept for Security (Medium). DSM modules automatically enter Management Point websites in Local Intranet when the DSMC or the Installer are started on the computer. This needs to be done manually if neither DSMC nor Installer have been started; or you need to log on additionally each time you open the website. Test Computer Testing packages is easier if you use an additional workstation; this workstation acts as a managed computer and corresponds to the workstation of a “normal“ user that is managed by DSM modules. 16 Notes on AddOns and HEAT Integration DSM Web DSM Web is a DSM Management application; it is installed on Management Points with Business Logic Server automatically. For all areas of the DSM Web, a user needs specific rights to employ it. Assign the required rights on ORG level with the Manage Permissions task. In order to use the Web Console on the computer from which you will start DSM Web, you need the following application: Silverlight 5 Please enter the following link in your browser to get the required plugin:http://www.microsoft.com/silverlight/ Dependent on the operating system, you can use the following browsers: http://www.microsoft.com/getsilverlight/locale/en-us/html/installation-win-SL5.html Silverlight is no longer supported by new versions of browsers such as Microsoft Edge. DSM Web will therefore be transmitted to a new platform in one of the next releases. ITSM, HEAT and Discovery Integration The integration applies to all supported platforms. HEAT/ITSM requires basically the same release version as DSM. 17 Third Party Support Linux Using DSM OS Deployment you may install the following Linux operating systems on client computers: l l l l l l CentOS 5 and 6 Fedora 9 and 10 OpenSUSE 10.3, 11 and 12 Red Hat Enterprise Linux Client 5, 6 and 7 SUSE Linux Enterprise Desktop 10 and 11 SUSE Linux Enterprise Server 10 and 11 The manufacturer's hardware requirements are recommended. In order to install and run the DSM Unix Client on 64 bit systems, the 32 bit libraries must be installed. Mac OS The following Mac operating systems can be managed with HEAT DSM: l MacOS X Citrix Support The DSM Citrix Integration is installed on the Central Management Point in the DSM environment and is completely integrated in DSM NetInstall. Therefore the DSM Citrix Integration has the same requirements as DSM NetInstall. The DSM Citrix Integration is integrated into and can be managed completely from the DSM Console (DSMC). For the complete functionality of the DSM Citrix Integration, you also need the DSM OS Deployment (OSD). By installing the DSM Citrix Integration, OSD is extended to contain specific OSD packages you can use to automatically install Citrix Servers and Citrix Farms. Computers onto which the Citrix Server software shall be installed have to meet the requirements specified mentioned hereafter. You can either install Citrix Servers "out-of-the-box" via DSM OS Deployment or import existing Citrix Servers with Citrix Farms into the DSM environment. Hardware Requirements for Installing Citrix Platforms Please find detailed information concerning planning Citrix Server farms (e. g. on special adaptations of the supported operating systems, system hardware requirements and database usage) on the Citrix® homepage in the Citrix Product Documentation Library. 18 Software Requirements for Installing Citrix Platforms Prior to installing Citrix XenApp, you have to install Microsoft Power Shell 2.0 on the Management Point that will host the Citrix Management Suite. Please note that it is now possible to install DSM Citrix Integration on every Management Point of your DSM environment. The former restricition for the DSM Citrix Integration only to be installed on a Business Logic Server (BLS) or Business Logic Proxy (BLP) has been dropped. Citrix platforms supported by the DSM Citrix Integration Due to the close interconnection of the DSM Citrix Integration with DSM OS Deployment and DSM NetInstall, you can administer Citrix Farms from one source. With OSD, you can automate the installation and administration of Citrix® Servers, client computers and their respective Citrix Farms. During the setup, the required scripts and packages are imported and provided in the Global Software Library. DSM Citrix Integration supports the following Citrix® platforms: Citrix XenApp 7.6 EN for 64-bit systems Citrix XenApp 7.5 EN for 64-bit systems Citrix XenApp 6.5 EN for 64-bit systems Citrix XenApp 6.0 EN for 64-bit systems 19 Virtualization Management To employ DSM's virtualization functionality, please install the Microsoft PowerShell 2.0 on the following computers: l l The Management Point where the Business Logic Auxiliary Server is installed (by default: Primary BLS) The administrator workstation.This is the computer where you start the DSMC. Application Virtualization DSM supports the following virtualization platforms: l l l l l VMWare Thin App 4.0, 4.62 Citrix XENApp 5 Citrix XENApp 6.5 (x64) Citrix XENApp 7.5 (x64) Citrix XENApp 7.6 (x64) Desktop Virtualization DSM supports the following virtualization platforms: l l VMware View 4.5 Citrix XenDesktop 5 The manufacturer's hardware requirements are recommended. For the management with HEAT DSM you may use virtualization platforms without any special configurations. Hardware Virtualization DSM supports the following virtualization platforms: l l VMWare ESX Server 4.0, 4.1 Citrix XEN Server 5.5 and higher Microsoft Hyper-V at the moment is not supported by DSM. This virtualization solution can however be integrated by means of customizing with the help of Professional Services Consulting. 20 DSM Patch Management System Requirements for the Management Point Server The DSM Patch Management (Classic and HEAT PatchLink) is installed on the Central Management Point and is integrated completely in DSM NetInstall. If necessary, you can also use another Management Point on ORG level. Therefore, you can execute Patch Management completely from within the DSM Console (DSMC). For the integration into the Management Point, the Management Point Server has to meet the same hardware and software requirements as in DSM NetInstall. Specific requirements for the Management Point Server apply to the following areas of DSM Patch Management: Operating System Hardware Software Network Configuration Operating System DSM Patch Management has the same requirements as DSM NetInstall. Find a list of the operating systems DSM NetInstall supports in online documentation. Hardware Management Point with Patch Management Service We recommend that you provide at least 500 MB of RAM for Patch Management. HEAT PatchLink downloads the mass data of the patches to the following directory: C:\Program Files (x86)\HEAT Software\LPR\content. Depending on the number of different operating systems, this directory needs 500 MB to 1 GB of available free storage. HEAT PatchLink gets the mass data from the following servers: http://heat.cdn.lumension.com and https://akamai.net Managed Computers HEAT PatchLink copies the PM Client files and the individual patch catalog to this directory: C:\Program Files (x86)\HEAT Software\LPR\client. Here, 200 MB of free storage is enough. 21 Software DSM Patch Management requires the following DSM environment: DSM NetInstall Network The Management Point Server must have: Internet access Alternatively for Classic Patch Management: Access to a local WSUS server or a local update catalog 22 Configuration Please customize virus scanners for optimal use of DSM Patch Management: When downloaded, the update catalog is stored in the directory <Share>\Work\Master\Projects. Make sure to exclude this directory when using a virus scanner to avoid problems when loading and evaluating the catalog. System Requirements for the Client Computer DSM Patch Management creates patch packages for Microsoft's product updates and security patches. HEAT PatchLink supports the patch installation of numerous non-Microsoft and 3rd Party products. The following requirements have to be met so that these patch packages can be installed on the computers. For client computers there are the following specific requirements: Operating system Software Operating System Patch packages can be installed on all client and server operating systms that are supported by DSM. Software To be able to install all available patches on a Client computer, the following software has to be installed as a minimum: Windows Installer 3.1 23 HEAT Remote The system requirements for HEAT Remote refer to both the computer of the operator and the client computer that is remote controlled by the operator. Hardware The following hardware requirements apply to HEAT Remote: Intel x86 or x64 processor (or compatible) 333 MHz CPU minimum 256 MB RAM minimum 55 MB minimum free disk space Operating System HEAT Remote supports the following 32 bit and 64 bit operating systems: Windows XP Professional Windows Server 2003 Windows Server 2003 R2 Windows Vista Windows 7 Windows 8/8.1 Windows 10 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Network HEAT Remote is set up and configured using the DSM infrastructure. Therefore the same requirements apply for the network environment. In addition, one of the following requirements must also be satisfied: The client and operator computers must be connected via the local network (the client is a managed computer in the DSM environment). The operator computer additionally needs a connection to the Remote Cloud in the internet. The client and operator computers must be connected to the internet. 24 Internet For communication between the operator and the client computer is an existing internet connection with the following minimum values: l l 512 kbps minimum 6000 kbps recommended Supported browsers (oldest version): l l l Internet Explorer 6+ Mozilla Firefox 1.0+ Chrome 25 Copyrights and Trademarks Copyright © 1995-2015 HEAT Software USA Inc. All Rights Reserved USE OF THIS SOFTWARE, SUBSCRIPTION SERVICES, AND RELATED USER DOCUMENTATION IS SUBJECT TO THE TERMS AND CONDITIONS OF THE APPLICABLE HEAT SOFTWARE END-USER AGREEMENT, HEAT CLOUD SUBSCRIPTION SERVICES AGREEMENT, AND ANY TERMS OF SERVICE (“SUBSCRIPTION AGREEMENT”). YOU MUST AGREE TO THE TERMS AND CONDITIONS OF THE SUBSCRIPTION AGREEMENT IN ORDER TO USE THE SOFTWARE AND SUBSCRIPTION SERVICE. WARNING: The software described in this manual and its related user documentation are protected by copyright law. In no event, shall any part of the software or related user documentation be copied, reproduced, distributed, transmitted, stored in a retrieval system, or translated into any language, without the express written permission of HEAT Software USA Inc. HEAT Software Trademark Information The following are trademarks of HEAT Software USA Inc. and/or its affiliates in the United States and/or other countries: FrontRange Solutions®, FrontRange™, SaaSIT™, ModernizeIT™, SaaS2™, GoldMine®, GoldSync®, GoldMine® Answer Wizard™, GoldMine® Management Intelligence™, GoldMine® Manager's Console™, iGoldMine™, HEAT®, HEAT® Service & Support™, HEAT® PowerDesk™, iHEAT™, HEAT® Self Service™, HEAT® Manager's Console™, HEAT® Answer Wizard™, HEAT® Quick Start Wizard™, InfoCenter®, Automated Processes™, First Level Support®, enteo®, DeviceWall®, Centennial Discovery®, Discovery Dashboard®, MicroAudit®, SAM™, The HEAT Is On™, and other HEAT Software products and brands. Other products and brands are the trademarks of their respective owners or companies. Contact HEAT Software USA Inc. at [email protected]. Copyright notice updated: February 2015