Configuration information could not be read from the domain controller

SYMPTOM

When attempting an RDP connection to a Windows 2008 server (2012 not tested) via the IP address of the server instead of the server name, and when logging in with a local account (not domain account), if requested to change the password, you get an error message with the following wording:

Configuration information could not be read from the domain controller, either because the machine is unavailable or access has been deniedconfig_info

RESOLUTION

When attempting the RDP connection, use the server name instead of the IP address if the name is resolvable on the network. Also, for the username credential, use the syntax servername\username.

It seems that when connecting to a server via IP address, not enough access is given to the local security database to perform the actions to change your password. Once the password is changed however, you can again access the server the same way as originally done.

Empty Recycle Bins

For the times when you’re looking to clean up space on a server and you run a utility like Treesize Free and determine that you have loads of wasted disk space used by various users’ Recycle Bins.  Here’s how to clean that up (not to worry, the Recycle Bin directory structure is automatically recreated as it is needed).

To empty all Recycle Bins:

Windows 2003:
rd /s c:\recycler

Windows 2008/2012:
rd /s c:\$Recycle.Bin

Windows Server 2012 “Access” Issue

Wanted to post the contents of an email chain with an interesting symptom and less than interesting solution that I figured out, in case it might help someone else that comes across it (this is a Windows Server 2012 issue):
———————————————-
Eric,


The error appears when you are trying to get to the server d:\ drive remotely. For example from another server or workstation if you go to \\[name redacted]\d$ you get the error below. This happens with both my administrative credentials and with [name redacted].


You do not have permission to access <>. Please contact your network administrator to request access.


 

 

If you try to go to \\[redacted]\c$, or any of the drives on [names redacted], it prompts for credentials and works fine. [Name redacted] and I have gone through a bunch of settings and permissions on [name redacted] but nothing appears to be incorrect or different. I’m sure it is just something I’m missing. Any ideas?

Thanks . . .
————————–
Hey guys,

Without getting into too much details on the wrong paths I went down troubleshooting this issue, I thought I’d share some information on this issue that I finally got figured out last night.


You can reference the email above for the symptoms. I guess the problem would not have arisen with a proper patch strategy, but you never know with these bronze servers (especially with the Server 2012 bugs…errr…features).


The “permissions” problem was resolved by applying KB2822241 Windows Server 2012 update rollup: April 2013 http://support.microsoft.com/kb/2822241


The specific patch in that rollup that related to this issue is KB2811670 Issues when the Audit object access policy is enabled on Removable Storage in Windows 8 or Windows Server 2012 http://support.microsoft.com/kb/2811670


In VMware (and I imagine Hyper-V and others), the virtual SCSI drive might be recognized by the OS as removable storage, which would lead to the behavior described in the article, and which is also the exact behavior we were experiencing. Also of note, as described in the article, it did take a couple of reboots for the behavior to be alleviated.


Just thought I’d send this out in case someone might find it interesting.

Best regards,

Eric B. Cooper

Windows Server “BOOTMGR is missing” Error

SYMPTOM

Upon reboot of a server, you may receive a message similar to the following:

  BOOTMGR is missing

And the server will not boot into Windows.

RESOLUTION

Windows 2003

You will need to run the Recovery Console to write a new boot sector and repair the boot partition’s master boot record.

To run the Recovery Console, follow these steps:

  1. Configure the computer to start from the CD or the DVD drive. For more information about how to do this, see the computer documentation or contact the computer manufacturer.
  2. Insert the Windows Server 2003 CD in the computer’s CD or DVD drive.
  3. Restart the computer.
  4. When you receive the message that prompts you to press any key to start from the CD, press a key to start the computer from the Windows Server 2003 CD.
  5. When the Welcome to Setup screen appears, press the R key to start the Recovery Console.
  6. Select the Windows installation that you must access from the Recovery Console.
  7. Follow the instructions that appear on the screen, type the Administrator password, and then press ENTER.
  8. At the command prompt, type the following Recovery Console commands :

fixmbr
fixboot

  1. To quit the Recovery Console and restart the computer, type exit at the command prompt, and then press ENTER. (Certain commands will prompt for a reboot of the server).

 

Windows 2008

You will need to access the System Recovery Options to repair the installation.

To access the System Recovery Options, follow these steps:

  1. Configure the computer to start from the CD or the DVD drive. For more information about how to do this, see the computer documentation or contact the computer manufacturer.
  2. Insert the Windows Server 2008 CD in the computer’s CD or DVD drive.
  3. Restart the computer.
  4. When you receive the message that prompts you to press any key to start from the CD, press a key to start the computer from the Windows Server 2008 CD.
  5. You will choose the Repair your computer option. From that point, the available options should look similar to this

  1. Choose Command Prompt
  2. Type cd x:\sources\recovery
  3. Type StartRep.exe

Once that action has completed, you should be prompted for a reboot.