Aperto Installation Manager 6.0

Posted on  by

  1. Aperto Installation Manager 6.0 Crack
  2. Aperto Installation Manager 6.0 Key
  3. Aperto Installation Manager 6.0 Download
  4. Aperto Installation Manager 6.0 Free

Go to start of metadata. Installing WSO2 is very fast and easy. Before you begin, be sure you have met the installation prerequisites, and then follow the installation instructions for your platform. For information, contact team WSO2. Installing via the Installer. Keysight License Manager 6 Download. Keysight License Manager 6 download bundles a set of free software license management tools and documentation that enables you to easily manage licenses for your Keysight software products. This bundle includes: Keysight License Server (agileesofd.exe) Keysight Licensing Administrator's Guide. Standalone Installation Wizard for Communication Manager 6.0.1. This standalone version of the CM 6.0 / CM 6.0.1 Installation Wizard runs on Windows XP and allows an Electronic Pre-installation Worksheet (EPW file) to be created off-line prior to installing a Communication Manager 6.0 / 6.0.1 template. 1928478 Release Restrictions Note – SAP Work Manager 6.0. 1936034 SAP Work Manager 6.0 ABAP AddOn Installation Master Note. 1828657 Release strategy for the ABAP add-ons SMFND, SMERP, SMISU, and SMCRM. 2048221 – Quick Start Guide to install SAP Work Manager 6.0 with SMP 2.3 (Agentry).

After you issue the agentadmin command and acceptthe license agreement (if necessary) the installation program appears, promptingyou for information.

The steps in the installation program are displayed in this sectionin an example interaction. Your answers to prompts can differ slightly orgreatly from this example depending upon your specific deployment. In theexample, most of the defaults have been accepted. This example is providedfor your reference and does not necessarily indicate the precise informationyou should enter.

Aperto Installation Manager 6.0

The following bulleted list provides key points about the installationprogram.

  • Each step in the installation program includes an explanationthat is followed by a more succinct prompt.

  • For most of the steps you can type any of the following charactersto get the results described:

    ?

    Type the question mark to display Help information for thatspecific step.

    <

    Type the left arrow symbol to go back to the previous interaction.

    !

    Type the exclamation point to exit the program.

  • Most of the steps provide a default value that can be acceptedor replaced. If a default value is correct for your site, accept it. If itis not correct, enter the correct value.

About Installation Prompts in Agent for Apache Tomcat 6.0

The following list provides information about specific prompts in theinstallation. Often the prompt is self explanatory. However, at other timesyou might find the extra information presented here to be very helpful. Thisextra information is often not obvious. Study this section carefully beforeissuing the agentadmin --install command.

The Deployment URI for the Agent Application

The deployment URI for the agent application is required forthe agent to perform necessary housekeeping tasks such as registering policyand session notifications, legacy browser support, and CDSSO support. Accept /agentapp as the default value for this interaction. Once the installationis completed, browse the directory PolicyAgent-base/etc. Use the agentapp.war file to deploy theagent application in the application container. Please note that the deploymentURI for agent application during install time should match the deploymentURI for the same application when deployed in the J2EE container.

The Encryption Key

This key is used to encrypt sensitive information such thepasswords. The key should be at least 12 characters long. A key is generatedrandomly and provided as the default. You can accept the random key generatedby the installer or create your own using the .agentadmin --getEncryptKey command.

For information about creating a new encryption key, see agentadmin --getEncryptKey.

The Agent Profile Name

An agent profile should have been created as a pre-installationstep. The creation of the agent profile is mentioned in that section. Forthe pre-installation steps, see Preparing to Install Agent for Apache Tomcat 6.0. For the actual information on creatingan agent profile, see Creating a J2EE Agent Profile.

In summary, the J2EE agent communicates with Access Manager with a specificID and password created through an agent profile using Access Manager Console.For J2EE agents, the creation of an agent profile is mandatory. Access Manager usesthe agent profile to authenticate an agent. This is part of the security infrastructure.

The J2EE Password File

The J2EE password file should have been created as a pre-installationstep. For the pre-installation steps, see Preparing to Install Agent for Apache Tomcat 6.0.

When the installation program prompts you for the password for the agent,enter the fully qualified path to this password file.

After you have completed all the steps, a summary of your responsesappears followed by options that allow you to navigate through those responsesto accept or reject them.

When the summary appears, note the agent instance name, such as agent-001. You might be prompted for this name during the configuration process.

About the options, the default option is 1, Continue with Installation.

  • If you are satisfied with the summary, choose 1 (the default).

  • If you want to edit input from the last interaction, choose2.

  • If you want to edit input starting at the beginning of theinstallation program, choose 3.

  • If you want to exit the installation program without installing,choose 4.

You can edit your responses as necessary, return to the options list,and choose option 1 to finally process your responses.

Example of Installation Program Interaction in Agentfor Apache Tomcat 6.0

The following example is a sample installation snapshot of Policy Agent 2.2 for Apache Tomcat 6.0.By no means does this sample represent a real deployment scenario.

The section following this example, Implications of Specific Deployment Scenarios in Agent for Apache Tomcat 6.0, providesa short explanation about installing a J2EE agent on multiple Apache Tomcat 6.0 instances.If your deployment includes multiple instances of the deployment container,you might want to review that section before proceeding with the agent installation.See Installing a J2EE Agent on Multiple Apache Tomcat 6.0 Instances.


Implications of Specific Deployment Scenarios inAgent for Apache Tomcat 6.0

The following section refers to a specific deployment scenario involving Policy Agent 2.2 for Apache Tomcat 6.0.

Installing a J2EE Agent on Multiple Apache Tomcat 6.0 Instances

Once a J2EE agent is installed for a particular Apache Tomcat 6.0 instance,you can install the agent on another instance on the same machine by runningthe agentadmin --install command. Onceprompted to enter the appropriate server instance name, enter the server configurationdirectory and unique instance name that will enable the agent to distinguishthe first instance from consecutive instances.

Summary of a J2EE Agent Installation in Policy Agent 2.2

At the end of the installation process, the installation program printsthe status of the installation along with the installed J2EE agent information.The information that the program displays can be very useful. For example,the program displays the agent instance name, which is needed when configuringa remote instance. The program also displays the location of specific files,which can be of great importance. In fact, you might want to view the installationlog file once the installation is complete, before performing the post-installationsteps as described in Chapter 4, Post-Installation Tasks of Policy Agent 2.2 for Apache Tomcat 6.0.

The location of directories displayed by the installer are specific.However, throughout this guide and specifically in Summary of Agent Installationshown in this section, PolicyAgent-base is usedto describe the directory where the distribution files are stored for a specificJ2EE agent.

The following example serves as a quick description of the locationof the J2EE agent base directory (PolicyAgent-base)of Policy Agent 2.2 for Apache Tomcat 6.0.

Aperto Installation Manager 6.0 Crack

Aperto installation manager 6.0 key
Example 3–1 Policy Agent Base Directory of Agent for Apache Tomcat 6.0

The following directory represents PolicyAgent-base ofAgent for Apache Tomcat 6.0:


Aperto

where Agent-HomeDirectory is the directoryyou choose in which to unpack the J2EE agent binaries.

Information regarding the location of the J2EE agent base directoryis explained in detail in Location of the J2EE Agent Base Directory in Policy Agent 2.2.

The following type of information is printed by the installer:


Once the agent is installed, the directories shown in the precedingexample are created in the agent_00x directory, whichfor this example is specifically Agent_001. Those directoriesand files are briefly described in the following paragraphs.

PolicyAgent-base/Agent_001/config/AMAgent.properties

Location of the J2EE agent AMAgent.properties configurationfile for the agent instance. Every instance of a J2EE agent has a unique copyof this file. You can configure this file to meet your site's requirements.For more information, see the following sections:

PolicyAgent-base/Agent_001/logs/audit

Location of the J2EE agent local audit trail.

PolicyAgent-base/Agent_001/logs/debug

Location of all debug files required to debug an agent installationor configuration issue.

PolicyAgent-base/logs/audit/install.log

Aperto Installation Manager 6.0 Key

Aperto installation manager 6.0 download

Aperto Installation Manager 6.0 Download

Location of the file that has the agent install file location.If the installation failed for any reason, you can look at this file to diagnosethe issue.

Aperto Installation Manager 6.0 Free


vSphere Update Manager | 12 MARCH 2015 | Build 2503190

Last Document Update: 12 MARCH 2015

Check frequently for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

The Update Manager release notes provide information about VMware vSphere Update Manager, an optional module for VMware vCenter Server. For more information about VMware vSphere Update Manager, see the Installing and Administering VMware vSphere Update Manager documentation.


What's New

  • Support of new embedded database: Update Manager 6.0 and the UMDS 6.0 can be configured to use the new embedded database Microsoft SQL Server 2012.
    In Update Manager 6.0 release, to install the embedded database, you must select the option to use Microsoft SQL Server 2012 database before starting the Update Manager server or the UMDS installation wizard.
  • Additional database support: The Update Manager 6.0 server and the UMDS 6.0 are compatible with Oracle Database 12c.

Hardware Requirements and Sizing Estimator

Minimum hardware requirements for Update Manager vary depending on how Update Manager is deployed.

Hardware Requirements

If the database is installed on the same machine as Update Manager, requirements for memory size and processor speed are higher. The minimum requirements to ensure acceptable performance are as follows:

  • Processor: Intel or AMD x86 processor with two or more logical cores, each with a speed of 2GHz.
  • Network: 10/100 Mbps
    For best performance, use a Gigabit connection between Update Manager and ESXi hosts.
  • Memory:
    • 2GB RAM if Update Manager and the vCenter Server are on different machines.
    • 8GB RAM if Update Manager and the vCenter Server are on the same machine.

Sizing Estimator

For more information about the disk storage requirements, see the VMware vSphere Update Manager Sizing Estimator. The sizing estimator calculates the size of the Update Manager database and patch store. The estimate is calculated from the information that you enter about your deployment, such as the number of the hosts and virtual machines. The sizing estimator also provides recommendations for the Update Manager database and server deployment models.


Installation Notes

This section includes information about the installation of Update Manager and Update Manager Download Service, an optional module of vSphere Update Manager.

Update Manager

Installation of VMware vSphere Update Manager requires network connectivity with an existing vCenter Server system. Each installation of vSphere Update Manager must be associated with a single vCenter Server instance.

The Update Manager module consists of a server component and client component. The Update Manager server can be installed on the same system as vCenter Server or on a different system.
The Update Manager provides two client components:

  • Update Manager Client, which is a plug-in interface to a VMware vSphere Client instance.
  • Update Manager Web Client, which is a plug-in interface to a VMware vSphere Web Client instance.

Before you install Update Manager, you must install vCenter Server. For database compatibility information, see Databases that Support Installation of the Update Manager Server.

The Update Manager 6.0 server can be installed only on 64-bit Windows operating systems.

Update Manager Web Client

Update Manager Web Client is a plug-in to the vSphere Web Client. You can use Update Manager Web Client for viewing scan results and compliance states for vSphere inventory objects.

After you install the Update Manager server component, the Update Manager Web Client plug-in is automatically enabled on vSphere Web Client. The Update Manager Web Client plug-in appears as an Update Manager tab under the Monitor tab in the vSphere Web Client.
To be able to see the Update Manager Web Client in vSphere Web Client you must have the View Compliance Status privilege.

You cannot upgrade UMDS 5.x to UMDS 6.0. You can perform a fresh installation of UMDS 6.0 according to all system requirements for UMDS 6.0, and use an existing patch store from UMDS 5.x.

Update Manager Client

Update Manager Client is a plug-in interface to the VMware vSphere Client instance. The Update Manager Client provides you with the full set of capabilities you need to perform patch and version management for your vSphere inventory.

The Update Manager Client has a separate installer from the Update Manager server component.

The Update Manager 6.0 Client can be installed on both 32-bit and 64-bit operating systems.

Update Manager Download Service

vSphere Update Manager Download Service (UMDS) is an optional module of Update Manager that you can use to download patch definitions. Install UMDS in case your deployment system is secured and the machine on which Update Manager is installed has no access to the Internet.

UMDS can be installed only on 64-bit Windows operating systems.

You must not install the UMDS on the same machine where the Update Manager server is installed.

To use UMDS, the download service must be of a version that is compatible with the Update Manager server. For more information about the compatibility between Update Manager and the UMDS, see the Installing and Administering VMware vSphere Update Manager documentation

Installing UMDS 6.0 in an Environment with Update Manager 6.0 Instances Only

In the UMDS 6.0 installation wizard, you can select the patch store to be an existing download directory from an earlier UMDS 5.x installation and reuse the applicable downloaded updates in UMDS 6.0. You should uninstall existing UMDS 5.x instances before reusing the patch store. After you associate an existing download directory with UMDS 6.0, you cannot use it with earlier UMDS versions.
If you install UMDS and associate it with an existing download directory, make sure that you perform at least one download by using UMDS 6.0 before you export updates.

Installing UMDS 6.0 in an Environment with both Update Manager 5.x and Update Manager 6.0 Instances

Do not install and associate UMDS 6.0 with an existing UMDS 5.x download directory if your environment contains both Update Manager 5.x and Update Manager 6.0 instances. In such a case, you need a UMDS 5.x and a UMDS 6.0 installation on two separate machines, so that you can export updates for each respective Update Manager versions.

Update Manager Utility

When you install Update Manager or UMDS, vSphere Update Manager Utility is silently installed on your system as an additional component.

The Update Manager Utility allows you to change the database password and proxy authentication, re-register Update Manager with vCenter Server, and replace the SSL certificates for Update Manager. For more information about reconfiguring the Update Manager settings by using the utility, see the Reconfiguring VMware vSphere Update Manager documentation.


Upgrade Notes

This release allows upgrades from Update Manager versions 5.x and their respective update releases that are installed on a 64-bit operating system. Direct upgrades from Update Manager 4.x and earlier, and Update Manager systems that are installed on a 32-bit platform are not supported. You must use the data migration tool that is provided with Update Manager 5.0 installation media to move your Update Manager system from 32-bit operating system to Update Manager 5.0 on a 64-bit operating system, and then perform an in-place upgrade from version 5.0 to version 6.0. For detailed information how to use the data migration tool, see the Installing and Administering VMware vSphere Update Manager documentation for Update Manager 5.0.

Before you upgrade Update Manager, you must upgrade vCenter Server and the vSphere Client to a compatible version.

Upgrade from UMDS 5.x to UMDS 6.0 is not supported.


Interoperability and Software Requirements

The VMware Product Interoperability Matrix provides details about the compatibility of current and previous versions of vSphere Update Manager with other VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Client, and the vSphere Web Client. In addition, check this site for information about supported management and backup agents before installing ESXi or vCenter Server.

Operating Systems that Support Installation of the Update Manager Server and UMDS

To see a list of operating systems on which you can install the Update Manager server and the UMDS, see Supported host operating systems for VMware vCenter Server installation. The supported host operating systems for vCenter Server installation listed in the article also apply for installation of the respective versions of the Update Manager server and the UMDS.

Databases that Support Installation of the Update Manager Server and UMDS

The Solution/Database Interoperability option from the VMware Product Interoperability Matrix provides information about the databases that are compatible with Update Manager server and UMDS.

Operations with vSphere Inventory Objects that Update Manager supports

  • Host patching of the following host version:
    • ESXi 5.x
    • ESXi 6.0
  • Host upgrades of ESXi 5.x and their respective update releases to ESXi 6.0
  • Upgrades of VMware Tools and virtual hardware for virtual machines
  • Upgrades of virtual appliances

Supported Operating Systems for Upgrade of VMware Tools and Virtual Hardware

  • Windows Server 2012 [Standard/Datacenter] 64-bit
  • Windows Server 2012 R2 [Standard/Enterprise/Datacenter] 64-bit
  • Windows Server 2012 R2 Update 1 [Standard/Enterprise/Datacenter] 64-bit
  • Windows 8.1 Update 1 [Professional/Enterprise] 32-bit
  • Windows 8.1 Update 1 [Professional/Enterprise] 64-bit
  • Windows 8.1 [Professional/Enterprise] 32-bit
  • Windows 8.1 [Professional/Enterprise] 64-bit
  • Windows 8 [Professional/Enterprise] 32-bit
  • Windows 8 [Professional/Enterprise] 64-bit
  • Windows 7 [Professional/Enterprise] 32-bit
  • Windows 7 [Professional/Enterprise] 64-bit
  • Windows 7 [Professional/Enterprise] 32-bit SP1
  • Windows 7 [Professional/Enterprise] 64-bit SP1
  • Windows XP Professional 32-bit (SP3 required)
  • Windows XP Professional 64-bit (SP2 required)
  • Windows 2000 [Professional/Server/Advanced Server/Datacenter Server] 32-bit
  • Windows 2000 [Professional/Server/Advanced Server/Datacenter Server] 64-bit
  • Windows Server 2003 [Standard/Enterprise/Datacenter] 32-bit (SP2 required)
  • Windows Server 2003 [Standard/Enterprise/Datacenter] 64-bit (SP2 required)
  • Windows Server 2003 R2 [Standard/Enterprise/Datacenter] 32-bit (SP2 required)
  • Windows Server 2003 R2 [Standard/Enterprise/Datacenter] 64-bit (SP2 required)
  • Windows Vista [Business/Enterprise] 32-bit (SP2 required)
  • Windows Vista [Business/Enterprise] 64-bit (SP2 required)
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 32-bit
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 32-bit SP2
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit SP2
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit R2
  • Windows Server 2008 [Standard/Enterprise/Datacenter] 64-bit R2 Service Pack 1
  • Red Hat Enterprise Linux 2
  • Red Hat Enterprise Linux 3
  • Red Hat Enterprise Linux 4
  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 5.10
  • Red Hat Enterprise Linux 6.5
  • Red Hat Enterprise Linux 7.0
  • CentOS 4
  • CentOS 5
  • CentOS 5.10
  • CentOS 6
  • CentOS 6.5
  • Debian 4
  • Debian 5
  • Debian 6
  • Ubuntu 7.x
  • Ubuntu 8.x
  • Ubuntu 9.x
  • Ubuntu 10.x
  • Ubuntu 11.x
  • Ubuntu 13.10
  • Ubuntu 14.04
  • SUSE Linux Enterprise Server 8
  • SUSE Linux Enterprise Server 9
  • SUSE Linux Enterprise Server 11 Service Pack 3
  • SUSE Linux Enterprise Server 12
  • Oracle Enterprise Linux 4
  • Oracle Enterprise Linux 5
  • Oracle Enterprise Linux 5.1
  • Oracle Enterprise Linux 6
  • Oracle Enterprise Linux 6.5
  • Oracle Enterprise Linux 7.0
  • Asianux 3
  • Asianux 4

Resolved Issues


Known Issues

The known issues in this Update Manager release are grouped as follows:


Installing and Upgrading

  • Installing Update Manager with the embedded Microsoft SQL 2012 database fails on systems with Microsoft .NET Framework 4
    Attempts to install Update Manager with the embedded Microsoft SQL 2012 database fail if the host machine uses Microsoft .NET Framework 4. The following error message appears:

    SQL installation was not successful

    Workaround: To work around this issue perform the following steps:

    1. On the machine you attempt to install Update Manager, shut down and disable all services that require using Microsoft .NET Framework 4.
    2. Uninstall all Microsoft .NET Framework 4 components.
    3. Open a command prompt window and change to C:WindowsMicrosoft.NETFrameworkv2.0.50727
    4. Run the following commands to create security.config and security.config.cch files in the configuration folder:
      Caspol.exe -all -reset
    5. Change the path to C:WindowsMicrosoft.NETFramework64v2.0.50727
    6. Run the following commands to create security.config and security.config.cch files in the configuration folder:
      Caspol.exe -all -reset
    7. Download and install all Microsoft .NET Framework 4 components again.
    8. After installation completes, enable all services that require using Microsoft .NET Framework 4.
    9. Restart the operating system and attempt again to install Update Manager with the Embedded Microsoft SQL 2012 Database.
  • Update Manager Client fails to start on Windows system with non-English locales if during installation of the Update Manager server you configured DSN with non-ASCII characters
    When you install the Update Manager server on a Windows system with non-English locale, if you select the option to use an existing supported database and use non-ASCII characters in the DSN name, installation completes successfully. Then you install the Update Manager Client. When you attempt to start the Update Manager Client, the client fails to initiate and the following error is displayed:
    There was an error connecting to VMware vSphere Update Manager. Database temporarily unavailable or has network problems. Having non-ASCII characters in the DSN causes the Update Manager Client start to fail.
    Workaround: Do not use non-ASCII characters while installing the Update Manager server.
  • Update Manager installer stops responding if you already have Microsoft SQL 2008 R2 SP2 database on your system
    In case on the system where you are installing the Update Manager server or the UMDS exists an instance of the Microsoft SQL 2008 R2 SP2 database but there is no VIM_SQLEXP instance, when you attempt to install the Update Manager server or the UMDS if you select the option to install the bundled with the installer database, the installer stops responding.
    Workaround: To workaround this issue, perform the following steps:
    1. On the machine you are installing the Update Manager server or the UMDS, open a command line interface and type the following command:
      .redistSQLEXPRSQLEXPR_x64_ENU.exe /ACTION=install /IACCEPTSQLSERVERLICENSETERMS /SQLSVCACCOUNT='NT AUTHORITYSYSTEM' /HIDECONSOLE /FEATURES=SQL /SQLSYSADMINACCOUNTS='BUILTINADMINISTRATORS' /NPENABLED='1' /TCPENABLED='1' /INSTANCENAME=VIM_SQLEXP
    2. Atempt to install the Update Manager server or the UMDS again.
  • Update Manager Web Client is still present in the vSphere Web Client after Update Manager is uninstalled
    When you uninstall Update Manager, the Update Manager tab remains under the Monitor tab in the vSphere Web Client, and the Scan and Attach buttons are still active. If you select the Update Manager tab in vSphere Web Client after uninstalling the Update Manager server, the following error message appears: There was an error connecting to VMware vSphere Update Manager.
    Workaround: Log out and log in to the vSphere Web Client.
  • Attempts to install the Update Manager server and UMDS with the bundled database fail on Windows operating system with Turkish language pack
    On Windows operating systems with Turkish language pack, attempts to install the Update Manager server and UMDS with the bundled database fail with the following error:
    Error 25003. Setup failed to create database tables.
    Workaround: To work around the issue, perform one of the following tasks:
    • Install the Update Manager server and UMDS on a Windows operating system with English language pack.
    • Install the Update Manager server and UMDS on a Windows operating system with Turkish language pack and use one of the following databases:
      • Microsoft SQL Server 2012 64-bit
      • Microsoft SQL Server 2008 R2 64-bit
      • Oracle 11g R2 64-bit
  • After an upgrade, the Update Manager plug-in might be disabled for the duration of a download task
    If Update Manager loses connection to vCenter Server while a download task is running, the Update Manager plug-in cannot be re-enabled. This problem might occur after an upgrade of Update Manager.
    Workaround: Wait for the download task to complete, and then enable the Update Manager plug-in.
  • You might not be able to enable the Update Manager plug-in on the vSphere Client
    If the Update Manager database is located on a separate machine and the system DSN uses Windows authentication, you cannot enable the Update Manager plug-in on the vSphere Client. The error message you receive is There was an error connecting to VMware vSphere Update Manager. Database temporarily unavailable or has network problems.
    Workaround: Ensure that the Update Manager database uses SQL Server authentication.
  • A minimum of 600MB of free space for Update Manager on the boot drive is required to install Update Manager
    Although Update Manager does not need to be installed on the boot drive, some required components must be installed on the boot drive. 600MB of space for Update Manager is required at installation time to accommodate these required components, as well as temporary files used during the installation.
    Workaround: Ensure at least 600MB of free space on the boot drive before installing Update Manager.

Scanning, Staging, and Remediation

  • Update Manager fails to create baselines and download meta data about patches if you use Oracle databases of version 11.2.0.3 or 11.2.0.4
    When using Oracle databases of version 11.2.0.3 or 11.2.0.4, Update Manager fails to create baselines and download meta data about patches.
    Workaround: Use Oracle Instant Client Package - ODBC of version 11.2.0.2 for 32-bit Microsoft Windows to create a 32-bit DSN so that Update Manager connects and uses properly Oracle database servers of version 11.2.0.3 or 11.2.0.4.
    You can download Oracle Instant Client Package - ODBC of version 11.2.0.2 for 32-bit Microsoft Windows from the following link.
  • Product to vendor mapping in the New Baseline wizard is incomplete after new installation of the Update Manager server or after you download patches for the first time
    After you install the Update Manager server or after you download patches for the first time, when you are creating a new dynamic baseline, the Product text box of the Dynamic Baseline Criteria page of the New Baseline wizard might not list all the products of the vendor selected in the Patch Vendor selection window.
    Workaround: Log out and log in to the vSphere Client.
  • Remediation of Virtual SAN cluster fails if total number of CPUs for the virtual machines in the Virtual SAN data store exceeds 384
    Attempts to remediate a Virtual SAN cluster with virtual machines in the Virtual SAN data store that have 384 or more active CPUs, against a patch that requires the hosts to enter maintenance mode, fail.
    Workaround: Perform one of the following workarounds:
    • Power off the virtual machines that are part of the Virtual SAN data store to keep the number of active virtual machine CPUs below 384.
    • After Virtual SAN cluster remediation fails due to the inability of a host to enter maintenance mode state, attempt to run remediation on the hosts from the Virtual SAN cluster that failed to remediate.
  • During staging or remediation of patches a wrong warning message might appear
    During patch staging or remediation operations in Update Manager, you might be incorrectly warned that some patches are not available. The warning message you receive is:
    Some of the patches you selected for remediation are not available. Do you want to continue?.
    Workaround: Ignore the message, and click Yes to proceed with staging. All patches that you initially selected will be staged.
  • Update Manager reports the compliance status as Incompatible when scanning or remediating ESXi 5.x hosts that belong to an HA cluster
    When you perform an upgrade scan of ESXi 5.x hosts that belong to an HA cluster, Update Manager might report the compliance status of the hosts as Incompatible and might not allow the hosts to be remediated. The Incompatible compliance status is because of the way the FDM (HA) agent is installed on ESXi 5.x hosts. Starting with vSphere 5.0, the FDM agent is installed on ESXi hosts as a VIB. When a VIB is installed or updated on an ESXi host, a flag is set to signify that the bootbank on the host has been updated. Update Manager checks for this flag while performing an upgrade scan or remediation and requires this flag to be cleared before upgrading a host. The flag can be cleared by rebooting the host.
    Workaround: Reboot hosts that report the compliance status as Incompatible. Run the upgrade scan or remediation again after the host is back online.
  • Recent Tasks pane displays error message during VM Hardware upgrade of powered-on virtual machines on ESXi 5.1 host
    When you perform a VM Hardware upgrade of powered-on virtual machines on an ESXi 5.1 host that is incompatible with VM Hardware version 9, the Recent Tasks pane displays the error message: The target host does not support the virtual machine's current hardware requirements. For incompatibilities other than cpuid.LM: if possible, use a cluster with Enhanced vMotion Compatibility (EVC) enables; see KB article 1003212. Requirements were not met for the following features:
    See the error stack for details on the cause of this problem.
    The remediation process completes successfully and the VM Hardware version is upgraded to match the ESXi 5.1 host.
    Workaround: Ignore the error message.
  • Remediating ESXi 5.0 hosts against bulletins that are marked as requiring reboot might not reboot the hosts
    Some updates require the host to be rebooted during the remediation process. The information about whether a reboot is required is contained in the update metadata and is displayed in the Update Manager Patch Repository, under Impact. For ESXi 5.0 VIBs, the reboot requirement is not determined solely by the metadata, but instead depends on the VIB specification and whether a previous version of the VIB is installed on the host. This provides reboot optimization for some VIBs, where an initial installation does not require a host reboot and only subsequent patching of the VIB requires a reboot.
    Workaround: No workaround is required. Update Manager reboots hosts as necessary to ensure a successful remediation.
  • Host patch remediation fails when patch metadata is not available
    In the Update Manager installation wizard, you can deselect Download updates from default sources immediately after installation. After installation, on the Configuration tab, you can choose to download only patch metadata from sources for specific ESXi versions, for example, only patch metadata for ESXi 5.5. In such a situation, if you attempt to remediate a container with ESXi hosts of different versions, and you have downloaded patch metadata for some and not all host versions, the remediation fails.
    Workaround: Download patch metadata for all host versions you have in your inventory.
  • Host remediation might not complete if the host contains powered on fault tolerant virtual machines
    Host remediation might not complete if there are any Primary virtual machines with disabled FT on the host, and you select Fail Task or Retry on the Host Remediation Options page of the Remediate wizard. In such a scenario, powered on Primary virtual machines with disabled FT cannot be powered off or migrated in a DRS cluster. The host cannot enter maintenance mode while there are powered on virtual machines on it, and the remediation cannot be completed.
    Workaround: When you remediate hosts containing Primary or Secondary virtual machines, you can use one of the following workarounds:
    • Select Power Off virtual machines and Retry or Suspend virtual machines and Retry on the Host Remediation Options page of the Remediate wizard.
    • Manually migrate the fault tolerant virtual machine to another host before you start a remediation.
    • If EVC is enabled on a DRS cluster, virtual machines with disabled FT can be automatically migrated when the host tries to enter maintenance mode. This is possible only if DRS is not disabled on the particular host.
  • Host remediation might fail if vCenter Server does not properly update the power state of the host
    When a host is being powered on or exiting standby mode, the host power state might not get updated in vCenter Server and host remediation cannot finish or times out. When the power state of a host is not updated properly, in the vSphere Client inventory the host might be displayed as if it is in standby mode, even though it is powered on.
    Workaround: To remediate the host, remove the host from the inventory and add it again so that vCenter Server refreshes the power state of the host and then start the remediation process.
  • The Remediation Selection page might display an incorrect number of patches for the selected baselines
    When you remediate a vSphere inventory object against a patch or extension baseline preselected in Compliance view, the initial page of the remediation wizard might show an incorrect number of patches that need to be remediated. In this case, when the inventory object has multiple attached patch and extension baselines, the number of patches corresponds to the number of compliant patches from all attached baselines, and not just from the selected baselines.
    Workaround: Either change the selection of baselines or groups in the Remediation Selection page, or first click Next to go to the next page and then click Back to return to the selection page.
  • Host upgrade scan and remediation might fail if there is not enough free space on the host
    Host upgrade scan and remediation might fail with the AgentInstallFailed error message. This error might result from insufficient free space on the ESXi host.
    Workaround: To upgrade ESXi hosts, ensure you have at least 20MB free space in the /tmp directory of the host.
  • Host remediation might fail for some patches because of irresolvable conflict with the patches on the host
    Patch remediation of a host might fail when a patch (for example, patch A) in a baseline input conflicts with the host and the conflict cannot be resolved by the other patches in the baseline input.
    Workaround: The Patch Details window for patch A displays a recommendation to use another patch to resolve the conflict. The recommendation might also contain many patches. Including one or all of the recommended patches into the baseline might resolve the conflict. For more information, refer to the KB article associated with patch A and the recommended patches.

Internationalization Issues

  • When you double-click VMware vSphere Update Manager.msi, the hint message is not localized
    When you extract all components that are required for the installation of Update Manager to a local folder, either from a .zip file or an .iso image, you can run the VMware vSphere Update Manager.msi application by double-clicking it. When you run the application, the hint pop-up displays the message The installer should be started using VMware-UpdateManager.exe. The message is in English and not localized.
  • You cannot install Update Manager and download patches to directories with non-ASCII characters in their names
    In the installation wizard of Update Manager, you can change the installation and patch download locations of the Update Manager. Changing the installation and patch download locations to folders containing non-ASCII characters in their names might result in errors. Only ASCII characters are supported in installation paths and user names. However, non-ASCII characters are supported in passwords.

Using Update Manager

  • Update Manager displays only one vCenter Server in vSphere environments with multiple vCenter Server instances
    In vSphere environments with multiple vCenter Server instances, which are either registered to one Platform Services Controller or each of them is registered to individual Platform Services Controller, Update Manager displays only the vCenter Server instance which IP/DNS was used in the Update Manager Client.
    Workaround: None. Regardless of which IP/DNS you entered in the Update Manager Client, in the inventory you should see both the vCenter Server instances.
  • You might fail to use Update Manager in vSphere environments with multiple vCenter Server instances, which are registered to one Platform Sevices Controller
    If you set a vSphere environment with two vCenter Servers that are registered to one Platform Sevices Controller, and you have Update Manager servers registered to each vCenter Server instance, you can successfully log in to one of the Update Manager instances, but when you attempt to log in to the second one, the Update Manager Client fails to connect. The following error message is displayed in the case of the Update Manager instance that you cannot log in to:
    Insufficient permissions to retrieve data.
    Workaround: In vSphere Web Client that manages the vCenter Server instances, create a new user with all vSphere privileges, and use that account to log in to the Update Manager instance that displays the error.
  • The Update Manager server can loose connection to the vCenter Server instance after a few days of uptime
    If you use the Update Manager server for a few days, it might loose connection to the vCenter Server instance, and while you perform operations in Update Manager Client you might see the following error:
    No connection to VC server to relogin.
    Workaround: By using the Update Manager Utility reconnect the Update Manager server to the vCenter Server instance, and then restart the Update Manager service.
  • As part of Virtual SAN cluster remediation process, a host from a Virtual SAN cluster might enter maintenance mode, while another host from the cluster is still in maintenance mode and is going through a reboot
    When you start remediation on a Virtual SAN cluster against a baseline containing a patch that requires the hosts to reboot, while the first host is rebooting, a second host might enter maintenance mode, before the first host reconnects to the vCenter Server. This causes the remediation process to fail, because only one host from a Virtual SAN cluster can be in maintenance mode at a time.
    Workaround: None
  • Update Manager fails to upgrade ESXi hosts of 5.1 Update release version to ESXi 6.0 if unsupported hardware devices exist on the target host
    When you use Update Manager to upgrade a host from an ESXi 5.1 Update release version to ESXi 6.0 by using an ISO image, if Update Manager discovers a set of hardware devices on the target host that are not supported with the upgrade ISO image, Update Manager displays the compliance state of the host as Incompatible. As a result, the attached ISO image is not staged, and the upgrade fails.
    The following warning messages are also associated with potential issues that can cause the target host to be in Incompatible compliance state.
    • VMkernel and Service Console network interfaces are sharing the same subnet <subnet_name>. This configuration is not supported after upgrade. Only one interface should connect to subnet subnet_name.
    • Unsupported devices device_name found on the host.
    Workaround: On the ESXi 6.0 Upgrade page of the Remediate wizard, select the option about ignoring the warnings about unsupported devices on the host during remediation to ensure a successful remediation.
  • Non-informative system error is displayed when a host that is part of Virtual SAN cluster fails to enter into maintenance mode during remediation
    During remediation, if a host that is part of a Virtual SAN cluster fails to enter maintenance mode, a generic system error about Virtual SAN is displayed, such as the following:
    A general system error occurred: Operation failed due to vSAN error.
    The error message does not contain any context for the cause of the failure or relevant error message.
    Workaround: To see more context about the cause of the failure, perform the following steps:
    1. In the Recent Tasks pane, click View Details.
    2. Click Submit error report and see more information about the cause of the failure under Error Stack.
  • Update Manager Utility does not support IPv6 address for login
    Attempts to login to the Update Manager Utility by typing a vCenter Server machine IPv6 address fail with an error.
    Workaround: To successfully log in to the Update Manager Utility, type the vCenter Server machine IPv4 address or host name.
  • VMware Update Manager does not use the configured proxy authentication
    When you initiate a patch download task, even though Update Manager is configured to use a proxy with authentication, Update Manager uses anonymous credentials to authenticate to the proxy server. If the proxy server does not accept anonymous credentials, the patch download task may fail.
    Workaround: Change Update Manager service to run using a local administrator account with local administrator rights or a domain account with local administrator rights.
  • The virtual machine that runs Update Manager might be powered off during a host upgrade
    Outside DRS clusters, Update Manager does not upgrade the host on which the vCenter Server or Update Manager virtual machine runs. In DRS clusters, if you start a remediation task on the host running the vCenter Server or Update Manager virtual machine, DRS attempts to migrate the virtual machine to another host, so that the remediation succeeds. If you remove the host on which the Update Manager virtual machine runs from a DRS cluster and then add it to a datacenter in the vSphere Client inventory, you can remediate the host and the Update Manager virtual machine is powered off.
    Workaround: Before remediation, ensure that the host on which the Update Manager virtual machine runs is in a DRS cluster or move the Update Manager virtual machine to another host.
  • You might be unable to view compliance information for a cloned virtual machine
    When you clone a virtual machine, enable Fault Tolerance for the machine, and power on the cloned virtual machine, you might not be able to view compliance information. When you open the Compliance view, the error Failed to retrieve data appears.
  • Missing patch type information in the Import Patches wizard
    On a new Update Manager installation, when you import offline patch bundles for the first time, patch type information is not displayed in the Import Patches wizard. The Type column on the Confirm Import page is empty.
    Workaround: Although the patch type information is not displayed, you can import the patches successfully by completing the wizard. This problem occurs only during the first import of offline patch bundles. Consequent import operations have the patch type information displayed correctly in the wizard.
  • Download patch definitions task might fail if Update Manager is configured to use authenticated proxy
    If the Update Manager server is configured to use a proxy server that requires authentication, the Download patch definitions task might fail to download patches.
    Workaround: Enable anonymous user access on the proxy server.
  • ESXi 5.0 does not support staging of a tools bulletin
    When you run a stage task with an ESXi 5.0 tools bulletin, the task completes successfully, but the tools bulletin is not staged.
    Workaround: You can remediate the Tools bulletin directly to install it. Host maintenance mode or reboot, and consequently host downtime, are not required during the remediation of the tools bulletin.
  • Update Manager cannot download updates from a valid download source
    A non-existent HTTPS URL might be incorrectly displayed as accessible in the Add Download Source window. For example, if you type https://mydepot.com instead of http://mydepot.com and click Validate URL, the validation might succeed even if the actual download source is an HTTP address. As a result, Update Manager cannot download updates from the specified HTTPS URL address.
    Workaround: Delete the URL and add it correctly.
  • Invalid email addresses in the email notification settings prevent Update Manager from sending email messages
    In the patch and notification download schedules, you can configure Update Manager to send emails when new patches or notifications are downloaded. If you enter invalid email addresses, Update Manager might not send emails. If you enter an invalid email address with the same domain name as the SMTP Server sender account in vCenter Server mail sender setting, Update Manager does not deliver emails to any of the email addresses (including the valid ones). If the domain name of the invalid email addresses is different from the SMTP Server sender account in vCenter Server mail sender setting, email notifications can be successfully delivered to the valid email addresses entered in the Update Manager email notification settings.
    Workaround: Remove the invalid email addresses from the email notification settings.
  • In Windows Vista, all Help buttons in the Update Manager Client open the default Update Manager help page
    If you are using Internet Explorer 7 browsers installed on Windows Vista machines, the vSphere Update Manager context-sensitive help does not display the relevant help pages. Instead, the help displays the default vSphere Update Manager help page.
    Workaround: Apply Service Pack 2 to Windows Vista. For more details, see the Microsoft KB article http://support.microsoft.com/kb/942172.
  • Notification emails might be blocked by antivirus software
    You might not receive any email notifications from Update Manager if you have certain antivirus software installed on your vCenter Server system. Update Manager can be configured to send email notifications, such as notifications for newly downloaded patches and other scheduled tasks. If you have installed antivirus software (for example, McAfee) that monitors and blocks email traffic, you might not be able to receive the notifications from Update Manager.
    Workaround: Disable the antivirus software rule that blocks the email traffic.
  • Switching between Compliance view and Administration view might navigate you to the wrong location
    When you select a datacenter object in the VMs and Templates inventory of the vSphere Client and use the Admin view and Compliance view quick links to navigate to the Update Manager Administration view and the Update Manager Compliance view, you might go to the wrong vSphere Client inventory. For example, select Home > Inventory > VMs and Templates in the navigation bar. Select a datacenter object in the inventory and click the Update Manager tab to open the Update Manager Compliance view. When you click Admin view and then go back by clicking the Compliance view link, you navigate to the Host and Clusters inventory instead of the VMs and Templates inventory.
    Workaround: Manually navigate from the Hosts and Clusters inventory view to the VMs and Templates view by selecting Home > Inventory > VMs and Templates in the navigation bar.
  • Update Manager does not take snapshots of virtual machines on which FT is turned on before remediation
    You cannot take snapshots of virtual machines on which FT is enabled. If you remediate a virtual machine on which FT is turned on and in the Remediate wizard choose to take a snapshot before remediation, Update Manager ignores this setting and does not take a snapshot of the virtual machine.
    Workaround: Disable FT, configure Update Manager to take a snapshot of the virtual machine, and remediate the machine. If you want to turn on FT after the remediation, delete the snapshot and then enable FT.
  • When multiple users attempt to create a baseline with the same name simultaneously, Update Manager displays an ambiguous error message
    When multiple users attempt to create a baseline with the same name simultaneously, Update Manager displays the message The specified key, name, or identifier already exists. The message does not inform you explicitly that another user is attempting to create a baseline with the same name.
  • When you stage a baseline that contains multiple bulletins, some bulletins might be shown as missing
    After the successful staging of a baseline that contains multiple bulletins, some bulletins might be shown as Staged and others as Missing. For more information, see After you stage a baseline, a bulletin might be shown as Missing instead of Staged (KB 1018530).
  • Update Manager fails to install and upgrade the Cisco Nexus 1000V VEM, if the ESX host is running on an IPv6 networking stack
    When an ESX host is added to a Cisco Nexus 1000V DVS, Update Manager installs the Cisco Nexus 1000V VEM on the host. Upgrading the Cisco Nexus 1000V VSM to the latest version invokes Update Manager to upgrade the VEM on the host attached to the DVS. Both the installation and the upgrade operations might fail if the host is running on an IPv6 networking stack.
    Workaround: Install or upgrade the VEM on the host manually, by using the offline bundle.
  • During VMware Tools upgrade you might see a misleading error message in Recent Tasks pane
    When you perform a VMware Tools upgrade of a virtual machine, you might see a misleading error message Cannot complete operation because VMware Tools is not running in this VM even though the remediation is successful.
  • Scheduling a remediation task generates a set of tasks
    When you schedule a remediation task, several active tasks appear in the Recent Tasks pane. One of these tasks is Remediate Entity. This task appears when you create a new remediation task and is not an actual remediation task in which the objects are remediated. The Remediate Entity task creates sub-tasks for the scheduled remediation based on your input in the Remediate wizard.
  • Administration view and Compliance view quick-switch links might not work properly if your environment is in linked mode
    If your vCenter Server system is part of a Linked Mode and you have a separate Update Manager instances registered with each vCenter Server system, the Admin view and Compliance view navigation links might not work properly. For example, consider a scenario in which Update Manager instance 1 is registered with vCenter Server system 1 and Update Manager instance 2 is registered with vCenter Server system 2. When you select an object managed by vCenter Server system 1, click the Update Manager tab, and then click Admin view in the upper-right corner, you see the Administration view of Update Manager instance 1. When you click Compliance view, select an object from the inventory managed by vCenter Server 2, and click Admin view in the upper-right corner, you see the Administration view of Update Manager instance 1 again.
    Workaround: Click Compliance view and then click Admin view again to see the Administration view of the second Update Manager instance.
  • Conflicting patches are counted in the remediation wizard
    After you scan a selected object against a patch baseline, you might see a number of conflicting patches in the Patch Baselines window. When you try to remediate the selected object, the conflicting patches are counted in the Remediation wizard as patches that are going to be installed on the object, but only some or none of the conflicting patches are installed during the remediation process.
  • Update Manager Service might fill the Temp directory with many temporary system files
    You might see many files with names like ufa{*}.tmp and ufa{*}.tmp.LOG{*} in the Windows Temp directory (the default location is C:WINDOWSTemp).
    • ufa{*}.tmp files – These files are created when the Update Manager service becomes unavailable in the middle of an offline virtual machine scan. To delete the ufa{*}.tmp files (for example, to delete a ufa729F.tmp file), perform the following steps:
      1. Select Start > Run.
      2. In the Run window, type regedit and press Enter.
      3. In Registry Editor, navigate to the My ComputerHKEY_LOCAL_MACHINE folder and select the ufa729F.tmp file.
      4. Select File > Unload Hive.
      5. Open a command prompt window.
      6. Navigate to C: and run the following command:
        del C:WindowsTempufa729F.tmp
    • ufa{*}.tmp.LOG{*} files – These files are Windows transaction log files for registry operations. They can be generated as a result of Windows logging registry transactions, and are removed after use. ufa{*}.tmp.LOG{*} files are like any other Windows temporary files and can be deleted as a part of a Windows Disk Cleanup task.
      To delete the ufa{*}.tmp.LOG{*} files (for example, to delete a ufaFF50.tmp.LOG2 file), perform the following steps:
      1. Open a command prompt window.
      2. Navigate to C: and run the following command:
        del C:WindowsTempufaFF50.tmp.LOG2

Using Update Manager Web Client

  • Update Manager Web Client is not displayed in the vSphere Web Client
    If you registered the Update Manager server with a vCenter Server system using IPv6 address but then log in the vSphere Web Client using an IPv4 address, the Update Manager tab does not display in the vSphere Web Client.
    Workaround: To see the Update Manager tab in the vSphere Web Client, perform one of the following tasks:
    • If you registered the Update Manager serer with a vCenter Server system using IPv4, use IPv4 address to connect to the vSphere Web Client.
    • If you registered the Update Manager serer with a vCenter Server system using IPv6, use IPv6 address to connect to the vSphere Web Client.
  • Compliance state information inconsistencies might appear on Update Manager Web Client page
    When you select a baseline in Update Manager Web Client, you see compliance state information for the object in the Attached Baselines table, the Attached Baseline Groups drop-down menu, and compliance state details under the Attached Baselines table.
    If you or another user perform operations that affect the compliance state of an object, some inconsistencies might appear in the compliance state information that is displayed on the Update Manager Web Client page. For example, operations that can affect an object's compliance state are remediating the object in Update Manager Client, updating the object directly or changing the contents of the baseline in Update Manager Client.
    When you select a baseline in the Update Manager Web Client the compliance state details always show information for the object's latest compliance state. However, the baseline displays the compliance state from the last scan operation initiated from the Update Manager Web Client or from the last time you refreshed the vSphere Web Client.
  • The attached baselines in the Update Manager Web Client differ from the attached baselines in the Update Manager Client
    When you attach a baseline to a vSphere inventory object in the Update Manager Client, it does not appear in the Attached Baselines table of the Update Manager Web Client.
    When you detach a baseline in the Update Manager Client, it does not disappear from the Attached Baselines table in the Update Manager Web Client.
    If you initiate a scan from the Update Manager Web Client against a baseline that is already detached in the Update Manager Client, but is still visible in the Update Manager Web Client, after the scan operation completes, the baseline disappears from the Attached Baselines table of the Update Manager Web Client.
    This behavior occurs because Update Manager Web Client does not automatically refresh all contents after performed operations from the Update Manager Client.
    This behavior is the same for baselines and baseline groups.
    Workaround: Manually refresh the vSphere Web Client.