Version 8.0 MR1 - Questsupport-public.cfm.quest.com/e2a0cc16-5a80-46e4-b34b-5d6de74c14… ·...

vWorkspace

System RequirementsVersion 8.0 MR1

© 2012 Quest Software, 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 Quest Software, Inc.The information in this document is provided in connection with Quest 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 Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST 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 QUEST 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 QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest 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. Quest 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:Quest Software World HeadquartersLEGAL Dept5 Polaris WayAliso Viejo, CA 92656email: [email protected] to our Web site (www.quest.com) for regional and international office information.Patents

This product includes the following patent-pending technology:

TrademarksQuest®, Quest Software®, the Quest Software logo®, and vWorkspace™ are trademarks and registered trademarks of Quest Software, Inc., and its subsidiaries. See http://www.quest.com/legal/trademark-information.aspx for a complete list of Quest Software’s trademarks. Other trademarks are property of their respective owners.vWorkspace System Requirements Guide — Updated November 2013 — Software Version 8.0 MR1

vWorkspace™ Protected by U.S. Patent # 8,255,984. Additional patents pending.

vWorkspace™ Desktop Virtualization

Patents Pending.

Foglight™ for Virtualization

Protected by U.S. Patents # 7,979,245 and 8,175,863. Additional Patents Pending.

http://www.quest.com/legal/trademark-information.aspx

http://www.quest.com/legal/trademark-information.aspx

vWorkspace Hardware and Software System RequirementsThis document outlines the minimum system requirements for installing and running each of the vWorkspace components. vWorkspace includes the following infrastructure components:

• Foglight for Virtual Desktops Role

• Connection Broker Role

• Management Console Role

• Web Access Role

• Terminal Server/RD Session Host Role

• User Profile Management Storage Role

• Secure Gateway Role

• Universal Print Server Role

• Remote Site Relay Role

• Password Reset Role

• Proxy-IT Role

• Reporting and Logging Role

• Report Viewer

• Broker Helper Service

• Hyper-V Catalyst Components

• Extensions for the RD Connection Broker

• PNTools (installed in Virtual Desktop)

• vWorkspace Connector for Windows

• HyperCache Support for Microsoft Deduplication in Windows Server 2012 R2 (Technology Preview)

vWorkspace System Requirements

Foglight for Virtual Desktops Role

For system requirements and other documentation for the Foglight for Virtual Desktops role, see the Foglight for Virtual Desktops topic at Support.quest.com.

Foglight for Virtual Desktops documentation.

4

https://support.quest.com/Foglight%20for%20Virtual%20Desktops/Release-Notes-Guides

https://support.quest.com/Foglight%20for%20Virtual%20Desktops/Release-Notes-Guides

Connection Broker Role

Platform 2 Ghz or higher Intel Pentium 4 compatible CPU

System Memory (RAM) 2 GB or more recommended

Hard Disk Space 80 MB or more of free disk space

Operating System The Connection Broker Role can run on any of these operating systems:

• Microsoft Windows Server 2008 R2, Service Pack 1

• Microsoft Windows Server 2012

• Microsoft Windows Server 2012 R2

The Connection Broker Role should only run on a member server and either a physical machine or a virtual host that is not hosting virtual desktops.

SQL Server The vWorkspace management database can be hosted by:

• Microsoft SQL Server 2008 (x86 and x64) and 2008 R2

• Microsoft SQL Server 2012 (x86 and x64)

• Microsoft SQL Server Express Edition 2008 (x86 and x64) and 2008 R2

• Microsoft SQL Server Express Edition 2012 (x86 and x64)

Microsoft .NET Framework

The Connection Broker Role requires Microsoft .NET Framework 4.0.

This is automatically installed when this role is selected for installation.

Java If using vWorkspace with VMware, then the Java 2 Platform Standard Edition Runtime Environment 5.0 (update 9,10, or 11) is required.


5


Virtualization Platforms & Platform Management

vWorkspace can use one or any of the following Virtualization Platforms:

• Microsoft Hyper-V Server 2008 R2, 2012, 2012 R2

• Microsoft Windows Server 2008 R2, 2012, 2012 R2 Standard, Enterprise, or Datacenter. The Hyper-V role is required. NOTE: Microsoft Windows Server 2012 and 2012 R2 do not include Enterprise edition.

• Parallels Virtuozzo Containers (PVC) 4.6 running Microsoft Windows Server 2008 and Microsoft Windows 2008 R2 containers. PVA 4.6.

• Microsoft SCVMM 2008 R2 SP1, Microsoft SCVMM 2012, and Microsoft SCVMM 2012 SP1 (requires Broker Helper Service).

• VMware vCenter 4.1 update 3, 5.0 update 1, and 5.1 update 1.

Storage Management vWorkspace can use the following storage management technologies:

• NetApp FlexClone with Data Ontap 7.3.6, 7.6 and Data Ontap 8.0 7-mode or 8.1 7-mode.

(See support.quest.com for the currently supported version).

6

Management Console Role

Platform 1.5 Ghz or higher Intel Pentium compatible CPU



Operating System The Management Console Role can be run on any of these operating systems:

• Microsoft Windows 7, Service Pack 1 (x86 edition)

• Microsoft Windows Server 2003, Service Pack 2 (x86 and x64 editions)

• Microsoft Windows Server 2003 R2, Service Pack 2 (x86 and x64 editions)

• Microsoft Windows Server 2008, Service Pack 2 (x86 and x64 editions)




Web Browser • Microsoft Internet Explorer 8.0 and later.

Note: For the complete diagnostics and monitoring experience, use IE 9 or later.


The Management Console Role requires Microsoft .NET Framework 4.0.


Application Virtualization

The following versions of Microsoft Application Virtualization (App-V) can be used:

• App-V versions 4.6 and 5.0 SP1

Note: Microsoft App-V servers version 4.6 must be trusted for delegation in Active Directory.

7


Web Access Role

Platform 1 Ghz or higher Intel Pentium compatible CPU



Operating System vWorkspace Web Access can be run on a web server with any of these operating systems:




Web Browser • Microsoft Internet Explorer 9.0, 10.0, and 11.

• Mozilla Firefox version 23 and 24

• Google Chrome 29 and 30

• Safari on Mac OS and iOS devices

Note: Internet Explorer is recommended, as some features may be unsupported in Firefox and Google Chrome.


Web Access requires Microsoft .NET Framework 4.0.

This is automatically installed when this role is selected for install.

Two-factor Authentication Support

Web Access supports RADIUS authentication through Quest Defender or any other RADIUS compliant two-factor authentication solution.

Third Party Remote Access Support

Web Access supports the following third party remote access solutions:

• Microsoft ForeFront UAG 2010 SP2

• F5 Firepass SSL VPN 7.0.0 with hotfix HF-70-4.1-1

• Juniper Secure Access SSL VPN 7.0R1 - 7.0R5.1

• Cisco ASA 8.2(5)

8

Internet Services On the web server, Web Access requires Microsoft Internet Information Services (IIS) 6.0 or later.

• ASP.NET

• Enable network COM+ access

• Internet Information Services (Common Files, Internet Information Services Manager, World Wide Web Service)

If you are installing on Microsoft Windows Server 2008 R2, 2012 or 201R2, the following role services for IIS must be enabled. These roles are automatically enabled by the vWorkspace installer.

• Common HTTP Features

•Static Content

•Default Document

•Directory Browsing

•HTTP Errors

•HTTP Redirection

• Application Development

•ASP.NET

•.NET Extensibility

•ISAPI Extensions

•ISAPI Filters

9


Internet Services • Health and Diagnostics (The following three items are optional for monitoring purposes.)

•HTTP Logging

•Logging Tools

•Request Monitor

• Security

•Windows Authentication

•Client Certificate Mapping Authentication (only required if using smart cards for single sign-on with the Web Access Component)

•IIS Client Certificate Mapping Authentication (only required if using smart cards for single sign-on with the Web Access Component)

•Request Filtering

• Performance

•Static Content Compression

•Dynamic Content Compression

• Management Tools

•IIS Management Console

•IIS Management Scripts and Tools

•IIS 6 Management Compatibility

•IIS Metabase Compatibility

•IIS 6 WMI Compatibility

•IIS 6 Scripting Tools

•IIS 6 Management Console

10

Terminal Server/RD Session Host Role


System Memory (RAM) 2GB Minimum


Operating System The Terminal Server/RD Session Host Role can be run on a server with any of these operating systems:

• Microsoft Windows Server 2003, Service Pack 2 (x86 edition)

• Microsoft Windows Server 2003 R2, Service Pack 2 (x86 edition)

• Microsoft Windows Server 2008, Service Pack 2(x86 and edition)




11


User Profile Management Storage Role


System Memory (RAM) 512 MB minimum, 1 GB or more recommended


Operating System The User Profile Management Storage Role can run on a server with any of these operating systems:





The User Profile Management Storage Role requires Microsoft .NET Framework 2.0 or later.

This is automatically installed when this role is selected for install.

12

Secure Gateway Role




Operating System The Secure Gateway Role can run on a server with any of these operating systems:




Certificate The Secure Gateway Role requires one or more X.509 certificates (depending on configuration).

13


Universal Print Server Role




Operating System The Universal Print Server Role can run on a server with any of these operating systems:

• Microsoft Windows Server 2003, Service Pack 2 (x86 edition)

• Microsoft Windows Server 2003 R2, Service Pack 2 (x86 edition)




14

Remote Site Relay Role


System Memory (RAM) 512 MB Minimum, 1GB or more recommended


Operating System The Remote Site Relay Role can be run on a server with any of these operating systems:




15


Password Reset Role




Operating System The Password Reset Role can run on a server with any of these operating systems:




The Password Reset Role can only run on a member server.

Certificate The Password Reset Role requires an X.509 certificate.

16

Proxy-IT Role

In vWorkspace 8.0 MR1, this role is no longer supported.

17


Reporting and Logging Role

The reporting database is hosted by the same SQL Server instance as the management database. The disk space requirements below refer to the “extra” space needed on the database server.

Platform 2 Ghz or higher Intel Pentium 4 compatible CPU


Hard Disk Space 5 GB or more minimum free disk space

The actual space requirements will depend on your vWorkspace configuration and the amount of historical data retained.

By default, the reporting database will automatically purge all data older than 14 days. (This purge takes place every 6 hours).

SQL Server The Reporting and Logging Role can be hosted by:

• Microsoft SQL Server 2008 and 2012 (x86 and x64 editions)

• Microsoft SQL Server Express 2008 and 2012 (x86 and x64 editions)

18

Report Viewer

In vWorkspace 8.0 MR1, this role is no longer supported. This functionality has been replaced with the Diagnostics and Monitoring feature set of vWorkspace.

19


Broker Helper Service




Operating System The Broker Helper Service can run on a server with any of these operating systems in full installation:




The Broker Helper Service needs to be installed on the same machine that is hosting the SCVMM server and console.


Broker Helper requires Microsoft .NET Framework 3.5 or later.

Windows PowerShell Microsoft Windows PowerShell v2.0 and v3.0.

20

Hyper-V Catalyst Components

Platform 2.0 Ghz or higher x64 Intel VT or AMDV enabled processor


Note: The HyperCache feature of the Hyper-V Catalyst Components utilizes system RAM to cache parent VHDs and therefore its memory requirements will vary depending on the cache size and number of parent VHDs.


Operating System The Hyper-V Catalyst Components are installed on a Microsoft Windows Server 2008 R2 Service Pack 1, Windows Server 2012 or Windows Server 2012 R2 with the Hyper-V role enabled.

21


Extensions for the RD Connection Broker

In vWorkspace 8.0 MR1, this role is no longer supported.

22

PNTools (installed in Virtual Desktop)




Supported Guest Operating Systems

PNTools can run on a guest with any of these operating systems:

• Microsoft Windows XP, Service Pack 3 (x86)

• Microsoft Windows 7 Enterprise, Service Pack 1 (x86 and x64 editions)

• Microsoft Windows Server 2003 R2, Service Pack 2 (x86 edition) *PVC Only

• Microsoft Windows Server 2008, Service Pack 2 (x86)


• Microsoft Windows 8 Enterprise

• Microsoft Windows 8.1 Enterprise

• Microsoft Windows 2012

• Microsoft Windows 2012 R2

• Rhel 5.9 and 6.4 (5.7 is supported for RGS)

• CentOS 5.9 and 6.4 (5.7 is supported for RGS)

EOP Multimedia Enhancements

EOP Flash Acceleration

If using EOP Flash Acceleration, you must have one of the following versions of Adobe Flash Player installed on the Virtual Desktop:

• Adobe Flash Player 11

EOP Flash Acceleration works with Internet Explorer versions 8, 9, 10 and 11.

Note: The version (major versions) installed in the Virtual Desktop must match the version that is installed on the Client Access Device. If the versions do not match, the flash content plays without EOP Flash Acceleration, through RDP.

EOP Multimedia Acceleration

Microsoft Windows Media Player 11 and 12 are supported.

23


vWorkspace Connector for Windows




Operating System The Connector for Windows can run on a client access device with any of these operating systems:

• Microsoft Windows XP, Service Pack 3 (x86 edition)

• Microsoft Vista, Service Pack 2 (x86 and x64 editions)

No EOP support

• Microsoft Windows 7, Service Pack 1 (x86 and x64 editions)

• Microsoft Windows 8 (x86 and x64 editions)

• Microsoft Windows 8.1 (x86 and x64 editions)

• Microsoft Windows Embedded Standard 2009

• Microsoft Windows Embedded Standard 7 and 8

EOP Multimedia Enhancements

EOP Flash Acceleration

If using EOP Flash Acceleration, you must have one of the following versions of Adobe Flash Player installed on the Virtual Desktop:

• Adobe Flash Player 11

EOP Flash Acceleration works with Internet Explorer versions 8, 9, 10 and 11.

Note: The version (major versions) installed in the Virtual Desktop must match the version that is installed on the Client Access Device. If the versions do not match, the flash content plays without EOP Flash Acceleration, through RDP.

EOP Multimedia Acceleration

Microsoft Windows Media Player 11 and 12 are supported.

24

HyperCache Support for Microsoft Deduplication in Windows Server 2012 R2 (Technology Preview)

vWorkspace 8.0 MR1 supports Microsoft Windows Server 2012 R2 Deduplication as a Technology Preview. Customers are supported based on a best effort basis We do guarantee that we can fix all issues.

Microsoft Windows Server 2012 R2 Deduplication can be used with vWorkspace 8.0 MR1 in two different ways.

• Enable Microsoft Windows Server 2012 R2 Deduplication on a local volume of a vWorkspace managed Microsoft Windows Server 2012 R2 Hyper-V Host. This scenario is not recommended by Microsoft due to the fact that Microsoft Windows Server 2012 R2 Deduplication requires significant system resources and resource contention could occur. There is no technical limitation on using Microsoft Windows Server 2012 R2 Deduplication on a local volume of a vWorkspace managed Microsoft Windows Server 2012 R2 Hyper-V Host.

• Use Microsoft Windows Server 2012 R2 Deduplication on a Microsoft Windows Server 2012 R2 Scale Out File Server connected over SMB3 with a Microsoft Windows Server 2012 R2 Hyper-V host. To be able to use this scenario, a vWorkspace hotfix is required. The hotfix is scheduled to be available within 60 days of the general availability of vWorkspace 8.0 MR1. This method is recommended by Microsoft.

When evaluating vWorkspace 8.0 MR1 supports for Microsoft Windows Server 2012 R2 Deduplication consider the following:

• Testing has shown that a 70-80% deduplication rate can be achieved on vWorkspace placement volumes (local volume)

• When performing the deduplication operations, expect the following system resource increase:

• 50% Disk Read IO• 15-25% CPU • A variable amount of RAM. Tests have shown that the memory usage

is dependent on the number of files and the size of the files being analyzed and the amount of available memory.

• The biggest impact is seen in VDI scenarios, although the same benefits can be seen on RDSH deployments.

• There is no need to shut down virtual desktops with Microsoft Windows Server 2012 R2 Deduplication.

25


Use the following guidelines when evaluating vWorkspace 8.0 MR1 supports for Microsoft Windows Server 2012 R2 Deduplication:

• When using a local Hyper-V volume, run the deduplication operation at off-peak times when the vWorkspace managed Microsoft Windows Server 2012 R2 Hyper-V Host is not busy (at night, for example). Consider the projected system resources to prevent resources contention.

• Use the Microsoft deduplication UI to schedule the deduplication operation.

• Use a traditional Hyper-V Group and configure it to not delete virtual desktops at logoff (do not use a Desktop Cloud). Note: Not deleting a virtual desktop at logoff does reduce the effect of vWorkspace VDI (re)load balancing.

26

Version 8.0 MR1 - Questsupport-public.cfm.quest.com/e2a0cc16-5a80-46e4-b34b-5d6de74c14… ·...

Documents

Transcript of Version 8.0 MR1 - Questsupport-public.cfm.quest.com/e2a0cc16-5a80-46e4-b34b-5d6de74c14… ·...