2. • This presentation may contain product features that are currently under development.
• This overview of new technology represents no commitment from VMware to deliver these
features in any generally available product.
• Features are subject to change, and must not be included in contracts, purchase orders, or
sales agreements of any kind.
• Technical feasibility and market demand will affect final delivery.
• Pricing and packaging for any new technologies or features discussed or presented have not
been determined.
Disclaimer
CONFIDENTIAL 2
4. AirWatch Mobile:
• A Leader for 5 Consecutive Years
• Placed Highest on Ability to
Execute Axis 3 Consecutive Years
Magic Quadrant
Figure. Magic Quadrant for Enterprise Mobility Management Suites
Source: Gartner, Inc., Magic Quadrant for Enterprise Mobility Management Suites, Terrence Cosgrove, et al, June 8 2015. &
Gartner, Inc., 2015 Critical Capabilities for Enterprise Mobility Management Suites, Terrence Cosgrove, et al, June 9 2015.
This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of
the entire document. The Gartner document is available upon request from AirWatch.
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise
technology users to select only those vendors with the highest ratings or other designation. Gartner research publications
consist of the opinions of Gartner¹s research organization and should not be construed as statements of fact. Gartner
disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or
fitness for a particular purpose.
CONFIDENTIAL 4
5. Horizon Desktop:
VMware leaps past the competition
“VMware's position reflects the company's market
position and commitment to providing resources to
expand its EUC product portfolio and infrastructure.”
CONFIDENTIAL 5
7. Horizon 6.2 Platform New Features
View Composer for RDSH Hosts
RDSH Feature Enhancements
Cloud Pod Architecture Enhancements
FIPS / Common Criteria
vDGA for AMD Hardware
One Way AD Trusts
Streamlined Pool Creation
Enhanced Licensing Information
8. 8
View Composer for RDSH Farms
Extend the functionality of View Composer
Linked Clones to RDS Hosts
Automate build-out of RDSH Farms
Single Image Management
Storage savings
OS, Patch, and Application Consistency
Simplified deployment
Master RDSH
VM
Datastore
Replica
Benefits
Overview
Linked Clones
9. Datastore 1
Linked Clones in Action
1
Master RDSH
VM
2
Replica 1
1
C Drive
Datastore 2
3
4
Replica 1
Read-
only
10. View Composer - Provisioning
20GB
Provisioning VMs with Traditional Clones
2TB SAN
Provisioning VMs with View Composer
20GB
2GB RAM
20GB
x =
+
100 Linked Clones
5GB
+
540GB SAN
=
100 VMs
20GB
Replica
11. View Composer for RDSH Farms
11
New Automated Option in Add an
RDSH Farm Wizard
Naming Pattern – like Composer for
desktops
Minimum servers available during
recompose can be set
Supports Sysprep and using a
customization specification
12. Linked Clone Feature Comparison
CONFIDENTIAL 12
Feature VDI RDSH
Recompose RDSH Farm Level Only
Rebalance
Refresh
VM Naming - Manual
VM Naming - Pattern
Sysprep
Quickprep Sysprep Only for RDSH
View Storage Accelerator (CBRC)
User Data Disk
Disposable Disk
13. Enhanced RDSH Load Balancing
13
Performance Counters
Application Anti-Affinity Rules
Better measurement of load on RDS Hosts
Use Perfmon counters to determine best host on
which to start a session
Set rules about the number of instances of an
application on a given RDS Host
Combine counter data and application instance
rules to create a better session placement
algorithm
Benefits
Better control of session placement for administrators.
Better user experience
Overview
14. RDSH Load Balancing - Perfmon-based Load Reporting
14
View Connection
Server
0
Script
View
Agent
RDS Host 1
View
Agent
RDS Host 2
View
Agent
RDS Host 3
1
3
Magnetic Sessions: A user with an existing session will re-use that session and
ignore the load balancing rules.
Script
Script
15. RDSH Load Balancing - Application Anti-Affinity
15
Stop user connections to an RDS Host running
more than the defined number of instances of an
application
Magnetic Sessions: A user with an existing session will re-use that session and
ignore Application Anti-Affinity rules.
Processed after server placement order is
calculated
If a user is attached to a desktop session the
Anti-affinity rule does not count.
16. 3D for RDS Hosted Applications
16
Enable hardware accelerated 3D support for RDS
applications in Horizon 6 v6.2
vDGA with NVIDIA
GRID vGPU with NVIDIA
Windows Server 2008 R2 and 2012 RDS Hosts
Benefits
Overview
Flexibility to provision 3D enabled RDSH
applications in Horizon 6 as well as desktops
17. 3D for RDSH Applications
17
Requires dedicated vDGA or shared GRID vGPU
NVIDIA – Check VMware Compatibility Guide
RDS Host - View Agent Installer has 3D RDSH Feature
that must be enabled
Device Manager will show VMware SVGA disabled and
NVIDIA adapter enabled
GPU-Z can be downloaded to monitor GPU activity
when 3D apps are running,
18. RDS Applications with Cloud Pod Architecture
18
Create Global entitlements to RDS applications with
Cloud Pod Architecture
Extend a user application entitlement to multiple
application pools within a datacenter, between
datacenters, or between sites
Benefits
Overview
Expand the use case for Cloud Pod Architecture to
include applications as well as desktops
Federated Horizon Pods
Pod 1
VCS 1 VCS 2
LDAP Replication
Pod 2
VCS 3 VCS 4
LDAP Replication
Global LDAP Replication
Global RDS Application
Entitlements
19. Cloud Pod Architecture – RDS Applications
Global Entitlements for RDS Applications
Works with any Horizon client that
supports CPA
Horizon Agent 3.5 or higher
20. Cloud Pod Architecture – HTML Access
20
HTML Access for Cloud Pod Architecture Desktop and Application
Global Entitlements
21. Cloud Pod Architecture – HTML Access (Cont)
21
Configure HTML Access in Global
Entitlement Policies
Requires Horizon 6.2 Connection
Server and HTML Access 3.5 or higher
Configure for each Global Entitlement
as with Desktop and Application pools
22. Horizon 6 FIPS / Common Criteria Certification
22
FIPS
FIPS Crypto for Horizon Windows Components
Common Criteria Certification in process – Targeted for
1H 2016
FIPS mode optional for customers who require it
Benefits
Overview
US Federal Government ready along with IPV6 and
CAC Smart Card capabilities
Meets demanding compliance regulations for
environments that require it.
23. vDGA with AMD Hardware
23
Support AMD Hardware for vDGA Passthrough
Provide 3D Accelerated VDI desktops on supported
hosts and AMD GPUs
Expand the hardware choices for 3D
Accelerated desktops
Benefits
Overview
24. vDGA with AMD Hardware – Technical Details
24
Supported on Specific AMD GPU Hardware
Check Hardware Compatibility Guides
Supported on Specific Server Platforms
Check Server support with AMD
vDGA Configuration similar to NVIDIA
Refer to Horizon 6 v 6.2 3D Rendering for Desktops Documentation
AMD Drivers must be installed in guest VM – leverages AMD RapidFire & ADL
APIs
Supports resolutions of 640x480 to 4096x2160
25. One Way Trust Support
25
Broker Domain
(Internal)
User Domain
(External)One Way Trust
Secondary credentials required for each admin account
to authenticate to domains with limited trust relationships
Secondary credential is a user in trusted domain that
can traverse directory
Support environments with limited trust relationships
between domains WITHOUT need for broker in external
domain
Secondary credentials stored in local LDAP database in
encrypted format.
New vdmadmin –T flag to add and manage
Secondary Credentials.
26. Child Domain Enumeration
26
Broker Domain
(Internal)
User Domain
(External)
User Child
Domain
User Child2
Domain
One Way Forest Trust
Parent-Child Trust
Parent-Child Trust
Support child domain enumeration for Child Domains of
Domains with One-Way transitive forest trusts
Broker Child
Domain
Parent-Child Trust
27. Streamlined Pool Creation
Simplifies Desktop Pool Deployment
Automated Pools only
Windows VDI Desktop Pools only
Consistent setting across Pools
New UI update
Overview
29. Horizon 6.2 Integration Features
View Composer for RDSH Hosts
Access Point Integration
vSphere 6.0 U1 Support
Virtual SAN All Flash Support
Virtual SAN Stretched Cluster Support
Enhanced VMware UEM Integration
30. Access Point – Overview
Hardened appliance for external user access –
Security Server alternative
SLES 11 Linux Appliance
Added Security & Multifactor Authentication
Pass-Through Authentication
Smart Card Support – Tech Preview
Feature Parity with Security Server
Overview
Benefits
Remove Windows VM’s from DMZ
Scale Out independent of Connection Server
Product Independence
Simplified Installation
Access Point
Appliances
Internal Network
External
Connection
Servers
Load
Balancer CS1
CS2
DMZ
Load
Balancer
31. vSphere 6 Update 1 Support
31
Horizon 6 v 6.2 certified on latest vSphere platform on
Day One
Check specific Horizon and vSphere interoperability at
VMware Product Interoperability Matrix
http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php
32. Virtual SAN All Flash Architecture
Performance with Predictable Latency
32
vSphere + Virtual SAN
…
• Flash devices used for caching as well as data
persistence
• Cost-effective all-flash 2-tier model:
o Cache is 100% write: using write-intensive, higher
grade flash devices (SSDs, PCIe, Ultra DIMM)
o Persistence tier: can leverage lower cost read-
intensive SSDs
• Up to 90K IOPS/Host
• Consistent performance with sub-millisecond
latencies
• Tested with Horizon 6 v 6.2
Virtual SAN All-Flash
Virtual SAN All-Flash Datastore
SSDs SSDs SSDs
http://www.vmware.com/files/pdf/VMware-Horizon-View-And-All-Flash-Virtual-SAN-Reference-Architecture.pdf
33. Virtual SAN Stretched Clusters Overview
33
HDDSSD HDDSSD
vSphere + Virtual SAN
Witness
VM
Site-level protection with zero data loss and near-
instantaneous recovery.
Active-Active data center
Virtual SAN cluster split across 3 fault domains
Network latency between the two main sites must be less
than 5 milliseconds RTT
Witness VM resides on a 3rd site It holds cluster metadata
Max FTT is 1
Automated failover in case of site failures
QE Tested with Horizon 6.2
<= 5 ms latency
>=10 Gbps
Requires Multi-cast
& L2
100Mbps
100ms
L3
FD1 FD2
FD3
100Mbps
100ms
L3
Overview
Benefits
Planned Maintenance
Disaster avoidance
34. Client Info at Logon– VMware UEM Integration
34
Client Information available to UEM before the user logs
on
Enables UEM to access View Client IP / Client Name
Information from Horizon Volatile Environment Variables
Client information updated on reconnect
VMware
UEM
Enables more control for UEM Dynamic Configuration
for Horizon sessions
RDS Applications
Works with VDI desktop and RDS desktops and
applications
User Logon
Dynamic Configuration
based on client info
VDI Desktops RDSH Desktops
35. CART 3.5 Features Summary
35
Client Drive Redirection for Mac
Client Drive Redirection for Linux (Tech Preview)
Encryption & Compression for Client Drive Redirection
File Type Association for RDS Applications
ThinPrint Static Printer Name Support
Windows 10 Support
OSX 10.11 “El Capitan” Support
36. CART 3.5 Features Summary
36
iOS 9 Support
Biometric Support for Mobile
Linux Desktop NVIDIA GRID vGPU Support
Linux Desktop vSGA Support
Linux Desktop Guest Logoff Automation
4K Guest Resolution Support
MS Lync (Skype for Business) Support for RDS & Windows 10
37. ClientDrive Redirection
Client Drive Redirection for VDI and RDSH
37
Easily access your local files from your Desktops and Applications
Easily access local files from VDI, RDSH Desktops
and Applications
Provide access to local, external and network drives on
the client endpoint
Supported with Windows & Mac clients
Compression & AES Encryption (SHA256)
Tech Preview – Linux clients
Benefits
Allows users to access local files on their client device
and network drives
Overview
VDI & RDSH
Local Drives
External Drives
Network Drives
RDSH Desktops &
Apps
VDI
38. Client Drive Redirection for Linux Client – Tech Preview
38
Redirect local Linux client drives to
RDSH Desktops & Applications and
Windows VDI desktops
Horizon Client 3.5 for Linux
Do not use both USB and CDR
together. CDR is preferred.
Local Drives
External Drives
Network Drives
RDSH Desktops &
Apps
Windows VDI
Does not redirect local client drives to
Linux VDI Desktops
39. Client Drive Redirection for Mac Client
39
Redirect local Mac client drives to
RDSH Desktops & Applications and
Windows VDI desktops
Horizon Client 3.5 for Mac
Do not use both USB and CDR
together. CDR is preferred.
Does not redirect local client drives to
Linux VDI Desktops
41. File Type Association - Published Apps
41
Administrator can associate file extensions to launch
an appropriate Horizon RDS Hosted application
Data Compression
SHA 256 encryption between client and session
Supported with Horizon Windows 3.5 clients only
Overview
.DOCX
.PPTX
.XLSX
.PDF
WORD
POWERPOINT
EXCEL
ACROBAT
Benefits
Simplifies Horizon RDS Hosted Application launch for
users
Seamless User experience to use local with hsoted
applications.
42. ThinPrint Static Printer Name Support
Prior to Client 3.5: ThinPrint used Printer Name
and Client ID to name the printer
This caused printing issues with applications
when users moved from end point to end point in
the same session.
Client 3.5: ThinPrint uses Printer Name only to
keep printer name consistent within session.
Client ID now stored in registry in order to
identify the correct printer.
VDI & RDSH Supported
Horizon Windows Client 3.5 and Agent 3.5
Required
43. Windows 10
43
Windows 10 Agent & Client support
for Horizon View Desktops
Smart Card Support
vSphere 5.5 U3 / vSphere 6.0
Lync / Skype for Business Support
44. Max OS X – El Capitan
44
Horizon Client 3.5 will support OSX 10.11
46. Biometric Authentication for Mobile
46
Admin defined policies
Leverages iOS Biometric capabilities
iOS 8 / iOS 9 support
Horizon 6.2 & Horizon Client 3.5
Credentials stored in KeyChain
Benefits
Enhanced Security
Enhanced User Experience
Overview
47. Linux Desktop NVIDIA GRID vGPU Support
NVIDIA GRID vGPU 3D Acceleration on RHEL 6.6 VDI
desktop
Shared vGPU
Certified application drivers
Requires vSphere 6.0 U1 and Horizon 6.2 Linux Agent
DirectX 9, 10, 11
OpenGL 2.1, 3.x, 4.x
Benefits
Excellent consolidation ratios with NVIDIA GRID vGPU
Scalable performance from entry level to high end
users
Overview
Specific NVIDIA GRID cards will
support this feature – check
compatibility after product GA
48. Linux Desktop vSGA Support
Lightweight graphics without video acceleration on
RHEL 7.1 VDI Desktop
Shared vGPU
Drivers not application certified
Requires vSphere 6.0 U1 and Horizon 6.2 Linux Agent
DirectX 9
OpenGL 2.1
Benefits
Good consolidation for low-end graphics users
Overview
RHEL 7.1 Now Supported as Linux
Desktop in Horizon 6.2
49. Linux Desktop – Automated Guest Logoff
Enhancement allows Admins to logoff
users after Disconnect
51. 4K Resolution Support
51
4K (3840x2160) Windows VDI desktop
resolution support
Single monitor support with Aero on
Win7 / Win 8 with HW10
3 x Monitor support with Win7
(Aero Disabled) with HW11
Client 3.5 & View Agent v6.2
4K Guest resolution – Not 4K monitor
support with high DPI scaling
52. Overview
Benefits
Windows 10 VDI desktops and RDSH
desktops with Lync client installed
Windows 10 VDI desktop now supported
Client support includes Windows 7, Windows
8, Windows 8.1 & Windows 10 with Microsoft
VDI Plug-in for Lync
Customers can migrate to Windows 10 or leverage
RDSH desktops for VOIP and video.
Highly scalable VOIP and video calling within the
VDI infrastructure
Enterprise grade UC VOIP and video using
standard codecs
QoS support for real-time VOIP and video
Lync 2013 (Skype for Business) Support RDS & Windows 10
RDSH Desktops
Desktops
Why is VMware credible to drive this market shift? Why us?
VMware is the leader in business mobility today:
VMware delivers the industries unquestionable leader in mobile management and security (AirWatch).
VMware is bringing innovation to the desktop platform and extending app delivery across any device (Horizon).
VMware is the market leader in data center and cloud infrastructure, a critical component of the mobile-cloud era.
Just recently announced, we have shown our continued leadership and positioned highest in execution with AirWatch Mobile for Gartner’s 2015 MQ for EMM.
Existing Legacy farms are renamed to Manual Farms
At present, RDSH Servers have to be manually created and added to farms which form the building blocks of Remote Desktop(RDS)/Application pools. As the RDS servers in a farm are not linked clones, it is not possible to recompose farms resulting in the following drawbacks...
Requires an ESD tool set to mange the patching and application deployment
Using view composer's linked clone technology to build out RDS Server farms will solve all the above issues
Increased storage requirements as there is no sharing of base OS/App disk across multiple RDS servers
With RDSH, there is only a OS, internal disk. There is no UserData Disk or System Disposable disk
No refresh of automated RDS server farm as there is no compelling use case
Re-balancing of automated RDS server farm as there is no compelling use case. RDS servers are essentially stateless so we expect customers to simply delete and build a fresh farm if they move storage.
On the fly automated farm creation while adding an RDS Desktop Pool is not supported.
Specified VM Naming of RDS servers in an Automated Farm is not provided. Since RDS servers are multi-user machines, it does not make sense to provide a specific name to an RDS server and pair it with a single user which is what specified naming feature is all about.
QuickPrep is not supported for automated farms.
CBRC option is not available for automated farms. The RDS servers are not rebooted frequently unlike VDI desktops. So, there is no compelling use case for providing this feature.
Today View uses the current session count (and limit) as the only method to determine where to place a new session. The session count represents a course measure of a RDSH's capacity and does not take into account that different sessions will place different kinds and amounts of load on a RDSH. A related issue is that badly behaved applications may consume more than their fair share of resources so there is a need to ensure the instances of such applications on a RDSH can be controlled.
This feature enhances RDSH load-balancing by providing functionality which will
Use counters from the RDSH to determine the best server to start a new session
Allow the specification of rules to control the number of instances of an application running in a server
Combine the counter data and instance rules to create a new session allocation algorithm
This feature provides a configurable means for a RDSH to report it's current load to the broker. This takes the form of a script which the agent can execute whose output is a single number. The load value is then reported back to the broker with session state responses ( asynchronous and queried ).The script may report CPU utilisation, Memory utilisation or any other metric the administrator wishes to use for performing load-balancing. For new sessions, the broker will use the load values to order the servers. The load value returned by a script is a single number. The agent will map the single number to a preference as shown in the table for the 4 possible values that can be returned:
The default load value for an agent is MED. This will be returned for all cases where a load script hasn't been configured. For cases where a script is executed but doesn't complete within 10 seconds or returns an unsupported value, the load preference value will be set to BLOCK and the agent will set it's state to 'configuration error' which will effectively remove the RDSH from the pool of available RDSH for brokering. For the case where a valid load preference value is already cached it will be possible with a registry flag to override the default behaviour of placing the RDSH into a 'configuration error' state.
Application anti-affinity can be used to stop users connecting to a RDSH server that are running more than a defined number of instances of an application.
Application anti-affinity is processed after the Server Placement order is calculated.
For Example, your define the application “Calc.exe” with a Pattern of “autocad.exe: and Count of “2”, if when a session starts the agent reports that a RDSH server exceeds the pattern count the server is skipped and a connection is made with the next server in the placement order.
If multiple patterns match for an application in a single TS session then it only counts as a single match
A wildcard can be used e.g. *pad.exe would match notepad.exe, wordpad.exe and would = 2 count.
A ? Can be used to act as a wildcard for a single character i.e. notepad-?.exe would match notepad-a.exe, notepad-b.exe etc.
If a users is attached to a desktop session, the Anti-Affinity rules will not apply i.e. There are two version of AutoCad.exe running, a user on that RDSH server will be able to launch a 3rd copy from the desktop.
When calling start session, the broker will pass the count rules to the agent. The agent will use the patterns to count the current number of instances of the application and compare with the count. If the count is exceeded, then the StartSession/StartApp will be failed. The broker will then try the next server in the list.
Windows 2008 R2:
1: Apply the patch referred to in https://support.microsoft.com/en-us/kb/2483177
On Windows 2012 the Agent installer does the following when 3D RDSH is selected:
1: If using a virtual machine, disable the VMware SVGA display adapter. Agent installer should do this by default.
2: Set this local GPO setting: (must be logged on as local admin to see this) Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment. “Use the hardware default graphics adapter for all Remote Desktop Services sessions” = enabled
3. Sets the registry key "HKLM\SOFTWARE\VMware, Inc.\VMware SVGA DevTap\Enable3DRDSH" 0: disable 3D RDSH; Boot-time configuration will be performed to disable IHV 3D devices and connect VMware SVGA devices. 1: enable 3D RDSH; Boot-time configuration will be performed to connect IHV 3D devices and disconnect VMware SVGA devices. other value (or value absent): ignored; The system will stay as is, and no boot-time configuration is performed. This is intended for debugging/triaging and should only be used when the user knows what she is doing.
Cloud pod architecture now supports global entitlement for RDS applications in addition to VDI and RDS desktops.
Entitlements can be created and managed through the View Administrator console
Home site supported for Global Application Entitlements as with desktops
Will reconnect to existing application session instead of creating new session.
No change to scaling - total scale will be the same as current - based on total sessions - mix and match app and desktops sessions.
HTML Access 3.5 component is installed with Connection Server by default. No separate HTML access install is required as with CART 3.4 release.
Works with one way external or realm trusts and one way transitive forest trusts.
Two way transitive trusts have been and continue to be supported
Can be turned off via GPO – Child domain enumeration policy.
RDSH Automated Desktops are not supported.
Ability to see the license key file that is applied
Ability to see the Total Concurrent & Named Users
Enforcement. The connection server will continue to enable connections (etc) to be satisfied even if they may appear to be in excess of what is licensed.
License stacking. The current licensing infrastructure within the connection server only requires (and only allows) a single license to be applied. Practically many customers purchase additional licenses which are not tracked in the connection server. This will not change for this feature.
Additional licensed features. The current feature sets enabled by the available licenses will not be changing as part of this feature. If such license changes are necessary they will be tracked separately.
With Horizon 6.0.x and 6.1, Horizon View has three editions, standard, advanced and enterprise:
Standard is licensed per CCU, Advanced and Enterprise can be licensed either as NU or CCU.
Virtual SAN All-Flash architecture - Virtual SAN 6.0 allows the ability to create an all-flash architecture in which SSDs are used for caching as well as data persistence. In this architecture, the flash cache is used completely for write caching.
This all-flash architecture allows tiering of SSDs: a write-intensive, high endurance caching tier for the writes and a read-intensive, cost-effective SSD tier for data persistence, thereby reducing the cost of the all-flash architecture.
Virtual SAN All-Flash provides consistent, predictable performance with up to 90K IOPS/Host and sub-millisecond response times, making it ideal for tier-1 workloads or any applications that require consistent, predictable response times.
In the Q3’15 release, Virtual SAN Stretched cluster could be used to enable active-active data centers. If any of the sites fail for whatever reason there will not be any data loss.
Stretched Cluster is built based on the foundation of Fault Domains, with two main sites and a witness in the 3rd sites. Witness is very unique because it is not contributing any storage or compute to the cluster
QE tests were competed with Horizon 6.2 to ensure interoperability. There is currently no reference architecture in place to provide design for this feature with Horiona 6.2
Will enable UEM to act on information from the client prior to the user logging into the session. This will enable UEM to customise the user experience at an earlier stage.
Tested on WAN up to 250ms latency but performance may be a factor as latency and packet loss increase.
Now includes Compression to reduce network bandwidth and reduce the time to load
Now included AES Encryption (SHA 256) to protect data in transit
Support for MAC is now GA
Do not use both Client Drive Redirection for external drives and USB redirection at the same time
Allows end users to redirect their local drives, external drives (USB storage devices) and network drives on their client machine
Supported on LAN and WAN environments
To disable CDR you can edit registry setting or choose not to install it in the View Agent (per desktop pool). Alternatively you can disable the feature in GPO.
This was in tech preview in 3.4
Do not use both Client Drive Redirection for external drives and USB redirection at the same time
Allows end users to redirect their local drives, external drives (USB storage devices) and network drives on their client machine
Supported on LAN and WAN environments
To disable CDR you can edit registry setting or choose not to install it in the View Agent (per desktop pool). Alternatively you can disable the feature in GPO.
This was in tech preview in 3.4 and now GA in 3.5
When you launch a session you will be prompted on first launch to enable access to local drives (assuming the option is permitted by the administrator).
Encryption and compression are now standard.
AutoConnect will use the Session ID instead of the User Name for printer naming. Therefore, the naming scheme of AutoConnect and VMware print monitor will be extended. In addition the Client ID of the target printer will no longer part of the printer name.
Background
Per default AutoConnect creates redirected printers during logon/reconnect and deletes these printers during logoff/disconnect. The redirected printers use a particular naming scheme to identify the corresponding client printer. This naming scheme equates <printer name>#<user name>:<client printer ID>.
For certain use cases it is necessary to use static printer names that remain the same even as the user connects to the same session from different clients.
Example of Use Case
Take an example of a Horizon environment with:
• Windows 7 end clients
• Windows 7 Horizon desktops.
• End Clients have two printers attached; a laser and label printer.
• The applications inside the View desktop remember the printer names and expect to find the same printer names present throughout the session.
Behavior:
• A user logs on from Client1. ThinPrint AutoConnect creates the two printers from Client1 inside the View desktop.
• The user disconnects and reconnects from Client2. AutoConnect creates the two printers from Client2.
The names of the printers need to remain exactly the same across the two sessions, for example, “laser printer”, “label printer”. This is so that:
The end user does not have to manually remap the printers to the application when she connects to the second session
The application always sees two printers (“laser printer” and “label printer”) regardless of where the end-user is connecting in from.
There are two versions of Windows 10, Server & Client. Only Client is supported with this release, Windows 10 Server is due for release in early 2016.
Horiaon Client on Windows 10 is fully functional and includes all the standard Horizon CART features:
Serial redirection
Scanner Redirection
HTML access with Spartan browser
USB redirection
Client Drive Redirection
RTAV
Smart card redirection
Thinprint
Lync 2013
Graphics with vSGA, vDGA, NVIDIA GRID vGPU
Unity Touch
Horizon Client 3.5 will support OSX 10.11 – El Capitan
Horizon Client 3.5 will support iOS 9
Admin Defined Polices: Admin can define is the setting is enabled / disabled from the Broker.
Admin can define the duration that the TouchID can be used without re-authentication need to re-read and update this wording
Admin Defined Polices: Admin can define is the setting is enabled / disabled from the Broker.
Admin can define the duration that the TouchID can be used without re-authentication need to re-read and update this wording
Admin Defined Polices: Admin can define is the setting is enabled / disabled from the Broker.
Admin can define the duration that the TouchID can be used without re-authentication need to re-read and update this wording
This feature will enable 4K (3840x2160) monitor support for View.
Up to 3 monitors are supported with HW11 Windows 7 with aero off.
Only a single monitor is supported with Windows 8 or aero on in Windows 7 or with HW10.
Expect some bandwidth increase but not necessarily 4x - If you take for example, 1080p video inside a 4k resolution desktop, the video is still only 1080p and not 3840 x 2160. Now if video happens to be in 3840 x 2160 resolution then the bandwidth will go up. No test data at this point to refer to. It will require more but will depend on the usage patters and of course number of monitors. WAN use cases will need to be tested for implementation.
zero clients will be supported, but they won’t necessarily support High DPI scaling. We don’t have DPI scaling Windows clients, even though we have it for the mac client already.
When you enable 3d support for a desktop or RDS applicaion, the maximum resolution inside the guest that you will be able to support is 2560 x 1600 - http://blogs.vmware.com/euc/2015/03/nvidia-grid-vgpu-vmware-horizon.html
Video memory guidance around 4K monitors will be provied a t GA