Björn Schläfli
-
Posts
270 -
Joined
-
Last visited
-
Days Won
15
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Björn Schläfli
-
-
You can use RDP Proxy feature, but you will need to have advanced or premium license. With a rdp client profile you will be able to disable things like drive redirection...
-
One of our netscaler nodes is not compressing the log files in /var/log/. /var/nslog is working fine. The support article to check value in nslog.nextzip and nslog.nextfile is therefore not helping (also there are values in these files). restarting the vm didn't help.
Netscaler 14.1-12.35
-
Hi
Client: Notebook EntraID-joined
Authentication Notebook: EntraID
Citrix Site: on-prem AD-joined
The user logs in via EntraID. Is there a way to enable passthrough for the (on-prem) Citrix Workspace app?
-
CVAD 2203
Outlook 2016
Some of our users use their smart card to sign emails in Outlook. Every now and then they're unable to send the signed mail. The PIN prompt window doesn't load and the error message "error in underlying security subsystem. internal error" is displayed. It only affects Outlook over Citrix. No issue in Outlook locally installed on clients.
If the issue happens kill all open Outlook processes and start Outlook again fix it for a while (same session).
It affects Outlook seamless and in published hosted desktops.
It also happens on Virtual Desktops (Windows 10 22h2).
-
It's noted in the known issue list of StoreFront 2203 CU4:
"Usernames with special characters might appear corrupted. [CVADHELP-24499]"
-
My Microsoft case id: 2402060030007022
-
As a workaround you could create an entry in the strings...js, the one for your language.
%SystemDrive%\inetpub\wwwroot\Citrix\....Web\custom
For english use the strings.en.js:
Replace the Example... lines with
WelcomeUser: "Welcome!"
The displayname comes from a variable {0}. Because I'm not familiar with js, css... I have no clue where this {0} is defined. And I was unable to find the correct file which is responsible for the wrong encoding.
receiver.html contains the line <meta charset="utf-8" /> in the header which is good and should display the umlauts correctly. It must be configured wrong in another place.
-
We have the same problem. We have updated our Storefront servers to 2203 CU4 because of the security issue. This issue does not exist with 2203 CU0. The issue also exists with 2308, but only in the settings menu. The welcome text is correctly encoded.
-
A colleague informed me that the problem no longer occurs with patch KB5034203. I immediately tested this patch in our test environment and no longer found any problems. There is nothing mentioned about black screen or windows search in the fixed issues list, but Microsoft seems to have fixed it again.
Patch KB5034203
-
Good news.
A colleague informed me yesterday that the problem no longer occurs with patch KB5034203. I immediately tested this patch in our test environment and no longer found any problems. There is nothing mentioned about black screen or windows search in the fixed issues list, but Microsoft seems to have fixed it again.
Try it out and give feedback, please
-
I tested it with an image on which nothing other than the PVS target device software was installed. So no fslogix. It's a clear Microsoft problem. The problem always occurs when a virtual disk (pvs, app layering or other) is used. I spoke to someone yesterday who reproduced the problem with a virtual disk without Citrix or fslogix. For me it's clearly because the Windows Search service doesn't start. Of course, FSLogix has a big problem with this because it needs this service.
Workaround: boot the image in private mode, boot again, seal the image.
-
I've done a lot of tests with no success.
- replaced searchindexer.exe
- used a clean new golden machine with only pvs target device software
- Procmon recorded while booting, but didn't found anything helpful
- As I used a clean image API hooking is completely out of focus
- compared windows search regkeys working / non-working
- It works in the golden machine, but the first boot of a vdisk of it shows the windows update startpending status. After a reboot more it is working.
I'll open a case next week.
-
I just tested a clean image with nothing more than vmware tools, citrix pvs target device software and had the same issue. I suspect it's more of a general virtual desktop problem.
The cause here is that the Windows Search service is not starting. It stucks with the status StartPending.
-
I don't use AppLayering.
I just tested around with windows search service. The service is running in the golden machine. In the pvs targets the service comes up with start pending. If I kill the Searchindexer.exe, the service starts and Searchindexer.exe is reloaded. After that a user can logon to the desktop smoothly.
Thanks to Steven for pointing out the cause.
Now I try to figure out why the search service stuck at start pending state.
-
The one with Windows Search service was a good one Steven. Same here. Service has the status starting and type automatic. After a few seconds the type switches to disabled. If I stop the Searchindexer.exe the desktop is loaded successfully.
-
I was interested in the way how Jean disabled it. Set the DWORD Enabled to 0, use the Exclude List or set the gpo setting to disabled.
FSLogix Profile Exclude List doesn't help in my case. The desktop still stuck at the black screen.
I suspect a possible connection with dll hooking. But the earlier mentioned support article doesn't help either (CTX585692).
-
If I kill the frxsvc.exe process while the user's desktop shows black screen, the desktop is displayed shortly afterwards. That would point to FSLogix. But if I don't even have FSLogix in the image, I also have the black screen, which just doesn't make any sense (veryfied once again).
-
Hi KFI Service,
which versions do you use? Site, vda? Do you use VMware or other hypervisors? Do you use fslogix?
-
Jean, how did you disable fslogix?
-
Hi Jean,
thank you. We use 12.3.0. Then an update won't help either.
Which site and vda version do you use?
-
What hypervisors are you using?
VMware? Which tools version?
-
I just tested fslogix 2210 HF3 Preview. No success. I'm sure it's not a FSLogix problem. Yesterday I made a Procmon and CDF Control recording, which I will now analyze.I just tested FSLogix Hotfix 3 Preview. Without success. I'm very sure that's not the reason.
I have no case open at the moment. I'm still troubleshooting to get more and clearer information. I've recorded a procmon and Citrix CDF Trace yesterday which I will now analyze.
-
Interesting fact:
If I update the image manually (usually we use our software deployment solution to set up images) with one of the black screen patches the image boots after the patch installation only once. After that is stucks with a black screen after the vdisk status is displayed from pvs. If I install one of the good patches, e.g. 10th october 2023, the image machine reboots smoothly.
-
Hi all. We are affected also.
Windows 10 22H2, 2203 site. VDA 2203 CU3 and CU4. The issue starts with MS patch october 2023 preview 5031445 and still exists with january 2024 patch.
I'm troubleshooting for hours now.
I'm nearly sure it's not FSLogix related, since I've uninstalled FSLogix in a test image and tested with the same effect. Without FSLogix I should be able to login with a local profile if FSLogix would be the cause. I've also able to log on my test user in VMware console directly to a W10 Citrix target. The black screen only happens if I connect by a Citrix HDX ICA connection.
I've denied gpo's - same issue
Two different images are affected. Both newly set up completely (OS, apps...).
Netscaler not compressing /var/log/ on one ha node
in Core ADC use cases
Posted
Thanks man, there was a shortcut instead of a file in nsconfig.