Catalogs, Delivery Groups, Zones

Last Modified: Oct 12, 2016 @ 9:35 am


ūüí° = Recently Updated


This section details how to create zones and put resources in those zones. In 7.9 and older, there’s no way to select a zone when connecting. In 7.11 and newer, NetScaler and StoreFront can now specify¬†a zone and VDAs from that zone will be chosen. See Zone Preference for details.

Citrix Links:

There is no SQL in Satellite zones. Instead, Controllers in Satellite zones connect to SQL in Primary zone. Here are tested requirements for remote SQL connectivity. You can also set HKLM\Software\Citrix\DesktopServer\ThrottledRequestAddressMaxConcurrentTransactions to throttle launches at the Satellite zone.

From Mayunk Jain: “I guess we can summarize the guidance from this post as follows: the best practice guidance has been to recommend a datacenter for each continental area. A typical intra-continental latency is about 45ms. As these numbers show, in those conditions the system can handle 10,000 session launch requests in just under 20 minutes, at a concurrency rate of 36 requests.”

If Satellite zone loses connectivity to SQL, then the Connection Leasing feature kicks in. See Connection leasing and CTX205169 FAQ: Connection Leasing in XenApp/XenDesktop 7.6 for information on Connection Leasing limitations (e.g. no pooled virtual desktops, 2 week-old leases, etc.).

The following items can be moved into a satellite zone:

  • Controllers ‚Äď always leave two Controllers in the Primary zone. Add one or two Controllers to the Satellite zone.
  • Hosting Connections ‚Äď e.g. for vCenter in the satellite zone.
  • Catalogs ‚Äď any VDAs in satellite catalogs automatically register with Controllers in the same zone.
  • NetScaler Gateway ‚Äď requires StoreFront that understands zones (not available yet). StoreFront should be in satellite zone.

Do the following to create a zone and move items into the zone:

  1. In Studio 7.7 or Studio 7.8, expand the Configuration node and click Zones.
  2. If you upgraded from an older XenApp/XenDesktop and don’t see zones, then run the following commands:
    cd 'C:\Program Files\Citrix\XenDesktopPoshSdk\Module\Citrix.XenDesktop.Admin.V1\Citrix.XenDesktop.Admin\StudioRoleConfig'
    Import-AdminRoleConfiguration ‚ÄďPath .\RoleConfigSigned.xml
  3. Right-click Zones and click Create Zone.
  4. Give the zone a name. Note: Citrix supports a maximum of 10 zones.
  5. You can select objects for moving into the zone now, or just click Save.
  6. Select multiple objects, right-click them, and click Move Item.
  7. Select the new Satellite zone and click Yes.
  8. To assign users to the new zone, create a Delivery Group that contains machines from a Catalog that’s in the new zone. There is no Zone Preference and Failover option in this release.
  9. If your farm has multiple zones, when creating a hosting connection, you’ll be prompted to select a zone.
  10. If your farm has multiple zones, when creating a Manual catalog, you’ll be prompted to select a zone.
  11. MCS catalogs are put in a zone based on the zone assigned to the Hosting Connection.
  12. The Provisioning Services XenDesktop Setup Wizard ignores zones so you’ll have to move the PvS Machine Catalog manually.
  13. New Controllers are always added to the Primary zone. Move it manually.

Zone Preference

XenApp/XenDesktop 7.11 adds Zone Preference, which means NetScaler (11.0 build 65 and newer) and StoreFront (3.7 and newer) can request XenDesktop Controller to provide a VDA in a specific zone.

However, 7.11 does not have any offline database capability. If you are stretching a farm across datacenters, I still recommend separate farms in each datacenter. Hopefully offline database is addressed in a future release of XenApp/XenDesktop.

To configure zone preference:

  1. Create separate Catalogs in separate zones, and add the machines to a single Delivery Group.
  2. You can add users to one zone by right-clicking the zone, and clicking Add Users to Zone. If there are no available VDAs in that preferred zone, then VDAs are chosen from any other zone.
  3. Note: a user can only belong to one zone.
  4. You can delete users from a zone, or move users to a different zone.
  5. If you edit the Delivery Group, on the¬†Users page, you can specify that¬†Sessions must launch in a user’s home zone.
  6. For published apps, on the Zone¬†page,¬†you can configure it to ignore the user’s home zone.
  7. You can also configure a¬†published app with a preferred zone, and force it to only use VDAs in that zone. If you don’t check the box, and if no VDAs are available in the preferred¬†zone, then VDAs can be selected from any other zone.
  8. Or you can right-click on a zone, and configure multiple Applications to use that zone as preferred.

  9. NetScaler can specify the desired zone by inserting the X-Citrix-ZonePreference header into the HTTP request to the StoreFront 3.7 server. StoreFront 3.7 will then forward the zone name to Delivery Controller 7.11, which will select a VDA in the desired zone. This functionality can be combined with GSLB as detailed in the 29 page document Global Server Load Balancing (GSLB) Powered Zone Preference. Note: only StoreFront 3.7 and newer will send the zone name to the Delivery Controller.

MCS – Full Clones

In XenApp/XenDesktop 7.9 and earlier, Persistent Linked Clones are created by selecting¬†Yes, create a dedicated virtual machine in the Create Catalog wizard. Please, never do this in 7.9 or earlier, since you can’t move the machines once they’re created. A much better option is to use vCenter to do Full Clones of a template Virtual Machine. Then when creating a Catalog, select¬†Another service or technology to add the VMs that have already been built.

In XenApp/XenDesktop 7.11 and newer, you can create MCS Full Clones. Full Clones are a full copy of a template virtual machine. The Full Clone can then be moved to a different datastore (including Storage vMotion), different cluster, or even different vCenter. You can’t do that with Linked Clones.

For Full Clones, simply prepare a Master Image like normal. There are no special requirements. There’s no need to create Customization Specifications in vCenter since¬†Sysprep is not used. Instead, MCS uses it’s identity technology to change the identity of the full clone. That means every full clone has two disks: one for the actual VM, and one for identity (machine name, machine password, etc).

During creation of a Full Clones Catalog, MCS still creates the master snapshot replica and ImagePrep machine, just like any other linked clone Catalog. The snapshot replica is then copied to create the Full Clones.

In 7.11 and newer, during the Create Catalog wizard, if you select Yes, create a dedicated virtual machine:

After you select the master image, there’s a new option for¬†Use full copy for better data recovery and migration support. This is the option you want. The¬†Use fast clone option is the older, not recommended, option.

Since these are Full Clones, once they are created, you can do things like Storage vMotion.

During Disaster Recovery, restore the VM (both disks). You might have to remove any Custom Attributes on the machine, especially the XdConfig attribute.

Inside the virtual machines, you might have to change the ListOfDDCs registry value to point to your DR Delivery Controllers. One method is to use Group Policy Preferences Registry.

In the Create Catalog wizard, select Another Service or technology.

And use the Add VMs button to add the Full Clone machines. The remaining Catalog and Delivery Group steps are performed normally.

MCS – Machine Naming

Once a Catalog is created, you can run the following commands to specify the starting count:

Set-AcctIdentityPool -IdentityPoolName "NAME" -StartCount VALUE

MCS – Memory Caching (XenApp/XenDesktop 7.9 and newer)

Memory caching in MCS is very similar to Memory caching in PvS. All writes are cached to memory instead of written to disk. With memory caching, some benchmarks show 95% reduction in IOPS. Here are some notes:

  • You configure a size for the memory cache. If the memory cache is full, it overflows to a cache disk.
  • Whatever memory is allocated to the MCS memory cache is no longer available for normal Windows operations, so make sure you increase the amount of memory assigned to each virtual machine.
  • The overflow disk (temporary data disk) can be stored on shared storage, or on storage local to each hypervisor host. Since memory caching dramatically reduces IOPS, there shouldn’t be any problem placing these overflow disks on shared storage. If you put the overflow disks on hypervisor local disks then you won’t be able to vMotion the machines.
  • The overflow disk is uninitialized and unformatted. Don’t touch it. Don’t format it.
  • For¬†a good overview of the feature, see Citrix Blog Post¬†Introducing MCS Storage Optimization¬† ūüí°
  • Andrew Morgan¬†Everything you need to know about the new Citrix MCS IO acceleration¬†details the performance counters that show¬†memory cache and disk cache usage.


Memory caching requirements:

  • XenApp/XenDesktop 7.9, VDA 7.9, and newer
  • Random Catalogs¬†only (no dedicated Catalogs)


Studio needs to be configured to place the temporary overflow disks on a datastore. You can configure this datastore when creating a new Hosting Resource, or you can edit an existing Hosting Resource.

To create a new Hosting Resource:

  1. In Studio, go to Configuration > Hosting, and click the link to Add Connection and Resources.
  2. In the Storage Management page, select shared storage.
  3. You can optionally select¬†Optimize temporary data on local storage, but this might prevent vMotion. The temporary data disk¬†is only accessed if the memory cache is full, so placing the temporary disks on shared storage shouldn’t be a concern.
  4. Select a shared datastore for each type of disk.

Or you can edit an existing Hosting Resource:

  1. In Studio, go to Configuration > Hosting, right-click an existing resource, and click Edit Storage.
  2. On the Temporary Storage page, select a shared datastore for the temporary overflow disks.

Memory caching is enabled when creating a new Catalog. You can’t enable it on existing Catalogs. Also, no AppDisks.

  1. For virtual desktops, in the Desktop Experience page, select random.
  2. Master Image VDA must be 7.9 or newer.
  3. In the Virtual Machines page, allocate some memory to the cache. For virtual desktops, 256 MB is typical. For RDSH, 4096 MB is typical. More memory = less IOPS.
  4. Whatever you enter for cache memory, also add it to the Total memory on each machine.
  5. Once the machines are created, add them to a Delivery Group like normal.
  6. The temporary overflow disk is not initialized or formatted.¬†From Martin Rowan at “Don’t format it, the raw disk is what MCS caching uses.”

MCS – Image Prep

From Citrix Discussions: When a Machine Creation Services catalog is created or updated, a snapshot of the master image is copied to each LUN. This Replica is then powered on and a few tasks are performed like KMS rearm and Personal vDisk enabling.


From Citrix Blog Post Machine Creation Service: Image Preparation Overview and Fault-Finding: here are some PowerShell commands to control what Image Prep does: (run asnp citrix.* first)

  • Set-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps -Value EnableDHCP
  • Set-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps -Value OsRearm
  • Set-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps -Value OfficeRearm
  • Set-ProvServiceConfigurationData -Name ImageManagementPrep_DoImagePreparation -Value $false

If multiple excluded steps, separate them by commands: -Value "OsRearm,OfficeRearm"

To remove the excluded steps, run Remove-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps


From Mark Syms at Citrix Discussions: You can add one (or both) of the following MultiSZ registry values

  • HKLM\Software\Citrix\MachineIdentityServiceAgent\ImagePreparation\Before
  • HKLM\Software\Citrix\MachineIdentityServiceAgent\ImagePreparation\After

The values are expected to be an executable or script (PoSh or bat), returning 0 on success


Citrix CTX140734 Error: ‚ÄúPreparation of the Master VM Image failed‚ÄĚ when Creating MCS Catalog in XenApp or XenDesktop: To troubleshoot image prep failures, do the following:

  1. In PowerShell on a Controller, run:
    asnp citrix.*
    Set-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown -Value $True
  2. On the master image, set the DWORD registry value HKLM\Software\Citrix\MachineIdentityServiceAgent\LOGGING to 1
  3. If you now attempt catalog creation, an extra VM will be started; log into this VM (via the hypervisor console, it has no network access) and see if anything is obviously wrong (e.g. it’s bluescreened or something like that!). If it hasn’t there should be two log files called “image-prep.log” and “PvsVmAgentLog.txt” created in c:\ – scan these for any errors.
  4. When you’ve finished doing all this debugging, remember to run:
    Remove-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown

Delivery Groups in 7.8 and newer

In XenApp/XenDesktop 7.8, when creating a Delivery Group, there are new options for publishing applications and publishing desktops.

On the Applications page of the Create Delivery Group wizard, From start menu reads icons from a machine in the Delivery Group and lets you select them. Manually lets you enter file path and other details manually. These are the same as in prior releases.

Existing is the new option. This lets you easily publish applications across multiple Delivery Groups.

You can also go to the Applications node, edit an existing application, change to the Groups tab, and publish the existing app across additional Delivery Groups.

Once multiple Delivery Groups are selected, you can prioritize them by clicking the Edit Priority button.

On the Desktops page of the Create Delivery Group wizard, you can now publish multiple desktops from a single Delivery Group. Each desktop can be named differently. And you can restrict access to the published desktop.

There doesn’t seem to be any way to publish a Desktop across multiple Delivery Groups.

It’s still not possible to publish apps and desktops across a subset of machines in a¬†Delivery Group. But the new method of publishing apps across multiple Delivery Groups should make it easier to split your machines into multiple Delivery Groups.

RDSH Scheduled Restart

  1. Once an RDSH Delivery Group is created, you can right-click it and click Edit Delivery Group.
  2. The Restart Schedule page lets you schedule a restart of the session hosts.
  3. XenApp 7.7 and newer lets you send multiple notifications.


Or use a reboot script:

Multiple Sessions

From Configure session roaming at By default, users can only have one session. On XenApp 7.6 (experimental support) and XenApp 7.7+ (full support), you can configure SessionReconnection setting available via PowerShell.  On any Server OS delivery group, run:

Set-BrokerEntitlementPolicyRule <Delivery Group Name> ‚ÄĎSessionReconnection <Value>

Where <Value> can be:

  • Always – This is the default and matches the behavior of a VDI session.¬† Sessions always roam, regardless of client device.
  • DisconnectedOnly – This reverts back to the XenApp 6.x and earlier behavior.¬† Sessions may be roamed between client devices by first disconnecting them (or using Workspace Control) to explicitly roam them.¬† However, active sessions are not stolen from another client device, and a new session is launched instead.
  • SameEndpointOnly – This matches the behavior of the “ReconnectSame” registry setting in XenApp 6.x.¬† Each user will get a unique session for each client device they use, and roaming between clients is completely disabled.

This will change the roaming behavior for desktop sessions.  For app sessions, use:

Set-BrokerAppEntitlementPolicyRule <Delivery Group Name> ‚ÄĎSessionReconnection <Value>

Static Catalog – Export/Import Machine Assignments

It is sometimes useful (e.g. DR) to export machine assignments from one Catalog/Delivery Group and import to another.

From Adil Dean at Exporting Dededicated VDI machine names and user names from catalog in Xendesktop 7.x at

Hopefully this is what you are after, it turns out you don’t actually need PowerShell as the functionality is built into the tool.

  1. In Studio, click Delivery Groups on the lefthand menu
  2. Right click Edit delivery group
  3. Select Machine allocation tab on the left
  4. Click Export list
  5. Select a file name > Click Save
  6. Create the new machine catalog
  7. Right click the delivery group > Click Edit
  8. Select Machine allocation tab on the left
  9. Click Import list..
  10. Select the list you exported in step 4
  11. Click Apply

Your clients will now have users re-assigned to machines.

Monitor the Number of Free Desktops

Sacha Thomet wrote a script at victim of a good reputation ‚Äď Low free pooled XenDesktops that polls Director to determine the number of free desktops in a Delivery Group. If lower than the threshold, an email is sent.

Related Topics

Email this to someonePrint this pageTweet about this on TwitterShare on LinkedInShare on FacebookPin on PinterestShare on RedditShare on StumbleUpon

50 thoughts on “Catalogs, Delivery Groups, Zones”

  1. Carl,

    I actually found that using ‘Set-ProvServiceConfigurationData -Name ImageManagementPrep_ExcludedSteps’ does not work. Using ‘Set-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps’ works for me.


  2. Hi,

    One of my MCS servers computer object got deleted from AD and now MCS server showing unregistered. Is it possible to remove the machine from domain and rejoin? or do i need to create new machine from base image?


  3. Hi Carl,

    you mentioned the following
    During Disaster Recovery, restore the VM (both disks). You might have to remove any Custom Attributes on the machine, especially the XdConfig attribute.

    Now, This will be a huge manual effort and will require a significant time if we are talking for 5000+ VDI or can we automate it.

    Just wanted to understand can we do the following with full clone

    create VMs in both DC and no storage is attached to the DR VMs. In the event of a failure, these VMs disk will be assigned from the backup storage location. the storage for each VM will be made available from the latest storage backup of the dedicated VMs and to be attached individually to the pre-created VMs which is already present.

    Please let me know your inputs.

    Kind Regards,
    Nivesh Pankaj

    1. They’re just regular VMs so you can do anything that normally works for a VM.

      As for the attribute, there might be a PowerCLI option. Let me do more research.

  4. Carl,

    Setting up a new XA 7.11 site. I’ve been through XA 6.5, XD 5.6, XD 7.6, and now XA 7.11. This time when I go to create an MCS-based machine catalog I don’t see any option to specify CPU (this has changed). What is the recommended way to set your socket/core count for the catalog? I also don’t see networking anymore? If everything is setup in the base image will it properly propagate?


    1. Networking comes from the Hosting Resources.

      I think CPU was intentionally removed. Can’t remember which version. But it should copy from the master.

  5. Hello Carl,

    I have XenDesktop 7.8 setup. Some of my MCS servers are moved to different vCenter but on same Cluster, Storage and Virtual network and now power status is unknown. Only vCenter server is changed.

    I have two hosting connections for those two vCenter (vCenter1 and vCenter2). The vCenter1 is the previous vCenter on which MCS servers were hosted. On vCenter 1 I can see Resources connection but not showing storage as it is moved to vCenter2.

    On vCenter2, I don’t have any resources connection set up yet but have VDI’s and Servers hosted manually on it.

    I am thinking to rename Resource on vCenter1 and then create new Resource with the same name (same cluster, storage and virtual network) on vCenter 2. vCenter2 hosting connection was created with other tools (not with Studio tools Machine Creation Service). Can I create Resources connection for MCS servers under same existing connection or should I create new hosting connection with vCenter 2 for MCS servers?

    Is it possible to update the MCS servers hosting connection details with Powershell commands after creating new hosting connection-resource and get power status?


    1. If the UUIDs change in vCenter then it probably won’t work.

      To move MCS, you basically have to rebuild them. If Dedicated MCS, you can clone them to Full Clones, then add them to a Manual Catalog.

      1. I get following entries which looks same.

        Get-BrokerMachine -PowerState Unknown –HostedMachineId : 422e2e47-6da9-69b1-cb74-0ff0b1427bad
        Vmx file entry for MCS server — uuid.bios = “42 2e 2e 47 6d a9 69 b1-cb 74 0f f0 b1 42 7b ad”

        Can I update it with Set-BrokerMachine -MachineName ‘MyDomain\MyMachine’ -HostedMachineId

        Also please share your thoughts on below point.

        I am thinking to rename Resource on vCenter1 and then create new Resource with the same name (same cluster, storage and virtual network) on vCenter 2. vCenter2 hosting connection was created with other tools (not with Studio tools Machine Creation Service). Can I create Resources connection for MCS servers under same existing connection or should I create new hosting connection with vCenter 2 for MCS servers?


        1. If you look inside the .vmdk file, it has a pointer to the parent image. If the path doesn’t change, then it might work.

          Yes, you can add Hosting Resource to an existing Connection.

          1. My base image is also moved from vCenter 1 to vCenter 2 on same cluster, storage and virtual network where MCS app servers are.

            Is it the right command to update -> Set-BrokerMachine -MachineName ‚Äėxyz\Server1‚Äô -HostedMachineId 422e2e47-6da9-69b1-cb74-0ff0b1427bad

          2. The connection will work, but the machines probably won’t. MCS has many links and dependencies and can’t be easily moved. You usually have to recreate them.

          3. In this case i need to rebuild MCS servers. Please check below steps. Is there anything I m missing?

            * Create new hosting connection and resources
            * Create new Machine Catalog with a single server using the existing base image snapshot
            * Add the newly created server to the existing Delivery Group
            * Put existing servers in maintenance mode and check apps on new server
            * Add additional servers to new Machine Catalog
            * Add new servers to existing Delivery Group
            * Remove old servers from old machine catalog and delete old catalog

  6. Question. I would like to use zones to setup a single site (two physical sites) XenApp environment. They are connected by a 100mb WAN connection and the sattlite site would be a DR site with its own hypervisor, controllers, Netscalers, and server VDAs. I don’t see how connection leasing would work as users would only connect to DR in the event of a failover. Would I be able to use SQL mirroring/Always On in conjunction with a primary/satellite zone model? I don’t really see any reason why this wouldn’t work, but I can’t find anything saying you can do this.

    1. I still prefer two separate farms until Citrix adds zone preference / failover and true offline database. No SQL DR required. StoreFront controls the connections.

  7. Is there a way to span subnets within a single machine catalog using MCS? We would like to have a single catalog of 5000 machines, but having a single subnet with 5000 machines causes broadcast storms. We would like to avoid having multiple catalogs with the only difference being the network they are assigned to.

  8. Carl,
    Wondering if you can point me in the right direction.
    We are running XD7.8 and using MCS to create new servers in our AWS environment.
    Everything is running nicely, however I want to run a script to install AV software and activate Office after MCS creates the machine.
    What would be the best way to have a script launch once a machine is created by MCS?
    The base image which is being used by MCS is an Amazon Web Service AMI that I created.

    Thank you in advance.

    1. Can you create a group policy with a computer startup script?

      Or you can create a Scheduled Task that runs when then computer starts.

  9. Hi Carl,

    I created a MCS provisioned catalog at that time I used 3 LUN’s so base disk is there on all LUN’s.

    I added 3 more LUN’s but i could not see base disk there on new LUN’s. Do i need to update the machine catalog to get base disk copied along all LUN’s

    Please suggest.

    Thanks in advance!

    1. When you add more machines it should start using the new datastores and copy the snapshot to those datastores. You might have to add 6 machines before it does it. Note, there is no rebalance option. To rebalance, you’ll have to delete the VMs and remake them.

  10. Is there an equivalent to the load balancing policies pf XenApp 6.5 in XD 7.6?

    in 7.6 I don’t see failover policies that XenApp 6.x had where you could specify one worker group of servers as primary and failover to a secondary group.
    I can’t see how you can add 2 machine catalogues to 1 delivery group and place a catalogue in maintenance Рunless you create a single MC and failover individual machines.

  11. Insightful,
    I am creating 2 machine catalogs (1 at DR site other at main site) to be used by a single delivery group, not at the same time.
    How do I load balance (or SWAP) the machine catalogs so I can perform maintenance one at a time without affecting user sessions?

    1. Add both to the Delivery Group. Then put the DR machines in maintenance mode and they won’t be used until you turn off maintenance mode. No need to remove and add machines.

      1. I have XD7.9, there are 2 machine catalogs created(A- 1 Machine, B-1 Machine). I was tried to add both catalogs in delivery group C but appreantly it doesn’t allow do so.
        Can you please tell me whether i have done anything wrong

  12. Carl,

    I’ve found that specifying session reconnect options for the delivery groups to anything but “Always” breaks session sharing. Have you found a way to to keep the session from roaming and keep session sharing?

  13. Hi Carl

    You suggested not using Link-Clone for Persistent VDI, are such machines to be configured as “Remote PC Access” ?

    When installing VDA, there are are only the Options “Create a Master Image” and “Enable Remote PC Access”. Which Option would be appropriate in this case?

    1. It doesn’t matter. The “Master Image” option installs a few more services than the other option. That’s the only difference. I usually install with “Master Image” just in case I want to do that later.

      1. I have some persistent VDI which were earlier created with MCS under Version 7.6.
        I would like to upgrade both the catalog and Delivery Group to 7.7, but the VDA on the VM should be same Version as to access the latest Feature.

        Since creating persistent VDI actually disassociate itself from the Original Base Image and there is no longer possible to update the Machines through “Catalog”, would it be okay to upgrade the VDA directly on the persistent VDI?


        1. Yes. The linked clones are handled by vSphere, not Citrix. Citrix only does the machine identity.

          I would recommend that you clone each persistent VM into a full clone so you don’t have to worry about linked clones anymore.

  14. Hello Carl,

    I have an issue with configuring “Windowed Mode” and “Multiple Instance” on XenApp 7.6 at the same time.

    I will be able to achieve any one at a time. For example, If I edit defalut.ica file as below, it will allow me to launch an application in windowed mode. If this setting is removed, then I will be able to launch multiple instance. Please suggest.


        1. When you launch multiple instances, are they in the same session? If so, I would expect all of the instances to run in the same window.

          Otherwise, I don’t have any advice. You can try posting to or contact Citrix Support.

          1. When I launch multiple instances, they are in same session, meaning I don’t see multiple sessions on Studio. But it is launched in different window. I will try posting in Citrix. Thanks for your Inputs so far.

  15. HI Carl,

    I wondered what you would think is the best delivery method if I was to build two XenApp images for roughly 100 people. This is a single data centre solution, so no DR required.

    Would MCS be preferred if it is non-persistent? I would imagine PVS would be over kill. Else, if it was persistent, as you stated, something else such as SCCM or hypervisor cloning would be best?

    1. The problem with MCS is that you can no longer just login to your VDAs and make a change. Instead you have to update the master and then push it to the linked clones. For only two identical machines, I would do updates manually on both. However, some people prefer the master image method because it gives them one thing to back up.

  16. Good Afternoon Carl,
    Curious if If you ran accoss if Citrix recommendation to have a separate drive (D:) for the windows OS paging file and the windows spool location. This I believe was the recommendation awhile back for optimum performance (separate disk queues for each drive). Just curious if we should be concerned with that or does Citrix just recommend a C: drive large enough to hold everything? The Provisioning service will be MCS as well.

    1. I don’t see any difference between Citrix VDAs and regular PCs. If you don’t multi-partition your PCs then don’t multi-partition your VDAs. XenApp is nothing more than a PC that lets multiple users login at once.

Leave a Reply