This message was deleted.
# microsoft-fslogix
s
This message was deleted.
k
How about \\fileserver\RDS\%username%.%userdomain%\Desktop\App.lnk
FSLogix should be able to handle variables
c
you should be also able to delete the shortcut with WEM if the rule applies.
👍 1
and re-create it if another rule applies.
d
@Kasper Johansen Yea, I thought so too, but it doesn’t work! Invalid path specified.
@Csaba Yes, this was my intention. Maybe with a condition? Do you have more details how to do that with WEM?
k
Yeah, I see that these particular variables aren't supported
d
Could be so easy… 😒
c
@Dennis what is your condition ?
d
I think I have an idea… we use deviceTRUST to check if the device is allowed to use the app (device licensing). I can check a registry key that is created from deviceTRUST to create the app shortcuts. So the WEM condition is simply a Registry value match 😉 I will try this…
👍 1
c
from what I've read about FSLogix, I am not sure whether it would be the right way to go forward. As from what you are describing that app.lnk is unique to the user. If you just delete it only that user will be affected, also if you re-create it only that user will be affected. We generally use AD groups to manage conditions/rules but you can use other conditions
d
By the way… deviceTRUST rocks! https://devicetrust.com 👊
c
WEM does have quite a few conditions
d
Yes, but if you really want to know if it’s YOUR device, you need some bulletproof conditions. deviceTRUST gives you these conditions. Like BIOS serial nr., MAC Address and lots more! Support for Igel devices let you check if the device is managed by YOUR UMS. Really great stuff!
s
We use Filescreening on the fileserver hosting the redirected desktops to 'filter' anything not being a .lnk. Probably not exactly you were looking for but I though it might be worth adding it here
a
Not sure if this will help but WEM uses ##username## instead of %username%