This message was deleted.
# microsoft-fslogix
s
This message was deleted.
k
Which application and OS?
d
Windows Server 2019 with any application. I opened a support case, let’s see what the FSLogix support says.
j
What version of FSLogix is this? I can seem to remember a similar error message a good few versions ago...
d
The latest MS release.
j
Must be a bug then
d
I’ll let you know… Support is analyzing the logs.
k
Thx @Dennis 🙂
e
Set Everyone = Yes at top of the list and the the AD groups that need persmisdions = No. This works perfectly on W10 & WS19 bit only if Everyone is on top of the list
j
I always use Everyone at the top, do people do it differently? I was always of the impression that the more globally-encompassing the "Apply" group, the better
d
It’s about device based licensing. The majority is allowed to use the app. I use deviceTRUST to control AppMasking based on the users device. DeviceTRUST puts the user in the rule dynamically. So that’s why everyone is set to no.
j
Interesting...can't you just app mask on the environment variable for the client name?
d
I could, but at customer audits clientname was not enough, cause you can easily fake this. It’s about using MS Office on RDS (device based licensing). We had a conversation on Twitter about this. With deviceTRUST no problem cause there are plenty of properties you can use to identify your devices. But the problem has nothing to do with deviceTRUST. If I manually add a user AppMasking also sometimes doesn’t work.