World of EUC

Something to note, Adobe Acrobat Pro has recently had a name change in one of the later updates - i found that it 'broke' AppMasking for FSLogix rules, so if you are using this to hide Adobe Acrobat the rule will need to be redone - the new name is "Adobe Pro"

The vdi handbook might have some info that is still pretty relevant from memory 

Thank you for reminding me if that. I will go find that and have a look. 

Dang, looks like the link was updated to Techzone. I’ll have to see if I can find it on a 3rd party site. 

I found it. But something I noticed, it seems like most of the older stuff is now being sent to techzone. Which is great, but it may not have everything yet. I understand it is a lot to keep up with on their side as well. Hats off to them. 

Thank you so much James. It has a bit of stuff I needed

image.png

From the docs:
<https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html>

Thanks :pray:<@ULL6F7DRA> for your input.  Unfortunately me too, just had a user with a chrome book facing this. This might be a device limitation in relation to the optimization 

Do you have the latest CWA installed on the Chromebook?

Yep :+1: … i can make it work.
on-prem need an entrie in we.config and in citrix cloud you need to enable it explicitly on the DaaS tenant.
This will work straight afterwards, the thing is, the user is then allowd to not only share the vdi Session content but his entire privat endpoint.
Nice, isn’t it? :grinning: 

solved it. Printer driver was generating the dump files.

I still disable preview pane , but it's not something I've tested since doing it years ago.

The downsides it presented -- locking files sometimes, slowdowns on multi user systems -- just weren't worth it for a feature none of my users asked for or noticed when we disabled it

Yeah, that's still where i'm at too. Just checking the community pulse.

I didn't think so either. But most of the other VDI handbooks now redirect to TechZone. Well from my research and checking.

It had been so long since we updated the handbook I think we removed all the links to it.  Though much of it would still be valid.

Yea, I was looking through the 7.15 handbook today. Most of it seem legit still. I really loved those handbooks. I hope they continue to do them.

There is alot of work that goes into them, but very solid.

Techzone for i think it's for quick information.
But handbook for with detailed information. Citrix should release handbook every LTSR release

Rob, any idea.... if you are allowed to say. Is the effort still geared towards that?

Now Citrix Cloud + Hybrid+ On-Prem + Licensing Terms + ADC + ADM for this product detailed information like handbook is required

I'm not sure if Marketing has plans, consulting is not working on anything,  The originals were joint efforts between the two groups.

Some information like Sizing and best practices are very clear and how to manage projects and it's delivery

We do, I look at the monitoring companies like CU, EG and they have so much data that goes into it. I often wonder why Citrix can't partner with them to do a collective effort.

WEM is easy and you will pick that up fast. AppLayering is another subject I tried to get into. But I have not yet as much as I would like.

<@ULLH5JGFR> may b due to confidential information

I mean WEM and Applayering required in Handbook

For app layering I wrote a reference architecture that has what you need it is on tech zone

<@ULCBDDJCR>
Just in case you need it.
<https://docs.citrix.com/en-us/tech-zone/design/reference-architectures/app-layering.html>

As for WEM, <@UR9T47CRM> has a ton of great info on his blog: <https://www.deyda.net/index.php/en/category/citrix-en/wem-en/>

Thx. And I try the same for adc / netscaler. But at the moment only the first part is online. 

<https://www.deyda.net/index.php/en/2021/06/22/citrix-adc-101-fundamentals/|https://www.deyda.net/index.php/en/2021/06/22/citrix-adc-101-fundamentals/>

It was for Branch Repeater, but that is EOL for quite some time

Whatever happened to Project Accelerator?
Looks like it went from this to Smart tools to nothing?
<https://support.citrix.com/article/CTX141316/project-accelerator>

Hi, Are there any paths i need to add for Office 365 to UPM?  I read this link (<https://docs.citrix.com/en-us/profile-management/current-release/profile-management-best-practices.html>) and it said its done by default but i thought there were additional paths that need to be added to upm...

If you check the !ctx_localappdata!\Microsoft\Office\16.0\Licensing folder can you  verify that it is included in the users UPM profile and that the license token file is there?

Also how often does the issue with users having to reactivate happen?
If i remember corretly the license token file lasts for 30 days, and the token will refresh every time someone uses a office application on the TS. So if someone hasn't logged in for at least 30 days it is expected that you have to manually sign in again if you don't have sso/adfs (I might be misremembering though so someone feel free to correct me if'm wrong)

Check and see if the .txt files mentioned in this article exists in the UPM profile<https://learn.microsoft.com/en-us/deployoffice/troubleshoot-shared-computer-activation?redirectSourcePath=%252fen-us%252farticle%252fTroubleshoot-issues-with-shared-computer-activation-for-Office-365-ProPlus-c3aeb487-d45f-4079-8c35-7558a45b876c#verify-that-activation-for-microsoft-365-apps-succeeded|https://learn.microsoft.com/en-us/deployoffice/troubleshoot-shared-computer-activation[…]for-Office-365-ProPlus-c3aeb487-d45f-4079-8c35-7558a45b876c>

however, when the user is logged in to the server and activate office, i see it in their local profile

I have seen mirror work many times over sync 

Don't laugh, but i've never used Director.  :slightly_smiling_face:  Can you export reports easily?

CU all day long to be honest. Director is weak

CU costs money though.  Will start with Director and see where that leads me.  Thank you!

Oh my bad :slightly_smiling_face: I assumed you had it.

Historically, we don't use stuff that costs money.  :smile:

If you're asked for this on a constant basis, you can save your report as a query so that you just have to re-run it each time you need it. Saves a bunch of time if you want to add columns to display, etc.

Director works fine for this, thankfully.

Awesome.  Yeah, I assume they will want it once a month.  Or, who knows, find it useless once they fire X employee.

Yea, I always hated giving them reports. Because I knew that would lead into something like that.

I was gonna say, that sounds like a micromanager.

Screenshot 2022-12-08 at 2.30.32 PM.png

Screenshot 2022-12-08 at 2.28.42 PM.png

Here is an example..  Director &gt; Trends &gt; Custom Reports &gt;

Missed opportunity to use 'GallierR' in that screenshot, Paul...

We have to run a similar report against a specific delivery group every quarter or so.  Our finance people want to ensure their contracted company are not billing for users who don't login..

I could be incorrect, but does the Odata feed give you more data as well?

Maybe not
<https://support.citrix.com/article/CTX211428/using-excel-to-report-on-director-data>

I query SQL. I can better track a session and see when a user has disconnected vs simply the beginning and end of a session. My scenario was we had W10 VDAs that only rebooted once a month for updates, but idle sessions would disconnect after a couple hours of inactivity. It better illustrated when the user started and stopped working for those who cared.

```USE [CitrixMonitoring];

SELECT	Users.UserName AS 'Username',
	Users.FullName AS 'Full Name',
	Connections.ClientName AS 'Client Name',
	Connections.ClientVersion AS 'Client Version',
	Connections.ClientAddress AS 'Client IP Address',
	Connections.ClientPlatform AS 'Client Platform',
	Machines.HostedMachineName as 'Hosted Machine Name',
	Connections.LogonStartDate AS 'Logon Start Date',
	Sessions.StartDate AS 'Session Start Date',
	Connections.DisconnectDate AS 'Disconnect Date',
	Sessions.EndDate AS 'End Date',
	Sessions.SessionKey

FROM MonitorData.[Session] AS Sessions

LEFT JOIN MonitorData.[Connection] AS Connections 
ON Sessions.SessionKey = Connections.SessionKey

LEFT JOIN MonitorData.[User] AS Users 
ON Users.Id = Sessions.UserId

LEFT JOIN MonitorData.[Machine] AS Machines 
ON Machines.Id = Sessions.MachineId

WHERE Users.UserName = 'USERNAME'
ORDER BY Connections.LogOnStartDate DESC```

Ah, this is great.  Thank you for sharing!

In a lab? I’ll wait about 1 week for my lab just in case.

Wasn’t this the main thing that was a pain?

When you attempt to connect to a VDA running version 2203 on a multi-session OS, the logonui.exe process might become unresponsive with a black screen or get terminated. However, event logs might appear. [CVADHELP-20338]

I'm going lab first, then production on Sunday, assuming nothing pops up in the lab.

There are a lot of things that are a pain for us and I have to get it pushed out for license server upgrade in order to upgrade XenMobile on-site. Played with the pre-release version version already as well in the lab without issues, so I'm fairly comfortable with it. We have a long standing ticket for Windows Search issues that we need to get on current supported release to get Citrix to really get involved in helping troubleshoot and CU1 with private hotfixes has been the only stable release, but need to go with CU2 to really put the hammer down on testing.

I'll let you know how things go, in this thread.

Good luck , and I appreciate the communication 

Pushed on preproduction Friday morning, works fine

Had issues with Storefront upgrades due to Performance counters that I'm not sure how they got corrupted, but other than taking a while to figure out the issue in test and working through it in production, it went pretty smooth. Director was a non-issue, no problem upgrading. Test delivery controllers had no issue upgrading.

Then hit the first production site upgrade and it died a horrible painful death. Reverted the DB and checkpoints. Will schedule with Citrix before attempting again. Never had an issue with the DB upgrades in the past, and this just took out the entire site. Was an interesting time.

VDA upgrades went fine on the few test and (internal - non-client) production systems pushed to. Will monitor for issues there as well.

<https://support.citrix.com/article/CTX279999/upgrade-from-xendesktop-715-to-cvad-1912-ltsr-fails-with-exception-databaseconnectiondetailsalreadyconfigured|https://support.citrix.com/article/CTX279999/upgrade-from-xendesktop-715-to-cvad-1912-[…]s-with-exception-databaseconnectiondetailsalreadyconfigured>

This is the same issue I faced. I will attempt the upgrade again "soon".

Upgraded two sites successfully with no issue using Set-LogSite –State “Disabled”. The KB says Enabled or Disabled should work, but was set to Enabled, not Mandatory, already when failed.

Hello, does anyone know if this is still valid - can it be changed to chrome

The nodomaindetour registry key fixed it for me on 2209 a couple of times. Cloud studio only for me.

Hi <@ULDHJB8BB>, you did apply the regkey correctly as mentioned in this article?
<https://support.citrix.com/article/CTX472865/cvad-version-2206-2209-gpss-fail-to-apply>

How do you apply the regkey? In your master image?

we have an open incident for about 1 year,  VDA version 2112, where CTX policies startet to fail, only single session os.  Citrix changed something in the code.
They want us to change "loopback mode" from replace to merge. What we will not do.
If we go to LTSR - they think they can write a private fix, or we need to open a feature request, for something that worked for years:-(
We are in contact and have escalated this.

sure --&gt; 81340382 working with Nikhil and our PM is Matthias F.

<@UNBRPVD4G> hello Rody, could you see/find the case. Do you have any insider news about this issue.
We still work with 1912 on 2'000 single VDI's, upgrade to 2109 brings not the big bang in relation to optimizations or Teams features. This start's with 2112, where logon problems and applying CTX policies starts.
to change the loopback mod, from replace to merge, is not an option at our environment.
thx a lot and wish you a good start in the new week.
regards,
Thorsten

<https://github.com/leeej84/-DEPRECATED---PowerScale>

Can you try and see if the issue occurs through RDP? If the issue does not occur using RDP, maybe try excluding the specific process from citrix hooks to see if that makes the issue disappear? <https://support.citrix.com/article/CTX107825/how-to-disable-citrix-api-hooks-on-a-perapplication-basis>

I was going to suggest testing with RDP as well. I know it is a pain or can be to have users do that.

Hi all, does anyone know if Safe Links (Defender for Office 365) is causing issues with Teams client, links are working fine on browser but are no longer working on client ?

As far as I remember protocolhandler is only used for the client detection. I don't know for sure but I don't think that would have any effect on the domain pass through. What are you seeing or trying to achieve?

I am trying to get rid of the "Detect Receiver/Workspace" button and in past i have just disabled protocolhandler in the web.config but when i did it domain pass through on MS Edge/Chrome seemed to of broke and i found this <https://support.citrix.com/article/CTX269089/domain-passthrough-does-not-work-with-microsoft-edge-and-google-chrome>

Oo not seen that before, real shame it doesn't go into very much detail. Maybe in that case I stand corrected. But I still not seeing how client detection would break passthrough unless protocolhandler does more than client detection. I'll see if I can give it a whirl in my lab.

At my last place, we tried every fix that I could find to get domain passthrough/SSO working in Edge/Chrome, and nothing seemed to work.

Yes I know that the OG edge could not do passthrough at all, but I thought they fixed that a couple of years ago. 
Maybe protocol handler has also something to do with the ssonserver workspace component but that would only stop the vda sign in from working not the storefront iis bit as far as I remember.

Does anyone have experience with in-place upgrade of VDA for Workstation-OS  via ConfigManager? I have a customer who has a lot of Windows machines where they use the RemotePC feature in the VDA. They are on VDA 1912 today and want to go to the latest VDA 2203

not in my lab and the Citrix support statement says they don’t test or validate minor releases

Fuckin hell, I guess that makes me a little happier.

It's actually a colleague of mine experiencing the issue

When this happens, I have to run VDA cleanup utility, and then still manually delete C:\ProgramData\Citrix\XenDesktopSetup

The customer have 600 WIndows comptuers with RemotePC enabled

in what context are you running the task sequence? Local admin?

I have done so many VDA upgrades over the years, and have _never_ seen this behavior.

Fail: Logged in with non-admin account, PowerShell is launched as Administrator and run in that context

Success: Logged in with admin account, PowerShell is launched as Administrator and run in that context

How about the SCCM task sequence, is this running in the local user context?

I highly doubt it, but also don't know. That's another team entirely.

I assume it's running under SYSTEM like most SCCM packages, as that install method is showing the same issue that I just posted with my bad manual install.

This is what I get for commenting that I never have VDA upgrade issues here.

The /noresume cmdline switch should prevent the runonce registry entry though

Why would you need the noresume switch? If you do use it, do you need to manually kick off the .exe after reboot?

How the hell do you use SCCM to upgrade the VDA then without a task sequence?

I don't know. I don't have very much experience with SCCM

I honestly can't recall how that works. I would expect the /noreboot switch to not require any of that, though.

The finishing of the install post-reboot is likely what's killing this

I did try and manually launch the RunOnce entry after my manual attempt (logged in as non-admin, ran PS as admin and launched .exe), but that didn't do anything. The installer just ran multiple copies of itself (new PID every few seconds) and did nothing until I killed the task

I have seen the VDA installer spitting out an exit code of 3010, if I remember correctly, even though it installed correctly

In our logs, the final entry in the log file was 'pending reboot', and nothing afterwards

Actually looks like this is happening after prereqs, not even the VDA.

Yes, it looks like it happens because of a Visual C++ install

Now I wonder if we have to make that package a prerequisite package in SCCM. That would be so dumb.

I had to upgrade c++ first then to the vda upgrade

This just made all VDA upgrades that much more of a PITA

But with sccm it seems to always work best to remove the vda clean up upgrade the pre reqs then reinstall the vda.  Might also need a reboot in there

I don't see any way of doing it without a task sequence then. I have seen the VDA cleanup utility require 3 reboots to complete - like on my own VM just now.

If that utility could run and only require a single reboot, that would work, but I don't see how this functions properly with that many reboots in between.

Unless the /unattended switch resolves that

And honestly, requiring the VDA cleanup utility for upgrades... woof.

In sccm there should be sn exit code if you need to reboot. And yes def needs a task sequence. Its not a simple upgrade due to the prereq requirements. You can roll those out separately then it’s usually a much easier upgrade. 

Yeah, the SCCM guys sent me a screenshot of the TS. Looks like VDA cleanup is being run 4 times, with 4 total reboots, so I don't think that part of the process is the issue. Getting a few VMs back to 1912 so that they can add VC++ back to the TS post-cleanup to see if that yields different results.

This is the kind of stuff that scares all of us for the auto VDA upgrades in cloud, BTW.

Has in-place upgrade of the VDA ever been good? It seems like there has always been issues

Honestly, I never really had an issue with 1912 and earlier that I can recall. 2203 for us has been a mess with upgrades.

If adding a separate step for VC++ doesn't work, I imagine we'll be engaging Citrix support, because there's no way we can upgrade the VDA on our thousands of persistent VDAs any other way.

VDA cleanup + reboot x3, 1912 CU5 install + 1 reboot... VDAs register fine

When we were doing tons of remotepc installs the key was getting the prereqs installed before trying the vda.  The issues always seemed to be when the vda had to do the prereq upgrades. No prereqs and it worked fine. 

A little late to this party...

Sorry if what I say has already been said, I only skimmed through this whole thread.

The VDA cleanup utility provides a return code to know if a restart is required or not, so can be scripted to restart as many times as needed, which I do in my deploy script.

I use the /noreboot /noresume  flags in my VDA deployment so I control the entire process in my script because Citrix doesn't seem to do things consistently, and depending on what pre-reqs are needed there may be more restarts required. My script manages the entire process.

I always use a local admin account where the account is granted admin rights on the local machine during script run and uses Autologon to manage the process. Autologon and Admin rights are cleared at script end.

If adding VC++ as a separate step doesn't resolve this for us, I'm going to suggest using /noresume and having them kick that process off via the TS.

<@UM04QUUSJ>: There's no hard requirement for VC++ 2015-2019, right? We're going to attempt to use a newer 2015-2022 package.

Just to close the loop on this, that seemed to work. Here's our new process (via Task Sequence in SCCM):


1. Run VDACleanupUtility
2. Reboot
3. Run VDACleanupUtility
4. Reboot
5. Run VDACleanupUtility
6. Reboot
7. Run VDACleanupUtility
8. Reboot
9. Install VC++ 2015-2022
10. Reboot
11. Install VDA
12. Reboot

Wouldn't it be great if we didn't need the VDA Cleanup Utility?

Now that we've got the process down for 2203 CU1, I can ignore everything we've seen and immediately do the same for CU2, lol.

I just told the SCCM team, and I'm pretty sure that I could hear them slamming their keyboard. :joy:

Just started testing CU2, and all of the installations appear to have failed... until I manually RDP into one of them, and it kicks off in the background. Trying to get the install string they're using, because I don't understand why anyone would need to logon in order for the installs to kick off/continue.

Sounds fun. Certainly sounds like they didn't run to completion and are not using -noresume in the command line. I know I script the process using -noresume and do my own checks to rerun the process until it completes successfully or fails and notifies.

We aren't using /noresume, correct. I think I'm going to have to get them to change this up, because this isn't working. That said, it's 2023 and Citrix still can't build an installer that fucking continues after a reboot automatically, without having somebody login?

If you're running SCCM for the installs, would you mind posting your task sequence and commands?

I'm not using SCCM. I have a PowerShell script which I have posted a "cleaned" version in the past that I can share, but I have re-written it since then to cut it down a bunch (removed a lot of unneeded steps that removed 6.x for upgrades in the past mostly) and I think I have the VDA Cleanup utility functioning better since then, since Citrix added a return code.

If you want either, I can probably spend some time doing a quick cleanse of the current script to share.

Nah, it's all good. I had our SCCM team just add a step to run the local path post-VDA install, and added some more reboots. Damn thing is going to be take 8 reboots to upgrade a VDA now... insanity.

I can't speak to MCS, but at my old job we didn't do anything for the join outside of ensuring that the GPO was set to join. There's a built in scheduled task that already handles this, so I'm not sure if your task is missing something that this one is doing.

Well, I didn't remove anything, so the built-in task isn't working either.  Looking

"Register domain joined computers as devices" is the GPO setting, in Computer\Windows Components/Device Registration

So, this is the proper method of doing it?  Man, i'm so antiquated sometimes.

I don't even know if it's the proper way, to be honest. Just how we always did it in our W10 PVS non-persistent devices.

I can't see why MCS would be any different, but maybe I'm wrong

Exclude Masterimage from AAD Sync and sync only the OU containing your MCS VM's. Be sure that the Masterimage is unjoined, remove all MCS VMs (including your Masterimage) from Azure AD and run dsregcmd /join on your MCS Clones at startup via BIS-F.

I don't use BIS-F.  How is BIS-F doing this function?

I have a scheduled task at startup for this function, which doesn't appear to be working

I use BIS-F for this.  The policy mentioned above if linked at whatever level will then need you to exclude any OUs for syncing (like master OU for sure).  So sometimes I run into that policy that is org wide, sometimes not. But then BIS-F doing its thing (leave/join) and also making sure "worksplace join" scheduled task not disabled for reason and it seems to work fine then  - this is excluding the whole conversation on the PRT ticket situation with FAS scenarios, but yea, just for hybrid joining, seems to work fine so far.

Teams click issue.mp4

I have seen the behavior on other apps. Just last week I seen this (not teams) but another app. The users had 2 monitors. One was 100% and the other was 150%. Once set equal, it responded. Worth a check.

Good call.  I'm using a triple monitor, with sides at 150% and main at 100%.  Though going to be tough to get my users to all accept 100% on all monitors.  Not that I'm holding out hope for Citrix ever fixing non-100% DPI scaling to work properly after all these years.

Thanks!  Will test. :slightly_smiling_face:

Depending on the CWA version. Tell it to use native resolution. Then It seemed to help

These two seem to help. Depending on what you want.

Unfortunately, setting native resolution causes our 3D Pro sessions (all of our sessions, gaming company) to go absolutely wild at random on multi-monitor mixed DPI scenarios, to the point that the left monitor stretches into the center, with the left 100% corrupted and mostly black with flashing glimpses of what should be there, the center about half-visible, and about half-seizure-inducing blinking, and only the rightmost monitor rendering correctly.  Once it gets into that state, nothing will fix it - a Workspace reinstall + cleanup, VDA reinstall + cleanup don't help at all.  Only setting the DPI back to 100% on all monitors or forcing the GPO for scaling to "yes" to scale instead of use native will fix it.

B/c of that, the only workaround I have there is either forcing users to turn on scaling, or set their monitors locally to 100% and turn that setting to native, then set their in-session DPI to their desired DPI on every reconnection, at least until it's fixed.

Does using Alt+Space, then Move allow you to move the window?

I've had all kinds of....suboptimal things happen with Teams + HDX Redirection.  Sometimes the Share button doesn't allow me to select what I want to Share, the known issue about reconnects not always being optimized, local camera (remotePC) but not redirected camera showing up in Teams.  All are inconsistent...

Compounding, I still hit the _&gt;_ 6 Audio device redirection ceiling if I leave my GoXLR turned on in the morning... if I remember to turn it off before connecting, Teams gets pissed if I turn it on midsession (the rest of the HDX audio devices still work if I connect with it off then turn it on after connecting).

6 Audio device redirection ceiling........ I hit this last week and it took me 1 hour to remember.

Known issue entry on one of the 22xx versions... I went looking for it the other day but couldn't find it

Found it in the 2203 LTSR notes:

Your High Definition Experience (HDX) Audio devices disable when you are connecting to a single-session RemotePC or Workstation Virtual Delivery Agent (VDA) on a client that is enabling more than eight HDX Audio devices. As a workaround, choose one of the following:
    ◦ Connect to a single-session RemotePC or Workstation VDA from a client that is enabling less than eight HDX Audio devices.
    ◦ Enable the HDX Audio devices after the single-session RemotePC or Workstation VDA has launched.
    ◦ Connect to a multi-session RemotePC or Workstation VDA.
• [CVADHELP-20164]


Says fixed in 2203 CU2!  Haven't tried it yet

interesting it was fixed in CU2...I moved onto 2209 so maybe they'll release it in 2212

From what I was told from a good source, it still acts up in CU2

<@U013YSR4QAZ> Just tested, and alt+space -&gt; move does unstick the window. Will note this down as an alternative workaround, thanks!

Re: the audio device issue, our enterprise architect has the same GoXLR and has the same issue on 2209.  Hoping it's fixed in 2212.

Was infuriating to collect CDFTrace logs from his machine to try to debug why he was losing audio myself (hadn't seen that audio device limit mention) only to find out that Citrix no longer publishes up to date TMF files and has gated those behind a TRM.

You would set that to Disabled. That's exactly how we had it configured in our environment, as well.

It here as well
<https://docs.citrix.com/en-us/tech-zone/build/deployment-guides/microsoft-365-citrix.html#outlook>

thanks Ray! thats where my screenshot is from.   <@ULC9J5XPB> for "Cached Exchange Mode synce settings for profiles" is All actually recommended?  or is there a better option?

Personally I had a very similar setup as Nick posted if not almost 100% identical. 
One environment was outlook container by Citrix. 
Another environment was FSLogix. I also had extra settings for shared mailboxes.
Then In recent setups I set this:FSLogix Policy Enable Cached Exchange mode on successful container attach this will ensure that if the container fails to mount, outlook sessions will operate in online mode.

My 3rd Option isn’t needed but I like it because it provides what I call a a solid solution so the user can get email if for whatever reason the Odfc can’t attach. Sorry I’m getting way of track
. Extra Info
<https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=odfc#outlookcachedmode-1|https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=odfc#outlookcachedmode-1>

yeah, i have to work on fslogix this week as well...i've only done it once.  i read not to enable roam search if you are using w2k19 for multi-user sessions...does that apply to outlook as well? or do they mean windows search?

The newer FSLogix builds are supposed to detect the OS and by default know what to do with each OS for "roam search"
<https://learn.microsoft.com/en-us/fslogix/configure-search-roaming-ht>

Probably best to set that up in your default user profile. I'm not a fan of applying hundred of user settings by GPOs since it's super slow.

When done right, the user should be able to work after the first login.

<@U01EW1U122G> just a heads up, roaming is only supported for multi-user searching with outlook e-mail search.

<https://learn.microsoft.com/en-us/fslogix/configure-search-roaming-ht>

also <@ULC9J5XPB> One month is the recommend value for "Cached Exchange Mode sync setting"
<https://docs.microsoft.com/en-us/azure/virtual-desktop/install-office-on-wvd-master-image>

thanks <@ULDHJB8BB> would that be the same for on-prem citrix server VDI?  i don't see why it wouldnt.

I would say yes. Because the whole purpose is the O365 setup idea

<@ULLH5JGFR> - i know we discussed this before but just want to confirm i am reading the MS article correctly.  for windows 2k19 server VDAs the roam search setting should be disabled even for outlook,correct?  <https://learn.microsoft.com/en-us/fslogix/configure-search-roaming-ht#overview>

Yes sir. Also is the next to last release I believe it will not allow it as well on that OS if set by accident. Should be in the doc saying that

thanks for responding..hope you are not working like i am.  i am just getting a head start on my.  aw, i am confused by the article b/c in the prereqs it says Windows Server 2019 version 1809 or newer and Windows 10 or Windows 11 Multi-session.  Then in the next paragraph it says its not supported than why put those OSs in the prereqs?

<@UM2G5G8E5> sorry, just now seeing this.

I plan on testing as well today, if time permits. But I expect it to not work either.

<@U03E3RH2J90>

I DM'd Ray, as I didn't want to derail Shawn's thread any further.  I should have just done this and created another thread.

FWIW, I'm on CWA 22.10.5.14.  I saw they released 2212 TP today

Oh the life of a gamer and Citrix "consumer" <@U03JF4T98JZ>

Whoops, saw this after putting a response in my own thread.  Yeah, hoping for a fix for that at some point.

Well, doubly when you work for a game studio. :slightly_smiling_face:

The other scenario I see is WFH, Onboard audio, USB Headset, Webcam with mic, and multiple displays with speakers (each with an HDMI audio device)

Lots of work being done at Citrix on the 3D Pro side to get it up to spec with Parsec (shout out to Rody and his team on the stuff they're working on), but sometimes Citrix at a AAA studio feels like a square peg / round hole situation. :slightly_smiling_face:

Oh, that makes it even more fun for us.  We're a big studio that's gone _entirely_ hybrid.  Our offices are closed right now while they're being expanded / renovated, so almost _everyone_ is WFH

Gaming + WFH spread around the country + Citrix = lots of sleepless nights trying to figure out how to shave down that square peg LOL

<@ULN862X8E> I could not find the other thread, but can you reiterate what you are seeing?

Client device has &gt;8 Audio devices, connecting to RemotePC, Audio Devices fail to redirect.

Looks like this in the RemotePC

Old reddit post on the same <@UNBRPVD4G> <https://www.reddit.com/r/Citrix/comments/ip0bva/citrix_hdx_engine_no_longer_accessing_microphone/>

Have seen that one myself with our Enterprise Architect, can confirm.  If more than (in our tests, iirc - been a few months) 4 audio output devices, the audio output engine will stop passing through output, but the devices will still show up.  Session has to be logged off and back on to get audio output again after a device over the limit of audio devices connects in once, even if you disconnect and connect from another device with less.

Been a few months, so the details might be fuzzy, but it was something to that effect.

We ended up just telling the EA to disable some of the devices on his endpoint in Sound control panel to get down to &lt;= 4 and that cleared it up for him, and added it to our KB for now, as it's easily enough worked around that the other stuff Citrix is working on with us is more valuable to spend time on. :-)

With the GoXLR it's easy... power switch on GoXLR and poof -5 devices.  When I originally posted and I had the Schiit stack (DAC/AMP and virtual audio cables abound)... it was less fun.

Ah yeah, he uses his GoXLR for a critical piece of his audio routing for his conferencing setup so we couldn't just power it off.  But we were able to go into Sound Control Panel on his endpoint and just disable the output devices on it that he didn't actively use, and that cleared it up for his particular case.

I got around to testing this today, But from the DaaS seutp. Same thing, I had to unplug most of the USB devices, disconnect the session, then go back in for it to allow me to use the Sound/Speaks as an example. running 2203CU2 VDA on Windows 10 21H2, MCS, VMware 7.0 update 3. Just provisioned from Citrix Cloud.

FWIW, Optimized Teams does in fact see, and can use, all devices when HDX Optimized...even if the rest of the desktop cant.

Sorry for reviving an older thread, but did this ever get resolved?