Transcript Provisioning Services 5.1 - SP1

Techy Thursday proudly presents:
Utilize the new features in
Provisioning Services 5.1
Mikael Lindholm, Sr. Systems Engineer
EMEA Sales Dev, Server Virtualization
October 2009
Webinar protocol
• Use the GoTo Webinar Q&A panel in the right of your screen
to ask any questions.
• You can also use the ”Raise your hand” -function to request
to have yourself unmuted during Q&A time
• Presentation available beginning of next week.
A few words on the presenter
• Took two years to understand the beauty of Citrix
after first encounter in 1998
• Citrix Instructor and Consultant for a partner since 2000
First CCIA in the Nordics
• Joined Citrix Systems Finland in 2004
• Joined Citrix Systems EMEA in 2008 as a
Product Specialist specializing in PVS
• Moved to the EMEA Server Virtualization group in 2009
focusing on the Essentials for XenServer and Hyper-V
• Gained ~10 kg since joining Citrix and has long hair because no time to
go to the barber shop
Citrix Confidential - Do Not Distribute
Agenda
• Provisioning Services brief overview
• PVS 5.1 New Features – What, when and why use them
• Scalability and Sizing
• A few tips from the field
• PVS 5.1 SP 1
• Q&A
Provisioning Services Brief Overview
Provisioning Services - Conceptual
• Components
vDisk 1
Data Collectors
vDisk 2
Web Interface
vDisk 3
Mission Critical
vDisk 4
Common
• vDisks
• Provisioning Services
Provisioning Server Farm
• Target Devices
• Streaming
• Write cache
Data Collectors
Mission Critical Silo
Web Interface
XenApp Farm
Common Application Silo
Provisioning Services 5.1New Features
Provisioning Services 5.1 - Complete Feature list
• Feature List:
•
•
•
•
•
•
•
•
•
•
Standard Image Mode NIC Teaming
Multiple Volume vDisks
Offline DB Support
User assigned vDisks
Improved Logging
VHD Direct Boot
Read-only File System
Server Initiated Failover
XP Embedded Streaming
Auditing
Standard Image Mode NIC Teaming
• Hardware NIC Teaming supported in
all vDisk modes
• Vendors supported
• Intel
• Broadcom (not on Dell)
• Modes supported
• Fault Tolerance
• Load Balancing
Creating vDisk Image - XenConvert
• Image one or more volumes:
•
•
•
•
Up to 4 volumes per vDisk
NTFS only
Not contained within an extended partition
Partitions will be sized automatically on the
destination disk
• Two ways of building the vDisk
• To Provisioning Services vDisk
• To VHD, IF the PVS drivers are installed
• Two ”versions”
• With PVS converto to PVS vDisk only
• Full version with XenServer or from myCitrix
Multiple Partition vDisks
• Imaging of systems with multiple physical / logical drives into a single vDisk
• How XenConvert Partitions Multiple Drivers
Offline Database Support
• Continued operation
of Provisioning
Services hosts and
provisioned systems
in the event of a
database failure or
outage
Offline Database Support
Unavailable when database connection is lost, regardless if Local
Database Resiliency option is enabled:
•
•
•
•
•
•
•
Active Directory password changes
AutoAdd target devices
AutoUpdate or Incremental vDisk updates
RamDisk mode
Stream Process startup
User Groups (user assigned vDisks) – called follow the user
vDisk creation
Offline Database Support
Offline Database Support
MCLI Get farm
When to enable ”Offline database support”
• No real reason yet to not turn on this feature
• Small performance gain at the cost of a small
memory footprint increase.
• If disconnected from the PVS Datastore before the
first snapshot there might be a MMC snap-in error.
User Assigned Virtual Disks
User Assigned Virtual Disks
• Selects vDisk to
stream to a
provisioned
system based on
user logon
User Assigned Virtual Disks
User Assigned Virtual Disks
User Assigned Virtual Disks
• vDisks assigned to individual users rather than machines:
• Port Blocker and Personality settings will be supported on a per-Device basis, not on a
user or group basis. GPO settings may continue to be applied on top of these settings
• If device is not a member of a Collection with user groups enabled, target device boots
using the vDisk assigned to that target device
• Each target device maintains its own Difference Disk, which does not follow the user from
machine to machine
• Domain\username is not used for authentication, just vDisk
assignment
When to use this feature?
• As part of a PVS for Desktops or XenDesktop scenario
• Enable ”Follow the User” with (fat) streamed endpoints
• Does not currently make sense in hosted XenDesktop
environments
Enhanced Logging - Server
•
New logging
improvements will
greatly simplify
and expedite
problem
remediation
Enhanced Logging – Target Device
• There is no config file
on the client side
• NOTE:
You need the Server
logging level to be the
same or higher to get
logs from the Target
Enhanced Logging – Log Files
Enhanced logging – log files
Enhanced logging – log files
Enhanced logging – log files
Typical Log Info/Errors
• Client's DB record about connected Server is incorrect/out
of sync. Possibly due to reconnect, failover, DB error:
• CSSProtocol::UpdateClientStatus Server IP mismatch Requesting Device
(KARENPVS01D), ID=13. Mismatching server IP AC16ECA5:AC16F036
• Client reconnect:
• CSSProtocol::DispatchServiceRequest Recv: LS_SERVICE_REQUEST from
device at IP:AC16533B. Reconnect=1
• DEBUG CSSProtocol::DispatchServiceRequest Re-using IO Context for device
at IP:AC16533B
Typical Log Info/Errors
• Client has no IO for a while, it is detached from the vdisk
(normal behavior):
• DEBUG CSSVirtualDisk::CheckQuietFile Close quiet file
\\172.17.129.148\cpvfs\HP7800_Vista321_Pilot
• Target device has sent heartbeat to server, but server
does not know anything about the target:
• ERROR Error - No connection found for heartbeat from device at IP:907443D9
Typical Log Info/Errors
StreamProcess threads hanging:
• DEBUG
CSSProtocolModule::CheckMonitorThreads 10 threads appear to be in danger of hanging
• TRACE
CSSProtocolModule::CheckMonitorThreads Thread TimerThread:170 [112c] appears to be
in danger of hanging, waiting since 1252533287 (for about 176 seconds) at
.\SSProtocolModule.cpp:1793
• TRACE
CSSProtocolModule::CheckMonitorThreads Thread SSProtocol:45 [11e8] appears to be in
danger of hanging, waiting since 1252533297 (for about 166 seconds) at
.\SSProtocol.cpp:367
• ERROR
CSSProtocolModule::CheckMonitorThreads Thread SSProtocol:43 [11e0] hung since
1252533272 (for about 241 seconds) at .\SSProtocol.cpp:883
• ERROR
CSSProtocolModule::DoLogEvent Detected one or more hung threads.Please send
Stream.log to support
• ERROR
CSSProtocolModule::DoLogEvent Terminating StreamProcess
• ERROR
CSSProtocolModule::CheckMonitorThreads 1 threads hung, 9 threads in danger
Typical Log Info/Errors
Expected Errors when there are Disk access issues for the
stores:
• ERROR
CManagedVdiskLock::Open - path_ = <\\stream1\I$\755_Update 4.lok>
• ERROR
CManagedVdiskLock::Open - in CManagedVdiskLock::Open, could not
open .lok file, last_error = 53
• ERROR
Error - Cannot get vdisk header for device at IP:C0A80661, DiskId=29
• ERROR
Error - Vdisk cannot be accessed for device at IP:C0A80661
Typical Log Info/Errors
Stream process started or restarted, a lot of configuration
settings like IP address and database:
• DEBUG
CSSProtocolModule::CreateNoEx Creating protocol module
• DEBUG
didn't get general inet addr from registry, falling back to ACE-provided value
• DEBUG
general inet addr is: <10.42.101.37:6909>
• DEBUG
host name: <D00510>
• DEBUG
Loaded db library <StreamDb>
• DEBUG
• DEBUG
computerName_ = <D00510>
about to read reg key <Software\Citrix\ProvisioningServices\Database> for
db settings
Typical Log Info/Errors
License server connection in the streamprocess startup:
• INFO
LicenseMgr::OnLSConnStatusChange Successfully contacted the license
server D00512.services.lab.vic.gov.au:27000
Offline vDisk Maintenance
• Mount PVS VHD files directly within Microsoft Hyper-V
• Easier vDisk Updating
• Especially vm-tools, PVS and network drivers
• Upgrade from previous PVS version to PVS 5.1 (and higher)
• Create Common Image between physical device and Hyper-V
• vDisk upgrade process Hyper-V (and XenServer (not supported))
• http://community.citrix.com/display/ocb/2009/07/28/New+Way+to+Upgrade+with+PVS+5.1+and+H
yperV
• http://community.citrix.com/display/ocb/2009/08/15/PVS+5.1+Direct+VHD+Boot+using+XenServer
Provisioning Services Readonly vDisk storage
Shared storage challenges
• MS cluster based (SMB shared folder) storage low performance, only
usable in smaller environments
• Connecting more than one Windows Server to the same NTFS
formatted LUN runs a high risk of disk corruption
• Clustered Shared Volumes introduced in Windows Server 2008 R2 is
only supported for Hyper-V VMs (by Microsoft)
• Until recently the ”only” workaround has been using 3rd party Cluster
File Systems like:
• Sanbolic’s Melio FS
• HP Polyserve
• Quantum StorNext
Read-only vDisk storage
• Improves system performance by allowing VHDs to be
deployed on read-only volumes, reducing disk I/O
• Simplifies deployment of standard image mode on SAN
and NAS devices
• Enables vDisk to reside on a shared LUN allowing
concurrent access by multiple servers
Read-Only vDisk Storage – Setup Process
Setup LUN
Mount iSCSI
volume on all
PVS Servers
Create Store
Install MS iSCSI
Initiator on PVS
Servers
Re-login to readonly volume
Add vDisks
through PVS
Console
Add Initiator to
iSCSI
Make volume
read-only
Login to SAN
from 1 PVS
Server only
Format volume
and copy vDisks
Read-only vDisk storage – Typical Architecture
Target Devices
Provisioning Services
Farm
SAN Array
LUN1 (NTFS R/O Shared)
vDisk 1 (v1)
Stream Network
Data Network
LUN2 (NTFS R/O Shared)
vDisk 2 (v1)
ode
M
e
ag
te Im
a
Priv
Ded
icat
ed
Acc
ess
LUN3 (NTFS R/W)
vDisk 2 (v2)
“Master” Target Device
Read-only vDisk storage – FAQ
• When should I choose this configuration?
• Environments that use SAN for vDisk storage and client-side write-back cache
(disk or RAM)
• Does this feature improve performance?
• Use of a read-only volume for vDisk storage eliminates overhead of normal PVS
disk locking mechanism (impact primarily visible during target device boot)
• Boot time performance is improved 25-50% depending on number of devices
booting concurrently (greater improvement achiveved with higher device counts)
Read-only vDisk storage – FAQ
• I need to use server side cache with my SAN storage. Can I
still use this feature?
• Yes, but you need a shared access solution to enable shared access to the volume
with the write-back cache files
• Can I use this feature with storage solutions other than SAN?
• Generally, this feature is not needed with other solutions (such as NAS or Windows File
System shares) as access to these devices is through CIFS or SMB which support safe
shared volume access
Read-only vDisk storage – FAQ
• Do we support FC SAN with read-only LUNs?
• There is no reason this should not work (as you said the LUN appears as a
drive to windows so PVS should have no problem using it) however it has not
been tested
• When using FC SAN is the iSCSI initiator software required?
• iSCSI initiator is not required, vendor specific software for FC device should be
used.
Scalability and Sizing Discussion
Disclaimer
• Does any number discussed next apply to my environment?
Sub-agenda
• XenApp and PVS
• XenDesktop and PVS
• General scalability and sizing
PVS Scalability - Streaming XenApp Farm
• PVS to deploy XenApp farm with physical and virtual
target “servers”
• Two questions:
• Is there a performance difference between a streamed and installed XA
• How many XenApp servers per PVS Server
Test 1: Streamed XA scalability
Streamed XenApp Server
XA 5 – Windows 2008
HP DL360G5
Single Intel Xeon 2.0 GHz Quad
Core Processor
8GB of RAM
2 internal 1GB network cards
Physical XenApp Server
ESLT Controller
Lenovo T60 2GHz CPU 2GB of RAM
ESLT Launchers
HP DL360G5
Single Intel Xeon 2.0 GHz Quad
Core Processor
8GB of RAM
2 internal 1GB network cards
XA 5 – Windows 2008
HP DL360G5
Single Intel Xeon 2.0 GHz Quad
Core Processor
8GB of RAM
2 internal 1GB network cards
• Word users
added
incrementally
• Excel user
runs during
stable load
00:02
00:04
00:06
00:08
00:10
00:12
00:14
00:16
00:18
00:20
00:22
00:24
00:26
00:28
00:30
00:32
00:34
00:36
00:38
00:40
00:42
00:44
00:46
00:48
00:50
00:52
00:54
00:56
00:58
01:00
01:02
01:04
01:06
01:08
01:10
01:12
01:14
01:16
01:18
01:20
01:22
01:24
01:26
01:28
01:30
01:32
01:34
01:36
Test: Word and Excel users
90.0
80.0
70.0
60.0
50.0
40.0
30.0
20.0
10.0
0.0
Word Users
Citrix Confidential - Do Not Distribute
Excel Users
The Results….
Average it took to run excel script on each XenApp system
Citrix Confidential - Do Not Distribute
Results – Streamed vs Physical XenApp Server
• Script exectuion times were not any different.
• CPU utilization on average was no greater than physical box
• Processor queue length was almost consistent between the
2 machines
• In the series of tests conducted no measurable impact on:
• User density
• Stability of a streamed XenApp environment
Citrix Confidential - Do Not Distribute
Test 2: How many Streamed XenApps / PVS server
• Architectural Components:
• 1 PVS Server
• 1 dedicated SQL Server
• 5 vDisks to accommodate physical and virtual scenarios
• Storage:
• vDisks on PVS Server
• Write cache on client side
• Hardware
• 3 different major HW vendors
• XS Virtual Machines
Provisioning Server specifications
• Vendor/Model: HP ProLiant DL360 G5
• Processor: Two quad-core Intel Xeon CPU E5335 @ 2.00GHz
• Memory: 16 GB FB-DDR2, PC2-5300 (333 MHz)
• Disks: 6 disks 72GB 15k configured as:
• C: 2 disks, RAID 0 array, OS and PVS install
• F: 4 disks, RAID 0 array, local VHD store
• Network Adapter: 2 HP NC373i Multifunction Gigabit Server
Key findings
• Large numbers of streamed XenApp servers from a single
virtual hard disk under load have little impact on PVS:
• When streamed image activity is cached, PVS load is negligible once
initial connections are established
• Server caching affects Provisioning Server load:
• Number of vDisks / PVS Server increases network and CPU load
Citrix Confidential - Do Not Distribute
Analysis
• One PVS Server can handle well over 700 XenApp Servers
• Always deploy two PVS servers at the minimum for HA
• Limiting factor was the network in this test, server resrouces not maxed out
• A mixed physical/virtual stream target environment does not
present any issues from a single Provisioning Server
• Local HDD cache: preferred model for XenApp with PVS
• Scalability depends on many factors, primarily network
bandwidth, but also storage hardware affect performance
and capacity
Citrix Confidential - Do Not Distribute
XenDesktop and PVS
PvS 5.0 SP21
# Desktops / PvS Server
Hosted
desktops
Local
desktops
500 - 750 desktops 250 - 450 desktops
per PvS server 2
per PvS server 3
All figures derived from Citrix proprietary methodology - provided for sizing
guidance only, NOT suitable for comparative purposes
Notes:
1
Running on Windows Server 2008 64bit (for enhanced caching capability)
2
Write-back cache on local VM storage (ie. on shared storage)
3
Lack of separation of bootup vs logon events impacts concurrency. Also, diskless-endpoints
require handling of write-back cache through PvS server
• Hardware – Dual quad core, 2.3 GHz, 8 GB RAM, dual 1Ge NICs
• Network throughput generally the bottleneck - RAM and CPU not limiting factors
Things to consider in sizing
• Avoid / plan for boot storms
• At boot
• Large application start-up
• Write cache sizing and placement
• Use SAN or local storage over CIFS shares
Boot storms
• When a large number of devices boot up or applications
are started simultanously
• Network bandwidth consumed by streamed server/desktop
target devices upon boot:
• About 60-80 MB per desktop image and 100-120 MB per server image to
boot is a base calculation typically used
• Newer OSs require up to 200 MB to get up to normal operation
Control the boot storm by Boot Pacing
• Performance required per vDisk
can be tailored with the Server's
"Boot Pacing" parameter
• Pull down the Maximum
devices booting to 50 or even
lower if needed.
Write cache discussion
• Write cache placement
• When possible use client side to reduce network traffic
• Client side RAM is not recommended as target device will freeze when RAM
fills up
• If client side write cahce fills up it will fail over to server side
• Will cause freeze if using Read Only vDisk storage
• If using server side, plan for the extra network load
• Write cahce sizing
• Use server side caching to get a good estimate, and then add some headroom
• Max size is the size of the vDisk
• Huge cache files often indicates a misconfiguration (Indexing services, AV...)
Write cache discussion
• Write cache perfromance
• A slow write cache has a huge impact on performance
• Try to do sizing on the IOPS / target to get a number to help you size your Wc
disk system
• A general number in XenDesktop environment is 30 IOPS / target
• To check whether a performance issue is Wc related,
temporary switch to RAM cache and redo the test
Local and Remote concurrent I/O limits
• PVS service is a highly multi-threaded
service, it can send hundreds of
simultaneous I/O requests to a given
storage device
• I/O requests are usually queued up by
the storage device and processed
when time permits. Some storage
devices, Windows Network Shares
most notably, do not deal with hits of
large number of concurrent requests
well
Local and Remote concurrent I/O limits
• Using fast drives you can
raise the number of
concurrent I/Os
• In extremely fast disk
systems you can remove the
limit (Limit = 0)
• When using slow shares or
disks and see retries at high
load or boot storms, lower the
concurrent I/O to 3 or lower.
PVS ports 6910-6930 for I/O operations
• If we have 150 devices, around 40 devices per PVS Server,
should this value be changed in case of PVS server outage?
• The important thing to know is that stream service has multiple threads per port which is
different from a typical network application where there is one port per client
• PVS will be able to handle all 150 targets using this port range
PVS Scalability numbers
• Max number of server/desktop target devices per vDisk
varies based on:
1.
2.
3.
4.
5.
Storage performance characteristics: drive speeds, IOPS capacity
Network between PVS servers and storage (if any)
# of PVS servers
Network between PVS servers and target devices
Number of copies of vDisk being used (i.e. if you distribute)
Recommendations for better scalability
• Network is generally the most significant bottleneck:
• Whenever possible, minimizing network traffic between the Provisioning
Server (PVS) and target device should be completed
• Additionally, the network used for streaming PVS based images should be
dedicated to PVS strictly PVS traffic, when possible
• Use vendor-based NIC teaming
• When possible, use vendor-based NIC teaming to reduce CPU load on the
Provisioning Server if there are more than 2 NICs or there are NICs with
multiple ports
• More NICs are generally better, as long as the network is capable of handling
the throughput
Recommendations for better scalability
• Memory is heavily used by PVS:
• Since read disk blocks are stored in the Windows system cache, a 64-bit server
will provide performance benefits over 32-bit systems when additional memory
is present, especially in environments with a large vDisk or more than one vDisk
• Windows Server 2008 handles memory better than
Windows Server 2003
• NOTE: Windows Server 2008 R2 not currently supported.
Scalability Documents
• PVS 5.0 with XenDesktop 2.1 Scalability Analysis
• CTX119286 – PVS High Availability Considerations
• CTX115460 – Delivering a Highly Available Citrix Provisioning
Server using Storage Technologies
• CTX117922 – XenApp and XenServer – Reference Architecture
• CTX120464 – Provisioning Services for XenApp Best Practices
Provisioning Services
A few words on streaming
XenApp
Normal XenApp image build and deployment
EdgeSight
EdgeSight
EdgeSight
EdgeSight
XenAppPrep
XenAppPrep
XenAppPrep
XenAppPrep
Apps & Conf
Apps & Conf
Apps & Conf
Apps & Conf
XenApp
XenApp
XenApp
XenApp
OS
OS
OS
OS
vDisk build
Private mode
AD PWD Mgmt
Standard mode
AD PWD Mgmt
Deployed to all targets
Local Disk
XenAppPrep /pvs
Other de-personalistaion
Challenge 1: Update to image
In some cases:
• IMA not starting
• Domain membership issues
EdgeSight
EdgeSight
XenAppPrep
XenAppPrep
Apps & Conf
Apps & Conf
Apps & Conf
XenApp
XenApp
XenApp
OS
OS
OS
Standard mode
Deployed to all targets
AD PWD Mgmt
Convert to Private mode
Deploy to one target
AD PWD Mgmt
XenAppPrep /pvs
Other de-personalistaion
Convert to Standard
Deploy to all targets
AD PWD Mgmt
EdgeSight
XenAppPrep
Copy
Challenge 2:
Updating PVS or NIC drivers (XenTools, VMWare...)
EdgeSight
EdgeSight
XenAppPrep
XenAppPrep
Apps & Conf
Apps & Conf
Apps & Conf
XenApp
XenApp
XenApp
OS
OS
OS
AD machine account
PWD managed by PVS
AD machine account pwd
NOT managed by PVS
- Rejoin domain
- Possible IMA problems
- Update drivers
- De-personalistaion
Standard mode
AD PWD Mgmt
(Reset AD PWD in PVS
for the machine account
used)
EdgeSight
XenAppPrep
Reverse image/
Load in Hyper-V
Proposed solution that works
Updates to the vDisk would start here by
taking a copy of the private vDisk and starting
it up on the Template Management Machine
EdgeSight
XenAppPrep
Copy
XenAppPrep
Apps & Conf
Apps & Conf
XenApp
XenApp
OS
OS
OS
Local Disk
vDisk build
Private mode
NO AD PWD Mgmt
Install EdgeSight
XenAppPrep /pvs
Other de-personalistaion
Standard mode
AD PWD Mgmt
Deploy to all except
Template Mgmt Machine
• No problems with AD machine account pwd
• Will work with problematic apps / confs
• Easier updates to vDisks
Provisioning Services for XenApp
• CTX116063 – XenAppPrep Integration Utility for XenApp /
Presentation Server
• https://iguide.citrite.net/.Groups/Integrated_Solutions/Provisi
oning_Services_for_XenApp
• XenApp Cloning Tool:
• http://www.citrixtools.net/en/Downloads.aspx
Citrix Confidential - Do Not Distribute
Provisioning Services Resources
• CTX120464 – Provisioning Services for XenApp Best
Practices
• CTX120760 – XenDesktop Design Handbook
Citrix Confidential - Do Not Distribute
Fresh CCS "issues"
Issues on recent Consulting projects XA/XS/PVS
Issue
Provisioning
Services vDisk
capture
Windows Server
2003 Boot
Description
Follow-up/Resolution
•When attempting to capture the vDisk
image on any server, the server
seems to lose connection with vDisk
and image cannot be captured
•Symantec Endpoint Protection on PVS server
gives an error stating "Traffic from IP address
<XAServer> is blocked…" "[SID: 20087] Fizzer
Worm Propagation (UDP) Detected“
•Symantec Endpoint Protection was disabled on
PVS server and was successfully able to capture
vDisk image
•XenApp servers often do not boot on
the first attempt
•An error is encountered stating that
Windows cannot be found
•Assumption is a timing issue with
Provisioning Services streaming
•Verified all NICs and switches are set to 1Gbps
Full Duplex however this has not resolved the issue
•New server was built using XenServer template
and new vDisk was created from this server
•vDisk showing the error will no longer be used
Issues on recent Consulting projects XA/XS/PVS
• Time Synchronization:
• Make sure time synchronization is functioning with all servers as Kerberos ticketing will fail if off
by more than 5 minutes
• Causing issues with user authentication and machine authentication to AD
• Driver Issues:
• HP iLo drivers causing servers to randomly reboot
• Caution using RAM Cache:
• If you run out of memory, the server will halt. Even with proper planning, there is the possibility
of memory leaks and runaway processes that can quickly deplete the RAM cache
• A better option is to use local machine storage
Issues on recent Consulting projects XA/XS/PVS
• SMB Issue in Windows:
• If Windows 2008 or Vista tries to access the same resources via SMB, the
computer might stop responding. There is a fix for this that can be downloaded
from here: http://support.microsoft.com/kb/972596/
Citrix Confidential - Do Not Distribute
Provisioning Services 5.1SP 1
PVS 5.1 SP1
• Feature List:
• License Changes
• Streaming of VM Hosted Apps in XenApp
• XenDesktop native license file support
• Hotfix Rollup
*Subject to change
PVS 5.1 – Service Pack 1 – New in this release
• Linux Ubuntu support
• Windows 7 support
• Unified Edition
• Licensing
• XenConvert 2.0.2 (CTX121646)
Citrix Confidential - Do Not Distribute
Pre SP 1 PVS Licensing Actions with
XenApp Platinum
1. PVS Streamed
Server Boots
4. PVS Client checks
for XenApp Edition
2. PVS Client waits up
to 3 hours for IMA to
Start
5. Reports Edition to
PVS Server
3. IMA Service Starts
6. PVS Server checks
for XenApp License
7. PVS Server
checks SA date
PVS Licensing Actions – SP 1
1. PVS Streamed
Server Boots
4. PVS Client checks
for XenApp Edition
2. PVS Client waits up
to 3 hours for IMA to
Start
5. Reports Edition to
PVS Server
3. IMA Service Starts
6. PVS Server checks
for XenApp License
7. PVS Server
checks SA date
PVS Licensing Actions – SP1
1. PVS Server checks
license type
2. PVS Server checks
SA date
3. PVS Server starts
streaming
PVS 5.1 – SP1 – Licensing details
• XenApp Platinum:
• Unlimited provisioning of any and all physical/virtual servers associated with
the XenApp deployment
• Provisioning of desktop sessions being used to support VM Hosted Apps
• No physical/virtual desktop provisioning
• XenApp Enterprise:
• Provisioning of desktop sessions being used to support VM Hosted Apps
• No physical/virtual provisioning
• No physical/virtual desktop provisioning (other than VM Hosted App sessions)
PVS 5.1 – SP1 – Desktop Grade OS part of XenApp
• Windows XP
• Windows Vista
• Windows 7 (KMS 1.1 current support model)
PVS 5.1 – SP1 – Licensing details
• XenDesktop Enterprise:
• Provisioning of any physical/virtual desktop associated with the XenDesktop
deployment, including:
• Virtual hosted desktops running the primary OS session
• Physical streamed desktops running the primary OS session
• Physical desktops, desktop appliances, or thin clients used to access a virtual hosted
desktop
• No physical/virtual desktop provisioning
PVS 5.1 – SP1 – Licensing details
• XenDesktop Platinum:
• Unlimited provisioning of any and all physical/virtual servers associated with
the XenDesktop deployment
• Provisioning of any physical/virtual desktop associated with the XenDesktop
deployment, including:
• Virtual hosted desktops running the primary OS session
• Physical streamed desktops running the primary OS session
• Physical desktops, desktop appliances, or thin clients used to access a virtual hosted
desktop
• CTX117378 - Provisioning Server and Citrix License Server
Interaction FAQ (PVS 5.1 – SP1)
… going forward
The Future… What we are looking at
• Windows 2008 R2 Support
• Enhanced image management
• Read-only FileSystem v2
• And lot’s of other cool features
• Possible Tech Preview end of
this year
• Release: 1st half of next year
(subject to change)
*Subject to change
Questions?
(and hopefully also answers)