Thank you for this feature request. As usual, no guarantees on whether or when this might be added , but I'd like to have the conversation.
I think I understand the AD attributes part, but could you clarify LDAP queries? My understanding is that those would typically result in zero or more AD objects, and I'm not sure how we could use such a result with placeholders.
Would you (or anyone else reading this thread) also see value in a condition based on AD attributes?
In powershell I use LDAP sometimes instead of get-aduser so that I don't need to add the module. I just imagine that LDAP might be easier for UEM as well plus add the ability to query other directories.
Maybe something like this:
Ah, I see – just using an LDAP URI to identify an object. Do you see a use case for that object ever being something else than the currently logged-on user?
Yes, that's what I was wondering about when I asked "Would you (or anyone else reading this thread) also see value in a condition based on AD attributes?" in my initial response
We are about to implement something to leverage the Extended AD attributes to apply the new O365 Viewer Mode reg key based on whether or not the employee had an E1 or E5 license... I was thinking about the module issue as well. One vote for me!
I was also wondering about a possible way to apply existing Group Policies (User) post login via UEM. It would be very handy to have a GUI that we could just check off a few of the existing managed Group Policies, and NOT have it delay login, but apply after the desktop has loaded.
Your vote has been counted
As for your other question: would you mind starting a new thread for that? I'd be happy to chat about that, but I'd prefer to keep these two topics separate.