This was an annoying problem today, so I'm posting it in case it helps anyone else.
I was trying to get the OA for our blades connecting to our AD. I setup the LDAP like the manual said, but no joy. Some research on the HP forums said that if the user you want to connect as is in a different OU than the group they're a member of, both need to be configured as search contexts in the OA config. My config page looks like this:
Directory Server Address: dc.domain.com
Directory Server SSL Port: 636
Search Context 1: OU=AdminGroups,OU=Admin,DC=domain,DC=com
Search Context 2: OU=Admins,OU=Admin,DC=domain,DC=com
And then the group setup is like so:
CN=ILO-Admin,OU=AdminGroups,OU=Admin,DC=domain,DC=com
So the group above is listed in the search context 1, but my admin account is in a different OU, which is search context 2. Bah.
Subscribe to:
Post Comments (Atom)
4 comments:
Hi Brad;
Did you ever get this figured out? I'm working on the exact same thing and was wondering what your outcome was, thanks.
Lindis.
at the search context add @domainname.... example: @google
this should get it back to work.
I too was having this problem: I'd hope by now you have it figured out. I had my OU structure backwards in my Search Context where I had the parent OU first and then the Sub-OU second: example:
domain.com
-POU1
--COU1
---COU2
The wrong search context was:
OU=POU1,OU=COU1,OU=COU2,DC=DOMAIN,DC=COM
The proper search context is:
OU=COU2,OU=COU1,OU=POU1,DC=DOMAIN,DC=COM
Also be sure to add the @domain.com in one of the search fields as Cor suggested.
I know it's been a while, but I hope this helps.
Thanks for posting Max. I had the same issue. Security Group in one OU, user accounts in another OU.
Post a Comment