Vworkspace 8.6.3 Administration Guide

Wyse™ vWorkspace™ 8.6.
3
Administration Guide
©2017 Dell Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written
permission of Dell Inc.
The information in this document is provided in connection with Dell products. No license, express or implied, by estoppel or
otherwise, to any intellectual property right is granted by this document or in connection with the sale of Dell products. EXCEPT
AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, DELL ASSUMES NO
LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. IN NO EVENT SHALL DELL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR
INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS
OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF DELL HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. Dell makes no representations or warranties with respect to the accuracy or completeness of
the contents of this document and reserves the right to make changes to specifications and product descriptions at any time
without notice. Dell does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Dell Inc.
Attn: LEGAL Dept.
One Dell Way
Round Rock, TX 78682

Refer to our web site (www.dell.com) for regional and international office information.
Patents
This product is protected by U.S. Patent #: 8,255,984, 8,453,145, 8,560,593, 8,966,112, 9,032,403, 9,054,913, 9,077,583,
9,197,644, 9,311,375, 9,444,808.
Trademarks
Dell, the Dell logo, and Wyse vWorkspace are trademarks of Dell Inc. Other trademarks and trade names may be used in this
document to refer to either the entities claiming the marks and names or their products. Dell disclaims any proprietary interest
in the marks and names of others.
Administration Guide
Updated - February 2017
Software Version - 8.6.3
1
Introduction to Workspace
Virtualization
• About vWorkspace
• vWorkspace virtualization
• vWorkspace resources
• Benefits of vWorkspace
• Key features of vWorkspace
• Infrastructure components
• Infrastructure extensions
• User profile management
• Web Access
• Secure Access service
• License type
• License models
About vWorkspace
Workspace virtualization is a concept in which the desktop environment of a computer is separated from the
physical computer and hosted as a virtual workspace on multiple environments, such as a Virtual Desktop
Infrastructure (VDI), terminal servers, and/or blade PCs running in a data center.
Workspace virtualization helps group and deliver a list of applications or desktops together as a single complete
virtual workspace. It isolates and centralizes an entire computing workspace.
Virtual workspaces can be published and made available to users from a virtual infrastructure comprising
hypervisors, terminal servers, and/or blade PCs. A virtual workspace contains applications, settings, and user-
specific information and can be accessed from most access devices.
Workspace virtualization allows you to maintain a user’s productivity applications from a data center, while
having the flexibility to host these applications on multiple platforms.
vWorkspace virtualization
vWorkspace is a workspace virtualization solution that helps organizations to use the most economical
combinations of virtualization technologies and achieve increased workspace virtualization success.
vWorkspace supports a wide range of technologies and features that help organizations deploy and manage
workspace virtualization projects. vWorkspace also helps leverage existing investments and reduces the cost of
application delivery. This module provides a brief overview of vWorkspace.
With vWorkspace, you can build, implement, and manage a scalable on-demand virtual infrastructure. You can
seamlessly blend multiple virtualization techniques in your infrastructure and achieve lower average cost for
virtual workspace delivery.
vWorkspace helps you deliver full-featured virtual workspaces from a centralized infrastructure that consists of
virtual and physical computers and provision new users quickly. You can provide users with a single, secure
vWorkspace 8.6.3
3
access point to the vWorkspace-enabled infrastructure through the built-in Secure Access service. vWorkspace
also supports various third-party SSL and VPN appliances to facilitate secure access.
vWorkspace provides a single, graphical console that helps you manage your virtual infrastructure and perform
administrative tasks.
vWorkspace resources
The vWorkspace home page is found at:
http://www.dell.com/us/business/p/dell-software-vworkspace/pdf.
The following resources are available from the vWorkspace web site.
• Software downloads. Select the Download link and log in. Downloadable files include the vWorkspace
product, hotfixes, prerequisites, and documentation.
• Support. Select the Support link to be redirected to the Support Portal web site, where you can
download the latest releases, documentation, and patches; enter new support cases and manage
existing cases using the Case Management option, and search the knowledge base.
• Community. Select the Community link, or use the following URL:
http://en.community.dell.com/techcenter/virtualization/vworkspace
• Third party licenses. View descriptions of third party licenses.
vWorkspace independence
Most organizations use a mix of virtualization technologies and platforms for different categories of users:
knowledge workers, task workers, or power users.
vWorkspace provides several levels of independence that help organizations deliver virtual workspaces.
vWorkspace supports multiple storage optimization options, virtualization platforms, desktop and application
delivery types, display protocols, and access devices. You can mix and match or change technology providers
based on your requirements.
For example, you can choose the storage optimization technologies from companies such as Microsoft and
VMware. You can mix and match desktop and application delivery types from multiple virtualization platforms,
such as Microsoft Hyper-V, Parallels Virtuozzo, and VMware ESX hypervisors. With vWorkspace, you can change
the platform as required. You can also leverage your existing infrastructure investments and blend them with
new investments.
You can deliver virtual workspaces on VDI, Remote Desktop Session Host (RDSH), and blade PCs from a single,
integrated product and use application streaming to ensure optimized management experience. You can also
configure the right computing resource for users based on their needs or job role—for example, full desktop,
seamless windowed applications, or client- and server-directed content.
vWorkspace supports multiple display protocols to ensure optimal user experience. It also supports operating
systems, such as Windows, Macintosh, Linux, and Java, and thin clients from manufacturers such as HP, Wyse,
IGEL, and 10zig.
vWorkspace 8.6.3
4
Figure 1. Virtualization technologies and platforms used with vWorkspace
Platform management
vWorkspace delivers a management platform that consolidates multiple techniques and technologies.
vWorkspace delivers simplicity to the organization comprised of one user access point, one management
console, excellent user and administrator experience, and the lowest cost for virtual desktop and application
delivery.
vWorkspace delivers five levels of independence, enabling organizations to deliver desktops and applications
with the most cost-effective combination of virtualization technologies for the needs of each user
classification.
• Storage Management
• Virtualization Platforms
• Desktop Application and Delivery Type
• Delivery
• Access Devices
Benefits of vWorkspace
vWorkspace provides several benefits, such as simplified management, improved security and business
continuity, increased workforce productivity, and optimized user experience.
Simplified management
vWorkspace provides a single, graphical management console to perform configuration, management, and
administrative tasks. From this interface, you can configure and manage virtual workspaces across VDI, RDSH,
and blade PC environments. You do not need to switch screens to manage multiple environments. The
Management Console includes wizards that provide step-by-step instructions to perform complex installations.
vWorkspace automates certain administrative tasks, such as provisioning of desktops, resource pooling, and load
balancing.
vWorkspace 8.6.3
5
Improved security and business continuity
vWorkspace provides security features such as two-factor authentication, built-in Secure Access service, and
delegation of administrator privileges. vWorkspace helps ensure business continuity by providing high system
availability with features such as fault tolerance, rapid recovery, and simple desktop re-provisioning.
Increased workforce productivity
With vWorkspace, you can provide flexible, location- and platform-independent access to your users by
delivering virtual workspaces from multiple virtualization platforms.
Optimized user experience
vWorkspace supports a host of protocols such as Remote Desktop Protocol (RDP), and TCX. Performance
optimizations ensure that the performance of virtual workspaces is as good as or even better than physical
desktops.
Key features of vWorkspace

vWorkspace features can be grouped into two major categories: connection brokering and enterprise-level
management.
Connection brokering
vWorkspace helps you consolidate different platforms and technologies. You can configure vWorkspace to broker
connections to VDI desktops that run on a variety of different platforms, such as Hyper-V, Virtuozzo, and ESX
Hypervisors. You can run these platforms simultaneously or switch between platforms. vWorkspace also provides
an alternative to the VDI solution by supporting connections to desktops running on an RDSH environment, also
referred to as terminal servers. You can configure vWorkspace to broker connections to physical and blade PCs
that run in the data center.
Enterprise-level management
vWorkspace provides several enterprise-level management features. vWorkspace includes automation tools such
as cloning and MSI deployment that reduce the deployment time. You can manage VDI with RDSH and blade PC
environments from a single management console.
Infrastructure components
A vWorkspace farm is a collection of vWorkspace servers and desktop operating systems. The environment
infrastructure consists of databases, the connection broker, the Terminal Server role, the Management Console
role, the data collector service, and the vWorkspace Connectors. Vendor integration is also an important
component of the infrastructure.
vWorkspace infrastructure components that are installed as roles are the prime installable components of
vWorkspace. Each role has a set of features and responsibilities that support the end user’s virtual workspace.
vWorkspace environment databases
vWorkspace includes two types of environment database; Management and Reporting. The Management
database stores all environment-related configurations, data, and activities, and the Reporting database
maintains historical data.
Management database
The Management database performs administrative functions. The Management database stores the information
relevant to a vWorkspace environment, such as configuration data, administrative tasks and results, and
information regarding client connections to virtual desktops and RDSH environments. Each vWorkspace
environment has one Management database associated with it. You can use the data in the Management
database for real-time reporting.
Reporting database
vWorkspace 8.6.3
6
A Reporting database maintains the history of all activities in the environment. Configuring the Reporting
database is not mandatory.
When an activity occurs in the environment, such as the creation of a virtual computer or user login, the details
of the activity are stored in the Management database. If you enable reporting, SQL Triggers populate the
information written in the Management database to the Reporting database. If you disable reporting, historical
data will not be added to the Reporting database. However, you can still generate real-time reports from the
management database. The Reporting database is useful in troubleshooting scenarios where you need historical
data to find the root cause of a problem. You should configure the reporting database at an initial size of 4 GB
with 10% growth rate.
Connection broker
Helps users connect to their virtual desktops, applications, and other hosted resource sessions. The user’s
connecting device sends a request to the connection broker for connectivity to the virtual environment. The
connection broker processes the request by searching for available desktops, and then redirects the user to the
available managed desktop or application.
The connection broker integrates with different virtualization platforms and supports multiple virtualization
servers simultaneously within a single environment to provision and customize new virtual workspaces. You can
configure multiple connection brokers in a single environment.
The connection broker also performs a variety of management tasks. It validates user names, monitors the
activities of the virtual desktops assigned to the users and sets the status as active or inactive, and
communicates with the data collector service running inside each managed desktop. In case of a logoff or
session reset action, the connection broker marks the virtual desktop as available or logged off.
Terminal server role
A set of executables, dynamic link libraries, and device drivers that provides features and management
functionality for RDSH deployments in a vWorkspace environment.
Management Console
An integrated graphical interface that helps you perform various management and administrative functions. You
can install the Management Console on any workstation or laptop.
The Management Console allows you to configure and manage desktops and applications across multiple
environments in your virtual infrastructure. You do not need to switch screens to manage multiple
environments. The Management Console simplifies management by including various automation tools and step-
by-step instructions for performing any configuration task.
You can launch multiple instances of the Management Console. However, changes made simultaneously by
different administrators can cause configuration conflicts.
Data collector service
A Windows service that you install on RDSH servers, virtual desktops, and blade PCs in a vWorkspace
environment. You also need to install the server component of this service on the connection broker. The data
collector service running on a managed desktop sends a heartbeat signal to the connection broker and
communicates the login status of the managed desktop. In case of an RDSH server, it also communicates
whether the managed desktop can accept additional connections.
vWorkspace Connectors
A vWorkspace Connector allows you to access virtual workspaces from a client device. vWorkspace provides
Connectors for the following platforms:
• Windows Connector. Allows users to access virtual desktops and managed applications from Windows
computers, laptops, and thin client terminals.
vWorkspace has an intuitive Windows application that helps users to view a list of authorized desktops and
applications. vWorkspace Web Access allows users to retrieve a list of available applications or desktops through
a web browser.
The vWorkspace Connector for Windows is available in three client packages. VASCLIENT32, which includes
vWorkspace Connector for Windows and the Web Access component, VASCLIENT32T, which includes only the
Web Access component, and VASCLIENT32TS, which includes a silent installation for Web Access.
vWorkspace 8.6.3
7
• Linux Connector. Allows users to access virtual desktops from a Linux-based client. It supports Red Hat
Enterprise Linux Desktop.
• Mac OS X Connector. Users can access their virtual desktops from a Mac-based client.
• Java Connector. A platform-independent Connector that works in conjunction with the Web Access
component.
• iOS Connector. Allows users to connect to virtual desktops from an iOS device. It has a built-in support
for VPN connections.
• Android Connector. Allows users to connect to virtual desktops from an Android device.
Vendor integration
vWorkspace integrates with several vendor platforms and technologies. You can choose those that best meet
your requirements and configure your virtual infrastructure. Some of the key vendor technologies that you can
integrate with vWorkspace include remote desktop services, such as RD Session Host and RD Connection Broker,
Hyper-V/SCVMM, RemoteApp, App-V, Virtuozzo, FlexClone, and display protocols, such as RDP.
Infrastructure extensions
vWorkspace includes various infrastructure extensions, such as Virtual Desktop Extensions, RDP enhancements,
user profile management, Web access, Secure Access service, and performance optimizations. These extensions
simplify deployment and management of workspace virtualization environments and also help you deliver
virtual workspaces optimized for individual users.
Virtual Desktop Extensions (VDE)
Virtual Desktop Extensions (previously called Pntools) are a set of executables, dynamic link libraries, and
device drivers that provide features and management functionality for managed computers in a vWorkspace
infrastructure. You can install these extensions from the Management Console on virtual as well as physical
computers managed through a computer group.
RDP enhancements
RDP is a protocol used for invoking remote sessions to RDSH or managed computers. vWorkspace provides
various high-performance RDP enhancements over remote desktop software.
Application, desktop, and content publishing
Application, desktop, and content publishing provides users with the familiar experience of local computing,
and enables them to operate from any location or device over any network. This feature also helps you publish
individual applications, full desktops, or specific content, such as URLs, on the user’s screen.
Seamless windows
Seamless windows allow users to launch the published applications seamlessly. An application is displayed on a
remote computer or server to the user’s desktop as if the application is running locally on the user’s desktop.
Session sharing
The session sharing feature enables users to launch multiple applications with seamless windows within the
same RDP session and prevents multiple Microsoft or vWorkspace licenses from being consumed by a single user.
Load balancing
The load balancing feature of vWorkspace helps the computer system, network, or disk subsystem to evenly
distribute the data and processing across available resources. You can enable load balancing so that users are
directed to the least busy RDS host or Hyper-V hypervisor.
Desktop integration
With vWorkspace, you can add shortcuts on a user's desktop and the Start menu by using the vWorkspace
Connector for Windows in Desktop Integrated mode. vWorkspace Connector for Windows helps users receive a
list of authorized desktops and applications.
Pass-through authentication
vWorkspace 8.6.3
8
When you enable the pass-through authentication feature, a user’s locally cached domain credentials or the
Kerberos ticket are re-used and the user is not prompted for credentials when connecting to a terminal server
or a remote desktop. The locally cached domain credentials are automatically forwarded to the connection
broker when the user logs on to the vWorkspace infrastructure.
Performance optimizations
The performance optimizations provide performance enhancements over remote desktop software. The
performance optimizations augment RDP by using virtual channels to enhance the user’s experience.
• WAN acceleration. Is designed for latent networks. This feature not only provides faster RDP screen
responses, but also improves performance of all other optimizations.
• Enhanced Audio. Allows users to use audio devices and applications for voice-over IP (VOIP)
communications and collaboration
• USB Redirection. Provides universal support for all USB devices.
• Universal Printing. Provides a universal print driver.
• Multi Monitor. Supports multiple monitors with different resolutions.
• Graphics Acceleration. Adds compression to RDP and reduces bandwidth consumption.
User profile management

You can use vWorkspace to configure virtual user profiles as an alternative to roaming profiles in a Microsoft
Windows environment. You can configure virtual profiles for terminal servers as well as VDI desktops. Virtual
profiles eliminates potential profile corruption and accelerates login and logoff time. This feature helps retain
administratively defined portions of a user’s profile. Everything else, including the local user profile, is
discarded when the user logs off.
A virtual profile works as a client-server application. The two key components of virtual profiles are user profile
storage server and user profile agent.
You can install the agent on the virtual computer, physical computer, or terminal server, and configure one or
more storage servers for maintaining the user settings. When a user logs onto the virtual workspace, the agent
downloads the compressed user settings from the storage server and applies the settings for the user’s session.
When the user logs off, the agent exports the settings and deletes the local profile of the user.
With virtual user profiles, you do not need to clean up local user profiles or configure roaming profiles. Virtual
profiles compress and store the applicable profile data on the user profile storage server and does not consume
drive space on a terminal server or a managed desktop. With virtual user profiles, you can efficiently manage
user profile settings, reduce administrative overhead and help desk calls, and speed up user logins compared to
roaming profiles.
Web Access
Web Access is a web application that acts as a web-based portal to a vWorkspace environment. It allows users to
retrieve the list of available applications and desktops from their web browser. There are no custom settings
required to access this portal. Users just need to specify the address of the Web Access server in the browser
and log on for authentication. After successful authentication, their published desktops and applications are
displayed in the web browser.
You can also use this web-based portal for centralized administration. The management interface helps you
configure Web Access to work with multiple vWorkspace environments and authenticate users to all configured
environments in the same Active Directory domain. It also facilitates configuration of rule-based client settings,
access methods, and pass-through authentication.
vWorkspace 8.6.3
9
Secure Access service
The vWorkspace Secure Access service is an SSL gateway that simplifies the deployment of applications over the
Internet. It prevents direct access to internal vWorkspace resources of an organization.
You can access published applications through the vWorkspace Web Access client and start these applications
over SSL connections. With Secure Access service, traversal of the firewall and proxy server is seamless, so you
don't need to compromise firewall security.
Secure Access service can provide proxy connections to vWorkspace components such as RDP sessions, the Web
Access client, and connection brokers.
License type
vWorkspace is available with one type of license: Premier Edition. This edition includes WSM, vWorkspace
Monitoring and Diagnostics, which monitors vWorkspace VDI and Remote Desktop Session Host (RDSH)
implementations, and provides IT with real-time and historical data.
License models
vWorkspace supports four licensing models: Concurrent users, Per access device, Per named user and
Subscription.
Concurrent users. A user count is associated with each license. This count indicates the maximum number of
users that can connect simultaneously and use the respective services.
Per access device. An access device is a device that is used to access applications and desktops published by
vWorkspace. Software licensed by this type, which is registered to a specific device (such as node-locked), can
be transferred only to a device other than one on which it was initially installed if (a) the new device replaces
the original device and is used for the same purpose as the replaced Device, or (b) Dell provides written
consent.
Per named user. A named user is an individual who is specifically authorized to use the software. Software
licensed by this license type may be used by one user on an individual computer, on a network storage device,
or in a virtualized or shared environment.
Subscription. Pay for the licenses monthly based on the number of connected users in a month.
vWorkspace 8.6.3
10
2
Installing vWorkspace
• Installation overview
• Installation prerequisites
• About the Simple installation
• Advanced installation
• Post installation
• Upgrading vWorkspace
Installation overview
There are two ways to install vWorkspace: Simple installation and an Advanced installation. A Simple
installation installs a preset list of roles while an Advanced installation provides a choice of roles to install.
Installation prerequisites
This section describes the setup that must be complete before starting the installation of vWorkspace.
TCP port requirements

The following are the TCP/IP port number requirements for vWorkspace services:
• Data Collector Service. Listens for Connection Broker service connections on 5203.
This is a Windows service that runs inside each managed computer or vWorkspace enabled RDSH, and
communicates with the Connection Broker. When you install Virtual Desktop Extensions onto a desktop, a
Windows Firewall port exception rule is automatically added to allow incoming connections on this port.
• Connection Broker. Listens for Data Collector service connections on 5201. It also listens for incoming
client connection requests on a configurable port, using 8080 as the default. Optionally, you can
configure the Connection Broker to require SSL encryption using 443 as the default.
This service communicates with the Data Collector running inside each managed computer or
vWorkspace-enabled RDSH.
• Password Management service. Accepts SSL protected client password reset requests on a configurable
port, using 443 as the default.
• Web Access. Uses HTTP and HTTPS application protocols. Although the default port numbers are 80 and
443 respectively, any ports can be used.
• Secure Access service. Acts as an SSL proxy for Connection Broker, Web Access, and RDP
communications, and by default listens on 443.
• RDP Listens on 3389 by default.
Use Microsoft Remote Desktop Protocol (RDP) for connections from a vWorkspace Connector to RDSH or a
managed computer.
• Universal Print Service. Listens on port 5204 on UP printer servers only.
• Registry Service. Listens for registry messages on port 5205 on RDSH and Connection Broker computers.
• User Profile Management Storage. Listens on port 5206.
vWorkspace 8.6.3
11
Prerequisites for installing vWorkspace Monitoring and
Diagnostics
If you are using the Simple Installation to install the Monitoring and Diagnostics role, ensure that your computer
has at least 6GB of memory. If you do not have the required amount of memory, a message appears:
This computer does not have the required minimum amount of memory (6GB) to install Simple Mode
with the Monitoring and Diagnostics role.
Do you wish to continue the installation without the Monitoring and Diagnostics role?
Clicking Yes continues the installation without installing the Monitoring and Diagnostics role. Clicking No cancels
the installation.
If you are using the Advanced installation method, the Monitoring and Diagnostics role cannot be installed on
the Connection Broker. It must be installed on its own machine.
Prerequisites for installing Web Access

When installing the Web Access role on Windows Server 2008 and later, the Microsoft IIS role is installed (if it is
not already).
Use the Secure Access service with Web Access to protect sensitive data, such as passwords.
The following is a list of requirements for vWorkspace Web Access. Web Access can be placed in the DMZ
(perimeter network) or a secured subnet.
Table 1. Prerequisites for installing Web Access
Hardware • Server class hardware that meets the

minimum requirements of the selected
operating system.
• One or more 100 Mbps or 1000 Mbps Ethernet
adapters.
• Implemented as a virtual computer is an
option.
Optional • Microsoft Network Load Balancing
• Third-party load balancing appliance
• X.509 server certificate (if the Web site
requires SSL encryption)
• X.509 trusted root certificate (if used with
vWorkspace Secure Access service)
Prerequisites for installing the Secure Access service

The Secure Access service requires the following for installation:
• One or more X.509 web server certificates
• When securing the communication between the Secure Access service and other back-end servers, such
as the Connection Broker or Web Access, you must install SSL certificates on the Web Access or
Connection Broker servers and the root certificate for the issuing Certificate Authority must be installed
into the Windows certificate store of the Secure Access service and the certificate store of the
connecting client end points.
NOTE: Microsoft IIS can exist with the Secure Access service, but it is not required.
The following are recommended and supported configurations for the Secure Access service:
• Should be placed in a DMZ network or a protected internal network.
• Can be installed on either a physical or virtual computer.
vWorkspace 8.6.3
12
• Can be used with or without Web Access.
• Can be used in conjunction with third-party load balancing appliances.
CAUTION:The Secure Access service should not be installed on a Session Host. The only
exception would be for proof of concept purposes.
Prerequisites for WSM integration

To integrate with WSM, at least one server in your environment must have the WSM role installed (see Advanced
installation on page 16). vWorkspace integrates with a WSM environment through the vWorkspace Web API. The
vWorkspace Web API can be installed on any machine that can access both the vWorkspace database and the
WSM Core server.
To install the Web API rest service

1 Open UDP port 4500 on the machine that will be running the Web API.
2 Run the WSM integration installer from the WSM folder in the following location:
WSM\vWorkspace.WebApi.Installer.msi.
3 Set up the parameters needed for vWorkspace to communicate with the WSM client. For details, see the
vWorkspace example script, also found in the WSM folder.
vworkspace.webapi.demo.ps1
About the Simple installation

A Simple installation allows you to easily install the components that are most used in creating and managing a
vWorkspace environment. The Simple Installation should be used only for testing or Proof of Concept
installations, not for production environments.
A Simple installation installs the following vWorkspace roles:
• Connection Broker role
• Management Console role
• Web Access role. Completes a default Web Access configuration and enables you to immediately start to
use the Web Access feature. The vWorkspace installer adds a default Management Console link and Web
Access user links in the Start | All Programs | Quest Software | vWorkspace folder and desktop
shortcuts.
• User Profile Management Storage Server role. Uses port 5206 for the User Profile Management Storage
service and configures the User Profile Management Storage role, including a silo.
• Monitoring and Diagnostics role. Password: foglight
• Terminal Server/RD Session Host role. Available if Terminal Server is installed. If Microsoft RDSH is
present on a Session Host during the Simple installation, the installer prompts you to install the Terminal
Server/RDSH role.
• WSM role
vWorkspace 8.6.3
13
The Simple installation installs Microsoft SQL Server Express 2014 with the following set values:
Table 2. Values for a Simple installation
Management Database
Value
Configuration field
SQL Server Name <computername>\vWorkspace
NOTE: <computername> is the computer that
vWorkspace is being installed on.
SA User Name sa
SA Password Password1
Database Name vWorkspace_Database
vWorkspace Login Name pnadmin
vWorkspace Login Password Password1
Installing vWorkspace: Simple method

Use the following steps to complete a Simple installation of vWorkspace.
To install vWorkspace: Simple method

1 Download the current version of the vWorkspace installation.
2 Run start.exe on the target computer.
Figure 2. vWorkspace installation window
3 On the vWorkspace installation window, click Install.

Use the other buttons to view the License agreement, browse the installation CD, or exit the
installation.
A message appears indicating that any prerequisites (Windows Installer 4.5 or Microsoft .NET Framework)
will be installed.
vWorkspace 8.6.3
14
Figure 3. Installation prerequisites
4 Click Yes to start the process.

5 During the installation process, you might be prompted to restart. Use the same credentials to log on to
the computer after the reboot. The installation process resumes upon login.
Figure 4. Welcome to InstallShield Wizard
6 On the Welcome to the InstallShield Wizard for vWorkspace, click Next.

7 Accept the License Agreement option, and click Next.
8 On the Customer Information window, enter the User Name and Organization, and click Next.
Figure 5. Simple installation Setup Type
9 On the Setup Type window, select Simple, and click Next.
vWorkspace 8.6.3
15
10 On the Information window, click Yes to continue the Simple install.
11 On the Ready to Install the Program window, click Install.
The vWorkspace components are installed in addition to Microsoft SQL Express 2014, which can take
several minutes. The Microsoft SQL Express 2014 setup windows are displayed during the installation.
TIP: When the Monitoring and Diagnostics role starts to install, do not cancel the
installation until it is finished. Doing so could cause the configuration to be
incomplete.
12 On the InstallShield Wizard Completed window, click Finish.

13 Click Yes to restart the computer, if necessary.
Advanced installation
The Advanced installation allows you to specify the vWorkspace components that you want to install. This type
of installation is recommended for advanced users, larger Proof of Concept or production environments.
Installing vWorkspace: Advanced method

Use the following steps to complete an Advanced installation of vWorkspace.
To install vWorkspace: Advanced method

2 Run start.exe on the target computer.
Figure 6. vWorkspace installation window
3 On the vWorkspace installation window, click Install.

Use the other buttons on this dialog to view the License agreement, browse the installation CD, or exit
the installation.
A message shows the prerequisites that (Windows Installer 4.5 or Microsoft .NET Framework) will be
installed.
vWorkspace 8.6.3
16
Figure 7. Installation prerequisites
4 Click Yes to start the process.

5 During the installation process, you may be prompted to restart. Use the same credentials to log on to
the computer after the reboot. The installation process resumes upon login.
Figure 8. Welcome to InstallShield Wizard
6 On the Welcome to the InstallShield Wizard for vWorkspace, click Next.

7 Accept the License Agreement option, and click Next.
8 On the Customer Information window, enter the User Name and Organization, and click Next.
Figure 9. Advanced installation Setup Type
9 On the Setup Type window, select Advanced, and click Next.
vWorkspace 8.6.3
17
Figure 10. Custom Setup window
10 On the Custom Setup window, select the roles and options that you want to install on this computer.
a Click on an icon in the list of roles to change how a role or feature is installed. Choose one of the
following for each role:
• This feature will be installed on the local hard drive.
• This feature, and all subfeatures, will be installed on the local hard drive.
• This feature will not be available.
Table 3. Roles and Features
Role Description
Connection Broker Role Facilitates Workspace deployment and performs most of the
management functions in vWorkspace. The Management Console role
is installed with this role.
Management Console Role Installs the vWorkspace Management Console to the target computer.
Web Access Role Enables browser-based enterprise access to desktops and applications
published in vWorkspace.
Terminal Server/RD Session Host Installs on top of the native Windows Terminal Server/RD Session Host
Role role and turns vWorkspace into an enterprise platform. The
Management Console role is installed with this role.
User Profile Management Storage Manages the efficient and secure storage of vWorkspace-managed
Role user profiles. The Management Console role is installed with this role.
Secure Access Role Provides SSL-encrypted access to vWorkspace desktops and
applications, enabling secure access over any network.
Universal Print Server Role Enables driver-free, optimized and managed universal printing for
network printers. The Management Console role is installed with this
role.
Remote Site Relay Role Extends the benefits of the vWorkspace Universal Print Server to
other locations, over other networks.
Password Reset Role Securely allows users to remotely change or reset expired passwords
using a vWorkspace Connector or vWorkspace Web Access.
vWorkspace 8.6.3
18
Table 3. Roles and Features
Role Description
Monitoring and Diagnostics Role Provides complete enterprise monitoring and diagnostics for
vWorkspace deployments ranging from hypervisor monitoring to user
experience monitoring. The Management Console role is installed
with this role.
NOTE: When you select the Monitoring and Diagnostics Role, there
will be additional steps to install the Foglight Management Server. See
Monitoring and Diagnostics Role on page 21.
Monitoring and Diagnostics Agent Monitoring and Diagnostics uses agents to monitor vWorkspace. Agent
Manager Role Manager is a process that hosts the agent that monitors components.
It provides a centralized communications link between the
Management Server and the agents.
NOTE: When you select the Monitoring and Diagnostics Agent Manager
Role, there will be additional steps to install the Foglight Agent
Manager. See the Monitoring and Diagnostics Agent Manager role on
page 22.
WSM Role Delivers and manages desktops and applications from a central
location. All applications run locally on the cloud desktop. When a
user’s session is over, all data is stored in the data center. See
Prerequisites for WSM integration on page 13.
b The Install to field shows the location where vWorkspace will be installed. If you want to change
the default installation folder location, click Change and select a Destination folder.
c Click Next to display the Management Database Setup window.
vWorkspace 8.6.3
19
Figure 11. Management Database Setup window
11 On the Management Database Setup window, select one of the options. Then click Next to display the
Management Database Configuration window.
Table 4. Management Database Setup options
Management Database Setup

Value
option
Connect to an existing database Select this option if the management database
already exists and you want to connect this
computer to it.
Create a new database on an Select this option if the management database
existing SQL server does not already exist and you want to create it ion
an existing SQL Server (or SQL Server Express
Edition).
Install SQL Server Express Edition Select this option if you want to install an instance
on this computer and create a of SQL Server Express Edition and create the
new database management database.
Do nothing at this time Select this option if you want to skip database
configuration at this time.
NOTE: If you are installing just the Secure Access service role or the Web Access role, the Management
Database Configuration window is not displayed.
vWorkspace 8.6.3
20
Figure 12. Management Database Configuration
12 On the Management Database Configuration window, complete the necessary information and click Next.
The installer installs the features that were selected. If you chose to install Microsoft SQL Server
Express, that is also installed.
13 On the InstallShield Wizard Completed window, click Finish.
14 If you are prompted to restart the computer, click Yes.
Monitoring and Diagnostics Role

The Monitoring and Diagnostics Role provides enterprise monitoring and diagnostics for vWorkspace
deployments ranging from hypervisor monitoring to user experience monitoring. It provides diagnostic details
about servers and other components, historical trending information, and informative alerts and graphs.
The hardware requirements to run vWorkspace Monitoring and Diagnostics can vary, depending on the size of
your monitored environment.
To install the Monitoring and Diagnostics role

1 After selecting the Monitoring and Diagnostics role in the vWorkspace installation, the Discovery prompt
is displayed.
Figure 13. Discovery prompt
2 Select Yes to automatically discover the vWorkspace environment. If you select No, you must log in to
Monitoring and Diagnostics through a browser and run the discovery process manually.
vWorkspace 8.6.3
21
Figure 14. Installshield Wizard prompt
3 From the Installshield Wizard prompt, click OK.

4 Enter the vWorkspace Database credentials and click Next.
5 On the Monitoring and Diagnostics Configuration window, provide the administrator credentials for
Monitoring and Diagnostics configuration and click Next. The vWorkspace installer executes the
Monitoring and Diagnostics installation and prompts the Monitoring and Diagnostics installation screens
to input data. vWorkspace installer provides you with progression feedback during the installation. For
detailed information about the installation process, see the vWorkspace Monitoring and Diagnostics
Installation Guide.
Figure 15. Monitoring and Diagnostics Configuration window
6 When the Monitoring and Diagnostics installation process completed, click Done.
7 When the vWorkspace Installer finishes, click Finish.
NOTE: If you chose Auto Discovery, depending on the size of your vWorkspace environment the discovery
process can take from few minutes to a few hours. Do not interrupt the discovery process after it has
started since this can produce unexpected results.
Monitoring and Diagnostics Agent Manager role

The Monitoring and Diagnostics Agent Manager Role uses minimal system resources, whether running on a
monitored host or monitoring remotely. The amount of resources used depends on a variety of factors including
the number of agents running on the monitored host, the amount of data being collected, and whether the
Management Server is running.
vWorkspace 8.6.3
22
To install the Monitoring and Diagnostics Agent Manager role
NOTE: Before installation, ensure that the Foglight Management Server is installed.
1 After selecting the Monitoring and Diagnostics Agent Manager role in the vWorkspace installation, the
Agent Manager Info window is displayed. Enter the credentials of the Foglight Management Server.
Table 5. Agent Manager Information
Field Description
Foglight Server Name The machine where the Monitoring and Diagnostics server is
installed.
Foglight HTTP Port Number HTTP port number to which the Monitoring and Diagnostics
server is listening.
Foglight HTTPS Port Number HTTPS port number to which the Monitoring and Diagnostics
server is listening.
Foglight User Password The default user password is foglight.
Foglight Lockbox Password The default Lockbox password is foglight.
Number of Agent Manager Number of remote agent manager instances you want to
Instances install.
NOTE: If the Agent Manager instances are already installed
on the server then the number of agent managers is
incremented by this amount.
2 The Agent Manager installation continues. Click Finish when the installation is complete.
Scripted installation
vWorkspace supports scripted installations. Setup.exe can be executed with switches that provide answers to
the dialog box prompts of a vWorkspace installation. This section outlines the commands and switches used to
perform a scripted (silent) installation.
setup.exe /s /v”/qn ADDLOCAL=<Role Codes> <Database Options>”
Role Codes
Table 6. Switches and commands used to perform a scripted installation
Core Must always be specified

CB Connection Broker Role1,2
MC Management Console Role1
WA Web Access Role
WA Common Includes important files that are common to CB,
MC, TS, PRT, UPS, and WA roles.3
TS Terminal Server\ RD Session Host Role1,2
UPS User Profile Management Storage Role1,2
SG Secure Access service Role
PRT Universal Print Server Role1,2
RSR Remote Site Relay Role
PR Password Reset Role
RL Reporting and Logging Role
1 Requires Database Options (see below).
vWorkspace 8.6.3
23
2 Requires the Management Console role to be installed.
3 Must be installed on items that require a database connection, such as a print server.
TIP: To specify more than one role code, delimit role codes with commas without
spaces. For instance, to specify the connection broker and management console
roles, use the following syntax:
ADDLOCAL=Core,CB,MC,WACommon
Table 7. Database options used to perform a scripted installation
DBOPTION Specifies how to setup the database connection

1=Connect to existing SQL Server
2=Create new database on existing SQL
Server
DATASOURCENAME ODBC data source name (DSN name)
SQLSERVERNAME SQL Server name
DATABASENAME vWorkspace_Database
SQLLOGINACCOUNT vWorkspace administrator name (pnadmin account)
SQLLOGINPASSWORD vWorkspace administrator password
SAUSERNAME sa *
SAPASSWORD SA Password *
* only required for DBOPTION=2

TIP: Any values specified that contain spaces must be surrounded by \” characters.
For instance, to set the DATABASENAME options to vWorkspace Database, use
the syntax:
DATASOURCENAME=\"vWorkspace Database\"
Additional switches
REBOOT=\"ReallySuppress\"
Ensure that the following software prerequisites are met prior to starting the scripted installation:
• Microsoft .NET Framework 4.5 Service Pack 1
• Microsoft Windows Installer 4.5
• J2SE Runtime Environment 7.0 Update 55 (Only when the Connection Broker role is selected)
Examples of a scripted installation

This section provides examples of installing vWorkspace with the scripted installation.
To install the Web Access role only
setup.exe /s /v"/qn ADDLOCAL=Core,WA,WACommon"
To install the Management Console and Terminal Server/RD Session Host roles, and connect to an existing
database:
setup.exe /s /v"/qn ADDLOCAL=Core,CB,TS,WACommon DBOPTION=1
SQLSERVERNAME=\"SQLSERVER01\"
DATASOURCENAME=\"vWorkspace Database\"
DATABASENAME=\"vWorkspace_Database\"
vWorkspace 8.6.3
24
SQLLOGINACCOUNT=\"pnadmin\"
SQLLOGINPASSWORD=\"Password1\""
To install the Management Console and Connection Broker roles, and create a new database
setup.exe /s /v"/qn ADDLOCAL=Core,CB,MC,WACommon DBOPTION=2
SQLSERVERNAME=\"<servername\instancename"
DATASOURCENAME=\"vWorkspace Database\" SAUSERNAME=\"sa\"
SAPASSWORD=\"Password1\"
DATABASENAME=\"vWorkspace_Database\"
SQLLOGINACCOUNT=\"pnadmin\"
SQLLOGINPASSWORD=\"Password1\""
Post installation
After you complete the installation of vWorkspace, you might need to perform additional tasks before you begin
the configuration process.
• Installing vWorkspace Connectors
• Enabling vWorkspace reporting
Installing vWorkspace Connectors

To allow users to connect to managed applications and desktops in a vWorkspace infrastructure, a vWorkspace
Connector must be installed onto the client device.
Automatically installing the vWorkspace Connector for

Windows
The Connector Management node allows you to centrally create and manage the configuration of all of your
vWorkspace Connectors.
After creating a client configuration, you can deploy the configuration to client devices. Connector
configuration allows you to detect vWorkspace Connectors on client devices, easily deploy Connector updates to
any platform, and push Connector configurations to end users, all managed from a central location.
See Connector management overview on page 104 for detailed information about setting up and deploying the
Connector configuration.
If this feature is set up in the Management Console, the user is automatically prompted to install or upgrade
vWorkspace as needed.
To automatically install the vWorkspace Connector for Windows

1 The user opens a Web browser and enters the vWorkspace website provided by the administrator.
2 In the Credentials prompt, the user enters credentials. vWorkspace verifies whether the Connector for
Windows is installed.
3 If the vWorkspace Connector for Windows is not installed, the user is prompted to install the current
version. Clicking Install installs the current version of the Connector.
• On Windows IE, the vWorkspace Connector is downloaded and installed.
• On other Internet browsers, the vWorkspace Connector is downloaded to the browser’s download
location. The user must run the installer from that location.
vWorkspace 8.6.3
25
To upgrade the vWorkspace Connector for Windows
1 From the Windows desktop: The user clicks the vWorkspace icon.
From Web Access: The user opens a Web browser and enters the vWorkspace website provided by the
administrator.
2 At the Login prompt, the user enters credentials. vWorkspace verifies whether the Connector is
installed.
3 If an earlier, unsupported version is installed, the user is prompted to install the current version. Clicking
Install installs the current version of the Connector. Clicking Continue opens the older version.
NOTE: If the user selects Continue, vWorkspace does not prompt to upgrade again within a 24-hour period
unless the user clears the browser cookies. 

The Continue button is displayed only if the Require a valid Connector before continuing option is not
selected from Connector Management | Installation | Connector Properties |Requirements.
4 If the user installs the new version:

• On Windows IE, the vWorkspace Connector is downloaded and installed.
• On other Internet browsers, the vWorkspace Connector is downloaded to the browser’s download
location. The user must run the installer from that location.
Manually installing the vWorkspace Connector for Windows

If the auto-detect feature is not set up in the vWorkspace Management console, users need to manually install
the Connector.
VASCLIENT32. This package includes vWorkspace Connector for Windows and Web Access. VASCLIENT32.EXE is
an MSI-based installation with EXE bootstrapper. The MSI Engine (2.0 or higher) must already be installed onto
the target client workstations.
Vasclient32.exe, can be renamed to control the installation behavior as follows:
• vasclient32.exe. All options are installed.
• vasclient32t.exe. The vWorkspace icon and startup icons will not be created and the Dell URL
Redirection plug-in for Internet Explorer will not be installed.
• vasclient32nousb.exe. USB components are not installed.
• vasclient32t_nousb.exe. The vWorkspace icon and startup icons are not created and the Dell URL
Redirection plugin for Internet Explorer is not installed. USB components are not installed.
This installer uninstalls previous versions of both the Full and Web vWorkspace Connectors for Windows during
upgrades. In this installer, the Credentials Pass-through dialog is no longer part of the setup steps simplifying
the setup process for users.
To manually install the vWorkspace Connector for Windows

1 Download the appropriate package.
2 Execute the Connector file.
3 On the Welcome window of the vWorkspace Connector InstallShield wizard, click Next.
4 Accept the terms of the License Agreement, and then click Next.
5 On the Customer Information window, enter the appropriate information, and select one of the options
to whom this client package is to be installed. Click Next.
6 On the Destination Folder window, click Next to accept the default location. Or click Change to change
the location.
7 OPTIONAL: Select the option Enable Credentials Pass-Through, and click Next.
vWorkspace 8.6.3
26
Select this option if the client computer is joined to the domain and you want to reuse the user domain
credentials on the client computer to authenticate with the vWorkspace-enabled desktop infrastructure
without having to retype.
This option is only for computers that do not support Kerberos.
8 On the Shortcut Options window, select the desired shortcuts, and click Next.
This window is available only if you are installing a client option that includes vWorkspace Connector for
Windows.
9 On the Ready to Install the Program window, click Install to begin the installation.
10 When the InstallShield wizard has completed, click Finish.
You might be prompted to restart your system after the installation of the vWorkspace Connector has
completed.
vWorkspace Windows Connector silent installation

The vWorkspace Connector for Windows is supported on Microsoft Windows computers, laptops, and Microsoft
Windows Embedded thin client terminals, and is available in various packages. This section describes the
unattended setup (silent) procedures for each of the following Connector packages.
See Using the vWorkspace Connector for Windows on page 176 for more information about using the
vWorkspace Connector for Windows.
VASCLIENT32
As an InstallShield package, vasclient.exe can accept a number of command line arguments. Command line
options that require a parameter must be specified with no spaces between the option and its parameter.
If you run a normal installation using vasclient32.exe, InstallShield extracts and then executes the included
vasclient32.msi package. The file, msiexec.exe, begins the installation and queries the user four times.
The installation prompts the user to install For All Users or Just Myself, to Enable Single Sign-On or not, to To
Launch in Desktop Integrated Mode or not, and to Place a shortcut on the Desktop or not.
These four user dialog boxes are represented by MSIEXEC switches of:
• ALLUSERS=\"1\" or ALLUSERS=\"\"
• ENABLESSO=\"1\" or ENABLESSO=\"\"
• STARTUPSHORTCUT=\"1\" or STARTUPSHORTCUT=\"\"
• DESKTOPSHORTCUT=\"1\" or DESKTOPSHORTCUT=\"\"
• \"1\" is Yes.
• \"\" is No (Null).
The InstallShield switch to pass parameters to msiexec is the /v switch. There can be no spaces between the /v
switch and its parameters so that the command will look initially like this following.
vasclient32.exe /v"<options>"
The <options> are the msiexec parameters. For msiexec, the /q option is used to set the user interface level
along with any of the following flags.
Table 8. MSIEXEC silent or Near silent switches
Option
/q No user interface.
/qn No user interface.
/qn+ No user interface. A dialog box appears at the end of the
installation.
vWorkspace 8.6.3
27
Table 8. MSIEXEC silent or Near silent switches
Option
/qb Basic user interface.
/qb+ Basic user interface. A dialog box appears at the end of the
installation. If you cancel the
installation, a dialog box is not
displayed.
/qb- Basic user interface. No dialog box boxes appear.
/qr Reduced user interface.
If you want to hide the initial vWorkspace splash screen, add the /s option and the installation displays only the
installation progress bar dialog box.
To silently install the vasclient32.exe, issue the setup instruction:
vasclient32.exe /s /v"ENABLESSO=\"\" ALLUSERS=\"1\" /qn"
The /s suppresses the splash screen. The /v passes everything within the quotes to msiexec. The msiexec /qn
switch provides a no dialog box, silent install.
If you want the progress dialog boxes shown for user feedback so that they know something is happening, issue
the following command.
vasclient32.exe /s /v"ENABLESSO=\"\"ALLUSERS=\"1\" /qr"
The /s suppresses the splash screen. The /v passes everything within the quotes to msiexec. The/qr switch
shows a reduced user interface with only the progress bar dialog box.
Integrating the Dell Wyse ThinOS™ thin clients with

vWorkspace
ThinOS is a purpose-built cloud client computer operating system with an unpublished API, which makes it very
secure against attacks. ThinOS provides instant-on access so users can log on in seconds, and automatically
checks for firmware upgrades from a network server. Users can be centrally managed using simple .INI
configuration files.
You can use the following thin client models with vWorkspace or any future models as long as they are based on
the ThinOS operating system:
• 3000 series Thin Clients

• 5000 series All-In-One Thin Clients
vWorkspace supports both Virtual Desktops and Seamless Window Application Publishing.
TIP: Use vWorkspace 8.0 or later to publish applications to ThinOS devices.
Thin client configuration

When a Dell Wyse ThinOS client device is powered on and the operating system is started the device is
configured to automatically obtain an IP address from a Dynamic Host Configuration Protocol (DHCP) server.
Administrators can optionally use DHCP Scope Options to provide the File Server and Connection Broker server
information.
When a ThinOS device starts, it attempts to locate a valid File Server to download the initial environment
configuration files (named WNOS.INI and RDP.INI) and the bitmap files that conform the desktop background and
the login window logo. The device then contacts the vWorkspace connection broker server to authenticate the
vWorkspace 8.6.3
28
user to the virtual environment and to obtain the list of published virtual desktops or applications available to
the authenticated user.
There are two configuration methods: The DHCP method (recommended for production environments), and the
Manual configuration method (used for easier deployment and testing).

DHCP Server Configuration

You should set the DHCP server’s option tags 161 and 188 to the IP address or addresses of the Connection
Broker(s) or Web Access site using the following syntax:
<protocol>://<iplist>:<port>
protocol: HTTP or HTTPS. This parameter is optional. If omitted, http is automatically assumed.
iplist: list of IP addresses or FQDN corresponding to the Connection Brokers. The specified addresses must be
separated by commas or semi-columns.
port: the TCP port that the Connection Broker(s) is/are configured to listen on. This parameter is optional. If
omitted, ports 80 (HTTP) and 443 (HTTPS) are automatically assumed. 
Examples:
HTTP://10.0.0.22:8080 One Connection Broker (10.0.0.22), protocol

= HTTP, port = 8080
HTTP://10.0.0.22;10.0.0.23:8080 Two Connection Brokers (10.0.0.22 and
10.0.0.23), protocol = HTTP, port = 8080
HTTPS://10.0.0.22 One Connection Broker (10.0.0.22), protocol
= HTTPS, port = 443
HTTPS://10.0.0.22:8081 One Connection Broker (10.0.0.22), protocol
= HTTPS, port = 8081
HTTPS://WebAccess-Site/proxy One WebAccess site, protocol = HTTPS, port
= 443
HTTPS://WebAccess-Site:8081/proxy One WebAccess site, protocol = HTTPS, port
= 8081
Please note that option tag 161 is used to specify the servers from which the WTOS firmware updates can be
downloaded to the thin client, while option tag 188 is used to specify the VDI brokers. Since the Connection
Brokers are capable of fulfilling both functions, option tags 161 and 188 may be configured identically.
Enabling HTTP and HTTPS Support 
The Connection Broker can be configured to accept HTTP and HTTPS requests simultaneously. To configure the
Connection Broker's HTTP and HTTPS ports, follow these steps:
1 In the vWorkspace Management Console, right-click on Locations. Select Properties. Select one or both
protocol options (HTTP and/or HTTPS) and specify the corresponding TCP port numbers. If IIS is installed
on the same server, be sure to select non-conflicting TCP ports.
2 For HTTPS support, a server certificate is needed for each Connection Broker. The certificate can be
issued by an internal CA or an external one. Once the certificate has been installed onto the Connection
Broker, expand the Connection Brokers node in the Management Console and right click the
corresponding Connection Broker whose certificate you just installed. Under vWorkspace Broker Settings
vWorkspace 8.6.3
29
select Certificate and then click Select Server Certificate. Finally, select the desired certificate from
the list. Repeat this for all of your Connections Brokers that will communicate via HTTP and HTTPS
Supporting Environments with Multiple Subnets 
In environments entailing multiple subnets, it is possible to specify unique WNOS.INI and RDP.INI files on a per
subnet basis. This is accomplished by making use of DHCP option tag 162 to specify a unique subnet identifier
per subnet. For example, given SUBNET1 and SUBNET2, the DHCP option tags for these two subnets would be
configured as follows:
SUBNET1:
161: http://<iplist>:<port>
162: subnet1
188: http://<iplist>:<port>/subnet1/wyse
In this case, WNOS.INI and RDP.INI are stored on the Connection Broker under:
C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet1\wyse\WNOS

SUBNET2:
161: http://<brokerip>:<port>
162: subnet2
188: http://<brokerip>:<port>/subnet2/wyse
C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet2\wyse\WNOS

Furthermore, by appending the $ symbol to the end of the subnet identifier, the “\wyse” component of the path
following the subnet identifier can be omitted. In this case, reconfigure the subnets as follows, noting the
omission of “\wyse” in option tag 188:
SUBNET1:
161: http://<iplist>:<port>
162: subnet1$
188: http://<iplist>:<port>/subnet1
C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet1\WNOS

SUBNET2:
161: http://<brokerip>:<port>
162: subnet2$
188: http://<brokerip>:<port>/subnet2
In this case, WNOS.INI and RDP.INI are stored on the Connection Broker under: 
C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet2\WNOS

TIP: Replace broker_name with your connection broker name or IP addresses. If you
use a name ensure that you have DNS resolution. Use ';' for multiple addresses.

Manual configuration
If you do not have access to a DHCP server or if you do not want to make changes to your DHCP servers you can
use the manual configuration method by powering on your thin client and manually entering the required
changes.
vWorkspace 8.6.3
30
Before starting the configuration, upgrade your device firmware to the latest available version. Contact
customer support to obtain the latest firmware for your device.
To manually configure the thin client

If your device is locked, or you want to obtain administrative access to the device, press the G key on your
keyboard repeatedly while your device is starting.
TIP: Pressing the G Key while starting also resets the device to the default factory
settings.
1 Configure the File Server setting. The vWorkspace connection broker natively provides file server
support for your ThinOS thin clients, so you do not need to set up an additional FTP or HTTP server in
your environment.
If you already have a file server in your current environment, you can skip this step.
a Click on the desktop area and select Administration from the menu, then click Central
Configuration. The Central Configuration window appears.
b In the File Servers/Path field, enter your connection broker server name or address in the format:
"http://broker_name:8080/"
c Leave the User Name and Password with the default values. The vWorkspace connection broker
server accepts anonymous requests.
d Click OK. Reboot the device, if prompted.
2 Configure the connection broker server setting by specifying the vWorkspace connection broker servers
available in your environment.
a Click on the desktop area and select Administration from the menu, then click Remote
Connections. The Remote Connections window appears.
b Under the Select Broker tab, select Dell vWorkspace. If you are using an older version of ThinOS
that does not include the Dell vWorkspace option, select Other.
c In the Broker Server field, enter your connection broker server name or address in the format:
"http://broker_name:8080/"
d Click OK. Reboot the device, if prompted to.
Configuring the vWorkspace connection broker
After configuring the Dell Wyse ThinOS thin client, you need to configure the vWorkspace connection brokers.
Please refer to the WYSE Administrators Guide for detailed information on how to customize wnos.ini.
On each Connection Broker, under the installation directory of vWorkspace there is a directory named WYSE. In
this directory, there is a file called wtos_sample_files.zip, extract it to the WYSE directory, after extracting you
should have the following:
C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS
C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS\bitmap
C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS\cacerts
C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS\ini
In each directory that is created contains sample files as follows:

C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS
Wnos.ini
Rdp.ini
vWorkspace 8.6.3
31
C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS\bitmap
Dell_WhiteonBlue.png
Dellform.jpg
C:\Program Files (x86)\Quest Software\vWorkspace\WYSE\WNOS\ini
JoeUser.ini
WNOS.INI
This file, which contains various WYSE commands and parameters, is sent from the Connection Broker to the
thin client upon device boot-up. Please refer to the WYSE Administrators Guide for detailed information on how
to customize wnos.ini.
Please note that the bitmap directory created is used to store optional bitmap files (i.e., corporate logo to be
displayed on the thin client) referenced in wnos.ini. 

RDP.INI 
RDP.INI is used to specify additional RDP connect parameters to be appended to the RDP connect commands in
{username}.ini. If RDP.INI exists under the WNOS directory, the Connection Broker will automatically append the
contents of this file to the RDP connect commands. For a list of valid RDP connect parameters, please refer to
the WYSE Administrators Guide.

{USERNAME}.INI 
Upon successful user authentication, the Connection Broker dynamically generates a user-specific configuration
file named {username}.ini (i.e., peggy.ini, john.ini) and sends it to the thin client. This file is generated
entirely in memory and contains a list of RDP connection strings referencing the user’s authorized published
desktops.

Optionally, additional parameters can be automatically appended to the dynamically generated 
{username}.ini. This is accomplished by manually creating a per-user configuration file, also named
{username}.ini, under the ini directory. Please refer to the WYSE Administrators Guide for the list of optional
parameters that can be specified in {username}.ini.
The following takes place upon authenticating a given user: if a custom {username}.ini exists in the ini
directory, the Connection Broker will merge its contents into the dynamically generated {username}.ini. The
final {username}.ini sent to the client contains the list of authorized RDP connections, as well as the
parameters specified in the custom {username}.ini. 

To create the required file and directory structure
1 Open the file named wnos.ini with a text editor, such as Notepad.
2 Replace the values, BROKER_NAME, with your vWorkspace connection broker server name or address.
3 Replace the Language value with your keyboard specifications.
4 Replace the DomainList value with your active directory windows domain.
5 To automatically log off the Thin Client device when a user logs off or disconnects from a virtual
desktop, include the value named "AutosignOff=Yes"
6 Make additional customizations to the wnos.ini or save your changes. The wnos.ini file provides the
minimum settings required.
7 Open the rdp.ini to configure the AutoConnect value.
a To automatically connect users to a virtual desktop after authentication to the connection broker,
set this value to 1.
b To provide users with an icon representing the virtual desktop in order to connect, leave the
default value of 0.
8 To customize the ThinOS desktop background image and login window by navigating to the "bitmap"
directory under the WNOS folder and replacing the files with the following file specifications:
a Desktop Background: File name Dellback.jpg 1024 x 768 pixels
vWorkspace 8.6.3
32
b Login Window Logo: File name DellForm.jpg 352 x 80 pixels
To verify the configuration

After configuring the Dell Wyse ThinOS thin clients with vWorkspace, test the configuration to verify that it is
set up correctly.
1 Restart the thin client device. The customized desktop background and the login window appears.
2 After connection broker authenticates the user, the list of published virtual desktops and applications
appears.
3 If you click on the Connect Manager window, the list of published virtual desktops also appears.
4 Choose your preferred Visual Experience by navigating to System Administration | Remote Connections |
Visual Experience and choose Classic Desktop or Zero Launchpad.
• Classic Desktop. Provides a full task-bar, Desktop and Connection Manager.
• Zero Launchpad. Provides an overlay interface, which enables end users to switch between
virtual desktop sessions.
5 Click OK.

Updating the WYSE Thin OS Firmware 
In order to update the thin clients with the latest WTOS firmware, obtain the latest WTOS firmware file for the
model of the WTOS device, and store it the WNOS directory. Upon rebooting the thin clients, the firmware will
be automatically updated if necessary. Please note that option tag 161 must already be configured as discussed
above for the firmware update process to work.
Please note that the Connection Broker only supports HTTP-based firmware updates, and therefore does not
respond to FTP-based update requests. In order to update existing thin clients running older WTOS firmware, an
FTP server is required. For this purpose, it would be possible to install the Microsoft FTP service on the
Connection Broker(s). Please note that newer WTOS firmware releases do support HTTP based upgrades, thus
obviating the need for an FTP server in order to perform future firmware updates.
Enabling vWorkspace reporting

After you install the Monitoring and Diagnostics role using an Advanced Installation, you can use the vWorkspace
Management Console to enable reporting, which allows you to generate detailed reports on both the real-time
and historical state of your desktops, servers, and application permissions. You can also generate reports
detailing the actions performed by administrators within the vWorkspace Management Console.
To enable vWorkspace reporting

1 Open the vWorkspace Management Console and navigate to File | Database Configuration. The Configure
vWorkspace Database window is displayed.
2 Click the Database Configuration button. The Database Configuration wizard is displayed.
3 On the Action window, select Enable vWorkspace Reporting, and click Next.
4 On the Database Information window, enter a name for the new reporting database, and click Next.
The reporting database must be on the same SQL Server as the vWorkspace database.
5 On the Credentials window, specify the credentials for the database actions.
a Enter the login name and password of an existing SQL administrator. These are needed to install
the reporting capability.
b Enter a login name and password for a new vWorkspace SQL login that you want to create. If the
new vWorkspace SQL login already exists, the existing login will be used and the password
specified must be correct.
vWorkspace 8.6.3
33
6 Click Finish to display the confirmation dialog box.
7 Click Yes, and then click Finish on the Credentials window to complete the process.
To disable vWorkspace reporting

Disabling vWorkspace reporting keeps your current historical data, but no more data will be added. You can
continue to run real time reports that show the current state of the system.
1 Open the vWorkspace Management Console and navigate to File | Database Configuration.
2 On the Configure vWorkspace Database window, click Database Configuration.
3 On the Action window, select the Disable vWorkspace Reporting option.
4 Click Finish.
Upgrading vWorkspace
This section outlines the recommended procedures for upgrading your vWorkspace environment to the current
version.
Upgrade prerequisites
Before upgrading vWorkspace, ensure that you have done the following:
• Refer to the vWorkspace System Requirements for supported platform updates. For a summary,
see Windows version compatibility matrix by role on page 34.
• Fully back up the existing vWorkspace database and reporting database.
• Create a snapshot of the virtual environment, excluding VDI Machines.
• Download the current version of vWorkspace and all current hotfixes.
Windows version compatibility matrix by role

The following table summarizes the Windows operating system versions supported by vWorkspace roles and
components. For more details, refer to the vWorkspace System Requirements document.
Table 9. Windows operating systems supported by vWorkspace
Win 7 2008 R2
Win 8 Win 2003 2012 R2
Feature
Win 8.1 R2 2016
Win 10
Connection Brokers NO NO YES
Management Console YES NO YES
Terminal Server/RDSH NO NO YES
User Profile Management NO NO YES
Storage Server
Universal Printing NO YES YES
Remote Site Relay Server NO NO YES
Secure Access service NO NO YES
Web Access NO NO YES
Reporting NO NO YES
Monitoring and Diagnostics NO NO YES
vWorkspace 8.6.3
34
Table 9. Windows operating systems supported by vWorkspace
Win 7 2008 R2
Win 8 Win 2003 2012 R2
Feature
Win 8.1 R2 2016
Win 10
Monitoring and Diagnostics NO NO YES
Agent Manager
Password Reset NO NO YES
Broker Helper Service NO NO YES
Virtual Desktop Extensions for YES NO YES
VDI
Connector for Windows YES NO YES
Upgrade phases
In many cases, upgrading a large vWorkspace environment cannot be done in a short time period. You can break
the upgrade process into two phases. The first phase includes all critical components that must be updated at
once. The second phase includes all other components that can be updated over an extended period of time.
Upgrade phase 1
The following components must be upgraded in Phase 1. Connection brokers must be upgraded first. The first
connection broker to be upgraded updates the current vWorkspace database schema. All other upgrade
combinations require a database schema update. The other roles (if applicable to your environment) can be
upgraded in any order after the connection broker role, but must be completed in phase 1.
• Connection Broker Role
• Management Console Role
• Monitoring and Diagnostics Role
• Monitoring and Diagnostics Agent Manager Role
• MetaProfile Storage Server Role
• Broker Helper Service for SCVMM
Things to consider:
• After the Connection Brokers are upgraded, Web Access sites continue to operate, but you cannot make
configuration changes to Web Access sites in the Management Console until the Web Access server is
upgraded.
• After the Connection Brokers are upgraded, the Management Console on the Connection Broker can be
used to manage the environment. Management Consoles installed on other computers cannot be used
until they are also upgraded.
• After the Connection Broker is upgraded, initialize the Hyper-V virtualization hosts that are managed
directly in vWorkspace. To initialize a Hyper-V host, in the Management Console go to the Locations |
Location | Virtualization Hosts | Hyper-V node, right click on a Hyper-V host and select Initialize. The
initialization process upgrades the Hyper-V Catalyst Components. After initialization has completed, the
Catalyst field for the Hyper-V host will indicate the version of the Hyper-V Catalyst Components. If
properly upgraded, the field will report a version later than or equal to the version reported in the
Management Console status bar. Upgrading the Hyper-V Catalyst Components flushes the HyperCache on
the host. It is important to reboot at least one of the virtual machines on the host soon after the upgrade
to populate the HyperCache.
vWorkspace 8.6.3
35
Upgrade phase 2
The following components can be upgraded after phase 1 in any order.
• Secure Access service Role
• Web Access Role
• vWorkspace Java Connector (updated on the Web Access server)
• vWorkspace Connectors (for Windows, Mac, iOS, Android and Linux)
• TS/RDSH Role
• Virtual Desktop Extensions for VDI Computers
• Universal Print Server Role
• Remote Site Relay Role
• Password Reset Role
Things to consider:
• You should not enable Forced Broker Authentication (FBA) until all vWorkspace Connectors are upgraded
to a version that supports FBA. Refer to Features that are compatible with vWorkspace Connectors to see
the minimum vWorkspace Connector versions that support FBA. FBA can be enabled after the install from
the Secure Access service control panel.
• Saved PIT files that point directly to an RDP server through the Secure Access service are not supported
with FBA. Saved PIT files that reference a published application or desktop will work with FBA.
• vWorkspace users can continue using an older version of the vWorkspace Connector. It is recommended
that the vWorkspace Connector and Server components (RDSH/VDI) be on the same version as some
features may not work as expected with a newer version of the server. For most functionality, the
vWorkspace Connector continues to operate normally. Some features of the Connector may not work as
expected on older versions. Refer to Features that are compatible with vWorkspace Connectors for more
details.
Feature compatibility matrix for vWorkspace

Connectors
The following table shows the features that are compatible with vWorkspace Connectors.
Table 10. Features that are compatible with vWorkspace Connectors
Connector feature Windows Mac OS X2 Java Linux iOS2 Android Thinshell1 HTML5
Connector YES YES N/A YES YES YES N/A
Management
Auto-Configuration YES YES N/A YES YES YES N/A
Connection YES YES YES YES YES YES YES YES
Brokering
Flash Acceleration YES YES NO YES YES NO

Graphics YES YES YES YES YES YES YES NO
Acceleration
WAN Acceleration YES YES YES YES YES YES YES NO
Audio YES NO NO YES NO NO YES NO
vWorkspace YES YES NO YES NO NO YES NO
MultiMonitor
Universal Print YES YES NO NO NO NO YES NO
(Universal Driver)
vWorkspace 8.6.3
36
Universal Print YES YES YES YES YES YES YES NO
(Network Printers)
Universal USB YES NO NO YES NO NO YES NO
TS/RDSH YES NO NO NO NO NO YES NO
USB Redirection
Reconnect on YES YES YES YES YES YES YES NO
Disconnected
Session
RemoteFX Remote YES NO NO NO NO NO NO NO
Audio
Microsoft Multi YES NO NO NO NO
Monitor
Microsoft YES YES NO NO NO NO NO NO
RemoteApp
Microsoft YES YES NO YES YES YES NO NO
RemoteFX
RemoteFX Media YES NO NO NO NO NO NO NO
Streaming
Seamless Windows YES NO NO NO NO NO NO NO
Web Access YES YES YES YES YES YES YES YES
Desktop Size YES YES YES YES YES YES YES NO
Color Depth YES YES YES YES YES YES YES NO
Connection Bar YES YES YES YES YES NO
Full Screen YES YES YES YES YES
Disk Drives YES YES YES YES NO NO YES NO
Printing (native YES YES YES YES NO NO YES NO
RDP)
Clipboard YES YES YES YES NO NO YES YES
Serial Ports YES YES NO YES NO NO YES NO
Kerberos/Network YES YES NO YES YES YES YES NO
Level
Authentication
Smart Card/CAC YES NO NO YES NO NO YES NO
Support
Pass-through YES NO NO NO NO NO YES NO
Authentication
Secure Access YES YES YES YES YES YES YES YES
service Support
Two-factor YES YES YES YES YES YES YES NO
Authentication *
Enhanced On- N/A N/A N/A N/A YES N/A NO
Screen Mouse
Enhanced N/A N/A N/A N/A YES YES N/A NO
Keyboard
Email log files N/A N/A N/A N/A YES YES N/A NO
Direct RDP N/A N/A N/A N/A YES YES N/A NO
Connection
vWorkspace 8.6.3
37
Native gesture N/A N/A N/A N/A YES YES N/A NO
support
RemoteFX N/A N/A N/A N/A YES YES N/A NO
MultiTouch
ThinShell relies on the installed version of the Windows Connector.

1.
2.The Mac OS X and Linux Connectors achieve universal printing by using the MS Publisher
print driver on the Windows Remote Desktop to create a postscript print stream that is
redirected to the local printers.
vWorkspace version compatibility matrix by role

If upgrading a large vWorkspace environment cannot be done in a short time period, parts of the environment
can be upgraded first, and others can be updated later. It is important to know which roles or features of
vWorkspace are backwards compatible.
The following roles are backwards compatible with a vWorkspace environment:
Table 11. Roles that are backwards compatible with vWorkspace versions
Feature 8.6.3 8.6.2 8.6.1 8.6 8.5 8.0 MR1

Connection Brokers YES YES YES NO NO NO
Management Console YES YES YES NO NO NO
Monitoring and Diagnostics YES YES YES NO NO NO
Monitoring and Diagnostics Agent YES YES YES NO NO NO
Manager
Reporting YES YES YES NO NO NO
Broker Helper Service YES YES YES NO NO NO
TS/RDSH YES YES YES YES YES YES
User Profile Management Server YES YES YES YES YES YES
Universal Print Server YES YES YES YES YES YES
Remote Site Relay Server YES YES YES YES YES YES
Secure Access service YES YES YES YES YES YES
Web Access YES YES YES YES YES YES
Password Reset YES YES YES YES YES YES
Virtual Desktop Extensions (PNTools) YES YES YES YES YES YES
Connector for Windows YES YES YES YES YES YES
Web Access YES YES YES YES YES YES
1. The Management Console role is installed by default with this role but cannot be used to manage the
environment. The environment must be managed on a server that has been fully upgraded.
2.Secure Access service in vWorkspace 7.6 introduced a higher mode of security called Connection Broker
Authentication. Static PIT files (saved PIT) cannot be used to connect to vWorkspace sessions through a
Secure Access service if you enable Forced Broker Authentication on the Secure Access service.
3. Web Access continues to run but cannot be configured by the Management Console until the Web Access
role is upgraded.
vWorkspace 8.6.3
38
Upgrade the vWorkspace roles
Use the following procedure to upgrade the vWorkspace roles on each computer in your vWorkspace
environment. The vWorkspace installer automatically update the components associated with the vWorkspace
role installed on the computer.
To upgrade the vWorkspace roles

1 From the downloaded vWorkspace installer package, right click start.exe and select Run as Admin to
start the installer program.
2 When prompted if you want to allow changes to be made, click Yes.
3 On the vWorkspace home window, click Install to start the process.
4 At the Install .NET prompt, click Yes.
5 On the InstallShield Wizard window, click Next.
6 Accept the License agreement, and then click Next.
7 On the Previous Version Detected window, click Upgrade.
8 If prompted that vWorkspace services are running, Select Automatically close and click OK.
9 Click Yes to restart your computer.
10 On the Login window, log in using the same credentials that you used when you started the upgrade
process.
11 On the Install window, click Next.
12 Accept the License agreement, and then click Next.
13 On the Customer Information window, enter the appropriate information, and click Next.
14 On the Custom Setup window, the roles installed on your computer are selected. If you want to upgrade
the computer as it is, click Next. If you want to add or remove a role from the server, select or de-select
the role, and then click Next.
To upgrade the Monitoring and Diagnostics role

The Monitoring and Diagnostics role can be upgraded using the vWorkspace Installer. The minimum version of
vWorkspace Installation required is vWorkspace 8.0.
NOTE: The Monitoring and Diagnostics Role was previously called the Foglight for Virtual Desktops Role (in
vWorkspace 8.0 and 8.0 MR1).

2 Run start.exe on the target computer. You are prompted to upgrade.
vWorkspace 8.6.3
39
Figure 16. Previous Version Detected window
3 Click Upgrade.
Figure 17. Files in Use window
4 On the Files in Use window, click OK.

IMPORTANT: When upgrading from vWorkspace 8.0, the Uninstall Foglight for Virtual Desktops prompt is
displayed. Click No.
5 On the Installer Information dialog, click Yes.

6 When the server is restarted, the Welcome to the InstallShield Wizard for vWorkspace window is
displayed. Click Next.
7 On the Licensing window, accept the licensing terms and click Next.
8 On the Custom Setup window, ensure that the Monitoring and Diagnostics Role is selected and click Next.
vWorkspace 8.6.3
40
Figure 18. Current Database Configuration window
9 On the Current Database Configuration window, select Keep the existing database configuration and
click Next.
10 On the Database Schema Upgrade window, click Next.
11 On the Installing vWorkspace window, wait until the installation finishes and click Finish.
Upgrade other vWorkspace components

vWorkspace has other components that are installed using separate installers. These components are the
Connectors, VDI Extensions (PNTOOLS), Broker Helper Service and the Instant Provisioning Service. To upgrade
these vWorkspace components, run the corresponding installer and follow the instructions provided.
If the environment uses template virtual machines to provision VDI desktops or RDSH servers, upgrade the
software installed on the template virtual machines. This may include VDI Extensions (PNTOOLS), vWorkspace
TS/RDSH Role and Instant Provisioning Service. After upgrading, new and re-provisioned virtual machines run
the upgraded software.
For existing VDI desktops that are not going to be re-provisioned, upgrade VDI Extensions by selecting the VDI
desktop in the Management Console under Locations | [Location Name] | Desktops | [VM Group]. On the
Desktops tab, right click on the VDI Desktop and select PNTools & other MSI packages | PNTools | Install/Update.
vWorkspace 8.6.3
41
3
The Management Console
• About the Management Console

• Setting up your environment using the Quick Start Wizard
• The Management Console interface
• The Welcome window
• The Management Console Menu
• Managing a vWorkspace environment
• Defining targets
• User Environment Management
• User Profile Management
• Application layering
• Packaged Applications
• Load Balancing
• Web Access
• Monitoring and Diagnostics
About the Management Console

The vWorkspace Management Console provides database management and administrative functions to
vWorkspace administrators.
Install the Management Console on any device that can connect to the vWorkspace database. Most functions
performed by the Management Console can be done from any computer, but registry tasks or applying virtual
memory optimizations must be performed from the console of the affected server.
Apply Hotfixes that affect the Management Console to all installed instances.
CAUTION:Multiple instances of the Management Console can be used simultaneously. Your
changes may interfere with changes made by another administrator.
Setting up your environment using the

Quick Start Wizard
When you initially open the Management Console, the Quick Start Wizard appears. The Quick Start Wizard
allows you to set up a vWorkspace environment through a guided process.
The wizard navigates you through the process of creating a functional vWorkspace environment.
You can choose from the following types of environments:
• Setting up a desktop cloud environment
• Setting up a virtual desktop environment
• Setting up an RDSH environment
• Setting up a blade PC environment
vWorkspace 8.6.3
42
As you progress through the Quick Start Wizard, the information entered on each form is validated. Information
is saved and can be used in future setups.
TIP: Items that are check marked in the Quick Start Wizard are set as global
items. Upon logoff, the profile is deleted and only the checked items are
retained. Keep this in mind if you are importing desktops with a local profile
that you want to retain.
Setting up a desktop cloud environment

Computer groups created through the Desktop Cloud Quick Start Wizard are automatically configured with
provision-time and connection-time load balancing. Auto-size and virtual desktops are deleted at logoff. Along
with HyperCache, HyperDeploy, and Instant Provisioning, these Hyper-V computer groups provide a platform
where desktops can be moved in and out of the cloud.
To set up a desktop cloud environment

1 From the Quick Start Wizard, select the type of environment you want to configure.
2 Add a connection broker.
3 Add Hyper-V Hosts to the current location.
4 Specify a desktop cloud.
5 Specify the desktop cloud size.
6 Specify the provisioning settings.
7 Set up optional user settings such as managed user profiles, printers, and automated tasks.
8 Finish from the wizard.
Setting up a virtual desktop environment

From the Virtual Desktops Quick Start Wizard, you can add virtual desktops by creating new virtual computers,
publishing applications and desktops, and configuring user environments.
The Virtual Desktops Quick Start Wizard supports provisioning of new virtual computers on Microsoft Hyper-V,
Microsoft SCVMM, VMware vCenter Server, and Parallels Virtuozzo virtualization platforms.
To set up a virtual desktop environment

3 Select the virtualization platform.
4 Add virtualization hosts to the current location.
5 Specify a managed desktop group.
6 Add or import computers to the managed desktop group.
7 Set up optional user settings such as managed user profiles, printers, and automated tasks.
Setting up an RDSH environment

The Remote Desktop Session Host Quick Start Wizard allows you to configure a session host environment. You
can publish applications and desktops, configure access control, experience optimization, and manage user
profiles.
vWorkspace 8.6.3
43
To set up an RDSH environment
2 Add a Connection Broker.
3 Specify a Remote Desktop Sessions Host.
4 Create Managed Applications.
5 Set up optional user settings such as Managed User Profiles, Printers, and Connection Policies.
Setting up a blade PC environment

You can use the Blade PCs Quick Start Wizard to build an environment for managing session hosts on blade PCs
or other physical computers.
To set up a blade PC environment

3 Specify a managed desktop group.
4 Add computers to the managed desktop group.
5 Set up optional settings such as network drive mappings, automated tasks, and printers.
The Management Console interface

The vWorkspace Management Console has a graphical user interface that includes a menu bar, toolbar,
navigation pane, and an information pane.
The vWorkspace infrastructure is displayed in a treeview format in the Navigation pane. It includes several main
nodes, which allow you to perform setup and maintenance on the vWorkspace environment.
vWorkspace 8.6.3
44
Figure 19. The Management Console interface
Menu Bar Navigation Pane
Information /Detail Pane
Toolbar
Object
Nodes
The Welcome window

The Welcome window is displayed when you open the Management Console. From this window you can access
the Getting Started Panel (which includes the Quick Start Wizard and documentation), items you recently
accessed in the Management Console, and useful links such as home pages and technical support.
Software Improvement Program

Upon initial start of the Management Console, the vWorkspace Software Improvement Program window is
displayed. You can use this feature to provide anonymous usage data about vWorkspace. You can change your
selection at any time.
To change the Software Improvement Program selection

1 From the Help menu, select Software Improvement Program.
2 On the vWorkspace Software Improvement Program window, select your country or region.
3 Select one of the following:
• Yes, I would like to participate in the Software Improvement Program.
• No, I do not wish to participate at this time.
• Please remind me later.
4 Click OK.
The Management Console Menu

The options on the Management Console menu bar allow you to perform administrative tasks with your
vWorkspace environments. The menu items are described in the following sections.
Using the File menu

The File menu options allow you to manage a vWorkspace environment:
• Viewing current user sessions
vWorkspace 8.6.3
45
• Administration
• Licensing
• Database configuration
Viewing current user sessions

The Current User Sessions window allows you to view active user sessions, license information, and product
usage.
To view current user sessions

1 Select File | Current user sessions to open the Current User Sessions window.
2 Use the scroll bar at the bottom of the window to see additional information.
3 Click Close.
Remote assistance support options

Figure 20. Remote assistance support options
To enable Remote Assistance

Before you can use remote assistance, it must be enabled.
1 Navigate to Locations| Properties | RDP Connection Restrictions. The RDP Connection Properties
dialog box is displayed.
2 Select Enable RDP Remote Administration Control.
3 Click OK. The Remote Assistance feature is available for use in the vWorkspace Management Console.
To Remote Assist a live user session

Remote assistance can only be used when initiated from one RDP session to another. A warning message
indicates when this functionality is not available.
Remote assistance is not supported on computers running RDP8 (Windows Server 2012, Windows 8 and
potentially Windows 7 Service Pack 1 with the RDP8 Client installed).
TIP: Because of a Microsoft platform limitation, remote assist is not supported on
computers running RDP8 (Windows Server 2012, Windows 8 and potentially
Windows 7 Service Pack 1 with the RDP8 Client installed).
1 Open the vWorkspace Management Console.

2 Select Location | Select a location | Desktops | Select a Desktop.
vWorkspace 8.6.3
46
3 Select the Desktops tab in the information pane and right-click on the computer. Select Remote Control
| Remote Assistance.
This option is unavailable for inactive sessions.
4 In the Remote Control dialog box, set the key command that you want to use when you want to end the
remote session.
5 Click OK. The session is displayed.
6 Use the key command when you want to exit the session.
Accessing remote desktops

The Remote Control feature allows you to access a remote desktop. vWorkspace provides the following remote
control features:
• To access a remote desktop using RDP
• To access a remote desktop using Microsoft Hyper-V
• To access a remote desktop using VMware
To access a remote desktop using RDP

Remote control can only be initiated from one RDP session to another. You can use Remote Desktop to log into a
user’s desktop and view the desktop parameters without accessing the user’s session.
2 Select Location | <Select a location> | Session Hosts.
3 Highlight the session host or computer group to which the computer belongs.
4 Select the Desktops tab in the information pane and right-click on the computer.
5 Select Remote Control | Remote Desktop.
6 On the Remote Desktop dialog box, select the screen size you want to display for the remote session, and
click Connect to Console/Admin Session if needed. Click OK.
7 Log into the desktop when prompted.
8 Perform the necessary administrative tasks on the user’s desktop.
9 Close the remote desktop when finished.
To access a remote desktop using Microsoft Hyper-V

Use Hyper-V to log into a user’s desktop and view the desktop parameters without accessing the user’s session.
Using Hyper-V allows you to connect without RDP.
4 Select Remote Control | Hyper-V VMConnect.
To access a remote desktop using VMware

Use VMware to log into a user’s desktop and view the desktop parameters without accessing the user’s session.
VMware allows you to connect without RDP.
vWorkspace 8.6.3
47
4 Select Remote Control | VMware Connect.
Administration
Until an administrator account is added, any user with administrator privileges will have full access rights to the
Management Console. It ensures that the current Microsoft Windows user is also a local Microsoft Windows
administrator.
The first administrator defined in the system is automatically is defined as a system administrator, and the last
administrator to be removed from the system must be a system administrator. This prevents inadvertent
lockouts.
A system administrator can modify permissions for any user or group. Non-system administrators cannot set
their own permissions or the permissions of a group to which they belong.
When you assign a user as an administrator, you can assign one of the three initial permissions: Allow All, Deny
All, or Copy From Existing. These permissions can be changed later.
The permissions structure is hierarchical and follows a parent-child relationship model. Child objects inherit
permissions from the parent if the permissions for the child object are not set explicitly.
An administrator can be assigned conflicting permissions. This happens if an administrator belongs to more than
one group and the groups have been assigned conflicting allow/deny permissions for the same object. The
resolution of these conflicts is governed by the Settings page of the vWorkspace Administration dialog box. You
can choose whether to allow or deny the permission when a conflict occurs.
Permission check boxes may be one of the following. The gray checkmarks indicate that the permission is
inherited from its parent if set. Permissions that are disabled for an administrator cannot be modified by that
administrator.
Table 12. Permissions check boxes
Enabled, permission not set.

Check box has white background.
Enabled, explicit permission set.

Enabled, inherited permission set.

Disabled, permission not set.

Check box has gray background.
Disabled, explicit permission set.

Disabled, inherited permission set.

To add a system administrator

2 Select File | Administration.
vWorkspace 8.6.3
48
3 On the Administrators step, click Add User/Group.
4 On the Administrator Wizard window, click Next.
5 On the User/Group Name step:
a Select User or Group, and then enter Domain\User or Domain\Group.
Use the ellipsis button to assist in selecting users or groups.
b Select the check box to indicate that this user or group is a system administrator.
(If no other system administrators are defined, then this check box is required, and will be selected by
default.)
c On the Select Users step, click OK.
6 On the User/Group Name step, click Finish.
7 From the login prompt, log in as the new system administrator.
The new administrator is displayed in the Administrators step. The Settings and Permissions for the
system administrator are set by default and cannot be changed.
8 Click OK to close the window.
To add a (non-system) administrator

3 On the Administrators step, click Add User/Group.
4 On the Welcome step, click Next.
5 On the User/Group Name step:
a Select User or Group, and then enter Domain\User or Domain\Group.
Use the ellipsis button to assist in selecting users or groups.
b Ensure that the check box is not selected, indicating that this user or group is a not a system
administrator.
c Click Next to display the Initial settings step.
6 On the Initial settings step, select one of the default permission settings, Deny All, Allow All, or Copy
from, and then click Next.
Use Copy from to quickly set the initial permissions of a new administrator to those of an existing non-
system administrator.
7 On the Permissions step, make any changes to the Allow and Deny columns, and click Finish.
The Administrators step appears, showing the new administrator.
To edit administration settings

3 Click Properties to display the Administrator properties step.
4 Edit as appropriate, and then click Apply.
5 Click OK to close the step.
To remove an administrator
vWorkspace 8.6.3
49
3 Highlight the user or group name from the list.
4 Click Remove.
5 On the Confirmation step, select Yes.
6 Click OK to close the window and save your changes.
Licensing
vWorkspace can be licensed per named user, per access device, per concurrent user and on a subscription basis
(from Dell service provider channel partners).
There are two types of vWorkspace licenses available:
• vWorkspace Premier Edition. Supports both VDI and RDSH integration with vWorkspace. You can use this
edition to deliver published desktops and applications with seamless windows from any Microsoft
Windows operating system hosted on remote session hosts, a hypervisor, such as Hyper-V, or ESX. 
The Premier edition also includes Wyse Streaming Manager (WSM). This provides Server and Client
operating system image streaming and application layering. It also includes vWorkspace Monitoring and
Diagnostics.
• vWorkspace Desktop Edition. Supports only VDI and blade PC deployments with vWorkspace. You can
use this edition to deliver published desktops and applications with seamless windows from any Microsoft
Windows operating system hosted on a hypervisor, such as Hyper-V, or ESX. With this edition, you cannot
configure and deploy RDSH environments.
To add licenses
When you launch the Management Console for the first time, the Licensing window appears if there are no
references to licensing in the vWorkspace database. If your vWorkspace database has references to licenses, you
can manage your licenses from the Management Console.
The process is the same for both a Simple or Advanced vWorkspace installation.
2 From the File menu, select Licensing.
3 Select the Licenses option.
4 Click the Add License button.
5 Browse to the location of your Licenses ASC file.
6 Select the file and click Open.
7 On the message window stating the license has been added, click OK.
8 Click Close.
To view licenses
The Licenses window also allows you to view current licenses.
2 From the File menu, select Licensing to display the Licensing window.
3 Select the Licenses option.
4 Click the tabs to view the licenses. Importing a license file will replace any already imported license of
the same type (Premier or Desktop). If you want to import both a Premier and Desktop license you can
use the Licensing page, which allows up to two ASC files to be added.
• License 1 and License 2.View licenses that have been acquired from the Licensing Management
System (LMS). Licenses retrieved from LMS are ASC files. All new licenses are received in this file
format. The Licensing page allows up to two ASC files to be added.
vWorkspace 8.6.3
50
• Other Licenses. View existing licenses that have been previously acquired from the vWorkspace
web site.
• User limits. Specify a maximum number of concurrent users that can be set by vWorkspace
environment.
5 To view licenses for the current user sessions:
a Click the User Sessions option in the left pane.
b Click the User Sessions button. The Current User Sessions window is displayed.
c Click Close to return to the Licensing window.
6 Click Close to exit the Licensing window.
Database configuration
The vWorkspace database is configured during installation, but you can define additional database connections
at any time. When the Management Console is started, it looks to the Windows Registry for a pointer to a
System Data Source Name (DSN) and uses the settings contained in the DSN to connect to the vWorkspace
database.
The Configure vWorkspace Database window opens when the Management Console is started and a DSN has not
been defined, or if the data in the DSN is invalid.
To create a new database and DSN

1 Open the vWorkspace Management Console on a vWorkspace Connection Broker or an administrative
computer.
2 Select File | Database Configuration.
3 On the Configure vWorkspace Database step, click Database Configuration.
4 On the Action step, select Create new vWorkspace database, and then click Next.
5 On the Database Information step, specify the following parameters, and then click Next.
Table 13. Database Information fields
New database • Enter the Server name of the SQL server

where the database is to be created.
If you are using MSDN or SQL Express, use the
format:
server_name\instance_name
• Enter a Database name, or accept the
default name, vWorkspace_Database.
New data source name • Enter a Name for the DSN or accept the
(DSN) default name.
• Enter a Description for the DSN or accept
the default.
6 On the Credentials window, enter an existing SQL administrator login for the specified server and a new
vWorkspace SQL login.
7 Click Finish.
To connect to an existing database

After the vWorkspace database is created, configure DSNs on all servers with vWorkspace components that
require database connectivity.
1 Start the vWorkspace Management Console from the additional Connection Broker or administrator
computer.
vWorkspace 8.6.3
51
2 Select File | Database Configuration.
3 On the Configure vWorkspace Database step, click Database Configuration.
4 On the Action step, click Connect to an existing vWorkspace database, and then click Next.
5 On the Database Information step, specify the following parameters, and then click Next.
Table 14. Database Information fields
Existing database • Enter the Server Name of the SQL server

where the database is to be created.
If you are using MSDN or SQL Express, use the
format:
server_name\instance_name
• Enter the name of the database.
New data source name • Enter a Name for the DSN.
(DSN) • Enter a Description for the DSN.
6 On the Credentials step, enter the existing vWorkspace SQL login name and password, and click Finish.
Actions menu
The options available from the Actions menu depend on the item selected in the navigation pane of the
Management Console. Some of the items include:
• Show/Hide Advanced RDSH Tools. Showing the Advanced RDSH Tools will display additional nodes
for the environment: Performance Optimization, Virtual IP and File & Registry Redirection.
• Properties. Opens the Properties window for the selected node.
Help menu
The Help menu provides you with additional resources that you can access while using the Management Console.
• vWorkspace Community
• Search vWorkspace Knowledge base
• Contact Dell Support
• vWorkspace Home Page
• vWorkspace Blog
• Find vWorkspace Hotfixes
• vWorkspace Documentation
• Monitoring and Diagnostics Documentation
• Software improvement program
• About
vWorkspace 8.6.3
52
Managing a vWorkspace environment
The navigation pane of the Management Console contains a tree structure that organizes the multiple
management tools. Each node of the tree addresses a different management need of the virtual workspace.
The table below provides an overview of the vWorkspace object notes. Refer to the following sections for
detailed information about using these to maintain the vWorkspace environments.
Table 15. vWorkspace object nodes
Node Description
Environment (Farm) name Represents the entire vWorkspace infrastructure.
Locations Organize groups of users based on geographical locations,
within a vWorkspace infrastructure.
Targets Set the criteria for which vWorkspace Resource is applied
and when it is applied to a remote session. Once targets are
defined in the vWorkspace database, they can be used in
Access Control Lists associated with various vWorkspace
Resource objects.
Managed Applications Enable Graphics Acceleration globally for managed and
unmanaged applications, set custom properties, and set
permissions for users for all managed applications.
Connector Management Centrally create and manage the configuration of all of your
vWorkspace Connectors.
User Environment Management Contains the list of items that can be assigned to clients
using Client Assignment.
A toolbar option, Toggle Client Assignment List Display,
allows the client assignment to be displayed at the bottom of
the window, the right-side of the window, or not at all.
User Profile Management User Profiles are used to define storage servers, assign
compression levels, define silos, and assign permissions to
users so that they can be allowed to or denied access to
adding, modifying, or deleting Virtual User Profiles.
Packaged Applications Identify Microsoft Application Virtualization (App-V) servers
and their hosted application packages, and MSI packages.
Performance Optimization Configure CPU Utilization and Virtual Memory Optimization
(Displays only if Show Advanced policies, and to view the results of these policies.
RDSH Tools is enabled from the
Actions menu).
Virtual IP (Displays only if Show Provide special configuration options for applications running
Advanced RDSH Tools is enabled in a multi-user environment that require unique IP addresses
from the Actions menu). for identification.
File & Registry Redirection Provides mechanisms that allow applications to work
(Displays only if Show Advanced properly in a multi-user environment.
RDSH Tools is enabled from the
Actions menu).
Load Balancing Configure load balancing when published applications are
hosted on multiple RD Session Hosts. A load balance can be
assigned to either the published application or the RD
Session Hosts.
Web Access Define and manage Web Access web sites. The configuration
for Web Access web sites is stored in the Management
Console.
vWorkspace 8.6.3
53
Table 15. vWorkspace object nodes
Node Description
Monitoring and Diagnostics Links to vWorkspace Monitoring and Diagnostics. After
entering the URL and credentials, the Monitoring and
Diagnostics console opens, which allows you to generate
detailed reports.
Reporting Allows you to generate reports about various aspects of your
virtual desktops environment.
Overview of the vWorkspace environment

The first node in the navigation pane is the environment, and it represents the vWorkspace infrastructure.
To set up the environment (Farm) properties

Use the following procedure to specify settings for a vWorkspace environment (Farm).
1 Right-click on the environment node and select Farm Properties, to access the Farm Properties window.
2 On the Farm Name step, specify a name for the new farm.
Table 16. Farm Name fields
Field name Description

Farm Name This is the name that is assigned to the
vWorkspace infrastructure. It is stored as a
record in the vWorkspace database and
requires no configuration changes to member
servers.
It can be changed at any time and is
automatically passed on by the vWorkspace
Connection Broker servers to the vWorkspace
clients.
NOTE: Do not use a period (.) in the name.
3 Select Reporting Database, and specify the Reporting Database values. The following settings can be
defined on the Reporting Database step.
Table 17. Reporting Database fields
Data Expiration (days) The age at which reporting data is
automatically purged.
Purge Interval (hours) How often expired data is purged.
4 Select Managed Domains, and set up the managed domains.

The Managed Domains step displays a list of the domains that can be managed in the current farm. The
domains in the Automatic list are automatically populated with the local, trusted domains, and cannot
be modified here or deleted. Trusted domains require a separate installation of the brokering
infrastructure for each organizational unit, domain and forest.
The domains in the Additional list are those that have been added manually. This feature allows you to
provision virtual desktops and RD Session Hosts in domains without the requirement of a two way trust
between the different domains and forests. Items in the Additional list can be modified or deleted.
vWorkspace 8.6.3
54
The following settings can be defined on the Managed Domains step.
Table 18. Managed Domains fields

Add Access the Domain Properties dialog box,
where you can add a new domain. Enter the
properties for the new domain as necessary
(see the Properties field), and click OK.
Remove Select an added domain, and then click the
Remove button to remove it.
Verify Select a domain, and then click the Verify
button to test the connection to the domain.
Properties View or edit the following properties for an
added domain.
• Domain Name
• Unqualified NetBIOS domain name
• DNS Server IP Address
• Account
• Password
• Test Connection to Domain
• Use SSL LDAP
• Ignore server certificate errors
• Use Clear text LDAP
Use SSL LDAP Connect to the domain with a secure
connection.
Ignore Server Certificate Errors Ignore certificate-related errors.
Use Clear Text LDAP Connect to the domain with an unencrypted
connection.
5 Select Authentication and specify the settings for authentication.

The following settings can be defined on the Authentication step. If you use two-factor authentication,
you cannot use credentials pass-through.
See Two-factor authentication on page 158 for more information.
Table 19. Authentication fields

Enable RADIUS Enables the RADIUS options.
Server Name or IP Address Name or IP address of a RADIUS server.
Port Listening port of the RADIUS server.
Secret Key Shared password used to communicate with
RADIUS server.
Timeout Enter amount of time (in seconds) that a
connection is not authenticated before a
session times out.
Authentication type Select between encrypted (CHAP - Challenge-
Handshake Authentication Protocol) and
unencrypted (PAP - Password Authentication
Protocol).
Password Layout Controls the order the Active Directory and
OTP passwords are entered by the user.
vWorkspace 8.6.3
55
Table 19. Authentication fields

One-time password length Inform the Connection Broker the length of the
OTP.
Require all users to be two-factor Overrides all other vWorkspace policies.
authenticated NOTE: You cannot use this option if you have
enabled two-factor authentication in both the
Management Console and WebAccess.
Enable CredSSP Enables CredSSP (Credential Security Support
Provider).
Connector Configuration Require authentication before retrieving
configurations directly from the connection
broker.
6 Select Anonymous Login to enable anonymous login.

You can use the Anonymous Login step to assign vWorkspace resources anonymously, removing the need
for authentication before a user can use a vWorkspace resource (for example, a Managed Application).
This feature is useful in environments where shared workstations are common, such as in healthcare or
education.
Anonymous login does not allow reconnection or session roaming.
TIP: The anonymous user will be a local computer account. Mapping printers to
anonymous users requires that the network printers permissions are set up so
that non-domain users (local users) can map those printers. If you want the user
to be able to use network printers, they must be accessible by non-domain
users.
The following setting can be defined on the Anonymous Login step.

Table 20. Anonymous login field

Enable anonymous login Allow users to connect to this environment
without entering credentials.
7 Select Other Settings to configure the other miscellaneous settings.

The following settings can be defined on the Other Settings step.
Table 21. Other Settings fields
Reset all pop-up messages If selected, this check box resets all of the
pop-up message tips, including the Please do
not show me this message again check boxes,
so that they reappear if necessary.
Clear recent items list Select this check box to reset the list of recent
items on the Welcome screen.
8 Click Apply to save the settings.
Managing locations
The Locations node represents a group of one or more data centers and the desktops within those data centers.
Administrators define Connection Brokers, Session Hosts, Virtualization Hosts, and desktops for each defined
location. Multiple locations can be defined and are typically configured for delegation of administration
purposes.
vWorkspace 8.6.3
56
Locations can be used to group items based upon location or for other management purposes such as
departmental organization and delegated administration.
Locations node options

The following menu options are available from the Locations node by either right-clicking on Locations, or from
the icons in the toolbar when Locations is selected.
• Management servers. Select to open the Management Server step and the Virtualization Server Wizard,
which is used to add virtualization management servers such as Microsoft SCVMM or VMware vCenter. See
Virtualization Platform Integration on page 127 for more information.
• New location. Select to open the New Location wizard used to add a new location.
• Properties. Select to display the Locations properties which includes central settings for Connection
Brokers, Session Hosts, Virtualization Hosts, and Other Settings.
• Refresh. Select to refresh the Locations node view.
To add a location
Connection Brokers and Session Hosts can be defined when adding a location.
Right-click on the Locations node, and select New Location to start the New location wizard.
2 On the Welcome step of the New Location wizard, click Next.
3 On the Location Name step, enter the name for the location, and then click Next.
This is the name that will be displayed in the vWorkspace Management Console.
4 On the Add Servers step, add Connection Brokers to this location:
a Click Add Connection Broker.
b On the Server Wizard, click Next.
c On the Server Name step, enter the name or IP address of the server, and then click Next. Use the
ellipsis button if you want to browse for the server.
d On the Server Role step, specify the roles for the server, and then click Next.
This new server may perform more than one role, such as a vWorkspace Connection Broker and
Microsoft Remote Desktop Connection Broker (RD Broker).
e On the Certificate step, you can optionally specify or view the certificate that is to be used on
this server. Then click Next.
f On the Logging step, select the check box if you want to enable trace logging on this server, and
then click Next.
Typically, logging is only used when assisted by Technical Support.
g If you selected the Microsoft Remote Desktop Connection Broker (RD Broker) option on the Server
Role step, complete the next two steps. Otherwise, skip to Step j to specify Permissions for this
server.
h On the Administrative Account step, specify an administrative account and password for the RD
Broker, and then click Next.
i On the Logging step, select the check box if publishing and resource plug-in logging is to be
enabled on this server, and then click Next.
Typically, logging is only used when assisted by technical support.
j On the Permissions step, specify permissions for this server, and then click Finish.
Before assigning permissions, you must first add users or groups using the New Administrator wizard from
File| Administration.
vWorkspace 8.6.3
57
k On the Add Servers step, click Next to advance to the next step. Or, proceed to the next step to
add session hosts.
5 On the Add Servers step, add a session host to this location:
a Click Add Session Host.
b On the Welcome step of the Server wizard, click Next.
c On the Server name step, enter the name or IP address of the server, and then click Next. Use the
ellipsis button if you want to browse for the server.
d On the Server Role step, select Session Host, and then click Next.
e On the Folder step, specify the folder for this Session Host, if appropriate. Click New Folder to
create a new folder. Click Next when done.
Folders are for organization and display; it does not change the operation of the servers.
f On the Load Balancing step, you can optionally specify the load balancing rule, and then click
Next.
g On the Session Auto-Logoff step, select the setting for session auto-logoff, and then click Next.
h On the Connectivity step, specify an Alternate IP Address, and then click Next.
i On the Experience Optimization step, specify the performance optimizations options to be
j On the Enhanced Audio step, specify whether Enhanced Audio is to be enabled or disabled on this
server, and then click Next.
k On the Virtual IP step, specify the virtual IP settings and then click Next.
l On the Permissions step, specify any permissions for this server and then click Finish to return to
the New Location step.
Before assigning permissions, add users or groups using the New Administrator wizard located at File|
Administration.
6 Click Next to display the Virtualization Hosts step, where you can associate Datacenters, hosts, nodes,
host groups, or clusters to this location by using the Add Entities option.
If you choose to not assign them at this time, click Next. Virtualization Hosts can be added later by right-
clicking on the specific location, and then selecting the Properties option and completing the
information in the Virtualization Hosts section.
See To add Virtualization Server connections on page 128 for more information about adding
virtualization hosts.
7 On the Administrative Account step, you can optionally select Specify default administrative account
and enter an account and password if you want to specify a default administrative account for new
computer groups that are created in this location. Click Next.
8 Use the Permissions step to assign permissions to users or groups.
Users and groups must be added using the New Administrator wizard. See To add a system administrator
on page 48 for more information.
9 Click Finish to save the new location.
To delete a location
Locations can only be deleted after Connection Brokers, Session Hosts, Desktops, and Virtualization Hosts
associated with the location are deleted.
2 In the navigation pane, right-click on the location that is to be deleted.
3 Select Delete Location.
4 On the confirmation message, click Yes.
vWorkspace 8.6.3
58
To edit location properties
Location properties are defined for Connection Brokers, Session Hosts, Virtualization Hosts, and Other Settings.
Location properties are the same for all the locations within an environment.
1 Right click the Locations node and select Properties.
2 On the Locations properties step, modify the properties of the location as necessary. See the following
table for a description of each.
Table 22. Locations properties
Locations Property Description

Connection Brokers
Communication settings Specify the TCP/IP port number that is to be used when listening for
inbound connection requests.
Any port number can be used if it is available on all servers with the
Connection Broker.
Default values are:
• HTTP: 8080
• HTTPS: 443
The HTTP and HTTPS protocols can be used simultaneously. The use of
the HTTPS requires an X.509 digital certificate containing the server’s
FQDN to be installed into the steps computer store of each
Connection Broker.
Bypass proxy settings when communicating with the connection
brokers. If selected, proxy settings are not used when communicating
with Connection Brokers.This setting is selected by default.
Show a statistics web page when connecting to connection brokers
from a web browser. Enabling this will display a Statistics web page
when users connect to a connection broker from a web browser.
The Ticket Expiration setting is used to specify the expiration time
for tickets that are sent to the Connection Broker when applications
are launched.
The default for the Ticket Expiration setting is 1 minute.
License pool Enter a number of minutes to define update interval, which is the
number of minutes the Connection Broker servers update license
usage information.
Session hosts
Session auto-logoff This policy is for users that start published applications and not full
desktops. If enabled, vWorkspace automatically logs off when the last
published application is closed. This eliminates the potential issue of
applications remaining in memory, and never really terminating.
Enter a module name for a process. If the process with the module
name persists after the session has been closed, then the session is
automatically logged off.
To add a process, click Add.
To delete a process from the use, highlight the process and click the
red X.
RDP connection restrictions Enable RDP remote administration control. Select this option to
enable remote administration control. This is across the environment
and is disabled by default.
Hyper-V Catalyst components
vWorkspace 8.6.3
59
HyperCache Enable vWorkspace HyperCache. Enable this feature to improve
performance and reduce IOPS requirements for the Hyper-V host.
Total cache size (MB) sets the default cache size for a parent VHD,
and can be overridden for individual parent VHDs.
VDI boot cache size. Specify a percentage of the total cache of the
boot cache to optimize VDI performance at boot time.
NOTE: If you specify a percentage that is not recommended for the
values you entered, a warning button is displayed. Click the warning
button to see the recommended percentage.
Cache lifetime. Sets the amount of time before unused data is purged
from the VDI and RDSH templates.
NOTE: Disabling HyperCache and changing the cache size can be done
on a per Hyper-V-host-basis from the Properties window of a Hyper-V
host in the Management Console.
HyperDeploy Approximate bandwidth usage. Select an approximate bandwidth to
be used by HyperDeploy when copying parent VHDs to local hosts.
Enabled HyperDeploy advanced storage optimization. Select this
option to allow vWorkspace to optimize the way virtual computer files
associated with vWorkspace-provisioned virtual desktops are stored.
Diff disk storage optimizations Select a setting for overcommitting differencing disk storage.
MAC address management Allow vWorkspace to manage virtual computer MAC addresses.
Select this option to generate and assign MAC addresses for Hyper-V
virtual computers.
Base address. Specify the base MAC address to use as the starting
point for new computers.
Auto-size settings Limit the number of new computers per auto-size iteration. Select
this option to specify the maximum number of computers that
vWorkspace creates in a single iteration of auto-sizing a group.
Number of computers. Select the appropriate number of computers.
Other settings
Computer timing settings Heartbeat interval. Specifies how often the Data Collector Service on
managed computers sends status information to the Connection
Broker.
Offline count. Specifies the number of missed heartbeats before a
managed computer is considered offline.
Offline retry. Specifies how often the Connection Broker attempts to
contact an offline managed computer.
Inactivity timeout. Specifies how long a managed computer is logged
off before it is considered inactive and automatically placed into a
Suspend state.
Logon attempts. Specifies now many bad logon attempts are allowed
before the virtual desktop is placed into a failed-logon state.
Sysprep period. Specifies how long the system waits during the
system preparation operation before attempting to initialize the
computer.
Host Timing Settings Heartbeat interval. The frequency hosts send status information to
the Connection Broker.
Offline count. Number of missed heartbeats before a host is
considered offline by the Connection Broker.
Offline retry. How often the Connection Broker attempts to contact
an offline host.
vWorkspace 8.6.3
60

Task & Log Settings Task history. Age at which completed task records are automatically
deleted.
Task display expiration. Age at which the current or most recently
executed task on a managed computer is no longer displayed in the
desktop list.
Log history. Age at which log records are automatically deleted.
Active Directory Credentials Specify global delete credentials. Use this setting to add
administrative credentials that can be used to delete a computer
from Active Directory.
Enter account and password credentials that are to be used to remove
computers from Active Directory.
NOTE: If a computer cannot be removed from Active Directory using
these credentials, then the system attempts to use the computer
group administrative credentials.
Permissions property
Permissions Enter users or groups and then set permissions to Allow or Deny for
the following:
• Add Locations
• Add Virtualization Servers
• Delete Locations
• Delete Virtualization Servers
• Modify Locations
• Modify Virtualization Servers
3 Click OK to save the new settings.
Setting up Connection Brokers for a location

The Connection Broker is a central component in a vWorkspace environment. A connection broker does much
more than just broker connections and must be added to an environment before any connections to the virtual
workspace can be made. Some of the responsibilities of the vWorkspace Connection Broker include:
• Manages most communication within an environment.
• Integrates with virtualization platforms to provision and manage new workspaces.
• Provides native load-balancing.
• Brokers connections from vWorkspace Connectors to the vWorkspace infrastructure and responds to
client connectivity requests and redirects the client to an appropriate virtual workspace.
NOTE: To add a vWorkspace Connection Broker server to the Management Console, the
vWorkspace Connection Broker role must be installed and configured to
communicate with the environment management database.
Connection Broker registry settings

The following registry settings can be set up for the connection broker.
Session Roaming Mode
vWorkspace 8.6.3
61
This option allows users to move between stations without disconnecting their session. The setting would be
useful in a health care environment.
When enabled, the vWorkspace Connection Broker looks for both active and disconnected sessions when a user
issues a launch request.
This enforces one user session per farm, and allows a user to roam, being able to return to their active session
from any terminal. The default setting is 0.
HKLM\SOFTWARE\Provision Networks\Common\Load and License Manager
SessionRoamingMode REG_DWORD (0=disabled 1=enabled)
Deferred Authentication
An optional mode to retrieve applications and desktops through vWorkspace Connector for Windows
and Web Access, even by users whose passwords have expired or need to be changed.
Account Locked Pass Through mode

When this feature is enabled, it allows the user, whose account appears to be locked, to get to the Windows
logon screen to unlock the account. A third party password reset application is needed to use this setting.
When enabled, if LogonUser() returns the following error code, the vWorkspace Connection Broker enumerates
the groups and OUs for the user and returns ERROR_SUCCESS (0).
ERROR_ACCOUNT_LOCKED_OUT (1909)
This feature is controlled though the following registry key. The default is 0.
HKLM\SOFTWARE\Provision Networks\Common\ Load and License Manager
AccountLockedPassthruMode REG_DWORD (0=disabled 1=enabled)
Password Expired Pass Through mode
Enabling this feature allows users to access the Microsoft Windows logon screen to change an expired password
or to change a password.
When enabled, if LogonUser() returns the following error code, the vWorkspace Connection Broker enumerates
the groups and OUs for the user and returns ERROR_SUCCESS (0).
ERROR_PASSWORD_EXPIRED (1330) and ERROR_PASSWORD_MUST_CHANGE (1907)
This feature is controlled through the following registry key. The default is 0.
HKLM\SOFTWARE\Provision Networks\Common\ Load and License Manager
PasswordExpiredPassthruMode REG_DWORD (0=disabled 1=enabled)
This section includes procedures for the following:
• To add connection broker servers
• To set up Connection Broker properties
• To remove Connection Broker servers
To add connection broker servers

1 From the vWorkspace Management Console, expand the Locations node
2 Expand the location that you want to add Connection Broker to.
3 Right-click on Connection Brokers, and then select New Connection Broker.
4 On the Add Connection Broker step, select the New Server check box, and click OK.
5 On the Server Wizard step, click Next.
6 On the Server Name step, enter the server name (NetBIOS), and then click Next. Use the ellipsis button
to browse for the server.
The text box is limited to 15 characters, the maximum allowed in NetBIOS naming conventions.
vWorkspace 8.6.3
62
7 On the Server Role step, specify the role or roles for the server, and then click Next.
A server can perform more than one role; for example, a vWorkspace Connection Broker and Microsoft
Remote Desktop Connection Broker (RD Broker).
8 If you selected the vWorkspace Connection Broker role on the Server Roles step, then on the Certificate
step, specify or view the certificate that is to be used on this server, and then click Next.
9 On the Logging step, select the check box if trace logging is to be enabled on this server and then click
Next.
Typically, logging is used only when assisted by Technical Support.
10 If you selected Microsoft Remote Desktop Connection Broker (RD Broker), complete the next two steps. If
not, then continue to Step 13 to specify permissions for this server.
11 On the Administrative Account step, specify an administrative account and password for the RD Broker,
and then click Next.
12 On the Logging step, select the check box if publishing and resource plug-in logging is to be enabled on
this server, and then click Next.
Typically, logging is only used as assisted by Technical Support.
13 On the Permission step, specify any permissions for this server, and then click Finish.
In order to assign permissions, you must first add users or groups using the New Administrator wizard
located at File| Administration.
To set up Connection Broker properties

After Connection Brokers have been added to a location, set the properties as appropriate.
1 Under the location in which you want to add the permission, right-click on the Connection Brokers node
and select Properties.
2 On the Connection Broker Properties step, select the Permissions tab.
3 Highlight the user or group.
4 Set the Permissions to Allow or Deny.
5 Click Apply to save your changes, and then OK to close the window.
To remove Connection Broker servers

Removing a Connection Broker deletes its associated records within the vWorkspace database, but it does not
uninstall any of the vWorkspace components or any other software on the server, nor does it change its database
configuration (DSN).
1 In the navigation pane of the vWorkspace Management Console, expand the Connection Brokers node,
and select the Connection Broker sever that is to be removed.
2 Right-click on the Connection Broker, and select Delete Server from the context menu.
3 Click Yes to complete the removal.
Setting up session hosts for a location

Session hosts need to have the TS/RDSH role installed and configured to communicate with the vWorkspace
Management Database before it can be added to the vWorkspace Management Console.
• To add session hosts
• To set up session host properties
• To delete session hosts
vWorkspace 8.6.3
63
To add session hosts
1 From the Management Console, navigate to Locations | Session Hosts | Management.
2 Right-click on Management, and then select New Session Host.
3 In the Add Session Host step, select <New Server> and click OK.
4 On the Welcome step of the Server wizard, click Next.
5 On the Server Name step, enter the server name (NetBIOS), and then click Next. Use the ellipsis button
to browse for the server.
The text box is limited to 15 characters, the maximum allowed in NetBIOS naming conventions.
6 On the Server Role step, specify the Session Host, and then click Next.
7 On the Folder step, specify the folder for this Session Host. Click New Folder to create a new folder.
Click Next when complete.
Folders are for organization and display; it does not change the operation of the servers.
8 On the Load Balancing step, accept the default load balancing rule or select to specify a custom load
balancing rule, and then click Next.
Additional custom load balancing rules can be created from the Load Balancing node of the vWorkspace
Management Console.
9 Click Next to inherit the global exception list for Session Auto-logoff.
Or select Specify the exclusion list to create an exclusion list specific to this Session Host, and then
click Next.
TIP: The default processes that are part of exclusion list are: alg.exe, csrss.exe,
ctfmon.exe, dwm.exe, getflash.exe, ie4uinit.exe, userinit.exe,
pndmhelper.exe, pngdiagt.exe, pngdilic.exe, pnlteagt.exe, pnsenapp.exe,
pnssosvr.exe, pnstart.exe, proquota.exe, rdpclip.exe, rdpinit.exe,
rdpshell.exe, servermanagerlauncher.exe, sftdcc.exe, splwow64.exe,
svchost.exe, taskeng.exe, taskhost.exe, VMwareTray.exe, VMwareUser.exe,
winlogon.exe, wisptis.exe, wmiprvse.exe, wscntfy.exe, wuauclt.exe,
PNMicSessionRedir.exe, tlsbln.exe, taskhostex.exe, rundll32.exe,
PNFMMRRouter.exe.
10 On the Connectivity step, complete the following information, and then click Next.
Table 23. Connectivity fields
Connections Select the Accept least busy

connection requests check box if
you want the server to participate
in load balancing.
Alternative IP Address Enter an alternative IP address.
11 On the Performance Optimization step, specify the performance optimizations options that are to be
12 On the Experience Optimization step, specify the experience optimization settings for this server, and
then click Next.
For more information about WAN Acceleration, see the Experience Optimizations on page 215.
13 On the Licensing step, specify licenses, and then click Next.
14 On the Permissions step, specify any permissions for this server, and then click Finish.
You must first add users or groups using the New Administrator wizard located at File| Administration.
vWorkspace 8.6.3
64
To set up session host properties
When Session Hosts have been added, you can set properties to apply to all servers in the vWorkspace
environment that have the Session Host role.
1 Under the location (Locations | <location>) in which you want to add the permission, right-click on the
Session Hosts node, and then select Properties.
2 On the Session Host Properties step, highlight the user or group, and then change the Permissions to
Allow or Deny.
For more information about permissions, see Administration on page 48.
3 Click Apply to save your changes, and then OK to close the step.
To delete session hosts

Use the following steps to remove a Session Host from inclusion in the vWorkspace infrastructure. Removing a
Session Host deletes its associated records within the vWorkspace database, but it does not uninstall any of the
vWorkspace components or any other software on the server nor does it change the database configuration
(DSN).
1 In the navigation pane of the vWorkspace Management Console, expand the Session Hosts node, and
select the Session Host that is to be removed.
2 Right-click on the server and select Delete Server from the context menu.
3 On the Confirmation step, click Yes to complete the removal.
To manage users connected to session hosts

1 To view connected users:
a Open the vWorkspace Management Console.
b Expand the Locations node.
c Expand the location of the Session Host.
d Expand the Session Hosts node.
e Expand the Management node.
f Double-click the Session Host.
g Select the Users tab.
The following information can be viewed:
Table 24. User information
Domain The NetBIOS name of the steps domain to which the

user’s account belongs.
Session The name of the user’s session as assigned by the
Session host.
User The user account name used to log on to the session.
Session ID The numerical session ID assigned to the user’s
session by the Session Host.
State The state of the Session Host session. The options
are:
• Active
• Disconnected
• Idle
• Down
vWorkspace 8.6.3
65
Table 24. User information
Idle time The amount of time no activity has occurred between
the client and the Session host.
Logon time The date and time the session was logged on.
2 To connect to a specific Session Host: From the Management node, double-click on a Session Host object.
3 To connect to all Session Hosts: Double-click on each Session Host object.
4 To issue a command to a Session Host: Right-click a server session. Administrators can perform the
following actions:
Table 25. Administrator actions
Disconnect If a session state is active, use you put it into a

disconnected state. Selecting Disconnect causes
the network connection between the client
device and the Session Host to be closed,
releasing memory and CPU threads.
The working state of the session is persisted by
writing to the Session Host’s page file, allowing
the user to reconnect to the session, with no loss
of data.
Send message An administrator can send a message to the
selected user if the session is active.
Remote control An administrator can connect to the user’s active
session, and depending on the policy settings,
view and interact with the session.
See Database configuration on page 51 for more
information on this feature.
Reset An administrator can reset a session which
disconnects the session in a non-graceful way.
NOTE: All unsaved data is lost.
Log off An administrator can gracefully log a user off
from a Session Host session. The user is prompted
to save any unsaved data.
To view session host sessions

2 Expand the Locations node, and then the expand location where the Session Host is located.
3 Expand the Session Hosts node.
4 Highlight the Management node.
5 To view a session on a specific Session Host, double-click on the Session Host and click on the Sessions
tab.
6 To view sessions for all Session Hosts:
a Right-click on the Session Hosts node and then select Connect All.
b Click on the Session Hosts node.
c Click on the Sessions tab.
vWorkspace 8.6.3
66
Table 26. Session hosts information
Domain The NetBIOS name of the steps domain to which the

user’s account belongs.
Session The name of the user’s session as assigned by the
Session Host.
User The user account name used to log on to the session.
Session ID The numerical session ID assigned to the user’s session
by the Session Host.
State The state of the Session Host session. The options are:
• Active
• Disconnected
• Idle
• Down
Type The connection type. The options are:
• Console
• RPD
Client name The NetBIOS name of the vWorkspace client device.
Idle time The amount of time no activity has occurred between
the client and the Session Host.
Logon time The date and time the session was logged on.
Comment Not used.
7 Right click on a user session. You can perform the following actions:
Table 27. Administrator action
Disconnect If a session state is active, use you put it into a

disconnected state. Selecting Disconnect
causes the network connection between the
client device and the Session Host to be closed,
releasing memory and CPU threads.
The working state of the session is persisted by
writing to the Session Host’s page file, allowing
the user to reconnect to the session, with no
loss of data.
Send message An administrator can send a message to the
selected user if the session is active.
NOTE: The only administrative action allowed
for the session is Send Message.
Remote control An administrator can connect to the user’s
active session, and depending on the policy
settings, view and interact with the session.
NOTE: See Database configuration on page 51
for more information on this feature.
vWorkspace 8.6.3
67
Table 27. Administrator action
Reset An administrator can reset a session, which ends
the session in a non-graceful way.
NOTE: All unsaved data is lost.
The session with Session Name of RDP-TCP and
Session ID 65536 is the Session Host’s RDP
listening port. The only administrative action
allowed is Reset.
Log off An administrator can gracefully log a user off
from a Session Host session. The user is
prompted to save any unsaved data.
To view client information for an active session

2 Expand the Locations node, and then expand the location where the Session Host is located.
3 Highlight the Session Hosts node.
4 Double-click on the Session Host.
5 Expand the Session Host, and click on the active session.
6 Click on the Information tab.
Table 28. Information fields
User name The name of the user.

Client name The NetBIOS name of the CAS Client device.
Client build number The vWorkspace internal build number of the
client software installed on the client device.
Client directory The complete directory path to which the
vWorkspace client software was installed.
Client product ID The vWorkspace internal identification number
of the client software.
Client hardware Not used.
Client address The IP address of the vWorkspace client
device.
Client color depth The color depth used in the session.
Client resolution The height and width, expressed in pixels,
used in the session.
To manage session host processes

3 Expand the Session Hosts node.
4 Click the Management node.
• To view a session on a specific Session Host:
a Double-click on the Session Host.
b Click on the Processes tab.
• To view sessions for all Session Hosts
a Right-click the Management node and then select Connect All.
vWorkspace 8.6.3
68
b Click the Session Hosts node.
c Click the Processes tab.
Table 29. Session hosts processes information
Domain The NetBIOS name of the user’s Windows domain

that owns the process.
Processes running in the console session are listed
as Unspecified.
Session The name of the Session Host session in which the
process is running.
User The name of the user account that owns the
process.
Session ID The numerical session ID the process is running in,
on the Session Host.
Process ID The assigned process ID by the Windows operating
system when the process is started.
Process The file name of the process.
5 Right click a user process from the list. Administrators can perform the following actions:
Table 30. Administrator actions for processes
End process An administrator can end the

process.
NOTE: System processes such as
winlogon.exe and lsass.exe,
cannot be terminated, even by an
administrator.
Remote control An administrator can connect to
the user’s active session, and
depending on the policy settings,
view and interact with the
session.
NOTE: See Database configuration
on page 51 for more information
on this feature.
To view session host applications

• To view a session on a specific Session Host:
a Double-click the Session Host.
b Click on the Applications tab.
• To view sessions for all Session Hosts:
a Double-click each Session Host object.
b Click the Session Hosts node.
c Click the Applications tab.
vWorkspace 8.6.3
69
Table 31. Applications information
Name The name of the published

application.
Type The published application type.
Status The status of the application. The
options are:
• Enabled
• Disabled
App-V server The name of the App-V server.
Published on The name of the Session Host that
it is published on.
Provisioning session hosts

The Session Hosts node allows administrators to create computer groups, from which Session Host servers can
be created.
Session Host computer groups are created in a similar way that computer groups are created from the Desktops
node. Session Hosts that are members of a computer group can be managed and can be classified as a managed
computer. Session Hosts can also be created in computer groups using the Add Computers wizard.
Virtual Desktop Extensions & Other MSI packages

The optional category Virtual Desktop Extensions & MSI packages appears on the Properties menu of a Session
Host computer group and on the properties of a Managed Session Host, but the option to deploy MSIs to a session
host is the only option available.
CAUTION:Installation of Virtual Desktop Extensions onto a Session Host is not
recommended.
The Virtual Desktop Extensions & MSI packages node can be used to deploy MSI packages that have been defined
within the Packaged Applications node of the Management Console.
Session host computer groups

Computer groups created within the Provisioning node of Session Hosts have properties similar to computer
groups created in the Desktops node. The table below details the attributes of a session host computer group.
Table 32. Attributes of a session host computer group
Property Description Applies to:

Group name Name of the managed desktop group. • Microsoft Hyper-V
• VMware vCenter Server
• Microsoft SCVMM
• Parallels Virtuozzo
• Other/Physical
System type System type for the computers in this • Microsoft Hyper-V
group. • VMware vCenter Server
• Microsoft SCVMM
• Other/Physical
Datacenter Datacenter in which the computers in • VMware vCenter Server
this group belong.
vWorkspace 8.6.3
70
Table 32. Attributes of a session host computer group

Administrative account Name of the user account that is used • Microsoft Hyper-V
when performing administrative tasks • VMware vCenter Server
on the desktop computers within this
• Microsoft SCVMM
group.
• Other/Physical
Provisioning settings Define the parameters used to • Microsoft Hyper-V
generate virtual computers that will • VMware vCenter Server
become members of the computer
group. The following parameters are
set: • Microsoft SCVMM
Template
Hosts. All hosts or selected hosts
Naming convention
Sysprep customization. Native, Quick
and Direct.
Configure Computers. Video Adapter,
Memory and Network Adapter
Load balancing Used to specify a load balancing rule • Microsoft Hyper-V
for the group, if appropriate. Load • Microsoft SCVMM
balancing rules that are created using
the Load Balancing node in the
Management Console are presented as
load balancing rule options.
NOTE: Hyper-V Load Balancing is
configured from the Properties
window of the Hyper-V host.
Task automation Tasks can be scheduled to be • Microsoft Hyper-V
completed at specified times. • VMware vCenter Server
See Task automation for more • Microsoft SCVMM
information.
• Other/Physical
Permissions Specify permissions for this computer • Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
For more information on Computer Groups see Setting up computer groups for a location.
vWorkspace 8.6.3
71
Managed session hosts
A Session Host that is a a member of a computer group is considered a Managed Session Host. The following
table details the properties of a available on a managed session host.
Table 33. Managed session host information

System type System type for the computers in this • Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
Datacenter Datacenter in which the computers in • VMware vCenter Server
this group belong.
Administrative account Name of the user account that is used • Microsoft Hyper-V
when performing administrative tasks • VMware vCenter Server
on the desktop computers within this
• Microsoft SCVMM
group.
• Other/Physical
Provisioning settings Define the parameters used to • Microsoft Hyper-V
generate virtual computers that will • VMware vCenter Server
become members of the computer
group. The following parameters are
set: • Microsoft SCVMM
Template
Naming convention
Sysprep customization. Native, Quick
and Direct.
Configure Computers. Video Adapter,
Memory and Network Adapter
Load balancing Used to specify a load balancing rule • Microsoft Hyper-V
for the group, if appropriate. Load • Microsoft SCVMM
Balancing Rules that are created using
the Load Balancing node in the
Management Console are presented as
load balancing rule options.
NOTE: Hyper-V Load Balancing is
configured from the Properties
window of the Hyper-V host.
Task automation Tasks can be scheduled to be • Microsoft Hyper-V
completed at specified times. • VMware vCenter Server
See Task automation for more • Microsoft SCVMM
information.
• Other/Physical
Permissions Specify permissions for this computer • Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
vWorkspace 8.6.3
72
To provision a session host
Use the following steps to configure a template that is used to create virtual computer within a Session Host
computer group.
1 Join the server to the domain you are using if you are using Instant Provisioning.
2 Create a Windows Server with the TS/RDSH role enabled.
3 Install vWorkspace using the Advanced installer option, and select the TS/RDSH role.
In the Installation wizard, Management Database Setup step, select Do nothing at this time. Do not join
this vWorkspace installation to an environment.
4 Install the Instant Provisioning components to the template.
The Instant Provisioning components are located in the vWorkspace download in a folder named
Template Tools. Make sure you select the correct version (x86 or x64).
When Session Host managed computers are deployed from this template, they are initialized in a manner
similar to the initialization of virtual desktops. The difference is that the Session Host initialization
process knows this is an RDSH and automatically provides the RDSH with the correct database
information.
Setting up desktops for a location

You can define computer groups which, in turn, are used to create and contain managed computers. The
managed computers within a group can be either physical or virtual, and typically have the same operating
system version and service pack level, a common set of installed applications, and are used by individuals with
similar job tasks and responsibilities.
To set up desktop properties

After desktops have been added to a location, you can set the properties.
1 From the Management Console, right-click on the Desktops node under the location where you want to
add the permission.
2 Select Properties.
3 Highlight the user or group on the Desktops Properties window, and then change the Permissions to Allow
or Deny, by selecting the appropriate check box.
For more information on permissions, see Administration on page 48.
4 Click Apply to save your changes
Desktops node terms

The following terms are associated with the Desktops node of vWorkspace.
• Computer groups. Containers for managing a group of desktop computers as a single entity. One or more
computer groups may be created for each system type.
See Setting up computer groups for a location for more information.
• Managed computers. Objects in the vWorkspace database that represent the desktop computers that
are managed by vWorkspace. These desktops are installed on virtual computers or physical devices, such
as blade PC’s.
See Setting up managed computers for a location for more information.
• Initialize computer. Managed computers and Microsoft Hyper-V Virtualization Hosts need to be able to
communicate properly with the Connection Brokers. The Initialize task is the process that enables this
communication, and is the responsibility of the Connection Broker.
vWorkspace 8.6.3
73
See To initialize a computer for more information.
• Virtual Desktop Extensions (PNTools). Set of executables, dynamic link libraries, and device drivers
that provide features and management functionality for managed computers in a vWorkspace
infrastructure. Virtual Desktop Extensions can be installed on all computers, virtual or physical, which
are being managed using the Desktops node.
See Virtual Desktop Extensions (VDE) for more information.
• Publish managed desktops and applications. Managed desktops must be published before users can
connect to their assigned applications or managed computer. Once published, icons representing the
managed desktop appear in the application set of the Connector or Web Access client, allowing the user
to click on an icon to initiate the program.
See Publish a managed desktop and Publish managed applications for more information.
• Power management. Managed computers are considered to be power-managed computers if the power
state can be changed automatically by the Connection Broker, or manually by an administrator using the
Management Console.
See Power management for more information.
Setting up computer groups for a location

After locations are established and are configured with at least one Connection Broker and Virtualization Host,
administrators can add computer groups to the Desktops node in the location. There are no limitations as to
how many computer groups can exist in each location.
The system types are:
• Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
For specific information on completing the Computer Group wizard based on system type, refer to the
appropriate section in the Virtualization Platform Integration chapter.
Computer group properties

The Properties associated with computer groups are described below:
Table 34. Computer group properties
Property Description Applies to

Group name Name of the managed desktop group. • Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
Group mode Configures the Computer Group for either Cloud • Microsoft Hyper-V
mode or Traditional mode.
System type System type for the computers in this group. • Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
vWorkspace 8.6.3
74

Datacenter Datacenter in which the computers in this group • VMware vCenter Server
belong.
Administrative account Name of the user account that is used when • Microsoft Hyper-V
performing administrative tasks on the desktop • VMware vCenter Server
computers within this group.
• Microsoft SCVMM
• Other/Physical
Auto-size Automatically adjusts the number of virtual • Microsoft Hyper-V
computers in the computer group based on user • VMware vCenter Server
demand.
Enable auto-size turns on Auto-sizing and
• Microsoft SCVMM
requires that the following values be set:
Minimum number of computers specifies the
minimum number of virtual computers to be
maintained in the group.
Demand buffer computers specifies the number
of virtual computers that should be powered on
and available at all times.
Maximum number of computers specifies the
maximum number of virtual computers allowed
in the group.
Provisioning settings Define the parameters used to generate virtual • Microsoft Hyper-V
computers that will become members of the • VMware vCenter Server
computer group. The following parameters are
set:
• Microsoft SCVMM
Template
Naming convention
Sysprep customization. Native, Quick and
Direct.
Configure computers. Video Adapter, Memory
and Network Adapter
Enable/disable Connection requests to computers in this group • Microsoft Hyper-V
may be temporarily suspended, if disabled. • VMware vCenter Server
• Microsoft SCVMM
• Other/Physical
vWorkspace 8.6.3
75

Client assignment Used to permanently assign users to specific • Microsoft Hyper-V
computers. • VMware vCenter Server
The two types of user assignment are: • Microsoft SCVMM
• Persistent. A permanent desktop is • Parallels Virtuozzo
assigned to the user.
• Other/Physical
• Temporary. A free desktop is assigned on
a temporary basis to the user, and then is
available to be used again at user logoff.
A client type can be assigned to the computers
in the group based on the following:
• User
• Device name
• Device address
• Organizational unit
• Group
• Advanced
NOTE: Since users can be in more than one
group or organization unit, administrators must
manually assign individual computers to users if
client assignment is based on Group or
Organizational Unit.
Assign computers using the Client Assignment
window for the specified computer. See Setting
up managed computers for a location for more
information on this window.
Access timetable Used to restrict access to the computers in this • Microsoft Hyper-V
group based on day and time. • VMware vCenter Server
• Microsoft SCVMM
• Other/Physical
Load balancing Used to specify a load balancing rule for the • Microsoft Hyper-V
group, if appropriate. Load Balancing Rules that • Microsoft SCVMM
are created using the Load Balancing node in the
Management Console are presented as load
balancing rule options.
NOTE: Hyper-V Load Balancing is configured
from the Properties window of the Hyper-V host.
User privileges Automatically assigns users to local security • Microsoft Hyper-V
groups. • VMware vCenter Server
This policy is useful when provisioning desktop • Microsoft SCVMM
workspaces to users that require elevated
privileges.
• Other/Physical
vWorkspace 8.6.3
76

Session auto-logoff Automatically logs off user sessions. • Microsoft Hyper-V
This policy is for users that start published • VMware vCenter Server
applications and not full desktops. If enabled, • Microsoft SCVMM
vWorkspace automatically logs off when the last
published application is closed. This eliminates
the potential issue of applications remaining in • Other/Physical
memory, that never actually terminate.
Enter a module name for a process. If the
process with the module name persists after the
session has been closed, then the session is
automatically logged off.
To add a process, click Add.
To delete a process from the use, highlight the
process and click the red X.
Inactivity timeout Automatically suspends computers in the group • Microsoft Hyper-V
when they are inactive. • VMware vCenter Server
• Microsoft SCVMM
Logoff action Can be set to automatically reset, reprovision or • VMware vCenter Server
delete a computer in this group when the user • Microsoft SCVMM
logs off.
Session protocol Specify the protocol for remote user sessions for • Microsoft Hyper-V
this group, either Microsoft’s Remote Desktop • VMware vCenter Server
Protocol.
• Microsoft SCVMM
• Other/Physical
Experience Specify if user experience optimizations are to • Microsoft Hyper-V
optimization be enabled or disabled for this computer group. • VMware vCenter Server
This includes the settings for bandwidth • Microsoft SCVMM
optimization appliances.
• Other/Physical
Task automation Tasks can be scheduled to be completed at • Microsoft Hyper-V
specified times. • VMware vCenter Server
See Task automation for more information. • Microsoft SCVMM
• Other/Physical
Permissions Specify permissions for this computer group. • Microsoft Hyper-V
• Microsoft SCVMM
• Other/Physical
Finish Select from the options available as to the finish • Microsoft Hyper-V
process for this group. • VMware vCenter Server
• Microsoft SCVMM
• Other/Physical
vWorkspace 8.6.3
77
To add a computer group
The settings presented differ based upon the system type, such as VMware or Microsoft SCVMM. Review the
previous table to view which property applies to which type.
TIP: Virtualization servers and virtualization hosts must be added prior to adding
computer groups. See the Virtualization Platform Integration chapter for more
information on the set up of virtualization servers and hosts.

2 From the Desktops node, open the Computer Group wizard:
a Expand the location to which the computer group is to be added.
b Right-click on the Desktops node.
c Select New Computer Group.
4 In the Group Name field on the Group Name window, enter the name of the computer group, and then
click Next.
5 On the System Type step, select the system type for the group, and then click Next.
6 Complete the settings, based on the selected system type. Click Next.
7 On the Finish step, do one of the following:
a Select the Create new computers from a master template to add new desktops to the group and
enter the number of desktops to create. Complete the process using the Add Computers tool.
See the Virtualization Platform Integration chapter for more information about the Add
Computers tool.
b Select Import existing computers to add computers by importing existing virtual computers and
complete the process using Importing existing computers into a group on page 156.
c Select Do nothing. I will create or import computers later to create the desktops at a later
time.
8 Click Finish.
After managed computer groups are established, their properties can be viewed and modified from the
vWorkspace Management Console by right-clicking on the managed computer group, and selecting
Properties.
To view summary information for a computer group

2 Select Desktops for the location, and highlight the computer group.
3 Select the Summary tab.
To view managed computers

2 Navigate to the Desktops node of the computer group that you want to view, and highlight the computer
group.
3 Select the Computers tab.
4 Enter the text of the search term in the Find field.
For example, enter Powered On to locate powered on computers in the Power State column.
5 Do one of the following:
• To highlight the next computer meeting the search criteria, click the Find Next icon.
• To highlight all computers meeting the search criteria, click the Select All Matching icon.
vWorkspace 8.6.3
78
If the criteria is not found a message box displays stating [criteria] not found.
To view tasks for a computer group

2 Navigate to the Desktops node of the computer group that you want to view the tasks, and highlight the
computer group.
3 Select the Summary tab in the information pane.
4 Click Toggle Lower Pane on the toolbar of the information pane.
This enables the lower pane.
5 Select the Tasks tab to view.
For example, enter Reconfigure to locate reconfigured computers in the Task Item column.
To view log files for a computer group

2 Navigate to the Desktops node of the computer group that you want to view the logs, and highlight the
computer group.
3 Select the Summary tab.
4 Click Toggle Lower Pane.
This enables the lower pane.
5 Select the Log tab.
To modify the properties of a computer group

2 Navigate to the Desktop node that includes the computer group that you want to modify.
3 Right-click on the computer group, and select Properties.
4 Change the properties as needed, and then click OK.
To delete a computer group

2 Navigate to the Desktops node of the computer group that is to be deleted.
3 Right-click on the computer group, and then select Delete Group.
If the group is not empty, a message appears stating that all managed computers from the group need to
be removed prior to deleting the group.
4 Click Yes on the Confirmation step to delete the group.
vWorkspace 8.6.3
79
To arrange Information Pane column order and sort order
Columns are grouped and ordered according to computer group type. In the Column Options window, the
Grouped check box indicates if the selected column is part of a group and its order is determined by its position
in the Selected Columns pane, with the top column on the far left of the Information pane.
1 To arrange columns in the Information pane, click and hold down the mouse button in the column
heading, and drag the column to the desired location.
2 To sort information within a column, click the column heading to toggle the ascending or descending
arrowhead, or right-click in the column heading and select Sort Ascending or Sort Descending from the
drop-down context menu.
To resize columns
1 Right-click in a column heading and select Size Column to Fit from the drop-down context menu to fit a
column to its contents.
2 Right-click in a column heading and select Auto Size All Columns to Fit to automatically fit all the
columns in the Information pane to their contents.
To add columns
2 Navigate to and select a computer group.
3 Select the Desktops tab.
4 Right-click within a column heading.
5 Select Column Options in the context menu.
6 In the Column Options window, use the right arrow to move columns from the Available Columns pane to
the Selected Columns pane, or the left arrow to move columns back to the Available columns pane.
7 In the Selected Columns pane, highlight a column name and click the up or down arrows to adjust its
position. Click OK.
8 To display all the available columns, right-click in an information pane column heading and choose Show
All Columns from the drop-down context menu.
Task automation
The Task automation property of a managed computer group provides the ability to schedule execution of a
vWorkspace supported operation on a vWorkspace managed virtual or physical computer or Session host is
available through the Automated Task Wizard. Some of the scheduled tasks include:
• Power management.
• Deletion of virtual computers, including the ability to delete computers that have been inactive for a
specified number of days.
• Installation of MSI packages.
• Installation and update of Virtual Desktop Extensions.
• Program and script execution.
To schedule tasks using the Automated Task Wizard

2 Expand the Desktops node for the location to which you want to add the scheduled task.
3 Right-click on the computer group and select Properties to open the Computer Group Properties
window.
4 Select Task Automation in the left pane of the Computers Properties window, and then click New (green
+ plus sign). The Automated Task wizard appears.
vWorkspace 8.6.3
80
6 Enter a Name for the task, and then click Next.
7 On the Task step, select the task from the list, and then click Next.
8 On the Task Parameters step, complete the information, and then click Next.
The fields on the Task Parameters step change based upon the type of task that is selected.
9 Complete the information on the Schedule step, and then click Finish.
Setting up managed computers for a location

Managed Computers are objects in the vWorkspace database that represent the desktop computers and Session
Hosts that are members of a managed computer group. These desktops and session hosts are virtual computers
or physical devices. Virtual computers can be provisioned from a template or parent VHD or imported into a
computer group. Physical computers must be imported into a computer group.
Managed computers have properties that control their creation and use. The properties that are available
depend upon the type of group in which the managed computer exists. When a computer is added or imported
into a managed computer group, it inherits the property settings of the group.
To add computers to a managed computer group

1 From the Management Console, open Locations | <Choose a location> | Desktops.
2 Right click Desktops and select New computer group.
3 Create a new computer group (see Properties of a managed computer).
4 On the Finish page of the New Computer Group wizard, select Create new computers from a master
template.
For more information on how to use add computers based upon system type, refer to the Virtualization Platform
Integration chapter.
Properties of a managed computer

The following section describes each listed property of a managed computer.
Table 35. Summary step
Summary step Description

Name The computer name.
DNS name The Domain Name System name.
NetBIOS name The NetBIOS name. The first 15 characters of the
Windows computer name are assigned
automatically by Windows setup and cannot be
modified.
IP address The TCP/IP address last assigned to the managed
computer.
MAC address The Media Access Control address assigned to the
managed computer’s network interface card.
NOTE: Only one active physical or virtual network
interface is supported on a virtual machine,
physical PC, or blade PC.
Allow power-management Selecting this option allows the vWorkspace
(suspended, reset, etc.) through Management Console to control the power state of
the vWorkspace management the managed computer, if it is an applicable option.
console.
vWorkspace 8.6.3
81
Table 36. Administrative account step
Administrative Account step Description

Override group properties Selecting this option allows a different
administrative account and password to be
assigned to the managed computer from the
ones being used by the group.
Account This field is used to specify the name of a user
account that has local administrative rights.
User the ellipsis button to browse to the
account.
Password/confirm password This field is used for the password of the user
account specified by Account.
Table 37. Enable/disable step
Enable/Disable step Description

Override group properties Selecting this option allows this computer to have a
different property than the group.
Enabled or disabled Select one of the options for this computer.
If Disabled is selected, the Connection Broker
does not redirect incoming connection requests to
this computer.
Table 38. Client assignment (see Temporary Client Assignment for more details)
Client Assignment step Description

Current user Displays the name of the user account currently
logged on to the managed desktop computer.
If a user is not logged on, a None value is displayed.
Permanent user Displays the name of the user account permanently
assigned to the managed desktop computer.
If a user is not logged on, a value of None is
displayed.
Select a user to whom this Use this option to select a user account that is
desktop should be permanently permanently assigned to the managed desktop
assigned computer.
This option is available if a user is currently not
logged on to the desktop.
NOTE: If a Client Assignment policy for the desktop
group is set to Temporary, it is overridden for this
desktop computer only.
NOTE: If the Client Assignment policy for the
desktop group is set to Persistent, this setting can
be used to pre-assign a user account to the
managed computer.
vWorkspace 8.6.3
82
Table 38. Client assignment (see Temporary Client Assignment for more details)
Client Assignment step Description

Persistently assign the current Use this option to assign the currently logged on
user to this desktop user account to the managed computer.
This option is available if a user is currently not
logged on to the desktop.
group is set to Temporary, it is overridden for this
desktop computer only.
Remove the current permanent Use this option to remove the current permanent
assignment assignment from the managed computer.
group is set to Temporary, the managed computer
is available for automatic, permanent assignment.
NOTE: If the Client Assignment policy for the
desktop group is set to Persistent, this setting can
be used to pre-assign a user account to the
managed computer. However, the vWorkspace
administrator can still choose to pre-assign the
desktop to a user.
Table 39. Access timetable
Access Timetable step Description

Override group properties If selected, you can specify a different access
timetable setting than that of a desktop group.
Click on the green grid to set a time schedule.
If selected, choose from the following:
Grant Permission. Specifies the days of the week
and the hours of the day when logons to the
desktop computer are allowed (marked in green).
Deny Permission. Specifies the days of the week
and the hours of the day when logons to the
desktop computer are not allowed (marked in red).
Table 40. User privilege

User Privileges step Description
Override group properties If selected, you can specify a different level of user
privileges for the users that log on to this desktop
computer.
Power User At logon, the user is added to the desktop
computer’s built-in Power Users local group.
Administrator At logon, the user is added to the desktop
computer’s built-in Administrators local group.
None At logon, the user is added to the desktop
computer’s built-in Users local group.
vWorkspace 8.6.3
83
Table 41. Power savings (SCVMM and Hyper-V)
Inactivity Timeout step Description

Desktops can be automatically suspended when idle for a specified amount of time.
Override group properties If selected, you can specify a different power
savings setting than that of the parent desktop
group.
Automatically suspend Select to enable automatic suspension of the
desktop computer when inactive (user is logged
off, but computer is still powered on), or if offline.
Do not automatically suspend Select to disable automatic suspension of the
desktop computer when inactive (user is logged
off, but computer is still powered on), or if offline.
Table 42. Power savings (VMware)
Power Savings step Description

Override group properties If selected, you can specify a different power
saving than that of a desktop group.
To conserve computing Inactive status is marked when the managed
resources, automatically computer has been logged off, disconnected or goes
suspend computers in the group offline.
that are inactive
Computers to remain powered Number of computers in the computer group that
on will not be suspended. This parameter ensures that
a connecting user is logged into the virtual
workspace quickly.
Values: none - 500

Power Savings Feature Update

In 8.6.2, we added the capability to globally configure the action to take when power savings is enabled. Now
the power savings feature can alternatively be configured to power off or shutdown the guest. This setting is
configured in the vWorkspace database as specified below:
Table: DmSettings
SectionKey: BrokerSetting
ValueKey: PowerSavingAction
IntValue: 4,5 or 11 (Power Off, Suspend (default) or Shutdown Guest)
vWorkspace 8.6.3
84
If this record does not already exist in the DmSettings table, the system will default to 5 (Suspend). If the
record doesn’t exist, use this SQL statement to add the record:
DECLARE @RecordGUID uniqueidentifier;
SET @RecordGUID = NEWID();
INSERT INTO DmSettings
(SectionKey
,ValueKey
,CharValue
,IntValue
,ImageValue
,DateTimeValue
,RecordGUID)
VALUES
('BrokerSetting'
,'PowerSavingAction'
,NULL
,5
,NULL
,NULL
,'{'+CONVERT(varchar(38), @RecordGUID)+'}')
GO
If this record already exists, just modify the IntValue field as necessary. A connection broker restart is not necessary for this
setting to take effect.
Table 43. Session auto-logoff
Session Auto-Logoff step Description

Override group properties If selected, you can specify a different session
auto-logoff setting than that of a desktop group.
Module Name Enter the name, such as wuauclt.exe.
Add Select after entering a name in the Module Name
box.
Remove Select to remove items from the list.
Table 44. Configuration (VMware system type only)
Configuration step Description

Reconfigure Enables administrators to modify the current
memory and virtual disks configuration.
Refresh Refreshes the current view of the step.
vWorkspace 8.6.3
85
Table 45. Configuration (Hyper-V and SCVMM system type)
Configuration step Description

Reconfigure Enables administrators to modify the current video
adapter, memory, memory priority and network
adapter configuration.
Refresh Refreshes the current view of the window.
Table 46. Logoff action
Logoff Action step Description

Override group properties If selected, you can specify a different logoff action
setting than that of a desktop group.
Nothing If selected, no actions are performed at logoff.
Reset If selected, this computer is reset when the user
logs off.
Reprovision If selected, this computer is reprovisioned at log
off.
NOTE: It is recommended that you install Virtual
Desktop Extensions (PNTools) onto your VMware
template if you are using the reprovision
functionality.
Table 47. Session protocol
Session Protocol step Description

Override group properties If selected, you can specify a different Session
Protocol setting than that of a desktop group.
RDP Remote session protocol for this computer is set to
RDP.
RGS Remote session protocol for this computer is set to
RGS.
vWorkspace 8.6.3
86
Table 48. Optimizations
Optimization step Description

Enable support for bandwidth Enables or disables support for bandwidth
optimization appliances optimization for this computer.
Override group properties. If selected, you can
specify a different bandwidth optimization setting
than that of a desktop group.
Enable support for WAN Override group properties. If selected, you can
acceleration specify a different WAN acceleration setting than
that of a desktop group.
Enabled. Enables support for WAN Acceleration.
Enable RDP pass-through mode. Enables WAN
Acceleration to use the RDP port, eliminating the
need to configure extra firewall settings.
WAN Acceleration Port Number. The default port
number is 33389.
Maximum number of connections. Enter a
maximum number of connections.
Disabled. Disables support for WAN Acceleration.
Table 49. Automated tasks
Task Automation step Description

Name Identifies the name of the task.
Task Identifies the task that is to be completed.
Schedule Identifies the schedule to which the task is to be
completed.
New Select to add a new scheduled task.
See To schedule tasks using the Automated Task
Wizard for more information.
Table 50. Permissions
Permissions step Description

User/groups Lists users and groups who have permission to
perform administrative tasks on this computer.
Select a user or group to view their permissions.
Permissions Lists permission for this computer and if they are
allowed or denied for the selected user or group.
For more information on permissions, see
Administration on page 48.
Operating system customizations

You can create the operating system customization information for Hyper-V, SCVMM, VMware and Parallels
Virtuozzo type computers.
You can select one of the following System Preparation (Sysprep) types based on the system type:
• Windows XP, Server 2003 (sysprep.inf)
vWorkspace 8.6.3
87
• Windows 7, 8.1 and 10, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and
Windows Server 2016(unattend.xml)
You can also import an existing sysprep.inf or unattend.xml file, and then make additional customizations to the
file through the Operating System Customizations wizard.
Operating system customization types

vWorkspace supports three operating system customization types: Instant, Native, and Direct.
• Instant mode is available for provisioning virtual computers on Hyper-V and VMware platforms and uses
Instant Provisioning, which is the fastest way to customize a computer.
NOTE: Generation 2 virtual machines are not supported when using instant provisioning on Hyper-V.
Instant Provisioning requires the master template be configured as follows:

• vWorkspace Instant Provisioning tools (TEMPLATE_TOOLS\InstantProvisioning.exe) is pre-installed.
• Joined to the target domain (the template must have valid trust with the domain).
• Microsoft Sysprep uses the virtualization system’s native sysprep execution and passes all the
customizations to the virtualization system (Hyper-V, SCVMM, VMware vCenter).
• Direct Sysprep invokes Sysprep directly after the clone operation is complete. This is the slowest of the
Sysprep mechanisms.
Direct sysprep requires that Virtual Desktop Extensions (PNTools) be pre-installed and must be
configured on the master template.
Instant Provisioning can be configured to run custom commands after the provisioning process is complete. On
the template, locate the following folder:
%programfiles%\Quest Software\Instant Provisioning\vbscripts.
Any .vbs files in this folder are run at the end of the Instant Provisioning process.
About Sysprep files

Using an imported sysprep.inf file provides you with more customization than using the Operating System
Customization wizard. For example, you can configure TCP/IP and networking options. However, if you choose
to import a sysprep.inf file, you must include the following sections or the customization process pauses and
awaits user interaction.
[Unattended]
OemSkipEula=Yes
OemPreinstall=Yes
InstallFilesPath=c:\sysprep\i386
[GuiUnattended]
OEMSkipRegional=1
OEMSkipWelcome=1
EncryptedAdminPassword=No
[Networking]
InstallDefaultComponents=Yes
The following table shows which Sysprep execution mode is compatible with each virtualization platform and
operating system.
Table 51. Sysprep execution modes
Instant Microsoft Sysprep Direct Sysprep

Hyper-V INF, XML INF, XML n/a
vWorkspace 8.6.3
88
Table 51. Sysprep execution modes
SCVMM n/a INF, XML n/a
VMware INF, XML INF, XML INF
Parallels n/a n/a INF, XML
INF = Windows XP and Windows Server 2003
XML = Windows 7, 8.1 and 10, Windows Server 2008/R2, 2012 and 2016
Preparing templates on VDI machines

vWorkspace allows you to deploy many virtual desktops or RD Session Hosts from a single template on a range of
supported virtualization platforms. Refer to the following recommendations for setting up the template:
• The template is representative of the virtual desktops your users need.
• The Microsoft volume licensing is required when using VDI (this is a requirement of all Windows Desktop
Virtualization solutions.
• Microsoft KMS is recommended (see http://technet.microsoft.com/en-us/library/ff793434.aspx).
• The most recent version of PNTools is installed.
• The template is not a part of any vWorkspace environment. Ensure that the following values are blank on
the template:
Reg type is Reg_SZ
HKEY_LOCAL_MACHINE\SOFTWARE\Provision Networks\Common\LLMServerList=
HKEY_LOCAL_MACHINE\SOFTWARE\Provision Networks\Common\ComputerID=
HKEY_LOCAL_MACHINE\SOFTWARE\Provision Networks\Common\PublicKey=
• A supported version of the Flash Player (15.0.0.223) is installed if you use Flash Acceleration.
• DHCP is enabled and the template has only one network adapter.
• Firewalls are not blocking communication between the virtual desktop and the vWorkspace connection
brokers. (allow TCP 5203 and TCP 5201 and 8080 to the vWorkspace connection broker).
• The relevant virtualization platform agents are installed (such as VMware tools).
• Consider running the vWorkspace Desktop Optimizer on the template (see Optimizing a virtual computer
on page 95).
To prepare the template

1 Prepare the base operating system (such as Windows 7).
2 Generalize the template.
• Generalizing the template for Microsoft Sysprep mode
• Generalizing the template for instant provisioning
3 If you are using software that modified the Userinit key, set up Userinit chaining (see Using Microsoft Key
Management Services with Instant Provisioning).
Generalizing the template for Microsoft Sysprep mode

When using Hyper-V and SCVMV, the last step in preparing your machine for deployment is generalizing the
template. When you make a copy of the machine and turn it on, the copy will attempt to locate the template
file. You do not need to generalize the template if you are using VMware for instant provisioning.
To generalize the template for Microsoft Sysprep mode

1 Create the Base Template Image.
2 Update the image with the latest updates and line of business applications.
vWorkspace 8.6.3
89
3 Install PNtools.
4 Point your template to the KMS server.
5 Make a copy of the Base Template Image vhd(x) file before performing the Sysprep /Generalize
/Shutdown operation.
6 Perform Sysprep, import or update the vWorkspace template. All the new provisioning and re-
provisioning will be done from this template now.
7 When the base image needs to be updated, the copied base template image file will be used and another
copy of this file will be made before performing the Sysprep. This way rearm limitation can be worked
around.
Generalizing the template for instant provisioning

When you generalize the template for instant provisioning, you do not need to Sysprep the template.
To generalize the template for instant provisioning

1 Create the Base Template Image.
2 Update the image with the latest updates and line of business applications.
3 Install PNtools.
4 Point your template to the KMS server.
5 Install vWorkspace Instant Provisioning tools.
6 Join the virtual machine to the domain that you want to provision to.
Using Microsoft Key Management Services with Instant Provisioning

Microsoft Key Management Services (KMS) is used to activate volume-licensed Microsoft products. If the KMS
template is set up correctly, no modifications are required for it to work with vWorkspace.
To use Instant Provisioning with Microsoft KMS, you will need the KMS Client keys that Microsoft provides from
the following link:
http://technet.microsoft.com/en-us/library/ff793421.aspx
This link contains the KMS keys that are needed for the client operating system to obtain the appropriate KMS
license.
TIP: When you create the Instant Provisioning configuration from the Management
console, do not enter a Product key in the Operating System Customization
Properties (ensure that the Specify a Product Key box is not selected).
The following sections provide examples of how to prepare the template for KMS to work with vWorkspace. Your
specific needs may differ. Refer to Microsoft Key Management Services documentation for more information.
The following methods are outlined described:
• Using the Existing Template Method
• Using a New Template Method
To activate volume-licensed Microsoft products using an Existing Template method

Instant Provisioning makes a copy of the template and does not run a full Sysprep on the newly created
computer. This may cause issues with Microsoft licensing.
When using Microsoft Sysprep or a Direct Sysprep, you are performing a Sysprep on the computer being
provisioned, which causes a new Client Machine ID (CMID) to be generated for each new computer. Instant
Provisioning makes a copy of the computer and vWorkspace inserts the computer name and other information
into the image that is created.
vWorkspace 8.6.3
90
Microsoft KMS licensing verifies that the computer has been activated. All provisioned computers use the same
CMID as the template, so the KMS server returns information that the computer is active and does not need a
license.
Use the following procedure to enable the computer to be licensable, allowing the KMS server to generate a
valid license.
On your template that has been joined to a domain, perform the following steps:
1 Verify that Instant Provisioning is installed.
2 Verify that Virtual Desktop Extensions is installed.
3 Verify that you have the KMS Client Setup Key installed as the key when you created the template.
4 Generalize the template. From an elevated command prompt, run the following command:
Sysprep /generalize
This removes the computer from the Domain and removes any KMS information that may be on the
computer.
5 Add the computer back into the domain.
6 When you restart the template, add the KMS server information back into the template. This can be
done using the following command in an elevated command prompt:
SLMGR-skms <KMS server>
7 Copy and paste the following script into Notepad and save it as EnableSPPSVC.vbs in the following
location:
C:\Program Files(x86)\Quest Software\Instant Provisioning\VBScripts\
Option Explicit
On Error Resume Next
Public Sub StartApplication(App, WindowStyle)
dim aShell
set aShell= CreateObject("WScript.Shell")
aShell.Run App,WindowStyle
set ashell=nothing
end sub
StartApplication "%SYSTEMROOT%\system32\sc.exe config sppsvc start=delayed-auto",0
on error goto 0
8 Close the template.
9 Re-import the template into the Management Console for the new changes to take effect.
To activate volume-licensed Microsoft products using a New Template method

Instant Provisioning makes a copy of the template and does not run a full Sysprep on the newly created
computer. This may cause issues with Microsoft licensing.
When using Microsoft Sysprep or a Direct Sysprep, you are performing a Sysprep on the computer being
provisioned, which causes a new Client Machine ID (CMID) to be generated for each new computer. Instant
Provisioning makes a copy of the computer and vWorkspace inserts the computer name and other information
into the image that is created.
Microsoft KMS licensing verifies whether the computer has been activated. All computers being provisioned use
the same CMID as the template, so the KMS server returns information that the computer is active and does not
need a license.
On your new template, perform the following steps:
1 When creating the template, make sure that you are using the KMS client Setup Key for the appropriate
operating system you are using.
2 Install all applications.
3 Run all updates and installed applications to the operating system.
4 Generalize the template. From an elevated command prompt, run the following command:
Sysprep /generalize
vWorkspace 8.6.3
91
This removes the computer and any KMS information from the Domain.
5 Add the computer back into the domain.
6 When you restart the template, add the KMS server information back into the template.This can be done
using the following command in an elevated command prompt.
SLMGR-skms <KMS server>
7 Install Instant Provisioning.
8 Install the version of Virtual Desktop Extensions appropriate for the template.
9 Copy and paste the following script into Notepad and save it as EnableSPPSVC.vbs in the following
location:
C:\Program Files(x86)\Quest Software\Instant Provisioning\VBScripts\
Option Explicit
On Error Resume Next
Public Sub StartApplication(App, WindowStyle)
dim aShell
set aShell= CreateObject("WScript.Shell")
aShell.Run App,WindowStyle
set ashell=nothing
end sub
StartApplication "%SYSTEMROOT%\system32\sc.exe config sppsvc start= delayed-auto",0
on error goto 0
10 Shut down the template.
11 Import the template into the Management Console.
To create operating system customizations for Windows XP/2003

1 On the Add Computers wizard, Customize Operating System setting, select the New icon (green plus
sign).
2 Operating System Customization Wizard, Welcome window, click Next.
3 Enter a Name for this customization, and then click Next.
4 Select the platform type Windows XP/2003 (sysprep.inf), for this operating system customization.
5 On the Import window, complete the information if you want to import an existing sysprep.inf file, and
then click Next.
Or, if you do not want to import an existing file, click Next.
See About Sysprep files for more information about importing an existing sysprep.inf file.
6 On the Operating System step, specify the Windows operating system, and then click Next.
7 On the Registration step, enter the Windows registration information of Owner and Organization, and
then click Next.
8 On the Time Zone step, select a Time Zone to be used, and then click Next.
9 On the Product Key step, select one of the options, and then click Next.
• Specify a single product key.
• Retrieve product keys from a text file. Use the ellipsis to browse.
10 On the Customizations Type step, select one of the options: Instant, Microsoft Sysprep, or Direct
Sysprep, and then click Next.
11 On the Licensing Mode step, if Windows Server 2003 or Windows Server 2003 (64-bit) was selected as the
Operating System, select one of the options and then click Next.
• Per Server
• Per Device
• Per User
vWorkspace 8.6.3
92
12 On the Administrator Password step, enter the Password for the administrator account for the desktops
created in this group, and then click Next.
13 On the Domain or Workgroup step, the select Domain or Work group where the computers are to be
added, click Next.
If you select Domain, specify a user account that has permission to add a computer to the domain.
14 On the Active Directory Path step, enter the Active Directory Organization Unit Path to which the
computers are to be added, and then click Next.
15 Enter the path to the folder where the installation files are located, and then click Next.
If you do not want a folder specified, delete the default value in the Path field.
This is an optional step. The default is c:\sysprep\i386.
16 On the Regional Settings step, select one of the options, and then click Next:
• Use the default regional settings for the Windows version you are installing.
• Specify the regional settings. Select a default value for the language.
17 On the Languages step, select the language in which the users can view the content, and then click
Next.
18 Use the Run Once step to configure Windows to automatically run a command the first time a user logs
on.
a Enter the command in the Command box, and click Add.
b Use the green arrows to define the commands order.
c Click Next when you are finished.
19 Enter an Identification String, which is written to the registry of the computer to assist in determining
what customization object was used to customize a computer. Click Next.
20 On the Custom Entries step, alter the customization entries. This is an optional step. Click Next to
proceed to the next step.
21 On the Summary step, review your entries and do one of the following:
• Click Back to make changes.
• Click Finish to create the desktops.
• Click Cancel to exit without saving the settings or creating the desktops.
22 Complete the Add Computers wizard.
To create operating system customizations for Win7 and 8/Windows Server2008/ Windows
Server 2008 R2, and Windows Server 2012
1 On the Add Computers wizard, Customize Operating System setting, select the New icon (green plus
sign).
2 On the Welcome to the Operating System Customizations Wizard window click Next.
3 On the Name step, enter a Name for this operating system customization, and then click Next.
4 On the Platform step, select the Platform type for this customization, and then click Next.
5 On the Import step, click Select file and browse to the location of your answer file template if you want
to use an existing unattend.xml file.
a Click Edit to use Notepad or a shell application to edit the file.
b If you have modified the file outside of vWorkspace or have used the Edit option to modify the
file, click Re-import to reimport the file.
c Click Next to continue.
vWorkspace 8.6.3
93
This is an optional step, and is used if you have an existing unattend.xml file that you want to use in the
Sysprep process.
6 Select the operating system and the processor architecture for this customization, and then click Next.
7 On the Registration step, enter the Windows registration information of Owner and Organization, and
then click Next.
8 On the Time Zone step, select a Time Zone that is to be used when configuring Windows, and then click
Next.
9 On the Product Key step, select one of the following, and then click Next.
• Select Specify a product key and then select Specify a single product key. Enter the specified
product key.
The entered product key replaces the Product key value and elements in the unattend.xml file if
you have imported an existing unattend.xml file.
• Select Specify a product key and then select Retrieve product keys from a text file. Enter the
file or browse to its location.
• Unselect Specify a product key.
The Product key values and elements that are specified in the imported unattend.xml file (if you
have imported an existing unattend.xml file) will be used in the operating system customization
process.
If there are no Product key values or elements specified in the unattend.xml file, a message is
displayed warning that the operating system customization might fail.
The need for a product license key is based upon Microsoft’s license scheme for their products.
10 On the Customizations Type step, select one of the options: and then click Next.
• Instant
• Microsoft Sysprep
• Direct Sysprep
11 On the Domain or Workgroup step select Domain or Workgroup to identify how the desktops will
participate in the network, and then click Next.
If you select Domain, you must enter a user account that has permission to add a computer to the
domain.
12 On the Active Directory Path step, specify the Active Directory Organization Unit path into which the
computers are to be added, and then click Next.
13 On the Local Account step, specify a local administrator account if you are using Microsoft Windows 7, or
Microsoft Server 2008, and then click Next.
14 On the Firewall step, enable or disable the firewall for the public profile, domain profile, and private
profile, and then click Next.
15 On the Regional Settings step, specify the regional settings and then click Next.
16 On the Run Once step, configure Windows to automatically run a command the first time a user logs on.
a Enter the command in the Command box, and click Add.
b Use the green arrows to define the commands order.
c Click Next when you are finished.
17 On the Identification String step, enter an Identification String, which is written to the registry of the
computer to assist in determining what Sysprep object was used to customize a computer.
18 Click Finish to complete the Operating System Customizations wizard.
19 Complete the Add Computers wizard.
vWorkspace 8.6.3
94
Optimizing a virtual computer
The vWorkspace Desktop Optimizer allows you to apply optimizations to virtual computers. You can use the
Desktop Optimizer to disable Windows services that are not essential for your environment, improving
performance.
The Desktop Optimizer is an option that can be installed with Instant Provisioning tools.
To modify the optimization settings

1 Open the Desktop Optimizer from C:/Program Files (x86) /Quest Software/vWorkspace/Desktop
Optimizer.
Figure 21. The Desktop Optimizer
2 If you want to filter the list of optimization settings, click the Select heading and choose one of the
following filtering options:
• By Impact. Choose between Low, Medium and High. The higher the impact, the more beneficial
the optimization is for your VDI environment (scalability).
• By Category. Optimizations can be sorted by area they have the most effect on. Categories are:
Storage, User Experience and CPU/Memory.
3 Enable or disable the Optimization Settings.
When you click on an item from the list, the following information is shown for the selected item:
• Description. A description of the selected optimization.
• Justification. A reason why you might want to apply the selected optimization.
• Impact. The level that your VDI environment (scalability) is impacted.
• Category. The category that the selected optimization can be sorted by.
4 Click Run to apply the optimizations. There is no undo for this operation.
5 Click Save to save the current configuration. The configuration is stored in an XML file that is in the same
directory as the vWorkspace Desktop Optimizer EXE file.
6 If you want to export the current configuration to an XML file, click Export.
7 Click Exit.
Setting up Userinit chaining

If you have a software installed that modified the UserInit registry key, then vWorkspace pushes that custom
UserInit key down the chain, so that PNShell executes first, and then runs that value that was previously in the
UserInit key. PNtools must be on the template.
vWorkspace 8.6.3
95
To install Userinit chaining on a new instance on windows
Before PnTools installation:
HKLM\Software\WindowsNT\CurrentVersion\Winlogon - value: UserInit.exe (this is the Windows default)
After PNTools installation
HKLM\Software\WindowsNT\CurrentVersion\Winlogon - value: PnShell.exe
HKLM\Software\Wow6432Node\Provision Networks\Provision-IT\UserInit (this key is added during installation) -
value: UserInit.exe (this value is what was in the WinLogon key)
To install Userinit chaining on a system on which Userinit has already been modified by a third
party application
Before PnTools installation
HKLM\Software\WindowsNT\CurrentVersion\Winlogon - value: LWL.exe (arbitrary value)
After PNTools installation
HKLM\Software\WindowsNT\CurrentVersion\Winlogon - value: PnShell.exe
HKLM\Software\Wow6432Node\Provision Networks\Provision-IT\UserInit (this key is added during installation) -
value: LWL.exe (this value is what was in the WinLogon key)
Using the new registry key

After PNShell completes, it then reads the value of the HKLM\Software\Wow6432Node\Provision
Networks\Provision-IT\UserInit key and attempts to run it as a command line operation. If there have been no
errors in execution, logon will proceed smoothly.
Checking the status of the registry

When the data collector runs, It copies the value in HKLM\Software\WindowsNT\CurrentVersion\Winlogon and
then compares it with the value in HKLM\Software\Wow6432Node\Provision Networks\Provision-IT\UserInit
If the value is already there (or if the value of WinLogon is PnShell.exe) then it does nothing; otherwise, it
copies the WinLogon value to Provision-IT's UserInit key and then puts PnShell.exe into WinLogon.
The process supports multiples in a comma-delimited list (for example "LWL.exe, UserInit.exe")
It also creates the key if it did not exist previously.
Viewing managed computers

Administrators can view summary information of a managed desktops from the vWorkspace Management
Console. Administrators can also remotely access a user’s active RDP session. See To access a remote desktop
using RDP on page 47 for more information on this option.
• To view summary information for managed computers
• To View tasks for managed computers
• To view logs for managed computers
To view summary information for managed computers

2 Navigate to the computer group to which the computer belongs (Location | Location | Session Host or
Desktops), and highlight the computer group.
3 Select the Computers tab in the information pane, and then highlight the computer.
4 Click Toggle Lower Pane from the toolbar of the information pane.
This enables the lower pane with three tabs: Summary, Tasks, and Log.
5 Select the Summary tab to view property and status information.
vWorkspace 8.6.3
96
To View tasks for managed computers
5 Select the Tasks tab to view tasks performed on the selected computer. Use the Actions menu and
toolbar of the tasks pane to refresh information or cancel tasks.
To view logs for managed computers

5 Select the Log tab to view log information.
Initializing a computer
When a managed computer (virtual or physical) is added to a computer group, the vWorkspace Data Collector
Service must be installed to allow the managed computer to communicate properly with vWorkspace
Connection Brokers.
This process is accomplished using the Initialize Computer task, which is initiated and executed by the
Connection Broker.
Initialization triggers
The following events can trigger the Initialize Computer task:
• Successful clone operation
• Add/Import desktops
• Missed heartbeats
To initialize a computer
1 The Connection Broker checks for the IP address of the computer to be initialized by querying the
Virtualization Host. For other/physical system type computers, it checks for the issuing DNS or NetBIOS
name resolution queries.
2 After the IP address of the target computer has been retrieved, the Connection Broker attempts to
connect to the Data Collector service on that computer using TCP port 5203. If successful, it queries for
the version of the Data Collector service.
3 If the Connection Broker is unable to connect to the Data Collector service, or if the version of the Data
Collector service on the target computer is older than that running on the Connection Broker, the
Connection Broker attempts to install the newer version of the service by remotely connecting to the
Windows Service Control Manager and system drive of the target managed computer.
It then stops the Data Collector service if it is running and copies the newer version of PNDCSVC.exe to
the Windows\System32 folder. After the file has been copied, the Connection Broker issues a remote
command to start the Data Collector service.
vWorkspace 8.6.3
97
4 When the Data Collector service is started on the target computer, the Connection Broker again attempts
to contact the Data Collector service on TCP port 5203. If the connection is successful, the Connection
Broker passes the following to the Data Collector service:
• List of all available Connection Brokers.
• Informs the Data Collector service to use TCP port 5201 when initiating connections to a
Connection Broker.
• Request that subsequent connections be encrypted, and provides the public key to use for SSL
encryption, if configured.
• Configured heartbeat interval (the interval at which the Data Collector service will send status
updates to the Connection Brokers).
• Information about the License Mode for the vWorkspace infrastructure.
• Assigned Unique Computer ID for the computer.
When an Initialize Computer task is unsuccessful, the Connection Broker considers the desktop unusable and
marks it offline, making it unavailable to users. Some common causes of a failure include:
• Firewalls are blocking the communications between the Connection Broker and the managed
computer.
• Name resolution issues.
• Insufficient privileges held on the managed computer. You need to be able to connect to the
administrator file shares and have the privilege to create a service on the managed computer.
The privilege is set in the Properties of the computer group, in Computer Administrative
Account.
To manually initialize a computer or multiple computers

2 Select the computer group (Locations | Location | Session Hosts or Desktops).
3 From the Computers tab of the information pane, highlight the computers that are to be initialized.
4 From the information pane toolbar, right-click to select the Initialize option or select
Actions | Initialize.
Virtual Desktop Extensions (VDE)

Virtual Desktop Extensions (previously called PNTools) is a set of executables, dynamic link libraries, and
device drivers that provide features and management functionality for managed computers in a vWorkspace
infrastructure. VDE’s can be installed on all computers, virtual or physical, that are members of a computer
group in the Desktops node.
VDEs provide the following:
• Data Collector
• Seamless window display mode
• User Profile Management
• Full-fledged desktop or published application sessions
• Performance Optimizations
To install Virtual Desktop Extensions

The installation program for VDE is located in the following folder on all Connection Brokers:
ProgramFiles(x86)\Quest Software\vWorkspace\PNTools\pntools.msi
There are several ways to install, upgrade, or uninstall VDEs:
vWorkspace 8.6.3
98
• Use PNTools | Install/Update from the context menu of a specific managed computer group or managed
computer on the vWorkspace Management Console.
• To define a package for VDE, use the vWorkspace Management Console, Packaged Applications node,
MSI Packages option. See MSI Packages for more information.
• Use the Automated Tasks option. See Task automation for more information.
• Manually install Virtual Desktop Extensions.msi into the virtual computer template.
• Use third-party software distributions.
To install Virtual Desktop Extensions on Windows 7 SP1 virtual machines

If you are installing VDE on Windows 7 SP1 virtual machines, apply the following updates to take advantage of
the performance enhancements available with the Remote Desktop Protocol (RDP) update for Windows 7:
1 Hotfix for DTLS in Windows 7 SP1. https://support.microsoft.com/en-us/kb/2574819
2 Hotfix for RDP 8.1 on Windows 7 SP1. https://support.microsoft.com/en-us/kb/2923545
3 Group policies that enable the functionality in the virtual machine.
• Set Computer Configuration | Administrative Templates | Windows Components | Remote
Desktop Services | Remote Desktop Session Host | Remote Session Environment | Enable Remote
Desktop Protocol 8.0 to Enabled.
• Set Computer Configuration | Administrative Templates | Windows Components | Remote
Desktop Services | Remote Desktop Session Host | Connections |Select RDP Transport Protocols to
Use both UDP and TCP.
4 Restart your computer.
Defining targets
Use the Targets node on the vWorkspace Management Console to define the list of accounts and definitions that
are used in target assignments for a resource. vWorkspace uses targets to assign resources such as managed
applications, and connection policies to users connected to a virtual workspace.
A user can belong to more than one target definition. Target assignments are cumulative (users receive the
assignments of all of the target definitions they are members of, except when a conflict exists).
In the case of a conflict, the client with the highest priority takes precedence. Target types at the top of the list
have higher priority than those lower in the list. The settings Yes, No, and Defer to End User have priority over
Undefined. You can modify priority by using the green Move Up or Move Down options from the toolbar, or from
the context menu of the target name.
To define targets by users

Define a trusted Windows domain or local user account.
1 In the navigation pane of the vWorkspace Management Console, expand the Targets node.
2 Right-click on the Users node, and select New users.
• To add users by selecting from a domain, do the following:
a On the Add Targets step, click the Users tab.
b From the Domain list, select a Windows domain or computer.
c In the Enter the User field, type the user name, or select the user from the list in Select the
Users.
d Click OK.
• To add users by selecting them from Active Directory, do the following:
a On the Add Targets step, click the Active Directory tab.
vWorkspace 8.6.3
99
b From the Domain list, select the Windows domain.
c In the Display section, select Organizational Units, Users, or both.
d In the Filter field, enter a specific or partial name. You can also enter an asterisk (*) as a wild
card.
e Click Refresh. The system displays a list of organizational units or users in the bottom pane.
f Select one or more of the items, and then click OK.
To define targets by groups

Define a trusted Windows domain or local group account.
2 Right-click on the Groups node, and then select New Targets.
• To add groups by selecting them from a domain, do the following:
a On the Add Targets step, click the Groups tab.
b From the Domain list, select a Windows domain or computer.
c In the Enter the Groups field, type the user name, or select the group from the list in Select
the Groups.
d Click OK.
• To add groups by selecting them from Active Directory, do the following:
a Right-click on the Groups node, and select New Targets.
b On the Add Targets step, click the Active Directory tab.
c From the Domain list, select the Windows domain.
d In the Display section, select Organizational Units, Groups, or both.
e In the Filter field, enter a specific or partial name. You can also enter an asterisk (*) as a wild
card.
f Click Refresh. The system displays a list of organization units or groups in the bottom pane.
g Select one or more of the items, and then click OK.
To define targets by device address

Define IP address assigned to the client hardware device.
2 Right-click on the Device Addresses node, and then select New Device Addresses.
3 Click the Device IP Addresses tab and enter a Starting Address and Ending Address to define the client
IP address or a range of addresses.
4 Click OK.
To define targets by device name

Define the NetBIOS name of the client device.
2 Right-click on the Device Names node, and then select New Device Names.
3 On the Device Names tab, enter the device names, separated by a semicolon (;). To enclose a range, use
square brackets ([]). For example W2K3-[0-10].
4 Complete the information on the Active Directory tab.
a From the Domain list, select the Windows domain.
vWorkspace 8.6.3
100
b In the Display section, select Organizational Units, Computers/Client Names, or both.
c In the Filter field, enter a specific or partial name. You can also enter an asterisk (*) as a wild
card.
d Click Refresh. The system displays a list of organization units or groups in the bottom pane.
e Select one or more of the items.
5 Click OK.
To define targets by organizational unit

Use the following procedure to define targets by the Active Directory organizational unit containing the user,
group, or computer account.
2 Right-click on the Organizational Units node, and then select New Organizational Units.
3 Select the Domain from the list.
4 In the Display section, select Organization Units.
5 In the Filter field, enter a specific or partial name. You can also enter an asterisk (*) as a wild card.
6 Click Refresh. The system displays a list of organizational units in the bottom pane.
7 Select one or more of the organization units, and then click OK.
Advanced targets
Advanced Targets allow you to create target groupings based on logical criteria. You can granularly limit the
scope of a resource assignment. Multiple conditions can be combined into a single target that is assigned to a
resource such as a printer, a connection policy or a managed application. A condition is defined by providing a
target field, a function, and a value.
Additional conditions can be created. Logical operators AND and OR can be applied between each condition.
Conditions can also be grouped. Within each group a logical operator can be applied, and separate logical
operators can be applied between multiple condition groups or between single conditions and condition groups.
To create an advanced target

2 Right-click on the Advanced node, and select New advanced targets.
3 In the Target Name field, enter a name for the new target.
4 Click the Click here to add a condition link to display the Advanced Target Condition step.
5 Select the target fields that will be compared to the values that you specify (see Table 52), and then
click Next.
6 Click Step 2: Operator/Function. Select the function used to evaluate the target field (See Table 53), and
then click Next.
7 Click Step 3: Value. Specify the value for the condition.
NOTE: Values are dependent on the type of Target field. For example, setting the target field to Device
Address presents the administrator with an IP address input field. Selecting Day of the week - UTC
presents a drop-down list with days of the week. Other Target fields, such as Two-factor Authentication,
have no value assignment.
vWorkspace 8.6.3
101
8 Click Finish.
Table 52. Advanced target condition fields
Target Field Description

User account The end user’s account in the format: domain\user.
User Group The end user’s group in the format: domain\group.
Computer The desktop or RDSH server hosting the user’s
session.
Computer Group The computer group to which the host computer
belongs.
Organizational Unit The end user organizational unit.
Device Address The device address of the end user’s access device.
Trusted Entry Point The last hop IP address of the end user’s connection
to the connection broker, such as vWorkspace
Secure Access service or Web Access.
Device Name The name of the end user’s access device.
Connector Type (Legacy The type of vWorkspace Connector.
Connectors)
Launch Apps Using The type of Connector used to launch applications.
Web Browser The web browser used by the end user.
Connector Version The version of the Connector.
Two-factor Authentication The client two-factor authentication.
Day of the Week - UTC The day of the week based on Coordinated
Universal Time (UTC).
Day of the Week - Client Local The day of the week based on the time zone of the
end user’s access device.
Time of Day - UTC The time of day based on Coordinated Universal
Time (UTC).
Time of Day - Client Local The time of day based on the time zone of the end
user’s access device.
Date - UTC The date based on Coordinated Universal Time
(UTC).
Date - Client Local The date based on the time zone of the end user’s
access device.
Web Access Site The vWorkspace Web Access site name.
Operating System The operating system of the end user’s device
(Windows, Mac, iOS, Android, Linux, ChromeOS,
ThinOS).
Table 53. Advanced targets functions
Functions Description
Is Equal to Returns true if the target field is equal to the
specified value.
Is Not Equal to Returns true if the target field is not equal to the
specified value.
Is Greater Than Returns true if the target field is greater than the
specified value.
Is Greater Than or Equal to Returns true if the target field is greater than or
equal to the specified value.
vWorkspace 8.6.3
102
Table 53. Advanced targets functions
Functions Description
Is Less Than Returns true if the target field is less than the
specified value.
Is Less Than or Equal to Returns true if the target field is less than or equal
to the specified value.
Matches Pattern Returns true if the target field matches the
specified wildcard pattern value. Use an asterisk (*)
to match zero or more characters, use a question
mark (?) for single characters, and use [a-z] for
character ranges.
Does Not Match Pattern Returns true if the target field does not match the
specified wildcard pattern value.
Is in the List Returns true if the target field matches at least one
item in the specified list of values.
Is Not in the List Returns true if the target field does not match any
items in the specified list of values.
Is in the Range Returns true if the target field is between the
specified from/to values (inclusive).
Is Not in the Range Returns true if the target field is not between the
specified from/to values.
Is Required Enforces the Target Field parameter.
Managed applications
Before an application can be published and accessed by users, it first must be installed on the hosting computer.
In a vWorkspace infrastructure, the hosting computer can be any of the following:
• Microsoft RD Session Hosts
• Managed Computers
• Virtual Applications
From the Managed Applications node, you can enable Graphics Acceleration globally for managed and
unmanaged applications, set custom properties, and set permissions for users for all managed applications.
For more information, see Managed Applications on page 160.
Connector management overview

The Connector Management node allows you to centrally create and manage the configuration of all of your
vWorkspace Connectors. From the Connector Management node, you can use the following nodes to set up
Connector Management.
• Installation. Define the software download location and minimum required version for each Connector.
• Configuration. These define how a user connects, and the default settings for the connection.
• Policies. Allows administrators to override the default settings based upon business or security
requirements.
After creating a client configuration, you can deploy the configuration to client devices. Connector
configuration allows you to detect vWorkspace Connectors on client devices, easily deploy Connector updates to
any platform, and push Connector configurations to end users, all managed from a central location.
The following sections provide information for setting up the installation location, creating a configuration, and
setting connection policies.
• Connector management installation
vWorkspace 8.6.3
103
• Connector management configuration
• Setting Connection Policies for Connectors
• Deploying Connector updates
Connector management installation

The Connector Management Installation node allows you to define the software download location and minimum
required version for each type of Connector.
You can use this node to set up the location from which users install the Connector by specifying a URL or a
shared file location. The location should be accessible to all users. Shared file locations work only for non-
mobile devices that have file access to the shared location.
When users connect to vWorkspace, the version of their Connector will be validated against the specified
version. If a new version of the Connector is required, the user will be redirected to the installation location to
upgrade.
To enter an installation location and required version for a Connector type

1 From the Management Console, open the Connector Management node.
2 Click the Installation node.
3 Select the Connector operating system you want to modify.
4 Click Properties.
5 On the Setup Location step, specify the location of the vWorkspace Connector software. You can use the
Test Location (check mark) button to test the connection to the location. The following types of hosting
can be used:
• Broker-hosting. If you want to host the setup file on the connection brokers, specify the name of
the setup file. vWorkspace will automatically locate the file in the Connectors sub-folder on the
connection broker. For example:
%ProgramFiles(x86)%\Quest Software\vWorkspace\Connectors. 
This is the simplest way to deploy. The same version of the setup file must be present on all
connection brokers. Large deployments may want to consider using an internal or public website
to host the vWorkspace Connector software to reduce stress on the connection broker.
• Internal Website. Place the installation files in an existing Web Access or other site. You must
specify the full URL to the Connector-specific file.
• Public Website. This is similar to an internal website, but accessible from anywhere, such as a
third-party host. This is useful for mobile users. You must specify the full URL to the Connector-
specific file.
• File share. Used mainly for Windows, Mac or Linux deployments on internal networks. All end
users must have file access or a drive mapping to the share. You can specify the format
\\server\path\..\file or drive:\path\..\file.
6 Click Requirements. On the Requirements step do the following:
a Specify the minimum version for this Connector. Check this box if you want to specify the
minimum version that the user must have installed to run vWorkspace. If you do not specify a
minimum version, the version of the users’ Connectors will not be validated while connecting to
vWorkspace.
b Version. Enter the minimum version for the selected Connector. If the user does not have this
version, an upgrade to the newer version will be offered.
c Require a valid Connector before continuing. If this option is selected, and a Connector is not
detected or a new version is required, users will not be permitted to connect to their
applications.
7 Click OK.
vWorkspace 8.6.3
104
Connector management configuration
You can use the Connector Management Configuration node to create one or more client configurations. After
creating a configuration, you can assign the configuration to targets.
To create a Connector configuration

2 Click Configuration | New Configuration. The Connector Configuration Wizard is displayed.
3 Click Next to continue. The General step is displayed.
4 Enter the necessary information on each step (see Connector Configuration properties on page 106), and
then click Finish.
vWorkspace 8.6.3
105
Connector Configuration properties
Table 54. General
General field Description

Name Specify a friendly name for this Connector configuration,
which will display in the Connector Management
Configuration node step. This name will also be displayed in
the users’ configuration properties.
Table 55. Connectivity
Connectivity fields Description

Location Two default connection locations are initially available from
the list. This field determines the location you will modify.
Test connection Use to test the connectivity settings for a location. You will
be prompted to log into the domain.
Rename Use this button if you want to customize the location name,
such as Office or Home.
Add location Click this button to add a new location.
Remove location Click this button to remove a location.
Properties for location
These settings are used to communicate with the Connection Broker, and are configured
separately for each location.
Access Type Select the access type for the connection.
Direct to connection broker as defined. The All connection
brokers names list will be populated with all of the
connection brokers defined in the Management Console. You
can also specify the Protocol and port. If the list of
Connection Brokers does not reflect all connection brokers,
you can click Refresh.
NetBIOS Name: (Windows) Short name.
IP address.
FQDN: Fully Qualified Domain name, which can be used if
the other names cannot be determined.
Web Access Broker Connection. Goes through a Web Access
Site (DMZ). The list is populated with your Web Access
servers. You can select the ones you want to use for this
configuration. The protocol and port are specified, and
cannot be changed.
Secure Access service Broker Proxy. Populated with the list
of Secure Access services set up in vWorkspace. If the port is
specified, you cannot change it. Users typically come from
outside location.
Custom. Define a custom access type.
Protocol Use either HTTP or HTTPS.
TCP Port Use to specify the port in which the Connection Broker
listens on for inbound connection requests.
Servers Use Add to enter the host name, FQDN or IP address for a
Connection Broker.
IMPORTANT NOTE: You must use FQDN when traversing the
SSL Gateway.
Use the arrow buttons to change the order in which the
connections are attempted.
vWorkspace 8.6.3
106
Table 56. Firewall/proxy traversal
Firewall/Proxy Traversal fields Description

Connection Options for Location
These settings are used to specify secure network communications.
Location Displays the location that you selected on the Connectivity
tab. You can change this to manage Firewall/Proxy Traversal
settings for a different location.
Enable NAT support for firewall Use this when vWorkspace enabled Session Hosts are located
traversal behind a firewall that is using Network Address Translation
and Alternative Addressing.
Enable RDP over SSL/TLS Use SSL/TLS encryption of RDP session traffic.
Secure Access server Use this to enter the FQDN or IP address of the Secure Access
service server.
This option is only available when Enable RDP over SSL/TLS
is selected.
NOTE: You must use FQDN when traversing the SSL Gateway.
Proxy Server for Location
These settings are used when the vWorkspace client device is located behind a NAT enabled
firewall and Socks Proxy Servers are used to gain access to the outside network.
Use the default from the system Use if the proxy settings are the same as those used by
Internet settings Internet Explorer.
Do not use a proxy server Use if you do not want to set a proxy server.
Enter an address manually Use to indicate the address as entered.
The address must be entered in the following format:
proxyserver:port
proxyservername = host name, FQDN, or IP address of the
Socks Proxy Server.
port = TCP port number the Socks Proxy Server is listening
on.
Do not use proxy server for Use to list proxy server exclusions.
addresses beginning with: Use semicolons (;) to separate the entries.
Table 57. Authentication

Credentials Settings fields Description
Use cached credentials Uses credentials from the Windows credentials cache on the
client device.
To use this option, Enable Credentials Pass-Through
(Settings | Authentication) must be enabled.
Use Kerberos/Network Level Uses the Kerberos or NLA protocols.
Authentication credentials To use this option, the client device must be a member of
Microsoft Windows Active Directory domain and the user
must log onto the device using their domain user account
and password.
Check the Initial authentication only box if you want to use
Kerberos/NLA only on initial authentication.
vWorkspace 8.6.3
107
Table 57. Authentication
Credentials Settings fields Description

Prompt for credentials Select this option if you want the Connector to always
prompt for credentials. If you select this option, you can also
enable the following:
• Specify a default domain. As a convenience to the
end user, the administrator can specify a domain
name that will automatically populate the Domain
text box on the Credentials prompts on the
Connectors.
• Automatically populate the domain field using the
computer’s domain. This option will automatically
populate the Domain text box on the Credentials
prompts with the device's computer domain name.
This does not apply to mobile devices.
• Disable the domain field. Disables the Domain field
so the user cannot enter a domain in that field. This
is used in conjunction with the two previous options.
If neither Specify or Auto Populate are specified, and
the Domain field is disabled, the end user must enter
their user name in either UPN or down-level logon
formats.
If the Domain field is not disabled, the end user can
skip the Domain field and enter their credentials in
UPN or down-level logon formats.
• Do not allow users to save credentials. If selected,
the Save Credentials checkbox will be disabled on the
Connectors.
Login anonymously Check this box if you do not want to prompt users for
credentials while logging in. The global setting for
Anonymous Authentication must be selected. See Overview
of the vWorkspace environment on page 54 for information
abut anonymous login.
Table 58. Display
Display fields Description

Display configuration Sets the remote session window size during a full desktop
connection.
Colors Sets the remote session color depth.
Display the connection bar when Displays a connection bar when the session is in full screen
in full screen mode mode.
Pin Connection Bar option disables the connection bar auto-
hide feature.
Enable Smart Sizing Smart Sizing is functional when connecting to a full desktop.
The content of the session window is scaled to fit within the
window on the client device.
Display remote applications Enables the remote application to display its own window on
seamlessly on local desktop the client device, allowing it to have the same look and feel
as if it were installed on the client device.
This setting also enables session sharing, which allows
multiple remote applications to run through a single session,
given those applications are installed on the same Session
Host or Managed Computer.
NOTE: On mobile devices, the seamless application will be
displayed in a full screen.
vWorkspace 8.6.3
108
Table 59. Local resources
Local Resources fields Description

Remote audio Bring to Local Computer. Plays sound from the remote
session only on the local device.
Leave at Remote Computer. Plays sound only on the
remote session’s host computer.
Do not Play. Disables all sounds in remote desktop
sessions.
Keyboard These options apply to Windows shortcut key
combinations, such as Alt+Tab (different Connectors may
have different hotkey settings).
On the local computer. Configures your connection so that
Windows shortcut keys always apply to your local desktop.
On the remote computer. Configures your connection so
that Windows shortcut keys always apply to the desktop of
the remote computer.
In full screen mode only. Configures your connection so
that Windows shortcut keys apply to the remote computer
only when the connection is in full screen mode.
Local devices and resources
These settings determine which client side devices are available to the remote applications or
desktops.
Printers Local printers. Standard Windows print drivers are used for
printing, so the appropriate drivers need to be installed on
both the client devices and the remote computer.
Clipboard Enables redirection of copy and paste functionality.
NOTE: If you disable this feature, drag-and-drop
functionality will also be disabled.
Microphone Enables support for applications that require the use of a
microphone.
Universal printers Optimizes performance and simplifies session host
maintenance by using a vWorkspace universal print driver
for client printing.
USB Devices Devices that are attached to a USB port on a client device
can synchronize with applications running in a remote
session.
More Click this button to display the Remote Desktop
Connection window, where you can choose the devices and
resources on this computer that you want to use in your
remote session.
• Smart Cards
• Ports
• Drives
• Other supported Plug and Play devices
vWorkspace 8.6.3
109
Table 60. Experience
Experience fields Description

Choose your connection speed The options are:
to optimize performance • Modem (28.8 Kbps)
• Modem (56 Kbps)
• Low-Speed broadband (256 Kbps - 2 Mbps)
• Satellite (2 Mbps - 16 Mbps with high latency)
• High-Speed broadband (2 Mbps - 10 Mbps)
• WAN (10 Mbps or higher with high latency)
• LAN (10 Mbps or higher)
• Detect connection quality automatically
Allow the following These options are used to create a custom setting:
• Desktop background
• Font Smoothing
• Desktop Composition
• Show contents while dragging
• Menu and window animation
• Visual Styles
NOTE: If Desktop Composition (Windows Aero) is enabled,
Graphics Acceleration is disabled.
Optimizations These options are used to automatically enable
optimizations when logged on to the remote computer:
• Flash Acceleration. Allows flash content (such as
Youtube) to be played on the client computer,
leveraging the resources of the client computer and
providing an optimal user experience.
• WAN Acceleration. accelerates RDP traffic on wide
area networks (WANs). This provides for an improved
user experience by providing faster RDP screen
responses and improved performance of all
optimization features.
• Graphics Acceleration. Reduces bandwidth
consumption and dramatically improves the user
experience, making RDP usable over WAN
connections.
Persistent bitmap caching Reduces bandwidth usage by storing images on the computer
for later use.
Reconnect if connection is Allows for automatic reconnection if connection is dropped.
dropped
vWorkspace 8.6.3
110
Table 61. Password Management
Password Management fields Description

Dell One Identity Password Select this option if you want to use Dell One Identity
Manager Password Manager to reset passwords.
Server URL. Enter the URL that points to the Dell One
Identity Password Management server.
vWorkspace password reset Select this option if you want to use vWorkspace password
service reset service to reset passwords.
Server Name or IP Address. Enter the Server Name or IP
Address (the FQDN of the vWorkspace Password Management
Server).
Port. The TCP port to which the vWorkspace Password
Management Server has been configured. The port is usually
443.
Table 62. Desktop Integration
Desktop Integration fields Description

Allow client shortcuts on This option controls where the placement of shortcut icons
occurs when the Connector is started in Desktop Integrated
mode:
• Desktop
• Start Menu
• Start Menu/Programs
NOTE: The placement of shortcuts when either Start Menu or
Start Menu \ Programs are selected depends on whether
Windows is using the Standard or Classic start menu.
vWorkspace Application This option is used to specify the name of managed
Extensions applications that have been configured for Application
extensions to specify preferred file types.
Use the ellipsis to browse for applications that have been
configured or click Add and enter the name of a configured
application.
NOTE: The managed application must be configured with
%Connector_ARGS% in the argument field. See Windows
Client registry settings for more information.
Table 63. Auto-Launch

Auto-Launch fields Description
Auto-launch application This option is used to specify applications that are to be
launched automatically when the Connector is started.
This option is for the Connector in desktop integrated mode,
or if an environment is connected to automatically at
startup.
NOTE: Only the first application found is automatically
launched.
vWorkspace 8.6.3
111
Table 64. Target Assignments
Target Assignments fields Description

Target Assignments Select the targets that you want to assign to this Connector
configuration by doing the following:
1 Click on the blue plus sign.
2 Select a target from the list, or click the green plus sign
to add a target.
3 Browse for the user on the Add Target(s) window, and
then click OK.
4 Select the added targets from the Select Targets window,
and then click OK.
See Defining targets on page 99 for more information about
targets.
Table 65. Permissions
Permissions fields Description

Permissions Identify users and groups who can modify these settings.
To modify a configuration
2 Click Configuration | Configuration Properties. The Connector Configuration Properties is displayed.
3 Modify the fields as necessary (see Connector Configuration properties on page 106).
4 Click OK.
To delete a configuration
1 From the Management Console, open the Connector Management node, and click Configuration.
2 Select the configuration that you want to delete.
3 Click Delete.
4 Click OK.
Adding targets to a configuration

2 Select the configuration that you want to add a target to.
3 Click Add Targets.
4 Select the target that you want to add to the configuration.
5 Click OK.
Assign targets to a configuration

2 Select the configuration that you want to assign a target to.
3 Select the targets that you want to assign to the configuration.
Unassigning targets
2 Select the configuration that you want to add a target to.
3 Click Unassign Targets.
vWorkspace 8.6.3
112
4 Select the target that you want to unassign from the configuration.
5 Click OK.
Setting Connection Policies for Connectors

Connection policies can be used with Connector configurations to restrict or require specific local resource and
experience settings. Connector configurations set default values for these settings, which can be overridden by
users. Use connection policies to enforce these settings (turn on or off) and disallow the end user from
modifying them.
There are four possible values for each setting:
• Yes/No. Set the values (according to each setting's description) and prevent the end users from
modifying those values on their local devices.
• Defer to End User. Does not enforce the setting and allows the end users to modify it.
• Undefined. Allows the connection policies to be applied in a layered manner, with narrower policies
applied to more specific targets over more general policies applied to many targets. 
For example, you may want to turn on the remote clipboard for all users, but allow USB devices only for
system administrators. To accomplish this, you could create two connection policies: ClipboardPolicy and
USBPolicy. In ClipboardPolicy you would set the Clipboard value to Yes and USB Devices to No. In the
USBPolicy you would set the Clipboard value to Undefined and USB Devices to Defer to End User. Then
assign the policies to user and admin groups as follows:
Table 66. Connection policies
Policy Clipboard Setting USB Setting Target Assignment

USBPolicy Undefined Defer DomainAdminsGroup
ClipBoardPolicy Yes No DomainUsersGroup
The order that your targets appear in the management console affect the order in which the policies are
applied. The top-most targets that are assigned a policy with a Yes, No, or Defer setting take precedent. In this
scenario, users that are members of DomainUsersGroup but not DomainAdminsGroup will be forced to use
clipboard (ClipboardPolicy:Clipboard=Yes) and not permitted to use USB (ClipboardPolicy:USB=No). On the other
hand, users that are members of both DomainAdminsGroup and DomainUsersGroup will be forced to use
clipboard (ClipboardPolicy:Clipboard:Yes) and permitted (but not required) to use USB (USBPolicy:USB:Defer).
Administrators are still forced to use Clipboard since that setting is Undefined in the USBPolicy.
NOTE: Connection policies take effect after the first login to an environment, since the policy information
is sent to the end users' devices after authentication.
To define new connection policy properties

2 Expand the Connector Management node, right click on Policies and then select New Connection Policy.
3 On the Welcome step of the Connection Policy Wizard, click Next.
4 On the Name step, enter a name for the connection policy, and then click Next.
5 On the Remote Computer Sound step, select a setting, and then click Next.
6 Define the local device settings, and then click Next.
7 On the Experience Optimizations step, enable the performance optimizations that you want used when
logged into the remote device.
8 On the Target Assignments step, assign targets to this connection policy by doing the following:
a To add targets, click on the blue plus sign.
b Select a target from the list, or click the green plus sign to add a target.
c Browse for the user on the Add Target(s) step, and then click OK.
vWorkspace 8.6.3
113
d Select the added target from the Select Targets step, and then click OK.
e Click Next.
9 On the Permissions step, enter the appropriate permissions.
10 Click Finish.
Deploying Connector updates

The Policy-based Connector configuration allows you to detect vWorkspace Connectors on client devices, deploy
Connector updates to any platform, and push Connector configurations to end users, all managed from a central
location.
Policy-based configuration
The simplest way to initially deploy and configure native Connectors that support policy-based configuration is
to direct your end users to a Web Access site. The site automatically detects, installs and configures the users’
devices, based on the Connector Management settings in the Management Console.
After a native Connector is installed and configured, users can launch the native Connector without going
through a Web Access site. The Connector will automatically check for updates to its configuration and new
versions of the application, based on the Connector Management settings.
See Installing vWorkspace Connectors on page 25 for information about how users install and upgrade the
vWorkspace Connector for Windows.
Legacy Connectors
vWorkspace Connectors previous to version 8.5 that do not support auto-detection and policy-based
configuration can still benefit from centrally-managed Connector configurations. Any configuration managed in
the Management Console can be accessed directly from the connection brokers or through Web Access sites.
Your legacy Connectors can use these direct links to download configurations.
To access the configurations from legacy Connectors, your environment must be configured to not require
authentication for configuration requests. This can be set on the Farm Properties dialog in the Management
Console (Authentication | Connection Configuration).
To deploy and configure native Connectors

1 If you want to enable email address-based discovery of the Connector, create the DNS service record (see
Creating a DNS service record for email address-based discovery).
2 From the vWorkspace Management Console, select Configuration node | Select a configuration.
3 Click Deployment.
• Policy-Based Configuration
• Legacy Connectors
5 Copy the link of the Website that you want to distribute.
6 Direct your users to the correct Web Access sites by distributing the hyperlink by email or other means.
vWorkspace 8.6.3
114
Creating a DNS service record for email address-based
discovery
Email address-based discovery makes it easy for users to discover and log into an environment. If you want to
enable email address-based discovery for the Connector configuration login process, create the following DNS
service record for the vWorkspace environment.
To configure a DNS service record

This procedure is for Windows Server 2012. For other DNS platforms, see documentation for each platform.
1 On the DNS server, click Start, click Administrative Tools, and then click DNS.
2 In the console tree for your domain, expand Forward Lookup Zones, and then right-click the domain.
3 Click Other New Records.
4 In Select a resource record type, click Service Location (SRV), and then click Create Record.
5 Click Service, and then type _vworkspace.
6 Click Protocol, and then type _tcp.
7 Click Port Number, and then type 443.
8 Click Host offering this service, and then type the FQDN of the Web Access site or connection broker.
9 Click OK, and then click Done.
User Environment Management

The User Environment Management node includes a list of child nodes that provide for the creation of objects
that are assignable to targets within the Management Console. Each child node manages a specific component
of the virtual workspace and allows administrators control over aspects of a user’s session when connected to
the vWorkspace infrastructure.
The following table provides a list of the available User Environment Management options and a description of
each.
Adding user environment management options

1 From the Management Console, expand User Environment Management.
2 Right click on the node you want to add, and click New to display the corresponding wizard.
3 Complete the wizard as necessary.
The following table provides a list of the available User Environment Management options and a description of
each.
Table 67. User Environment Management options
Resource Name Description

Additional customizations The ability to customize items relating to the
Windows Desktop, Start Menu, drive mappings, and
network mappings.
Color schemes The ability to assign standard Windows color
schemes.
Drive mappings The ability to assign network drive mappings to
clients without logon scripts or Active Directory
Group Policy.
Environment variables The ability to assign user environment variables
that are automatically created and removed.
vWorkspace 8.6.3
115
Resource Name Description

Printers The ability to assign shared printers on LAN or WAN
based Windows print servers by using either the
vWorkspace Universal Printer or Windows native
print drivers.
Registry tasks The ability to assign per-session modifications to
user’s HKCU registry hive.
Scripts The ability to assign scripts on a per-session basis to
vWorkspace clients without having to modify
Session Host’s complex login script sequence or the
Active Directory Group Policy.
Time zones The ability to assign time zones on a per-session
basis.
User policies The ability to assign user level policies on a per-
session basis.
Wallpapers The ability to assign Windows wallpaper to
vWorkspace clients.
User Profile Management

User profiles are used to define storage servers, assign compression levels, define silos, and assign permissions
to users so that they can be allowed to or denied access to adding, modifying, or deleting Virtual User Profiles.
User profile properties can be configured after components have been installed on the appropriate servers.
For more information, see User profile management on page 239.
Application layering
An Application Layer is a virtual hard disk that contains the components that are present for an application. See
the Dell Wyse vWorkspace WSM Administrator’s Guide for detailed information about application layering.
To layer applications with a VDI desktop session

1 Install the necessary components.
a Install the WSM role (see Installing vWorkspace: Advanced method on page 16).
b Install the Web API rest service (see Prerequisites for WSM integration on page 13).
c Install the WSM Client tool on the VDI template (see Installing the WSM Client in the Dell Wyse
WSM Administrator’s Guide).
2 Using the WSM tools, create an application layer.
a Use the WSM Virtual Image Disk Creation utility to create a disk (see Capturing an Application
Image from the Reference Device in the Dell Wyse WSM Administrator’s Guide).
b Use the WSM Console to import the application layer (see Assigning the Application Image to User
Groups in the Dell Wyse WSM Administrator’s Guide).
IMPORTANT: Do not assign the application layer to users or groups at this stage in WSM.
Application layer assignment will be done in Step 3.
3 Integrate WSM with vWorkspace.

a Create a VDI desktop group that uses the VDI template referred to in step 1c. (Setting up a virtual
desktop environment on page 43).
vWorkspace 8.6.3
116
b Import the WSM layers into vWorkspace and assign application layers to users and desktops. The
series of steps below come from the vWorkspace.WebApi.demo.PS1, which is located in the
vWorkspace ZIP file's WSM folder. For simplicity, copy this file to the server that is used to install
the vWorkspace WebAPI (step 1b).
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# Step 1: Every new PowerShell session setup
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# This line should point to the location of the vWorkspace.WebApi.psd1 file
# This is installed with the WSM Web API components
Import-Module "C:\Program Files (x86)\Wyse vWorkspace WebAPI\vWorkspace.WebApi"
# Here is where you set up access to the vWorkspace web api

# Replace 'webApiServer' in the command below with the server running the web api
# Replace 'FarmAlias' in the command below with the name of the farm
# This cmdlet will then prompt the user for credentials, the credential specified
# must be a pre-defined vWorkspace administrator
Connect-DVWFarm -WebApiAddress "http://webApiServer:4500/api/farm/FarmAlias"
# Running the cmdlet above without specifying the -Administrator parameter will prompt the user for a
credential
# To specify credentials programatically, see the example below
# The credential specified must be a pre-defined vWorkspace administrator
# $adminCreds = New-Object System.Management.Automation.PSCredential("domain\username", (ConvertTo-
SecureString "password" -AsPlainText -Force))
# Connect-DVWFarm -WebApiAddress "http://webApiServer:4500/api/farm/FarmAlias" -Administrator
$adminCreds
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# Step 2: First time setup
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# This lets you review the WSM servers already in your vWorkspace farm
Get-DVWServer -WSM
# If there is no WSM Core server defined, the line below (New-DVWServer) will let you put one in
# This will only need to be done once ever per farm
# New-DVWServer -Name "wsm-core-server" -AlternateIpAddress "10.4.167.70" -Type "WSMCore"
# This lets you review the settings that allow the vWorkspace api to contact the WSM api
# If they need adjustment (or don't yet exist), the line below (Set-DVWSetting) will let you set them
# This will only need to be done once ever per farm
Get-DVWSetting
vWorkspace 8.6.3
117
# Set-DVWWetting -WSMAPIPort 8082 -WSMUseSSL $false
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# Step 3: Synchronization
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# This synchronizes the WSM servers and then WSM applications
Sync-DVWWSMServer
Sync-DVWWSMApplication
# This lets you review the WSM application layers present in the farm
Get-DVWWSMApplication
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# Step 4: Publish a WSM Application to a desktop group
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# This lets you review the desktop groups present in the farm
Get-DVWDesktopGroup
# This publishes our application to our desktop group
Publish-DVWWSMApplicationToDesktopGroup -GroupName "WSM01" -WSMApplicationName "firefox"
# This lets us review what we just did by listing off all WSM applications published to our desktop group
Get-DVWWSMApplication -GroupName "WSM01"
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# Step 5: Assign a WSM Application to a target
# ::::::::::::::::::::::::::::::::::::::::::::::::::
# This lets you review the targets present in the farm
Get-DVWTarget
# This assigns our application to our target
Publish-DVWWSMApplicationToTarget -WSMApplicationName "firefox" -TargetName "Domain\Domain Users"
# This lets us review what we just did by listing off all WSM applications assigned to our target
Get-DVWWSMApplication -TargetName "Domain\Domain Users"
TIP: You can manually edit the psd1 file that is installed with the web api powershell wrapper to view
hidden cmdlets.
If application layers are configured for particular users and desktop groups, the application layer will be
dynamically applied when the user logs into the VDI desktop and later removed on logoff.
vWorkspace 8.6.3
118
Packaged Applications
The Packaged Applications node allows administrators to identify Microsoft Application Virtualization (App-V)
servers, their hosted application packages, and MSI Packages.
Microsoft App-V
Microsoft Application Virtualization (App-V) allows you to stream applications to client computers without
installing the applications directly on those computers. This simplifies tasks such as managing multiple versions
of applications and updating application packages.
You can import, update, and publish App-V applications from the App-V node on the Management Console
To connect to a new App-V server

1 From the Management Console, expand the Packaged Applications node
2 Right click App-V and select New App-V server.
3 On the Welcome to the App-V Server Wizard step, click Next.
4 On the Server Name & URL step, enter the appropriate information for the new App-V server, and then
click Next.
Table 68. Server Name & URL fields
Server Name Enter the server name.

Server URL App-V 4.6: Click in this field to
populate the path to the App-V
Management virtual directory.
App-V 5.0 or later: Click in this
field to populate the path to the
App-V Management virtual
directory. At the end of the path,
add a colon, followed by the port
number (for example: home-
appv5:8081)
If the Server Name field is DNS
unresolvable, the path needs to
be corrected to have the DNS
name or IP address of the server.
NOTE: Multiple connections can
be made to the same server by
entering different friendly names
in the Server Name field.
5 On the Credentials step, enter the appropriate credentials for the new App-V server, and then click
Next.
Table 69. Credentials fields
Account Enter the user name for the App-V

Administrator.
Use the ellipsis to browse to the
user in the directory.
Password Enter the password for the App-V
Administrator.
Use the check mark to check the
password.
vWorkspace 8.6.3
119
6 Specify any permissions that are to be used with this App-V server, and then click Finish.
To edit the properties of an App-V server

1 From the Management Console, expand the Packaged Applications node, and then expand the App-V
node.
2 Right-click on the specified server, and then select App-V Server Properties.
3 On the App-V Server Properties step, edit the properties and click OK.
To import App-V applications

1 From the Management Console, expand the Packaged Applications node, and then highlight the App-V
node.
2 Right-click on the server in the navigation pane and select Import/Update Applications.
If this is the first time that you have imported applications to the specified server, the Welcome step is
displayed.
3 In the Welcome step, select Next.
4 On the Select Applications step, click Refresh to refresh the list. Do one of the following and then click
Next:
• To import all the applications, click Select All.
• To import specific applications, select them on the list by pressing Ctrl and using a left-click.
If importing for the first time, Next is the option to move to the next step. If you are updating
applications, use Apply to save your changes on the current step. Use OK to close the wizard.
5 On the Create Access Groups step, do the following:
a Select the access groups that are to be imported, and click Yes.
b Select the access groups that are not to be imported, and click No.
c Click Select All to import all the groups.
d Click Next or OK.
6 On the Launch Location step, do one of the following:
• To choose all the applications from the list, click Select All, and then select either Client or
Server.
• Select individual applications and then select the Launch Location of Client or Server.
• Click Next or OK.
7 To publish the application on a Session Host, do the following on the Publish On step:
a To publish all on the same Session Host, click Select All. Or to select the specific applications, use
Ctrl + left-click.
b Click Session Host.
c From the Publish On step, select the Session Host, and then click OK.
8 Do the following on the Publish On step to publish the application on a desktop group:
a To publish all on the same desktop group, click Select All. Or to select the specific applications,
use Ctrl + left-click.
b Click Desktop Group.
c From the Publish On step, select the desktop group, and then click OK.
9 From the Publish On step, click Next or OK.
10 On the Launch Location step, select one or more of the applications and then specify if the content is to
be launched on the client or the server.
vWorkspace 8.6.3
120
11 On the vWorkspace Folders step, select one or more applications, and then click Folder(s) to define the
folders in which the application or applications selected should be assigned. Click Manage Folders to
add or change the folders listed.
Applications with a launch location of client may only be assigned to vWorkspace client folders.
12 On the Load Balance step, click Select All or the specific applications by using Ctrl + left-click to specify
the applications for load balancing. Click the Load Balance Wizard to choose the load balancing rule
evaluator for the selected applications.
If you do not want to use load balancing, click Next.
13 On the Desktop Integrations Settings step, specify the location of the shortcuts on the vWorkspace client
host when using the vWorkspace Connector for Windows in desktop integrated mode by doing the
following:
a Select specific applications, or use the Select All button.
b Click Desktop Integration.
c Select one or more of the options, Desktop, Start Menu, Start Menu/Programs, and click OK.
d Click Next or OK on the Desktop Integration Settings step.
14 Review the selections on the Summary step and click Back to make changes or click Finish.
To view and edit imported App-V application properties

1 From the Management Console, click on Managed Applications.
2 View the App-V applications in the right pane. The applications are listed by server name, and their type
is Content on Server or Content on Client.
3 View or edit the properties by right-clicking on the application or select the application and select the
Properties icon.
NOTE: The executable Path and the Type cannot be edited.
To set up the client computer

1 Install the App-V client on the template.
2 From a Powershell command prompt, do the following:
a Set the Execution Policy. ExecutionPolicy: Unrestricted
b Import the appvclient module.
c Set the AppvClientconfiguration. SharedContentStoreMode: 1
d Add the AppvPublishingServer.
• Name: displayname
• URL: http://publishingservername:port
e Sync? AppvPublishingServer. ServerId: 1
3 Stream the application from the server to the client.
MSI Packages
The MSI Packages node is used to define MSI packages that can be deployed, as well as used in the Task
Automation feature.
To add a new MSI package

1 From the Management Console, expand Packaged Applications.
2 Right click MSI Packages and click New.
vWorkspace 8.6.3
121
3 From the Welcome step on the MSI Package Wizard, click Next.
4 On the MSI Package Name step, enter a Name for the MSI package, and then click Next.
This is the name that is displayed in the vWorkspace Management Console.
5 On the Source File step, enter the MSI source file or click the ellipsis to browse, and then click Next.
6 On the Run Location step, do one of the following, and then click Next.
• Execute the MSI file directly from the source location.
• Copy the MSI file to each computer before executing.
• Enter the full path and file name of the destination file in the Destination file field.
7 On the Credentials step, enter the credentials necessary to access the source MSI file, and then click
Next.
8 On the Parameters step, complete the following information, and then click Next.
Table 70. Parameters fields
Enter the parameters necessary Enter the necessary parameters.

for a new installation:
Enter the upgrade code for this Enter the upgrade code.
MSI package. Use Retrieve to get the upgrade
code from the MSI file.
Enter the parameters necessary Enter the parameter necessary to
to perform an update: perform an update.
Enter the parameters necessary Enter the parameter necessary to
to uninstall: complete an uninstall.
Help Select this button for assistance
with the installer parameters.
9 On the Timeout Period step, do one of the following, and then click Next.
• Select the option Select the timeout value, and then specify the Timeout after value by using
the list.
• Select the option, Execute the MSI operation and Continue.
10 On the Permissions step, specify MSI Package permissions, and then click Finish.
Load Balancing
The Load Balancing node is used to create and manage rules used in the load balancing process for Session
Hosts, Microsoft Hyper-V computer groups, and Microsoft SCVMM computer groups.
See Load balancing on page 247 for more information.
Web Access
The Web Access node is used to define and manage vWorkspace Web Access web sites. Web Access is a web
application for vWorkspace environments that enable users to retrieve their list of allowed applications and
desktops using a web browser.
See Using Web Access on page 198 for more information.
vWorkspace 8.6.3
122
Monitoring and Diagnostics
The Foglight® solution simplifies application performance monitoring and reduces the skills and effort required
to manage applications, the user experience, and the supporting infrastructure.
Monitoring and Diagnostics monitors vWorkspace-hosted VDI and Remote Desktop Session Host (RDSH)
implementations providing you with real-time and historical data.
Accessing Monitoring and Diagnostics

From the Diagnostics and Monitoring node in the Management Console, you can access the Welcome to the
Monitoring and Diagnostics window, which gives you immediate access to all the main product capabilities. From
there, you can drill down into the Explorer, or diagnostic pages.
See Monitoring and Diagnostics documentation for detailed information (available from the Help tab on the
right side of the Welcome window).
Figure 22. Monitoring and Diagnostics interface
Accessing Monitoring and Diagnostics from the Management

Console
You can optionally access Monitoring and Diagnostics directly from the vWorkspace Management Console
menu items to see diagnostic information for the selected item.
For example, to see diagnostic information for a specific connection broker, navigate to Locations |
Select a location | Connection Brokers | Right click on a connection broker | Select Monitoring and
Diagnostics. The diagnostic information for the selected connection broker will be displayed, as shown in
the following figure.
vWorkspace 8.6.3
123
Figure 23. Example of diagnostic information
Table 71. Accessing specific diagnostic information from the vWorkspace Management Console
Access Monitoring and Diagnostics
Navigation
information for...
A specific user File | Current User Sessions | Right click on the user | Select
Monitoring and Diagnostics.
A specific user from a session host Locations | Open a location | Session Hosts | Management | Click on a
terminal server in the left pane | Select a user in the right pane |
Select Monitoring and Diagnostics.
A specific connection broker Locations | Open a location | Connection Brokers | Click on a
connection broker | Select Monitoring and Diagnostics.
A managed terminal server Locations | Open a location | Session Hosts | Management | Click on a
terminal server | Select Monitoring and Diagnostics.
A provisioned terminal server Locations | Open a location | Session Hosts | Provisioning | Click on a
terminal server | Select Monitoring and Diagnostics.
A selected desktop group Locations | Open a location | Desktops | Select a desktop group |
Right click on the Desktops tab | Click the desktop group | Select
Monitoring and Diagnostics.
A Hyper-V environment Locations | Open a location | Virtualization Hosts | Click on the
Hyper-V node | Monitoring and Diagnostics.
A specific Hyper-V server Location | Open a location | Virtualization Hosts| Hyper-V | Click on
the individual hyper-V server | Monitoring and Diagnostics.
A VMware environment Locations | Open a location | Virtualization Hosts | Click on the
VMware node | Select Monitoring and Diagnostics.
A specific VMware datacenter Location | Select a location | Virtualization Hosts| VMware | Click on
the individual VMware datacenter | Select Monitoring and
Diagnostics.
vWorkspace 8.6.3
124
Table 71. Accessing specific diagnostic information from the vWorkspace Management Console
Access Monitoring and Diagnostics
Navigation
information for...
A specific Web Access server Web Access | Right click on the website | Select Monitoring and
Diagnostics.
The print server for a specific User Environment Management| Printers | Click on a printer | Select
printer Monitoring and Diagnostics.
A managed application Managed Applications | Right click on the managed application in the
right pane | Select Monitoring and Diagnostics.
To modify the Monitoring and Diagnostics URL or credentials

The Monitoring and Diagnostics URL and credentials are created upon installation of vWorkspace. If you need to
modify the URL or credentials, use the following steps:
1 Right click the Monitoring and Diagnostics node and select Properties.
2 Update the URL and your credentials for the Monitoring and Diagnostics console as necessary.
3 Click OK.
vWorkspace 8.6.3
125
4
Virtualization Platform Integration
• Virtualization platform integration overview

• Microsoft Hyper-V integration
• Microsoft SCVMM integration
• VMware vCenter server integration
• Parallels Virtuozzo Containers integration
• RD Session Host integration
• Importing existing computers into a group
Virtualization platform integration

overview
Management Servers extend management functionality within the environment, as the vWorkspace Connection
Broker passes commands and queries to them to be processed.
The following are categories of vWorkspace Management Servers.
• Virtualization management servers
• Defining management servers
Virtualization management servers

A Virtualization Management Server is a Microsoft Windows-based computer system. You can use it to centrally
manage physical servers that are enabled with computer virtualization technology. You can also manage virtual
computers the servers are hosting.
vWorkspace Connection Brokers integrate with virtualization management servers through APIs provided by the
vendors. All the necessary prerequisites to communicate with a virtualization management server are installed
with vWorkspace.
vWorkspace supports the following virtualization management servers: VMware vCenter Server, Microsoft
System Center Virtual computer Manager, and Parallels Virtuozzo Containers (master nodes).
Defining management servers

Connections to management servers are configured using the Management Servers window.
• To define the initial management serverTo define the initial management serverTo define the initial
management server
• To add Virtualization Server connections
• To add Network Storage servers
To define the initial management server

If virtualization servers have not been defined, the Virtualization Server Wizard is displayed, which allows you
to add them. After a management server has been added, the Management Servers window is opened when the
Management Server option is selected.
vWorkspace 8.6.3
127
The following information is included on the Management Servers window.
Table 72. Management Servers fields
New Opens the Virtualization Server wizard so that new

virtualization server connections can be added.
Properties Allows the vWorkspace administrator to make changes to
the configuration of the selected virtualization server.
Delete Deletes the virtualization server’s record from the
database.
Test Connection Allows you to test the connection to the virtualization
server.
Refresh Updates the display list of virtualization server
connection entries.
Virtualization Servers Options
Name Alias name of the management server.
URL/Server Name Uniform Resource Locator (URL) path or server name
used by the Connection Broker to communicate with the
virtualization server.
Type Type of the management server is displayed in this
column. The types are:
• Microsoft SCVMM
To add Virtualization Server connections

The Virtualization Server wizard is used to add new entries to the virtualization server connections.
2 Right-click on the Locations node or a defined location, and select Management Servers.
If you have not previously added virtualization servers, the Virtualization Server wizard is displayed.
If you have previously added virtualization servers, click on the green plus sign (+), to display the
Virtualization Server wizard.
3 On the Virtualization Server Wizard Welcome window, click Next.
4 On the Name and System Type window, specify the settings and then click Next.
Table 73. Name and System Type fields
Name Enter the friendly name that is used when

referring to the virtualization server.
System type Select one of the virtualization server types.
vWorkspace 8.6.3
128
5 On the Server & Credentials window, specify the settings, and then click Next.
Table 74. Server & Credentials fields
Server URL or SCVMM Enter the URL path to the virtualization

Server Name or IP server.
address For Microsoft SCVMM, enter the SCVMM
server name or IP address.
For VMware vCenter Server, the URL must
be in the format:
• https://servername or IP
Address/sdk
For Parallels Virtuozzo, the URL must be in
the format:
• https://servername:port
User name Enter the name of a user account that has
the required access permissions to the
target server specified in the Server URL
field.
For a Windows domain account, use:
DomainName\UserName
Click the ellipsis to the right of this field,
and the Select User window is displayed.
Password Enter the case-sensitive password.
The check mark to the right of the field is
used to verify the entered credentials, if the
computer is part of the domain.
Test connection Click to test the server connection.
6 On the Other Settings window, specify the settings, and then click Finish.
The options on the Other Settings window are based upon the supported features of the System Type
selected, so some options may be unavailable.
Shutdown Guest OS Specify the number of guest operation

system shutdown commands that can be
sent to the virtualization server from the
Connection Broker at one time.
Restart Guest OS Specify the number of guest operation
system restart commands that can be sent
to the virtualization server from the
Update PNTools Specify the number of Update PNTools
commands that can be sent to the
virtualization server from the Connection
Broker at one time.
Initialize Specify the number of Initialize Computer
commands that can be sent to the
Broker at one time.
Power On Specify the number of virtual computer
power on commands that can be sent to the
Broker at one time.
vWorkspace 8.6.3
129
Power Off Specify the number of virtual computer
power off commands that can be sent to
the virtualization server from the
Suspend Specify the number of guest operation
system suspend commands that can be sent
Resume Specify the number of guest operation
system resume commands that can be sent
Reset Specify the number of guest operation
system reset commands that can be sent to
the virtualization server from the
Delete Specify the number of delete virtual
computer operations that can be sent to the
Broker at one time.
Clone Specify the number of clone virtual
computer operations that can be sent to the
Broker at one time.
NOTE: This option does not apply to
Microsoft Hyper-V.
Connection timeout Specify the amount of time that the
Connection Broker waits for a response from
the virtualization server.
Default option is 30 Seconds.
For medium to large production
environments where the virtualization
server is busy, you may need to set the
Connection Timeout to two or three
minutes.
NOTE: A Connection Timeout error does not
necessarily mean that the task requested by
the Connection Broker has failed. It may be
that the virtualization server is too busy to
report the successful completion of the
operation in a timely manner.
7 Click Finish to complete the wizard.
To add Network Storage servers

2 Right-click on the Locations node or a specific location, and then select Management Servers.
3 Click Network Storage Servers, and then click New.
4 On the Welcome window of the Network Storage Server Wizard, click Next.
5 On the Name window, enter a name for the new network storage server, and then click Next.
6 On the Server window, specify the System Type of the network storage server, and then enter the IP
address for the network storage server. Then click Next.
vWorkspace 8.6.3
130
7 On the Credentials window, enter the credentials for this network storage server, and then click Finish.
The Use Default Credentials option can be used if you have specified credentials on the Default
Credentials window.
Virtualization hosts
After a virtualization management server is defined, Virtualization Hosts must be added to support cloning
operations and the creation of computer groups. Virtualization hosts are the server platforms in which virtual
computers reside. The following types of hosts can be added:
• Defining Microsoft Hyper-V hosts
• Defining SCVMM, VMware, or Parallels slave nodes
• Defining Parallels independent hosts
For Hyper-V hosts and Parallels Virtuozzo independent nodes, vWorkspace communicates directly with the
virtualization host. Therefore, no additional management servers need to be defined when using these types of
hosts.
Defining Microsoft Hyper-V hosts

When Hyper-V hosts are added, the initialization process is started and the Data Collector and Hyper-V Catalyst
components are installed. If the Hyper-V host is removed from the Management Console, the Data Collector and
Hyper-V Catalyst components are automatically uninstalled.
To define a Hyper-V host

1 Expand the Locations node in the vWorkspace Management Console.
2 Expand the location to which you want to add the virtualization host.
3 Expand the Virtualization Hosts node, right-click on Hyper-V and select Add host.
4 On the Hyper-V Host window, click Next.
5 On the Root Node Credentials window, specify the credentials for the Hyper-V root node, then click
Next.
6 On the Hyper-V Host window, enter a name for the Hyper-V host that properly resolves to an IP address.
Click the ellipsis to browse for a host. Then click Next.
7 On the Credentials window, do one of the following:
• Click Next to use default credentials.
• Select Override parent credentials to use separate credentials. Add the user name and password
for the new credentials, then click Next.
8 On the Connection Load Balancing window, do one of the following:
• Click Next to accept the values inherited from the Hyper-V node (parent node).
• Select Override parent settings, select one of the following options, and then click Next.
Use the default load balancing rule (click View to see the default load balancing rule).
Specify a custom load balancing rule.
Three load balancing rules are included with the vWorkspace installation. For more information on the
rules or how to create them see Load balancing.
9 On the Provisioning Load Balancing window, do one of the following.
• Click Next to accept the values inherited from the Hyper-V node (parent node).
vWorkspace 8.6.3
131
• Select Override parent settings, select one of the following options, and then click Next.
• Use the default load balancing rule.
• Click View to see the default load balancing rule.
• Specify a custom load balancing rule.
Three load balancing rules are included with the vWorkspace installation. For more
information on the rules or how to create them see Load balancing.
10 On the Other Settings window, complete the settings and then click Finish.
Performing too many operations at once causes the virtualization host to perform poorly. The default
value for all concurrent operations is five. For Hyper-V hosts, the settings can be inherited from the
parent Hyper-V node.
Enabling Server Message Block (SMB) Support

If you want to use shared network storage for your virtual machines, you can configure vWorkspace to use
particular UNC shares. This is supported only for 2012 and 2012R2 Hyper-V hosts.
Setting up Universal Naming Convention (UNC) support for Hyper-V

If you want to use UNC support for shared storage, use the following procedure to set it up.
1 From the Management Console, ensure that the Hyper-V host is initialized.
2 From the vWorkspace Connection Broker, copy the script file to the target host from the following
location on the system drive:
\Program Files (x86)\Quest Software\vWorkspace\HyperV Catalyst\SetHvAdministratorCredentials.ps1
3 Set up necessary credentials to access UNC shares. These credentials must be in the credential store for
the local system account and not the account of the active user (the data collector service runs as a
local system).
a Download psexec.exe from live.sysinterals.com.
b Open the administrator’s Powershell prompt and run psexec.exe ‐i ‐s powershell.exe.

An interactive Powershell prompt runs under the system account.
4 From the system’s Powershell prompt, run the script file on the Hyper-V host.
5 Enter your user name and password when prompted.
The new credentials are added to the store.
6 From the following location in the registry editor, create a directory for Shares
HKLM\Software\Wow6432Node\Provision Networks\Provision-IT\Shares
7 In the Shares directory, set up the shares you want to use.
Name: Name of the share.
Data: Full path to share.
8 From the vWorkspace Management console | Hyper-V host Properties window, refresh the volumes. Then
specify the template volume and placement volumes for the host (see To set up the Hyper-V host
properties on page 136).
Defining SCVMM, VMware, or Parallels slave nodes

Microsoft SCVMM host groups or clusters must be added to the SCVMM node to enable the creation of SCVMM
type computer groups. vWorkspace leverages features of SCVMM when hosting virtual desktops on Hyper-V to
enable technologies such as clustering for Fault Tolerance and Live Migration.
vWorkspace 8.6.3
132
VMware Datacenters are groupings of ESX or ESXi hosts and must be imported as objects in the vWorkspace
database, just as SCVMM Host groups or Hyper-V hosts, before creating VMware type computer groups.
Parallels Virtuozzo slave nodes must be added to enable the creation of Parallels type computer groups.
To define SCVMM, VMware or Parallels slave nodes system types

1 Expand the Locations node in the vWorkspace Management Console.
3 Expand the Virtualization Hosts node, and right-click on one of the following:
• SCVMM, select Add host groups or clusters.
• VMware, select Add datacenters.
• Parallels, select Add a Virtuozzo slave node.
4 On the Welcome window, click Next.
5 Do one of the following on the wizard window:
• SCVMM Server window. If an SCVMM server has already been added as a virtualization
management server, select the appropriate SCVMM server, and then click Next. Click Edit
Virtualization Servers and complete the wizard if an SCVMM virtualization management server
needs to be added.
• VMware vCenter Server window. If a VMware vCenter server has already been added as a
virtualization management server, select the appropriate vCenter server, and then click Next.
Click Edit Virtualization Servers and complete the wizard if a VMware virtualization
management server needs to be added.
• Parallels Master Node window. If a Parallels Master Node has already been added as a
virtualization management server, select the appropriate Master node, and then click Next. Click
Edit Virtualization Servers and complete the wizard if a Virtuozzo Master Node virtualization
management server needs to be added.
6 Do one of the following based on the system type selected:
• SCVMM. Expand the SCVMM server and select a host group or cluster from the list. Click Finish.
• VMware. Select a datacenter from the list, and then click Finish.
• Parallels. Select a slave node from the list, and then click Finish.
Defining Parallels independent hosts

Parallels Virtuozzo independent hosts must be added to enable the creation of Parallels type computer groups.
To define Parallels independent hosts

1 From the Management Console, expand the Locations node.
3 Expand the Virtualization Hosts node, right-click on Parallels, and select Add independent Virtuozzo
node.
4 On the Welcome window, click Next.
5 On the Name and System Type window, enter a descriptive name for the host, and then click Next. The
Parallels Virtuozzo system type is selected by default.
6 On the Server & Credentials window, enter the name and the IP Address of the Virtuozzo independent
node, and then enter a Virtuozzo administrative user account name and password. Click Next.
7 On the Other Settings window, complete the settings and then click Finish.
vWorkspace 8.6.3
133
Too many operations at once causes the virtualization host to perform poorly. The default value for all
concurrent operations is 5.
Microsoft Hyper-V integration

vWorkspace communicates directly with Microsoft Hyper-V hypervisors to manage, provision, and optimize
virtual computers hosted on Hyper-V. To do this, vWorkspace includes a direct integration with the Hyper-V
platform, as well as a set of unique tools called Hyper-V Catalyst Components.
The Connection Broker communicates directly with Hyper-V hypervisors for provisioning, brokering, load
balancing, and other management tasks. The integration with Hyper-V, along with Hyper-V Catalyst Components
and other management options, provide support for Desktop Clouds. The Hyper-V integrations are:
• vWorkspace data collector
• Hyper-V catalyst components
vWorkspace data collector

The vWorkspace Data Collector communicates heartbeat and performance metrics to the Connection Broker.
The Data Collector is pushed from the Management Console to Hyper-V hosts after they are added to the
Virtualization Hosts node. This process is called initialization, which also installs the Hyper-V Catalyst
components.
Hyper-V catalyst components

Hyper-V catalyst components increase the scalability and performance of virtual computers on Hyper-V Hosts.
Hyper-V catalyst components consist of two components: HyperCache and HyperDeploy.
About HyperCache
HyperCache provides read Input/Output Operations Per Second (IOPS) savings and improves virtual desktop
performance through selective RAM caching of parent VHDs. This is achieved through the following:
• Reads requests to the parent VHD are directed to the parent VHD cache.
• Requests data that is not in cache is obtained from disk and then copied into the parent VHD cache.
• Provides a faster virtual desktop experience as child virtual machines requesting the same data find it in
the parent VHD cache.
• Requests are processed until the parent VHD cache is full. The default size is 800 MB, but can be changed
through the Hyper-V virtualization host property.
To access the HyperCache report

The HyperCache report details statistics, such as data cached and read requests cached. Use the following
procedure to access the HyperCache Report:
1 From the vWorkspace Management Console, expand Locations and then the Location of the Hyper-V
group.
2 Expand Virtualization Hosts.
3 Expand Hyper-V Hosts.
4 Select the Hyper-V group, and then click on the HyperCache tab in the lower right-side pane.
5 Click HyperCache Report.
vWorkspace 8.6.3
134
HyperCache usage considerations with Clustered Shared Volumes (CSV) on Windows Server 2008/R2
CSV must be in redirected access mode and must remain so while HyperCache is caching the MasterVHD. If the
CSV is placed in direct access mode, the Hyper-V host will continue to function normally, but the VDI virtual
machines using the HyperCached MasterVHD may terminate abnormally.
Both MasterVHD/Template VHD and differencing VHDs can be placed on CSV.
HyperCache usage considerations with Clustered Shared Volumes (CSV) on Windows Server 2012.
HyperCache can be used in Windows Server 2012 with MasterVHDs on CSV. The CSV can be in any operational
mode; direct access mode or redirected access mode. CSV can transition from one access mode to another and
HyperCache will continue to work normally.
With CSV, one of the nodes is designated as the CSV owner node. While HyperCache is operational, CSV
ownership can transition from one node to another, and HyperCache will continue to work normally.
Both MasterVHD/Template VHD and differencing VHDs can be placed on CSV.
About HyperDeploy
HyperDeploy manages parent VHD deployment to relevant Hyper-V hosts and enables instant cloning of Hyper-V
virtual computers. HyperDeploy uses the following techniques to minimize the time used to deploy a virtual
computer.
• Smart copying that only copies to the Hyper-V hosts the parent VHD data that is needed.
• Instant provisioning allows the child VHDs to be cloned while the parent VHD is still being copied to the
Hyper-V host.
• Copy status is displayed on the Parent VHDs tab to allow for monitoring of the progress and completion.
HyperDeploy is a core component and requires no configuration.
HyperDeploy usage considerations with Clustered Shared Volumes (CSV) on Windows Server 2008/R2
CSV must be in Redirected Access mode and must remain so while HyperDeploy is deploying and copying the
MasterVHD. After HyperDeploy is done copying, the CSV can be placed into Direct Access Mode, but HyperCache
cannot operate with CSV in Direct Access Mode.
Both Master VHD/Template VHD and differencing VHDs can be placed on CSV.
HyperDeploy usage considerations with Clustered Shared Volumes (CSV) on Windows Server 2012
HyperDeploy can be used in Windows Server 2012 with Master VHDs on CSV and the CSV can be in any
operational mode, Direct Access mode or Redirected Access mode. CSV can transition from one access mode to
another and HyperDeploy will continue to work normally.
With CSV, one of the nodes is designated as the CSV owner node. While HyperDeploy is operational, CSV
ownership can transition from one node to another, and HyperDeploy will continue to work normally.
Both Master VHD/Template VHD and differencing VHDs can be placed on CSV.
Accessing the Hyper-V host context menu

To access the context menu of a Hyper-V host
1 From the vWorkspace Management Console, expand Locations.
2 Select and expand the location node where the Hyper-V host resides.
3 Expand the Virtualization Hosts node.
4 Expand the Hyper-V node, and then right-click on the appropriate Hyper-V host. The following options
are available:
• Disable provisioning. Disables provisioning of virtual computers to this host. Also referred to as
removing the host from the cloud.
vWorkspace 8.6.3
135
• Remove. Removes the host from the Management Console that causes the Data Collector and
Hyper-V Catalyst components to uninstall.
• vWorkspace Monitoring and Diagnostics. Displays diagnostic information about the Hyper-V host.
• Properties. Controls settings for the Hyper-V host.
• Initialize. Checks and, if needed, updates the Data Collector and Hyper-V Catalyst components
on the Hyper-V Host.
Hyper-V host properties

This section describes the Volumes and Parent VHD settings of a Hyper-V Host. For information on the
Credentials, Connection Load Balancing, Provisioning Load Balancing, and Other Settings refer to Virtualization
hosts on page 131.
To set up the Hyper-V host properties

1 Select Properties from the context menu of a Hyper-V host.
2 Define the Volume and Parent VHD (Virtual Hard Disk) settings, described in the following table.
Table 76. Volume and Parent VHD fields
Hyper-V Host Property Description

Volume Displays the local volumes of the Hyper-V host and
allows for the specification of placement volumes.
The settings are:
Volume. Displays the local volumes of the Hyper-V
host.
Template. Used to store parent VHDs. There can be
only one template volume per host.
Placement. Used to store virtual computers.
Multiple volumes can be selected and virtual
computers are distributed across them based on the
available space of the volume.
Priority. Options are Normal, Medium, High, or
Maximum.
Free Space. Amount of space available on the
specified volume.
Capacity. Total capacity, in megabytes, of the
volume.
Parent VHD settings Parent VHD settings control caching of Parent VHDs.
Use the global default settings. Select to use the
default settings. To review the current settings,
click View.
Disable caching for new parent VHDs. Select to
prevent caching on newly created parent VHDs.
To disable caching on an individual basis, click
Caching for a Parent VHD and select Disabled from
the drop-down box.
To set the cache size for each parent VHD, click
cache size number for a parent VHD, and then click
the ellipsis to set a new cache size.
3 Click OK.
vWorkspace 8.6.3
136
Performing desktop cloud maintenance
The Desktop Cloud Maintenance settings are used to maintain your desktop clouds.
To perform desktop cloud maintenance

1 Right-click on the desktop cloud group, and then select Cloud maintenance.
• Maintenance mode on. When maintenance mode is turned on, auto-size is disabled and new
connections are not accepted. You can maintain templates, clear out VMs, and delete the cloud.
• Maintenance mode off. When you have completed cloud maintenance, select this option to turn
maintenance mode off.
• Drain the desktop cloud(s). Deletes all of the computers in the specified cloud that are not in
use and are not persistently assigned.
3 Click OK.
Adding computers to a Hyper-V computer group

To add computers to a hyper-v computer group
1 From the vWorkspace Management Console, select the Hyper-V computer group. Right-click on the
managed computer group, and select Add Computers.
2 On the Welcome window of the Add Computers Wizard, click Next.
3 On the Number of Computers to Create window, in the Number of computers to create field, enter a
number, and click Next.
4 On the Clone Method window, select the method you want to use when adding computers to the group.,
and click Next.
• Standard. Each virtual machine utilizes a single virtual disk.
• Rapid Provisioning. Choose either the Differencing Disks or Full Disk method.
• Differencing Disks. Utilizes vWorkspace Hypercache and HyperDeploy with differencing
disks to quickly deploy virtual machines, save storage space and minimize disk I/O.
• Full Disk. Utilizes vWorkspace HyperDeploy to quickly deploy a single virtual disk.
NOTE: The Differencing Disks method saves on average 90% IOPS when compared to the Standard or Full
Disk clone methods.
5 On the Template window, select the template that is to be used to create virtual computer clones, and
click Next.
• Update. Checks for newer versions of the existing templates.
• Import. Imports new templates from the Hyper-V hosts. This launches the Import Templates
wizard.
• Remove. Removes the highlighted template from the list.
6 On the Host Options window, select one of the options, and click Next:
• All Hosts. New virtual computers created in the computer group to be distributed across all
Hyper-V virtualization hosts defined for the location.
• Selected Hosts. New virtual computers created in the computer group to be distributed across
selected hosts only.
7 On the Hosts window, select the Hyper-V hosts where the virtual computers are to be distributed, and
click Next.
vWorkspace 8.6.3
137
If All Hosts is selected in the previous window, the option to select a host will be unavailable.
• Click Distribution to set the distribution logic for the clone operation.
• Click Add Hosts to launch the Hyper-V Host Wizard.
8 On the Naming Conventions window, select the method for assigning a computer name to the new
desktop computers in Source, then click Next.
If Specify the base name is selected, do the following:
a Enter the text string in the Base Name field.
b Select a value from the Start values at and Increment values by fields.
c Select Re-use the names of deleted desktops, if appropriate.
If Specify a text file containing names is selected, do the following:
a Enter the path and file name of the text file containing the list of computer names in the Names
File field.
b Enter a text string that is prepended to the beginning of computer names in the Prefix field, if
appropriate.
c Enter a text string that is appended to the end of computer names in the Suffix field, if
appropriate.
9 On the Customize Operating System window, do one of the following, and then click Next:
• To use the operating system customization tools, select Specify operating system
customizations. The computers in this group are powered on after they are created.
• To create a new customization, select a customization from the list, or click New. See Operating
system customizations for more information.
• To not use Microsoft System Preparation tools, select Do not specify operating system
customizations. The desktops in this group are not powered on after they are created.
10 On the Configure Hardware window, set up the Video Adapter, Memory, Network Adapter and High
Availability settings.
a Click the Video Adapter tab, and do one of the following:
• To use the template, select Use template settings.
• To use the standard adapter, select Standard video adapter.
• To use the Microsoft RemoteFX 3D video adapter, select Microsoft RemoteFX 3D video
adapter. Select a value for maximum number of monitors from the Maximum number of
monitors, and select a value for Maximum monitor resolution.
b Click the Memory tab, and do one of the following:
• To use static memory, select Static memory. Select a value for virtual computer memory
from the Virtual computer memory field.
• To use Dynamic memory, select Dynamic memory. Select a value for startup memory from
the Startup memory field, select a value for maximum memory from the Maximum
memory field, and select a value for memory buffer percentage from the Memory buffer
(%) field.
c Click the Memory Priority tab, perform one of the following, and then click Next:
• To allocate dynamic memory resources, select one of the following options: High,
Medium, Low, or Custom. If Custom is selected, select a value for memory priority in the
Custom field.
d Click the Network Adapter tab, do one of the following, and then click Next:
vWorkspace 8.6.3
138
• To use the template settings for the virtual network name, select Use template settings.
To specify a network name select Specify network name, and type the appropriate name in
the Network Name input field.
• To use the virtual LAN identification from the settings of the template, select Use
Template settings under Virtual LAN Identification. Select Disable VLAN ID to disable the
use of VLANS for the cloned virtual computers in this operation.
• To enable a custom virtual LAN identification, select Enable VLAN ID and type the
appropriate VLAN ID number in the VLAN ID field. Supported values 1- 4094.
e Click the High Availability tab. Select this option if you want to create a clustered virtual
machine that can be failed over to a different server in a fail-over cluster.
• the Hyper-V host being used to create the virtual machine must be in a failover cluster.
• The virtual hard disk (VHD) for the clustered virtual machine must be on a clustered disk.
NOTE: To provision to a cluster for failover, the target template and placement volumes must be
on Cluster Shared Volumes (CSVs). FailOverClustering Powershell cmdlets must be installed on the
system. Any changes to Hyper-V volumes on a host in a cluster will be applied to all hosts in the
cluster.
NOTE: To use Microsoft RemoterFX vGPU and dynamic memory, your Hyper-V environment must
meet specific requirements. For more information about these requirements, see your Hyper-V
documentation.
11 On the Options window, select either Now or At a specific time, and enter a date and time. Then click
Next.
12 On the Finish window, review and confirm the information, and do one of the following:
Red text is displayed to remind administrators not to create more virtual computers than their
infrastructure is designed to support.
Hyper-V 2012 Memory Management Update


The Hyper-V role in Windows 2012 has an improved Dynamic memory feature that adds a property called
Minimum Memory.This allows you to specify a memory value smaller than the Startup Memory value so
that after startup a VM can release unneeded memory back to the host and allow the host to run more
VMs.This property is not configurable via the vWorkspace console, however in 8.6.2, we've provided the
ability to control this new property on a given HyperV host.

To control Minimum Memory for all new VMs, add the following registry value to all Hyper-V hosts
managed by vWorkspace.
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Provision Networks\Common
HyperV-VMMinMemoryMB : DWORD
If the value doesn't exist, the system behaves like it did previously, setting the minimum memory to be
equal to the startup memory.Note the following:
• The value is specified in MB (megabytes).
• Hyper-V will not accept a minimum memory value less than 32, so vW will ensure minimum
memory value is no less than 32 MB.
• Hyper-V will not accept a minimum memory value greater than the startup memory, so vW
ensures the minimum memory is not larger than startup memory.
• Hyper-V will not accept a minimum memory value that is not divisible by 2, so vW ensures the
minimum memory is divisible by two.
vWorkspace 8.6.3
139
Microsoft SCVMM integration
vWorkspace is integrated with Microsoft System Center Virtual computer Manager (SCVMM) to provide
management functionality to Hyper-V virtual computers. The following Microsoft SCVMM integrated features are
available in vWorkspace:
• Import Host Groups from SCVMM.
• Manage virtual computer power states.
• Use SCVMM Intelligent Placement to automate desktop and server provisioning using templates.
• Customize guest Microsoft Windows operating system.
• Distribute managed desktops across multiple storage locations.
• Import existing computers from SCVMM to an existing computer group.
• Managed computers that are members of SCVMM enabled Host Groups are considered to be power
managed computers. This means that the power state can be changed, either automatically by the
Connection Broker or manually by an administrator, using the vWorkspace Management Console.
Connecting to Microsoft SCVMM

The vWorkspace Connection Broker needs to communicate with Microsoft SCVMM before computers running as
virtual computers can be managed using vWorkspace. The following conditions must be met before this
communication occurs.
• Communication parameters for each Microsoft SCVMM server must be added to the vWorkspace
database. See To add Virtualization Server connections for instructions.
TIP: The administrator must have SVMM Administrator credentials to configure a
Microsoft SCVMM server.
• vWorkspace Broker Helper Service needs to be installed on the Microsoft SCVMM server.
Microsoft differencing disks

Microsoft differencing disks are virtual hard disks that can be used to isolate changes to a virtual hard disk or
guest operating systems by storing them in a separate file. The virtual hard disk is referred to as the parent
disk, and the differencing disk is the child disk.
You can also reprovision the clone, which enables administrators to change a virtual computer to a clone of a
new snapshot after the parent has been updated or patched.
The Add Computers wizard in the Management Console can be used to create, add, and manage Microsoft
differencing disks computers.
Reprovisioning SCVMM computers

The Reprovision Computers option allows for SCVMM clones to be reprovisioned based upon administrator
settings.
To reprovision SCVMM computers

1 Access the Reprovision Computers option from one of the following ways:
• Right-click on the SCVMM desktop group.
• Select computers from the information pane, and then select Reprovision Computers from the
Action menu.
vWorkspace 8.6.3
140
2 In the Automated Task Wizard, name the new task, then select Reprovision from the Task list. Set the
task parameters in the Task Parameters window, then set the schedule and finish. Apply the task in the
Automated Task Wizard. For more information, see To schedule tasks using the Automated Task Wizard.
3 When the Reprovision Computers option is selected, the Reprovision Computer window opens. The
options on this window allow you to set the action to be performed by clone type. You can also select for
reprovisioning to occur once users have logged off.
The Clone Types, which represent the type of clones for virtual computers of the selected desktop
group, are:
• Standard Clones
• Differencing Disks Clones
The Reprovisioning Using options are:
• Existing Parent VHD. This option reprovisions the computer using the stated virtual hard
disk.
• New Parent VHD. This option reprovisions the computer using a different virtual hard disk
than the one used to create the clone.
• Do Not Reprovision. This option does not reprovision the computer.
Adding computers to an SCVMM computer group

For SCVMM type computer groups, there are two different clone methods that can be used:
• Standard. Using this method, each virtual computer becomes a complete, independent copy of the
original template.
• Rapid Provisioning. This method uses differencing disks to create virtual computers with minimal
overhead and reduced storage space.
To add computers using the standard clone method

1 Start the Add Computers tool by doing one of the following:
• On the Finish window of the Computer Group wizard, select the Create new desktops from a
master template.
• From the vWorkspace Management Console, select the computer group. Right-click on the
managed computer group and select Add Computers.
3 On the Number of Computers to Create window, Enter the number of computers to create field, enter
a number and then click Next.
TIP: If you previously provisioned a computer group, and want to quickly create
computers using those settings, enter the number of computers, and then click
the Create Now button.
4 On the Clone Method window, select Standard as the clone method that is to be used when adding
computers to this group, and then click Next.
5 On the Host Groups & Clusters window, select a Microsoft SCVMM server and the host group or cluster, as
appropriate. Click Next.
6 On the Template window, select a template from the list, and then click Next. If there are no templates
listed, or to update the list, click Import.
desktop computers.
a In the Base Name field, enter the text string.
vWorkspace 8.6.3
141
b From the Start values at and Increment values by fields, select a value.
a In the Names File field, enter the path and file name of the text file containing the list of
computer names.
b In the Prefix field, enter a text string that is prepended to the beginning of computer names.
c In the Suffix field, enter a text string that is appended to the end of computer names.
8 Click Next.
• Select a customization from the list, or click New to create a new customization. See Operating
10 On the Configure Hardware window:
monitors field and select a value for Maximum monitor resolution from the Maximum
monitor resolution field.
b Click the Memory Priority tab, perform one of the following, and then click Next:
• To allocate dynamic memory resources, select one of the High, Medium, Low, or Custom
buttons. If Custom is selected, select a value for memory priority in the Custom field.
c Click the Memory tab, and do one of the following. Click Next when completed.
(%) field.
d Click the Memory Priority tab, perform one of the following, and then click Next:
Custom field.
e Click the Network Adapter tab, do one of the following, and then click Next:
vWorkspace 8.6.3
142
• To use the VLAN ID from the settings of the template, select Use Template settings under
Virtual LAN Identification. Select Disable VLAN ID to disable the use of VLANS for the
cloned virtual computers in this operation.
• To enable a custom VLAN ID, select Enable VLAN ID and type the appropriate VLAN ID
number in the VLAN ID field. Supported values 1- 4094.
11 On the Options window, select either Now or At a specific time (and enter a date and time), and then
click Next.
To add computers using Rapid Provisioning Clone method

• On the Finish window of the Computer Group wizard, select the Create new desktops from a
master template.
3 On the Number of Computers to Create window, Enter the number of computers to create field, enter
a number and then click Next.
4 On the Clone Method window, select Rapid Provisioning as the clone method that is to be used when
adding computers to this group, select Differencing Disks or Full Disk, and click Next.
• Differencing Disks utilizes vWorkspace HyperCache and HyperDeploy with differencing disks to
quickly deploy virtual machines, save storage space and minimize disk I/O.
• Full Disk utilizes vWorkspace HyperDeploy to quickly deploy a single virtual disk.
5 On the Parent Virtual Hard Disk window, click New to create a new parent virtual hard disk.
6 The Parent Virtual Hard Disk Wizard opens. Click Next on the Welcome window, and enter the following
criteria:
a Select the SCVMM server where the template that is to be used to create the parent virtual hard
disk resides. Click Next.
b Select the template that is to be used for the parent virtual hard disk. You may need to click
Import.
c Click Next.
d Select the host group or cluster that is to be used for the parent virtual hard disk, and then click
Next.
e Select the volume on to which the parent virtual hard disk file is to be stored. Click Next.
f Enter a description for the parent virtual hard disk. This is an optional step.
g Click Finish. You are returned to the Add Computers wizard.
7 Select the volume or volumes on to which the computers should be created. You may need to click
Import to refresh the list. Click Next.
desktop computers.
vWorkspace 8.6.3
143
a Enter the text string in the Base Name field.
c Select Re-use the names of deleted desktops.
a Enter the path and file name of the text file containing the list of computer names in the Names
File field.
b In the Prefix field, enter a text string that is prepended to the beginning of computer names.
c In the Suffix field, enter a text string that is appended to the end of computer names.
9 Click Next.
• To create a new customization, click New, or select a customization from the list. See Operating
11 On the Configure Hardware window:
monitors field and select a value for Maximum monitor resolution from the Maximum
monitor resolution field.
b Click the Memory tab, and do one of the following:
(%) field.
c Click the Memory Priority tab, perform one of the following, and then click Next:
Custom field.
d Click the Network Adapter tab, do one of the following, and then click Next:
• To use the VLAN ID from the settings of the template, select Use Template settings under
Virtual LAN Identification. Select Disable VLAN ID to disable the use of VLANS for the
cloned virtual computers in this operation.
• To enable a custom VLAN ID, select Enable VLAN ID and type the appropriate VLAN ID
number in the VLAN ID field. Supported values 1- 4094.
vWorkspace 8.6.3
144
click Next.
Video adapter and static/dynamic memory

Microsoft SCVMM virtual computers can be reconfigured for Microsoft RemoteFX or regular RDP (using video
adapter) and static or dynamic memory settings from the vWorkspace Management Console.
To reconfigure computers
1 Navigate to the desktop that is to be configured.
1 Highlight the desktop, right-click and select Reconfigure Computers.
2 On the Video Adapter tab, do the following:
a Enable Reconfigure Video adapter.
b Select either the Standard video adapter or the Microsoft Remote FX3D video adapter option.
If you selected Microsoft RemoteFX 3D video adapter, you must also set a Maximum number of monitors
and a Maximum monitor resolution.
3 On the Reconfigure Computers window, Memory tab, do the following:
• Enable Reconfigure memory.
• Select one of the following:
Static memory. If you selected this option, set a value for the Virtual computer memory.
Dynamic memory. If you selected this option, set values for Startup memory, Maximum memory, and
Memory buffer (%).
4 On the Reconfigure Computers window, Memory Priority tab, do the following:
a Enable Reconfigure memory priority.
b Select either High, Medium, Low, or Custom values to further define memory priority.
5 On the Network Adapter tab, do one of the following, and then click OK.
• Select Reconfigure networking.
• Enter a name in the Network Name field.
• Select Disable VLAN ID to disable the use of VLAN for the cloned virtual computers in this
operation.
To enable a custom VLAN ID, select Enable VLAN ID and type the appropriate VLAN ID number in the
VLAN ID field. Supported values 1- 4094.
Delete missing computers from an SCVMM database

SCVMM automatically imports computers on any host being managed by SCVMM. If vWorkspace is also using the
host with direct Hyper-V integration with computer groups in Desktop Cloud mode, the SCVMM database can be
filled with computers with a state of Missing.
vWorkspace 8.6.3
145
Administrators can add the registry entry so that computers in a missing state can be deleted. All missing
computers are deleted regardless of the computer’s host, either Hyper-V or SCVMM.
If you want missing computers to be deleted, add the following registry entry on the computer that runs the
Broker Helper Service:
HKLM\Software\Provision Networks\BrokerHelper
RemoveMissingVMs
REG_DWORD 0=off(default) 1=on
The broker helper service checks for missing records every three minutes, and removes any that are found. The
SCVMM console must be re-started to refresh the list of computers.
Microsoft Azure integration

This feature provides the ability to power manage virtual machines running in Azure.
Prerequisites
• vWorkspace must be running on Azure virtual machines.
• The vWorkspace connection broker must have Azure PowerShell cmdlets 0.8.6 or later installed.
• The vWorkspace connection broker must be set up using pnazuresetup.exe to specify the Azure account,
subscription and service to use when communicating with Azure (see Using PNAZURESETUP.exe).
• The Azure account used must be an Azure organizational account, not an Azure personal account.
• For a virtual machine to be recognized as an Azure virtual machine, the Azure agent must be running on
the virtual machine. This is an option available during the creation of virtual machine from a gallery
image.
• All virtual machines that are to be managed must exist under the same cloud service.
Using PNAZURESETUP.exe
To set up vWorkspace to communicate with Azure
1 Run pnazuresetup.exe on a connection broker. This is located on the connection broker in the following
folder:
C:\Windows\SysWOW64
2 When you run the program, you are prompted to enter your Azure account. The specified account is
checked to ensure that it is an Azure organizational account. For more information on creating and using
an Azure organization account, refer to: 
https://azure.microsoft.com/en-us/documentation/articles/sign-up-organization/
3 After the account is verified, you are prompted to select the subscription you want to use.
4 If there is more than one service associated with the selected subscription, you are prompted to select
the server you want to use.
5 Click Finish to complete the setup. You can then import Azure virtual machines into vWorkspace.
Importing the Azure virtual machine

To import an existing Azure virtual machines into vWorkspace
1 Create a Desktop Group or Session Host Group with the system type of Other/Physical.
2 Add the Azure virtual machine to the new group by specifying the name of the virtual machine. IP
addresses cannot be used to specify an Azure virtual machine in vWorkspace.
vWorkspace 8.6.3
146
3 Initialize vWorkspace. vWorkspace must be successfully initialized before power management is possible.
4 Ensure that the administrative credentials specified for the group are capable of logging into the
administrative share (C$) on the virtual machine.
VMware vCenter server integration

The following VMware integrated features are available in vWorkspace:
• Import Datacenters.
• Manage virtual computer power states.
• Automate desktop and server provisioning using VMware vCenter templates.
• Guest Windows operating system customization.
• Distribute managed computers and servers across multiple resource pools and datastores.
• Configure memory and disk persistence.
Rapid provision VMware computers

The Rapid Provisioning option, in the Add Computers wizard of a computer group, can be used to clone a
VMware virtual computer quickly while reducing storage space. This can be achieved by using VMware Linked
Clones. This option is available on the Add Computers wizard, Clone Method window.
VMware linked clones

VMware linked clones are copies of virtual computers that share virtual disks with a parent virtual computer.
Linked clones are created from a snapshot of the parent computer. However, changes made to the parent
computer or the linked clone computer do not affect each other; the linked clone is a clone of the parent
computer at the time that it is created.
Linked clones need to be able to access their parent computer, and are disabled if they cannot access their
parent computer.
You can reprovision the linked clone. Administrators can redeploy a user’s virtual computer from a new linked
clone snapshot after the parent virtual machine has been updated or patched.
Unlocking a virtual machine

A parent virtual machine might need to be unlocked when a parent virtual machine is removed from the
vWorkspace Management Console for editing.
To unlock the template

1 Right-click it and select Unlock VM.
2 You can complete the unlock process two different ways; by using the Add Computers wizard, or through
the computer Reprovision settings.
• Add Computer Wizard. Right-click on the desktop group for the computer, and then select Add
Computers. On the Welcome window, click Next, and then select Parent Virtual computer. Right-click
on the parent virtual computer and select Unlock VM.
• Reprovision settings. Select the computer from the vWorkspace Management Console. Right-click and
select the Reprovision option. On the Reprovision Computers window, select New Snapshot for the
VMware Linked Clones option, and then click the ellipsis. Right-click on the parent virtual computer and
select Unlock VM.
vWorkspace 8.6.3
147
VMware linked clone setup
VMware linked clone desktops can be deployed to any datastore. Performance of provisioned linked clones
might be increased when using a different datastore than the datastore where the parent virtual computer is
hosted. It is important to note that the datastores are not validated from the vCenter servers, therefore
administrators must be sure that each host has access to that shared datastore.
See To add computers using the VMware Linked Clone method for more information on using the Add Computers
wizard to create VMware Linked Clones.
VMware vNetwork distributed switch

In VMware environments, linked clones can be configured to use vNetwork Distributed Switches (vDS). VMware
Linked Clones are configured to use vDS are supported in a vWorkspace environment.
When configuring VMware vCenter, before starting linked clones that will connect to vDS:
• The vDS port group needs to be configured as Ephemeral- no binding, per the VMware Knowledge Base
article, 1021193, before any virtual machines are connected to it.
• The parent virtual machine needs to be configured to connect to a vDS port group.
Refer to VMware product documentation for more information on vDS.
Reprovisioning computers
The vWorkspace Management Console Reprovision Computers option, allows for VMware clones to be
reprovisioned based on administrator settings.
To reprovision VMware clones

1 Right-click on the VMware desktop group and select Reprovision. The Reprovision Computer window
opens.
2 Set the Action that is to be performed by Clone Type.
3 Select Reprovisioning to be completed once users have logged off.
4 The Clone Types, which represent the types of VMware virtual computers for the selected desktop
group, are:
• Standard Clones
• VMware Linked Clones
• Unknown Clone Type
5 The Reprovision Using options are:
• Existing Template. This option reprovisions the computer using the stated template or snapshot.
• New Template. This option reprovisions the computer using a different template or snapshot than
the one used to create the clone.
• Do Not Reprovision. This option does not reprovision the computer.
6 Use the ellipsis button to browse for the appropriate template or snapshot for the specified clone.
TIP: If you are using the reprovision functionality, it is recommended that you install
PNTools onto your VMware templates that are being used for reprovisioning.
7 Click OK.
vWorkspace 8.6.3
148
Disk persistence and memory
VMware virtual computers can be configured for disk persistence and memory from the vWorkspace
Management Console. Disk persistence and memory are configurable for individual computers, as well as
computer groups. There are three virtual disk modes available:
• Persistent
• Independent and Persistent
• Independent and Nonpersistent
To configure disk persistence and memory for an individual computer

Do one of the following:
• Set the options on the Configuration window of the Computer Properties wizard. This window can be
opened by selecting Properties for a computer, or when creating a new computer.
• Highlight the computer group in the navigation pane, and then click on the Summary tab in the
information pane.
Select Actions | Reconfigure.
• Highlight the computer group in the navigation pane, and then click on the Computers tab in the
information pane. Right-click on the computer and select Reconfigure from the context menu.
• Set the Logoff Action properties of the Computer Properties wizard for the computer. The Logoff Action
property, if enabled, resets the computer when a user logs off. See Setting up managed computers for a
location for more information.
To configure disk persistence and memory for a computer group

Do one of the following:
• Right-click on the computer group in the navigation pane, and then select Reconfigure Computers.
• Highlight Desktops, and then select the Groups tab.
Select Actions | Reconfigure Computers.
• Highlight the computer group in the navigation pane and click on the Summary tab in the information
pane.
Select Actions | Reconfigure Computers.
• Set the Logoff Action properties for the computer group. The Logoff Action property, if enabled, resets
the computers in the group when users log off. See Setting up computer groups for a location for more
information.
Upgrading and changing non-persistent disks

If you have set your virtual machine disks to be non-persistent disks, use the following process if you need to
upgrade or make any other changes to them.
To upgrade or make changes to non-persistent disks

1 In the Properties of a virtual computer, open the Configuration section.
2 From the Virtual Disk tab, highlight the intended virtual disk and click Reconfigure.
3 Change the Disk Configuration for the virtual computer to Independent and Persistent.
If the Independent check box is not selected, any changes you make are lost after the next logoff or
reset of the virtual computer.
4 Apply the upgrade or make any other necessary changes.
vWorkspace 8.6.3
149
5 Change the Disk Configuration for the virtual computer back to Independent and Nonpersistent.
Computer groups
Computer groups are containers of desktops that can be managed together. The following computer groups
properties are associated with VMware vCenter Server.
VMware customizations, available from the Managed Computer Group Wizard, enable administrators to specify
items such as where new computers are stored and how they are named. The following customization settings
can be specified for each managed computer group that belongs to a VMware type data center.
Table 77. VMware Customization settings
VMware Customization Setting Description

Template Indicates the name of the virtual computer
template in the vCenter inventory that is used when
adding new managed computers to the group.
Folder Indicates the name of the folder in the vCenter
inventory where newly created managed desktop
computers are located.
Datastore distribution method Specifies how newly created managed virtual
computers are distributed among the available
datastores in vCenter. The options are:
• Equal. The desktops are distributed equally
across the selected datastores.
• Free Space. The desktops are distributed
across the selected datastores proportion to
the available free space on the datastores.
• Weighted. The desktops are distributed
across the selected datastores based on the
percentages specified.
• Manual. The desktops to be created are
specified for each datastore.
Resource pools/datastores Indicates the names of the Resource Pools and
Datastores and the allocation percentages of the
vCenter inventory selected for storage of newly
created managed computers within this group.
Naming conventions Base Name. Indicates the base name that is used
when constructing the Windows computer name
that is assigned to the newly created managed
desktop computers added to the group.
Base Name Start Value. Indicates the starting
numeric value that is added to the base name when
constructing the Windows computer name that is
assigned to the newly created managed desktop
computers added to the group.
Base Name Increment. Indicates the numeric value
by which subsequent Windows computer names are
incremented when new managed desktop
computers are added to the group.
Re-use Names. Indicates whether previously
generated Windows computer names can be reused
if the managed desktop computer has been deleted.
vWorkspace 8.6.3
150
Table 77. VMware Customization settings
VMware Customization Setting Description

Configure memory Specifies the memory configuration used with this
computer group.
Configure disk Specifies how the disk is configured for this
computer group.
Adding VMware computers

When adding VMware type computer groups, there are three different clone methods that can be used:
• Standard. Using this method, each virtual computer becomes a complete, independent copy of the
original template.
• Rapid Provisioning VMware Linked Clone. Using this method, you can create a clone from a snapshot of
a parent virtual machine. Changes to the disks of either the linked clone or the parent do not affect each
other.
To add computers using the Standard Clone method

• On the Finish window of the Computer Group wizard, select Create new desktops from a master
template.
2 Type a number into the Enter the number of computers to create field on the Number of Computers to
Create window, and then click Next.
3 On the Clone method window, select Standard as the clone method, and then click Next.
4 From the list on the Template window, select a template, and click Next. If there are no templates listed
or to update the list, click Import.
5 On the Folder window, select a folder in which the new computers are placed, and click Next. If the list
is empty or to update the list, click Import.
6 On the Resource Pools/Datastores window, select one or more resource pools and datastores. This is
where the virtual computer disk files are to be stored. If the list is empty or to update the list, click
Import.
a To change the distribution method, click the Distribution button on the toolbar above the list of
datastores. Complete the information on the Datastore Distribution Method window as
appropriate.
b Click Next.
7 On the Naming Conventions window select the method for assigning a computer name to the new
desktop computers.
• Enter the text string in the Base Name field.
• Select a value from the Start values at and Increment values by fields.
• Select Re-use the names of deleted computers, if needed.
• In the Names File field, enter the path and file name of the text file containing the list of
computer names.
• In the Prefix field, enter a text string that is prepended to the beginning of computer names, if
appropriate.
vWorkspace 8.6.3
151
• In the Suffix field enter a text string that is appended to the end of computer names, if
appropriate.
8 Click Next.
• To use Microsoft System Preparation tools, select Specify operating system customizations. The
computers in this group are powered on after they are created.
• Select a customization from the list, or click New to create a new customization. See To create
operating system customizations for Windows XP/2003 or To create operating system
customizations for Win7 and 8/Windows Server2008/ Windows Server 2008 R2, and Windows
Server 2012 for more information.
10 On the Configure Hardware window, select the check box to reconfigure the computer’s memory and disk
persistence after the cloning, if appropriate, then do the following:
a Select Reconfigure Memory, and move the slider or enter a number to adjust for the memory
value.
b Select the Virtual Disks tab, select Reconfigure Virtual Disks, and then select First disk only or
All disks. Select the Disk Mode, and set it to one of the following:
• Persistent
click Next.
Red text reminds administrators to not create more virtual computers than their infrastructure is
designed to support.
To add computers using the VMware Linked Clone method

• From a master template on the Finish window of the Computer Group wizard, select Create new
desktops.
• From the vWorkspace Management Console, select the computer group, right-click on the
3 On the Number of Computers to Create window, Enter the number of computers to create field, type a
number, and then click Next.
4 On the Clone method window, select Rapid Provisioning VMware Linked Clone as the clone method,
and then click Next.
5 On the Parent Virtual computer window, select a parent virtual computer or click Import to import the
parent virtual computers.
6 If you selected Import on the Parent Virtual computer window, do the following on the Import/Refresh
Parent Virtual computers wizard.
a Specify the tasks that are to be performed on the Options window of Import/Refresh Parent
Virtual computers, and then click Next.
vWorkspace 8.6.3
152
• Import parent virtual computers.
• Remove orphaned parent virtual computers.
b On the Inventory window, select one or more virtual computers that are to be imported or
updated, and then click Finish.
c On the Parent Virtual computer window, highlight the parent virtual computer that you just
imported, and then click Next.
7 On the Snapshot window, select the appropriate snapshot, and then click Next.
8 On the Folder window, select a folder in which the new computers will be placed, and click Next. If the
list is empty, or to update the list, click Import.
9 On the Resource Pools/Datastores window, select one or more resource pools and datastores. This is
where the virtual computer disk files are to be stored. If the list is empty, or to update the list, click
Import.
You are not limited to using the datastore of the parent virtual computer. Using a different datastore
than the parent virtual computer might increase provisioning performance.
a To change the distribution method, click the Distribution button on the toolbar above the list of
datastores. Complete the information on the Datastore Distribution Method window.
b Click Next.
desktop computers in Source.
a In the Base Name field enter the text string.
c Select Re-use the names of deleted computers, if appropriate.
a In the Names File field, enter the path and file name of the text file containing the list of
computer names.
b In the Prefix field, enter a text string that is prepended to the beginning of computer names, if
appropriate.
c In the Suffix field, enter a text string that is appended to the end of computer names, if
appropriate.
11 Click Next.
• Select a customization from the list, or click New to create a new customization. See To create
operating system customizations for Windows XP/2003 or To create operating system
customizations for Win7 and 8/Windows Server2008/ Windows Server 2008 R2, and Windows
Server 2012 for more information.
13 Select the check box to reconfigure the computer’s memory and disk persistence after the cloning on the
Configure Hardware window, then do the following:
a Select Reconfigure Memory, and move the slider or enter a number to adjust for the memory
value.
b Select the Virtual Disks tab, and select Reconfigure Virtual Disks, and select First disk only or
All disks. Select the Disk Mode, and set it to one of the following:
vWorkspace 8.6.3
153
• Persistent
click Next.
Red text is displayed as a reminder to administrators not to create more virtual computers than their
Parallels Virtuozzo Containers integration

This section describes the range of desktop management and provisioning features offered by vWorkspace for
Parallels Virtuozzo Containers environments.
Parallels Virtuozzo nodes

Parallels Virtuozzo nodes can be imported to the vWorkspace Management Console as either independent hosts
or as part of a group. A Virtuozzo group can contain master and slave nodes that are associated with each other.
However, a Virtuozzo host cannot simultaneously be an independent host and part of a group.
A location can contain both slave nodes and independent nodes.
If you do not have independent nodes a master node must be defined as a management server for the location
to support slave nodes. When a location is added, slave nodes can be imported from any of the virtualization
server master nodes, and are associated with the location.
Virtuozzo independent nodes are added to a location, rather than imported, as is the case with Virtuozzo slave
nodes.
When setting up the Parallels Virtuozzo Containers in the vWorkspace Management Console, once a location has
been defined, the following steps must be completed:
• Associate virtualization hosts, independent nodes and slave nodes, to the location.
Virtuozzo slave nodes. Use this option to import master nodes and select slave nodes that are to be
imported.
Independent Virtuozzo nodes. Use this option to add the independent nodes to the location.
• Computer groups can be added to locations by selecting Desktops from the location in the vWorkspace
Management Console. See Setting up computer groups for a location for more information.
• Add computers to the established computer groups by using the Add Computers Wizard. See the The
Management Console chapter for more information.
CAUTION:Parallels Virtuozzo Containers disable the startup of certain Microsoft Windows
services by default, including ones that are required for vWorkspace.
You need to set the type to Enterprise to prevent the disabling of certain
Windows services. Also refer to the Parallels Virtuozzo knowledge base article,
http://kb.parallels.com/1007, for more information.
To add computers to a computer group

vWorkspace 8.6.3
154
a On the Finish window of the Computer Group wizard, select the Create new desktops from a
master template.
b From the vWorkspace Management Console, select the computer group. Right-click on the
2 On the Welcome to the Add Computers Wizard window, click Next.
3 On the Number of Computers to Create window, Enter the number of computers to create field, type a
number, and then click Next.
4 Select a template from the list on the Template window, and click Next. If there are no templates listed
or to update the list, click Import.
5 Select one or more Virtuozzo network devices from the Nodes/Network Devices window. This is where
the computers should be created. If the list is empty or to update the list, click Import.
a To change the distribution method, click Distribution on the toolbar above the list of datastores.
Complete the information on the Datastore Distribution Method window.
b Click Next.
desktop computers.
a Type the text string in the Base Name field.
a In the Names File field, type the path and file name of the text file containing the list of
computer names.
b In the Prefix field, enter a text string that is prepended to the beginning of computer names, if
appropriate.
c In the Suffix field enter a text string that is appended to the end of computer names, if
appropriate.
7 Click Next.
• Select a customization from the list, or click New to create a new customization.
CAUTION:It is important that you make sure your operating system customization
configuration is accurate and works on a computer that is visible to you. If the
customization information is incorrect, you may have a computer that requires
user input, but you will have no way of connecting to it.
9 On the Options window, select either Now or At a specified time (and enter a date and time), and then
click Next.
vWorkspace 8.6.3
155
Red text is displayed as a reminder to administrators not to create more virtual computers than their
RD Session Host integration

This section describes features offered by vWorkspace to integrate with Microsoft Remote Desktop Services
(RDS) using Microsoft Windows Server 2008 R2.
RDS, formerly Terminal Services, provides users with an entire desktop environment or individual applications
that are running from within a datacenter, but appear to the user as a local application.
The integration between vWorkspace and Microsoft RDS enables the following features:
• Support for publishing applications and desktops using Microsoft RemoteApp Start menu integration in
Microsoft Windows 7 and Microsoft RD Web Access.
• Support for publishing individual applications using Microsoft’s built-in RemoteApp technology for
seamless windows for Microsoft Hyper-V virtual desktops and RD Session Hosts.
• Support for Remote Desktop Gateway for secure Internet access.
• Support for the addition of Microsoft Remote Desktop Connection Brokers to the vWorkspace
Management Console.
• Support in vWorkspace Connector for Windows for connectivity to Microsoft Remote Desktop Connection
Broker and Remote Desktop Gateway.
RemoteApp support
RemoteApp support for Hyper-V virtual desktops and RD Session Host enables the publishing of individual
applications using Microsoft's RemoteApp technology on access devices.
Importing existing computers into a group

You can import existing computers from a virtualization host to an existing computer group.
After computers have been successfully imported, the task Initialize Computer is automatically created. This
process establishes the relationship between the farm and the virtual desktop and must be completed
successfully. See To initialize a computer for more information on this process.
Several controls are available to assist with importing and resynchronizing (Import/Re-sync Computers tool)
desktop computers.
For more information about adding computers, refer to the specific integration components in this chapter.
To import existing computers into a group

2 Select the group on which the import will be performed, and do one of the following:
• Right-click on the computer group and select Import/Re-sync computers.
• Select Import existing desktops from VMware from the Finish window of the Computer Group
wizard, and then click Finish, if you are completing the Computer Group wizard.
3 On the Import/Re-sync computers options, complete the settings shown below, and then click Next.
NOTE: The options presented are dependent upon the type of computers that are being imported.
vWorkspace 8.6.3
156
Table 78. Import/Re-sync computers options
Option Description
Options
Import computers into group If selected, virtual computers that have previously
[managed_desktop_group_ name] been imported into other managed computer
groups in the vWorkspace data center are
prevented from being imported into the current
managed desktop group.
Remove orphaned desktops If selected, managed desktop computers are
removed from the selected managed desktop
group if they no longer exist in the VMware
VirtualCenter inventory.
Inventory
Folders/computers This displays a list of folders and virtual computers
available in the VMware VirtualCenter data center
inventory.
Expand the nodes to view the computers.
Microsoft Hyper-V inventory This control displays a list of folders and virtual
computers available in the Microsoft Hyper-V data
center inventory.
Nodes This displays a list of folders and virtual computers
available in the Parallels Virtuozzo Host inventory.
View:new If selected, displays a list of virtual computers that
have not yet been imported into the managed
desktop group.
View:existing If selected, displays a list of virtual computers that
have previously been imported into the managed
desktop group.
Finish If selected, the chosen virtual computers are
imported into the current managed desktop group
as managed desktop computers.
The To initialize a computer task is automatically
started for each desktop computer successfully
imported.
Cancel If selected, the Import/Re-sync selections are
discarded, and the window is closed.
4 On the Inventory window, do the following:

a Select the appropriate View option (New or Existing).
b Select the computers that are to be imported.
5 Click Finish to start the import.
Monitoring operations
You can monitor an operation by using the middle and bottom panes of the vWorkspace Management Console.
The middle pane on the vWorkspace Management Console displays the overall progress. You can use Refresh to
update the view. The bottom pane on the vWorkspace Management Console uses the Tasks tab to display the
status of the tasks to complete the process, and a Log tab to display more detailed status information.
vWorkspace 8.6.3
157
To cancel a task, select it from the list of tasks and choose Cancel from the Actions menu, or right-click on the
task and select Cancel.
NOTE: <Choose>PNTools is a required component for managed computers in the
vWorkspace infrastructure. If you did not install <Choose>PNTools as part of
the template for the new desktops, it needs to be installed.
Configuring templates with multiple

network interfaces
Virtualization Network IP address range
This configuration option is used with virtual machines that have multiple IP addresses. It can be useful in cases
such as if the virtual machine has multiple network adapters and the user starts a client VPN connection, a USB
video camera adds a network adapter when plugged in. This configuration option allows you to specify the IP
address range vWorkspace should use to communicate with the virtual machine. It should be performed on the
template virtual machine and includes the entire range of IP addresses that can be assigned to virtual machines
created from the template virtual machine.
To configure this option from a registry key on the VDI computer

• On 32-bit computers, navigate to HKLM\Software\Provision Networks\Common
• On 64-bit computers, navigate to HKLM\Software\Wow6432Node\Provision Networks\Common
2 Create the following values:
• IPRange - REG_SZ - Enter one of the IP addresses in the IP address range that should be used
(e.g.10.1.1.1)
• IPMask - REG_SZ - Enter the sub-net mask for the IP address range that should be used (for
example, 255.255.255.0)
This example configuration results in an IP address range of 10.1.1.1-10.1.1.255. If a computer has multiple IP
addresses and one of the IP address is in the configured range, vWorkspace will use that IP address for
management and remote desktop communication. If none of the IP addresses are in the configured IP address
range, the first IP address based on binding order will be used.
vWorkspace 8.6.3
158
5
5
Managing the Virtual Workspace
• Overview of the virtual workspace

• Power management
• Two-factor authentication
• Managed Applications
• vWorkspace interfaces
• User Environment Management
• Secure Access service
• Using Web Access
Overview of the virtual workspace

Virtual workspace is a term used to encompass all of the technologies and platforms that
vWorkspace uses to host the end user's computing environment. The virtual workspace consists
of the applications, data, settings, and operating system subsystems required to provide a
functional desktop computing environment.
With workspace virtualization, you can facilitate the execution of a user's productivity
applications from a data center with the flexibility to host these applications on multiple
platforms.
vWorkspace centralizes the execution of desktop computing, but also to centralizes its
management.
Power management
Managed computer power states can be changed, either automatically by the Connection Broker
or manually by an administrator using the vWorkspace Management Console.
vWorkspace Connection Brokers periodically query their configured virtualization entity servers
for the current power state of managed computers running as virtual computers.
vWorkspace Connection Brokers can also submit commands to change the power state of a
virtual computer. For example, when a user attempts to connect to a managed computer running
as a virtual computer and that virtual computer is powered off, the Connection Broker
automatically sends a command to power on the computer. After the virtual computer is
powered on and the operating system has loaded, the user is then connected to the desktop and
logged on.
vWorkspace 8.6.3
The power states and virtualization entities that can be manipulated with vWorkspace are as
follows.
Table 79. Power states
Power state virtualization Entity

Power On. Powers the virtual • VMware
computer on in the same way as • Microsoft Hyper-V
using the power switch on a
• Microsoft SCVMM
physical computer.
Power off. Powers the virtual • VMware
computer off in the same way as • Microsoft Hyper-V
using the power switch on a
• Microsoft SCVMM
physical computer.
Reset. Powers the virtual • VMware
computer off and then on again in • Microsoft Hyper-V
the same way as using the reset
• Microsoft SCVMM
switch on a physical computer.
Resume. Reawakens a virtual • VMware
computer that has been in a • Microsoft Hyper-V
suspended state.
• Microsoft SCVMM
Suspend. Suspend saves the • VMware
system state and working set of • Microsoft Hyper-V
the virtual computer to disk
• Microsoft SCVMM
before powering off. When
resumed, the computer is
returned to the state it was in
before being suspended. This
option is faster since the
operating system does not have to
go through the complete load and
initialization process.
Shut Down OS. Gracefully shuts • VMware
down the guest operating system • Microsoft Hyper-V
in the same way as using the Shut
• Microsoft SCVMM
Down function in Windows.
• Other/Physical (Blade PCs)
Restart OS. Same as the Restart • VMware
option in Windows. • Microsoft Hyper-V
• Microsoft SCVMM
Log off user. Logs the user off in a • VMware
graceful manner. The user is • Microsoft Hyper-V
prompted to save any unsaved
• Microsoft SCVMM
data.
Reset session. Closes all • VMware
programs that are running and • Microsoft Hyper-V
deletes the session from the
• Microsoft SCVMM
server that is running Remote
Desktop Services. This can be • Other/Physical (Blade PCs)
used if a session is not functioning
correctly, or if the session has
stopped responding.
vWorkspace 8.6.3
Two-factor authentication
Two-factor authentication can be enabled in both the vWorkspace Management Console and Web
Access. You can set up two-factor authentication in any vWorkspace Connector.
The examples in this section use Quest Defender.
To set up two-factor authentication from the Management Console

1 Open the Management Console.
2 Right-click on an environment node and select Farm Properties.
3 On the Farm Properties window, select Two-Factor Authentication.
4 On the Two-Factor Authentication window, complete the following information.
NOTE: If you use Two-Factor Authentication, you cannot use credentials pass-through.
Table 80. Two-Factor Authentication fields
Field Description
Enable RADIUS Enables the RADIUS dialog box.
Server name or IP address Name or IP address of a RADIUS server.
Port Listening port of the RADIUS server.
Secret key Shared password used to communicate with
RADIUS server.
Timeout Enter amount of time that a connection is not
authenticated before a session times out.
Authentication type Select between encrypted (CHAP - Challenge-
Handshake Authentication Protocol) and
unencrypted (PAP - Password Authentication
Protocol).
Password layout Controls the order the AD and OTP passwords
are entered by the user.
One-time password length Informs the Connection Broker of the length of
the OTP.
Require all users to be two-factor Overrides all other vWorkspace policies.
authenticated NOTE: Do not enable this option if the Use
Separate OTP field is selected on the Two
factor authentication window of the Web
Access site properties.
5 Click Apply to save the settings.

6 If two-factor authentication is not required for all users then you can set up Advanced
Targets and assign this to published application. See Advanced targets on page 102.
If you assigned applications to an advanced target requiring the use of two-factor (when
authenticated) these applications are visible to the end user. If a user does not enter
their two-factor credentials, then only those applications assigned to them through
Targets are available to them.
To set up two-factor authentication in Web Access

2 Click the Web Access node and then click Properties to display the Web Access Site
Properties window.
vWorkspace 8.6.3
3 Select Two-Factor Authentication, and complete the information on the window (the
fields that are displayed on this form vary depending whether you select the Secure
Computing PremierAccess or RADIUS options).
• If you select Secure Computing PremierAccess, enter the location for the
PremierAccess configuration file.
• If you select RADIUS, enter the RADIUS settings.
Table 81. Two-factor authentication fields for PremierAccess
Field Description
Enable two-factor Check this box to enable two-
authentication factor authentication for all
applications.
Secure computing Select this button to display the
PremierAccess authentication options for Secure
Computing PremierAccess.
RADIUS Select this button to display the
authentication options for RADIUS.
File The location for the
PremierAccess connection
configuration file.
Table 82. Two-factor Authentication fields for RADIUS
Field Description
Enable two-factor Check this box to enable two-
authentication factor authentication for all
applications.
Secure computing Select this button to display the
PremierAccess authentication options for Secure
Computing PremierAccess.
RADIUS Select this button to display the
RADIUS options.
Servers Add the RADIUS servers that you
want to use for authentication.
If more than one is identified,
Web Access will enforce load
balancing by randomly choosing
the next available server.
Port Listening port of the RADIUS
server.
Secret key Shared password used to
communicate with the RADIUS
server.
Use separate OTP field Allows Radius Authentication to
use a separate Active Directory
password field and passcode field.
NOTE: If you have two-factor
authentication enabled on both
the vWorkspace Management
Console and on Web Access, you
must have an advanced target set
up.
vWorkspace 8.6.3
Table 82. Two-factor Authentication fields for RADIUS
Field Description
Authentication type Select between encrypted (CHAP -
Challenge-Handshake
Authentication Protocol) and
unencrypted (PAP - Password
Authentication Protocol).
Password structure Controls the order the AD and OTP
passwords are entered by the user.
OTP length Inform the Web Access server of
the length of the OTP (one-time
password).
4 Click Apply to save the new settings.
To set up two-factor authentication in the vWorkspace Management Console and

Web Access
You may consider setting up two-factor authentication on both the vWorkspace Management
Console and Web Access if:
• You use vWorkspace Connector for Windows Connector internally and your end users
access vWorkspace through Web Access externally.
• You are in the process of a migration from either a pre-7.5 vWorkspace environment or a
Citrix deployment.
NOTE: If you have two-factor enabled on both your vWorkspace Management Console and on Web Access,
then you must have an advanced target set up.
Managed Applications
From the Managed Applications node, you can enable graphics acceleration globally for managed
and unmanaged applications, set custom properties, and set permissions for users for all
managed applications.
Before an application can be published and accessed by users, it must be installed on the hosting
computer. In a vWorkspace infrastructure, the hosting computer can be any of the following:
• Microsoft RD Session Host applications
• Managed Computer applications
• Virtualized Applications
Microsoft RD Session Host applications

Applications installed and published on Microsoft RD session hosts (RDSH) are sometimes referred
to as shared or multi-user applications. This is because a single installation of the application
can be used simultaneously by multiple connected users.
When Remote Desktop Services is enabled on Microsoft Windows servers, you must ensure the
application is installed properly.
Considerations:
• Session hosts need to be in the install mode when installing applications intended for
multi-use. This is done automatically when the Control Panel, Add |Remove Programs is
used, but can also be started from a command prompt using the following command:
Change User/Install.
vWorkspace 8.6.3
• Users should not be logged on to the system when installing applications.
• Review documentation for issues that might exist when installing and using an application
with Remote Desktop Services. Some applications have special procedures or command
line switches that must be used for installation on Remote Desktop Services.
• Restrictions such as support for the full feature set or license restrictions may be
applicable when used on Session Hosts.
• Applications such as Computer Aided Design or scientific modeling and analysis programs
may not be good candidates for Session Host based deployments. These types of
applications place an increased demand on the physical resources of a computer.
When provisioning a new session host into an existing folder of session hosts, managed
applications that have been published to all of the other session hosts in the folder are
automatically added to the new session host.
Managed Computer applications

A major benefit of hosting applications on vWorkspace-enabled managed computers is that no
special considerations are needed; you install the application as it would be done for a Microsoft
Windows computer. The applications can be installed manually, or pushed to the managed
computer using third-party tools such as Microsoft Active Directory Group Policy (Software
Installation) or Microsoft SMS.
Considerations:
• Install all the applications a user might need on to the same managed computer. This
reduces the number of remote sessions needed for a user to accomplish their work.
• Use managed computers for special-purpose applications that do not need to be made
widely available.
• Use managed computers for applications that are too resource-intensive to be installed
on Session Hosts.
• Use managed computers for applications being created and tested in a software
development environment, especially when implemented as virtual computers.
Virtualized Applications
Many application deployment solutions simplify and accelerate the process of deploying line-of-
business applications to the user desktop. These same tools are ideal for use in a vWorkspace-
enabled desktop infrastructure.
Specify properties for Managed Applications

The Managed Applications Properties option allows administrators to globally:
• To enable Graphics Acceleration for applications.
• To set up custom properties for applications.
• Set Permissions.
To enable Graphics Acceleration for applications

You can globally set graphics acceleration and image quality for all managed and unmanged
applications.
2 Right click on the Managed Applications node, and select Properties.
vWorkspace 8.6.3
3 From the Graphics Acceleration window, select the default graphics acceleration setting.
4 Select the image quality for graphics accelerated applications.
5 Click OK.
You can set graphics acceleration for individual managed applications.
2 Right click on the Managed Applications node
3 In the Managed Applications window, right click a managed application, and select
Properties.
4 Select the Graphics Acceleration option.
5 From the Graphics Acceleration window, specify the graphics acceleration setting.
6 Click OK.
To set up custom properties for applications

Managed applications can have up to five custom properties. You can label managed
applications, for example, by customer.
Create the custom properties.
2 Right click on the Managed Applications node, and select Properties.
3 Select the Custom Properties option.
4 From the Custom Properties window, enter the names of the custom properties.
These names will appear in the column headers in the applications view.
5 Click OK.
Then, define values for each custom property.
7 Right click on the Managed Applications node
8 In the Managed Applications window, right click a managed application, and select
Custom Properties.
9 In the Custom Properties window, define values for each custom property.
10 Click OK.
Permissions
Managed Applications properties is used by administrators to allow or deny actions for
activities within the vWorkspace Management Console. For more information on Permissions, see
To add a system administrator on page 49.
New Application tool

The New Application command is used to publish an application, desktop, or content. It can be
opened from the following locations within the vWorkspace Management Console.
• Sessions Hosts node
• Desktops node
• User Environment Management node
• To start new applications for a Resource
vWorkspace 8.6.3
To start new applications for a Session Host
2 Expand Locations and then the location name where the Session Host is located.
4 Select either Management or Provisioning.
5 Select the Applications tab in the information pane.
6 Select New Applications from either the toolbar or by the context menu which can be
accessed by right-clicking in a blank area of the information pane.
To start new applications for a Desktop

2 Expand Locations, and then the location name where the computer group is located.
3 Expand the Desktops node.
4 Select the computer group into which the application is to be published.
5 Right-click on desktop group, and then select New application in group.
To start new applications for a Resource

2 Expand the Resource node, and highlight Managed Applications.
3 Right-click the Managed Applications node, and then select New Managed Application.
Publish RD Session Host applications

The most direct way to publish applications hosted on RD Session Hosts is to start New
Application from either the Session Hosts or User Environment Management nodes (see New
Application tool for more information).
To publish an application hosted on session hosts

1 From the Management Console, right click the Managed Applications node and select New
Managed Application.
2 On the Welcome window of the Managed Application Wizard, click Next.
3 On the Application Name window, specify the following and then click Next.
Table 83. Application Name fields
Field Description
Name Specify a friendly name for the application.
Published application friendly names are limited to 150
characters. If any names are longer than 150 characters,
they get truncated, and any duplicates are suffixed with a
numeric value to ensure uniqueness.
Custom Properties Enter the names of the custom properties you want to assign
to the managed applications. These names appear in the
column headers in the applications view, which can assist
with searching and sorting.
4 On the Application Type window, select the type of application, and then click Next.
5 On the Publishing window, select Session Hosts and select the servers on which to publish
the application for a specified location, and then select Next.
vWorkspace 8.6.3
6 On the Defaults window, complete the following information and then click Next:
Table 84. Defaults fields
Field Description
Select App-V Application If the application to be published is a virtualized application
package stored on an App-V server, click Select App-V
Application.
Path Enter a path, or select the ellipsis to browse.
Arguments Enter any arguments that you want to have passed to the
application when started.
%Connector_ARGS% needs to be added as an argument if you
want to use this managed application to assign a file type
association in Desktop Integrated mode. See vWorkspace
Connector for Windows actions menu options for more
information.
Working Dir If the application requires a working directory, type its path
7 On the Server Specific window, enter server-specific program specifications. Click Next.
8 On the Display Name window, enter a Display Name if you want the name that is
displayed to the user to be different than what is in the Name box on the Application
Name window. Click Next.
9 On the Icon window, select an icon for the application, and then click Next.
10 On the Window window, specify the following settings, and then click Next.
Table 85. Window fields
Field Description
Initial window state Specify the initial window state for this application.
Specify seamless window mode Specify the seamless window mode to use for this
application:
Use vWorkspace seamless window mode. When end users
have seamless windows enabled, the vWorkspace seamless
window technology is used for this application.
Force off. Does not allow seamless window mode to be used
for this application.
Use Microsoft seamless window mode. When end users
have seamless windows enabled, the native Microsoft
seamless windows technology is used for this application.
11 On the Desktop Integration window, select the appropriate option (Desktop, Start Menu,
Start Menu \Programs) for clients using vWorkspace Connector for Windows in desktop
integrated mode, and then click Next.
12 On the Graphics Acceleration window, select the appropriate option, and then click Next.
The Use Default option refers to the default Graphics Acceleration option setting on the
Managed Applications Properties window. See To enable Graphics Acceleration for
applications on page 161 for more information.
13 On the Enable/Disable window, select Enabled or Disabled, and then click Next.
NOTE: If you select Disabled, the application is not displayed in client application lists.
14 On the Load Balancing window, complete the settings, and then click Next.
NOTE: The Enable this application to share on active session option must not be selected if you are
using Web Access with published applications where multiple users use the same computer, such as a kiosk
or other semipublic user.
vWorkspace 8.6.3
15 On the Virtual-IP window, specify the Virtual-IP settings for this application, and then
click Next.
16 On the Target Assignment window, assign this application to targets, and then click Next.
17 On the Permissions window, set the Permissions for this application, and then click
Finish.
To publish session host desktops

The steps for publishing a shared Windows desktop hosted on a Session Host are exactly the same
as that for publishing a shared application, except for the following:
1 The Application Type is set to Desktop. When this is done, no path, arguments, or
working directory are needed, and the fields for these are not presented.
2 The Defaults and Server-Specific options are not available.
3 The Startup option is only available if the Type is Program.
vWorkspace Application task bar

A vWorkspace Application task bar allows users to access published applications from non-
Windows Connectors that do not support seamless applications. When you launch an application,
the Application Taskbar is displayed at the bottom of the screen, under the application window.
The Application Taskbar is similar to the Windows taskbar. It shows each running application with
an icon and window title, and allows you to switch between them. It also displays the system
tray icons.
If the Seamless Window Mode is set to Force Off, then the seamless taskbar will not
automatically display on non-windows Connectors.
Publish a managed desktop

You can publish a desktop to the managed computer group using the New Managed Application
wizard.
To publish a desktop to a managed computer group

2 Expand the Desktops node at the required location.
3 Navigate to the computer group where the desktop is to be published.
4 Select New Application from the context menu.
5 On the Welcome window of the Managed Application Wizard, click Next.
6 On the Application Name window, do the following:
a Specify a friendly name for the application in the Name box, and then click Next.
Published application friendly names are limited to 150 characters. If any names are
longer than 150 characters, they get truncated, and any duplicates are suffixed with a
b Enter the names of the custom properties you want to assign to the managed
applications. These names appear in the column headers in the applications view,
which can assist with searching and sorting.
7 On the Application Type window, select the type of application, Desktop, and then click
Next.
vWorkspace 8.6.3
8 On the Publishing window, select the Managed Computer Group option, and then select
the managed computer group from your location on which to publish the application.
Click Next.
11 Select the appropriate option (Desktop, Start Menu, Start Menu \Programs) for clients
using vWorkspace Connector for Windows in desktop integrated mode on the Desktop
Integration window, and then click Next.
12 Select the appropriate option on the Graphics Acceleration window, and then click Next.
The Use Default option refers to the default Graphics Acceleration option setting defined
in the Managed Applications Properties.
13 Select Enabled or Disabled to specify if this application is displayed on the client
application list.
14 Use the Target Assignment window to assign this application to targets, and then click
Next.
15 Set Permissions on the Permissions window, and then click Finish.
Publish managed applications

Publishing an applications hosted on a managed desktop is similar to that of RD Session Host. The
major differences is that Load Balancing is not available for managed desktops.
To publish an application
2 Expand the Desktops node for the required location.
3 Navigate to the computer group where the desktop is to be published.
4 Start New Application by selecting the New Application icon from the toolbar or
Actions | New Applications.
5 Click Next on the Welcome window of the Managed Application Wizard.
6 On the Application Name window, do the following:
a Specify a friendly name for the application in the Name box, and then click Next.
Published application friendly names are limited to 150 characters. If any names are
longer than 150 characters, they get truncated, and any duplicates are suffixed with a
The following characters cannot be used in application names that are to be published for
Web Access: <, >, /,\, *, y ’.
b Enter the names of the custom properties you want to assign to the managed
applications. These names appear in the column headers in the applications view,
which can assist with searching and sorting.
7 On the Application Type window, select the type of application, Program, and then click
Next.
8 On the Publishing window, select Managed Computer Group, and then select the
managed computer group from your location on which to publish the application. Click
Next.
9 Complete the following information on the Defaults window, and then click Next:
vWorkspace 8.6.3
a If the application to be published is a virtualized application package stored on an
App-V server, click Select App-V Application.
b Enter a Path, or select the ellipsis to browse.
c Enter any arguments that you want to have passed to the application when started
in the Arguments box.
d If the application requires a working directory, type its path in the Working Dir
box.
12 On the Startup window, specify the application window state when started, and then
click Next.
13 Select the appropriate option (Desktop, Start Menu, Start Menu \Programs) for clients
using the vWorkspace Connector for Windows in desktop integrated mode on the Desktop
Integration window, and then click Next.
14 Select the appropriate option on the Graphics Acceleration window, and then click Next.
The Use Default option refers to the default Graphics Acceleration option setting of
Managed Applications Properties.
15 Select Enabled or Disabled to specify if this application is displayed on the client
application list.
16 Select Target Assignments to specify the targets that are to have access to this
application and assign this application to them, and then click Next.
17 Set permissions on the Permissions window, and then click Finish.
Publish content
Traditionally in Windows networks, users have relied on network drive mappings, browsing, or
corporate Web sites to get information. As networks grow in size and complexity, these methods
have become less efficient.
Web based resources that are not located on the corporate network can require users to
remember numerous and sometimes long URLs, or to know how to build efficient and effective
search queries. Published content provides an easier way for users to access the information
they need. When an administrator publishes content, the complete path to the resource is
specified and is associated with an icon. This path can be in Universal Naming Convention (UNC)
format or web based formats, such as http, https, ftp, ldap. The icon representing the content is
passed down to the vWorkspace Client in the same manner as application and desktop icons.
To access the content, the user simply clicks on the icon. The content path is passed to an
application, based on Windows file type associations, capable of opening that type of content.
For example, content using a UNC path would be opened with Windows Explorer, while content
using http would be opened with Internet Explorer. The administrator has the option of
specifying whether the application used resides on the client device or on a remote device.
TIP: If you want users to have multiple sessions to the same server, the Restrict
each user to one session setting at the following path must be set to No.
Administrative Tools | Terminal Services Configuration | Server Settings
If you are using an application deployment solution such as Application Virtualization,

applications are published using the type Content.
The process of publishing content is exactly the same as publishing an application hosted on a RD
Session Host or desktop with the following exceptions:
vWorkspace 8.6.3
• Type. Select Content on the Application Type window of the Managed Application
Wizard, and then select where the content is to be published (Server or Client).
• Publishing. Select Session Host(s) if you want the content to be opened with an
application installed on an RD Session Host, and then select which RD Session Host to use.
Select Managed Computer Group if you want the content to be opened with an
application installed on the client device. When this is chosen, the Server-Specific and
Load Balancing windows are unavailable as they do not apply to desktops.
• Path. Enter the path to the content on the Defaults window. A UNC path can be either to
a shared folder or a file within a shared folder.
NOTE: Share, NTFS, and web permissions all apply when users try to access the
content. Therefore, even though clients are listed in the published content’s
access control list, the client may still be denied access because of other
permissions.
Published applications tasks

After applications have been published on either Session Hosts or desktops, additional
applications can be added, modified, duplicated, and deleted.
The Select Applications to Publish menu option is a way to add existing published applications,
desktops, or content to either a Session Host or computer group when new Session Host or
computer groups have been added to the vWorkspace infrastructure.
Managed applications that are published to all session hosts within a folder, are published to all
newly provisioned session hosts in the same folder. For example, if Adobe Reader has been
published on all of the session hosts in a folder, then it will automatically be published to a new
session host in the folder.
All properties of published applications, desktops, or content can be modified after they are
created. An existing published application can be duplicated and then modified, but the
duplicate needs to be given a unique name.
When a published resource is no longer needed, it can be deleted from the database. Deleting a
published application, desktop, or content does not remove the application from the hosting
computer nor does it delete the actual desktop or content.
• To add published applications to a session host
• To add published applications to a computer group
• To modify published applications for a session host
• To modify published applications for a Desktops
• To modify published applications from User Environment Management
• To duplicate a published application
• To delete a Published application
To add published applications to a session host

3 Click on the Session Host node in which to add the existing published resources.
4 Double-click on Management or Provisioning.
5 In the information pane on the right, click on the Applications tab for the selected
Session Host.
vWorkspace 8.6.3
6 Click on the Published Applications icon from the navigation pane toolbar or the
information pane toolbar, or select Actions | Publish Applications. A list of published
resources is presented.
7 Select each published resource you want to add to the server. To select a published
resource, select the box to the left of the application.
8 Click Apply to make the changes without closing the window, or click OK to make the
changes and close the window.
To add published applications to a computer group

2 Expand Locations and then the location name where the computer group is located.
3 Expand the Desktops node and highlight the computer group.
4 Use one of the following to open the Select Applications to Publish:
• Right-click on the computer group.
• Select the Managed Applications tab in the information pane, and then Actions|
Select Applications to Publish in the information pane.
5 Select each published resource you want to add. To select all published resources, select
the box to the left of Applications.
changes and to close the window.
To modify published applications for a session host

3 Click on the Session Hosts node in which to modify the existing published resources.
4 Double-click on either Management or Provisioning.
5 Click on the Applications tab located in the Session Hosts information pane.
6 Highlight the published resource to be modified, and then select Properties from the
context menu, or click on the Properties icon on the information pane toolbar.
7 On the Managed Application Properties window, navigate through the various windows to
make the necessary changes.
To modify published applications for a Desktops

2 Expand Locations and then the location name where the computer group is located.
3 Expand the Desktops node (you can also navigate to a specific datacenter or computer
group).
4 Click on the Managed Applications tab in the information pane.
context menu, or select Actions | Properties on the information pane.
6 On the Managed Application Properties window, navigate through the various tabs to
make the changes, as appropriate.
vWorkspace 8.6.3
To modify published applications from User Environment Management
2 Expand the User Environment Management node, and then click on the Managed
Applications node.
context menu, or select the Properties icon from the information pane.
4 On the Managed Application Properties window, navigate through the various tabs to
make the changes, as appropriate.
To duplicate a published application

2 Navigate to the desired published application under the Session Hosts, Desktops, or User
Environment Management node.
3 Right-click on the published application, and select Duplicate from the context menu.
4 Make the necessary changes using the appropriate windows on the Managed Applications
Properties window.
To delete a Published application

2 Navigate to the desired published application under the Session Hosts, Desktops, or User
Environment Management node.
3 Click Delete on the toolbar or from the context menu.
4 After reviewing the warning message, click Yes to delete or No to cancel.
Internet Explorer browser management

There are two features that are available in vWorkspace in conjunction with Internet Explorer
(IE):
• Internet Explorer redirection
• Internet Explorer compatibility
Internet Explorer redirection

This feature allows IE browser content on a Virtual or Terminal server to be opened using the IE
browser on the client physical desktop. It redirects IE from the server to the user access device.
For example, if a user clicks a link to a URL on their VDI desktop, that URL is opened using the IE
browser on their local PC. The browser on the virtual machine or terminal server is not used.
TIP: When IE redirection is enabled, some embedded hyperlinks in documents may
not be redirected.
The advantages and disadvantages to this feature are as follows:

Advantages:
• Frees up resources.
vWorkspace 8.6.3
• Frees up bandwidth.
Disadvantages:
• If you have Linux or Mac OS X clients, you will need to create separate virtual machine
and terminal server pools so IE is not redirected. This is because IE is not available to
those operating systems.
• If the user is connected externally and no VPN is connected, the user will not be able to
connect to local resources (such as intranets).
When you enable IE Redirection from the virtual computer to the end point, embedded URLs are
intercepted on the virtual computer and sent to the end point. The user's locally installed
browser is then used to access the URL. Users cannot disable this feature.
For example, users may frequently access web and multimedia URLs they encounter when
running an email program published on a server. If you do not enable IE Redirection from the
virtual computer to the end point, users open these URLs with IE present on servers running
vWorkspace redirection-enabled servers.
You must install Virtual Desktop Extensions (PNTools) and the following server side registry
entries need to be set.
To register:
• HKEY_CLASSES_ROOT\HTTP\shell\open\command
"(Default)" (REG_SZ) = ""C:\Program Files\Quest Software\ PNTools\IE
Redirection\iexplore.exe" %1"
• HKEY_CLASSES_ROOT\HTTPS\shell\open\command
"(Default)" (REG_SZ) = ""C:\Program Files\Quest Software\ PNTools\IE
For a x64 bit system, the registry entry should be set as follows:
"(Default)" (REG_SZ) = ""C:\Program Files(x86)\Quest Software\ PNTools\IE
"(Default)" (REG_SZ) = ""C:\Program Files(x86)\Quest Software\ PNTools\IE
For a computer where Windows is installed on a drive other than C:, the registry entry should be
set with the appropriate drive designation as follows (for example, if the drive designation is D):
"(Default)" (REG_SZ) = ""D:\Program Files\Quest Software\ PNTools\IE
"(Default)" (REG_SZ) = ""D:\Program Files\Quest Software\ PNTools\IE
To unregister:
"(Default)" (REG_SZ) = ""C:\Program Files\Internet Explorer\IEXPLORE.EXE" -nohome"
"(Default)" (REG_SZ) = ""C:\Program Files\Internet Explorer\IEXPLORE.EXE" -nohome"
Resetting Internet Explorer as the default browser
If the computer has another web browser installed and one of them is set as default, reset
Internet Explorer as the default web browser by doing the following:
vWorkspace 8.6.3
1 Go to Control Panel |Default Programs |Set Default Programs.
2 Click on Internet Explorer on the left and click Set as Default on the right bottom area.
3 Set the following registry keys to enable IE Redirection:
HKEY_CLASSES_ROOT\IE.HTTP\shell\open\command"(Default)" (REG_SZ) ="C:\Program
Files\Quest Software\vWorkspace\IE Redirection\iexplore.exe" %1
HKEY_CLASSES_ROOT\IE.HTTPS\shell\open\command"(Default)" (REG_SZ) ="C:\Program
Files\Quest Software\vWorkspace\IE Redirection\iexplore.exe" %1
For a x64 bit system, the registry entry should be set as follows:
HKEY_CLASSES_ROOT\IE.HTTP\shell\open\command"(Default)" (REG_SZ) ="C:\Program Files
(x86)\Quest Software\vWorkspace\IE Redirection\iexplore.exe" %1
HKEY_CLASSES_ROOT\IE.HTTPS\shell\open\command"(Default)" (REG_SZ) = "C:\Program Files
(x86)\Quest Software\vWorkspace\IE Redirection\iexplore.exe" %1
Internet Explorer compatibility

vWorkspace Internet Explorer compatibility is a set of features that allow an alternate version of
Internet Explorer to be delivered to a Windows client running the vWorkspace Connector, or to a
Windows Server with the vWorkspace TS/RDSH Role.
vWorkspace Internet Explorer compatibility seamlessly presents vWorkspace-managed
applications from Windows Terminal Servers or Session Hosts to a Windows Client desktop when
applications that require a specific version of Internet Explorer are different than the version on
the Windows Client operating system.
A user’s local Internet Explorer browser can be set to hook specific URLs, and launch them with
associated vWorkspace managed applications. From a server, the user's hosted Internet Explorer
browser can be configured by vWorkspace to redirect back to the client's local Internet Explorer
instance when the user browses to specific URLs, or when the user browses to sites that are not
configured for use with the hosted browser.
Internet Explorer compatibility consists of the following components:
• vWorkspace Connector Settings Group Policy Admin template (vWorkspace.adm or
.admx). This template is used to configure the vWorkspace Connector, such as Broker
Type, Broker Name, XML Port, and Authentication Settings. This can be used as an
alternative to the config.xml file.
• Config.xml. This XML file is used to configure the vWorkspace Connector, such as Broker
Type, Broker Name, XML Port, and Authentication Settings. It can be used instead of the
vWorkspace Connector Settings Group Policy Administrative Template.
• vWorkspace Connector Internet Explorer URL Redirection Browser add-on
(pnurlhook.dll). This add on is used to launch the vWorkspace Connector for Windows in
Desktop Integrated mode and display the managed application associated with the URL.
• vWorkspace Session Host or Terminal Server Internet Explorer URL Redirection
Browser add-on (pnurlhook.dll). This add on is used to send a user to their local Internet
Explorer browser when the user browses to sites that are not configured for use with the
hosted browser.
• vWorkspace Client URL Redirection Group Policy Admin template (ClientSide IE.adm or
.admx). This User Configuration Group Policy Administrative template is used to configure
the URLs that should be redirected to a vWorkspace managed application. This template
is applied in a GPO that is linked to the OUs where the target user accounts exist.
• vWorkspace Server URL Redirection Group Policy Admin template (ServerSide IE.adm
or .admx). This Computer Configuration Group Policy Administrative template is used to
configure the URLs that should be redirected back to the client's local instance of
Internet Explorer. This template is applied in a GPO that is linked to the OUs where the
vWorkspace Session Hosts/Terminal Servers exists.
vWorkspace 8.6.3
Configuration of a managed application
For the URL Redirection Internet Explorer Browser add-on to successfully launch a web site in a
hosted Internet Explorer session, the following must be true:
• The client operating system default Internet browser is Internet Explorer.
• The URL Redirection Add-On (Pnurlhook.dll) is enabled in Internet Explorer. This is
done during the vWorkspace Connector installation.
• At least one URL is configured in on the client workstation for the logged on user
at HKCU\Software\Provision Networks\Provision-IT Client\Server
Farms\Farm1\URLCapture. This is configured using Group Policy, Config.xml, or
manual registry entry.
• A vWorkspace-managed application is properly configured for URL Redirection to
match the setting on the client, and is assigned to the appropriate vWorkspace
target.
Most web applications require a specific Java Applet, .Net application, or ActiveX
control, which needs to be installed on the selected session host for the application to
work properly.
The following needs to be considered when configuring a managed application:
When completing the Program Specifications | Defaults settings on the New Managed
Application wizard, use the following settings:
Table 86. New Managed Application settings
Path c:\Program Files\Internet Explorer\IEXPLORE.EXE

Arguments %Connector_ARGS%
The argument %Connector_ARGS%, means that Internet Explorer is
launched and the argument is the URL that is specified on the client
device at:
HKCU\Software\Provision Networks\Provision-IT
Client\URLCapture\
REG_SZ
Name = Integers starting at one, increasing for each additional
configured URL
Value = [Name of Managed Application]|URL
For example: REG_SZ=1,
Value=MyWebApp|http://mywebserver.mydomain.local/ mywebapp*
There is no space between the managed application name and the
URL, they are separated only by a pipe (|). The asterisk (*) is a
wildcard that can be placed anywhere in the URL string to capture
multiple web servers or multiple web sites.
For example: REG_SZ=1,
Value=MyWebApp|*.mywebserver*.mydomain.local/ mywebapp*
This would capture HTTP or HTTPS connections to web servers starting
with [mywebserver], like mywebserver01, 02, delivering any URL
starting with [mywebapp].
Select the Target that is allowed to run this application. Although in typical deployments,
all of the configured URLs are pushed to all users, only authorized users are allowed to
launch the application. Nonauthorized targets receive an error stating that the
application is not found.
For more information on how to configure a vWorkspace managed application, see Publish
RD Session Host applications.
vWorkspace 8.6.3
Typical vWorkspace deployment
A typical deployment of vWorkspace Internet Explorer Compatibility consists of:
• One or more Hyper-V servers running vWorkspace Hyper-V Catalyst components for
hosting vWorkspace Terminal Server or Session Host virtual computers.
• One Terminal Server or Session Host virtual computer for every 20-25 expected
concurrent users of Internet Explorer. Each virtual computer is typically configured for 2
vCPUs and 1024-4096MB of dynamic memory.
• Two or more vWorkspace Connection Brokers for user authentication and provisioning of
the vWorkspace Terminal Server or Session Host virtual computers.
• System Center Configuration Manager or Group Policy to deploy the vWorkspace
Connector.
• Group Policy to configure the client redirection URLs.
• Group Policy to configure the server redirection URLs.
• vWorkspace Connectors configured in Desktop Integrated Mode.
To deploy the settings through the group policy

If deploying the vWorkspace Connector Settings through Group Policy, the following must be
completed:
1 Configure vWorkspace Connector for Windows in Desktop Integrated mode. Although the
Client URL Redirection Plug-In dynamically launches vWorkspace Connector for Windows
in Desktop Integrated mode, farm authentication fails if vWorkspace Connector for
Windows does not launch in Desktop Integrated mode at least once before it is used to
redirect a URL.
2 Configure the following vWorkspace Connector Group Policy Administrative Template
settings.
a vWorkspace Connector\Delete Entries\Version\Enabled\
Version = Checked
b vWorkspace Connector\Delete Entries\ Encrypted\Enabled\Encrypted = Checked
c vWorkspace Connector\Farm Type\Farm Settings\Enabled\
Select Farm Type = vWorkspace Connection Broker
d vWorkspace Connector\Connectivity\Location 1\
vWorkspace Connection Settings\Enabled\
Protocol = http, TCP Port = 8080 (or alternative XML port connection), 
Connection Broker(s) =ListBrokerNamesHere,
Broker1,Broker2,Broker3
e vWorkspace Connector\Credentials\
Cached Credentials = Enabled, 
User Supplied Credentials = Enabled, Allow User Supplied Credentials = Checked
3 Set the following in the GPO that applies to the Terminal Servers/Session Hosts OU, so
that Computer Group Policies are enforced the first time the Terminal Server’s Computer
Account authenticates with Active Directory.
Computer Configuration | Administrative Templates |System\Logon | Always wait for the
network at computer startup and logon = Enabled
4 Disable Shutdown Event Tracker. Failure to do this prevents a managed application from
successfully launching, without manually switching to desktop view to enter the reason
for an unexpected shutdown.
Computer Configuration |Administrative Templates | System\
Display Shutdown Event Tracker = Disabled
vWorkspace 8.6.3
5 Apply the hotfix referenced in Microsoft KB article 942610, if using Microsoft Server 2003
R2.
http://support.microsoft.com/kb/942610
In addition, the following registry entry needs to exist on the Terminal Servers so user’s
Remote Display Settings are not reduced to 8-bit when their screen resolution is higher
than 1600x1200.
HKEY_LOCAL_computer\SYSTEM\CurrentControlSet\Control\
Terminal Server
Registry entry: AllowHigherColorDepth
Type: REG_DWORD
Value: 1
6 Disable the screen saver if using Microsoft Server 2003 R2. The screen saver option is
enabled by default, which would require users to authenticate to unlock the screen saver.
To disable the screen saver setting, set the following in Group Policy:
User Configuration | Administrative Templates | Control Panel | Display | Password
protect the screen saver = Disabled
User Configuration | Administrative Templates | Control Panel | Display |Screen Saver
executable name = Disabled
User Configuration | Administrative Templates | Control Panel | Display | Screen Saver
timeout = Disabled
vWorkspace interfaces
A vWorkspace Connector allows users to access the virtual workspace from a client device.
vWorkspace provides Connectors for the following platforms:
• Connector for Windows. Allows users to access virtual desktops and managed
applications from Windows computers, laptops, and thin client terminals. vWorkspace has
an intuitive windows application that helps users to view a list of authorized desktops and
applications. vWorkspace Web Access allows users to retrieve a list of available
applications or desktops through a web browser.
• Mac OS X Connector. Users can access their virtual desktops from a Mac-based client.
Supports up to two monitors with a resolution of up to 1400 x 900 for each monitor.
• iOS Connector. Allows users to connect to their virtual desktops from an iOS device. It
has a built-in support for VPN connections.
• Android Connector. Allows users to connect to their virtual desktops from an Android
device.
• Linux Connector. Allows users to access virtual desktops from a Linux-based client.
Supports features such as bidirectional audio content redirection, which enhance user
experience.
• Java Connector. A platform-independent Connector that works in conjunction with the
Web Access component.
• Chrome. Allows users to connect to vWorkspace from a Chrome OS.
• HTML5. Allows users to connect to vWorkspace using HTML5.
This document describes using the vWorkspace Connector for Windows. For information about
using the non-Windows Connectors, see the vWorkspace documentation for each Connector.
vWorkspace 8.6.3
Using the vWorkspace Connector for Windows
The administrator can set up a vWorkspace Connector configuration from the vWorkspace
Management Console. Users can then connect to a vWorkspace environment by using Web Access
or by using the vWorkspace Connector for Windows. The Connector automatically detects,
installs and configures the users’ devices, based on the Connector Management settings (see
Connector management overview on page 104).
To initially connect to vWorkspace using Web Access

1 The Administrator creates a Web Access site (see Web Access configuration on page 199).
The option to immediately direct to the native Connector is NOT selected.
2 The Administrator copies the link of the Website from the Web Access configuration and
distributes the link to users by email or other means.
3 The user receives the link to the Web Access site and clicks on it.
4 vWorkspace detects that the Connector is not installed, and installs the current version.
5 The user is prompted to log in. The user sees the list of application icons in the web
browser.
6 The user clicks on applications and connects to the remote application using either the
native Connector, the Chrome Connector or the HTML5 Connector.
To initially connect to vWorkspace by redirecting from Web Access to the native

Connector
1 The Administrator creates a Web Access site and configures it to immediately redirect to
the native Connector (Web Access configuration on page 199).
2 The Administrator sets up Connector configurations (Connector management overview on
page 104).
3 The Administrator copies the link of the website from the Web Access configuration and
distributes the link to users by email or other means.
4 The user receives the link to the Web Access site and clicks on it from the native client.
6 The user is prompted to log in. After logging in, the list of application icons is displayed in
the web browser.
7 The user clicks on applications and connects to the remote applications using the native
Connector.
To initially connect to vWorkspace from a policy-based configuration

1 The Administrator creates a Web Access site (see Web Access configuration on page 199).
The option to immediately direct to the native Connector is NOT selected.
2 The Administrator copies the link of the website from the Deployment feature in the
Connector Management Configuration, (see Deploying Connector updates on page 115)
and distributes the link to users by email or other means.
3 The user receives the link to the Web Access site and clicks on it.
5 The user is prompted to log in. The user sees the list of application icons in the native
Connector.
6 The user clicks on applications and connects to the remote applications using the native
Connector.
vWorkspace 8.6.3
To connect to vWorkspace if the native Connector is installed
If you want some users to connect using Web Access and other users to use the native Connector, copy the
link from the deployment dialog (see Deploying Connector updates on page 115).
1 From the Windows desktop, the user clicks the vWorkspace icon. If a configuration is not
set up, the user is prompted to enter an email address or a website name.
2 On the Logon Credentials prompt, the user enters credentials and clicks OK. The
vWorkspace window is displayed.
3 The name of the vWorkspace environment and icons for the applications of the selected
configuration are displayed.
4 From the vWorkspace window, the user can access the following:
• Toolbar options. See Using the toolbar options.
• Change configurations. See Change to a different configuration.
• Configuration tools and applications. See Using the configuration tools.
Figure 24. .vWorkspace window
Using the toolbar options

The Toolbar contains the following options:
• Log out. Log out of the current configuration. The password is also cleared.
• Add configuration. Add a new configuration. See To add a new configuration on page
177.
• Refresh. Refresh the applications and shortcuts for the current configuration.
• Change password. Change your password.
• Options. Access context menu options.
• Search applications. Enter the name of an application or shortcut to find it in the list.
To add a new configuration

1 From the Toolbar, the user clicks Add Configuration.
vWorkspace 8.6.3
2 The user enters the website name or email address, then presses Enter or clicks OK.
3 On the Logon Credentials prompt, the user enters credentials and clicks OK.
4 The Welcome window is displayed. The user enters login credentials and clicks OK. The
vWorkspace window is displayed, showing the new configuration.
Change to a different configuration

If more than one configuration is set up, users can connect to a different configuration.
To change to a different configuration

• Click the name of the configuration to connect to.
Using the configuration tools

• Settings. Displays the settings for the connection. The user can modify the
settings as necessary and click OK to save the changes.
NOTE: From the vWorkspace Management Console, the administrator can override any of the
settings designated here by the end-user.
• Information. View connection information for the configuration. The

administrator can use this information to verify that the user has the connection
policies set up correctly.
• Delete Configuration. Delete the current configuration. At the Delete prompt,
click OK.
To modify the configuration settings

1 The user opens the configuration to be modified.
2 The user clicks the Settings button.
3 The user can modify the settings in the table below as necessary.
Table 87. Windows Connector configuration settings

Configuration setting Description
Automatically connect to this Select this check box if you want the new configuration to be the
configuration on startup default configuration.
NOTE: Only one configuration can be the default.
Clear existing credentials Select this button if you checked the Save Credentials check box
when you logged into the configuration, but now want to clear those
credentials so they are not saved.
Display settings Select the following display settings:
• Screen resolution
• Use all my monitors for the remote session
• Display connection bar
• Pin connection bar
Device settings Select any of the following to determine which resources are
available within the published applications:
• Play audio
• Use microphone
• Use USB devices
• More devices
vWorkspace 8.6.3
4 Click OK.
NOTE: The user configuration settings were simplified in vWorkspace 8.6. If you need to access the
advanced user configuration settings that were available in version 8.5, use the following shortcut keys:
Windows: Ctrl+Shift+Click on gear
Mac OS X: Cmd+E in connection setting 
iOS: Long press on any place in connection settings 
Android: Tap on gears in connection settings 
Linux: Ctrl + Shift + gear on connection
To open an application
• Click an application to open it.
vWorkspace System Tray applet (PNTray)

The vWorkspace System Tray applet (PNTray) is available when the vWorkspace Connector for
Windows is started, or when a connection to a managed computer or a managed computer
application is active. The PNTray is displayed in the Windows system tray as the vWorkspace
context menu. The commands that are available depend on the vWorkspace Connector for
Windows mode and an active connection.
• Open Session Status
Use this option to view the sessions that are active on Session Hosts, and the applications
that are running in each session. Session Host sessions, when selected, can then be
changed using the buttons of Disconnect, Logoff, and Full Screen. Applications can be
terminated by using Terminate without logging off from the session.
• Change Current Location
• Logon as Different User
• Change Password
• Authentication
• Enable Credentials Pass-Through
• Refresh Application Set
• Restore vWorkspace Connector for Windows Client
• Close vWorkspace Connector for Windows Client
The following options are available from the Universal Printer section of the PNTray when the
vWorkspace Connector for Windows is in normal mode:
• PDF Publisher Options
• Save PDF File
• email PDF File
• Preview before printing
• Apply Additional Printer Properties
• Native printer options, such as finishing and stapling are presented when this
option is selected.
• Client Properties
• Diagnostics
• USB
vWorkspace 8.6.3
Using the vWorkspace Diagnostics Tool
The vWorkspace Diagnostics tool enables log configuration for components, collects the logs and
compresses them into a Zip file, which you can then send to Technical Support for analysis.
Typically, vWorkspace Diagnostics is used only when assisted by Technical Support.
The vWorkspace Diagnostics tool is included in all Windows-based vWorkspace components.
Prerequisites:
• If you are using a virtual desktop, ensure that Virtual Desktop Extensions (PNTools)
is installed.
• If you have User Account Control (UAC) enabled, run the Diagnostics Tool as an
Administrator.
TIP: If you are using vWorkspace Diagnostics with vWorkspace 7.6, copy PNTray.exe
and PNTray.dll to the Diagnostics folder if they are not installed in SysWow64.
Do not copy PNTray.exe or PNTray.dll into Syswow64 as this can cause problems
with future installations.
To collect logs from the Diagnostics System Tray

Use the following procedure to run vWorkspace Diagnostics:
1 Run the Diagnostics Tool by opening the executable from C:\Program Files (x86)\Quest
Software\vWorkspace\Diagnostics\PNDiagnosticsTray.exe.
The Diagnostics option is created in the System Tray.
2 Click Enable Diagnostics to start collecting diagnostics.
3 Perform any procedures that you want the log to capture.
4 When you are finished, click Enable Diagnostics again.
5 Select the folder in which you want to store the SupportPackage<date/time>.zip file.
The support package contains a folder for each component that generated logs during the
session. It also can contain module information about the binaries that are installed on
the system.
Collecting logs from the command prompt

You can optionally use vWorkspace Diagnostics from the command prompt. The commands are
listed in the following table.
Table 88. vWorkspace Diagnostics commands
Switch Parameters Notes

enable none Enables diagnostics.
disable C:\support package Disables diagnostics and places
folder ZIP at the specified path. The
path must be a folder, not a file
name.
Using vWorkspace Connector for Windows in

Desktop Integrated mode
The vWorkspace Connector for Windows can be started in Desktop Integrated Mode (the user
interface shell is suppressed), which runs from the Windows system tray area. Applications icon
vWorkspace 8.6.3
shortcuts are placed on the user’s Desktop, Start Menu, or All Programs menu, depending on your
settings.
NOTE: On a Windows XP computer, the placement of shortcuts depends on whether
Windows is using the Start menu or Classic Start menu.
To start vWorkspace Connector for Windows in Desktop Integrated mode

1 Start | Run
2 Type C:\Program Files\ Quest Software\vWorkspace Client\
3 Select vWorkspace (Desktop-Integrated).
The vWorkspace icon is displayed on the Windows toolbar status area.
Windows Client registry settings

The following registry keys can be used to set up Windows Client settings.
Initial application wait time

A registry setting on Windows endpoints with the vWorkspace Connector. It controls
the default initial application wait time. The purpose is to prevent users from
accidentally launching an application more than once (by clicking too fast). After a
vWorkspace Connector sends a request to the connection brokers to launch a specific
application, this value defines the amount of time in seconds before another request to
launch the same application (from the same endpoint) will be honored.
The default wait time value is set to 10 seconds. To change the default wait time value
to some other value create the following registry value. In the example below the initial
wait time value is set to 15 seconds.
HKLM\SOFTWARE\Provision Networks\Provision-IT
"InitialAppWaitTime" (REG_SZ) = "15"
NOTE: This registry value needs to be created in the HKLM\SOFTWARE\Wow6432Node on a 64-bit

platform.
Double hop client IP pass through

This setting is used for double-hop scenarios, where the client connects to an RDSH/TS or VDI,
then runs another session to a RDSH/TS or VDI. The setting enables the IP address of the client to
be passed to the last server in the chain. If an application needs the IP address of the end
device, and it is a double-hop scenario, then this feature should be enabled.
This setting is controlled though the following registry key. The default is 0.
HKLM\SOFTWARE\Provision Networks\\Provision-IT
RemoteClientPassthru = REG_DWORD (0=disabled 1=enabled)
Double hop client name pass through

This setting is used for double-hop scenarios, where the client connects to an RDSH/TS or VDI,
then runs another session to a RDSH/TS or VDI. The setting enables the name of the client device
to be passed to the last server in the chain. If an application needs the name of the end device,
and it is a double-hop scenario, then this feature should be enabled.
This setting is controlled though the following registry key. The default is 0.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Provision Networks\Provision-IT (for 64-
bit systems)
vWorkspace 8.6.3
HKEY_LOCAL_MACHINE\SOFTWARE\Provision Networks\Provision-IT (for 32-bit systems)
DoubleHop = REG_DWORD (0=disabled 1=enabled)
Disable client disconnect message

This setting controls whether a message box is displayed when PNTSC disconnects. By
default PNTSC will display a message box on disconnect. To disable the message box
on disconnect create the following registry value:
TSClientShowMsgBoxOnDisconnect REG_DWORD 0=don't show msgbox 1=show msgbox

(default)
Disable client multi-monitor warning message

This setting controls whether a warning is displayed when the computer has multiple
monitors and Windows Aero enabled. To disable the warning, create the following
registry value:
HKCU\SOFTWARE\Provision Networks\Provision-IT
TSClientDoNotShowWarning (REG_DWORD) 1=disables the warning
Mouse movement
This setting controls whether to disable mouse movement. To disable mouse
movement, create the following registry value:
TSClientAutoLANOptimize REG_DWORD 0=don't show msgbox 1=show msgbox (default)

Administrators can use the vWorkspace Management Console to view user sessions, Session Host
sessions, and processes running on the Session Hosts in the vWorkspace infrastructure to assist
with troubleshooting.
Administrators can also access vWorkspace user options located in the User Environment
Management node. When the environment is defined, it can be applied to a target. Targets
include users as well as groups. When there are multiple options assigned to a user or group,
they are assigned based on target order, except for the following:

Comment
Option
Additional customizations Applied in reverse target order (bottom to top).
The upper-most items found take precedence.
Managed applications Applied cumulatively; all matching items are
Printers applied.
Color schemes The first option from the top, is applied.

Wallpaper
vWorkspace 8.6.3

Comment
Option
Drive mappings Applied cumulatively; all matching items are
Environment variables applied. Applied in reverse target order (bottom to
top). The upper-most items found take
User policies
precedence.
Registry tasks Applied cumulatively; all matching resources found
Scripts are applied. Also, registry tasks and scripts to a
particular target may be ordered.
Additional customizations
The Additional Customizations node gives administrators control over the configuration of the
Windows Desktop and Start menu, visibility of drive letters, and existing network drive and
printer mappings.
Default Customizations are a set of customizations configured with settings commonly used in
Session Host and VDI environments, which can be assigned to vWorkspace targets. Default
Customizations cannot be modified, but they can be duplicated and used to create new
customized settings.
To create new additional customization settings

2 Expand User Environment Management, and then select Additional Customizations.
3 If necessary, click on the Toggle Client Assignment List Display button to change the
display view.
4 From the toolbar of the information pane, activate New (green plus sign).
5 On the Welcome window of the new Additional Customizations wizard, click Next.
6 On the Name window, enter a name for the customization, then click Next.
7 On the Desktop/Start Menu Items window, select the appropriate settings, and then click
Next.
8 On the Drive Restrictions window, specify the drive letters that should not be visible to
users, and then click Next.
9 On the Network Resource Cleanup window, select Delete pre-existing Network Drive
Mappings and Delete pre-existing Network Printer Connections, and click Next.
10 Complete the Target Assignment window to specify the targets to which the
customizations are assigned, and then click Next.
a Click the plus (+) sign to select targets, and the Select Targets window opens.
b On the Select Targets window, use the green plus (+) sign to add targets that are
not included in the Select Targets window.
c Select users from the list. Use Ctrl to select more than one user to assign.
d Click OK to close the window and save your assignments.
11 On the Permissions window, specify permissions, and then click Finish.
vWorkspace 8.6.3
Color schemes
A color scheme can be assigned to vWorkspace clients by administrators. The color scheme is
used when connecting to applications or desktops hosted from vWorkspace enabled Session Hosts
and VDI computers.
NOTE: When assigning color schemes through the vWorkspace Management Console, a
color scheme is not loaded for Microsoft Windows 7 or later.
To assign a color scheme

2 Expand User Environment Management, and then select Color Schemes.
3 Click on the Toggle Client Assignment List Display button to change the display view, as
appropriate.
4 To select a color scheme, click on the color, and then select Assign to.
5 In the Select Targets window, add or remove targets.
6 Click OK.
Drive mappings
Administrators can assign network drive mappings to vWorkspace to use when they are
connecting to applications and desktops hosted from vWorkspace enabled Session Hosts and VDI
computers.
Assigning drive mappings through the vWorkspace Management Console has the following
advantages:
• Domain administrative rights are not required.
• Knowledge of scripting languages or command line syntax is not required.
• Drive mappings are only applied when connecting to vWorkspace enabled Session Hosts or
desktops. More flexibility in how mappings are assigned.
To create a new drive mapping

2 Expand User Environment Management.
• Select Drive Mappings, and then click on the + on the toolbar in the information
pane.
• Right-click Drive Mappings and select New Drive Mappings.
4 On the Welcome window of the New Drive Mapping wizard, click Next.
5 On the Values window, select the values for this drive mapping, and then click Next.
Table 90. Values associated with drive mappings
Command Type Use NET USE when creating a

traditional network drive mapping.
Use SUBST when a drive letter
substitution is required.
Network Path The Universal Naming Convention
(UNC) path to the shared network
resource.
Drive Letter The letter to be used for mapping.
vWorkspace 8.6.3
6 Enter alternative credentials to be used when mapping this drive, and then click Next.
7 Complete the Target Assignment window to assign the drive mapping, and then click
Next.
a Click the plus (+) sign and the Select Targets window opens.
b Click the green plus (+) sign to add targets that are not included in the Select
Targets window.
8 Specify permissions on the Permissions window, and then click Finish.
Environment variables
Administrators can assign environment variables to vWorkspace when connecting to applications
or desktops hosted from vWorkspace enabled Session Hosts or VDI computers. These environment
variables are created automatically when the user logs on, and are cleared when the user logs
off.
To create a new environment variable

2 Expand the User Environment Management node.
• Select Environment Variables, and then click the + on the toolbar in the
information pane.
• Right-click on Environment Variables, and select New Environment Variables.
4 On the Welcome window of the New Environment Variable wizard, click Next.
5 Enter a name and value for the environment variable, and then click Next.
6 Complete the Target Assignment window to assign the variable, and then click Next.
a Click the plus (+) sign, to open the Select Targets window.
Targets window.
Registry tasks
The Registry Tasks tool allows administrators to add, delete, or modify registry keys in the
HKEY_CURRENT_USER registry hive without manually loading and editing each user’s
ntuser.dat registry hive, or writing complex registry editing scripts for RD Session Host or VDI
environments.
NOTE: The vWorkspace Management Console should be started from a Session Host
when working with Registry Tasks. A non-Session Host computer may not have
the registry keys and hives that need to be manipulated.
To modify a registry task

vWorkspace 8.6.3
2 Expand the User Environment Management node, and then select Registry Tasks.
3 Click the Toggle Client Assignment List Display icon on the information pane to change
the view, if needed.
4 From the context menu of the Registry Tasks node, select New Registry Task.
5 On the Welcome window of the Registry Task wizard, click Next.
6 On the Name window, enter a name for the registry task and then click Next.
7 Select the Registry Action from the following options:
• Add Key
• Delete Key
• Add Value
• Delete Value
8 Enter the key or value parameters, or use Browse to find the appropriate parameters.
• If you are adding a key, enter the name in the Key field.
• If you are deleting a value, select it from the list, and then click OK.
• If you are adding a value, enter the corresponding parameters in the fields.
• If you are modifying an existing value, change the Value Name, Value Type, or
Value fields as appropriate.
• Select the type of registry value from the Value Type field.
10 Click Next.
11 Complete the Target Assignment window to assign the task, and then click Next.
Targets window.
Working with scripts

Scripts are files that are used to automate repetitive tasks. They can be simple text files or more
complex written in a specific programming language. vWorkspace administrators can easily
assign scripts to clients using the Scripts option in the vWorkspace Management Console. Some
advantages include:
• Administrators do not need to have domain administrative rights.
• Editing the registry on each Session Host is not necessary.
• Modifying the usrlogon.cmd command script on each Session Host is not necessary.
• Use any Windows executable to write the script, such as bat, cmd, or exe.
• Increased flexibility and control over how the scripts are assigned.
The following considerations should be used when working with scripts on vWorkspace enabled
Session Hosts:
• It is best to use a single method to start the script. Troubleshooting can be difficult if
scripts are started using different methods.
vWorkspace 8.6.3
• The scripts used in the vWorkspace Management Console and scripts started using other
methods should not interfere with each other.
• The simplest form of a script should be used for the task. Do not write a complex script to
carry out a task that can be accomplished using a command line script.
NOTE: The scripts do not execute in interactive mode, so Pause, Echo, and any other
outputs are not displayed.
To assign a script
2 Expand the User Environment Management node, and then select Scripts.
3 Click the Toggle Client Assignment List Display icon on the information pane to change
the view.
• Click the + on the toolbar of the information pane.
• Right-click on the Scripts node, and then select New Script.
5 On the Welcome window of the Scripts wizard, click Next.
6 On the Script File window, enter the complete path and file name in Script File, or use
the ellipsis to browse to the script. Click Next.
The script must be on a network share. If you are typing a path name, it should resemble
the following, \\servername\sharename\script.bat.
7 Complete the Target Assignment window to assign the script, and then click Next.
Targets window.
Time Zones
A date and time stamp that is placed on opened files, messages, and scheduled meetings is
based upon an application location, which can be a Session Host in a time zone that is different
from the user. The Time Zones tool allows administrators to assign appropriate time zones to
users in a Session Host or VDI environment.
To Assign a Time Zone

2 Expand the User Environment Management node, and then select Time Zones.
3 On the information pane, click the Toggle Client Assignment List Display icon to change
the view, if needed.
4 Select the appropriate time zone from the alphabetical list.
• Right-click on the time zone and select Assign to.
• Add or remove targets in the Select Targets window.
6 Click OK.
vWorkspace 8.6.3
User policies
The User Policies tool provides a way for vWorkspace administrators to better control user
desktop environments. The following settings can be controlled with User Policies:
• Windows Components — Windows Explorer and the Help and Support Center
• Start Menu and Taskbar— Control Panel and Display
• System — Ctrl+Alt+Del options and Logon
The Properties option of User Policies allow administrators to select which policy template is
used to create new user policies. Two user policies are provided with vWorkspace, Default Admin
and Default User, which contain settings that are commonly implemented for administrators and
users. These policies can be modified and duplicated as appropriate. vWorkspace administrators
can also add new policy templates.
To view user policy properties

2 Expand the User Environment Management node.
3 Highlight User Policies, and do one of the following:
• Right-click, and then select Properties.
• Select Actions | User policies properties.
• Click on the Properties icon on the toolbar.
4 Select the policies that are to be used as the default templates for new user policies.
5 On the Templates window, click Policy Templates to import or remove policy templates.
To create user policies

2 Expand the User Environment Management node, and then click User Policies.
3 In the information pane, click on the Toggle Client Assignment List Display button to
change the display view, as appropriate.
4 Select + on the toolbar of the information pane, or right-click on User Policies, and then
select New User Policy.
5 On the Welcome window of the User Policy wizard, click Next.
6 On the Name window, Enter a Name for the new user policy, and then click Next.
7 On the Templates window, click Policy Templates. On the Policy Templates window,
select Import, Remove, or Rename policy templates. Click Close.
8 On the Templates window, click Next.
9 On the Policy Settings window, select the policy settings, and then click Next.
The boxes associated with each setting are three-way toggles; checked enables the
setting, unchecked disables the setting, gray indicates the setting is not influenced by
this policy.
10 Complete the Target Assignment window to assign the policy, and then click Next.
a Click the plus (+) sign to select targets, to open Select Targets window.
Targets window.
vWorkspace 8.6.3
11 On the Permissions window, specify permissions, if needed, and then click Finish.
To modify user policies

2 Expand the User Environment Management node, and then click User Policies.
3 On the information pane, click Toggle Client Assignment List Display to change the
display view, if needed.
4 Double-click the policy that is to be modified.
5 On the User Policy Properties window, change the entries.
6 Click Apply to make the change, and click OK to close the window.
User profiles
User Profiles is an alternative to roaming profiles. User Profiles eliminate potential profile
corruption and accelerate logon and logoff times. It does this by combining the use of a
mandatory profile with a custom persistence layer designed to preserve user profile settings
between sessions.
Wallpaper
A wallpaper can be assigned to vWorkspace clients by administrators. The wallpaper is used
when connecting to applications or desktops hosted from vWorkspace enabled Session Hosts and
VDI computers.
To assign wallpapers
2 Expand User Environment Management, and then select Wallpapers.
3 On the information pane, click on the Toggle Client Assignment List Display button to
change the display view, if needed.
4 To select a wallpaper, do one of the following:
• Right-click on the style, and then select Assign to.
• Click the Assign to icon (the icon with the blue circle and a white plus sign) from
the toolbar.
5 Add or remove targets in the Select Targets window.
6 Click OK.
To change wallpaper properties

2 Expand User Environment Management, and then select Wallpapers.
3 Right-click on the selected wallpaper and select Properties.
vWorkspace 8.6.3
4 Change the property as appropriate.
Table 91. Properties fields
Wallpaper File The full path and file name of the wallpaper.
NOTE: Each Session Host must have a copy of
the bitmapped image file for the defined
wallpapers. It needs to be in the same location
as the one displayed here.
Default Style Three options:
• Centered
• Tiled
• Stretched
Target Assignments A list of vWorkspace targets to whom the
wallpaper is assigned.
You can assign or unassign wallpaper from this
list.
Permissions The user or groups with permissions for this
wallpaper are specified here.
To add new wallpaper

2 Expand User Environment Management.
3 Right-click on the Wallpaper node, and then select New Wallpaper.
Or, select the green plus sign (+) from the toolbar.
4 On the Welcome window of the Wallpaper wizard, click Next.
5 On the General window, Enter the full path and file name for the wallpaper file and
select the Default Style, and then click Next.
6 Complete the Target Assignment window to assign the wallpaper, and then click Next.
a Click the plus (+) sign to open the Select Targets window.
Targets window.

The Secure Access service provides secure (remote) access to a vWorkspace deployment.
Requests sent to Web Access servers, vWorkspace Connection Brokers, and Workspace remote
hosts are SSL-encrypted at the client end point and sent through the corporate firewall on TCP
port 443 to the Secure Access service. When data is received by the Secure Access service, it is
decrypted and forwarded to the destination on the appropriate port. Outbound responses from
the vWorkspace resource pass back through the Secure Access service and are encrypted and
forwarded to the client web browser or vWorkspace Connector, depending on the proxy.
TIP: Connections to Web Access can be direct, (not through the Web Interface Proxy)
and require a separate SSL certificate.
vWorkspace 8.6.3
The Secure Access service applet allows the management of three separate proxies. Each proxy
secures communication to a separate vWorkspace component.
• RDP Proxy. Allows users on a public network, like the Internet, to connect
to virtual desktops or Remote Desktop Session Hosts that are managed by
vWorkspace and located on a private network. The connection to this proxy
is always SSL encrypted.
• Web Interface Proxy. Allows users on a public network to connect to Web
Access through the Secure Access service. The connection to this proxy is
always SSL encrypted.
• Connection Broker Proxy. Allows users on a public network to connect to a
vWorkspace Connection Broker that is located on a private network. The
connection to this proxy is always SSL encrypted.
Secure Access service certificate best practices

The following are suggested best practices for your Secure Access service certificate.
• The certificate should be an RSA (1024) certificate, not an AES certificate. (4096-bit
certificates have been successfully tested.)
• You should have a private key that corresponds to the certificate.
• On the Certificate Properties window, General tab, Server Authentication should be listed
and selected.
To configure the Secure Access service

1 From the Windows Control Panel, open the vWorkspace Secure Access service applet.
2 On the vWorkspace Secure Access service Properties window, specify the connection
properties for each proxy as necessary.
Table 92. Proxies tab fields
Proxies tab fields Description

RDP Proxy
Local IP Address Enables SSL encryption of RDP session traffic
between the vWorkspace Connector and
vWorkspace enabled Remote Desktop Session Hosts
and virtual desktops.
The IP address for the vWorkspace Secure Access
service for inbound requests is selected from the
list.
Local Port The TCP port number to be used for SSL encryption
of RDP session traffic.
Default is 443.
NOTE: If Microsoft IIS exists on the Secure Access
service, the port 443 might already be in use.
Require vWorkspace Connection When enabled, a vWorkspace Connection broker in
Broker authentication the farm validates the connecting user before
sending connection information to the user’s access
device.
vWorkspace 8.6.3

IP List Click this button to manage your IPs.
To use Forced Broker Authentication, all connection
brokers must be accessible from the Secure Access
service. Use the following fields to add and test the
connection brokers.
Host Name. Enter the name of the host and click
Get IP to resolve the host name to the IP using the
existing DNS server.
Add. Add a new IP.
Remove. Removes the selected IP from the list.
Test. Validates the selected IP.
Close. Returns you to the Secure Access service
Properties window.
Certificate Name Selects the web server certificate that is to be used
by the Secure Access service for inbound SSL-
encrypted RDP session traffic.
NOTE: Only certificates installed in the Windows
computer store are recognized.
Web Interface Proxy
Local IP Address Enables secure web browser traffic between the
vWorkspace Connector and the Web Access web
server.
The IP address for the Secure Access service for
inbound Web Access SSL requests is selected from
the list.
Local Port The TCP port number to be used for SSL encryption
of the Web Access session traffic.
Default is 443.
Destination Host(s) The Secure Access service forwards requests
through the IP address, host name, or FQDN of the
Web Access web server. Use commas to separate
entries.
Destination Port The TCP port number that the web server listens
on.
Default is 80.
Enable SSL Decrypts and then forwards packets.
Unselect this check box, and the packet is sent
without being decrypted.
Used only if the Enable SSL check box is selected.
vWorkspace 8.6.3

Connection Brokers Proxy
Local IP Address Indicates secure traffic between the vWorkspace
Connector and the Connection Broker servers.
The IP address for the Secure Access service for
inbound Connection Broker SSL requests is selected
from the list.
Local Port The TCP port number for SSL encryption of
Connection Broker traffic.
Default is 443.
Destination Host(s) The Secure Access service forwards requests
through the IP address, host name, or FQDN of the
Connection Broker server. Use commas to separate
entries.
Destination Port The TCP port number that the Connection Broker
servers listen on.
Default is 80.
Enable SSL If this check box is selected, the Secure Access
service decrypts inbound SSL packets before
forwarding them to the Connection Broker servers.
If this check box is not selected the Secure Access
service does not encrypt SSL packets for inbound
Connection Broker servers.
This field is only for use if the Enable SSL check box
is selected.
3 Click the Options tab and specify the options parameters.

Table 93. Options tab fields
Options tab fields Description
Connections Settings
Inactivity Timeout (minutes) The amount of time a session can be inactive before
the Secure Access service terminates it.
Default is 0 (no time out).
Server Logging
vWorkspace 8.6.3
Table 93. Options tab fields
Options tab fields Description

Enable to Trace logging to the When selected, logging for troubleshooting is
specified file enabled.
The name and location for this file are entered into
the text box. You can also use Browse.
Log files have a maximum size of 10 MB. Once the
maximum is reached, a new log file will be
generated appended with the date and time. Thus,
when not troubleshooting, logging should be
disabled.
Create certificate Click this button if you want to create a self-signed
certificate or learn how to create a public
certificate.
See To create a self-signed certificate for details.
4 Click OK to save your changes and close the window.
To create a self-signed certificate

1 From the Windows Control Panel, open the Secure Access service applet.
2 On the Secure Access service Properties window, click Create Certificate to display the
Self signed certificate tool dialog box.
3 Select the Self-signed certificate button.
4 Enter a Fully qualified domain name.
5 Enter the date range that the certificate is valid.
6 Enter a friendly name.
7 Click the Create SSC button to create the certificate.
8 On the Success dialog box, click OK.
9 Click Export to file, select a location, click Open and then OK.
10 On the Self signed certificate tool window, click OK.
TIP: If you want to create a public certificate, click the Public Certificate button,
and then click the link to access a Knowledge Base article, which provides
detailed information.
Connection Broker authentication

The Secure Access service included in vWorkspace 7.6 introduced a mode called Connection
Broker Authentication. This mode offers a higher level of security. Static PIT files (PIT files that
are re-used) cannot be used to connect to vWorkspace sessions if you enable Connection Broker
authentication.
On new installations of vWorkspace 7.6 and later the Secure Access service role has Connection
Broker authentication enabled by default. Upgrades from previous versions of the Secure Access
service will prompt whether Connection Broker authentication should be enabled or disabled.
Connection Broker authentication can be enabled or disabled at any time from the Secure Access
Service Configuration dialog box of the Secure Access service server.
To use Connection Broker Authentication the computer running the Secure Access service must
be able to resolve the host names of the connection broker computers.
When a vWorkspace Connector that does not support Connection Broker authentication attempts
to establish a session the Secure Access service will log the event in the Windows Event Viewer.
vWorkspace 8.6.3
Disabling the Nagle Algorithm
The Nagle Algorithm places controls on packet delivery by limiting the sending of partial TCP
packets. While useful in may scenarios, this can cause performance issues for Secure Access
service when used in conjunction with delayed acknowledgments. The Nagle algorithm is
disabled by default during installation. This setting can be reversed by modifying the following
registry key on the Secure Access service server.
HKLM\SOFTWARE\Provision Networks\Secure-IT
DisableNagle REG_DWORD (0=nagle enabled, 1=nagle disabled (default))
Secure Access service deployment options

The following deployment options discussed in this section are:
• Configuring Secure Access service for Web Access
• Configuring Secure Access service for vWorkspace Connector for Windows
• Configuring Secure Access service for vWorkspace Connector for Windows and Web Access
Configuring Secure Access service for Web Access

Web Access acts as a web-based portal to a vWorkspace environment. Web Access validates
vWorkspace users, through successful authentication to Active Directory by way of the
vWorkspace broker, and directs vWorkspace Connectors to the appropriate virtual desktop.
To use Web Access in conjunction with the Secure Access service, Web Access must be configured
properly.
To configure the Secure Access service for Web Access

Complete the following steps to configure vWorkspace Web Access to use vWorkspace Secure
Access service:
1 From the vWorkspace Management Console, Web Access node, double-click the website
you want to configure. The Web Access Site Properties dialog box is displayed.
2 Select the Default Rule link on the left side of the page. The Default Rules control the
default connections for clients connecting to a vWorkspace environment through Web
Access.
3 Select the vWorkspace Secure Access service option.
4 Select Custom Rules Settings to display the Custom Rules dialog box.
You can use the custom rules if you need to create exceptions to the default settings. For
example Web Access can be used to connect from inside the company on a LAN/private
network as well as by users who connect from outside of the company over a public
network, like the Internet.
Users connecting over a public network should use the vWorkspace Secure Access service
to ensure maximum security, but those connecting from inside the company might not
need that level of security and could connect directly to a virtual desktop/RD session
host.
To connect directly to a virtual desktop or RD session host and override the Default
Address Translation, the Custom Rules section needs to be set to Normal Address, and
the network subnet of the excepted client end points needs to be entered into the Client
Address Prefix list.
This is done by entering the subnet and clicking Add. The network subnet notation needs
to end with a . (dot). The custom address translation setting would override the default
vWorkspace 8.6.3
setting of Secure Access service. As demonstrated below, all connections would be routed
to the Secure Access service unless the client prefix is equal to 10.24.
5 Click Secure Access service to define the Secure Access service settings.
Table 94. Secure Access service fields
Field Description
Enable Secure Access service Select to specify your Secure Access service server.
Secure Server Enter the external, fully qualified domain name
(FQDN) of your Secure Access service server.
This setting controls the vWorkspace Secure Access
service addressing for Web Access.
Port number Enter the port number for your Secure Access
service server.
Address Enter the local, internal address of your Secure
Access service server, and then click Add.
Additional addresses may be added if there are
multiple servers implementing your Secure Access
service in a cluster.
External URL Enter the external URL that is used to connect
remote users to Web Access.
Typically, this is the Secure Access service FQDN
with an https:// prefix.
Internal URL Enter the internal URL that is used to connect
internal users to Web Access.
Typically, this is the internal IP address of your Web
Access server with an http:// prefix.
Web Access URL (internal users) If the URL is different than the external users, this
enter the proper link for Internal Users.
6 Click OK to save your settings.
Configuring Secure Access service for vWorkspace

Connector for Windows
This configuration is used when a secure single point of entry is needed for users connecting
from external networks, but the connections are managed by vWorkspace Connector for
Windows, rather than Web Access. In this scenario, the vWorkspace Connection Broker proxy and
the RDP proxy are the two Secure Access service proxies enabled.
The Secure Access service is the only access point to the vWorkspace infrastructure. Remote
clients gain access to the system using a single FQDN. Only one firewall access rule is required to
permit inbound connections to the Secure Access service on TCP port 443.
NOTE: A valid 128-bit SSL certificate must be installed on the Secure Access service.
The Secure Access service, if situated in the DMZ, may require additional firewall rules to allow
the Secure Access service to communicate with the Connection Brokers and the virtual desktops
on the internal network.
To configure vWorkspace Secure Access service for vWorkspace Connector for

Windows
1 Use the following path to access the applet:
Control Panel | vWorkspace Secure Access service
vWorkspace 8.6.3
2 Complete the RDP Proxy section as follows:
a Select Local IP Address, and then select an IP address from the list.
b Enter the Local Port.
c Click the Lock icon to select the web server certificate used by the Secure Access
service for inbound SSL-encrypted RDP session traffic.
Only certificates installed in the Windows computer store are recognized.
3 Complete the Connection Broker Proxy section as follows:
a Select Local IP Address, and then select an IP address from the list.
b Enter the Local Port.
c Enter the IP address, host name, or FQDN of the Web Access web server that the
Secure Access service forwards requests. Use commas to separate entries.
d Click the Lock icon to select the web server certificate used by the Secure Access
service for inbound SSL-encrypted RDP session traffic.
Only certificates installed in the Windows computer store are recognized.
NOTE: Both the RDP and the Connection Broker proxies can share the same IP address
and TCP port.
4 From the vWorkspace Connector for Windows Interface at the client end point do the
following,
a Configure a connection using vWorkspace Connector for Windows | Manage
Connections.
b In the Server List on the Connectivity tab, enter the FQDN of the Connection
Broker proxy.
c Select Enable RDP over SSL/TLS, and then enter the FQDN of the RDP proxy in the
SSL Gateway Server field.
Configuring Secure Access service for vWorkspace

Connector for Windows and Web Access
This option describes a setup where the vWorkspace Connector is accessed by vWorkspace
Connector for Windows and Web Access.
The Secure Access service and Web Access, if situated in the DMZ, require additional firewall
rules to permit the Secure Access service to communicate with the virtual desktops and the
Connection Broker, and for Web Access to communicate with the Connection Broker.
CAUTION: If you are using Secure Access service in conjunction with Web Access, you must
specify both the internal and external Web Access URL’s on the Firewall/SSL
VPN section of the Web Access Management console. See Using Web Access for
more information.
There are two ways to configure the use of the vWorkspace Connector for Windows and Web
Access.
One option allows all three proxies to share the same IP address and SSL certificate, but the Web
Access and the Connection Broker proxies have different TCP ports. This allows the Secure
Access service to distinguish HTTP connections going to Web Access from HTTP connections going
to the Connection Broker.
A second option is for all three proxies to use the same TCP port, but the Connection Broker has
a different IP address and SSL certificate.
vWorkspace 8.6.3
To configure vWorkspace Connector for Windows and Web Access
1 Use the following path to access the applet:
Windows Control Panel | vWorkspace Secure Access service
2 To configure using the same IP address and SSL certificate:
a In the RDP Proxy, Web Access Proxy, and Connection Broker Proxy fields, enter
the same IP address.
b Enter the same Local Port for RDP Proxy and Web Access Proxy, and a different
Local Port for the Connection Broker Proxy.
3 Complete the other fields and then click Apply to make the changes without closing the
window. Or click OK to make the changes and close the window.
a Configure a connection using vWorkspace Connector for Windows | Manage
Connections.
b In the Server List on the Connectivity tab, enter the FQDN of the Connection
Broker proxy
c Select Enable RDP over SSL/TLS, and then enter the FQDN of the RDP proxy in the
SSL Gateway Server field, and then click OK.
NOTE: Both proxies may share the same FQDN, but the Connection Broker proxy is set
to a different TCP port.
4 To configure using the same TCP port:

a In the RDP Proxy, Web Access Proxy, and Connection Broker Proxy fields, enter
the same TCP Port number.
b Complete the other fields and then click OK.
c Configure a connection using vWorkspace Connector for Windows | Manage
Connections.
d In the Server List, enter the FQDN of the Connection Broker proxy.
e In the SSL Gateway Server field, enter the FQDN of the RDP Proxy.
f Click OK.
NOTE: The RDP and Web Access proxies can share the same IP Address, TCP Port, and
Certificate Name. The Connection Broker Proxy is bound to a different IP
Address and Certificate Name.
Using Web Access

vWorkspace Web Access is a web application for vWorkspace environments that enables users to
retrieve their list of allowed applications and desktops using a web browser. One or more Web
Access servers, configured to communicate with an environment, must be available to use the
Web Access browser interface.
No client side configuration is needed; users simply start their Internet browser and enter the
address of the Web Access server. After successful authentication, the user’s published desktops
and applications display in the web browser. A vWorkspace Connector must be installed, and
personalization settings of the Internet browser can be configured.
Web Access tools

Web Access includes tools that allow you to configure a Web Access web site. The Web Access
Site Manager (WASM) interfaces with Microsoft Internet Information Services (IIS) to create and
prepare IIS web sites for Web Access.
vWorkspace 8.6.3
Web Access Site Manager
The vWorkspace Web Access Site Manager (WASM) allows you to generate multiple Web Access
sites.
Web Access is an ASP.Net application that installs as a virtual directory within an IIS default web
site. You can initially create the Web Access site during installation or by using the WASM. An IIS
virtual directory is created with the proper folder structure to host a Web Access site. However,
the new site has no configuration. You must create a Web Access configuration in the
vWorkspace Management Console and export it to the Web Access site.
One Web Access server can host multiple Web Access sites. Each site provides an interface to a
separate vWorkspace environment. The WASM can be used to aggregate multiple Web Access
sites into a federated site. A federated site provides a hyperlinked list of Web Access sites to the
user.
To create a new Web Access site

The WASM allows you to view, create, edit, and delete vWorkspace Web Access sites. After you
create a Web Access site, you can use the vWorkspace Management Console to configure settings
for the site and push the configuration to the Web Access web site.
1 Start the Web Access Site Manager from the Start menu of the Web Access server.
2 On the Web Access Site Manager window, click New.
3 On the New Web Access Site window, enter a Friendly Name and Virtual Directory Name.
• Friendly Name. Enter the name that will be displayed in the vWorkspace
Management Console.
• Virtual Directory Name. Enter the name of the virtual directory used to access
the Web Access site.
The Virtual Directory Name cannot be edited after the Web Access site has been
created. The site must be deleted and a new one created.
4 Click Finish to complete the process.
5 After completing a new Web Access site, complete an update to the web server with the
site configuration. See Updating a Web Access site for more information.
After the site is created it can be edited or deleted from this interface.
Web Access node

vWorkspace Web Access is managed from the Web Access node in the vWorkspace Management
Console. The Web Access node allows you to define multiple Web Access sites for separate
vWorkspace environments. You can also set up Web Access properties such as Website
Information, Firewall/Secure Access service, and Experience settings.
These settings are similar to settings in a vWorkspace Connector. However, with Web Access, the
configuration is being defined centrally rather than on each client access device.
Web Access configuration

After the Web Access site has been created, either during installation or with the Web Access
Site Manager (WASM), the properties of the Web Access site are managed through the
vWorkspace Management Console.
To create or modify a Web Access configuration

1 In the vWorkspace Management Console, click the Web Access node. The Web Access Site
Properties window is displayed.
vWorkspace 8.6.3
2 Create or modify a website:
• To create a new website, click Actions | New Website. On the Welcome page,
click Next. On the Connection Properties step, specify the Display Name and URL
path used to connect to the new Web Access site. You can create multiple sites.
• To modify a website, select the website you want to modify and click Properties.
3 Set up the Firewall/secure access service step, which are used to inform the Workspace
Connector how to communicate with the vWorkspace environment when a connection is
attempted.
Table 95. Firewall/Secure Access service properties
Firewall/Secure Access service

Description
Properties
Default Rule: • Internal Address. Use this setting for clients that are
Set up the default addressing type on the corporate SSL or VPN or on the internal
that should be used when accessing network, or when using a third-party SSL gateway
remote sessions. This default setting configured outside of vWorkspace.
applies to all connecting clients, • Alternate Address. Use this setting for clients that
unless specifically overridden by access RDSH sessions through a firewall that
custom addressing rules. implements network translation (NAT) to the RDSH
servers.
• vWorkspace Secure Access service. Use this setting
when clients will be accessing RDSH or VDI sessions
through the vWorkspace Secure Access service.
Custom Rules Addressing Types:
Set up exceptions to the default • Internal. Web Access refers the connecting access
addressing rule. Any client address device to make a direct connection to the remote
that does not match a custom rule, RDP host.
access remote sessions using the • Alternate. Web Access refers the connecting access
default rule. Custom Rules can be device to make a connection to the remote RDP host
used to specify an addressing type and using the configured alternate address associated
an associated IP address specification with the RDP host (RDSH only).
that is added to the Custom Address
• Secure Access service. Web Access refers the
Rules list. Any client IP address or
connecting access device to make a connection to the
outside interface address of a firewall
remote RDP host using the Secure Access service.
or proxy server that matches the rule
uses the corresponding addressing
type.
Secure Access service: Web Access uses the information in this setting to direct a
Define the path to the Secure Access connecting device to Secure Access service. The typically
service. port number for a Secure Access service is 443.
Advanced Settings: • Enable NAT for firewall traversal. This is helpful when
Specify the advanced Web Access your Web Access server and Secure Access service are
settings. separated by a NAT enabled firewall.
Proxy Server: Proxy Server options:

Specify proxy server information for • Do not use a proxy server (This is the default setting.)
Web Access. Web Access can be • Use default from the system Internet settings
configured to inform vWorkspace
• Enter an address manually. Select this option and
Connectors which proxy server to use
then use the Proxy Server field to specify the address.
when connecting to a vWorkspace
environment. Generally, proxy server
settings are used for internal offices,
where the vWorkspace Web Access
server is in a DMZ and the internal
office is using a proxy server to
connect.
vWorkspace 8.6.3
4 Set up the Domain/Login settings. These settings define what access control methods are
used when authenticating connecting users. The Domain setting must be defined in order
for authentication to the farm to succeed. The other Domain/Login settings are optional
and can be used to further secure access to your vWorkspace environment..
Table 96. Domain/Login properties
Domain/Login Properties Description

User Domains Specify the user domain settings.
A Web Access site passes user credentials to a vWorkspace
Connection Broker for authentication and validation. The
vWorkspace Connection Broker must belong to a Microsoft
Active Directory domain for this to work successfully. The
User Domains settings can be used to prepopulate the user
domain field, and authenticate the user account across
multiple domains.
NOTE: vWorkspace allows the use of User Principal Names
(UPN) during logon. For example, someone@lswidgets.com
Password Management Specify password management settings. Configure a Web
Access site to leverage Password Management Service.
Multiple password management servers can be specified and
must be associated with a domain defined in the User
Domains setting.
NOTE: If more than one Password Management Server is
listed in the Password management servers field, users are
prompted for which server to use to change their password
Credentials Pass-Through To use this setting with Microsoft Internet Explorer, you must
Allows the use of locally cached or configure the following before enabling this feature:
Kerberos domain credentials to login • Enable Integrated Windows Authentication must be
to a vWorkspace environment. This is disabled (unchecked) in Advanced Internet Options of
helpful when the user is connecting to Internet Explorer, and the Microsoft IIS web server
a vWorkspace environment from a must be a member of a domain in the Active
client access device that is a member Directory forest containing the user’s account.
of a trusted domain. • Web Access site needs to be added to the list in both
Trusted Sites and Local Intranet.
NOTE: Credentials pass-through is not supported in the
vWorkspace Connector for Java.
NOTE: If you are using Mozilla Firefox and credentials pass-
through, you must configure Firefox to use Integrated
Windows authentication. See To configure Firefox to use
integrated Windows on page 205.
Two-Factor Authentication Allows for the integration of a two factor authentication
product such as Secure Computing PremierAccess or using
RADIUS to communicate with other authentication solutions
such as Quest Defender or RSA ACE/Server.
vWorkspace 8.6.3
Table 96. Domain/Login properties
Domain/Login Properties Description

Anonymous Login Use this setting to enable anonymous login for this site.
Auto-Launch The Auto-launch options are:
When a user logs onto a vWorkspace • Do not automatically launch an application
environment, a managed application • Single Application
can be launched automatically rather
• Specified Application
than having the user select the
application.
If you are using the Application Auto-
Launch option with Web Access and
Internet Explorer 7, 8, 9 and 10, end
users must add the Web Access URL to
the Trusted Sites list at the following
path: Internet Explorer | Tools |
Internet Options | Security | Trusted
Sites.
Then, from the Trusted Sites settings,
click Custom level, and select Enable
for the following options:
Downloads | Automatic prompting for
file downloads
Downloads | File download
5 Set up the Connectors and Downloads. This is a group of settings that define the
availability of the vWorkspace Connector and other files for download from the Web
Access user interface.
NOTE: To install the vWorkspace Connector for Windows you must have administrative
rights on the device where the Connector is to be installed.
Table 97. Downloads/Connectors
Connectors/Downloads Properties Description

vWorkspace Connectors Specify the options for displaying and launching applications
from WebAccess.
See Specifying vWorkspace Connector options on page 205
for detailed information about these settings.
Download Settings Specify whether you want to display a downloads page and
how to link tot he downloads page.
Custom Downloads Allows for the addition of custom download links to the
download page. This is helpful if a resource is needed to
allow connections to a vWorkspace environment, such as a
root SSL certificate for a private certificate authority.
6 Set up the Experience settings. These settings control Microsoft or RDP virtual channels,
such as Desktop Composition and Graphics Acceleration.
vWorkspace 8.6.3
Some settings display two tabs. The Default Settings tab provides the configuration of the
specific category unless the properties of a connection are set to override. The User
Overrides tab defines which values can be overridden by the user.
Table 98. Experience settings
Experience setting Description

Default Settings
Local Resources Specify sound, keyboard and local device settings. Each of
the Local Resources settings can be set to allow user
override by enabling Allow users to override the default local
resource settings on the User Overrides tab and selecting the
override options to present to the user in the Web Access
client.
Remote Audio Playback
• Play on the end user’s computer (this is the typical
setting)
• Do not play
• Play on the remote computer - this is useful when
audio is being redirected using vWorkspace USB
Redirection.
Apply Windows key combinations
• On the end user’s computer (default setting)
• On the remote computer
• On the end user’s computer only when using full
screen
Devices and resources
• Serial Ports. Select if users need access to devices
attached to serial ports on their physical device
• Printers. Select if users need to print to autocreated
access device printers using native print drivers.
• Clipboard
• Microphone. Select if users need to redirect the local
computer microphone when connecting to the virtual
workspace.
• Smart Cards. Select if users are required to log on to
their session using a Smart Card attached to their
physical device.
• Universal Printers. Select if users need to print by
autocreated access device printers using the Print
driver.
• USB Devices. Select if users need to make use of USB
devices when connected to the virtual workspace.
• More. Click the More button to specify disk drives or
other supported PnP devices.
• Disk Drives. Allows you to individually select drives.
vWorkspace 8.6.3
Table 98. Experience settings
Experience setting Description

Performance Settings Control the following aspects of a user connection.
• Connection Speed. Defines which of the following
performance options are enabled. For example, if
LAN is selected, all of the performance options listed
under Connection speed are selected. If High-speed
broadband is selected, only Desktop composition,
Persistent bitmap caching, and Visual styles are
selected.
• Optimizations. Enable optimizations automatically
when logged into the remote computer.
• Session options. Supports the feature to reconnect
sessions after they have dropped.
Display Settings Provide control of the display configuration.
• Display Configuration. Sets the default screen
resolution for users when connecting to a remote
host.
NOTE: Screen resolution only applies when connected to a
seamless windowed application.
• Color. Specify the color depth of the remote session.
• Other Settings.
• Display connection bar when in full screen mode
• Pin connection bar
• Enable Smart Sizing. Resizes the remote sessions
screen resolution to fit the resolution of the client
access device when a connection is made to a
disconnected session on a remote host.
• Display remote applications seamlessly on remote
desktop. Enables the remote session screen size and
color depth to match the settings of the client access
device, when connecting to a managed application
User Overrides tab To allow users to override default settings, select the
corresponding option on the User Overrides tab.
7 Set up the Browser Interface settings, and then click Apply. The Browser Interface
settings define the appearance of the Web Access client interface. The Web Access client
interface can be executed in Internet Explorer, Mozilla Firefox, or Google Chrome.
Table 99. Browser Interface settings
Browser Interface Settings Description

Messages Allow for the modification of the messages that users see in
the Web Access client interface.
Layout Controls how application icons are displayed in the Web
Access client Interface. Each of the parameters in Layout
can be set to allow user override by enabling Allow users to
override the default local resource settings on the User
Overrides tab and selecting the override options to present
to the user in the Web Access client interface.
Themes Allow the colors and images in the Web Access client
interface to be customized. The Header Image and Logon
Image can both be replaced with custom images.
vWorkspace 8.6.3
Table 99. Browser Interface settings
Browser Interface Settings Description

Other Settings Groups several miscellaneous settings.
Additional Farms Can be used to aggregate the application sets of multiple
environments.
To configure Firefox to use integrated Windows

If you are using Mozilla Firefox and credentials pass-through, you must configure Firefox to use
Integrated Windows authentication by completing the following steps:
1 Open Firefox.
2 Type about:config in the address bar.
3 Type network.automatic in the filter box after the Config page loads.
4 Modify network.automatic-ntlm-auth.trusted-uris by double-clicking the row, and enter
www.mydomain.com.
Multiple URLs must be separated by comas.
Specifying vWorkspace Connector options

The vWorkspace Connectors feature allows you to determine how application icons are displayed
and how applications and desktops are launched when a user starts vWorkspace from Web
Access.
IMPORTANT: The recommended Connector is selected by default for each operating system.
To specify the options for displaying and launching applications from Web Access
1 From the vWorkspace Management Console, select the Web Access node.
2 Select the name of a Website and click Properties. The Web Access Site Properties
window is displayed.
3 Select the Workspace Connectors step to display the vWorkspace Connectors window.
4 Select the tab of the operating system (Windows, Mac, iOS, Android, Linux or Chrome OS)
that you want to configure. The settings for the selected operating system will apply
when a user launches WebAccess from that operating system.
5 Select one of the following to define how to launch the applications and desktop remote
sessions. Select one of the following options:
• Native Connector Application. Provides the best user experience. Must be
installed on the user’s device.
• HTML5 Connector. Provides low user experience, but does not need to be
installed.
• Java Connector. Java Runtime must be installed on the user’s device.
• Chrome Connector. Must be installed on the user’s device.
• Immediately redirect users to the native Connector application. Select this
option to display and launch applications and desktops using the native Connector.
Table 100. Advantages of each Connector

vWorkspace Connector Needs to be installed Full Featured OS-Specific
Native Yes Yes Yes
HTML5 No No No
vWorkspace 8.6.3
vWorkspace Connector Needs to be installed Full Featured OS-Specific
Java No (Requires Java) Yes No
Chrome Yes No Noa
a. Supports only Windows, Mac and Chrome operating systems (not iOS, Android or Linux).
6 If you want to disable automatic detection, select the Disable automatic detection of
vWorkspace native Connector applications for this website button.
Updating a Web Access site

After a Website Configuration is created (see Specifying vWorkspace Connector options), you can
use the Update Site settings to push the Website configuration to a Web Access site. The Site
Manager utility is used to generate the site structure and the Update website utility is used to
create the Web Access site’s configuration. The configuration can be pushed to the site using the
Update website utility or exported to an XML file, WebSettings.xml, which can then be manually
copied into the config folder of the specific Web Access site.
To update a Web Access site

1 From the vWorkspace Management Console, select the Web Access node.
2 Right-click on the web site that needs to be updated, and select Update Website.
NOTE: This dialog box also appears at the end of the New Website Wizard when Finish is clicked.
3 Select one of the following options:

• Contact the Web Access site directly and update its configuration. If this option is
selected, a prompt appears asking for the path to the Web Access site.
• Save the configuration to a file and manually update the Web Access Site. If this
option is selected, a prompt appears asking for the location to save the
WebSettings.xml file. The .xml file needs to be copied to the following location:
\Inetpub\wwwroot\<virtual folder name>\Config
4 Click OK.
To delete a Web Access site

1 From the vWorkspace Management Console, expand the Web Access node.
2 Right-click on the web site that needs to be deleted, and select Delete Website.
3 Click Yes.
vWorkspace Connector packages

vWorkspace Connectors are supported on multiple end point devices. The vWorkspace Connector
for Windows installation packages are included with a Web Access installation and can be made
available for download from the vWorkspace Web Access User page.
When the Connector is selected in the Downloads settings in Web Access, a version and location
can be specified. In this case, it checks whether the vWorkspace Connector for Windows is
installed on the end point device. If the specified version or later version is not installed, it
attempts to automatically download and install the Connector from the specified location using
Microsoft ActiveX.
NOTE: ActiveX must be enabled on the user’s browser for client installation checking
to work. This feature is not supported for browsers other than Internet Explorer.
vWorkspace 8.6.3
Other vWorkspace Connectors
vWorkspace Web Access supports Linux, Mac, Android, and iOS as client Connectors. These, must
be installed through their respective methods. Web Access cannot be automatically installed on
these platforms.
Web Access Integration

Web Access integrates with several third-party products to extend secure access and
productivity for a vWorkspace environment. Web Access provides integration for the following
products.
• Juniper Secure Access
• F5 Firepass
• SharePoint integration
• Cisco ASA
• Microsoft Unified Access Gateway integration
• Citrix XenApp and XenDesktop
Juniper Secure Access

Web Access and Juniper Networks Secure Access SSL VPN can be integrated to be used as a single
sign-on solution by using custom headers created by the Juniper Secure Access Central Manager.
Prerequisites
• Secure Access Device must be running at least System Version 7.0 R0.
• Authentication Realm must be set up and configured for the correct Active Directory
domain.
• SSO License must be installed on the Administrator’s device, if SSO is required.
• Integration with WSAM and Network Connect.
• vWorkspace Web Access server configured properly.
To configure Secure Access

1 Create a new role, for example, vWorkspace_Users.
2 Select the SAM tab.
3 Click Add Application, and then select PNTSC, which is the vWorkspace connection tool.
4 Do the following on the Custom Application window, and then click Save Changes.
a Enter a Name.
b Add a Description, if needed.
c Enter Filename as pntsc.exe.
5 If you are using a vWorkspace Connector or vWorkspace Connector for Windows through
the administrator’s device, do the following on the Custom Application window, and then
click Save Changes.
a Enter a Name.
c Enter the Filename as pntsc32.exe.
vWorkspace 8.6.3
6 Do the following on the Allowed Server window, and then click Save Changes.
a Enter a Name.
c Add a Server. In this example, a subnet is used for the vWorkspace environment.
d Set the appropriate ports, such as 80 (Web), 8080 (Broker), and 3389 (Terminal
Services).
7 From the vWorkspace Role, select the SAM tab, and then select Options.
8 On the Options settings window, complete the following:
a Select Windows SAM.
b Set appropriate Windows SAM options for this role.
c Click Save Changes.
9 Select the Web tab, and create a bookmark for the vWorkspace Web Access server.
http://server/<identity>
10 From the main system menu, go to Users | Resource Policies | Secure Application
Manager Policies.
See Step 12 if SSO is required.
11 Add a new policy or modify an existing policy by doing the following:
a Enter a Name for the policy.
b Enter Resources to which this WSAM role is allowed to access. For example,
10.1.1.1/25:80,8080,3389.
c Select Policy applies to SELECTED roles.
d Select the vWorkspace role created previously.
e Select Allow socket access.
f Click Save Changes.
12 If SSO is required, from the main menu screen go to Resource Policies |Headers/Cookies
Policies, select the SSO tab, and then select Headers/Cookies.
13 Select New Policy on the Headers/Cookies Policies window, and do the following:
a Enter a Name.
b Add a description, if needed.
c Enter a Resource, which is the direct link to the vWorkspace Web Access site.
http://server/<identity>
a Set the role to which it applies.
b Select Append headers as defined below.
c Create three headers to write during the request process:
• PN_Username<User>
• PN_Password<Password>
• PN_Domain NetBIOS Domain
F5 Firepass
Web Access and F5 FirePass SSL VPN can be integrated to be used as a single sign-on solution by
creating tunnels in the FirePass Administrator Console.
vWorkspace 8.6.3
Prerequisites for F5 FirePass
• Must use version 7.0.0. or later.
• Must be configured for the appropriate Active Directory domain.
• vWorkspace Web Access server must be installed and configured properly, if configuring
connections to a Web Access server.
F5 Firepass can be configured to tunnel connections to a vWorkspace Connection Broker or a
vWorkspace Web Access server.
To tunnel to a connection broker

1 Select Application Access.
2 Do the following in the Application Tunnels tab.
a Click Add New Favorite.
b Select Favorite as the Type.
c Enter a Name.
d Enter servers, IPs, and networks along with ports for the vWorkspace
infrastructure in the Allow List.
Ports are 8080 (Broker default) and 3389 (Terminal Services).
e Click Add Favorite.
3 Click Add New Dynamic Tunnel, and do the following:
a Enter a Name for the application, such as PNTSC or vWorkspace Connector for
Windows.
b Set the proper path to the pntsc.exe file.
c Note that x86 and x64 versions are different paths and locations.
d Click Update. Repeat the process for each application required.
To tunnel to Web Access

1 Select the Web Application Tunnels tab.
2 Click Add New Favorite, and do the following:
a Select Favorite as the Type.
b Enter a Name.
c Enter the following URL.
http://server/<identity>/Login/F5
d Enter URL variables.
This is used if SSO is wanted to automatically sign in to the Web Access server with the
credentials which were used to login to the F% FirePass device.
For example: uname=%username%&pass=%password%&dom= <NetBIOS_Domain_Name>
e Select Use POST for URL variables.
f Enter servers, IPs, and networks along ports for the vWorkspace infrastructure in
the Allow list.
g Enter information into the Endpoint Protection required field, as appropriate.
h Click Add New.
i Repeat this process for each Web Access server.
vWorkspace 8.6.3
SharePoint integration
vWorkspace Web Access can be integrated with a SharePoint server, allowing users to access Web
Access from a link on the SharePoint site.
Microsoft SharePoint 2010 was used in the following step process.
To integrate Web Access and SharePoint

1 Log in to SharePoint.
2 Navigate to the project or directory where Web Access is to be integrated.
3 Select Site Actions | More Options.
4 Open Web Part Page.
5 Do the following on the New Web Part Page window, and then click Create.
a Enter a Name for the Web Part Page.
b Select Full Page, Vertical as the Layout Template.
c Select the Document Library where the page is to be saved.
6 Click Add a Web Part.
7 Do the following on the next screen, and then click Add.
a Select Media and Content in the Categories section.
b Select Page Viewer in the Web Parts section.
c Select Full Page in the About the Web Part section.
8 Click Open the tool pane in the Page Viewer section, and then do the following.
a In the Link field, enter the URL to the Web Access site.
Click on Test Link to verify the link.
b Expand the Appearance node and enter the Height and Width for the page.
c Click Apply.
9 Click Stop Editing.
The Web Access site is now integrated and available to users at the specified location.
Cisco ASA
Web Access and Cisco ASA can be integrated to be used as a secure connection solution.
Prerequisites for Cisco ASA

• Cisco ASA version 8.2(5) or later.
• ASA Connection Profile and Policies need to be set up appropriately.
• Authentication for Active Directory needs to be completed, if you are going to use SSO.
• The vWorkspace Web Access server needs to be configured and working correctly.
To configure Cisco ASA

1 On the top menu of the Cisco ASDM configuration utility, select Configuration.
2 From the left pane, select the Remote Access VPN menu.
3 From the Remote Access VPN window left pane, expand Clientless SSL VPN Access.
4 Expand Portal, and then select Bookmarks.
vWorkspace 8.6.3
5 Select Add or Edit on the Edit Bookmark List window.
6 Complete the following:
a Enter a Bookmark Title.
b Enter the URL.
If using SSO to access the vWorkspace page, append /Login/gateway/ to the link.
If you are not using SSO, remove /Login/gateway from the URL and set the Advanced
Options to Get.
c Enter a Subtitle, if needed.
d Select a Thumbnail, if needed.
e Unselect the Allow the users to bookmark the link option.
7 Expand Portal, and then select Smart Tunnels from the Remote Access VPN window.
8 On the Edit Smart Tunnel List window, select Add or Edit.
9 Add or edit a PNTSC item with the following information, and then click OK:
a Application ID: PNTSC
b OS: Windows
c Process Name: pntsc.exe
d Hash: optional (it is not needed).
10 Add a Connector for Windows item with the following information, and then click OK:
a Application ID: vWorkspace Connector for Windows
b OS: Windows
c Process Name: pnap32.exe
d Hash: optional (it is not needed).
11 From the Remote Access VPN window, select the Group Policies option.
12 Click Edit to edit a group policy item with the following information:
a Name: DNPolicy
b Type: Internal
c Tunneling Protocol: webvpn,svc
13 On the Edit Internal Group Policy window, select Portal, and do the following:
a In the Smart Tunnel section, select vWorkspace_Client from the drop-down list.
b Select Auto Start.
c Click OK.
Microsoft Unified Access Gateway integration

vWorkspace Web Access can be integrated with Microsoft Unified Access Gateway (UAG) to be
used as a secure connection solution.
Prerequisites for Microsoft UAG

• Microsoft UAG needs to be version MS UAG SP1 or higher.
• At least one Authentication Server needs to be configured.
• vWorkspace Web Access server needs to be configured and working correctly.
vWorkspace 8.6.3
Microsoft UAG folders
The following folders are used for the integration. These folders are located under \Program
Files\Microsoft Unified Access Gateway.
• Custom Update. These folders are where the vWorkspace integration files are placed.
• Trunk_Name. This folder is the name of the Trunk created within the Microsoft UAG
console. For example, if the name of your trunk is MyPortal, this folder would be called
myportal.
NOTE: • Check the folder locations to make sure there are no other files residing
in the locations.
• Prior to applying the vWorkspace integration templates, backup and
export the current working configuration.
Files used in integration

The following files are used in the Microsoft UAG for the vWorkspace integration.
Table 101. Files used in integration
File Name Description

TRUNK1PostPostValidate.inc This file is used to set three internal Microsoft UAG variables
for use with the vWorkspace Web Access integration. This
file is used for single sign-on integration.
WhlFiltAppWrap_HTTPS.xml This file is used to post new headers to the Web Access
portal page for single sign-on.
This file also has a rewrite that hides the Logoff link in the
Web Access site.
WhlFiltSecureRemote_HTTPS.xml This file removes a Microsoft UAG variable when browsing
the Web Access site, which is required for the integration.
This file only removes said variable when browsing a
vWorkspace Web Access site and no other websites.
WizardDefaultParam.ini This file integrates vWorkspace into the Microsoft UAG Step-
by-Step Wizard.
SSLVPNTemplates.xml This file has rules in place for vWorkspace integration with
Microsoft UAG.
File locations
There should be no files in the above locations. If files exist already, contact technical support to
provide you with assistance of modifying the existing files to append the changes to them.
Table 102. File locations for integration
File name location

Root \Program Files\Microsoft Unified Access
Gateway\von\
TRUNK1PostPostValidate.inc \InternalSite\inc\CustomUpdate
WhlFiltAppWrap_HTTPS.xml \conf\WebSites\<TRUNK_NAME>\conf\
CustomUpdate
WhlFiltSecureRemote_HTTPS.xml \conf\WEbSites\<TRUNK_NAME>\conf\
CustomUpdate
WizardDefaultParam.ini \conf\WizardDefaults\CustomUpdate
SSLVPNTemplates.xml \conf\CustomUpdate
If files do not exist in the current locations, copy the files to the appropriate locations and save
the configuration. Complete the following steps:
vWorkspace 8.6.3
1 Run IISRESET.EXE.
2 Activate the configuration.
3 Ensure activation completed fully by checking the UAG Activation Monitor.
Continue with the next steps to complete access to vWorkspace Connector for Windows, Remote
Desktop Connection, or Web Access.
To configure for PNTSC and vWorkspace Connector for Windows

1 Launch the Microsoft UAG management console.
2 Select the trunk to be configured.
3 From the Applications node click Add.
4 On the Add Application Wizard, click Next.
5 On Step 1-Select Application of the Add Application Wizard, select vWorkspace Connector
for Windows from the Client/server and legacy drop-down, and then click Next.
6 On Step 2-Configure Application, enter an application name, and then click Next.
7 On Step 3-Select Endpoint Policies window, click Next.
8 On Step 4 - Configure Server Settings window, enter the vWorkspace Servers and Broker
Servers by IP/Name or subnet, and then click Next.
9 On Step 5 - Portal Link window click Next.
10 On Step 6 - Authorization window, set Users and groups by clicking Add, and then click
Next.
11 Click Finish to complete the wizard.
To configure Web Access integration

1 Launch the Microsoft UAG management console.
2 Select the Trunk that is to be configured.
3 In the Applications node, click Add.
4 On the Add Application Wizard window, click Next.
5 On the Step 1 - Select Application window select vWorkspace Web Access <version>
option in the Browser-embedded drop-down, and then click Next.
6 On Step 4 - Deploying an Application window, click Next.
7 On Step 5 - Web Servers window, do the following, and then click Next:
a Enter the address of the Web Access server.
b Enter the paths as the create site.
8 On Step 6 - Authentication window, click Next.
9 On Step 7 window, enter the subnet, server names, or IP addresses of the vWorkspace
server which users connect through Web Access, and then click Next.
10 On Step 8 - Portal Link window, click Next.
11 On Step 9 - Authorization window, click Next.
12 Click Finish to complete the Add Application Wizard window.
13 After the configuration is completed, save and activate the changes. Use the Microsoft
UAG Activation Monitor utility to ensure the Activation has finished.
vWorkspace 8.6.3
Citrix XenApp and XenDesktop
Web Access can send user credentials to both vWorkspace Connection Brokers and servers
running the Citrix Program Neighborhood Agent (pnagent). Web Access takes the data returned
from each solution and aggregates it into the user’s application set. Therefore, the user can
access one interface to connect to presentation hosts from either solution seamlessly.
Web Access can integrate with the following Citrix products:
• XenApp 5.0
• Presentation Server 4.0 and 4.5
• XenDesktop 4.0, 5.0 and 5.5
To achieve this, a PNagent server must be configured to communicate with a Citrix environment
and the Web Access server must be configured with the URL of the PNagent server.
vWorkspace 8.6.3
6
Managing the User Experience
• About the user experience

• Experience Optimizations
• USB devices
• User profile management
• Configuring user profiles
• Load balancing
• vWorkspace Password Reset service
About the user experience

vWorkspace includes features that help you provide users connected to virtual workspace with
an experience similar to that of working on a physical desktop environment. You can optimize
and manage the end-user experience by providing seamless, reliable access to resources such as
network drives, registry keys, user profiles and printers.
Connections to Remote Desktop Session Hosts and virtual computers hosted on Hyper-V
hypervisors can be grouped and managed so that the workload is equally distributed and
balanced across the group of servers.
Experience Optimizations
The Experience Optimizations address the user experience challenges of presenting applications
and desktops using a remote display protocol by providing seamless, reliable, high-performance
enhancements to Microsoft’s Remote Desktop Protocol.
The following features are available through the Experience Optimizations:
• WAN Acceleration. Accelerates RDP traffic on wide area networks (WANs). This provides
for an improved user experience by providing faster RDP screen responses and improved
performance of all optimization features.
• Universal Printing. A single-driver printing solution that satisfies both client-side and
network printing needs in a vWorkspace environment.
• Enhanced Audio. Enables support for applications that require the use of a microphone,
such as dictation, collaboration, and certain Voice Over Internet Protocol (VOIP)
applications such as Office Communicator and Lync.
• Graphics Acceleration. Reduces bandwidth consumption and dramatically improves the
user experience, making RDP usable over WAN connections.
• USB Redirection. Universal USB enables the use of virtually any USB connected device,
such as PDAs, local printers, scanners, cameras, and headsets to be used in conjunction
with VDI.
These features can be assigned to Users, Groups, OU, Client IP, Client Device Name or Advanced
boolean targets.
vWorkspace 8.6.3
Setting up optimizations
The optimization features are installed by deploying Virtual Desktop Extensions to a virtual
desktop or by installing the TS/RDSH role on a Remote Desktop Session Host. In the vWorkspace
Management Console, administrators can manage which features govern a user’s connection to
the virtual workspace.
The optimizations settings can be found at the following locations. The options are set to
disabled by default.
Using the vWorkspace Remote Desktop connection
• Experience tab | Optimizations section
Using vWorkspace vWorkspace Connector for Windows
• Actions | Manage Connections | Experience section
Using Web Access
• Properties of a Web Site| Experience section
WAN Acceleration
WAN Acceleration accelerates RDP traffic on wide area networks (WANs). This provides for an
improved user experience by providing faster RDP screen responses and improved performance
of all Optimizations features.
WAN Acceleration is specifically designed for users on WAN links with modest to high round trip
latency. For example, the typical amount of latency that is common when connecting from the
United States to Europe. WAN Acceleration is also effective on WAN links that are much closer,
such as a VPN link from a home to a corporate office in the same city.
WAN Acceleration operates transparently to the users. WAN Acceleration is enabled with RDP
pass-through mode configured by default.
WAN Acceleration latency effectiveness

WAN Acceleration is not recommended for LAN traffic or WAN traffic with low latency. The
recommended network conditions listed below are guidelines. Network type, packet loss, and
other factors impact the effective useful range of WAN Acceleration.
• Typical effective round trip latency: 30ms-400ms.
NOTE: WAN Acceleration is designed to improve performance of screen updates and
other Optimization features. WAN Acceleration is not designed to reduce the
effect of keystroke latency (echo) commonly observed on WAN links that exceed
200ms of latency.
WAN Acceleration firewall considerations

The WAN Acceleration server listens on TCP port 3389 (RDP port). No additional configuration is
needed, as the Windows firewall port 3389 is automatically opened. This functionality is enabled
by RDP Pass-Through mode.
To configure WAN Acceleration for a computer group or an individual computer

1 Select Location | <Name of the location>, and then click the computer group or the
individual computer.
2 Select Experience Optimization.
vWorkspace 8.6.3
3 Configure the settings..
Table 103. WAN Acceleration settings
Experience Optimization
Description
setting
Enable support for bandwidth Enable or disable RDP compression.
optimization appliances
Enable support for WAN Enable or disable support for WAN Acceleration.
Acceleration
Enable RDP pass-through mode Selecting this option allows WAN Acceleration to
use the RDP port, eliminating the need to configure
additional firewall settings.
WAN Acceleration Port Number Enter a port number to be used, if other than the
default number, which is 3389.
NOTE: Any changes made to the default options
require a reboot. The reboot is automatic in a VDI
environment, but requires a manual reboot in an RD
Session Host environment.
Maximum number of Enter a maximum number of connections.
connections
4 Any changes made to the default options require a reboot. The reboot is automatic in a
VDI environment, but requires a manual reboot in an RD Session Host environment
To set the WAN Acceleration connection policy

There is also a Connection Policy for WAN Acceleration in the vWorkspace Management Console.
Connection policies are used to define automatic device connection and optimizations when
users log on to the virtual workspace. Connection policies can be configured, and assignments
and permissions defined. Connection policies are set to Undefined by default.
You can also enable WAN Acceleration from the following settings:
• vWorkspace Connector for Windows, User Experience settings
• vWorkspace Web Access, Performance settings
• vWorkspace Client Remote Desktop Connection, Experience settings
NOTE: Settings defined in Connection Policies override any settings made in
vWorkspace Connector for Windows and Web Access.
A configurable client side timeout is available for WAN Acceleration. The default timeout is 5
seconds, if no other value is stated in the registry entry.
The registry value that needs to be set is:
HKLM\Software\Provision Networks\PNDNACLI
"ConnectTimeout" (REG_DWORD) = "15"
Universal Printing
vWorkspace Universal Printing is a single-driver printing solution that satisfies both client-side
and network printing needs in a vWorkspace environment. In addition to its driver-independent
approach to printing, benefits include:
• Bandwidth usage control and intelligent font embedding (only fonts that do not exist on
the client are embedded inside the print stream).
• Excellent print quality and reliability.
vWorkspace 8.6.3
• Support for native printer features, such as bins, paper sizes, margins, stapling and
watermarks.
• Client-less support for LAN connected print servers and for remote site print servers in
situated and distributed environments.
Universal Printing components

The primary Universal Printing components are:
• Universal Print driver
• Universal Network print services
Universal Print driver

The Universal Print driver enables driver-independent printing to client side, corporate, and
remote site printers in a distributed enterprise.
The Universal Printing solution encompasses two main scenarios:
• Universal Network print services
• Universal Printer auto-creation
Both scenarios enable users to access printers without the need for printer specific drivers to be
installed in the virtual workspace.
Universal Network print services

Shared printers can be created for vWorkspace users when logging on to a virtual workspace
using Windows native print drivers, the vWorkspace Universal Print driver, or both. When
installed on a traditional Windows network print server, printers can be created and shared using
the Universal Print driver. These printers have the same features as the original network printer.
After the Universal Printers have been created and shared, they can be assigned to the
appropriate clients using the vWorkspace Management Console or scripted logic. Printer
connections are established successfully because the same driver is also installed on the servers.
Because the connections are to the Universal Print driver printers and not the original printers,
the manufacturer-specific print drivers do not need to be present on the session host, leaving
them driver-free.
When the Universal Print driver does not support a specialized feature of a printer, or the driver
is not compatible with a print device, printers can be assigned to clients using the native driver
for that printing device.
Universal Printer creation is independent of the access device; it does not require the
vWorkspace Connector to support Universal Printing.
Creating shared Universal network printers for vWorkspace clients using the vWorkspace
Universal Print Driver involves the following items:
• Install vWorkspace Universal Print Server Role on to a Windows-based print servers.
• Install and share the desired printers on the Windows-based print servers as normal.
• Add the Windows based print servers as print servers using the Manage Network Printers
option on the vWorkspace Management Console.
• Select the printers to be defined as Universal printers using the Manage Universal
Printers option on the vWorkspace Management Console.
• Assign the printers to the appropriate vWorkspace targets from the vWorkspace
Management Console.
vWorkspace 8.6.3
Universal Printer auto-creation
The Universal Printer Auto-Creation option enables client side printers to be autocreated during
logon for each user session. For each client printer, Universal Printer autocreates and configures
a server-side printer, using the Universal Print driver, that has the same printer features as the
client printer.
Universal Printer auto-creation relies on a custom virtual channel driver to transfer the print job
from the server to the client. This mode of operation requires a vWorkspace Connector, that
supports the Universal print driver, to be installed on the client access device.
Administrators specify what types of client printers to autocreate, as well as allow users to
choose which printers to autocreate. The options for client printers that can be autocreated
include:
• Local printers
• Network printer connections
• Only the default printer
• All the printers and printer connections
Administrators can also configure several preferences and performance parameters including the
printer naming convention, print bandwidth upper limit, and compression options.
To enable the auto-creation of client printers, the following criteria must be met:
• A vWorkspace Connector that supports the Universal Printer driver must be installed on
the client access device.
• The Universal Printer option must be enabled on the client.
• At least one Auto-Creation option must be enabled in the client.
To print to an auto-created client printer, the user selects the Print command, and a list of
printers is presented to them. Print preview is also available by selecting Preview before printing
from the vWorkspace system tray icon.
Universal Printer properties

When the Terminal Server/RD Session Host is installed, you can use the Universal Printer
Properties to define the server’s print settings. Below is a description of the tabs and options
that are available.
vWorkspace 8.6.3
Table 104. Universal Printer Properties, General tab
Universal Printer Properties

Description
General tab
Print Data Format The options are PDF or EMF.
NOTE: EMF is a more robust printing mechanism.
Client Printer Auto-Creation • Auto-create default printer. Creates a printer
Options mapping only to the default printer on the client
device.
NOTE: By selecting the Auto-create default printer option,
any other Client Printer Auto-Creation options that are also
selected do not apply.
• Auto-create local printers. Creates a printer
mapping for all of the local printers defined on the
client device.
• Auto-create network printers. Creates a printer
mapping for every network printer defined on the
client device.
• Inherit auto-creation settings from client.
Autocreates printers based on the properties set on
the client device.
Client Printer Auto-Creation • Auto create only default printer synchronously.
Wait Mode Requires the mapping to the client’s default printer
to be completed before presenting the application or
desktop window to the user.
• Auto create all printers synchronously. Requires
every printer on the client device to be mapped
before presenting the application or desktop window
to the user.
This is the slowest method for login.
• Auto create all printers asynchronously. Allows the
presentation of the application or desktop window to
the user without requiring printer mappings to be
made first.
This allows for the fastest login.
Advanced Options • Auto-create printers with full permissions. Elevates
user permissions to Full Control for all mapped
printers. This is sometimes a requirement for printing
with certain legacy applications.
• Delete auto-created printers when sessions
disconnect. Causes all mapped printers to be deleted
from the server if a user’s session is disconnected.
Enabling this feature can improve the reliability of
printing in a multi-user environment.
• Synchronize default printer on client and server.
Enables synchronizing the settings of the default
printer in the user’s Session Host session with those of
the default printer of the session running on the
client device.
vWorkspace 8.6.3
Universal Printer Properties, Compression tab
Controls when and to what extent compression is applied to the printer output. The options on
the window depend on the Print Data Format, either PDF or EMF, that is chosen on the General
tab.
Table 105. Compression tab (EMF format)

Description
Compression Tab
EMF Format Data Compression controls the level of compression used for
text.
JPEG Image Compression controls the level of compression
used for graphic images.
Options include:
• No compression
• Minimum (best speed and quality)
• Low
• Medium
• High
• Maximum (smallest size)
Table 106. Compression tab (PDF format)

Description
Compression Tab
PDF Format Black & White Image Compression controls the algorithm
used for compressing text and graphics. Algorithm choices
include:
• Default compression
• CCITT Fax Group 4
Color Image Compression controls the algorithm and quality
level of compression used for color images. Selectable
Algorithm options are:
• Automatic (recommended)
• Default compression
• 256 compression
• JPEG compression
Selectable options for Quality Level are:
• Maximum (largest file size)
• High
• Medium
• Low
• Minimum (smallest file size)
Remove duplicate images, if selected, embeds the image
once inside the print stream for the purpose of minimizing
the use of bandwidth. For example, an image of a logo
embedded in a header would only be embedded once.
vWorkspace 8.6.3
Universal Printer Properties, Naming tab
The Naming tab is used to control which client printer naming convention to use when naming
autocreated client printers.
Table 107. Universal Printer Properties, Naming tab
Universal Printer Properties naming

Description
Tab
Client Printer Naming Convention • Printer Name [Session #]
• Printer Name [Client Name:Session #]
• Printer Name [User Name:Session #]
• [Client Name:Session #] Printer Name
• [User Name:Session #] Printer Name
• Printer Name [User Name]
• [User Name] Printer Name
Use UNC names to client network Select if you want to use UNC names.
printers
Universal Printer Properties, Bandwidth tab

Use the bandwidth control slider to limit the amount of bandwidth consumed for printing
purposes with each user session on the RD Session Host. The range is between 5 Kbps and 2 Mbps.
Universal Printer Properties, Logging tab

The settings on this tab are used to enable trace logging for Universal Printer drivers and the
Print Monitor. If options are enabled, use the input boxes to enter or browse to identify the path
and file name of log files.
This tab is primarily used by technical support to assist in troubleshooting.
Universal Printer Properties, LicenseTab

The License tab is only used when the Universal Printer driver has been purchased on a per
server basis and is not using concurrent user licensing modes.
Universal Printer Properties, Server Farm tab

The Server Farm tab is used to propagate property settings to other servers within your server
environment.
Table 108. Universal Printer Properties, Server Farm tab
Universal Printer
Properties Server Farm Description
Tab
Server Types Filters the display of servers by type. Available types
include:
• Terminal Servers
• vWorkspace Servers
• Custom Server List
Propagate When selected, the universal printer settings are propagated
to all the servers that were selected.
vWorkspace 8.6.3
Universal Printer Properties, Notification tab
The Notification tab is used when administrators want a customized print notification to be sent
to user sessions.
Table 109. Universal Printer Properties, Notification tab

Description
Notification Tab
Display notification below when Select this option for a printing notification
printing message.
Title Type the text that is to be displayed on the title bar
of the message window.
Message Type the text for the print notification message.
Universal Printer Properties, PDF Publisher

This option enables the creation of a PDF file of any print job that is sent to the PDF printer.
Table 110. Universal Printer Properties, PDF Publisher
Universal Printer Properties PDF

Description
Publisher
Create the PDF Publisher on this When selected, autocreates a PDF Publisher printer
server for each user session on this server.
Show PDF Publisher menu items When selected, a PDF publisher options menu item
on client is added to the Universal Printers section of the
PNTray context menu.
Universal Printer Client Properties

The Universal Printer client properties are installed as part of the client installation and is used
to set various printing options. The Universal Printer client properties apply only to autocreated
client printers, and not to printers assigned by the vWorkspace Management Console.
The Universal Printer client properties can be accessed in Control Panel, from the Start option,
or from the vWorkspace System tray as a context menu option after a session to an RD Session
Host has been established.
The tabs and options available on the Universal Print window are described below.
Table 111. Universal Print Client Properties
Universal Print General Tab

Auto-Create Options • Auto-create default printer only. Creates a
printer mapping to the default printer only,
on the client device.
• Auto-create local printers. Creates a
printer mapping for each local printer
defined on the client device.
• Auto-create network printers. Creates a
printer mapping for each network printer
defined on the client device.
• Auto-create specified printers only.
Creates only the printers selected by the
user.
vWorkspace 8.6.3
Table 111. Universal Print Client Properties
Performance Options • Use Printer Properties Cache. Allows
printer properties from previous sessions to
be cached and used, instead of having to
reenumerate them each time a session is set
up.
Universal Print Bandwidth Tab
Enables the user to specify the amount of bandwidth available for printing.
Universal Print Logging Tab
Enables logging for troubleshooting purposes.
Universal print services

Print services enhance the user’s print experience and simplifies printer manageability in
vWorkspace environments by automatically creating shared network printer mappings
throughout a distributed enterprise, using a single print driver.
The following printing options are available for installation on Windows based print servers:
• Universal Print Server role. Installs on existing dedicated Windows network print
servers. Eliminates the need of installing large numbers of drivers on Remote Desktop
Session Hosts and managed computers by using a single universal print driver to create
shared network printers. Also improves network print performance by taking advantage
of the highly efficient compression engine found in the vWorkspace Print Driver.
• Universal Print Remote Site Relay role. Installs on remote site and branch office
network print servers and works in conjunction with the Print Server Role to extend the
benefits of the printing architecture across the enterprise. Includes encryption,
compression, and bandwidth usage control for high performance and security.
These options enable file servers to efficiently store user profile settings and enhance the
accessibility to corporate and remote site print servers through auto-creating and sharing
network printers using a single print driver.
Universal Print Server role

The Universal Print Server Role option is used to install the Universal Print driver onto Microsoft
Windows print servers. This option eliminates the need for brand specific print drivers to be
installed onto RD Session Host and managed computers; instead using a single print driver.
This option can also be used along with the Remote Site Relay Role to further optimize the
printing process.
To set up Universal printers

2 Expand the User Environment Management node, and then click Printers.
3 On the toolbar of the information pane, click Manage Universal Printers (the computer
icon with the letter U).
4 On the Manage Universal Printers window, click Add.
5 On the Add Print Server window, type the NetBIOS name or IP address of the Windows
print server or browse to it by using the ellipsis.
6 Below the Universal Printers section, click Add to select printers.
7 In the Select Network Printer window, browse to the Microsoft Windows Network and
select the printer or printers.
You can select printers shared from any Windows server, not just those with optimizations
installed on them.
vWorkspace 8.6.3
Use Ctrl to make multiple selections.
8 Click Close.
To add network printers

If a device or print feature is incompatible with Universal Printer, use the following steps to
configure autocreation of network printers using their native drivers.
3 On the toolbar of the information pane, click Manage Network Printers (the computer
icon with the letter N).
4 On the Manage Network Printers window, Print Server frame, click Add.
5 On the Add Print Server window, type the NetBIOS name of the Windows print server or
use the ellipsis to browse to it.
6 From the Print Servers list, select the desired server.
7 From the Shared Printers list, select each printer to be autocreated.
8 Click Close.
NOTE: Printers created using native Microsoft Windows print drivers are named using
the names that appear in the Printer and Faxes folder of the client device.
However, once they are added to the vWorkspace database, the name can be
changed.
To assign printers to targets

Universal printers and Network Printers must be assigned to vWorkspace clients before they can
be autocreated.
3 Select the desired server and click Toggle Client Assignment List Display to change the
layout.
4 From the list of Universal printers or Network printers, select a printer or printers.
You can select printers shared from any Windows server, not just those with Universal
Printers installed on them.
5 Use Assign to assign the printers to Targets.
6 Click OK to close the Select Targets window.
Remote site relay

Remote site relay is a WAN-optimized adaptation of the vWorkspace Network Print Services.
Organizations with geographically disbursed offices containing one or more local print servers
can use Remote Site Relay to allow their branch office users to access and print from server
based applications hosted at the central office.
Managed Service Providers (MSP) might also use this service to deliver bandwidth efficient
printing capabilities to their customers over private links, Internet, and VPN connections.
The advantages of using Remote Site Relay include:
• Clientless printing. The client software does not need to be installed on the remote
clients; only the Remote Site Relay role needs to be installed on the remote site print
servers.
• Bandwidth management. The print streams are sent over a WAN link at a preset rate,
specified in Kbps, to prevent a print job from consuming all the available bandwidth.
vWorkspace 8.6.3
• Size optimization. The print streams produce as small as 10 percent of the size of
conventional PCL or Postscript print jobs using techniques such as intelligent/partial font
embedding, duplicate image removal, and dynamic compression.
The process of deploying Remote Site Relay involves the following items:
• Install the Remote Site Relay role on the print servers at each remote site.
• Use the Remote Site Relay Control Panel applet to configure network communication
parameters and identify the printers that are to be available to vWorkspace targets when
connecting to a vWorkspace RD Session Host.
• Import the exported network printers from each remote site. Each imported printer is
created as a Universal printer and is shared from a designated print server.
• Assign the printers to the appropriate vWorkspace targets.
Mutual computer-level authentication can be configured using an assigned shared pass phrase.
When it is authenticated, the Remote Site Relay server and Universal Print Server can encrypt
the print data before it is passed across the WAN link, eliminating the requirement for complex
Windows or Kerberos trust relations and obtaining commercial server certificates.
Remote site relay can be configured to use any port that security administrators allow to be
open on the firewalls.
To configure Remote site relay

1 From the vWorkspace Connector for Windows, open the Remote Site Relay applet from
the Control Panel.
2 Complete the following information on the General tab.
Table 112. Remote Site Relay, General tab fields
Remote Site Relay Information

This section is used to configure the network communication protocol
and security used by Remote Site Relay on this server.
TCP Port Enter a port number.
Default is 82.
Secret Pass Phrase Enter a secret pass phrase for
mutual computer level
authentication when Use
Encryption is selected.
A maximum of 20 alphanumeric
characters is allowed.
Use Encryption Select for encryption between the
Remote Site Relay server and the
Universal printer server.
Bandwidth Control Select the maximum amount of
network bandwidth allowed for
passing print data to an exported
printer on the Remote Site Relay
server from another server.
The bandwidth limit is set on a per
exported printer basis, allowing
each printer to receive the
maximum bandwidth limit.
3 Complete the following information on the Export List tab.

a Select the printer or printers to be exported.
The list of printers that appear here are those that were installed
and shared on the Remote Site Relay server.
vWorkspace 8.6.3
b Select Properties to set printing preferences for each printer.
c Select the Use Printer Properties Cache check box, if needed.
4 Complete the Logging tab if you need to enable trace logging for troubleshooting.
5 Click OK.
NOTE: After making configuration changes using the Remote Site Relay Control Panel
applet, it may be necessary to restart the vWorkspace Remote Site Relay service
for the changes to be implemented.
Manage relay servers

After Remote Site Relay servers have been configured, their exported printers can be imported
into the vWorkspace infrastructure database. In addition to creating a database object
representing each printer, the import process also creates and shares a new printer using the
Universal printer driver on the designated print server.
To add Remote site relay servers

2 Expand the User Environment Management node, and then select Printers.
3 From the toolbar of the information pane, click the Manage Universal Printers icon.
4 On the Manage Universal Printers window, click Site Relay.
5 Select the Manage Relay Servers tab.
6 Click Add.
7 Enter the name or IP address of the Remote Site Relay server to be added or browse to
select it using the ellipsis, and then click OK.
8 On the Add Relay Server window, select Add new site, and then click OK.
9 On the Add Relay Server window, enter the name for the new site and then click OK.
10 Enter the two letter suffix to be used to identify the site, and then click OK.
11 Enter and confirm the secret Pass Phrase to be used for authentication to the Remote
Site Relay server, and then click OK.
12 Set the TCP Port number to the appropriate value.
13 Set the Bandwidth limit for printing.
The bandwidth value that is the lowest, either on the relay server or the print server, is
the value that is used.
14 Repeat Step 6 to Step 11 for each additional Remote Site Relay servers.
15 Click OK to complete the task.
To import remote printers

2 Expand the User Environment Management node, and then select Printers.
3 Click the Manage Universal Printers icon from the toolbar of the details window.
4 On the Manage Universal Printers window, click Site Relay.
5 Select the Import Remote Printers tab.
6 Select the Relay server that is to be used to import the Relay Sites and Relay Servers
listed.
7 Select the server from the list of Universal Print servers in which the imported printers
are to be created.
vWorkspace 8.6.3
8 Click Import Now to start the import process.
9 Review the message box confirming the import process has been initiated, and then click
OK.
10 To close the Remote Site Relay Servers window, click Close.
11 On the Manage Universal Printers window, click Close.
Maintaining printers in the Management Console

After printers have been added to the vWorkspace Management Console, you can change the
printer properties, assign printers to users, and view the printers by using the following path:
vWorkspace Management Console| User Environment Management | Printers
The Printers window in the details pane includes information such as:
• Listing of the network printers and Universal printers.
• Naming conventions for the printers are as follows:
• Universal printers are designated with a (U) after their name.
• Printer names that are relay site related appear with the administrator
designated two digit suffix.
• Printer properties for the printers can be viewed and edited by right-clicking on the
printer and selecting Properties.
To assign remote printers to clients

Printers imported from Remote Site Relay servers are assigned to vWorkspace targets in the same
manner as Universal Printers and Network Printers. Imported printers have the two letter remote
site suffix appended to their names.
2 Expand User Environment Management, and then click Printers.
3 Right-click on the printer in the navigation pane to which users are to be assigned, and
select Assign option.
4 Select the Targets for the assignment from the list, and then click OK.
You can multiselect by using the Ctrl button.

The properties for a Universal printer can be set by the vWorkspace administrator.
To view and edit Universal Printer properties

3 Right-click the printer from the list of Universal Printers.
4 Select Properties from the context menu to view and edit the properties.
5 On the General window, change the printer name, and then click Apply.
6 On the Data Format window, select PDF or EMF, and then click Apply.
7 On the Performance Options window, select the image compression options, and then
select Apply.
The options presented depend on the Print Data Format selected. For PDF format the
available options are:
vWorkspace 8.6.3
• B & W Image Compression
• Color Image Compression
• Color Image Quality Level
• Duplicate Images Removal
For EMF format, the available options are:
• Data Compression Level
• JPEG Image Compression Level
8 Change the Target assignments, as needed, and then click Apply.
9 Change permissions as needed, and then click Apply.
10 Click OK to complete the task and save changes.
Or, click Cancel to close without saving the changes.
Network Printer Properties

The properties for a Network printer can be set by the vWorkspace administrator.
To view and edit Network Printer properties

3 Right-click the printer from the list of Network Printers.
4 Select Properties from the context menu to view and edit the properties.
5 Change the Target assignments, as needed, and then click Apply.
6 Change permissions as needed, and then click Apply.
7 Click OK to complete the task and save changes.
Or, click Cancel to close without saving the changes.
Enhanced Audio
The Enhanced Audio feature enables users to redirect their audio devices to and hosted desktops
to use with applications involving dictation and for certain VOIP applications. These settings are
disabled by default.
Enhanced Audio is supported on the following:
• Microsoft Office Communicator
• Microsoft Lync (see Configuring the Microsoft Lync 2013 plug-in)
• Avaya Software
• Skype
Microphone sound quality is best with sufficient bandwidth, at least 25 to 30 Kbps, to support
the audio channels and round trip latency less than 250 milliseconds.
CAUTION:The Connection Policies Remote Computer Sound option overrides the setting
for Remote computer sound on the Local Resources window in the vWorkspace
Connector for Windows setup, as well as the Local Resource Settings window in
the Web Access preferences.
vWorkspace 8.6.3
Setting up Enhanced Audio
To set up Enhanced Audio from vWorkspace Connector for Windows
1 From vWorkspace Connector for Windows, select Manage Connections | Local
Resources.
2 Set the Remote audio option to Leave at Remote Computer.
NOTE: If you are using vWorkspace 8.0.1 or earlier, set the Remote Audio option to Bring to Local
Computer.
3 Enable the Microphone option.

4 Click OK.
To set up Enhanced Audio from Web Access

1 From the Management Console, click Web Access.
2 Select a Web Access site, and click Properties.
3 Select Local Resources.
4 Set the Remote audio playback option to Play on the remote computer.
NOTE: If you are using vWorkspace 8.0.1 or earlier, set the Remote audio playback option to Play on the
end-user’s computer.
5 Enable the Microphone option.

6 Click OK.
Configuring the Microsoft Lync 2013 plug-in

The Lync 2013 VDI Plug-in is an optimization component built by Microsoft for Lync 2013 in VDI. It
installs on a Windows client endpoint and provides pairing capabilities with vWorkspace virtual
desktops that optimizes the locally installed Lync 2013 client.
The plug-in provides point-to-point connectivity for functions such as desktop sharing, audio and
video calls. With this functionality it offloads the connection through the VDI computer host thus
reducing CPU, memory, IOPS, and network consumption from the VDI computer host.
To configure the Microsoft Lync 2013 plug-in

1 Ensure that no other Lync client is installed on the Connector computer.
2 Install the plug-in as instructed by Microsoft (see
http://www.microsoft.com/en-us/download/details.aspx?id=35457).
NOTE: vWorkspace is compatible both the 32 and 64-bit versions of the Lync VDI plug-in. However, the
bitness of the Lync VDI plug-in you install must match the local computer's operating system bitness.
3 Read the Lync plug-in from the following registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server
Client\Default\Addins\LyncVdiPluginLib]
"Name"="{DEDC9BA7-C55C-4a3b-965E-B08EAC50D504}"
4 Write the information from Step 3 into the following registry key:
For Windows x86 OS:
[HKEY_LOCAL_MACHINE\SOFTWARE\Provision Networks\Terminal Services
Client\Addins\LyncVdiPluginLib]
vWorkspace 8.6.3
For Windows x64 OS:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Provision Networks\Terminal Services
Client\Addins\LyncVdiPluginLib]
Flash Acceleration
Flash Acceleration allows flash content (such as Youtube) to be played on the client computer,
leveraging the resources of the client computer and providing an optimal user experience.
Adobe Flash Player must be installed on the server and client access device.
NOTE: The client Adobe Flash player version must match the version (major versions)
that is installed on the server.
If the versions do not match, then the flash content plays without Flash
Acceleration. Or, unexpected results may occur.
Flash Acceleration Version Compatibility

In vWorkspace 8.5, a new generation of Flash Acceleration was added called "Flash Acceleration
2". Flash Acceleration 2 provides support for more flash sites and better performance. In version
8.5 both Flash Acceleration and Flash Acceleration 2 are supported, therefore supporting legacy
client Connectors. Both have unique registry settings that allow for configuration of specific
features, that can be configured independently.
Flash Acceleration Registry Location

The registry settings are stored in the following registry paths:
Flash Acceleration
x86: [HKEY_LOCAL_computer\SOFTWARE\Provision Networks\Flash Redirection]
x64: [HKEY_LOCAL_computer\SOFTWARE\Wow6432Node\Provision Networks\Flash Redirection]
Flash Acceleration 2
x86: [HKEY_LOCAL_computer\SOFTWARE\Provision Networks\Flash Redirection 2]
x64: [HKEY_LOCAL_computer\SOFTWARE\Wow6432Node\Provision Networks\Flash Redirection 2]
Table 113. Flash Acceleration Settings
NAME LOCATION TYPE DEFAULT DESCRIPTION
Factory
defaults set at Blacklist of sites that are not redirected
BL Server REG_MULTI_SZ RTM and may using flash redirection. This is used for
vary with unsupported sites.
updates.
Factory Blacklist of sites that are not redirected

defaults set at using flash redirection. This is used for
BL_7.5 Server REG_MULTI_SZ RTM and may unsupported sites. This is used when client
vary with Connectors 7.5 and earlier are accessing a
updates. version 8 server or later.
Factory Blacklist of direct connect sites. Some
defaults set at websites that serve flash content do not
BL_monike REG_MULTI_SZ
Server RTM and may allow the client to access the content
r_dc
vary with directly, and the server must access the
updates. content.
vWorkspace 8.6.3
NAME LOCATION TYPE DEFAULT DESCRIPTION
To change the bandwidth, change the

0 = unlimited registry value by entering the maximum
bandwidth Server REG_DWORD
bandwidth bandwidth capacity (in KBps - Kilobytes per
second).
Flash Acceleration is recommended for low
and medium latency network connections.
For high latency networks, you can use a
0x78 (120) latency limit to disable Flash Acceleration,
maxRTT Server REG_DWORD 78h = 120ms and have Flash Acceleration fall back to
latency server-side rendering if the RDP8 protocol
is used. If RDP8 is not detected as the
protocol Flash Acceleration will continue to
redirect Flash content.
The client tries to first fetch Flash content
using the Internet connection on the client
device. This generally improves the end
DirectConn Client 1 = use Direct
REG_DWORD user experience, site compatibility and
ection & Server Connection
overall scalability. Disable this feature when
this behavior is not allowed due to local
firewall or other reasons.
0 = volume Some flash application use cases require

VolumeRed Client control is the client to have direct volume control of
REG_DWORD
irection & Server server side the flash content. The client setting
1 = client side overrides server setting.
Flash Acceleration setup

The following sections describe how to use Flash Acceleration.
To enable Flash Acceleration in vWorkspace Connector for Windows

1 Open the vWorkspace Connector for Windows.
2 Select Actions | Manage Connections to open the Farm Connections wizard.
3 On the Experience window, select Flash Acceleration in the Experience Optimized
Protocol section, and then click OK.
To set Flash Acceleration in Web Access

1 Open the Web Access Management Console.
2 Select a specific environment or all environments to which graphics acceleration is to be
enabled.
3 In the Experience settings section, select Performance.
4 Select Flash Acceleration, and then click Save Changes.
Graphics Acceleration
vWorkspace Graphics Acceleration adds additional compression to Microsoft’s Remote Desktop
Protocol (RDP) to dramatically reduce bandwidth consumption and improve end user experience,
making RDP usable over WAN connections. Graphic Acceleration can be assigned to Users,
Groups, OU, Client IP or Client Device Name.
Graphics Acceleration performs better with applications and documents that contain a high
degree of graphics, and may not perform as well with text based applications. It is
recommended that Graphics Acceleration be thoroughly tested with each application before
implementing in a production environment.
vWorkspace 8.6.3
Enabling this feature for specified applications ensures the benefits of this feature to the end
users.
Graphics Acceleration implementation

In this section provides procedures for implementing and using Graphics Acceleration. After
Graphics Acceleration is enabled on a managed application, you can set up connection policies
to enable or disable graphics acceleration.
Connection policies are defined from vWorkspace Management Console | User Environment
Management | Connection Policies.
The following are the available Connection Policies.
• User
• Group
• Organizational Unit
• Client IP/IP Range
• Client Name/Naming Convention
Graphics Acceleration registry settings

Below are two registry settings for Graphics Acceleration that can be used to set progressive
image display and compression quality that can be set per application.
Altering registry settings should only be completed by an administrator who understands these
types of settings. Your environment should be backed up prior to changing any registry setting.
HKLM\Software\Provision Networks\Image Acceleration
Progressive Image Display is disabled by default. 
ProgressiveUpdate (REG_DWORD): 0 disable progressive update, 1 enable
Jpeg Quality (REG_DWORD): Jpeg quality 20-100 [Note: this overrides Quality when present]
Jpeg Subsampling (REG_DWORD): 0 4:4:4, 1 4:1:1 (default), 2 4:2:2
Jpeg RGB (REB_DWORD): 1 using RGB instead YCbCr
ExcludedWindows: REG_MULTI-SZ (the window class names to be excluded in GA)
HKLM\Software\Provision Networks\Terminal Server

NOTE: Graphics Acceleration can be enabled or disabled and set compression quality per application.
HKLM\Software\Provision Networks\Image Acceleration\AppList\<executable name>

HKCU\Software\Provision Networks\Image Acceleration\AppList\<executable name>
Enabled (REG_DWORD): 1 Enable GA for this executable, 0 Disable GA
Jpeg Quality (REG_DWORD): compression quality (20-100)
NOTE: Graphics Acceleration checks the HKCU AppList first, if the executable is not on the list, it checks
the HKLM settings. If the executable is not on the HKLM AppList setting, Graphics Acceleration uses the
global setting, HKLM\Software\Provision Networks\Image Acceleration.
Graphics Acceleration setup

The following procedures describe how to use vWorkspace Graphics Acceleration.
• To enable Graphics Acceleration globally
• To disable Graphics Acceleration for an application
• To define connection policies
vWorkspace 8.6.3
• To enable Graphics Acceleration in vWorkspace Connector for Windows
• To set Graphics Acceleration in Web Access
To enable Graphics Acceleration globally

2 Right click Managed Applications, and then select Properties.
3 On the Graphics Acceleration window:
• Select Enabled.
• Select an image quality option.
4 Click Apply.
5 Click OK.
To disable Graphics Acceleration for an application

2 Select Managed Applications.
3 Right-click a managed application and select Properties to open the New Managed
Application window.
4 Select Graphics Acceleration, and set Graphics Acceleration to Disabled.
5 Click Apply to save the change.
6 Click OK.
To define connection policies

1 Open the vWorkspace Management Console and expand User Environment Management.
2 Right-click Connection Policies and select New Connection Policy.
3 On the Welcome window of the New Connection Policy wizard, click Next.
4 On the Name window, enter a name for the connection policy, and then click Next.
5 Define the Remote Computer Sound, and then click Next.
6 Specify the Local Devices settings, and then click Next.
7 Specify the Experience Optimizations settings, and then click Next.
8 On the Target Assignments window, assign users to this connection policy property, and
then click Next.
9 On the Permissions window, specify the permissions for this connection policy, and then
click Finish.
To enable Graphics Acceleration in vWorkspace Connector for Windows

2 from the Action menu, select Manage Connections.
3 On the Server Farm window, select Experience.
4 On the Experience window, select Graphics Acceleration, and then click OK.
To set Graphics Acceleration in Web Access

1 From Web Access, open the Management Console.
2 Select a specific farm or all farms to which graphics acceleration is to be enabled.
3 In the User Experience settings section, select Performance.
vWorkspace 8.6.3
4 Select Graphics Acceleration, and then click Save Changes.
USB devices
From headsets to mobile devices, USB devices are frequently used, but can sometimes be
problematic when used in a virtualized environment. USB device integration issues can be solved
with the vWorkspace features of USB Hub client and Load balancing.
USB Hub client

USB Hub Client enables the use of virtually any USB connected device, such as PDAs, local
printers, scanners, cameras, and headsets to be used in conjunction with VDI. Users can connect
multiple USB devices, and then decide which devices to share.
USB Redirection does not generally support Composite USB devices that include a mouse or
keyboard class device. A Composite USB device is a USB device that is not one entity, but two or
more, such as a keyboard with an integrated mouse or a scanner/printer/fax device. It is
important that you test all composite devices for vWorkspace compatibility.
USB Redirection is installed on managed computers as a component of Virtual Desktop Extensions
(PNTools).
The USB Hub client contains the following components:
• Client Applet
• System tray display
• Microsoft Windows Service component
To set up the USB Hub Client

1 From the Control Panel on the client device, open vWorkspace Virtual USB Hub Client.
2 On the Devices tab, select the devices that you want to share.
Table 114. USB Hub Client, Devices tab
Devices Tab
Share Makes the device available to the server. When a device is
shared, it is unavailable to the client computer.
Unshare Makes the device unavailable to the server, which makes it
available to the client computer.
Exclude Excludes this device from being shared.
See the Note in Auto-connect devices.
Unexclude Allows the device to automatically be shared.
Properties Displays the USB Device Properties window. The ability to add
an optional nickname for the device is included in the
properties.
Information on this window includes:
• Nickname
• Name
• Location
• Serial Number
• Information
• Status
vWorkspace 8.6.3
Table 114. USB Hub Client, Devices tab
Auto-share devices Allows the connected devices to automatically be shared
with the server.
NOTE: If a user is going to select this option and they are
using a USB keyboard or mouse, they need to confirm that
these devices have been excluded before selecting this check
box. The keyboard and mouse might not function locally on
the client while being shared.
Use Taskbar Icon Allows the system tray to be used.
3 Click the Advanced tab you want to enter advanced options.

Table 115. USB Hub Client, Advanced tab
Advanced Tab
Bandwidth Control Set the bandwidth control by moving the slider to
the threshold amount.
Compression Zip compression, and then do the following:
• Move the slider to set the minimum packet
size.
For example, if you set the compression to
1024 bytes, compression occurs only if the
amount is greater than 1024 bytes.
• Enter a number from one to ten in the
Settings field. The setting values are:
1 = best speed
10 = best compression
4 Click OK.
USB Redirection Client system tray

Select the USB Redirection icon to display the client system tray.
Devices are listed with their name, current status, and if they are shared (indicated with a check
mark) or excluded (indicated with an X).
To share a device using the system tray, click on it. To exclude a device using the system tray, use
Ctrl + click.
USB Redirection server

The USB Redirection server side contains the following components:
• USB Server properties
• System tray display
• Microsoft Windows Service component
vWorkspace 8.6.3
USB Server properties
You can use the following USB Server properties:
Table 116. USB Server properties fields
Connect Enables the device on the server.

Disconnect Disables the device on the server.
Exclude Excludes the device from being automatically connected.
See Auto-connect devices.
Unexclude Allows the device to be automatically connected.
Properties Displays the USB Device Properties window.
Auto-connect devices Allows devices to be automatically connected when they
are available to the server.
Use Taskbar Icon Allows the system tray to be used.
The Advanced tab on the USB Server properties allows you to set a priority for this service on
the server. The setting options are Normal, Low, or High, and the default setting is Normal.
USB Redirection Server System Tray

When the USB Redirection icon is selected, the server system tray becomes available.
Devices are listed with their name, current status, and if they are shared (indicated with a check
mark) or excluded (indicated with an X).
To share a device using the system tray, click on it. To exclude a device using the system tray, use
Ctrl + left-click.
USB Redirection server services

A Microsoft Windows Services option is available for the server side.
To manage USB devices

The USB Redirection software needs to be installed on the virtual desktop in addition to Virtual
Desktop Extensions.
1 Open the vWorkspace USB Redirection Client Control Panel applet.
As devices are plugged in, they display on the device list.
2 Highlight a device from the list and select one of the options.
If users are using a USB keyboard or mouse, prior to selecting the Auto-share devices
check box, they need to exclude those devices, If those devices are not excluded on the
list, they do not function on the client while being shared.
To auto-exclude a USB device

vWorkspace can be configured to auto-exclude any USB device.
1 Install this Client version on the user access device. This install can be completed as a
new installation, an upgrade from the previous Client version, or by uninstalling the
previous client version and installing this client version.
2 From the Control Panel, open the vWorkspace USB Redirection Client.
3 De-select the Auto-share devices check box so that devices are not autoshared.
4 Plug in the USB device that is to be autoexcluded. The device will be displayed in the list
of devices on the vWorkspace Virtual USB Redirection Client window.
vWorkspace 8.6.3
5 Select the device, and click Properties.
6 From the USB Device Properties window, you need the following information:
• VendorID
• ProductID
• Revision
7 Create the following key in the registry:
HKEY_LOCAL_computer\SOFTWARE\Quest Software, Inc.\Quest Software USB Virtual
Hub\Excluded USB Devices
8 Create a sub key with a unique name under the Excluded USB Devices key. This key name
can be any name.
9 In the Sub Key, create a value "HARDWAREID" of type REG_BINARY.
10 Enter the hardware identification information into this key in binary format.
You have the option to be more or less specific about the devices you want to auto
exclude. Entering only the VendorID excludes all devices with that VendorID, which may
exclude more devices than you want to exclude. Entering the VendorID, ProductID, and
Revision information from the USB device allows you to be very specific with the excluded
USB device.
The following table provides examples of a binary format:
Table 117. Binary format examples
USB Device Information Binary Format

VendorID: 0x04f2 f2 04
ProductID: 0x0112 12 01
Revision: 0x0103 03 01
For example, using the device information from the above table, the registry entries
might be:
Table 118. Example of registry entries
VendorID: f2 04
VendorID and f2 04 12 01
ProductID:
VendorID, ProductID, f2 04 12 01 03 01
and Revision:
11 After changing the registry key, unplug the device.

12 Select the Auto-share devices check box so that devices are autoshared.
13 Plug in the device.
The device should now be autoexcluded in the USB Redirection Client window.
Smart card USB redirection

You can redirect smart cards from a virtual desktop or RD Session Host session using USB
Redirection. This feature allows you to use a Smart Card for authentication inside a virtual
desktop rather than using it to log on.
The .dll to use this feature is packaged with Virtual Desktop Extensions in the
\Windows\System32 folder. In order to use this feature, you need to add to the following registry
value a list of the executables that are to be redirected. You can manually install this feature if
desired.
vWorkspace 8.6.3
To add the registry value
The installation steps are as follows:
1 Locate PNSCHOOK.DLL in the \windows\system32 directory.
2 Add PNSCHOOK.DLL to the AppInit_DLLs key.
3 Configure applications to hook in SCHookList registry value; that is, in the pathname
HKLM\Software\Provision Networks\Provision-IT. Locate a REG_SZ value called SCHookList
(which is a comma-delimited list of EXEs to be hooked).
Multiple Monitor support

To set up multiple monitors in vWorkspace Connector for Windows
2 Click the Display option.
3 On the Display window, select Span multiple monitors when in full screen mode.
4 Click Next and Finish to save your selection.
To set up multiple monitors in Web Access

1 Open Web Access.
2 Click the Preferences tab.
3 On the Display window, select Span multiple monitors when in full screen mode.
4 Click Save Changes.
TIP: Since resolutions can vary by screen, a started application in non-maximized,
normal Windows mode can open into a nonviewable area of the screen (when
using Monitor Spanning). If you are using applications where you cannot
maximize or resize the window, your monitors should be set to the same
resolution.
User profile management

vWorkspace user profiles is an alternative to roaming profiles. User Profiles eliminate potential
profile corruption and accelerate logon and logoff times by combining the use of a mandatory
profile with a custom persistence layer designed to preserve user profile settings between
sessions.
User Profiles may be temporarily used in conjunction with existing local and roaming profiles
until the relevant data has been completely exported from these profiles. Users whose data has
been exported can then be reconfigured to use a mandatory profile.
NOTE: The User Profiles feature does not support roaming between different
generations of Microsoft Windows. For example, a user cannot roam from an
Microsoft Windows 7 computer, and then log on to a Microsoft Windows 10
computer and have their profile follow them, as Windows 7 and Windows 10 are
not the same generation.
There are three components of User Profiles:

• User Profile Storage Server. This option is part of the Peripheral Server Extensions and is
only available if RD Session Host is not detected.
• User Profile (agent for Session Hosts). This option installs on Session Hosts. When it is
installed, it creates the User Profile Agent service.
vWorkspace 8.6.3
• User Profile (agent for desktops). This option installs on Desktops, using Virtual Desktop
Extensions (PNTools). See Virtual Desktop Extensions (VDE) for more information.
User profiles workflow

The following describes how user profiles simulate roaming profiles during user logon and logoff.
1 User accounts are reconfigured to use a small-size mandatory profile. This mandatory
profile is typically stored locally on each Remote Desktop Session Host.
2 One or more file servers are designated as storage servers for storing user data sets,
subset of HKCU and non-redirected shell folders. These file servers run a very low
overhead service dubbed the User State Management Storage Service.
3 All Session Hosts must run the User Profiles Agent Service. An RD Session Host running the
Agent Service is typically referred to as an Agent Server.
4 Using the vWorkspace Management Console, the administrator specifies all the relevant
HKCU subkeys and non-redirected special folders that must persist from one logon to the
next. Additional properties are also set to specify the scope of the subkey or folder to
either Global or Silo specific.
A Global setting is to be used when the registry subkey or folders are located on every
server.
A Silo setting is to be used when the registry subkey or folders are only located on a few
specified servers, and those servers are grouped together to create a silo.
5 When a user logs off, the User Profiles Agent Service exports all the relevant subkeys and
folders specified by the administrator. The Agent Service then compresses the exported
data and sends one or two compressed files (global, silo, or both) to the storage server.
6 When a user logs on again, the Agent Service requests the previously exported data from
the storage server. It then decompresses the data and merges the subkeys and folders
into the mandatory profile.
7 Compressed files are stored on the storage server and named according to the user’s
account SID.
Defining user profiles

User Profiles are used to define storage servers, assign compression levels, define silos, and
assign permissions to users so that they can be allowed to or denied access to adding, modifying,
or deleting Virtual User Profiles.
User Profiles can be configured after components have been installed on the appropriate
servers.
Configuring user profiles

The following items must be configured to use User Profiles:
• Defining user profiles
• Mandatory user profile
To configure user profiles properties

2 Right-click on User Profile Management and do one of the following:
vWorkspace 8.6.3
• Select New User Profile Item to add a new user profile.
• Select Properties to modify the User Profiles Properties.
3 On the User Profile Properties, General window, define the general properties and then
click Next.
Table 119. User Profiles Properties, General property fields
General Property Description

Compression Level The level of compression used when storing user profile element
data to the storage server.
Log Level The level of logging that takes place inside of the profile.
Refresh Interval The interval, in minutes, that checks are made for User Profiles
configuration changes.
4 On the Storage Servers window, define Storage Servers by clicking New and then do the
following:
a Enter a name for the Storage Server, and then click OK.
b Click in the columns on the ellipsis to change the Base Folder, Global Folder, and
TCP Port settings.
The profiles are saved in the Base Folder. It should be a local path on the server.
The Global Folder is the name of the folder for Global settings/profiles.
Table 120. Storage Server Properties
Storage Server Properties Description

Server name The NetBIOS name of the computer which
vWorkspace User State Management Storage
Service has been installed.
NOTE: The storage server name cannot include:
, \ * + = | : ; ? < > " <space>.
Base folder The root or base folder where the user profile
element data is stored. The specified folder is
created if it does not already exist.
Default value is C:\UserProfiles.
Global folder The name of the folder where the profile
elements defined as global is copied. This folder
is created as a sub folder of the Base Folder.
Default is Global.
TCP port The TCP listening port that the vWorkspace User
State Management Storage Service is configured
to listen on.
Default value is 5206 if you installed using the
Simple type of installation.
5 On the Silos window, set up Silos by clicking New, and then do the following:
a On the Welcome window of the Silo wizard, click Next.
b Enter a name for this silo group, and then click Next.
c Click Add Session Hosts or Add Computer Groups to define the silo. From the
Select window, select the appropriate Session Host computer group, and then click
OK.
Session Hosts and computer groups can only be added to one silo at a time.
d On the Members window, click Next.
vWorkspace 8.6.3
e Specify the Auto-Save setting, and then click Finish to close the wizard and return
to the User Profile Properties window.
f Select the User Profile Storage Server from the list, and then click Finish.
The new silo displays in the list.
g On the Silos window, click Next.
6 Specify the Permissions for the user profile.
7 Click Apply and OK.
Mandatory user profile

Mandatory user profiles should be used in conjunction with User Profiles. When creating a
mandatory user profile, consider the following:
• Use a specialized local or domain user account for purposes of profile management.
• Create the mandatory virtual user profile in which users are logging in to on one of the
Session Hosts.
• Make the mandatory virtual user profile as generic as possible.
• Use User Profiles, User Environment Control, and other management features within the
Management Console to control user profiles.
• Remember to rename ntuser.dat to ntuser.man to make the HKCU registry hive
mandatory (read-only).
• Use the System Control Panel applet to copy the mandatory user profile to the target
Session Hosts and set Permitted to Use to Everyone.
• Add a MAN extension to the root folder name of the mandatory user profile to make it
read-only (use folder redirection user profile elements with User Profiles to give users
write access to needed folders).
• Assign the mandatory user profile to the appropriate user accounts in Active Directory.
Assign mandatory user profiles

After the mandatory profile has been created and copied to all servers in the Session Host group,
it then must be assigned to the appropriate user accounts. When specifying the profile path,
keep the following in mind:
• The path should be expressed as a local file system path, not a UNC path.
• Variables such as %SystemDrive% can be used.
• Do not add the user account name or %username% at the end of the path.
• Use the Terminal Services Profile tab rather than the Profile tab of User Properties.
• Path cannot be set using Active Directory Group Policy as it requires using a UNC path and
automatically appends %username% to end of path.
To modify a user’s profile path in active directory

1 Open the Active Directory Users and Computers MMC snap-in.
2 Locate the user object that is to be modified.
3 Right-click on the user object, and then select Properties.
4 Click on the Terminal Services Profile tab.
vWorkspace 8.6.3
The Terminal Services Profile path can be set using Active Directory Group policy if the
domain controllers are Windows Server 2003 Service Pack 1 and appropriate hotfixes have
been applied.
5 In the Profile Path box, enter the local file system path to the mandatory user profile.
6 Click OK.
Visual Basic scripting can be used to automatically modify the profile path for existing users. The
sample below is from Microsoft TechNet Script Center Library.
Defining user profile elements

User Profile Elements determine which keys in the HKEY_CURRENT_USER registry hive are
exported and saved on the User State Management Storage Service.
Normally, when using a mandatory user profile, a user or applications being used cannot save
changes to ntuser.man, the file that makes up the user’s HKEY_CURRENT_USER registry hive.
User preferences and other user specific application settings are not saved. However, the user
and applications being used by the user can modify any of the keys that have been exported.
It is important for the vWorkspace administrator to accurately determine all the
HKEY_CURRENT_USER keys the user might need to modify, and then define them as User Profile
Elements to be exported.
If registry subkeys and folders are only located on a few specified servers, then those servers
should be grouped together into a single silo and the registry subkey should be marked Silo. For
example, if Microsoft Office is only installed on some Session Hosts in the environment, then it
makes sense to only import and export the registry subkey HKCU\Software\Microsoft\Office
when users access those servers.
Or, if registry subkeys and folders are located on every server, then it makes sense to always
import and export the registry subkey. For example, if Adobe Acrobat Reader is installed on all
the Session Hosts then use HKCU\Software\Adobe\Acrobat Reader and select Global as the
Scope.
There are two ways to configure user profiles in vWorkspace:
• Manually configure user profiles
• Importing and exporting user profiles
The vWorkspace Management Console is used to add, edit, and remove user profile items. There
are default profile items for some commonly used profile items to assist administrators in
getting started setting up user profiles.
Manually configure user profiles

In the vWorkspace Management Console, the User Profile Management node can be used to
configure user profiles. Select the green plus sign to start the User Profile Wizard and complete
the user profile elements. You can also right-click on any of the default user profiles and assign
them to the appropriate targets.
Special folder. User Profiles determine which folders within the user’s profile are exported and
saved on the User State Management Storage Server. As with registry keys, any folders or
applications being used need change permissions to be exported.
This mechanism offers control over a broader selection of folders, and higher levels of
compression for increased performance and reduced storage requirements.
vWorkspace 8.6.3
Each User Profile element has the following properties associated with it.
Table 121. User Profile Element Properties
User Profile Element Property Description

Category A user definable name used to associate one or
more user profile elements with each other.
Type and location This setting is used to define the User Profile
element being configured as either a Registry Key
or a Special Folder.
The Registry Key input box used to specify which
registry key or special folder is to be exported.
Logon processing If this setting is Synchronous, all elements must be
retrieved and merged before the user’s Window
desktop is presented.
If this setting is Asynchronous, not all registry keys,
files, and folders need to be present prior to the
presentation of the user’s Window desktop.
Profile persistence This setting is used to specify when the user profile
service saves modified profile data to the storage
servers.
• At a specified interval (auto-save) — Data is
periodically save to the storage servers
based on a specified interval. The interval
used is specified in the silo properties.
• At logoff only
Scope This setting specifies if the User Profile element is
applied on a Global or a Silo basis.
• Global is all Session Hosts in the vWorkspace
infrastructure.
• Silo is only those that are members of a
specified Session Host group. If Silo is
selected, a Silo input box appears.
Client assignments This setting is used to specify the clients to which
the user profile is to be assigned.
Permissions This setting is used to specify permissions for this
user profile item.
• To define a registry key in user profiles

• To define a special folder user profile element
To define a registry key in user profiles

1 Open the vWorkspace Management Console from the desktop of a Session Host that is
known to have the appropriate body of registry keys.
2 Select User Profile Management.
3 Right-click User Profiles, and then select New User Profile.
4 On the Welcome window of the User Profile wizard, click Next.
5 Type a new Category name or select an existing one from the list, and then click Next.
This is used only for organization within the Management Console.
If there are no categories in the database, the drop-down list is empty. Once you create a
category, it becomes available from the list.
vWorkspace 8.6.3
6 On the Type & Location window, select Registry Key, and then enter the desired Registry
Key path and name or use the ellipsis to browse to it. Click Next.
7 In the Logon Processing window, select Asynchronous or Synchronous, and then click
Next.
8 On the Profile Persistence window, select one of the settings to specify when modified
profile data is to be saved, and then click Next.
9 On the Scope window, select Global or Silo. If Silo is selected, use the Silo field to
identify the group that will use this profile element or click Edit Silos to add a new silo.
10 To assign this user profile to a user, complete the Client Assignments window, and then
click Next.
11 To assign permissions to this User Profile, complete the Permissions window, and then
click Finish.
To define a special folder user profile element

1 Open the vWorkspace Management Console from the desktop of a Session Host that is
known to have the appropriate body of registry keys.
2 Highlight the User Profile Management node in the navigation pane.
3 From the context menu of User Profiles, select New User Profile.
4 On the Welcome window of the User Profiles wizard, click Next.
5 Type a new category name or select an existing one from the list, and then click Next.
This is used only for organization within the Management Console.
If there are no categories in the database, the drop-down list is empty. After you create a
category, it becomes available from the list.
6 On the Type & Location window, select Special Folder, and then enter the desired Special
Folder path and name or use the ellipsis to browse to it.
7 Click Next.
8 On the Logon Processing window, select Asynchronous or Synchronous, and then click
Next.
9 On the Profile Persistence window, select one of the settings to specify when modified
profile data is to be saved, and then click Next.
10 On the Scope window, select Global or Silo. If Silo is selected, use the Silo field to
identify the group that will use this profile element. Or, click Edit Silos to add a new silo.
11 To assign this User Profile to a user, complete the Target Assignments window, and then
click Next.
12 To assign permissions to this User Profile, complete the Permissions window, and then
click Finish.
Importing and exporting user profiles

vWorkspace administrators can use an XML file to import and export profile items. The ability to
import and export through an XML file allows the vWorkspace community to share profile items
that can be used for specific purpose with other administrators.
Administrators must have User Profile add permissions to import XML files, but no special
permissions are necessary to export an XML file.
To import or export an XML file, locate User Profiles from the User Environment Management
node in the vWorkspace Management Console. You can select the Import XML or Export XML icon
from the right-pane.
vWorkspace 8.6.3
Import an XML file
After selecting to import an XML file, you need to confirm that you are about to import user
profile items. Once the import process has completed, another window displays the number
items found and the number items imported.
The default folder location for the XML file is My Documents.
Export to an XML file

After selecting to export an XML file, the default location, My Documents folder, opens and
includes the default file name, UserProfileItems.xml.
By default, version number attributes are not written to the export file.
To add a version to an export file item,

• select Shift+Ctrl and Export to XML at the same time.
XML file format

In addition to the default user profiles that are found in the vWorkspace Management Console,
administrators can also manually add items to an XML file.
The user profile settings of Scope and Profile Persistence are not exported. During the import
process, the value for Scope defaults to Global, and the value for Profile Persistence defaults to
Logoff only. These settings can be manually set after importing.
The following table displays the XML format used in user profiles.
<vWorkspace>
<UserProfiles>
<ProfileItem version="1" type="1" synchronous="1" autosave="0">
<Path>HKCU\Software\Adobe</Path>
<Category>Adobe Reader</Category>
</ProfileItem>
</UserProfiles>
</vWorkspace>
Table 122. XML formats used in user profiles
Item Type Value(s) Required Comments

vWorkspace Element N/A Yes Contains the UserProfiles
element.
UseProfiles Element N/A Yes Contains the ProfileItem
elements.
ProfileItem Element N/A Yes Represents a profile
item.
Type Attribute Reg key = 1 No, default is
File path = 2 1.
Synchronous Attribute Yes = 1 No, default is

No = 0 0.
Autosave Attribute Yes = 1 No, default is

No = 0 0.
vWorkspace 8.6.3
Table 122. XML formats used in user profiles
Item Type Value(s) Required Comments

Path Element Contains the Yes Reg keys must begin with
profile item HKCU\.
folder or reg key.
Category Element User defined No

category for this
item.
Version Attribute <integer 1 to No Internal use only, for
9999> auto-load of default
profile items.
User profile management registry setting

By setting the following registry setting, you are able to store settings using just the user name
without the SID. The default is to use both the user name and the SID. This setting would be
helpful if you are using the Novell Dynamic Local User feature.
HKLM\Software\<Wow6432Node>\Provision Networks\MetaProfile Manager\Storage Server
UseUserName
REG_DWORD 0=both username and SID 1=username only
Load balancing
Load balancing can be enabled in a vWorkspace infrastructure when published applications are
hosted across multiple RD Session Hosts or multiple Hyper-V hypervisors. Load balancing rules
are assigned SCVMM managed computer groups, Hyper-V managed computer groups or RD Session
Hosts.
Load balancing rules

Load balancing rules dictate how to calculate user session workloads between session hosts,
published applications, and SCVMM managed desktop groups. Load balancing rules are comprised
of counters and associated values that set minimum and maximum parameters as well as
assigned weight.
To be effective, rules should use as few counters as possible, and the counters selected should
be those that most closely reflect a server’s load. vWorkspace provides two default load
balancing rules and three custom load balancing rules. Both Default and Custom rules can be
duplicated, renamed, and used as a template to create new custom rules.
The available load balancing rules are:
Table 123. Load balancing rules
Load balancing rule Description

Default
Default RD Session Host Load balances users over the available RD Session
(read-only) Hosts based on the amount of users already logged
on. This default rule uses a maximum of 100 users
per host (x86 users may need a lower maximum).
Default VDI for SCVMM Load balances users over the available Hyper-V
(read-only) hosts based on the users already on the hosts. This
default rule uses a maximum of 75 users per host.
vWorkspace 8.6.3
Table 123. Load balancing rules
Load balancing rule Description

Custom
Advanced RD Session Host Load balances users over the available RD Session
Hosts based on a calculated average of: CPU Load,
Disk Queue Length and Memory Load. This custom
rule configures a maximum of 100 users per host.
Advanced VDI for SCVMM Load balances users over the available Hyper-V
hosts based on a calculated average of: CPU Load,
Disk Queue Length and Memory Load. This custom
rule configures a maximum of 75 users per host.
RFX for SCVMM Load balances users over the available Hyper-V
hosts based on an average GPU response time from
capture. The user will connect to a virtual desktop
that has the lowest GPU response time from
capture, resulting in the best RemoteFX user
experience.
How load balancing works

Based on the load balance assigned, the server evaluates its current workload and reports that
value to the Connection Broker. Connection Brokers maintain a memory table of the current
workload index of each server on which load balancing has been enabled.
When a Connection Broker receives a client request to connect to a published application, it
queries the list of servers on which the application is hosted and determines which one currently
has the lowest workload index value. The address of the least busy server is then returned to the
vWorkspace client. When the vWorkspace client completes the connection to the least busy
server, that server’s load is changed. The new workload is then reevaluated and reported to the
Connection Broker.
Load balancing applies only when a vWorkspace client initiates a request for a new connection.
If a vWorkspace client is already connected to an RD Session Host and requests to start another
application that is available on that same server, the application is run through the existing
session and load balancing is not applied.
Multiple counters can be included in a load balance. Each counter within a load balance has an
upper and lower threshold setting that is used to determine when the server is under maximum
or minimum load based on that counter. Each counter can also be assigned a weight which can be
used to adjust the relative importance of one counter over another.
Table 124. Available counters for load balancing
Counter Name Description

Context switches per second This counter measures the overall rate of switches
from one thread to another. Thread switches can
occur either inside a single process or across
processes.
A thread switch can be caused by one thread asking
another for information, or by a thread being
preempted by another higher priority thread.
CPU load This counter measures the percentage of time CPUs
in the system are actively executing threads
belonging to processes.
This counter does not include the System Idle
Process.
vWorkspace 8.6.3

CPU queue length This counter measures the number of threads in the
processor queue. Unlike disk queue, processor
queue length shows ready threads, not threads that
are currently running.
There is a single queue for processor time, even on
systems with multiple processor cores and sockets.
Therefore, if the system has multiple processors,
you need to divide this value by the number of
processors servicing the workload.
A sustained processor queue of less than 10 threads
per processor is usually acceptable.
Disk load This counter measures the percentage of time the
disks in the system are active.
Disk queue length This counter measures the average number of read
and write requests that were queued for the
selected disk during the sampling interval.
GPU response time from capture This counter measures the latency within RemoteFX
Capture (in microseconds) for GPU operations to
complete.
Interrupts per second This counter measures the average number of
hardware interrupts that were received and
serviced by the processor each second.
Interrupts per second is an indirect indicator of the
activity of hardware devices in the system that
generate interrupt requests, such as the system
clock, disk drives, and network interface cards.
These devices generate interrupt requests when
they complete a task or need attention from the
processor. Each service interrupt request consumes
CPU time, so an excessive amount can degrade
system performance and can be an indicator of a
malfunctioning device.
Memory load This counter measures the percentage of memory
being used by the system.
Memory pool pages bytes This counter measures the size, in bytes, of the
paged pool.
The paged pool is an area of physical memory used
by the system for objects that can be written to
disk (paged) when they are not being actively used.
Number of powered-on virtual This counter measures the number of powered-on
computers virtual computers currently running on the host.
Number of processes This counter measures the total number of process
contexts currently running on the system.
Number of users This counter measures the total number of user
sessions for which the operating system is currently
storing computer state information.
Number of virtual computers This counter measures the number of virtual
computers defined on the client.
vWorkspace 8.6.3

Page faults per second This counter measures the overall rate at which
faulted pages are handled by the processor. This
counter includes both hard faults (where the
memory page has to be retrieved from disk) and
soft faults (where the data is stored elsewhere in
physical memory).
A page fault occurs when a process requires code or
data that is not in its space in physical memory.
Most processors can handle large numbers of soft
faults without consequence. However, hard faults
can cause significant performance delays.
Pages per second This counter measures the number of pages written
to or read from disk to resolve hard page faults.
Redirector current commands This counter measures the number of requests to
the redirector that are currently queued for
service.
If this counter is much larger than the number of
NICs installed on the system, then network
throughput is likely becoming a bottleneck.
TDRs in server GPUs This counter measures the Total number of times
that the TDR times out in the GPU on the server.
Load balancing on session hosts

To enable load balancing of vWorkspace enabled Session Hosts, the following conditions must be
met:
• The RD Session Host role must be installed on one or more Session Hosts in the
vWorkspace infrastructure.
• The setting Accept “least busy” connection requests must be enabled (it is by default)
on each Session Host that participates in load balancing. This setting is found on the
General tab of the Session Host properties under Roles.
• The Session Host must host at least one of the configured managed applications.
• A load balance must be assigned to either the server or a managed application hosted on
the server.
Load balancing guidelines

Consider these guidelines when using load balancing:
• Use as few counters as possible. Each counter used in a load balance requires additional
processing.
• Use the counters that are most likely to reflect the critical resources of the server.
• Avoid using extreme limits for counters that use percentages for minimum and maximum
values.
• Use a counter only if you understand its meaning and what values are appropriate.
• Group Session Hosts by their hardware configuration and applications hosted on them.
Load balances can be created and optimized for specific hardware or application groups.
vWorkspace 8.6.3
To create a load balancer
The Number of Users counter is the default load balance assigned by the system, and its values
cannot be modified.
2 Right-click on the Load Balancing node, and select New Load Balancing Rule.
3 On the Welcome window of the Load Balancing Rule Wizard, click Next.
4 On the Name & Description window, enter a name and description for the new load
balancing rule, then click Next.
5 On the Counters window, do the following:
a Select the counter to be used by clicking in the Assigned column.
b Set the minimum value for each counter selected by clicking on its current value
in the Min Value column, and then type a new value in the input box.
c Set the maximum value for each counter selected by clicking on its current value
in the Max Value column, and then type a new value in the input box.
d Set the weight value for each counter selected by clicking on its current value in
the Weight column, and then select a new value from the list.
e Select Report full load when at least one counter has reached its maximum
value, if needed.
f Click Next.
6 Set the permissions and then click Finish.
To assign load balancing to session hosts

2 Expand the Locations node, and then expand the location in which the RD Session Host is
located.
3 Expand the Session Hosts node, and then highlight the RD Session Host.
4 Highlight the server object to which the load balancing rule is to be assigned, right-click,
and select Properties to display the Server Properties window.
5 Highlight Load Balancing.
6 Click the Specify a custom load balancing rule button to enable the custom rules. Select
the desired custom load balancing rule from the Custom Load Balancing Rule list.
Otherwise, the default load balancing rule will apply.
7 Click OK to complete the task.
To assign load balancing to SCVMM computer groups

2 Expand the Locations node, and right-click the Desktops node.
3 Select New Computer Group.
4 On the New Computer Group Wizard, click Next to display the Group Name window.
5 Specify the name for the new computer group and click Next to display the System Type
window.
6 Select the Microsoft SCVMM box to disable load balancing for all other system types.
7 Click Load Balancing. On the Load Balancing window, do one of the following:
• Click the Do not specify a load balancing rule action button to disable load
balancing rules.
vWorkspace 8.6.3
• Click the Use the default load balancing rule action button to use the default
SCVMM rule.
• Click the Specify a custom load balancing rule: action button to enable the custom
rules. Select the desired custom Load Balancing Rule from the Load Balancing Rule
list.
• Click the View button on any action button selection to view the rule properties.
8 Proceed through the windows to configure the new computer group.
9 Click Finish to complete the task.
For more detail on adding new SCVMM computer groups, see the Microsoft SCVMM integration
section.
To assign load balancing to managed applications

You may need to assign load balancing to specific published applications if the number of
instances of the application must be restricted due to constraints or the application consumes a
lot of system resources.
2 Highlight the Managed Applications node, right-click on the desired published application
and select Properties to display the Managed Application window.
3 Click Load Balancing.
4 Click the Specify a custom load balancing rule button to enable the custom rules. Select
the desired custom load balancing rule from the Load Balancing Rule list.
5 Click OK.
To assign load balancing to a Hyper-V host

2 Expand the Locations node, and then expand the location in which the Hyper-V Host is
located.
3 Expand the Virtualization Hosts node, and then highlight Hyper-V.
4 Highlight the hyper-V host to which the load balancing rule is to be assigned, right-click,
and select Properties to display the Hyper-V Host Properties window.
5 Highlight Connection Load Balancing. Specify the load balancing rule for connections to
this host.
6 Highlight Provisioning Load Balancing. Specify the load balancing rule for provisioning to
this host.
7 Click OK.
vWorkspace Password Reset service

The vWorkspace Password Reset Service facilitates SSL-protected password reset requests from
clients, to allow them to reset their Active Directory Credentials using Web Access or the
vWorkspace Connector for Windows. This service requires an SSL Certificate and listens on port
443 (by default).
The vWorkspace Password Reset Service can be installed on any Windows computer, physical or
virtual, that is joined to a domain trusted by the domain containing the accounts of the users
connecting in to the vWorkspace infrastructure.
CAUTION:The vWorkspace Password Reset Service should never be installed on a
computer that is in the DMZ network.
vWorkspace 8.6.3
To configure the vWorkspace Password Reset service
1 Use the following path to open the Password Manager Control Panel applet.
Start | Control Panel | Quest Password Manager
2 On the General tab, enter the TCP Port.
3 Click the Lock icon by Certificate Name.
4 On the Select Certificate window, select the certificate, and then click OK.
5 If you want to use logging, select the Logging tab and then Enable trace logging to the
specified file.
6 Enter the path and file name for the log file, or use the folder button to browse to it.
7 Click OK to save your changes.
To configure vWorkspace Password Management in the Connector for Windows

1 Open the vWorkspace Connector for Windows client.
2 Use the following path to open the Farm Connections window.
Actions | Manage Connections
• If you are configuring Password Management on an existing farm, do the
following:
a On the Select Farm window, select Modify existing farm, and then select the farm
that is to be edited from the list.
b Select Password Management from the left pane, and complete the information.
c Click OK.
d If you are configuring Password Management on a new farm, select Create new
farm on the Select Farm window. Complete the necessary information on the Farm
Connections window.
e Click OK.
To configure vWorkspace Password Management in Web Access

This option can only be configured as a global setting.
1 Under the Authentication options on the Web Access Management Console, select
Password Management.
2 Enter a Domain using the NetBIOS name of the Password Management server.
3 Enter the Server (FQDN).
The host name, NetBIOS name, or IP address can be used in this field.
4 Enter a Port number (usually 443), and then click Add.
5 Repeat the above steps to add multiple Password Management servers.
6 Click Save Changes.
vWorkspace 8.6.3
7
Appendix
Sentillion integration
Sentillion markets numerous health care integration products that unify single sign-on (SSO),
context management and strong authentication, into a fully integrated managed clinical workstation
enabling caregivers to quickly access their applications and the associated patient data. Sentillion
components install a custom Sentillion GINA that integrates with the clinical desktop to provide SSO
services and chains to subsequent GINAs. Thus, the Sentillion components should be installed after
Virtual Desktop Extensions (PNTools) to ensure proper GINA chaining with vWorkspace.
This section describes the registry entry necessary for the integration of vWorkspace and Sentillion.
Because of the Sentillion GINA, vWorkspace must properly initialize Windows Explorer and bypass
the normal PNStart execution. With the following integration, you are able to complete a single sign-
on to a virtual computer using the Sentillion solution.
The following registry entry needs to be added to the client endpoint running vWorkspace Connector
for Windows or PNTSC that is connecting to the Sentillion desktop. By setting this registry entry,
pnstart.exe is bypassed, launching Explorer directly, allowing Sentillion to obtain credentials for
further application logon passthrough.
HKLM\Software\Provision Networks\Provision-
"TSClientUsePNStart" (REG_DWORD) = "0"
This setting is only effective for terminal servers. PNStart is executed on VDI virtual machines using
the registry value:
HKEY_LOCAL_computer\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Shell REG_SZ
PNTools setup will set this value to ’PNSTART.EXE’. To disable PNSTART.EXE from running on VDI
computers, change this value to ’EXPLORER.EXE’.
vWorkspace 8.6.3
256
About Dell
Dell listens to customers and delivers worldwide innovative technology, business solutions and services they
trust and value. For more information, visit www.dell.com.
Technical support resources

Technical support is available to customers who have purchased Dell software with a valid maintenance
contract and to customers who have trial versions. To access the Support Portal, go to
http://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a
day, 365 days a year. In addition, the portal provides direct access to product support engineers through an
online Service Request system.
The site enables you to:
• Create, update, and manage Service Requests (cases)
• View Knowledge Base articles
• Obtain product notifications
• Download software.
• View how-to videos
• Engage in community discussions
• Chat with a support engineer
Third-party contributions
This product contains the third-party components listed below. For third-party license information, go to
http://www.quest.com/legal/license-agreements.aspx. Source code for components marked with an asterisk
(*) is available at http://opensource.dell.com.
vWorkspace 8.6.3
257

Vworkspace 8.6.3 Administration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vworkspace 8.6.3 Administration Guide

Uploaded by

Copyright:

Available Formats

Wyse™ vWorkspace™ 8.6.

Key features of vWorkspace

User profile management

TCP port requirements

Prerequisites for installing Web Access

Hardware • Server class hardware that meets the

Prerequisites for installing the Secure Access service

Prerequisites for WSM integration

To install the Web API rest service

About the Simple installation

Installing vWorkspace: Simple method

To install vWorkspace: Simple method

Figure 2. vWorkspace installation window

3 On the vWorkspace installation window, click Install.

4 Click Yes to start the process.

Figure 4. Welcome to InstallShield Wizard

6 On the Welcome to the InstallShield Wizard for vWorkspace, click Next.

Figure 5. Simple installation Setup Type

9 On the Setup Type window, select Simple, and click Next.

12 On the InstallShield Wizard Completed window, click Finish.

Installing vWorkspace: Advanced method

To install vWorkspace: Advanced method

Figure 6. vWorkspace installation window

3 On the vWorkspace installation window, click Install.

4 Click Yes to start the process.

Figure 8. Welcome to InstallShield Wizard

6 On the Welcome to the InstallShield Wizard for vWorkspace, click Next.

Figure 9. Advanced installation Setup Type

9 On the Setup Type window, select Advanced, and click Next.

Table 3. Roles and Features

Management Database Setup

Monitoring and Diagnostics Role

To install the Monitoring and Diagnostics role

Figure 13. Discovery prompt

3 From the Installshield Wizard prompt, click OK.

Figure 15. Monitoring and Diagnostics Configuration window

Monitoring and Diagnostics Agent Manager role

Table 5. Agent Manager Information

Core Must always be specified

1 Requires Database Options (see below).

Table 7. Database options used to perform a scripted installation

DBOPTION Specifies how to setup the database connection

* only required for DBOPTION=2

Examples of a scripted installation

Installing vWorkspace Connectors

Automatically installing the vWorkspace Connector for

To automatically install the vWorkspace Connector for Windows

4 If the user installs the new version:

Manually installing the vWorkspace Connector for Windows

To manually install the vWorkspace Connector for Windows

vWorkspace Windows Connector silent installation

Integrating the Dell Wyse ThinOS™ thin clients with

• 3000 series Thin Clients

Thin client configuration

HTTP://10.0.0.22:8080 One Connection Broker (10.0.0.22), protocol

Enabling HTTP and HTTPS Support 

Supporting Environments with Multiple Subnets 

C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet1\wyse\WNOS

C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet2\wyse\WNOS

C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet1\WNOS

C:\Program Files (x86)\Quest Software\vWorkspace \WYSE\subnet2\WNOS

To manually configure the thin client

Configuring the vWorkspace connection broker