VMware VMware Workspace Portal 2.1 released

At September 9 VMware released Workspace Portal 2.1

Workspace Portal is a portal which allows end-users access to web-based app, a Windows app hosted by Horizon or XenApp, a local Windows app packaged and streamed through Thinapp, a Google app, or Office 365 app, or nearly any SaaS app like ADP, SalesForce, Workday, or Box.

Workspace Portal provides the entitlement, access policy and single sign-on capability for all but native mobile applications. From laptops and desktops, it is truly a one-stop show for any app or service. When that same user is using their tablet or smartphone, now, there is no need to “go” to Workspace Portal as AirWatch can deliver the Workspace Portal entitled apps directly through to the “springboard” (what Apple iOS calls their “home screen”) or container on the device.

Apps which are run on a mobile device are deployed using VMware AirWatch.

Some more info on what is new here

More info on Workspace Portal in this VMware blog

Release notes are here

 

VMware ThinApp 5.1 released

VMware released at September 9 ThinApp 5.1

VMware ThinApp 5.1 is the latest version of ThinApp. This release has the following enhancements.

Release notes are here 

ThinApp is part of the VMware Horizon Suite. Download here

ThinApp Package Management

In earlier versions of ThinApp, to change some specific Package.ini parameters, you had to first make those changes in the configuration file, save the file, and rebuild the package. Using the new ThinApp package management feature, you can dynamically reconfigure the attributes of deployed ThinApp packages at runtime. ThinApp Package management helps IT administrators manage ThinApp packages and define group policy for each package. Each package to be managed must have an associated group policy defined using its inventory name.

When you install ThinApp 5.1, a new folder named Policy is created in the installation directory. This folder contains tools and templates for managing ThinApp packages and contains the following files:

  • AppPolicy.exe
  • README.TXT
  • ThinAppBase.adml
  • ThinAppBase.admx
  • ThinAppGeneric.adml
  • ThinAppGeneric.admx

ThinApp selects the policy precedence when you rebuild a package and deploy it. If a package is managed by a group policy, ThinApp gives precedence to the policy over its Package.ini configuration.

Group Policy Administrative Templates

ThinApp 5.1, introduces the group policy administrative template (ADMX/ADML) files. With these template files you can reconfigure group policy settings for applications that were packaged by ThinApp. The GPO files work on domain controllers that run in the following environments:

  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012

Administrative Template files contain markup language that is used to describe a registry-based Group Policy. The administrative files are divided into language-neutral (.admx files) and language-specific resources (.adml files), available to all Group Policy administrators. These factors allow Group Policy tools to adjust the user interface according to the administrator’s configured language.

Reconfiguring Attributes of Deployed ThinApp Packages

In addition to ThinDirect, with ThinApp 5.1 you can now reconfigure or manage the following attributes of a deployed package:

  • AppSync
  • AppLink
  • Entry-Point Shortcuts

Note: To know how to reconfigure these package attributes, see the ThinApp 5.1 User’s Guide.

ThinDirect

In ThinApp 5.1, the following enhancements have been made to the ThinDirect plug-in:

    • Support for the update of ThinDirect settings at specified time intervals

In ThinApp 5.1, the ThinDirect functionality has been enhanced to periodically poll for the ThinDirect setting changes. Since, the ThinDirect settings are now detected dynamically, the user need not restart the browser to view the updated changes.

    • Support for dynamic changes to Thindirect via ADM

In ThinApp 5.1, you can use ThinDirect.ADM file to manage the thindirect enabled firefox.

    • Support for Overriding the Thindirect settings through GPO

In ThinApp installation directory, locate the Thindirect.admx andThinDirect.adml files. Use these files to manage the settings for ThinDirect feature by defining a group policy object. If the Thindirect feature is defined through the GPO, these settings would override the text file (thindirect.txt) based redirection.

    • Support for Redirection between two virtual browsers

ThinApp 5.1 supports redirection between two virtual browsers.

    • Support for Thindirect in Mozilla Firefox

In ThinApp 5.1, ThinDirect has been enhanced to work with Mozilla Firefox version 22 and later. In earlier versions of ThinApp, ThinDirect was limited to Internet Explorer.

New Package.ini Parameter Introduced

ThinApp 5.1 introduces the SandboxWindowClassName parameter. When you set theSandboxWindowClassName=1 you can sandbox or isolate the application defined window class names created and used within the ThinApp package.

Extracting an existing ThinApp project to a system

ThinApp 5.1 allows you to extract an existing ThinApp project to a capture and build operating system by using snapshot.exe and snapshot64.exe commands.

Pre-requisites
Before you extract an existing ThinApp project to a capture and build operating system, ensure that the following conditions are met:

  • Verify that the architecture and type of the captured operating system is the same as that of deployed operating system.
  • Perform the extraction of an existing ThinApp project on a clean capture and build machine.
  • Ensure that the user profile in the existing virtual project is the same as that of the capture and build machine.

ThinApp 5.1 has the following command line options to extract existing projects to capture and build operating systems.

  • snapshot.exe: Is used to extract an existing ThinApp project to a capture and build 32-bit operating system
  • snapshot64.exe: Is used to extract an existing ThinApp project to a capture and build 64-bit operating system

Note: To know more about the process for extracting existing ThinApp packages, see the ThinApp 5.1 User’s Guide.

MAPI Support

ThinApp 5.1 supports the Messaging Application Programming Interface (MAPI) on the following Microsoft Windows platforms:

  • Windows 7
  • Windows 8 32-bit
  • Windows 8 64-bit
  • Windows 8.1 32-bit
  • Windows 8.1 64-bit

ThinApp 5.1 provides the DefaultEmailProgram option in Package.ini to register a virtual email client as the host’s default email program. You have to enable this option to register the default email program. The Messaging Application Programming Interface (MAPI) is not supported on Windows XP x86 operating system. For more information, see KB artilce2087898.

Support for Internet Explorer 10 and Internet Explorer 11

ThinApp 5.1 supports Internet Explorer 10 and Internet Explorer 11 only on the Windows 7 operating system.

Support for Windows 8.1

ThinApp 5.1 works on the Windows 8.1 August update (Update 2).

For additional information about ThinApp 5.1, visit the following Web site:

Visio Stencil Set for 2014 VMware vSphere and Horizon

Ray Heffer shares a new Visio stencil set for 2014 which contains some popular shapes for VMware Horizon View, Workspace and vSphere. These are not official VMware stencils, but have been created from existing external content (thanks to Maish Saidel-Keesing at TechnoDrone) in addition to using Adobe PhotoShop and pulling images from public PDF documentation.

Download at www.rayheffer.com

VMware Horizon View 5.3 is now generally available

At November 21 VMware released VMware Horizon View version 5.3.0.

This release has some interesting features like support for Virtual SAN, and Windows 8.1 & Windows Server 2008 as desktop operating system.

It also features  a new storage overcommit option for linked-clone desktop pool storage.
When customers select the Unbounded overcommit option, they can place as many linked clones on the selected datastore as they desire. This feature is beneficial to customers who use third-party storage technologies (for example, Atlantis Computing VSA), which optimize the space consumed by the virtual disks of the individual virtual machines.

More on the storage optimization features in View 5.3 in this blogpost. 

Release notes are here
Documentation can be downloaded here.
Download the software from MyVMware

What is new in View 5.3? 

VMware Horizon View 5.3 delivers important features and enhancements and resolves some known problems in the previous release. This release of VMware Horizon View adds the following new features and support.

  • Windows Server 2008 R2 Desktop Operating System Support
    Windows Server 2008 R2 (Datacenter edition) is now supported as a desktop operating system. For installation instructions and limitations, see KB 2057605: Using Windows Server 2008 R2 as a desktop operating system in VMware Horizon View.
  • Windows 8.1 Desktop Operating System Support
    Windows 8.1 is now supported as a desktop operating system.
  • VMware Horizon Mirage Support 
    You can now use VMware Horizon Mirage 4.3 to manage View desktops. See the VMware Horizon Mirage Administrator’s Guide for complete information about this feature.
  • VMware Virtual SAN Datastore Support
    When you create a desktop pool in View Administrator, you can now select a Virtual SAN datastore to store desktop virtual machines. Because Virtual SAN is in Beta, this feature is being released as a Tech Preview, which means that it is available for you to try, but it is not recommended for production use and no technical support is provided. The space-efficient virtual disk format is not available on Virtual SAN datastores. If you use Virtual SAN datastores to host virtual desktops, you will not be able to reclaim allocated unused space on the virtual machines.
  • View Connection Server Memory Recommendation Messages 
    If you install View Connection Server with less than 10GB of memory, VMware Horizon View provides memory recommendations by generating warning messages after the installation is complete.
  • vDGA Support
    vDGA (virtual Dedicated Graphics Acceleration) is now supported for View desktops. For linked-clone desktops, vDGA settings are preserved after refresh, recompose, and rebalance operations.
  • Linked-Clone Desktop Pool Storage Overcommit Feature Enhancements 
    The linked-clone desktop pool storage overcommit feature includes a new storage overcommit level called Unbounded. When you select Unbounded, View Manager does not limit the number of linked-clone desktops that it creates based on the physical capacity of the datastore. You select the storage overcommit level for a linked-clone desktop pool on the Select Datastores page when you add or edit a linked-clone pool. SelectUnbounded only if you are certain that the datastore has enough storage capacity to accommodate all of the desktops and their future growth.
  • View Persona Management Supportability Improvements
    Supportability improvements include new log messages and profile size and file and folder count tracking. View Persona Management uses the file and folder counts to suggest folders for redirection in the Windows event log and provides statistics for these folders.
  • Support to Grant Domain Administrators Access to Redirected Folders in View Persona Management
    A new group policy setting, Add the Administrators group to redirected folders, has been added to make redirected folders accessible to domain administrators. For information about the new group policy setting, see KB 2058932: Granting domain administrators access to redirected folders for View Persona Management.
  • VMware Horizon View Agent Direct-Connection Plug-in
    You can use VMware Horizon View Agent Direct-Connection Plug-in to connect directly to a virtual desktop. This plug-in is an installable extension to View Agent that allows a View client to directly connect to a View desktop without using View Connection Server. For more information, see VMware Horizon View Agent Direct-Connection Plug-in Administration.
  • View Composer Array Integration (VCAI) Support 
    The Tech Preview designation has been removed from VCAI. VCAI appears as an option during pool creation when you select an NFS datastore on an array that supports VAAI (vStorage API for Array Integration) native snapshots. The VCAI feature is now supported with select NAS vendors. For a list of supported NAS vendors, see KB 2061611: View Composer API for Array Integration (VCAI) support in VMware Horizon View.
  • Blast Secure Gateway Maximum Connections
    The Blast Secure Gateway (BSG) now supports up to 350 connections to Horizon View desktops from clients using HTML Access. This connection limit applies to a BSG on one View Connection Server instance or security server.