This message was deleted.

That used to be the case with Windows 7, but no longer with Windows 10. Confirmed from multiple sources, including our own testing for Citrix Optimizer.

Yea, mandatory was awesome, but with Win10 now, it isn't really buying much and now apparently 2019 as well. I stopped using it with Win10, but still use it anything 2016 when I can. But looks like 2019 might be similar to Win10 with the downsides

ahhhhh

Yep same here.

So are you using UPM/FSLogix instead? Seams like polar opposites from saving nothing to a full profile. I have a use case with 100,000+ named shift workers that don’t really need to save anything. Any profile solution is really overkill.

Just default profile tuning and tiles layout creation, etc. Sometimes along with Citrix Profile Management if personalization at all is needed. FSLogix in those cases might just be a O365 play. No reason to have it now using a bunch of storage for profile stuff you dont' need

@Oz Zy so just tuned local profiles? I assume you’re just discarding the profile on VDA reboot?

Profile Management temple profile or use FSLogix as well. See https://james-rankin.com/articles/quickpost-using-fslogix-to-create-multiple-default-profiles-and-start-tiles-layouts/

yea, the audit mode/copyprofile method. Works well now

I was reading some of the comments on @James Rankin blogs, seams there is some successes creating the mandatory profile on earlier builds of Win10. I tried using Server 2016 and got a proxy prompt when searching the start menu. I enter my credentials and it works. Ideally I shouldn’t be searching the internet to search the start menu. I thought I had Cortana crippled. Anyhow, if I kill SearchUI it works. I went back to the Server 2019 mandatory profile, kill SearchUI and it works too. Thinking about using a bandaid and using WEM to prevent SearchUI until I can figure out how to turn it off.

I've never had any problems until version 1903.....an 1803 mandatory profile seems to work OK on 1903 (although not great, by any means)

Have you also seen this? https://support.citrix.com/article/CTX225373

Yes, @Jarian Gibson that’s what I’m following, but I also tested outside App Layering and building an unattended.xml from scratch with the same results. After farting with it for most the day yesterday I better understand what’s going on. It appears my start menu is broken until my second logon, when the profile is a .man it’s always a first logon. It has something to do with SearchUI.exe and our proxy servers. On the first login, I can’t search the start menu until I kill SearchUI, but if I prevent Search UI from running at all, search never works. I read a little last night and even with GPO Cortana isn’t fully disabled. I’m going to try and use the Windows firewall to prevent SearchUI from accessing the internet.

Start menu will be the death of me, we use the import module on boot up with the bisf customization. This way I don’t screw up the default one.

@Cory Zaner Import-StartLayout? If so, I’m doing the same for the tile layout, just the search won’t work on the first login until I kill SearchUI.

Hmm haven’t noticed, I will check.