Highlighted
Hot Shot
Hot Shot

Placeholder wishlist, AD attributes and or LDAP query

Jump to solution

I'd like to see the ability to use placeholders Using Placeholders in Text Files  but using AD attributes or LDAP queries instead of environment variables.

1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

No.

Great! I'll add this to the list of feature requests, and will discuss with product management.

View solution in original post

0 Kudos
11 Replies
Highlighted
VMware Employee
VMware Employee

Hi EricNichols,

Thank you for this feature request. As usual, no guarantees on whether or when this might be added Smiley Happy, 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?

0 Kudos
Highlighted
Hot Shot
Hot Shot

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:

[Flex#LDAP://CN=<%username%>,OU=Users,DC=Domain,DC=Com#Title]

0 Kudos
Highlighted
VMware Employee
VMware Employee

Hi EricNichols,

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?

0 Kudos
Highlighted
Hot Shot
Hot Shot

Thank you for considering the feature. I do not see a use case for that object ever being something else than the currently logged-on user.

Highlighted
VMware Employee
VMware Employee

No.

Great! I'll add this to the list of feature requests, and will discuss with product management.

View solution in original post

0 Kudos
Highlighted
User Moderator
User Moderator

Condition sets too maybe? Smiley Happy I can see condition sets being more than just OUs and Groups by looking at other ad object

Highlighted
VMware Employee
VMware Employee

Hi sjesse,

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 Smiley Happy

0 Kudos
Highlighted
User Moderator
User Moderator

Must of misread that, well you have my vote then Smiley Happy

Highlighted
Hot Shot
Hot Shot

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.

John

0 Kudos
Highlighted
VMware Employee
VMware Employee

Hi JohnTwilley,

Your vote has been counted Smiley Happy

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.

0 Kudos
Highlighted
VMware Employee
VMware Employee

EricNichols, JohnTwilley,

It sure took a while, but DEM 2009 supports referencing Active Directory attributes in placeholders, like [Flex#%{AD$title}%].