Danny,
we have roughly 64 servers. All of the NT servers are domain controllers for
a different domain. When the network admin left, we had already planned on
not only replacing the nt servers, but also removing some of the domains.
Nether of us were here when all of the domains were created, but I can't see
where it's really necessary to have so many domains. We have one main domain,
called funco. Last year we started moving users to this domain and have
gotten very close to removing 2 nt domains already. There will be one domain
for sure which is an nt domain which will have to remain, but we'd like to
make that a child domain, it's gander domain. Since I'm not sure what exactly
was done to change the domain admin password for funco, it's taking me a
considerable amount of time to find all of the problems. My main question
here is that we have 2 nt servers, one is a domain controller for gander and
the other runs apps and an sql db for that domain. I believe this is a
subdomain. I notice that these 2 servers are still logging into their domains
with the old gander domain admin password, should I change this or will
leaving this alone not cause any problems with trusts, etc? If I do need to
change this what's the safest way? Also, we are a bank and we have to meet
fdic guidelines, one of which is that admin domain level passwords are
supposed to be changed periodically. With so many apps and mapped drives and
servers and trusts and sql dbs, is there a safe way to do this on a regular
basis?
"Danny Sanders" wrote:
> I will help you if I can.
>
> If possible can you describe your network set up as far as how many and what
> type of servers you have. Are the NT servers in their own domain or are they
> BDCs and member servers in the Win 2k domain? Or are the Win 2k servers
> member servers in the NT 4.0 domain?
>
>
> What are you trying to accomplish?
>
>
> DDS
>
> "rodge" <(E-Mail Removed)> wrote in message
> news:19DE302A-FB95-4B10-BA62-(E-Mail Removed)...
> > Danny,
> >
> > thanks for the reply. Unfortunately, that's not going to be possible. We
> > actually brought in a vendor whenever the network admin was let go and my
> > department head wanted all domain administrator passwords changed.
> > Unfortunately, this vendor wasn't real sure of what they were doing and
> this
> > caused severe problems throughout the networks, some of which are still
> > occuring. I can get by without this server 2003 being a domain controller,
> so
> > I think I'll just do that until I can get the proper training. Any chance
> you
> > could help me on this in the meantime? I honestly don't know what steps
> the
> > vendor took to change dmoain admin passwords, but none of the nt servers
> > domain admin passwords are changed. I'm not sure how these nt domains are
> > even replicating with the 2000 domains, but is there a method for bringing
> > them up to speed? Concerns I have with this are services or programs using
> > that logon, but after going through the change on all the 2000
> > servers/domains, I'm not as worried with the few nt servers we have out
> there.
> >
> > "Danny Sanders" wrote:
> >
> > > I would suggest hiring the services of a consultant.
> > >
> > > With NT 4.0 DCs, Win 2k DCs, Win 2k3 DCs, and remote sites your network
> is
> > > complex enough that a lot of network admins would need some advice.
> > >
> > > hth
> > > DDS W 2k MVP MCSE
> > >
> > > "Rodge" <(E-Mail Removed)> wrote in message
> > > news:434B108A-9B14-4595-866B-(E-Mail Removed)...
> > > > Where can I find info on how to accomplish this? I have some nt4
> servers
> > > > which are domain controllers and most of the network is running
> windows
> > > 2000
> > > > server. there are currently no server 2003 domain controllers. Our
> network
> > > > admin was fired and I'm the closest thing to a backup. I have a server
> > > 2003
> > > > at home, but I've never dealt with a forest this big. We have several
> > > > domains. This is for a remote site, but it will be a backup domain
> > > controller.
> > >
> > >
> > >
>
>
>
|
Similar Threads
