Slow response DFS namespace

KB244380 says:
“The DFSDnsConfig registry key must be added to each server that will participate in the DFS namespace for all computers to understand fully qualified names.”

We thought this meant that the registry key has to be set on the DFS namespace servers only, not realising that it was also required on the domain controllers. After we set DfsDnsConfig to 1 on our domain controllers (and restarted the “DFS Namespace” service), the problem vanished.

Troubleshooting account lockout issue

I had a problem when an Active Directory user account got locked out all the time.

I tried the following tools:
Account Lockout and Management Tools
NetWrix Account Lockout Examiner

I found out that when I unlocked the user account the bad password attempts started again and after 20 retries the account got locked out. I guessed that there must be a script or task some where on the network that used the user account and after a password change this caused the problem.

In LockoutStatus.exe (Account Lockout and Management Tools) I could see from what domain controller the lock originated from. I logged on to the domain controller and checked the security logs in the event viewer. I found the event ID 4740, that explained that user account was locked out and I also found out the caller computer name.

After a quick check on the caller computer I located the problem and solved it by adding the new password for the account.

Can’t find and install iLO 2 driver on HP ProLiant DL380 G5 running Windows Server 2012

I had problem finding an iLO 2 driver that would work with Windows Server 2012. The server was a HP ProLiant DL380 G5. I had earlier managed to get an iLO 2 driver to work with Windows Server 2012 on a HP ProLiant ML350 G5.

The hardware ID was: VEN_103C&DEV_3302.
It was shown in the device manager as ipmi interface.

We solved this by this by installing cp013803.exe (HP ProLiant iLO 2 Management Controller Driver for Windows Server 2008 x64 Editions)