This is indeed 'working as intended', but that intention might not always be matching your expectations, unfortunately...
Shortcuts (and some of the other user environment settings) have an "undo" option which means that UEM/DEM automatically removes them again at logoff:
Without that option configured, the shortcut will indeed "stick around" even if you disable or delete the setting in the Management Console.
Thank you for your help .. its appreciated.
I do Ineeded have the option checked. ( only that option ). However that shortcut still persists on my desktop .
i tried unchecking 'desktop' as Destination... and it wouldnt let me do that ( makes sense i guess ) .
i Do have a condition of Group Membership for the icon to be placed. that shouldn't matter right ? I am a member of the group .
Pls excuse my ignorance .
Do you mean a config specifically for the Application itself ? under General-Applications in UEM/DEM ?
Or maybe something under General - Windows Settings ?.. that captures shortcuts ?
As far as i can tell i dont have anything under those two that would deal w/ shortcuts.. and not the specific app itself in UEM.
I was just testing creating and deleting a Shortcut w/ an app thats in c:\windows\system32\... ie already on the machine .
We DO of course have a folder redirection in place for the users desktop .
Yeah, something like:
The settings from the Easy Start don't do anything like that, and I can't imagine you added it either , so we'll have to figure out what exactly is going on. Can you share a log file, at log level DEBUG, containing a full session from logon till logoff?
Nope.. not doing anything like you listed. thanks .
I Did find this old forum post :
Yep .. its a tad old.. we Are getting that "[ERROR] Async UEM actions or UEM Refresh in progress" error .
Im working on getting the logs. I should probably get my managers ok to post them just to be safe . Is there any method i can send them to you outside the forum ?.. Could you PM me ?
That "[ERROR] Async UEM actions or UEM Refresh in progress" is something we'd need to look at as well, but I don't think it's related.
Totally understand that you're hesitant to publicly share a log file – I'll PM you for that.