When users complain that they are experiencing slowness in their VDIs, there are some points to check within in citrix.
If you have Citrix ADM (Application Delivery Management) installed and configured, you should see users sessions and bandwidth details in ADM. You may see high ICA RTT even though users say that they have very good internet plan. They always try to download a file or stream a YouTube video in HD and say, my internet is good.
Here are few recommendations to save money on azure:
Reduce costs by eliminating unprovisioned Azure ExpressRoute circuits. Buy reserved instances to save money over pay-as-you-go. Right-size or shutdown underutilized virtual machines. Use Reserved Instance.Choose low-cost locations and regions. Right-size underutilized virtual machines. Deallocate virtual machines in off hours. Delete unused virtual machines. Migrate to PaaS or SaaS services. Use right size VMs. Azure Hybrid Benefit for Windows Server and SQL Server Use Dev/Test subscription offers Bring your own SQL Server license Use SQL Server Developer Edition for non-production use
We all know, Citrix initially was into provisioning apps and desktops to users. They came up with Citrix Cloud services where Citrix manages the admin part and you manage the VDI part (mostly).
Now they came up with another service where you can host the VDIs on Microsoft Azure and Citrix will help to manage the connection between your organization users and Azure. Now let’s see Citrix Managed Desktops is.
Here are list of some of the powershell 7 features:
Pipeline parallelization with ForEach-Object -Parallel New operators: Ternary operator: a ? b : c Pipeline chain operators: || and && Null conditional operators: ?? and ??= A simplified and dynamic error view and Get-Error cmdlet for easier investigation of errors A compatibility layer that enables users to import modules in an implicit Windows PowerShell session Automatic new version notifications The ability to invoke DSC resources directly from PowerShell 7 (experimental) ?
We may end up in a situation where we have delivery group with multiple servers (Let’s say 10 ) out of which application owners need to publish an application from only given set of servers ( Let’s say 5 ) from those servers.
This is how the process goes:
Application Launch Process Follow below process to publish application to only few servers in a delivery group.
Create a tag and add required servers to the tag.
Issue: VDI appears as not registered in studio console.
Event Viewer shows 1017 error:
The citrix desktop service failed to register with any controller. The service will try registering again approximately X seconds.
Troubleshooting:
Run Citrix Health Assistant tool. This will identify any errors with registration and domain memberships etc.. Make sure you use the correct port number for your VDA registration. By default it is 80. In case in your organization if it is changed, you have to use the same port number.
Provisioning Services Ports:
Source Destination Type Port Details Provisioning Server Provisioning Server UDP 6890– 6909 Inter-server communication Microsoft SQL Server TCP 1433 Communication with Microsoft SQL Server Domain Controller TCP 389 Communication with Active Directory Target Device (PVS outbound Broadcast/DHCPServer UDP 67 / 4011 Optional: Obtaining network boot information in case DHCP options 66 -TFTP Server Name (Bootstrap Protocol Server) and 67-Boot file Name (Bootstrap Protocol Client) are not configured or boot from ISO/ local disk not used.
Storefront:
For StoreFront, the credentials are verified directly to a Domain Controller. SF then passes the validation over to the DDC to begin resource enumeration (Step 4). Note: StoreFront validates user’s credentials by default on its own. From Storefront 3, we can enable xml service based authentication, When StoreFront is not in the same domain as XenApp or XenDesktop, and it is not possible to put Active Directory trusts in place.
We have several options to load balance target devices to vDisks. Under Subnet Affinity, they are None, Best Effort and Fixed.
If we want to restrict PVS vDisk streaming to only some subnets, where PVS servers are spread across different subnets, we can use subnet affinity feature.
Subnet Affinity When assigning the server and NIC combination to provide a vDisk to target devices, select from the following subnet settings:
None:
TCP Chimney (sometimes referred to as TCP Offloading)
This feature is designed to take processing of the network such as packet segmentation and reassembly processing tasks, from a computer’s CPU to a network adapter that supports TCP Chimney Offload. This has the effect of reducing the workload on the host CPU and moving it to the NIC, allowing both the Host OS to perform quicker and also speed up the processing of network traffic.
