Built-in Administrator acct. for Domain be password never expires?

Are there any risks associated with an expired built-in Administrator
password? I've been googling but can't seem to quite get results that speak
to this issue.

In article <#rMg9Ul5GHA.4616@TK2MSFTNGP05.phx.gbl>, <-> says...

> Are there any risks associated with an expired built-in Administrator
> password? I've been googling but can't seem to quite get results that speak
> to this issue.
>
>
>

The risk is that you cannot log in with the account once the password has expired without
resetting it. If an attacker is able to determine the original password, due to poor password
implementation, they could change the password from under you.
Brian

So is it better practice to have it expire, or to never expire?


"Brian Komar [MVP]" <bkomar@nospam.identit.ca> wrote in message
news:MPG.1f8b30636e4cb7849896c9@msnews.microsoft.c om...

> In article <#rMg9Ul5GHA.4616@TK2MSFTNGP05.phx.gbl>, <-> says...

> The risk is that you cannot log in with the account once the password has
> expired without
> resetting it. If an attacker is able to determine the original password,
> due to poor password
> implementation, they could change the password from under you.
> Brian

In news:%23rMg9Ul5GHA.4616@TK2MSFTNGP05.phx.gbl,
- <-> typed:

> Are there any risks associated with an expired built-in Administrator
> password? I've been googling but can't seem to quite get results
> that speak to this issue.

You can't make the built-in domain admin account password expire, to the
best of my knowlege.

Really, nobody should be using that account for their admin work anyway, nor
should it be used to run system services. Just set it up with a good,
complex password, write that down on a piece of paper and put it in a sealed
envelope, and give that to the company owner so that he or she can fire the
entire IT department without getting screwed over. Any techs working on the
network should have two accounts - one for daily use (user only), and
another that has the delegated domain permissions they need to do their
jobs. Complex passwords & regular changes should be forced.

This is an "ideal world" setup, but hey, we can strive for that, right?

I have to go with Lanwench on this one. Complexity is good. Keep it in a safe. Break glass in
case of emergency
Brian

In article <OwTGyQn5GHA.2044@TK2MSFTNGP02.phx.gbl>, <-> says...

> So is it better practice to have it expire, or to never expire?
>
>
> "Brian Komar [MVP]" <bkomar@nospam.identit.ca> wrote in message
> news:MPG.1f8b30636e4cb7849896c9@msnews.microsoft.c om...

>
>
>