Symptoms or Error Intermittently few Server VDA’s remain shutdown and do not turn on automatically after scheduled reboot. On the Delivery Controller below series of events are logged: Event ID 3012 - Warning; “The Citrix Broker Service detected that power action ‘Shutdown’ (origin: Schedule) on virtual machine’domain\severname’ failed.”
Event ID 3104 - Information; “The Citrix Broker Service has completed the processing of the ‘GroupReboot’ for ‘xxxx’. The reboot cycle (UID = ‘160’) successfully completed.
The major difference between the two is the type of desktop. XenApp delivers a one-to-many Windows Server (e.g. Windows Server 2008 or 2012) machine that is shared by many users. XenDesktop delivers a one-to-one Windows desktop machine (e.g. Windows 7 or 10) that is used by a single user.
At a high level, this fundamental difference has meant:
XenApp users share the CPU, GPU, memory, and disk resources with all of the other users on the same server.
Resource locations contain different resources depending on which Citrix Cloud services you are using and the services that you want to provide to your subscribers.
Typical resources include:
Active Directory domains Citrix NetScaler appliances Hypervisors like Citrix XenServer Virtual Desktop Agents (VDAs) StoreFront servers Machines hosting the Citrix Smart Tools Agent Resource locations also contain Citrix Cloud Connectors which are required for enabling communication between your resources and Citrix Cloud. For more information about using Cloud Connectors in your resource location, see Citrix Cloud Connector.
Recently, we had to change the display name for one of our delivery groups. This group is deployed as static assignment group, meaning private assignment, one user to one VDI, assigned on their first login to that VDI.
When you create delivery group, you set a display name for your desktops/VDIs that you want users to see when they login to your citrix portal.
Below are some points to note:
The process of creating machines in XenDesktop via MCS can be split into 2 sections.
Provisioning Scheme Machine creation. Let us understand provisioning scheme step by step here:
What is Provisioning Scheme?
Provisioning Scheme can be seen as a “template‟ used to store the parameters and create the VMs. It includes details like the CPU Count of the Master Image VM, the Memory Size of the Master Image VM as well as the location of the Master Image VM used in this provisioning scheme.
In XenDesktop version 5.0, MCS used only one way to create VDIs i.e., using fast clone way. This will have one base disk(master image disk) and all the machines created from this disk will have a delta disk which contains changes like user installed apps, data etc as shown in below image:
This method has its own pros and cons as given below.
Pros:
Small disk for delta file as it only has the updates.
Everytime, when we have such scenario like using upm to redirect user’s data, and if users have upm errors(Ex, as shown below), we always think of renaming user’s profile in the profile share path. If that doesnt work, along with that step, we should also try to remove user’s profile using the default way(system properties, advanced, user profiles, remove user profile) or using any tool like delprof2.
Note: When UPM is used, only user’s data is redirected to the share.
Load balancing provides a higher level of availability and scale by spreading incoming requests across multiple virtual machines. You can use the Azure portal to create a load balancer to load balance virtual machines. This quickstart shows you how to create network resources, backend servers, and a public Basic Load Balancer.
If you don’t have an Azure subscription, create a free account before you begin.
Sign in to the Azure portal Sign in to the Azure portal at http://portal.
If users try to access their VDA via remote desktop, they receive below error:
If you want to RDP to a VDA machine then you’ll need to be a local admin or a member of the local Direct Access Users group on the VDA.
Install the Cloud Connector on a dedicated physical or virtual machine that meets the following minimum configuration:
2 vCPU 4 GB RAM 50 GB hard disk space Note The machine configuration can vary, depending on the Citrix Cloud service and the requirements for your environment. For more information about component sizing and scalability with respect to specific Citrix Cloud services, see the Advanced Concepts section.
Additionally, the machine must meet the following requirements:
