Skip to main content

iLO admin password changes en masse

Worked on this the other day, very handy!


Need to change all the admin passwords for iLO.  It's okay if the passwords are the same, just has to be complex.  Note also there is a 20-char limit for IPMI 2.0 (recommended, not enforced).

Batch file
I created a batch file and server list file for each domain to keep things simple.  Note if the path has spaces, you need to enclose with quotes.  :P

------------
 @ECHO OFF
 set FILE=server_list_test.txt

 for /F "skip=2 tokens=1,2,3*" %%i in (%FILE%) do (
  echo %%i
  psexec \\%%i -u %%j -p %%k -h -c hponcfg.exe /f \\testserver.test.local\F$\temp\ilo_password.xml
 )
------------

Quick breakdown of what it's doing:
* '-c hponcfg.exe' is in here because '-w' to set local working directory doesn't seem to work, so we copy the exe over
* '-h' is for Vista and up, elevates the cmd
* '/f' specifies the location of the ilo xml file
* Note there are separate source text files for each domain, and separate XML locations due to cross-domain privilege limitations.

Batch source file
Use tab spacing.
------------
Target(I) Username(J) NewPassword(K)
 -----------------------------------------------------------------------
 testexch01.testlab.local TEST\ctrotter Password01
 testexch02.testlab.local TEST\ctrotter Password01
------------

ilo_password.xml
Note - use notepad++ to edit/create this to preserve XML formatting.  I used the template/sample XML file from HP (windows-LOsamplescripts4.00.0.zip).

Sorry, had to remove the leading '<' from every line for it to display properly.
------------

RIBCL VERSION="2.0">
   LOGIN USER_LOGIN="adminname" PASSWORD="password">
      USER_INFO MODE="write">
         MOD_USER USER_LOGIN="Administrator">
            PASSWORD value="eyeNEEDremoteaccess!"/>
         /MOD_USER>
      /USER_INFO>
   /LOGIN>
/RIBCL>

------------

Comments

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…