Jump to content

Björn Schläfli

Members
  • Posts

    273
  • Joined

  • Last visited

  • Days Won

    15

Posts posted by Björn Schläfli

  1. I've discoverd today, that Citrix UPM doesn't synchronize completely. Most of the files and directories are not written back to the file share. It's happening in two different sites with any extension in edge. Citrix UPM is configured to synchronize !ctx_localappdata!\Microsoft\Edge\User Data with some subfolders excluded. Extensions are completely included. 

    I've tested upm 2402 and 2305, no difference in behavior. 

    Permissions are correctly (one file and one folder is written back).

    Google Chrome extensions do work, but there we use profile.pb in roaming.

    UPM Log:

    "AppData\Local\Microsoft\Edge\User Data\Default\Extensions\Temp\scoped_dir10312_1402100676\CRX_INSTALL\manifest.json>. Ignoring."

    If I configure the directory extensions as Profile Container it works.

    Anybody else with this problem maybe?

  2. New Teams client on server 2022 with FSLogix HF4 is working in my environment as long as I used the following workaround:

    Configure a run once at logon External Task in WEM (or logon script in gpo) to run the following powershell script.

    Add-AppxPackage -RegisterByFamilyName -MainPackage MSTeams_8wekyb3d8bbwe -ErrorAction SilentlyContinue
    Start-Sleep -Seconds 3
    Start-Process -FilePath C:\Windows\explorer.exe -ArgumentList "shell:AppsFolder\MSTeams_8wekyb3d8bbwe!MSTeams"-ErrorAction SilentlyContinue

  3. 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?

  4. 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).

  5. 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.

  6. 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.

  7. 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.

  8. 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.

×
×
  • Create New...