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

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 want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …