Thursday, August 14, 2014

How to Configure HP ILO 4 for Active Directory Login

1. Make sure that your Windows Active Directory Domain Controller has an SSL Certificate to support port 636 (HP's authentication doesn't like 389)

2. Use Softerra LDAP Administrator (or whatever is your preferred tool to get the OU path) if you don't know how to do it by heart ( its better to verify).

3. Make sure that you have a way to authenticate users by adding in the OU where your restricted accounts are located. You don't want anyone in the domain to be able to login to the server.

ILO Login > Administration > User Administration - Click New and Add the Group DN Only:

Click Add Group and then you will see your group added. (*Make sure it's a security group)

4. Add in your Windows Active Directory DC to authenticate against (Verified against 2008R2):

ILO Login > Administration > Security - Directory (*Make sure it's the OU where the security group is)

5. Sign Out (Log off) and then Log Back in (If you don't see Directory or..., something is wrong):

Tuesday, August 12, 2014

How to Create a Red Hat Enterprise Linux 7.0 VMware Template

Red Hat (VMware Cloning Precautions) -
Linux Tutorials Website (NixCraft):
The Lone SysAdmin -
Mfariso1 -
DISA STIG Compliance Tool Viewer:
DISA STIG (Operating Systems):
DISA STIG How-To YouTube Video:
Force Use of Screen at Login (Red Hat): 

1. Upload the ISO to your datastore. Create a Linux virtual machine (Remove the floppy disk and boot into the BIOS and Disable anything you don't need or won't need) with only the packages you actually need and will use.

2. vi /etc/motd (This is the security banner message for your company).

2a. VMware Specific configurations: VMware Tools & Other

3. Antivirus/Malware Software: (Use Something)

3a. Don't forget visudo if your using Active Directory. This way you don't have to add it later manually
Note: If your using spaces in your AD security groups. Just change it to a "-" or "_" make life easier with a dash or an underscore.

4. Clean out your temporary files and log files
/usr/bin/yum clean all
go to /var/log and clean out all of the log files. You don't need anything for a template to remain.
/etc/ssh/sshd_config (configure to your security requirements. DO NOT LOGIN AS ROOT!!!)
/tmp/ (be careful completely blowing away /tmp on VMware for VMware Tools, etc)

5. Blow away the current NIC configurations:
 /bin/sed -i '/^\(HWADDR\|UUID\)=/d' /etc/sysconfig/network-scripts/ifcfg-ens19 (*whatever ens is)
(ens32 is new and different from eth0. Go Here is you want to know what changed)

6. Remove SSH Keys
/bin/rm –f /etc/ssh/*key*

7. Remove Root's History
/bin/rm -f ~root/.bash_history

8. Clear out all of the junk and anything showing what you did:
cat /dev/null > ~/.bash_history && history -c && init 0

*Only add && init 0 after history -c if you want to immediately shut the box down.

8. Shutdown and convert to template
init 0 
(*VMware/RHEV/OpenStack Convert it to a template)

Monday, August 11, 2014

How to Configure BGInfo for Windows Server 2012 R2

FYI: It's not hypervisor specific and works fine for physical servers also.

Download BGINFO from Microsoft Downloads Only

1. Create a folder named bginfo under C:\bginfo
2. Extract all of the contents of bginfo to that folder.
3. Open Bginfo and setup your configurations.

*Custom configurations can be found here thanks to Shay Levy:

4. Once you have completed your custom configurations. Click on File Save As and save your .bgi configuration to C:\bginfo (Don't bother saving to C:\Windows\System32\* SysPrep and Imaging will strip and mess up any settings so don't bother) *Do NOT just clone your VM's!!

5. After you have saved your configuration. Create a batch file named whatever and add the following to the first line (*whatever you named the .bgi file is what you put second after the bginfo.exe path):

6. In case you forgot how. Enable the ability to see the extensions on folders when you created the file in Notepad (NOTE: Make sure you disable it after you're done!)

7. Go to Regedit (Type regedit in PowerShell) and configure the string for Run (HKLM\Software\Microsoft\Windows\CurrentVersion\Run):

8. Finish configuring your template for your physical server or your virtual image (VMware/OpenStack/RHEV/Hyper-V/OracleVM).