Re: Ramifications of chaning admin password
- From: "MDBJ" <me@xxxxxx>
- Date: Thu, 8 Dec 2005 13:02:06 -0500
write down the admin password, lock it up, and NEVER USE IT AGAIN
it can't be snagged, if it's never used.
make another admin account for yourself and use that sparingly
make another poweruser account for yourself and always use that
apply your change policy to the latter two.
"epigram" <nobody@xxxxxxxxxxx> wrote in message
news:1134049169.a24baed9cf1c268f219c30e0687d30e9@xxxxxxxxxxxxxxxxxxxxxx
> I've recently updated my password policy and as a result I updated my
> admin password to comply. When I did this I knew that there would be
> items (backup jobs, scheduled tasks, etc.) that would now fail as they
> were setup to run under the admin account, but with the old password. I
> tried to remember everything, but indeed I forgot some items and those
> items all failed to run successfully until I updated the password
> associated with the job/task. I will be chaning this password frequently
> and wanted to know how do people deal with this scenario? I suppose one
> scenario is to not change the admin password, but that seems to defeat the
> purpose of updating my password policy to make my network more secure.
> The other scenario is keep a laundry list of the jobs affected by a change
> to the admin password and just update all of them every time this occurs.
> This just seems like a major pain. Any help would be much appreciated.
>
> Thanks!
>
.
- References:
- Ramifications of chaning admin password
- From: epigram
- Ramifications of chaning admin password
- Prev by Date: Re: ISA2004 "failed conection attempt"
- Next by Date: Migrate SBS 2k3 to new 2k3 on a different hardware
- Previous by thread: Ramifications of chaning admin password
- Next by thread: Re: Ramifications of chaning admin password
- Index(es):
Relevant Pages
|
