Phillip
Tue Mar 15 12:17:13 CST 2005
You should never use the Administrator Account to run Services. Each Service
should use it's own unique and distinct account or just use the System
Account. Exchange has server steps to go through to change the Service
Account and it can easily get screwed up.
How to change the service account
http://support.microsoft.com/default.aspx?scid=kb;en-us;152808
The "How to Change the Exchange Server 5.5 Service Account" white paper is
available
http://support.microsoft.com/kb/266041
How to change the service account password
http://support.microsoft.com/default.aspx?scid=kb;en-us;157780
To check for other dependencies use the utiliy called DumpSec (formerly
called DumpACL) by Somarsoft for find other services and what accounts they
use.
SomarSoft Utilities
http://www.somarsoft.com/somarsoft_main.htm
DumpSec Download Page
http://www.systemtools.com/cgi-bin/download.pl?DumpAcl
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"David K" <test@noemail.com> wrote in message
news:6k7e311sus5k93pu72b0bpm5h665e85snp@4ax.com...
> I'm running an NT4 based domain.
>
> I'd like to change the built-in Administrator account password. My
> boss tried changing it before I worked here, and he says everything
> stopped working and he had to call a guy to come change it back. That
> was kind of vague to me, but I know at least Exchange stopped working,
> as well as a Visual Foxpro based database application that users
> access via a file share.
>
> I know I need to take appropriate steps for changing the Service
> Account in Exchange, and I'll deal with BackupExec as well. I did a
> query on the services on both servers, and it appears that everything
> else is using the LocalSystem account.
>
> Is there anything else I should check for, to be certain that there
> are no more dependencies on the Administrator account?
>
> Thanks,
> Dave