Technical Guides

Delivering a Seamless Digital Workspace Experience with Horizon Cloud

VMware Workspace ONE integrates with VMware Horizon Cloud to provide a simple and secure enterprise platform that allows end users to access their applications, data and services from any device, anywhere. Both platforms were built to integrate with each other, which provides a single user interface (UI) through the Workspace ONE enterprise catalog, to deliver applications to end users.

Explore Workspace ONE further in a Hands-on Lab.

About Workspace ONE

Workspace ONE combines identity, real-time application delivery and mobility management to provide a digital workspace to your end users. This digital workspace delivers Software-as-a-Service (SaaS) applications, public native mobile applications—and when integrated with Horizon Cloud, virtual applications and desktops—all from a single, unified application store.

About Horizon Cloud

Horizon Cloud enables the delivery of cloud-hosted or on-premises virtual desktops and applications. With Horizon Cloud, you can leverage a cloud-based management plane and even infrastructure, instead of deploying an entire infrastructure to support VDI desktops and RDS applications traditionally. Your IT organization can focus on delivering applications and desktops, instead of spending time maintaining the infrastructure.

Benefits of Integration

The integration of Workspace ONE and Horizon Cloud provides a number of benefits:

Single Sign-On

One of the primary advantages that Workspace ONE and Horizon Cloud provide is secure, single sign-on (SSO) to both desktops and applications. This provides simplicity and ease of access while maintaining security. Users can utilize either the Workspace ONE web-based portal from any HTML 5 web browser or the Workspace ONE mobile application. And when used with an iOS-based device, users can utilize touch ID for SSO.

Two-Factor Authentication

Workspace ONE provides multiple multi-factor authentication methods, such as RSA, Radius, Certificate, Kerberos, and VMware Verify to protect your environment beyond the basic user ID and password. Workspace ONE also provides two-factor authentication (2FA) for Horizon Cloud to secure your Digital Workspace.

In addition, you can utilize step-up authentication, which allows additional multi-factor authentication beyond the initial authentication into Workspace ONE when accessing a desktop or application. This increases the security by requiring two-factor authentication to access a specific desktop or application, even if you don&#rsquo;t require it to access Workspace ONE.

Three Integration Options

Both Horizon Cloud and Workspace ONE have a cloud hosted option and an on-premises option. You can integrate the Horizon Cloud options with the Workspace ONE options in the following configurations:

Figure 2: Possible Integration Configuration Options

Although the two types of deployment have unique architecture requirements, both require an on-premises component. The on-premises component can be a virtual appliance or a Windows server, based on the type of deployment. For more information on the different deployments and their architecture, see VMware Workspace ONE Documentation.

Integration 1: Horizon Cloud with Hosted Infrastructure and Workspace ONE Cloud

Horizon Cloud with Hosted Infrastructure supports only Workspace ONE Cloud.

Figure 3: Integration 1: Horizon Cloud with Hosted Infrastructure and Workspace ONE Cloud

The following Figure 4 illustrates the integration option for Horizon Cloud with Hosted Infrastructure and Workspace ONE Cloud. The VMware Identity Manager Connector (a) is deployed on-premises in your data center. This integrates with your Active Directory and synchronizes the resources between Horizon Cloud and Workspace ONE, along with desktop and application entitlements. This synchronization between the VMware Identity Manger Connector and Horizon Cloud occurs over the VPN or Direct Connect (b), which connects your data center to your Horizon Cloud tenant (c). The VMware Identity Manager Connector then synchronizes the resources and entitlements to the VMware Identity Manager (IDM) Cloud service (d).

Figure 4: Integration 1: Horizon Cloud with Hosted Infrastructure and Workspace ONE Cloud

Integration 2: Horizon Cloud On Premises and Workspace ONE On Premises

Horizon Cloud with On-Premises Infrastructure supports both the on-premises and cloud versions of Workspace ONE.

Figure 5: Integration 2: Horizon Cloud On-Premises and on-premises version of Workspace ONE

You can use Horizon Cloud with On-Premises Infrastructure to run desktops and applications in their data center using Hyper Converged Infrastructure (HCI) Appliances, but with abut with a cloud base control plane.

Figure 6 illustrates the integration option for Horizon Cloud On-Premises Infrastructure and on-premises version of Workspace ONE. VMware Identity Manager (a) is deployed as a virtual appliance in your data center. This provides integration with your Active Directory (b) and also performs the synchronization of the resources between Horizon Cloud and Workspace ONE (c), along with desktop entitlements.

Figure 6: Integration 2: Horizon Cloud On-Premises and on-premises version of Workspace ONE

Integration 3: Horizon Cloud On Premises and Workspace ONE Cloud

Horizon Cloud with On-Premises Infrastructure supports both the on-premises version of Workspace ONE and Workspace ONE Cloud.

Figure 7: Integration 3: Horizon Cloud On Premises and Workspace ONE Cloud

For Workspace ONE Cloud, the VMware Identity Manager Connector (a) is deployed on-premises in your data center (b). This provides integration with your Active Directory and also performs the synchronization (c) of the resources between Horizon Cloud and Workspace ONE, along with desktop entitlements. The VMware Identity Manager Connector then synchronizes the resources and entitlements to the IDM Cloud service (d).

Figure 8: Integration 3: Horizon Cloud On Premises and Workspace ONE Cloud

Tips on How to Integrate

To integrate Horizon Cloud with Workspace ONE, you deploy VMware Identity Manager or VMware Identity Manager Connector on-premises with one of the Horizon Cloud Service options described earlier. To start the integration, ensure that VMware Identity Manager or VMware Identity Manager Connector is configured and integrated with your Enterprise Directory.

For more information, see the VMware Horizon Cloud Service Documentation or VMware Workspace ONE Documentation.

Enable Horizon Cloud Desktops and Applications in VMware Identity Manager

With a Horizon Cloud and Workspace ONE integration, you can use the VMware Identity Manager Administration Console, a component of Workspace ONE, to enable desktops and applications.

  1. Log in to the VMware Identity Manager Administration Console.
  2. In the Catalog tab, select Manage Desktops and Applications > Horizon Cloud.
  3. Select Enable Horizon Cloud Deployments and Applications.
  4. Enter the following information for your environment:
  5. Click Save.
  6. Click Sync now to sync Desktop and App entitlements from the Horizon Cloud environment.

Configure SAML Authentication

You should configure a a SAML authentication between Horizon Cloud and VMware Identity Manager, the identity provider, to enable trust between the two. To establish trust, you first create a Federation Artifact for Horizon Cloud, then set up custom user ID mapping, and finally configure SAML authentication.

Create Federation Artifact for Horizon Cloud

To enable trust between Horizon Cloud and VMware Identity Manager, you create the Federation Artifact in the VMware Identity Manager Administration Console and add a SAML authentication in the Horizon Cloud Administration Console.

  1. In the VMware Identity Manager Administration Console, click the arrow on the Catalog tab and select Settings.
  2. In the left pane, select Horizon Cloud.
  3. Enter the following information for your Horizon Cloud environment:
  4. Click the Accept Certificate link next to the Tenant Appliance URLs.
  5. Click Save.

After creating a federation artifact, set the custom User ID mapping.

Custom User ID Mapping

You can use custom User ID Mapping to customize the user ID that is used in the SAML response when users launch Horizon Cloud Desktops and Applications. You can resolve SSO launch failures that are caused by a mismatch of the user ID attribute between VMware Identity Manager and Horizon Cloud.

  1. In the VMware Identity Manager Administration Console, click the arrow on the Catalog tab and select Settings.
  2. Click Horizon Cloud on the left.
  3. In the Horizon Cloud page, specify the name ID format to use.
  4. Click Save.

After setting the custom User ID mapping, configure the SAML authentication.

Configure SAML Authentication in Horizon Cloud

To configure SAML authentication in Horizon Cloud:

  1. In the VMware Identity Manager Administration Console, click the arrow on the Catalog tab and select Settings.
  2. In the left pane, click SAML Metadata.
  3. Click the Identity Provider (iDP) metadata link.
  4. Make a note of the URL from the browser&#rsquo;s address bar, such as https://VMwareIdentityMangerFQDN/SAAS/API/1.0/GET/metadata/idp.xml
  5. Log in to the Horizon Cloud Tenant.
  6. Navigate to Settings > General Settings > Edit.
  7. In the VMware Identity Manager section, enter the following required information:
  8. Click Save.

Enforce User Authentication through Workspace ONE Portal

You can set Horizon Cloud to enforce end user authentication through the Workspace ONE portal, requiring SAML-based authentication.

Figure 13: Enforcing User Authentication

  1. In the Administration Console, navigate to Settings > General Settings, and click Edit.
  2. In the User Account Configuration section, make selections according to your organization’s needs.
    • Force Remote Users to vIDM – When set to Yes, users that are trying to access their desktops from locations outside of your corporate network must log in to their Workspace ONE portal and access desktops and applications from that portal.
    • Force Internal Users to vIDM – When set to Yes, users that are trying to access their desktops from locations within your corporate network must log in to their Workspace ONE portal and access desktops and applications from that portal.
  3. Click Save to confirm the configuration to the system.

After you verify that user authentication is enforced, your users can launch desktops and applications securely from Workspace ONE.

Launch a Desktop or Application using Horizon Client or Supported Browser

Your end users can use either the Horizon Client or any supported HTML 5 browser to launch desktops and applications.

  1. In the Workspace ONE portal, click Bookmarks
  2. Double-click the desktop or application to launch.

To Wrap this up….

Step-by-step documentation on how to integrate Horizon Cloud with VMware Identity Manager can be found in the VMware Horizon Cloud Service Documentation and VMware Workspace ONE Documentation. If you want to try configuring the integration yourself, but do not have a Horizon Cloud or Workspace ONE environment yet, you are in luck. At VMworld, we are releasing a Hands-on-Labs for Horizon Cloud, which contains an entire module that walks you through the configuration of the integration. Make sure to check out HOL-1856-ADV-1 in the Hands-on-Labs at VMworld in Las Vegas!

 

The post Delivering a Seamless Digital Workspace Experience with Horizon Cloud appeared first on VMware End-User Computing Blog.

Read more..

Easy as 9.1.1-2-3: VMware AirWatch EMM Feature Pack Review

Use the VMware AirWatch EMM feature pack review to learn about the added features added and bug fixes in the latest releases of the AirWatch Console.

VMware AirWatch EMM Feature Pack v9.1.3

Check out the latest features in theVMware AirWatch EMM Feature Pack v9.1.3 release!

New!Deploy Custom Bootstrap Packages for macOS

VMware AirWatch EMM Feature Packv9.1.2

The post Easy as 9.1.1-2-3: VMware AirWatch EMM Feature Pack Review appeared first on VMware End-User Computing Blog.

Read more..

Best Practices for Published Applications and Desktops in VMware Horizon Apps and VMware Horizon 7

The best practices guide for published applications and desktops in Horizon 7 and Horizon Apps is now available!

This guide is intended for anyone installing or administering published applications or published desktops in Horizon 7 or Horizon Apps. Readers should already be familiar with basic installation and administration procedures, such as those described in Publishing Applications with VMware Horizon 7.

When deploying a Horizon 7 or Horizon Apps RDSH-based published application and desktop solution, administrators will want to consider a number of best practices. Areas of consideration include VMware ESXi host sizing, RDSH image configuration and optimization, Horizon 7 configuration and policies, antivirus solutions, provisioning, and recurring maintenance.

Administrators will also want to consider integrating VMware JMP technologies, which include VMware Instant Clone Technology, VMware App Volumes, and VMware User Environment Manager. With our latest release of VMware Horizon 7, just-in-time delivery of virtual desktops is extended to include published applications delivered from RDSH servers, bringing increased speed, scale, and simplicity.

Be sure to download and read Best Practices for Published Applications and Desktops in VMware Horizon Apps and VMware Horizon 7.

To comment on this paper, contact VMware End-User-Computing Technical Marketing at euc_tech_content_.

The post Best Practices for Published Applications and Desktops in VMware Horizon Apps and VMware Horizon 7 appeared first on VMware End-User Computing Blog.

Read more..

Symantec VIP Authentication for VMware Identity Manager

Do you want to integrate3rd-party identity provider functionality into theVMware Identity Manager authentication workflow? Then you are in luck! Today’s post explains how toenable Symantec VIP authentication for VMware Identity Manager access.

Symantec VIP Authentication for VMware Identity Manager

VMware Identity Manager is an Identity as a Service (IDaaS) product offered by VMware. Since it is a stand-alone product, it does not require 3rd-party integrations to authenticate end users. However, integrating a 3rd-party authentication solution with VMware Identity Manager might make sense or be necessary in certain cases. That’s where Symantec Validation and Identity Protection (VIP), a centralized site for managing user credentials, comes into the picture. IntegrateSymantec VIPwith VMware Identity Manager to implement single or multi-factor authentication into vIDM via Symantec VIP.

Symantec VIP Authentication for VMware Identity Manager Workflows

Prior to attemptingintegration, it makes sense to review the configuration options. Since there are multiple ways to integrateSymantec VIP withVMware Identity Manager, this post explainstwo common options.

Single-Factor Authentication withSymantec VIP

This method uses Symantec VIP as the onlyauthentication factor for accessing the VMware Identity Managerportal and itsapplications.

The workflow begins when an end-user first opens the VMware Identity Manager portal. VMware Identity Manager redirects the end userto Symantec VIP, which challenges the user for their credentials. Theend user then provides their credentials which Symantec VIP validates. Post-validation, Symantec VIP redirects the end user to tothe VMware Identity Manager portal. Once connectedto the portal, end users access any managed application through single-sign on.

Multi-Factor Authentication withSymantec VIP

This method uses Symantec VIP as the second authentication factor for accessing the VMware Identity Managerportal or specific applications.Multi-factor authentication is ideal for organizations withcomplex security requirements.

The workflow begins when an end-user first opens the VMware Identity Manager portal. VMware Identity Manager then challenges the user for their credentials. In response to the challenge, theend user provides their credentials. Then, after validating the credentials, VMware Identity Manager redirects the end user to Symantec VIP with a SAML request. Since the SAML request contains aNameID, Symantec VIP uses the NameID to issue an authentication challenge. The end user then responds to the challenge, and Symantec VIP validates their response. Once authentication completes, the end-user redirects to the VMware Identity Manager portal. End users can now access any managed application from the portal through single-sign on.

Want to see the workflow in action? Then check out this VMware Identity Manager + Symantec VIPdemo.

Integrate Symantec VIP Authentication for VMware Identity Manager

Once you’ve reviewedthe available workflows, determine if you want to use Symantec VIP for single or multi-factor authentication. Once decided, you’re ready to begin integration! Complete the following steps to get started.

1. Obtain the VMware Identity Manager Service Provider Metadata

  1. Open the VMware Identity Manager Administrative Console.
  2. Navigate to Catalog > Settings.
  3. From the menuon the left, select SAML Metadata.
  4. On the Download SAML Certificate window, click Service Provider(SP) Metadata.
  5. Save the file as sp.xml.

2. Download the VMware Identity Manager Signing Certificate

  1. Open the VMware Identity Manager Administrative Console.
  2. Navigate to Catalog > Settings.
  3. From themenuon the left, selectSAML Metadata.
  4. On the Download SAML Certificate window, click Download.
  5. Save the file as signingCertificate.cer.

3. Configure Symantec VIP Login

  1. Open the VIP Manager Administrative Console.
  2. Navigate to Policies > VIP Login > Edit.
  3. Next to Import Metadata File, click Choose File.
  4. Select sp.xml.
  5. Next to Verification Certificate, click Choose File.
  6. Select signingCertificate.cer.
  7. Click Save.

4. If Configuring Single-Factor Symantec VIP Authentication, Enable VIP PIN and Set a PIN code.

  1. Open Symantec VIP.
  2. Navigate toPolicies> Account >Edit.
  3. Configure the VIP PIN policy settings.
    • Require a minimum number of characters.
    • Set character requirements.
    • Configure anexpiration date for the PIN.
    • Set the number of unique PINs required before the user can reuse a PIN.

5. Download Symantec VIP Metadata

    1. Open Symantec VIP.
    2. Navigate to Policies > VIP Login.
    3. Configure single or multi-factor Symantec VIP Authentication for VMware Identity Manager:
      • VIP Login Idp (Second Factor Only) -Download metadata xmlto enable multi-factor authentication with Symantec VIP.
      • VIP Login Idp (First and Second Factor) -Download metadata xmlto enable single-factor authentication with Symantec VIP.

6. Add Symantec VIP as a 3rd-party IDP in VMware Identity Manager

    1. Open the VMware Identity Manager Administrative Console.
    2. Navigate to Identity & Access Management > Manage > Identity Providers > Add Identity Provider.
    3. Complete the fields to add an identity provider:
      • Identity Provider Metadata -Copy the SAML metadata from the file saved in Step 5
      • Name ID Format - Appears asurn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.
      • Name ID Value- Select according to your environment.
      • Name ID Policyin SAML Request - Appears as urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.
      • Authentication Method - Select urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport.

7. Define Policy and Policy Rule

Define the policy and policy rule for single or multi-factor Symantec VIP Authentication.

  • Single-factor -Set the first authenticator in the authentication chain to the defined authentication policy.
  • Multi-factor -Set the second authenticator in the authentication chain to the defined authentication policy.

To learn more about configuring policies, refer to the chapter Managing Access Policiesin the VMware Identity Management Admin Guide.

Learn More

  • VMware Identity Manager Documentation
  • VIP Policy Configuration

The post Symantec VIP Authentication for VMware Identity Manager appeared first on VMware End-User Computing Blog.

Read more..

Horizon Cloud Service with Hosted Infrastructure – July 2017 Technical Updates

There are several technical updates to the VMware Horizon Cloud Service with Hosted Infrastructure this quarter. The updates for this release focus on expanding capabilities from the initial release in February. VMware will contact all customers individually to schedule the upgrade of their tenant(s) to the new release (17.1). For more details on this release, see the Horizon Cloud with Hosted Infrastructure 17.1 Release Notes.

New Data Center Availability Added!

VMware is continuing its partnership with IBM to bring VMware Horizon Cloud Service to more regions. Since Februrary, we have added capabilities to host Horizon Cloud in the United Kingdom (May), Germany (June) and in California (July). We now have three data centers in the U.S., one in Japan, and two in Europe. The Horizon Cloud team will continueto add more data centers in the next few months. Stay tuned!

Native Applications with App Volumes Technology Is Generally Available

In February, we enabled a few select customers to use VMware App Volumes technology to create and leverage AppStacks in Horizon Cloud. This feature is now generally available to any customer who requests it. Note that add-on storage is required to use this feature. If you are a HorizonCloud customer and would like to use Native Applications powered by App Volumes technology, consult with your VMware sales team.

Smart Policies Support

You can now leverage Smart Policies in Horizon Cloud. Smart Policies allow you to have fine-grain control over a user&#rsquo;s desktop experience. You can dynamically enable, disable, or control access to user features in Horizon Cloud based on who the user is, and how they are accessing Horizon Cloud. Smart Policies were released as an integration between VMwareHorizon 7 and VMware User Environment Manager in 2016.

For example, with Smart Policies, an administrator can decide to disable access to USB devices or to cut-and-paste from within the Horizon Client if a user is attempting to access the HorizonCloud environment from an untrusted or external network. You can also dynamically control display-protocol configurations based on the type of device that is being used.

Smart Policies in Horizon Cloud work the same as they do in Horizon 7. VMware Senior Product Line Manager Aaron Black wrote an excellent blog post pointing out some great use cases for Smart Policies. If you want to try out Smart Policies in your Horizon Cloud deployment, download the Reviewers Guide for View in VMware Horizon 7: Smart Policies.

Windows Server 2016 Support

Horizon Cloud continues to provide support for customers wanting to use the latest editions of Windows operating systems. With this release, Horizon Cloud with Hosted Infrastructure now supports Windows Server 2016 for RDSH hosts and for skinned Windows Server based virtual desktops. For full details on OS support in Horizon Cloud with Hosted Infrastructure, see the Horizon Cloud with Hosted Infrastructure Service Description document, which can be found in the Horizon Cloud Service with Hosted Infrastructure Terms of Service page.

Horizon Virtualization Pack for Skype for Business Support

Full support for the Horizon® Virtualization Pack for Skype for Business isreleased for Windows clientswith Horizon Cloud. This solution enables customers to use Skype for Business within Horizon desktops to make optimized audio-video calls and telephony features using the native Skype client. Please note that this functionality is only available on VDI desktops today, but will be made available on RDSH desktops / apps in the future. Details on what features are supported with this release can be found in the release notes for Horizon 7.2.

Enhanced Troubleshooting Capabilities through Console Access (BETA)

We have added more troubleshooting features to the Horizon Air Console Access - HACA tool. HACA, which is currently in Beta,gives administrators direct access to individual desktop consoles for troubleshooting purposes. The tool has been enhanced to allow administratorsthe abilitytotroubleshootvirtual machines that get stuck during the Windows OS startup process, before the Horizon Agent starts.

Horizon Agent 7.2 / Client 4.5 Support

Horizon Cloud with Hosted Infrastructure supports the latest Horizon clients and agents. Organizations can take advantage of new feature enhancements in the latest clients including enhanced security with Blast Extreme with support of SHA-256 encryption. You can download the latest clients from the Horizon Clientdownload page.

The post Horizon Cloud Service with Hosted Infrastructure - July 2017 Technical Updates appeared first on VMware End-User Computing Blog.

Read more..

Updated VMware App Volumes 2.12 Technical FAQ Now Available

We are excited to announce that the VMware App Volumes Technical FAQ has been updated for VMware App Volumes 2.12. The latest release includes many capabilities and features that improve the end-user experience.

Here are some of the feature details included in the updated document:

  • App Volumes 2.12 supports multiple Active Directory domains with one-way and two-way trusts.You can also move an Active Directory user to another OU or rename an Active Directory user without impacting AppStack or writable volume assignments.
  • With App Volumes 2.12, we have added certificate checking between the AppVolumes Manager and App Volumes Agents, and vCenter Server.
  • You can upgrade from App Volumes 2.12 to App Volumes 2.12.1 without uninstalling the existing 2.12 installation. Configurations and settings are preserved.
  • App Volumes 2.12 supports Windows 10 Anniversary Update and Microsoft Office365 version 2016.

We have even referenced additional VMware knowledge base articles such as:

  • Installing and using Microsoft Office Products with VMware App Volumes 2.x (2146035)
  • Windows 10 support for App Volumes 2.12 (2148177)
  • Supported Scenarios for delivering Visual Studio when using Horizon View and AppVolumes (2149369)

For these details and more, download the updated VMware App Volumes Technical FAQ.

The post Updated VMware App Volumes 2.12 Technical FAQ Now Available appeared first on VMware End-User Computing Blog.

Read more..

Updated VMware App Volumes 2.12 Technical FAQ Now Available

We are excited to announce that the VMware App Volumes Technical FAQ has been updated for VMware App Volumes 2.12. The latest release includes many capabilities and features that improve the end-user experience.

Here are some of the feature details included in the updated document:

  • App Volumes 2.12 supports multiple Active Directory domains with one-way and two-way trusts.You can also move an Active Directory user to another OU or rename an Active Directory user without impacting AppStack or writable volume assignments.
  • With App Volumes 2.12, we have added certificate checking between the AppVolumes Manager and App Volumes Agents, and vCenter Server.
  • You can upgrade from App Volumes 2.12 to App Volumes 2.12.1 without uninstalling the existing 2.12 installation. Configurations and settings are preserved.
  • App Volumes 2.12 supports Windows 10 Anniversary Update and Microsoft Office365 version 2016.

We have even referenced additional VMware knowledge base articles such as:

  • Installing and using Microsoft Office Products with VMware App Volumes 2.x (2146035)
  • Windows 10 support for App Volumes 2.12 (2148177)
  • Supported Scenarios for delivering Visual Studio when using Horizon View and AppVolumes (2149369)

For these details and more, download the updated VMware App Volumes Technical FAQ.

The post Updated VMware App Volumes 2.12 Technical FAQ Now Available appeared first on VMware End-User Computing Blog.

Read more..

What’s New in VMware Horizon 7.2 and Horizon Client 4.5

We have just announced the general availability of VMware Horizon 7.2 and Horizon Client 4.5. This is a significant release for our flagship product, with improvements across the board—from scalability and user experience to deep technical innovations and improved policy controls. Let us dive straight in and highlight the key technical advances this release delivers.

Horizon 7.2

What&#rsquo;s New Highlights

Horizon Help Desk Tool
  • Provides user-session details for the Horizon 7 environment.
  • Single console for troubleshooting and solving user issues.
Workspace ONE mode
  • Forces using Workspace ONE when the client supports it.
  • Optionally blocks clients that do not support it.
Reuse AD account for instant-clone pool
  • Create a new computer account only if it does not exist.
Graphics settings from snapshot
  • SVGA settings / vGPU profile from master snapshot.
ADM template removal
  • Only ADMX in 7.2.
Increased scale
  • Pod , Cloud Pod Architecture, and Connection Server.
Storage improvements
  • Storage DRS cluster, storage policy-based management, encryption, local storage.

Horizon Help Desk Tool

The Horizon Help Desk Tool provides a tailored troubleshooting interface for the help desk that is installed by default on the Connection Servers. To access the Horizon Help Desk Tool, navigate to https:///helpdesk, where CS_FQDN is the fully qualified domain name of the Connection Server, or click the Help Desk button in the Horizon Administrator console.

The Horizon Help Desk Tool reduces workload for administrators and provides quick troubleshooting and metrics for the help desk.

The tool allows help desk staff to easily perform the following tasks on the user machine:

  • Restart, Logoff, Reset, and Disconnect
  • Remote Assistance
  • Send Message

You can obtain the following metrics for the client and virtual machine:

  • Client
    • Username
    • Client IP, Name, and OS
    • Protocol, TX Bandwidth, and Frame Rate
  • VM
    • Computer Name
    • Agent Version
    • Session State and State Duration, Logon Time and Duration, and Session Duration
    • CPU, Memory, Latency, and Logon Segments
    • Connection Server
    • Pool
    • vCenter

To get logon segments in the help-desk feature, you need to enable timingProfiler writes to the event database on each Connection Server:

vdmadmin -I -timingProfiler -enable

For detailed information on the Horizon Help Desk Tool, see the VMware blog post Help&#rsquo;s on the Way with the New VMware Horizon Help Desk Tool.

Watch this quick demo of the Horizon Help Desk Tool to see it in action:

Workspace ONE Mode

Workspace ONE mode secures access to Horizon 7 by allowing applications and desktops to launch only from Workspace ONE. This setting enforces access policies per application or per desktop. You enable Workspace ONE mode on the Connection Servers. When a user connects to a Workspace ONE mode-enabled server in Horizon Client, they are redirected to the Workspace ONE portal to launch desktops or applications, and the Horizon Client will no longer show other items that are available to launch. You also have the option to disable clients that do not support Workspace ONE mode.

See Workspace ONE mode in action in this short demo:

Reuse AD Account for Instant-Clone Pool

You can now rebuild a virtual machine in an instant clone and keep all machine assignments by reusing the computer account.

Graphics Settings from Snapshot

Instant-clone desktop pools inherit graphics settings from the vCenter Server parent-VM snapshot:

  • Memory
  • Number of monitors (with a new maximum of four)
  • Resolution

Just as with the SVGA settings, the vGPU profile for an instant-clone desktop pool is automatically selected when you select the snapshot of the vCenter Server parent VM.

All Active Directory Group Policy Templates Are Available as ADMX

All policy settings have been migrated to ADMX, and ADM is now deprecated and no longer included with Horizon 7. With all settings now in the ADMX templates, managing Horizon 7 is more streamlined and simpler than ever because now all templates can be placed in a central store, and no redundant copies need to be made into Sysvol.

Scalability

Horizon 7.2 increases scalability for Cloud Pod Architecture deployments to now support up to 120,000 sessions across 12 View pods and five sites. Additionally, Horizon 7 can now support 4,000 desktops with a single VMware vCenter Server for linked-clone, full-clone and instant-clone deployments.

Local Storage Support for Instant Clones

You now have the option to use local storage as a low-cost storage tier for instant clones. However, for high-availability events, this requires careful pool capacity planning and adds complexity to vSphere host maintenance, which you would not have with vSAN.

Ability to Select Storage DRS Clusters for Full Clones

It is no longer required to select all storage devices belonging to a Storage DRS Cluster; you can now directly select the cluster for easier administration.

vSAN and Storage Policy-Based Management Improvements

Horizon 7.2 adds support for vSAN encryption and provides updated storage policy-based management for finer granularity.

Horizon Agent 7.2 for RDSH

What&#rsquo;s New Highlights

Smart Policies for applications
  • Extend support from desktop to remote applications.
Session pre-launch
  • Launch application on broker login.
  • Can be enabled per application.

Smart Policies for Applications

Smart Policies give administrators granular control of a user&#rsquo;s desktop experience. You can dynamically control a variety of Horizon 7 features based on user, device, and location. Horizon 7.2 now introduces Smart Policies for RDSH applications. Smart Policies for applications, together with tags, can control the behavior of published applications.

Following are client properties mapped to User Environment Manager properties:

Volatile Registry Key User Environment Manager Property Value
viewClient_Broker_GatewayLocation Client location Internal/External
viewClient_Launch_Matched_Tags Launch tag(s) Tags (comma)
viewClient_Launch_ID Pool name Pool ID

Edit the Connection Server settings to add a tag for a desktop pool. The tag can be any string value, for example, Internal or External.

Then, from User Environment Manager, create a Smart Policy and reference the tag name.

Or if you want this policy to apply only to specific applications, you can make the condition more specific, for example, only for applications that have Secure in their pool name:

But remember that the pool name that launched the session is evaluated at user-session launch time, so you cannot differentiate between applications on the same farm. If you want to differentiate, separate the applications with nonmatching settings into different farms and use OR to add all the applications to the conditions.

Session Pre-Launch

Administrators can configure a published application so that an application and remote desktop session are launched immediately after a user has authenticated to the Connection Server. When the user starts the session from Horizon Client, the session loads almost instantly. The pre-launch setting enables faster start times for frequently used applications. From the Horizon 7 Administrator console, you can configure pre-launch, as follows:

It is recommended to enable this option only for applications that the user will almost certainly use immediately after launching, to minimize unnecessary load on the farm. To further reduce impact, you can set a timeout for unused pre-launched applications, as follows:

To minimize impact even further, you can set a reasonable maximum amount of users, as determined by testing on the RDSH servers, and configure session load-balancing based on CPU and memory load, leaving enough headroom for boot storms.

For more information, see Configuring Load Balancing for RDS Hosts in View Administration.

Horizon Agent 7.2

What&#rsquo;s New Highlights

Recursive Unlock
  • Single unlock of the client device also unlocks the virtual desktop or published desktop.
USB over virtual channel
  • USB-redirection port consolidation.
HTML5 content redirection (beta)
  • Redirect HTML5 from agent to client.
Blast Extreme SHA-256
  • Upgraded to use the latest security algorithms.
Horizon Agent DX11
  • Complete rewrite of the D3D9 renderer.
Skype for Business GA
  • General availability.

Recursive Unlock

The Recursive Unlock feature unlocks all remote sessions after the client machine has been unlocked. After the user logs in to the server, remote sessions such as published applications, RDSH desktops, and Windows desktops are unlocked. This feature removes unnecessary authentication steps for the user.

Requirements for this feature include:

  • The Windows client device must be domain-joined
  • The user logging in to the client must be the same user logged in to the remote session
  • Enable the client setting Log in as current user
  • Enable the Group Policy setting Unlock remote sessions when the client machine is unlocked in ComputerPoliciesVMware Horizon Client ConfigurationSecurity.

USB over Virtual Channel

You can enable USB redirection without opening the firewall port 32111. USB over virtual channel allows USB over a side channel.

Configure this registry setting as follows:

  • Key path: HKEY_LOCAL_MACHINESOFTWAREVMware, Inc.VMware VDMAgentConfiguration
  • Key name: UsbVirtualChannelEnabled
  • Key value: true

HTML5 Redirection (Tech Preview)

The HTML5 redirection feature allows video content redirection for websites that do not use Adobe Flash Player. Benefits of this feature include reduced CPU usage and smoother video playback.

HTML5 redirection requires:

  • Windows 7 or Windows 10 Enterprise for the agent and client OS, with VMware Horizon 7 HTML5 redirection package (available by request)
  • Google Chrome 58 with extension, from Chrome Web Store
  • Setting URL lists in the registry, for example:

[HKEY_LOCAL_MACHINESOFTWAREPoliciesVMware, Inc.VMware HTML5MMR]

"enabled"=dword:00000001

[HKEY_LOCAL_MACHINESOFTWAREPoliciesVMware, Inc.VMware HTML5MMRUrlWhiteList]

"https://vimeo.com/*"=""

"https://www.youtube.com/*"=""

Note: Tech Preview features and capabilities arenot supported for production deployment. These features are available to test in a lab or UAT environment as a preview of potential upcoming innovations. You can provide feedback to improve these features throughVMware Communities.

Horizon Virtualization Pack for Skype for Business

Optimized audio and video calls are now possible with Skype for Business inside a virtual desktop without negatively affecting the virtual infrastructure and overloading the network. All media processing takes place on the client machine instead of in the virtual desktop during Skype audio and video calls. Using native Skype codecs, bandwidth usage is equivalent to native Skype for Business calls.

For detailed information on this feature, which is now generally available, see the VMware blog post VMware Horizon Virtualization Pack for Skype for Business (Beta) Is Now Available!.

Horizon Client 4.5

The Horizon Client has been updated, too, with availability of an XBox One Client in the Windows store, a new installer UI for Windows, dual-monitor support for HTML Access, SSO for RHEL/CentOS 7.x, and KDE and CDR support for Linux.

What&#rsquo;s New Highlights

For more information, see the Release Notes on the Horizon Clients Documentation page.

With all these great additions, it is easy to see why we are so excited about this release. We invite you to see it all yourself by visiting the Horizon 7.2 download page and the Horizon Clients download page.

 

The post What&#rsquo;s New in VMware Horizon 7.2 and Horizon Client 4.5 appeared first on VMware End-User Computing Blog.

Read more..

Announcing the Introduction to VMware Horizon 7 for Citrix Administrators

We are excited to announce the Introduction to VMware Horizon 7 for Citrix Administrators white paper. This guide is for Citrix administrators or anyone with a Citrix background who wants to learn about VMware Horizon 7. It offers a tour of Horizon 7, how the Citrix components map to a Horizon 7 deployment, and the steps to get you started in evaluating Horizon 7.

This guide covers some of the recent advances in Horizon 7, as well as how VMware JMP technologies deliver an enterprise-class, innovative solution. We also detail the key areas where Horizon 7 delivers a modern, enterprise-secure, and consumer-simple virtual desktop and application solution:

  • Enterprise-class application-publishing and virtual-desktop solution
  • Simple, fast, efficient management at scale
  • Consistent, adaptive user experience
  • Flexible, robust security

Did you know that Citrix XenApp and XenDesktop are very similar in architecture to VMware Horizon 7? Both solutions use a combination of connection brokers, web-based application catalogs, and RDSH or VDI servers to securely deliver virtual desktops and applications.

The following diagram compares the major Citrix XenApp and XenDesktop components to those of VMware Horizon 7.

For details on this diagram and more, download the Introduction to VMware Horizon 7 for Citrix Administrators now.

The post Announcing the Introduction to VMware Horizon 7 for Citrix Administrators appeared first on VMware End-User Computing Blog.

Read more..

VMware AirWatch 101: Honeywell Dolphin CT50 Bar Code Enrollment

The bar code enrollment workflow simplifiesenrollment intoVMware AirWatchfor Honeywell Dolphin CT50 devices. While Android Lollipop devices support bar code enrollment, Android Marshmallow devices require slightly different AirWatch Console configurations to enable this workflow. Today’s post covers the configurations and bar code enrollment workflow for Honeywell Dolphin CT50devices on Android Marshmallow.

Honeywell Dolphin CT50 Bar Code Enrollment

In the following workflow, the EZConfig Editor (designed for the Windows OS on a PC) produces two sets of bar codes. The first contains the information required to establish a Wi-Fi configuration on the Honeywell CT50. The second set contains the information to enroll the Honeywell CT50 into VMware AirWatch.The bar codes are presented from within the EZConfig Editor application directly on the PC display. Then, use the EZConfig for Scanning utility on a Honeywell CT50 deviceto scan the bar codes.

Download and Install the EZConfig Editor

The first step in the workflow is to install the EZConfig Editor. Later, you’ll use the EZConfig Editor tocreate bar codes thatestablish Wi-Fi settings and enroll devices into VMware AirWatch.

1. From your Windows PC, click the Honeywell Sensing and Productivity Solutions link.

2. Click the Software tab. Under Tools and Utilities, click the Honeywell EZConfig for Mobility Setup r411The file version number may vary depending on the update schedule from Honeywell. link and download the associated ZIP file.

3. Unzip the file, and run the setup.exe file.

4. When complete, the EZConfig Editor window appears on the PC.

Check the Honeywell CT50 for the Power Tools Application

After installing the EZConfig Editor, confirm that the correct version of the Power Tools Application installed on the device.

  1. On the Honeywell CT50 apps screen, look for the Power Tools icon.
  2. If not present, proceed to the section: Download and Install the Power Tools Application on the Honeywell CT50.
  3. If present, selectPower Tools > Diagnostic Information > About and check the version number.
  4. If the Power Tools version is lower than4.01.00.3791, proceed to thesectionDownload and Install the Power Tools Application on the Honeywell CT50.
  5. If the Power Tools version is 4.01.00.3791 or higher, proceed to the section: Use the EZConfig Editor to Establish Honeywell CT50 Wi-Fi Settings.

Download and Install the Power Tools Application on the Honeywell CT50

Take corrective action if you discovered the Power Tools application was not installed, or was running the wrong version. Simply download and install the Power Tools application suite.

1. Open the Honeywell Sensing and Productivity Solutionspage in your browser.

2. Under the Tools and Utilities section, click the Software tab, and download the Honeywell_CommonES_Android_3.15.3150.zip ZIP fileThe file version number may vary depending on the update schedule from Honeywell..

3. Once download completes, establish a USB connection between your PC and the Honeywell CT50.

4. On the Honeywell CT50&#rsquo;s internal storage card, copy the file to the /Honeywell/autoinstall folder.

5. On the Honeywell CT50, hold down the power button and select Reboot to trigger the application’s installation.

6. After installation successfully completes, click the Power Tools app to access the EZConfig for Scanning utility.

Use the EZConfig Editor to Establish Honeywell CT50 Wi-Fi Settings

After installing the software necessary for barcode enrollment, establish Honeywell CT50 Wi-Fi settings using the EZConfig Editor.

1. Establish a USB connection between your PC and the Honeywell CT50

2. From the Honeywell CT50 upload the DeviceConfig.xml file to the PC.

2. In the EZConfig Editor, navigate toFile > Open >Internal Storage > Honeywell > ezconfig > generatedAdd a Tooltip Text.

3. Select the DeviceConfig.xml file, and click Open.

4. Select DeviceConfig > Connection Settings > Radio Manager > Supplicant > Profile 1, and enter the valuesField values are described in the Key: PSK panel. to modify the Wi-Fi settings in the DeviceConfig.xml file.

5. Select File > Save As, and save the settings to an EXM file for future use. You can give the file a unique name, specific to your own requirements.

6. In the EZConfig Editor, select File > Create EZConfig Bar Code.

7. In the EZConfig Bar Code window, reviewthe resulting bar code.

7. On the Honeywell CT50, selectPower Tools > EZConfig for Scanning utility andscan the bar code.

Note:

After establishing a Wi-FiIf scanning multiple barcodes, the Wi-Fi connection may not establish. In this instance, reboot the Honeywell CT50 to establish the connection. connectionfor the Honeywell CT50,create access to files for VMware AirWatch enrollment.

Creating Access to Files for VMware AirWatch Enrollment

Return tothe EZConfig Editor, and establish access to the files used for VMware AirWatch enrollment:

1. Openyour browser, and log into the VMware AirWatch Console. Navigate toDevices > Staging & Provisioning > Staging, and click Add to create an Android Staging Package.

2. In the Staging window, enter the desired Enrollment User and Password credentials, and leave the Manifest tab empty.

3. In the upper-right corner of the Staging window, click the down arrow, and select Sideload Staging.

4. In the Generate Sideload Staging Package window, click the Organization Group field and select a group to configure device assignment. Leavethe Universal check box deselected.

5. Click Download to download the Sideload Staging ZIP file to your PC, and save the file to a convenient location.

6. On your PC, locate and unzip the file, and open the enrollment folder.

7. From the enrollment folder, upload the credentials.bin file to a file repository accessible to the Honeywell CT50. Take note of the path for future configuration within the EZConfig Editor.

8. From the VMware AirWatch Resources Portal, upload the latest VMware AirWatch Android Agent to the same file repository to be accessed by the Honeywell CT50. Again, take note of the path for future configuration within the EZConfig Editor.

Note: If you cannot access the VMware AirWatch Android Agent, request access from the VMware AirWatch Support Team via a Help Desk Ticket.

9. From the VMware AirWatch Resources Portal, upload the latest Honeywell Services APK file to the same file repository to be accessed by the device. Again, take note of the path for future configuration within the EZConfig Editor.

Note: If you cannot access the Honeywell Services APK file, request access from the VMware AirWatch Support Team via a Help Desk Ticket.

You have finished creating access to files for VMware AirWatch enrollment. The next step is to establish settings for VMware AirWatch enrollment in the EZConfig Editor on the PC.

Configure the EZConfig Editor for VMware AirWatch Enrollment

After creating file access for enrollment, establish settings for VMware AirWatch enrollment in the EZConfig Editor on the PC.

1. Download the Provisioner_bin.exm file toyour PC tomodify it within the EZConfig Editor.

2. In the EZConfig Editor, locatethe provisioner_bin.exm file.

3. Select File > Open to choose and open the file and see its Task folders.

4. In the first Task folder of the EZConfig Editor, modify the Value field entry to make the credentials.bin file available for enrollment.

  • Source – Repository link to the .bin file with a/ format. For example:<link>/credentials.bin
  • Action – Contains the action commandInstallFile.
  • Destination – Storage location on the device.For example:/sdcard/credentials.bin

5. In the second Task folder, modify the Value field entry to install the Honeywell Services