Rastislav Kovac

Hi, It was on Windows Server 2022. The solution was to enable Shellbridge feature. It's described in the article, although it states 2019, it's still valid also for 2022. No idea, why it wasn't enabled on more recent CUs for 2203 LTSR, but I guess they wanted to keep feature consistency across same version, but different CUs. After the feature is enabled ADFS SSO could do it's job without issues. https://support.citrix.com/article/CTX267071/password-field-not-displayed-for-published-apps-in-windows-server-2019

Hi, Thanks for the suggestion, in the end I found out it was caused by proxy settings. Even though the proxy was configured to be bypassed for the domain name which was included in the recording server FQDN, it still tried to go through it. I was not able to figure out why, but removing the proxy solved the issue.

Hi, I'm currently facing a strange issue. Installed M365 Apps for Enterprise on Citrix master image and deployed a machine through MCS. When I try to launch any of the Office apps as published app, it launches and prompts for credentials, which I enter, then the app just freezes, not greyed out, just unable to click on anything. If I decline the credential prompt, it logs me in as my account, but apparently without going through ADFS SSO, so I just end up with the message that I'm using unlicensed Office. The strange thing is however, if I publish a desktop to same user, log on and launch any Office app, I get automatically authenticated through ADFS SSO and the account becomes licensed. After this I can off course use the published apps as the licensing tokens are synced by UPM on the successful authentication attempt on the published desktop, so it doesn't require authentication, because it's using the token in the user profile. What I have noticed as I tried some troubleshooting is that if I try logging in with my admin account to server and then try to manually sign in with my user account, I get prompted for credentials which then brings up the ADFS authentication window, when I check the processes I can see the proces "Work or school account" which points to this window. However, this never happens if I try to manually log on in the published app and try manually. I have no idea why the ADFS SSO wouldn't work on the exact same server when launching the exact same app just published.

Hi, I've run into an issue with session recording. I have installed recording agent on Windows Server 2019, which works fine. There are 2 other agents on Windows Server 2022, which seem to run into some problem. Server is trying to communicate with the recording server. Port 443 is open (I can telnet to it also) and there is an SSL certificate present on the recording server. When checking MSMQ on the problematic server, I can see it in inactive state or sometimes waiting to connect, which never happens. Event Viewer just keeps outputting event ID2190 in 10 minute intervals as the server is trying to connect: Any suggestions are welcome. Thanks.