HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Part number: TB581-96332 Ninth edition: February 2013
Legal and notice information © Copyright 2010, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface ................................................................................................ 9 1 Overview ........................................................................................ 11 About basic system configurations ............................................................................................... Prerequisites for basic configurations ........................................................................................... DVD installations ..............
About post-installation tasks (overwrite or upgrade) ....................................................................... Post-installation tasks (overwrite or upgrade) ........................................................................... Backing up databases ........................................................................................................ Refreshing storage systems ...................................................................................................
Related information ................................................................................................................... 57 Conventions ............................................................................................................................. 58 A Unattended installation and removal .................................................. 61 Command View AE Suite server unattended installation .................................................................
Figures 1 Command View AE Suite: Basic configuration ............................................................
Tables 1 Server installation path requirements ......................................................................... 16 2 Database file storage path and location requirements .................................................. 17 3 Appropriate memory heap size for Common Component ............................................. 19 4 Appropriate memory heap size for the Device Manager server ..................................... 19 5 Database path and location requirements ..................................
Preface This manual provides information about installing and removing HP StorageWorks P9000 Command View Advanced Edition Suite.
Preface
1 Overview This chapter provides basic system configuration information for HP StorageWorks P9000 Command View Advanced Edition Suite. About basic system configurations HP StorageWorks P9000 Command View Advanced Edition Suite can manage different storage systems. A basic configuration must include a management server and appropriate components. The following figure shows a basic system configuration.
Provides user account management, security monitoring, and other functions common to all Command View AE Suite products. • Device Manager server The component used by Command View AE Suite to manage storage system volumes. • Tiered Storage Manager server The component used by Tiered Storage Manager to manage storage system volume migration. • Replication Manager server The component used by Replication Manager to manage storage system volume replication.
• The management server and management client communicate with each other using non-SSL protocol. • For copy pair management: • Command View AE Suite is configured for open-volume copy pair management at a single site. • Copy pairs are centrally managed from a pair management server. • For collecting information about managed hosts: • The Device Manager agent is installed only on the pair management server used to centrally manage copy pairs.
Programs installed by server administrators • Plug-in for Virtualization Server Provisioning NOTE: The following software versions support an upgrade installation from the installation DVD. Version 5.0 or later: • Device Manager server • Tiered Storage Manager server Version 6.0 or later: • Replication Manager server When using an earlier software version, first upgrade to 6.x and then to 7.0 or later.
2 HP StorageWorks P9000 Command View Advanced Edition Suite server installation This module describes how to install and set up servers. Planning for server installation Before installing the HP StorageWorks P9000 Command View Advanced Edition Suite (Command View AE Suite) software on the server, verify the conditions and gather the information you need to perform the installation.
Windows: installation-destination-path\backup Linux: /var/installation-destination-path/backup • Memory heap size The expected volume and copy pair counts in the following table are based on the default memory heap size.
Condition Requirements Windows: • Do not include consecutive spaces. • Do not include a period or space at the end of a folder name. • Do not use parentheses, except when the path includes the Program Files (x86) directory. • Do not include a symbolic link and junction for the installation folder. • Do not specify the root of a drive as the destination.
Condition Requirements Windows: • Do not include consecutive spaces. • Do not include a period or space at the end of a folder name. • Do not use parentheses, except when the path includes the Program Files (x86) folder. • Do not include a symbolic link and junction for the installation folder. • Do not specify the destination as a folder directly under a drive (such as D:\ ). • Do not specify a network drive.
Use the following tables to determine the appropriate memory heap size.
Memory Heap Size OS Managed Resource OS other than Windows (IPF) The number of LDEVs per storage system Small (Min: 128 MB, Max: 256 MB) Medium (Min: 128 MB, Max: 512 MB) Large (Min: 128 MB, Max: 1,024 MB) 2,000 or less 2,001 to 6,000 6001 or more Legend: --: You cannot use Device Manager to manage storage systems that have more than 6,000 LDEVs.
• Management server prerequisites (see “Prerequisites for the management server (Linux)” on page 21) • Kernel parameter values and shell restrictions (see “About setting kernel parameters and shell restrictions (Linux)” on page 21 and “Modifying kernel parameter values and shell restrictions” on page 30) • Registering firewall exceptions (see “Registering firewall exceptions (Linux)” on page 30) CAUTION: The following concerns storage tiers and upgrades Command View AE Suite to version 7.0 or later.
NOTE: Ensure that the maximum value set for a kernel parameter does not exceed the maximum value specified by the operating system. Recommended Red Hat Enterprise Linux /etc/sysctl.conf values Before installing Command View AE Suite on a Red Hat Enterprise Linux system, set the kernel parameters for the /etc/sysctl.conf file.
Tiered Storage Manager Software Replication Manager Software 123 50 50 kernel.shmmax 327487488 50000000 100000000 kernel.shmmni 497 0 0 kernel.shmall 442745856 100695040 100000000 Kernel Parameter 2nd parameter of kernel.sem Device Manager These formulas are for calculating kernel parameter values: • For kernel.
+ value-for-Replication-Manager , value-for-HiRDB } NOTE: Max{x, y, z} indicates the maximum value among x, y, and z. Recommended Red Hat Enterprise Linux 5 /etc/security/limits.conf values Before installing Command View AE Suite on a Red Hat Enterprise Linux system, set the shell restriction values for the /etc/security/limits.conf file. Set the shell restrictions for soft and hard settings. NOTE: The soft value must be less than or equal to the hard value.
, initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager , value-for-HiRDB } NOTE: Max{x, y} indicates the larger value of x or y. Recommended Red Hat Enterprise Linux 6 /etc/security/limits.conf values Before installing Command View AE Suite on a Red Hat Enterprise Linux system, set the shell restriction values for the /etc/security/limits.conf file. Set the shell restrictions for soft and hard settings.
value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager , value-for-HiRDB } NOTE: Max{x, y} indicates the larger value of x or y. Recommended Red Hat Enterprise Linux 6 /etc/security/limits.d/90-nproc.conf values Before installing Command View AE Suite on a Red Hat Enterprise Linux system, set the shell restriction values for the /etc/security/limits.d/90-nproc.conf file.
shell-restrictions-value-to-be-set = Max{ Max{ value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager , value-for-HiRDB } NOTE: Max{x, y} indicates the larger value of x or y. Recommended SUSE Linux Enterprise Server /etc/sysctl.conf values Before installing Command View AE Suite on a SUSE Linux Enterprise Server system, set the kernel parameters for the /etc/sysctl.
Kernel Parameter kernel.shmall Installer Check value Operating System Initial Value 695869696 268435200 Common Component HiRDB 26214400 Table 15 Kernel parameter values for SUSE Linux Enterprise Server /etc/sysctl.conf (2/2) Tiered Storage Manager Software Replication Manager Software 117073 512 512 162 30 30 kernel.msgmni 44 0 0 4th parameter of kernel.sem 10 1 1 2nd parameter of kernel.sem 123 50 50 kernel.shmmax 327487488 50000000 100000000 kernel.
+ value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-HiRDB • Other kernel parameters and shell restrictions: kernel-parameter-value-to-be-set = Max{ Max{ value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager , value-for-HiRDB } NOTE: Max{x, y, z} indicates the maximum value among x, y, and z.
Shell Restriction Installer Check value Operating System Initial Value HiRDB Common Component nproc (soft/hard) 4262 4096 512 165 Table 17 Shell restriction values for SUSE Linux Enterprise Server /etc/security/limits.
NOTE: For information about registering port numbers as exceptions, see “Avoiding port conflicts” on page 21. Command View AE Suite server installation When you install Command View AE Suite on the management server, use the installation procedure that is appropriate for the operating system you are using. Server installation prerequisites Before installing Command View AE Suite, review the information in “Planning for server installation” on page 15.
NOTE: If the installation window does not open, run the following command: DVD-drive:\HCS\setup.exe 4. 5. 6. When you are prompted, enter the required information. In the Installation Completed window, select the When installation completes, open the Device Manager GUI check box. Click Finish. The GUI login window appears. Installing Command View AE Suite on Linux Install Command View AE Suite on a Linux host by using the installation DVD. 1. 2. Log on to Linux as the root user.
After you have created a storage administrator, the storage administrator can register storage systems and hosts, add accounts for other storage administrators, and begin operating Command View AE Suite. Verifying the installation You can verify that the installation was successful by accessing the web client from a browser. 1. 2. Start a Web browser.
NOTE: After you install a Command View AE Suite product, you can add permissions (roles) for that product to existing user accounts. 1. 2. 3. 4. 5. 6. 7. Log in to Command View AE Suite using the System account. On the Administration tab, click Users and Permissions. In the tree view, click Users and then Add User. Specify the required information, such as user ID and password. On the Administration tab, click User Groups.
These permissions are required when using the Tiered Storage Manager CLI. In addition, All Resources must be assigned and roles must be set. • Admin: Allows the user to view information about Tiered Storage Manager resources and tasks. • Modify: Allows the user to perform any operation from Tiers on the Resources tab, and migrate volumes. • Execute: Allows the user to view information about Tiered Storage Manager Software resources and execute Tiered Storage Manager tasks.
About post-installation tasks (overwrite or upgrade) After aCommand View AE Suite installation, set the information required by each installed product according to the version of each product before the overwrite or upgrade installation. When upgrading from version 7.1.0 or earlier, existing user accounts are migrated according to the previous environment. After upgrading, the storage administrator can modify user group and resource group assignments as necessary.
Common-Component-installation-folder\bin\hcmdsbackups /dir folder-forstoring-backup-files /auto For Linux: Common-Component-installation-directory/bin/hcmdsbackups -dir directoryfor-storing-backup-files -auto NOTE: The dir option is used to specify the absolute path of the folder or directory on the local disk where the database backup files are stored. Verify that the folder or directory specified does not already include any files or subdirectories. (For Linux, do not specify a path that includes a space.
When managing the virtualization server VMware ESX by using Device Manager, you need to apply the latest virtualization server configuration to the database by using one of the following methods: • In the Add Hosts window, re-register the virtualization server in Device Manager. • From the Hosts tab in the Administration tab, update the information for each virtualization server.
The following table contains the necessary information for user account settings after an upgrade. Table 19 Account settings after upgrading Before upgrading From version 6.x and earlier 6.x and earlier Device Manager permissions (roles) Y Y Tiered Storage Manager permissions Resource group None All Resources None User defined resource groups After upgrading Registered in built-in user groups according to Device Manager permissions.
Before upgrading From version Device Manager permissions (roles) Tiered Storage Manager permissions Resource group After upgrading Registered in built-in user groups according to Device Manager permissions. 7.0.0 7.0.1 Y Y All Resources 7.1.0 Y None All Resources User groups, resource groups, and roles are inherited. Operations can be restarted without performing any additional tasks. None User defined resource groups User groups, resource groups, and roles are inherited.
2. 3. Register SMTP authenticated users to Device Manager. Customize the email template (optional). For more information, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide. Synchronizing Replication and Device Manager databases After performing an overwrite installation or upgrade, you must synchronize the Replication and Device Manager databases. 1. If Replication Manager Application Agent version 7.
HP StorageWorks P9000 Command View Advanced Edition Suite server installation
3 Agent installation This module describes how to install and set up Device Manager agents. Planning for Device Manager agent installation Before you install the Device Manager agent, verify the prerequisites and gather the information you need to perform the installation. Prerequisites for agent installation Before performing a new installation, gather the appropriate information for the installation wizard, including the installation folder.
• HiScan command execution schedule. Default: Daily at 2:30 AM. For RAID Manager: • Installation location. • Default on Windows: Device Manager agent installation drive. • Default on UNIX: /HORCM • By default, copy pairs are not batch managed by the agent host (default is No). NOTE: The host name of the machine where the Device Manager agent is installed must be no longer than 50 bytes.
NOTE: The host name of the machine where the Device Manager agent is installed must be no longer than 50 bytes. Prerequisites for agent installation locations Before specifying an installation folder for the Device Manager agent, verify that the required disk space is available. When creating the installation location for the Device Manager agent, adhere to the naming conventions in the following table.
About HiScan command execution The HiScan command configures Device Manager agents to send information to the server on a regular basis. You can schedule HiScan for hourly, daily, or weekly execution. NOTE: If you specify weekly executions, also specify the day of the week you want the scan to run. If no HiScan execution periods are set, agents do not regularly send acquired information to the server.
• Device Manager agent versions 5.7 and later are compatible with the Daylight Saving Time (DST) rules implemented in the United States and Canada in 2007. When using the Device Manager agent in these time zones, set the host operating system for the new DST rules according to information provided by the operating system vendor.
NOTE: The Microsoft terms for this functionality differ depending on the Windows operating system. These terms can refer to the same functionality: • Terminal Services in the Remote Administration mode • Remote Desktop for Administration • Remote Desktop Connection Keep the following in mind when working with Windows remote desktop: • When using the remote desktop, connect to the console session of the target server in advance and ensure that no one else connects to your session.
When IBM XL C/C++ Enterprise Edition V8 for AIX Runtime version 8.0.0.3 to 8.0.0.5 is applied, the overwrite installation of the Device Manager agent hangs if either: • the Hitachi Dynamic Link Manager installed is version 5.8 through 5.9 • the Device Manager agent installed is version 5.0 through 5.1.03 When you use the Device Manager agent, upgrade IBM XL C/C++ Enterprise Edition V8 for AIX Runtime to version 8.0.0.6 or later, or apply the APAR IY87291 patch.
• Verify that the file system mounted on the host matches the one defined in /etc/fstab. • Verify that the network settings (such as those in the hosts file) are correct. NOTE: Do not try to install the Device Manager agent on an HP-UX workstation. If you do, the installation fails and the following message appears: ERROR: Could not apply the software selection "HDVMAgent" because there are no product variations that are compatible with the destination host(s).
NOTE: To install the Device Manager agent and automatically configure the appropriate settings for Replication Manager operation, click Install (next to Replication Manager add-on). 4. 5. 6. Enter the required information when prompted. Log out. Log in again to add the agent-commands folder to the PATH environment variable. 7.
Modifying Device Manager agent properties After installing the Device Manager agent, you may have to modify some of its properties. 1. 2. 3. Stop the agent service. Modify the properties for the appropriate environment (see the categories that follow). Start the agent service. Internet Protocol version 6 (IPv6) Set the following properties in the agent server.properties file. • server.http.socket.
4 Removing Command View AE Suite This module describes how to remove Command View AE Suite and its components. Removing Command View AE Suite server You can remove Command View AE Suite when you no longer need to manage storage systems and hosts. Removing Command View AE Suite deletes all property files, database files, log files, and other files as well.
Removing Command View AE Suite from a Linux host Remove Command View AE Suite from Linux hosts using the command line. 1. 2. 3. Log on to Linux as the root user. Navigate to the root directory. Enter the following command: # Command-View-AE-Suite-installation-directory/Uninstall/uninstall.sh 4. Follow the on-screen instructions. When Command View AE Suite is removed, the following message appears: HP P9000 Command View Advanced Edition Suite removal completed successfully.
• When the process for removing the Device Manager agent starts, the Device Manager agent and any add-on modules automatically stop.
The following tasks that run the HiScan command remain after you remove Device Manager agent and must be removed manually: • Any task that runs exeHiScan.bat with a schedule that was changed in the Scheduled Tasks window that opens from the Control Panel (or changed from the Task Scheduler in Administrative Tools). • Any task that runs exeHiScan.bat that is registered on Windows. Removing Device Manager agents from UNIX hosts Remove Device Manager agents from UNIX hosts using the command line. 1. 2.
5 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This guide follows the conventions shown in Table 21 to refer to HP P9000 products.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: Data Retention Utility • Data Retention Utility • XP Data Retention Utility • LUN Security XP Extension This abbreviation is used when it is not necessary to distinguish the following products: External Storage • XP External Storage Software • External Storage XP • External Storage This abbreviation is used when it is not necessary to distinguish the following products: Flex
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: Volume Shredder • Volume Shredder • XP Volume Shredder • P9000 Volume Shredder 60 Support and other resources
A Unattended installation and removal This appendix describes unattended installation and removal operations. Command View AE Suite server unattended installation Command View AE Suite provides an unattended feature so that you do not need to provide responses during installation. You can perform an unattended installation by creating and executing a script file when the conditions on multiple management servers are the same.
Property Name Details Default Value Windows: HINST_DBDIR2 HINST_IPADDRESS3 HINST_DBBACKUP4 For a new installation: Specify the directory for database files. For a new installation: Specify the IP address or host name of the management server.
Property Name Details Default Value Specify whether to continue the installation when there is insufficient unused capacity: HINST_IGNORE_CAPACITY_CHECK • TRUE: Continue the installation FALSE • FALSE: Stop the installation. HINST_IGNORE_NETWORKING_CHECK Specify whether to continue the installation when the host name or IP address that was specified in HINST_IPADDRESS is not communicating with the network. FALSE • TRUE: Continue the installation. • FALSE: Stop the installation.
3. Verify that the execution result file (HInstReport.txt) is closed. The prerequisite checker verifies whether the installation destination satisfies the requirements. To access the prerequisite checker on Windows, use the integrated installation media or run the prereqchk.exe file located in DVD-drive:\HCS\ To access the prerequisite checker in Linux, run the prereqchk.
When the installation completes, the result is written in the HInstReport.txt file in the /tmp directory. If you see SUCCESS in the summary section of the file, the installation was successful. Device Manager agent unattended installation You can automate agent installation by creating and executing a script file. Unattended installation can be used when installing on multiple hosts with the same conditions. By creating a settings file (HDVMAgent.
Property Name Details Default value Specify the HiScan execution interval.
For a complete list of system requirements, see the HP P9000 Command View Advanced Edition Suite Software Release Notes. Installing a Device Manager agent on a Windows host (unattended installation) An unattended installation uses a script file (HDvMAgent.conf) that contains the necessary user input. 1. 2. Log on to the Windows operating system with administrator permissions. Open a command or PowerShell window, and change the directory to the location of the installer program (setup.exe).
If the return value is 0x00, the installation completed successfully. When starting the installer from a DVD-ROM, these characters can be specified in the mount path: A to Z, a to z, 0 to 9, underscores (_), forward slashes (/). Verifying Device Manager agent unattended installations When unattended installation of the Device Manager agent completes, check the returned values. You can verify the returned values listed in Table 24 to determine the result.
Return value (hexadecimal) Description Action Installation failed. Perform the following, depending on the cause of the error: 0x92 HDVMAgent.conf is not stored in the directory in which the installer execution file is stored, or HDVMAgent.conf contains some setting errors. • HDVMAgent.conf is not stored in the directory in which the installer execution file is stored. Store HDVMAgent.conf in the directory in which the installer execution file is stored and execute the installation again. • HDVMAgent.
Device Manager agent unattended removal The unattended removal of an agent eliminates the need for user responses during agent removal. This function is useful when agents are installed on multiple hosts. To perform an unattended agent removal, you create and execute a script file. Removing a Device Manager agent from a Windows host (unattended removal) You can perform an unattended Device Manager agent removal in a Windows environment. 1. 2.
Verifying the Device Manager agent unattended removal When the unattended removal of the Device Manager agent completes, check the returned values and verify them against the following table. Table 25 Device Manager agent unattended removal returned values Return value (hexadecimal) Description Action 0x00 Normal termination -The following are likely causes: • A program other than the Device Manager agent is either being installed or removed.
Unattended installation and removal
B Command View AE Suite ports This appendix describes the ports used for HP StorageWorks P9000 Command View Advanced Edition Suite (Command View AE Suite). For a complete list of system requirements, see the HP P9000 Command View Advanced Edition Suite Software Release Notes. Command View AE Suite server ports Ensure that Command View AE Suite ports do not overlap with those used by other programs on the management server. Some ports can overlap with ports temporarily assigned by the operating system.
Port Number Description If the port is in use by another product 23031/tcp Common Component port when the management server operating system is Windows Change the settings for the product that uses this port or change Common Component settings. Host Data Collector ports Change the settings for the product that uses this port.
Glossary allocated volume An LDEV for which one or more host LUN paths are defined. cache A set of RAM (Random Access Memory) modules used to store data temporarily. capacity The amount of data storage space available on a disk drive or storage system. Measured in MB, but it can also be measured in other units such as TB and PB, depending on the total storage space.
external volume A logical volume whose data resides on drives that are in an externally connected storage system. FC fibre channel FCoE Fibre Channel over Ethernet. An encapsulation of Fibre Channel frames over Ethernet networks. This allows Fibre Channel to use 10-gigabit Ethernet networks (or higher speeds) while preserving the Fibre Channel protocol. GUI graphical user interface HBA host bus adapter host group A means of segregating hosts by operating system.
LU (logical unit) A volume created in an open storage system. See also LDEV. LUN (logical unit number) A management number assigned to an LU in a storage system. A LUN is a number assigned to identify an LU for the port in the storage system to which the LU is connected, either by the port or by the host group assigned to the port. An open system host uses a LUN to access a particular LU.
Technology Attachment) SCSI (Small Computer System Interface) Standards that define I/O buses primarily intended for connecting storage systems and devices to hosts through host bus adapters. secure sockets layer (SSL) A commonly-used protocol for managing the security of a message transmission on the Internet. SLPR Storage Local Partition Smart Tiers (Smart) In addition to Thin Provisioning functionality, this functionality places data on a tier according to the I/O load.
volume A collective name for the logical devices (LDEVs) and logical units (LUs) that are created in a storage system. web client Browser WWN World wide name. A unique identifier used in storage technologies. It is typically a node name that is a 64-bit address assigned to HBAs (host bus adapters) or storage system ports that define the endpoints of a fibre-channel connection between storage and hosts for purposes of volume I/O.
Glossary
Index A agent modifying agent services, 45 modifying properties, 52 registering firewall exceptions, 52 resetting service execution user, 52 agent installation prerequisites, agent removal, agent configuration HiScan execution, 46 RAID Manager, 46 agent installation AIX precautions, 48 HP-UX prerequisites, 49 Linux prerequisites, 49 prerequisites, 43, 45 - 47 server information, 45 Stack Execution Disable function, 48 unattended, 65, 67 - 68 unattended Windows, 67 UNIX, 51 Windows, 50 agent removal prerequi
K kernel parameters, 21 Linux, 21 Red Hat Enterprise Linux, 22 SUSE Linux Enterprise Server, 27 L Linux kernel parameters, 21 server installation, 32 server installation prerequisites, 15 shell restrictions, 21 Linux prerequisites agent installation, 49 firewall changes, 49 Linux unattended installation server, 64 M management client, 11 management server, 12 installation information, 18 memory heap size server installation, 18 P password changing, 33 port number validation server installation, 21 R RAI
S server installation, 32 assigning resource groups, 36, 41 changing kernel parameter values, 30 changing shell restriction values, 30 creating user, 33 database backup, 20 database destination, 17 destination, 16 Device Manager roles, 34 Linux, 32 management server, 18 memory heap size, 18 port number validation, 21 prerequisites, 15, 31 refreshing storage systems, 37 registering licenses, 33 Replication Manager Software operation permissions, 34 resetting user account, 38 system account password, 33 tasks
W Windows additional installation files, 13 agent execution user, 52 agent firewall exceptions, 52 agent installation, 50 agent installation prerequisites, 43, 47 remote access, 47 server installation, 31 server installation prerequisites, 15 Windows (IPF) server installation prerequisites, 15 Windows (x64) server installation prerequisites, 15 Windows (x86) server installation prerequisites, 15 Windows Remote Desktop functionality, 47 Windows unattended installation agent, 67 server, 64 Windows unattended
