This post is more than 5 years old
8 Posts
0
3057
March 26th, 2019 13:00
Using RACADM to Remove iDRAC.ADGroup ?
We are providing some contractors access to our iDRACs for migration work and I want to remove that access once they are done. I've been searching and cannot find the command to remove them. Sure, I can set "IDRAC.IPv4.Enable" to zero but I would rather clean up the configuration so it's not on our next audit.
Is there even a command to do this?
0 events found
No Events found!


Daniel My
12 Elder
•
6.2K Posts
1
March 26th, 2019 17:00
Hello
I'm not sure what you are wanting to do, but I think I have an idea.
You can't delete index entries, the indexes are persistent. You can replace or overwrite values. For instance, if you perform racadm get idrac.adgroup you will get a list of your indexes. You can then find the index that you want to change the values and get more information with racadm get idrac.adgroup.1 or whatever the index number is.
You can replace all of these values with null/empty values. For instance, if I wanted to clear out what was in index 1 I would run these three commands:
Double quotes should put an empty value, and the 0x0 bitmask should remove all privileges. You should be able to locate more information about the bitmask values and these racadm commands in the racadm manual on the iDRAC support page.
http://www.dell.com/idracmanuals/
Thanks
VMAdmins
8 Posts
0
March 27th, 2019 06:00
Daniel, thank you very much for your response, overwriting with empty values will accomplish my end goal. Aside from thanking you, I wanted to let you know that you must put a space between quotes for the command to work.
PS I:\> RACADM Set IDRAC.ADGroup.2.Name "" ERROR: RAC917 : The syntax of the specified command is not correct. See the command help text. To see the help text, run "racadm help "
PS I:\> RACADM Set IDRAC.UserDomain.2.Name " "
[Key=IDRAC.Embedded.1#UserDomain.2]
Object value modified successfully
Daniel My
12 Elder
•
6.2K Posts
0
March 27th, 2019 09:00
It looks like you are using powershell. Last time I assisted someone with this in powershell they said they had to use double quotes """".
VMAdmins
8 Posts
0
March 28th, 2019 07:00
You are 100% correct.
Blah! I've been bit by that before and should have known. Thanks again!