Architecture Planning
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for View Agent
- Choosing a Display Protocol
- Using Hosted Applications
- Using View Persona Management to Retain User Data and Settings
- Using USB Devices with Remote Desktops and Applications
- Using the Real-Time Audio-Video Feature for Webcams and Microphones
- Using 3D Graphics Applications
- Streaming Multimedia to a Remote Desktop
- Printing from a Remote Desktop
- Using Single Sign-On for Logging In to a Remote Desktop
- Using Multiple Monitors
- Managing Desktop and Application Pools from a Central Location
- Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
- Virtual Machine Requirements for Remote Desktops
- View ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- RDS Host Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- vSphere Clusters
- Storage and Bandwidth Requirements
- View Building Blocks
- View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting Remote Desktop Access
- Using Group Policy Settings to Secure Remote Desktops and Applications
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding View Communications Protocols
- Overview of Steps to Setting Up a View Environment
- Index
This feature is available only on some types of clients. To find out whether
this feature is supported on a particular type of client, see the feature support
matrix included in the "Using VMware Horizon Client" document for the
specific type of desktop or mobile client device. Go to
https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.
Microsoft Lync
You can use a Microsoft Lync 2013 client on remote desktops to participate in
Unified Communications (UC) VoIP (voice over IP) and video chat calls with
Lync certified USB audio and video devices. A dedicated IP phone is no
longer required.
This architecture requires the installation of a Microsoft Lync 2013 client on
the remote desktop and a Microsoft Lync VDI plug-in on the Windows 7 or 8
client endpoint. Customers can use the Microsoft Lync 2013 client for
presence, instant messaging, Web conferencing, and Microsoft Office
functionality.
Whenever a Lync VoIP or video chat call occurs, the Lync VDI plug-in
offloads all the media processing from the datacenter server to the client
endpoint, and encodes all media into Lync-optimized audio and video
codecs. This optimized architecture is highly scalable, results in lower
network bandwidth used, and provides point-to-point media delivery with
support for high-quality real-time VoIP and video. For more information, see
the white paper about VMware Horizon 6 and Microsoft Lync 2013, at
http://www.vmware.com/files/pdf/techpaper/vmware-horizon-view-
microsoft-lync-install-configure.pdf.
NOTE Recording audio is not yet supported. This integration is supported
only with the PCoIP display protocol.
Integrating View with Business Intelligence Software
You can configure View Connection Server to record events to a Microsoft SQL Server or Oracle database.
n
End-user actions such as logging in and starting a desktop session.
n
Administrator actions such as adding entitlements and creating desktop pools.
n
Alerts that report system failures and errors.
n
Statistical sampling such as recording the maximum number of users over a 24-hour period.
You can use business intelligence reporting engines such as Crystal Reports, IBM Cognos, MicroStrategy 9,
and Oracle Enterprise Performance Management System to access and analyze the event database.
For more information, see the View Integration document.
You can alternatively generate View events in Syslog format so that the event data can be accessible to
analytics software. If you enable file-based logging of events, events are accumulated in a local log file. If
you specify a file share, the log files are moved to that share. For more information, see the View Installation
document.
Using View PowerCLI to Create Administration Scripts
Windows PowerShell is a command-line and scripting environment that is designed for Microsoft
Windows. PowerShell uses the .NET object model and provides administrators with management and
automation capabilities. As with any other console environment, you work with PowerShell by running
commands, which are called cmdlets in PowerShell.
Chapter 1 Introduction to View
VMware, Inc. 17