vRealize Operations for Published Applications 6.1

VMware vRealize Operations for Published Applications extends the functionality of VMware vRealize Operations Manager to monitor and manage Citrix XenApp 6.5 environments.

vRealize Operations for Published Applications collects data about your resources and presents that data in pre-configured dashboards for both real-time and predictive analysis.

Features in This Release

vRealize Operations for Published Applications 6.1 includes the following new features.

  • vRealize Operations Manager 6.0.2 support – vRealize Operations for Published Applications 6.1 is compatible with vRealize Operations Manager 6.0.2. It does not support earlier vCenter Operations Manager versions.
  • Monitoring and troubleshooting – vRealize Operations for Published Applications 6.1 monitors and generates reports for Citrix XenApp application, session, and license usage.
  • Citrix ICA virtual channel monitoring – vRealize Operations for Published Applications 6.1 monitors ICA virtual channels performance insight for faster session assessment and troubleshooting.
  • Out-of-the-box and custom summary reports – You can generate reports from pre-configured report templates or configure your own reports.
  • Internationalization – The vRealize Operations for Published Applications user interface and documentation are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.

More info at vRealize Operations for Horizon

Atlantis USX 2.2 Released

Atlantis USX is a software solution that accelerates performance and consolidates storage, increasing effective storage capacity to support running server workloads such as business-critical applications. USX builds on proven Atlantis compression, caching, deduplication, and tiering capabilities to provide a dramatically reduced storage footprint and improved performance, including built-in high availability. USX satisfies the storage requirements demanded by server workloads, removing the constraints of traditional storage.

With the new release the following new features came available.

  • XenServer – USX now supports Citrix XenServer. XenServer can use any of the USX volume types. USX configuration, deployment, and management is the same for all platforms.
  • New volume types:
    • The Hyper-Converged volume type supports server or VDI workloads and consumes only
      local resources. Hyper-Converged volumes are associated with an Infrastructure volume that
      provides shared storage so that the Hyper-Converged volume can migrate before entering
      maintenance mode even though the Hyper-Converged volume uses only local resources.
    • The Simple All Flash volume type supports persistent VDI deployments and enables you to
      use flash for both performance and capacity.
  • Maintenance mode – A host can be placed into maintenance mode from the new Hypervisors Management screen in the USX GUI.
  • Volume power operations and reboots can be performed from the Manage Volumes screen.
  • LDAP authentication – Use the new LDAP Authentication screen to bind to an LDAP server so that members of a specified LDAP group can log into USX.
  • Tree hierarchies are implemented for the display of datacenters, clusters, and hypervisors.
  • SNMP configuration – A new document, Atlantis USX SNMP Configuration, provides a listing of the USX MIB and information about configuring USX to communicate with an SNMP trap host.

Atlantis USX 2.2 is now available in the download portal

Upgrading vCenter Server Appliance 5.0.x/5.1 to 5.5

Prerequisites
To upgrade vCenter Server Appliance from 5.0.x/5.1 to 5.5:
  1. Deploy the new version of the vCenter Server Appliance. For more information, see Downloading and deploying the vCenter Server Appliance 5.x (2007619).

    Note: The new appliance has a default network configuration and the VMware VirtualCenter Server service is not configured and is disabled. There is a known issue were the vCenter Server Appliance will not change the hostname when deployed. For more information, see VMware vCenter Server Appliance 5.5 sets a wrong hostname after deployment (2065275)

  2. Connect to both the old and new appliances in separate browser windows. For example, use a URL similar to https://ip_address_of_vCenter_VM:5480.
  3. In the new appliance, start the vCenter Server Setup wizard and accept the end user license agreement.
  4. In the Configure Options panel, select Upgrade from previous version and then click Next.
  5. Copy the key from the Import this key section into the source appliance field.
  6. If you are upgrading vCenter Server Appliance 5.0.x to 5.5:
    1. In the old vCenter Server Appliance 5.0, click the Appliance Upgrade tab.
    2. Select source for the appliance role and click Setrole.
    3. Click Establish Trust.
    4. Paste the local appliance key into the Remote appliance key field.
    5. Click Import remote key.
    6. Copy the local appliance key.
    7. In the new vCenter Server Appliance 5.5, paste the local appliance key into the Remote appliance key field and click Next.
  7. If you are upgrading vCenter Server Appliance 5.1 to 5.5:
    1. In the old vCenter Server Appliance 5.1, paste the key from Step 5 into the Upgrade key field.
    2. Click Import key and Stop vCenter Server.
    3. Copy the Upgrade key.
    4. In the new appliance, paste the Upgrade key to the Paste the source appliance key into the field below field and click Next.
    5. If there are issues detected with your SSL certificates, select the Replace the SSL certificates option. You are prompted for SSO password for user administrator@vsphere.local.

  8. In the new vCenter Server Appliance, click Next.

    Note: The new appliance shuts down the old appliance and assumes the network identity (IP address, hostname, and network configuration) of the old appliance after the transfer has completed. This process can take some time and the virtual machines may appear unresponsive during the transfer. If the old appliance was configured to use dynamic addressing, the new appliance also uses dynamic addressing. When the import completes, the new vCenter Server Appliance starts.

  9. Review the list of hosts managed by the source appliance and ensure that all hosts to be managed by the new appliance are selected.
  10. Review the pre-upgrade check of the source appliance hosts and correct any errors before proceeding.
  11. Confirm that you have taken a backup or snapshot of the source appliance and the external database and click Next.
  12. (Optional) To follow the upgrade process, open an SSH session to the new vCenter Server Appliance and run this command:

    tail -f /var/log/vmware/vami/upgrade.log

    Note: This also helps in identifying where the process has stopped, if there are any issues with the upgrade.

  13. When the upgrade completes, click Close. vCenter Server Appliance is now upgraded and the new appliance reboots.

VMware Remote Console 7.0 Released

VMware Remote Console (VMRC) is a standalone Windows application that provides console access and client device connection to virtual machines on a remote host.  You need to download this installer before you can launch the external application directly from a vSphere Web Client.

In the VMware Remote Console Windows application, you will have access to:

  • Mouse and keyboard functionality in the VM
  • Send Ctrl + Alt + Delete
  • Full screen mode
  • VM power operations
  • Client-side device connection such as CD-ROM, USB, and Floppy (requires administrator access)

Internationalization

VMware Remote Console 7.0 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese
  • Russian
  • Italian
  • Spanish
  • Portugal
  • Nederlands

Download at source