Re: Changing servers

Many thanks for your help.

Steve.


"Danny Sanders" wrote:

If I just load the 2003 server (standalone) and use the wizard to set it
up
as a domain controller with the same domain name and set up all the user
accounts, do I have to log the existing workstations off the older domain
and
then add them back when my new server is on the network?


Yes you will have to remove your clients from the old domain and add them to
the new domain. The fact that you gave them the same name means nothing to
the clients. Doing it this way will result in new profiles being created for
each user in the new domain. In my experience changing a user's profile is
usually a big inconvenience to the users.

Alternatively, can I just manually create a computer account in Active
Directory (on the new server) for each workstation and then carry on using
as
before.

Again you are joining them to a new domain.

The way you started is the way to go if you want the least disruption of
your users.

However, when adding DNS to the new server, it came up with an error
message
at the end when trying to write to the registry and DNS would not work
correctly.

I would suggest posting what the error is and when it comes up. Solving this
error would be less work on you and less disruption on the clients.

hth
DDS
"Sawlmgsj" <Sawlmgsj@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DE85B583-D371-40E1-A2EB-8C1BB12D0BBA@xxxxxxxxxxxxxxxx
I am changing from Windows 2000 Server to Windows 2003 Server.
I went through the process of adding the new 2003 server as a domain
controller to the existing and then moving the roles. So far all went
well.

However, when adding DNS to the new server, it came up with an error
message
at the end when trying to write to the registry and DNS would not work
correctly.

If I just load the 2003 server (standalone) and use the wizard to set it
up
as a domain controller with the same domain name and set up all the user
accounts, do I have to log the existing workstations off the older domain
and
then add them back when my new server is on the network?

Alternatively, can I just manually create a computer account in Active
Directory (on the new server) for each workstation and then carry on using
as
before.

Thanks,
Steve.




.

Relevant Pages

  • Re: SBS Slow user logons problem
    ... You deleted both accounts and created new accounts for them (I also saw the ... Go to all workstations, log in as the Domain Admin and delete ALL profiles ... I have deleted the Reverse DNS zone on the SBS server and recreated it. ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Slow user logons problem
    ... You deleted both accounts and created new accounts for them (I also saw ... Go to all workstations, log in as the Domain Admin and delete ALL profiles ... I have deleted the Reverse DNS zone on the SBS server and recreated it. ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • RE: New SBS2003 and networking problems
    ... server has dhcp and working properly. ... when i try to connect shared files from workstations it takes so long time. ... DNS was successfully queried for the service location resource record ... Host records that map the name of the domain controller to its IP ...
    (microsoft.public.windows.server.sbs)
  • Re: User Based Slow Logon and Auth
    ... Workstations are WinXP Pro SP2 with all updates installed. ... The ERP is tied to the domain user for logon and that times out ... I have an SBS 2003 R1 server running my domain. ... made the user accounts in questions local administrators to the ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Slow user logons problem
    ... You deleted both accounts and created new accounts for them (I also saw the ... Go to all workstations, log in as the Domain Admin and delete ALL profiles ... I have deleted the Reverse DNS zone on the SBS server and recreated it. ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)