I work in a large organization that is still using a
windows NT 4.0 domain with several trusts running with
other domains. Currently all workstations in the company
are running windows 2000. We had a specific naming
convention we used on the workstation. However, we had to
change the naming convention to something new which
required us to "rename" each computer on the domain. The
way that this was done was to remove the computer from
the domain (by adding it back to a workgroup), requiring
a reboot. Renaming the computer, requiring a reboot. Then
joining it back to the domain, requiring a reboot.
However, from a previous company I worked for, if we
wanted to change a computer name that was already on the
domain, we just changed the computer name while it was on
the domain (which it allowed if you had the proper
credentials to add machines to the domain). Someone had
said to me that you cannot do this because it will
eventually fail with trust relationship problems when a
user trys to login. I have yet to find this to be a
problem. But I am not 100% sure this is a good thing. Any
suggestions? I do know that if you do it the first way i
described, and you skip reboots, it will hoze up the
system and trust relationships with workstation/domain
will arise. I just don't know about renameing ws while on
the domain (which does work).
Thanks.
|
Similar Threads
