This message was deleted.
# citrix-wem
s
This message was deleted.
j
I believe its all gui - what are you wanting to do, I used PowerShell to action these resets until it became part of the product
m
Reset applications after a user signs in to a published desktop. I have an issue with random blank WEM application icons when they are pinned tiles. Resetting the applications fixes the icons. I'm think I'm done putting time in to trying to figure out what the problem is and ready for a band aid.
j
You can't use WEM to pin tiles in the start menu with any form of consistency - it's never worked (even though the tiles might turn up initially) - from day one, that feature has been broken due to the start menu architecture - when you say reset - are you talking about right clicking the wem agent - reset actions - applications -> or whatever that process is?
m
Yes, exactly.
j
Best off using an alternate start menu management technique for tiles. This was one of my first blogs years ago specifically around your scenario. https://jkindon.com/citrix-wem-modern-start-menus-and-tiles/... this is by far my favorite and most efficient approach https://jkindon.com/appmasking-the-windows-start-menu/ Here is the code for deletion of tracking cache (before they made it a feature) -> https://jkindon.com/selective-deletion-of-the-wem-actions-tracking-cache/ It's powershell, so you can do what you want with it
m
Thanks, James. I'll check this out. The frustration here is on a prior desktop image, we used GPP to create Start Menu shortcuts. There was never any issue between GPP and the Start Menu Layout XML. We want to throw out GPP and move everything to WEM + a Start Menu Layout XML. It works... a LOT of the time. But when it doesn't, it just looks bad.
j
I feel you. Been there, done that many a time. Trust me, the most efficient, and consistent approach is put shortcuts in the common programs folder set, and then just control who has access to it. It then works flawlessly with a start menu layout AND it moves any processing into the machine context so less user tax as well.... works perfectly 🙂
this is specific for tile management, the rest of the start menu with shortcuts etc is a breeze with WEM -> It's purely tiles
m
Yes. Tiles set by the start menu layout XML is the pain point. The rest of the start menu has never given me a problem.
j
It's a glorious beast. If you don't want to appmask it, you can achieve the same with NTFS permissions on the shortcuts -> stick them in
c:\progradata\Microsoft\Windows\Start Menu\Programs
then use a GPO (machine level) to apply permissions to each shortcut. I've done that on a project with thousands of shortcuts and aligned it to WEM processing groups - also works a treat, and very fast
m
Citrix UPM file based profiles is our profile solution. I am going to test excluding the ...\Tasks Exec Cache\Applications key from registry write back. Not sure if I will need an action to refresh the cache after logon.
j
smells like playing with fire - but should be a giggle
m
lol! I am sensing you have gone down this avenue before.
j
so many times -> machine based for that portion of the start menu for the win man - you only win, no lose points. And you aren't forcing WEM to do things it shouldn't need to do
m
😩
It would be nice to have the best of both worlds. Enable "Remove common program groups from Start Menu" to rapidly wipe out the Start Menu for users, but also be able to reference a shortcut from
c:\progradata\Microsoft\Windows\Start Menu\Programs
in the start menu layout xml. For your second option to work, I think I would need to unconfigure the "remove common program groups" GPO to show common shortcuts and have a GPO apply NTFS permissions on individual shortcuts.
j
Remove common program groups from Start Menu
is the devil. It introduces so much non-needed user based configuration..... you are correct on the above process (or use app masking)
s
ResetActionsUtil.exe is all GUI based. for the start menu, wem will support the windows11 startmenu configuration soon.