Skip to main content

Accessing a Protected Domain Administrator Account

door, green, closed

As a good practice measure, the default domain administrator account which comes pre-installed with every Active Directory should be guarded from misuse. We all know this. To follow in this good practice, the account should be renamed from the default name and disabled.

So what happens if this account is the one you have to use to recover from a problem? Let’s say, for example, that all of your usual domain administrative accounts are somehow not accessible for use and requires you to get to this account. If it’s disabled, what do you do?

Should you find yourself in the scenario that you have a disabled administrator account AND know the password --

  • Boot up the domain controller to Safe Mode (make sure it is not Safe Mode w/ Networking.) This quasi-enables the account. You can at least log on with it.
  • Using the account and password, log in.
  • Open a command prompt and issue the following:

net user administrator /active:yes

Now you have an enabled default domain admin account. You can reboot the DC and presume as normal on what will probably be the worst day in your life. :)

 

Note: When you change the account password as a part of your routine process, make sure you verify that DCs receive the password change, in case you need it in a disaster scenario. You can easily validate replication by issuing the following command:

repadmin /showobjmeta <dc name> <admin account distinguished name>

Comments

Popular posts from this blog

opalis: blank entries in log and log history

ran into a problem today with opalis.  I had checked in a policy I was working with for testing and left it on overnight.  I came in the next day and found that it didn't work like I had expected.  I checked out the policy and tested it to make sure it was working.  it did exactly what I expected. I checked it again and started.  this is when I noticed something strange.  neither the log nor the log history had any information in it. usually, it would look something like this screenshot: I checked my lab environment and found the same thing.  I spent a few cycles reading logs , manuals, etc believing that I had missed a step setting it up somewhere or inadvertently turned something off.  I ran across an access denied error that I quietly shuffled to the back for now.  to rule out the ois client, I tried using the operator console.  that didn't work either. I checked the services on the server to see if it was started.  that's when I found that the opalisactionservice wa

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here . (get-netadapter | get-netipaddress | ? addressfamily -eq 'IPv4' ).ipaddress   update: this is by far the easiest. PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress 192.168.1.101     are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does. done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it. i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we wa

imaged machines and the dnsapi event id 11163

i wonder if this is going to end up a long-winded post.  i never intend for that to happen because somewhere i picked up that technical information should be succinct.  however, when i started looking into this problem, it seemed like there just wasn’t good information on it. synopsis a user in your environment needs to have their machine reimaged.  as a loyal IT citizen, you promptly do so by any manner that happens to be your favorite (e.g. mdt, swimage, ghost, etc).  you bring up this machine as the same name.  later on, you try to remotely manage the machine but realize that the ip it once had is different.  you spin your wheels a bit trying to figure out why the new ip hasn’t registered in dns.  upon reviewing the event log of the machine, you discover events that look eerily similar to these: Event Type: Warning Event Source: DnsApi Event Category: None Event ID: 11163 Date: 8/12/2008 Time: 5:32:32 PM User: N/A Computer: myComputer D