Actually it is more secure the way it is then. I've been doing just the
opposite,...all our new machines use the Serial Number as the Name rather
than the "job". If the system ever has an intruder they won't have any
[easy] means to know what machine they are looking at.
I use the Active Directory "description" field to identify the machine.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Bradley" <(E-Mail Removed)> wrote in message
news:95642084-B538-4915-BF7D-(E-Mail Removed)...
> OK, thanks because I have a network of about 50 machines and there is no
> reasoning to the current names on the machine and I want to be able to
know
> what machine is where. Thanks alot BB
>
> "Phillip Windell" wrote:
>
> > Just change it. It won't bother anything after "replication" completes
and
> > all DCs "agree" on the new name. The SID is what really identifies a
> > machine on the Domain, not the name. Changing the name does not effect
the
> > SID, so the Domain still sees it as the same machine.
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Bradley" <(E-Mail Removed)> wrote in message
> > news
91C2141-4A6B-4BD8-9CC3-(E-Mail Removed)...
> > > I just wanted to know if anyone knew of a good way to change the
computer
> > > name after it has all ready been joined to a domain controller, I do
want
> > to
> > > be able to keep it connected to that domain I just want to change the
> > > computer name itself on the domain, the windows verison that are used
on
> > my
> > > network is 2000 Pro and XP Pro. Any help would be great. Thanks, BB
> >
> >
> >