Citrix VDI Handbook for XenApp and XenDesktop 7.15


Almost one year ago, I announced the availability of the Citrix VDI Best Practices Handbook for XenApp and XenDesktop 7.6 (that’s a really long title).

Since then, I received many positive comments from many of you. Thank you.

One of the goals I set was to release an updated version of the handbook for upcoming Long Term Service Releases (LTSR). And with the release of XenApp and XenDesktop 7.15 LTSR, I’m happy to say that we achieved this goal.

Matthew Brooks, Jeff Qiu and I updated the handbook to include new capabilities and recommendations. We added 30 new sections and updated 15 other sections. For example, we have content related to

  1. Cloud
  2. App Layering
  3. Windows 2016
  4. Local Host Cache
  5. Machine Creation Services
  6. Provisioning Services Accelerator
  7. Adaptive Display & Adaptive Transport
  8. And much, much, much, much, much more

A complete list of updates can be found at the end of the paper in the Revisions Table.

So grab a drink, find a comfy chair, sit back, relax and enjoy the Citrix XenApp and XenDesktop 7.15 VDI Best Practices Handbook.

Daniel (Follow on Twitter @djfeller)
Citrix XenApp and XenDesktop 7.15 VDI Handbook
XenApp Best Practices
XenApp Videos

 

Advertisements

2 thoughts on “Citrix VDI Handbook for XenApp and XenDesktop 7.15”

  1. Hi Daniel! Congratulations to you, Matthew and Jeff on the handbook! Outstanding work! Regarding PVS threads/ports, is it possible to elaborate on scaling up? In the handbook, it states the following:

    ###
    Max Number of Streams = # of Ports * # of Threads/Port

    By default, the Streaming Service is configured with 20 sequential network ports, and 8 threads
    per port. Therefore, by default, a provisioning server can support 160 concurrent targets.

    Best performance is attained when the threads per port is not greater than the number of cores available on the provisioning server.

    Larger environments 8 vCPUs are recommended.
    ###

    If I build an 8 vCPU PVS server, the maximum number of targets by default is 160 as pointed out in the handbook. There was a Citrix blog a while ago in which the sequential network port range was increased to 6910 – 6968 for a total of 55 ports (first 3 ports are reserved according to the blog) . Using the formula above that means a maximum of 440 targets.

    Am I correct in understanding that I would need to increase the number of vCPUs on the PVS server before increasing the threads per port? Is that the recommended method to scale past 160 default targets or 440 targets (after modifying the port range) on an 8 vCPU PVS server? Or is it better to scale out once you reach 400 or so targets per 8vCPU PVS server?

    Like

    1. You can increase ports or threads. Ports is much easier to increase than threads because for best performance, your threads should equal the number of vCPU of your PVS server. And keep in mind that PVS doesn’t use the CPU very hard, so from a PVS perspective, adding more vCPU might be wasteful.

      That being said, PVS will scale well beyond the 160 targets with the default config. It will work fine. However, by tweaking the ports/threads, you can make it work a little faster as Jeff posted in his blog https://www.citrix.com/blogs/2016/03/30/updated-guidance-on-pvs-ports-and-threads/

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s