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.

What is Citrix Cloud ADM service, and does my company need it? Citrix Application Delivery Management (ADM) is a platform for Netscaler, whether a gateway or an Application Delivery Controller (ADC). However, the ADM service can do much more than manage Netscaler, and I will explain that in three parts. The first part will explain what can be done with the ADM service. The second part deals with the different configurations of the ADM agent and what to look out for. Finally, in the third part, I will explain what can be done with the data collected by the ADM service as an example. The Cloud ADM service offers excellent added value for Netscaler Gateway customers, especially from Netscaler version 13.x onwards.

Microsoft OneDrive is part of Office 365 and has become more popular with companies. This article is about how to handle Microsoft OneDrive within a virtual desktop infrastructure. The focus is mainly for multi-user environments with Server 2019 or Windows 10 VWD but could be used within other scenarios.

With OneDrive, all users' files are in the Microsoft cloud but synced down to the user profile. Therefore, OneDrive can fill up a user's profile fast and would require more local or on-prem storage again. In addition, users are changing the end device all the time, which impacts the logon time. How to make sense out of OneDrive in a VDI environment is what I will try to explain.

I'm celebrating my 20 years work anniversary with Citrix products as an administrator, consultant, and for the last 14 years as an independent freelancer. I started with MetraFrame 1.1 on Windows server NT 4.0, and back then, it was not easy to keep servers running. Every day I had several BSOD, and it was expected, I could only stabilize the environment by getting rid of third-party printer drivers. Back then, the drivers were executed within the kernel space and quickly crashed servers. The next battle was the Token-Ring Thin Clients with a Citrix Client running on Microsoft MS-DOS! Always a topic, the hardware memory was never enough and expensive....

18 years ago, I had written several pages about the Windows logon and how to speed up and optimize the logon. Today the logon is still a problem, and just some days ago, I helped a customer solve his slow logon issue.

While I was researching performance issues with server 2016, I found an interesting article by Microsoft talking about a new optimization. Already built into Windows 7 release, it was further developed and finally activated by default with Windows 10 Clients. With server versions the same feature is disabled but can be activated by a simple PowerShell command. I couldn't find anything on using the feature with multi-user systems. I was wondering, if this feature would give instant more performance or better user experience on session hosts running server 2016 or 2019. Customers of mine are testing it right now, and I'm interested in the results. Do you want to join them?