exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY |
Anybody using HP integrated lights out with AD DS?If so, can you post a screenshot (redacted of sensitive information) of your iLO settings? I'm having a helluva time configuring iLO.
Everything is working except for the authentication user when I run tests and I'm sure it has something to do with with my command to query AD DS. |
|
DarkLogixTexan and Proud Premium Member join:2008-10-23 Baytown, TX |
Whats the command you're using? |
|
exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY 1 edit |
Group accounts on iLO | AD DS settings | AD DS settings |
said by DarkLogix:Whats the command you're using? Damn DarkLogix , that was quick. See attached pictures. I don't think I'm using the correct command in iLO to query AD DS for pulling the iLOadmins security group I created. |
|
DarkLogixTexan and Proud Premium Member join:2008-10-23 Baytown, TX |
Can you try using adsi edit to get the context instead of typing it?
I've run into some issues of cn vs ou in the command for other things. |
|
dennismurphyPut me on hold? I'll put YOU on hold Premium Member join:2002-11-19 Parsippany, NJ |
to exocet_cm
First of all, in the Directory Settings, you're using DN=iLOadmins...... It should probably be a cn= .... |
|
exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY |
Updated to CN. Still same error as shown in image 3. |
|
dennismurphyPut me on hold? I'll put YOU on hold Premium Member join:2002-11-19 Parsippany, NJ |
to exocet_cm
Try this: I have now got logins working just using the canonical name part of my fully distinguished name. I did this with the correct "Directory User Context 1" for what you see after the CN= part of your account when you query the domain with "dsquery user -name blah*".
Note that you need to prefix a comma with the back slash character (i.e. the same way your CN= part of your fully distinguished name is displayed when you query the domain with "dsquery user -name blah*".
Also set Directory User Context #2 to '@addomainname' (I.e. @us.corp.com) Try logging in as domain\username |
|
exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY |
said by dennismurphy:Try this: I have now got logins working just using the canonical name part of my fully distinguished name. I did this with the correct "Directory User Context 1" for what you see after the CN= part of your account when you query the domain with "dsquery user -name blah*".
Note that you need to prefix a comma with the back slash character (i.e. the same way your CN= part of your fully distinguished name is displayed when you query the domain with "dsquery user -name blah*".
Also set Directory User Context #2 to '@addomainname' (I.e. @us.corp.com) Try logging in as domain\username You lost me here: for what you see after the CN= part of your account when you query the domain with "dsquery user -name blah Can you type an example or take a screenshot of your settings? |
|
dennismurphyPut me on hold? I'll put YOU on hold Premium Member join:2002-11-19 Parsippany, NJ |
to exocet_cm
|
|
dennismurphy |
to exocet_cm
I don't have access to a win machine at the moment....
But on the ad server run:
dsquery user -name dmurphy
(Replace dmurphy with your login name)
Best bet is to use the hpqlomig utility instead .... |
|
exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY |
to dennismurphy
I've read more papers and forums than I care to read and decided it would be easier for me to post here then continue to try and figure it out on my own.
When I get back to my workstation I'll try again. Posting/testing from my iPhone right now. |
|
dennismurphyPut me on hold? I'll put YOU on hold Premium Member join:2002-11-19 Parsippany, NJ |
NP ... Try the hpqlomig util; that (in theory) should do it! |
|
exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY |
said by dennismurphy:NP ... Try the hpqlomig util; that (in theory) should do it! Using option 4: "HP Directories Support for Proliant Management Processors" (which should be renamed to Configure iLO using guided setup installer, IMO) helped but some guess work finally got it. The white paper link that you posted, which I have about three copies open (one paper, two electronic) needs to be redone. I'm about to write a guide on how to get this sh*t to work properly. I'll post a link as soon as I'm done writing it. |
|
dennismurphyPut me on hold? I'll put YOU on hold Premium Member join:2002-11-19 Parsippany, NJ |
said by exocet_cm:said by dennismurphy:NP ... Try the hpqlomig util; that (in theory) should do it! Using option 4: "HP Directories Support for Proliant Management Processors" (which should be renamed to Configure iLO using guided setup installer, IMO) helped but some guess work finally got it. The white paper link that you posted, which I have about three copies open (one paper, two electronic) needs to be redone. I'm about to write a guide on how to get this sh*t to work properly. I'll post a link as soon as I'm done writing it. Awesome! Glad it's working now. Please do! I'll get it into the right hands. |
|
DarkLogixTexan and Proud Premium Member join:2008-10-23 Baytown, TX |
to exocet_cm
said by exocet_cm:Updated to CN. Still same error as shown in image 3. Did you find that it was CN in ADSI edit? |
|
exocet_cmWriting Premium Member join:2003-03-23 Brooklyn, NY |
exocet_cm
Premium Member
2013-Feb-15 11:13 am
No, it was the user context option that was jamming me up. It wasn't mentioned for configuration in the HP guide, only a screenshot of it was displayed in one of the guide's pictures and it wasn't the same as the distinguished name that the guide references.
An educated guess got me on the right path. |
|
exocet_cm |
to dennismurphy
said by dennismurphy:said by exocet_cm:said by dennismurphy:NP ... Try the hpqlomig util; that (in theory) should do it! Using option 4: "HP Directories Support for Proliant Management Processors" (which should be renamed to Configure iLO using guided setup installer, IMO) helped but some guess work finally got it. The white paper link that you posted, which I have about three copies open (one paper, two electronic) needs to be redone. I'm about to write a guide on how to get this sh*t to work properly. I'll post a link as soon as I'm done writing it. Awesome! Glad it's working now. Please do! I'll get it into the right hands. Done. I apologize for any grammatical errors. I'm working on two projects simultaneously. » www.johndball.com/2013/0 ··· 2-ad-ds/ |
|
dennismurphyPut me on hold? I'll put YOU on hold Premium Member join:2002-11-19 Parsippany, NJ |
Fantastic, thank you! Excellent writeup. I'll see what I can do with regard to the whitepaper. |
|