This message was deleted.

is given the CEO their own desktop and let the others continue current workflow an option?

Nah not an option as he wants everyone to use a published desktop unfortunately as he prefers it 🤦

that does suck, lot more admin work for you like you mentioned. I can’t think of anything you missed, maybe on retraining i would make sure to focus on where users save stuff unless you really lock it down so they can’t save files locally on the server.

Yeah I feel it's a lot of work for little to no benefit. Luckily got folder redirection in place and local drives hidden

Correct on all the things you're talking about.. what's your desktop technology going to be? (MCS, PVS, multi-user server?). Might be worth pointing out the cost of moving to a real VDI vs. published apps (massive increase in hardware costs, licensing costs etc.). I would unhide C: assuming you have PVS/MCS I'd create a shortcut on the c:\users\public\desktop for logoff.exe and change the icon (makes the users' lives much easier) It's definitely a big project :-)

The VDA's users will be connecting to via the published hosted desktop rather than the existing seamless apps will be exactly the same as it's the same PVS provisioned server 2019 image. The flexcast model isn't changing to a hosted vdi flexcast model such as random non persistent/ static persistent so there is no extra hardware Costs or licensing costs involved (might be a small decrease in user density seamless apps vs hosted desktop but not much that warrants extra hardware). I can't really unhide c: as a lot of the security frameworks we adhere to require c: to be hidden

Hiding the C: drive on a shared desktop is going to create some difficulties (not insurmountable.. just an issue to deal with). You're profile sizes will go up, probably substantially because of the explorer.exe adding a lot to the profiles. I was just referring to getting the CEO to move off of forcing a published desktop :-) . Definitely check your usage when you start migrating, because you will have an overhead increase with the desktops. But, you're definitely on the right track of all the locking down you'll need to do. As long as you have all your various folder redirections in place, and enough write-cache space for your user profiles, it's definitely doable.

the more you configure and lock down the more you have to manage/admin going forward. If they are just normal users on the machine and they are non persistent, i'd prefer not to go ballistic on locking everything down, but it's going to be org specific. Whatever experience they have on their endpoints (if they are company managed), i'd try to recreate in Citrix, for seamlessness. Appventix could help you manage the appv deployments based on user groups. Or you could do fslogix appmasking, or the new Citrix App Control feature just released. If you're sticking with fslogix, might just be easier to use appmasking.

I set a reminder to come back to this one but @Steve Noel hit it spot on. AppVentix will change your world and take away all the pain of anything App-V and MSIX, and I would (for now) stick with the ease of AppMasking. I would heavily suggest avoiding hiding the common programs folder, just AppMask the relevant content instead. for the C drive, there are plenty of ways around that one to meet the best of both worlds

What's appventix.. never heard of that?

The best thing to happen to App-V 🙂

Appventix was previously app v scheduler is good have used it in past