Koetzing IT
Thomas Kötzing - Freiberufler, Analyst - MVP, CTP
A slow login can have many reasons, but with newer operating systems, the bloated registry appears to be popular. This short article describes the three most common reasons why the registry is bloated, sometimes massively slowing down logins. Here is the three-step cure when the registry is bloated.
Temporary user profiles are unattractive and can also quickly become a problem with Microsoft FSLogix. The user then receives the message: The user profile failed to attach and further down can be read: Error Code 0x80090024, Message, The user's profile is a temporary profile. This is caused by BAK entries for the user in the ProfileList in the server registry. I have created a Powershell script to clean up these BAK entries.
The Citrix Netscaler firmware upgrade is complete and my job as an administrator is done, right? Many people are convinced that a firmware upgrade fixes all current security issues, but this is not always true. What else may need to be done and what is the easiest way to do it?
There are two very nasty pitfalls when using Citrix StoreFront with the native Workspace App. The result will be that users cannot launch any new session or must reset their Workspace App at best! The changes are very tiny but can screw your running environment terribly. So here are the things you should look after and keep in mind.
As described in the Citrix article "How to implement the Override Ica ClientName feature for StoreFront", the ClientName for the Workspace app (Receiver App Store) cannot be overwritten. Overriding the ClientName would only work with "Receiver for Web" (RfW), i.e. the StoreFront website, and then the ClientName becomes WR_ClientName. This is true for the StoreFront integrated feature, which can be activated via the advanced store settings. Fortunately, there is another, much more flexible option!
This article deals with the Citrix Cloud Network Locations Services (NLS) and explains why "Undefined" is the new external at Citrix. If you are dealing with the network locations, you might get confused because the wording might not be quite correct, at least for me.
Last week, I had a request from a customer that the MFA authentication suddenly stopped working. The customer then installed the latest NPS MFA extension and also ran the troubleshooting script for MFA, but nothing was found. In the end, he asked me for short-term support. A look at the MFA event log showed a critical error with: "CLIENT_CERT_IDENTIFIER" and thus a finger pointing to the local certificate on the NPS server. The certificate with the Azure tenant ID can be found in the personal certificate store, and this was still valid until one day before! A new certificate for the Azure Multi-Factor Auth Client must be generated, but how?
