This message was deleted.
# citrix-wems
Slackbot
04/27/2023, 6:50 PMThis message was deleted.
c
Carl Behrent
04/27/2023, 10:24 PMfollowing this one, have weird icon issues also
j
James Kindon
04/28/2023, 4:56 AM@Anthony Shi
b
Balint Oberrauch
04/28/2023, 7:58 AMme as well. WEM 2303 and manually pinned icons are blank sometimes. Shortcut has been delivered via WEM to the Startmenu. FSLogix as a profile solution
a
Anthony Shi
04/28/2023, 8:00 AMWill have a check
j
James Kindon
04/28/2023, 8:48 AMSeems odd with the double folder structure
c
Chris Schrameyer
04/28/2023, 3:37 PMI thought it was when a user logged into different published desktops (where WEM would have different ICON ID's). We have folder redirection turned on for Desktop folder. So i thought maybe WEM and folder redirection were fighting eachother, but that would not explain the strange multiple subfolders
Chris Schrameyer
05/03/2023, 12:08 PMHere is what I think is happening. I think it’s an issue between the interaction of the redirected desktop, WEM publishing apps to the desktop, and the inclusion of the icon files in the user profile. User logs in, WEM processes the desktop icons from the folder share and copies them to the local desktop. WEM then processes the applications in the policy. Since icons already exist on the user desktop and in the Appdata folder, I think this is where the issue comes into play.
We basically have 3 locations where icons are. 1. Desktop (which could be the incorrect icon names if a user accesses multiple published desktops, each with a unique WEM policy and as such, unique icon filenames), 2. Appdata\Roaming folder which was included in Citrix UPM, and 3. The desktop icons WEM creates when a user logs in.
Chris Schrameyer
05/03/2023, 12:09 PMWhat do you think? I have a solution that works for me, but want to see if I am describing my thoughts in a way that makes sense 🙂
b
Balint Oberrauch
05/03/2023, 1:23 PMI solved it in my environment:
AppSense Application Manager denied execution of '%localappdata%\citrix\citrix files\icon.ico [Hash:e68b8bbf500cc2a1ed565b3634f9b0be2fc9ad8a Size:164241 bytes] [ProductVersion: 0.0.0.0] [FileVersion: 0.0.0.0] [Product Name: ] [Company Name: ] [Vendor: ] [File Description: ] [Parent Process: %programfiles%\microsoft office\root\office16\outlook.exe]'
m
Matt Sliva
05/17/2023, 6:57 PMI saw this problem when using the WEM Tool Hub to copy icons to WEM Cloud. It appeared to copy, but the browser needed permissions to fully allow the copy. Once I gave it permissions, deleted the "broken" icon in WEM, and replaced it with a fresh copy, all was well.
a
Anthony Shi
05/18/2023, 3:08 AMWhat version of WEM? @Chris Schrameyer
Anthony Shi
05/18/2023, 3:10 AMhi @Matt Sliva Glad to see “WEM tool hub” can help. The problem has been solved after being granted permission, correct?
m
Matt Sliva
05/23/2023, 2:33 AM@Anthony Shi, yes, that's correct.