Performance Center Desktop Client Supported Environments. See. Virtual Environments. HP ALM Performance Center is certified to work with VMWare ESXESXi 5. HP Application Lifecycle Management Readme. HP Application Lifecycle Management Readme. Software Version 1. Document Release Date May 2. Managing shared mailboxes in Office 365 with PowerShell Thu, May 5 2016 Managing shared mailboxes in Office 365 with the GUI Wed, May 4 2016. Step by step guide to installing an Exchange Server 2013 Database Availability Group. Release Notes for Veeam Backup Replication 9. Update 2. Book Title. Cisco Prime Infrastructure 2. Administrator Guide. Chapter Title. Maintaining Prime Infrastructure Server Health. PDF Complete Book. AD FS 3. 0 has the capability to allow the user to change their password when they supply their existing password. To enable this, open the AD FS management console. Note To download the converter, see Microsoft Virtual Machine Converter 3. Microsoft Download Center. From this page, you also can download. Software Release Date May 2. This file provides the following information about ALM 1. You can view the most recent ALM help on the Web at ALM Help Center. For details on ALM add ins and extensions, see ALM Add ins and Extensions. Whats New. For a list of new enhancements in ALM, see Whats New in ALM 1. Installation Instructions. ALM Installation. If you are installing ALM1. ALM, follow the full installation instructions as described in the HP Application Lifecycle Management Installation and Upgrade Guide. If you are upgrading to ALM1. ALM and follow the full installation instructions as described in the HP Application Lifecycle Management Installation and Upgrade Guide. Performance Center Installation. If you are installing Performance Center. HP ALMPerformance Center Installation Guide. As a prerequisite to installing Performance Center 1. ALM 1. 2. 5. 3. System Requirements. The following section describes the system requirements for installing ALM and Performance Center. For the most up to date system requirements and supported environments information, see https hpln. Note HP ALM 1. 2. HP Quality Center Enterprise 1. FDCC regulations. This section includes ALM Server Side System Requirements. This section includes the server side system requirements and configurations for installing ALM on Windows and Linux. ALM Server Side Hardware Requirements. The following table lists the minimum hardware requirements for installing ALM on a server machine CPUWindows Quad Core AMD6. Linux Quad Core AMD6. Memory RAM8 GBFree disk space. GBRecommended ALM Server Side Environments. The following table lists the recommended configurations for each operating system Operating System. Database Server. Web Server. Microsoft Windows Server 2. R2. Microsoft SQL Server 2. Microsoft IIS 8. 5. Red Hat Enterprise Linux 6. Oracle 1. 2cHowever, to ensure best performance and quick support resolutions, use one of the Recommended ALM Server Side Environments. Operating System. Microsoft Windows Server 2. R2. Microsoft Windows Server 2. Microsoft Windows Server 2. R2. Red Hat Enterprise Linux 6. Bit. Red Hat Enterprise Linux 7. Bit. Oracle Linux 6. Bit. Oracle Linux 7. Bit. SUSE Linux Enterprise Server 1. SP3 6. 4 bit. SUSE Linux Enterprise Server 1. SP4 6. 4 bit. SUSE Linux Enterprise Server 1. Note  Localized editions of are supported only on Windows operating systems. Operating system service packs and updates are supported, provided they are compatible with the vendors general availability release. Oracle Linux versions are supported, provided they are compatible with the supported versions of Red Hat Linux. Database Server. Oracle 1. Microsoft SQL Server 2. Microsoft SQL Server 2. Note  All database servers, unless otherwise stated, have been validated on 6. ALM is certified to work with Enterprise and Standard editions of Microsoft and Oracle databases. Database server service packs and updates are supported, provided they are compatible with the vendors general availability release. ALM is certified to work with Transparent Data Encryption TDE for Microsoft and Oracle databases. Implementation of TDE does have an impact on system performance. For details, contact the database vendor that provides the encryption. Application Server. The Application server functionality is built in to the ALM platform and there is no need to install a third party application server Web. Logic, Web. Sphere, and JBoss from version 1. The HP ALM application server uses JDK7 1. JVM. Web Server. Apache 2. Microsoft IIS 7. 5. Microsoft IIS 8. 0. Microsoft IIS 8. 5. Note  By default, application servers include HTTP servers. If you need additional functionality a web server can be added. HP will certify the major and minor releases of Apache e. Apache 2. 2, while all minor minor releases of Apache e. Apache will maintain full compatibility. Virtual Environment. VMWare ESXESXi Server 5. Note HP ALMQC is certified to work with VMWare ESXESXi. Due to the rapidly evolving architectures provided by virtualization vendors e. Hyper V or Citrix as long as the above stated vendor guarantees full compatibility of the virtualized environment to the HP ALMQC approved system requirements for physical hardware, HP ALMQC will support the virtualized environments and function as designed. Full Disk Encryption. Full disk encryption FDE is supported for all system components, including database, server, repository server, and client machines. Implementation of FDE, does have an impact on system performance. For details, contact the vendor that provides the encryption. ALM Client System Requirements. The following are the client side system requirements and configurations for installing ALM on client machines. CPUCore duo 1. 6 GHz or faster or equivalent compatible processor. Memory RAM2 GBFree disk space. GBRecommended ALM Client Environments. The following table lists the recommended client configuration Operating System. Browser. Office Suite. Microsoft Windows 8. Microsoft Internet Explorer 1. Microsoft Office 2. Windows 7 Patch By Time here. ALM Desktop Client Supported Environments. The following table lists all supported Desktop client configurations. However, to ensure best performance and quick support resolutions, use one of the Recommended ALM Client Environments. Prerequisites. Microsoft. NET Framework 4. 0 Microsoft. NET Framework 4. 5. Microsoft Office 2. Microsoft Office 2. Operating Systems. Microsoft Windows 7 SP1 Microsoft Windows 8. CDATA. Microsoft Windows 1. Microsoft Windows Server 2. R2. Microsoft Windows Server 2. Microsoft Windows Server 2. R2. Note  If you are integrating Quality Center with other HP testing tools, you must modify the DCOM permissions on your client machine. DCOM is not required for running functional test sets server side execution. Functional test sets are available only in ALM Edition. ALMQC Client on Windows 6. WOW6. 4 mode. Browsers. Microsoft Internet Explorer 1. Microsoft Internet Explorer 1. Note For customers who have restrictions on plug ins in their browsers, such as Active. X, ALM can be loaded in the HP ALM Explorer Add in. For more information on downloading and installing the Add in, see the HP Application Lifecycle Management Installation and Upgrade Guide. Office Suites. Microsoft Office 2. Microsoft Office 2. Excel add in only. Microsoft Office 2. Microsoft Office 2. Excel add in only. Microsoft Office 2. Bit. Microsoft Office 2. Bit Excel add in only. Microsoft Office 3. Virtual Environments. Citrix Xen. App 6. Microsoft Terminal Services. Remote Desktop Services. Note HP ALM is certified to work with Citrix Xen. App, Microsoft Terminal Services and Remote Desktop Services. Due to the rapidly evolving architectures provided by Virtualization vendors as long as the above stated vendor guarantees full compatibility of the virtualized environment to the HP ALM approved system requirements for physical hardware, then HP ALM will function as designed. Other Configuration Settings. Screen Resolution 1. DPI Setting 1. 00ALM Lab Service for Remote Test Execution System Requirements. The following table lists the system requirements for installing ALM Lab Service for remote test execution Processor. GHz or faster. Memory RAMMinimum  1 GBCisco Prime Infrastructure 2. Administrator Guide Maintaining Prime Infrastructure Server Health Cisco Prime InfrastructureImproving Prime Infrastructure Performance. You can improve Prime Infrastructures speed and scalability using several techniques. Tuning the Server. You can improve Prime Infrastructures performance and scalability by increasing the amount of RAM, CPU, and disk space allocated to the Prime Infrastructure server and its virtual machine or VM. Successful server tuning requires you to complete the following workflow 1. Changes to the VM include a risk of failure. Take an application backup before making any changes to the VM. See Triggering Application Backups. Although it is enabled by default, you should ensure that the Server Tuning option is enabled before making changes to the VM. See Enabling Server Tuning During Restarts. Perform the resource modifications in the VM, then restart the VM and the server. See Modifying VM Resource Allocation Using VMware v. Sphere Client. Enabling Server Tuning During Restarts. During system start, the Prime Infrastructure server inspects its VM hardware allocations for changes and will adjust to make use of expanded resources automatically. The Enable Server Tuning during restart option is enabled by default and you will not want to change this setting under normal circumstances. If you find that the Prime Infrastructure server is not taking advantage of recent changes to its hardware, such as a larger RAM or disk space allocation, follow the steps below to ensure the tuning feature is enabled, Step 1 Choose Administration System Settings. Step 2 From the left sidebar menu, choose Server Tuning. Step 3 Select the Enable Server Tuning during restart check box, then click Save. Modifying VM Resource Allocation Using VMware v. Sphere Client. Use the following steps to make changes to the physical or virtual appliance RAM, CPU or disk space resource allocations. Be sure to back up the Prime Infrastructure server before attempting these types of changes see Backing Up and Restoring Prime Infrastructure. Tip For better performance If you are changing RAM and CPU resource allocations for the virtual machine on which you run Prime Infrastructure, and you have more than one virtual machine running on the same hardware, you may also want to change your RAM and CPU resource reservations using the v. Sphere Clients Resource Allocation tab. For details, see the VMware v. Sphere Client documentation. Step 1 Open a CLI session with the Prime Infrastructure server see Connecting Via CLI. Step 2 Stop Prime Infrastructure using the ncs stop command see Stopping Prime Infrastructure. Step 3 Halt the VMware virtual appliance PIServeradmin halt. Step 4 Launch the v. Sphere Client, right click the virtual appliance, then click Edit Settings. Step 5 To change the RAM allocation, select Memory and change the Memory Size as needed. Then click OK. Step 6 To change the CPU allocation, select CPUs and select the Number of Virtual Processors from the drop down list. Then click OK. Step 7 To add a new disk you cannot expand the space of the existing disk a. Click Add. b. Select Hard Disk, then click Next. Check Create a new virtual disk, then click Next. Enter the desired Disk Size and specify a Location for the new virtual disk, then click Next. With the Advanced Options displayed, click Next, then click Finish. Step 8 Power on the virtual appliance see Restarting Prime Infrastructure. Compacting the Prime Infrastructure Database. You can reclaim disk space by compacting the Prime Infrastructure database. Step 1 Open a CLI session with the Prime Infrastructure server see Connecting Via CLI. Step 2 Enter the following command to compact the application database PIServeradmin ncs cleanup. Step 3 When prompted, answer Yes to the deep cleanup option. Configuring Client Performance Settings. You can configure the following client processes to improve Prime Infrastructure performance and scalability Enabling Automatic Client Troubleshooting. The Administration System Settings Client page allows you to enable automatic client troubleshooting on a diagnostic channel for your third party wireless clients running Cisco Compatible Extensions CCX. With this feature enabled, Prime Infrastructure will process the client ccx test association trap that invokes a series of tests on each CCX client. Clients are updated on all completed tasks, and an automated troubleshooting report is produced it is located in distacswinwebnmslogs. When each test is complete, the location of the test log is updated in the client details pages, in the V5 or V6 tab, in the Automated Troubleshooting Report area. Click Export to export the logs. When this feature is not enabled, Prime Infrastructure still raises the trap, but automated troubleshooting is not initiated. Note. Automatic client troubleshooting is only available for clients running CCX Version 5 or 6. For a list of CCX certified partner manufacturers and their CCX client devices, see the Cisco Compatible Extensions Client Devices page. Step 1 Choose Administration System Settings. Step 2 From the left sidebar menu, choose Client. The Client page appears. Step 3 In the Process Diagnostic Trap area, select the Automatically troubleshoot client on diagnostic channel check box, then click Save. Enabling DNS Hostname Lookup. DNS lookup can take a considerable amount of time, so Prime Infrastructure has it disabled by default. You can enable or disable the DNS lookup for client hostnames, and change how long Prime Infrastructure retains the results of previous DNS lookups in its cache. Step 1 Choose Administration System Settings. Step 2 From the left sidebar menu, choose Client. Step 3 Select the Lookup client host names from DNS server check box. Step 4 Enter the number of days that you want the hostname to remain in the cache, then click Save. Specifying How Long to Retain Client Association History Data. Client association history can take a lot of database and disk space. This can be an issue for database backup and restore functions. The retention duration of client association history can be configured to help manage this potential issue. Step 1 Choose Administration System Settings Client. Step 2 Change the following data retention parameters as needed Dissociated Clients Enter the number of days that you want Prime Infrastructure to retain the data. The valid range is 1 to 3. Client session history Enter the number of days that you want Prime Infrastructure to retain the data. The valid range is 7 to 3. Step 3 Click Save. Polling Clients When Receiving Client TrapsSyslogs. Under normal circumstances, Prime Infrastructure polls clients on a regular schedule, every few minutes, identifying session information during the poll. You can also choose to have Prime Infrastructure poll clients immediately whenever traps and syslogs are received from them. This helps you discover new clients and their sessions quickly. This option is disabled by default, as it can affect Prime Infrastructure performance. Busy networks with many clients can generate large amounts of trapssyslogs, especially during peak periods when clients are roaming and associatingdisassociating often. In this case, polling clients at the same time can be a processing burden. Step 1 Choose Administration System Settings Client. Step 2 Select the Poll clients when client trapssyslogs received check box.