Microsoft is forcing its customers to switch to the "new Teams" by mid-2024! The feedback so far is that customers are once again beta testers, and extensive tests have not even been carried out by Microsoft. There are problems with Microsoft FSLogix and the Outlook add-in. The "new Teams" on a Server 2019 or Server 2022 is yet another challenge. I have developed a Powershell scripts that installs Teams on Server 2022, Server 2019, Windows 10 and Windows 11 multiuser and also takes the Outlook add-in into account. 

The new driver for MCS, MCSIO v2, has been available since Citrix Virtual Apps and Desktop version 1903. However, two important performance counters "Cache memory used" and "Cache disk used" are missing in this new version to read out current values. In addition, the performance counter path has changed from \Citrix MCS Storage Driver to \Citrix MCS(*). Unfortunately, the currently used cache disk size can no longer be determined, but only the current size of the cache disk file (mcsdif.vhdx). I have developed a Powershell script that at least gives me a quick overview of the RAM and disk cache status.

There are often misconceptions among customers about what the data flow or process is when making a Citrix HDX connection. Basically, it is simple, but sometimes misconceptions persist. My experience shows me that pictures often explain more than language. This is the second part and explains the process from external via the Citrix Gateway. Not every tiny detail is explained now, but it should clarify the basic process better.

There are often misconceptions among customers about what the data flow or process is when making a Citrix HDX connection. Basically, it is quite simple, but sometimes misconceptions persist. My experience tells me that pictures often explain more than language. This is a two-part article and the first part is about the internal connection setup for a single FQDN configuration and then the second part is about how the whole thing works externally. Not every tiny detail will be explained now, but it should clarify the basic process better.

Once set up, Citrix Application Delivery Management offers a flood of information with analytics enabled, but can the administrator or business do anything with it? The last part of the Citrix ADM Cloud Service deals with this question and the information on how and where to get the data in the first place.

The following second part of the Citrix Cloud ADM service is about setting up the ADM agent. There are significant differences in the deployment and the ADM agents used for this. First, there is the built-in ADM agent, which is already part of Netscaler 12.x, and second, the ADM agent appliance. Here, the ADM appliance is integrated as a standalone system, usually on-prem and linked to Netscaler. I want to explain the exact difference and how these agents are used in the following article.