Re: New Server BUT now "fresh" Users!! :(

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Dan (anonymous_at_discussions.microsoft.com)
Date: 08/08/04


Date: Sun, 8 Aug 2004 15:15:21 -0700

Seems that way.
I have found this:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;296592&Product=win2000

Which requires removing from the DC, renaming the
rejoining the DC.

BUT as the current server is called "server". I would
have to join the "newserver" to the domain. remove the
old from the domain at which point all domain control
should be handed over to new server. Then change the
name of the old server, join it to the domain again,
remove the new server from the domain, rename, then
rejoin.

Seems an awful lot of possiblity for stuff up :) haha

I think i'll try the "restore" option first. At worst it
will stuff up the new server if im unlucky and i'll have
to reload it......at best it will work exactly as the
existing server with correct name etc :)

Either way the original server will be 100% untouched and
there to connect backup if need be.

>-----Original Message-----
>You won't be able to rename a Windows 2000 domain
controller, unfortunately.
>
>Oli
>
>
>
>"Dan" <anonymous@discussions.microsoft.com> wrote in
message
>news:209a01c47d50$843c8170$a301280a@phx.gbl...
>> Thanks for the reply. Sounds like the way to go.
>>
>> One final question.
>> Say the current server is called "SERVER" 192.168.0.1
>> say i rename the new server to "NEWSERVER"
192.168.0.150
>>
>> I then join it to the domain as discussed and all AD
info
>> is replicated across.
>>
>> When i then DEMOTE (using dcpromo) the existing server
so
>> the new server is the then PDC taking over the roll of
>> the old (and the possibly later dcpromo the old out of
>> being a DC at all), will i NOT then be able to rename
the
>> NEW server to SERVER? (and change IP to 192.168.0.1)?
>>
>> Im guessing this is the case, which will no doubt cause
>> issues with mapped drives/shares amoungst other things?
>>
>>
>>
>>
>>>-----Original Message-----
>>>I would dcpromo the new server into the existing
domain,
>> but leave the
>>>existing server there as a backup DC (assuming you have
>> an extra license, of
>>>course).
>>>
>>>Another tip here is to make sure your DNS is AD-
>> integrated. Point your new
>>>server's DNS to the old one, dcpromo it into the domain
>> and add the DNS
>>>Server component to the new machine. At this point,
>> check that the DNS
>>>records are on the new server. Then, change the DNS
>> settings in TCP/IP to
>>>point to itself and reboot. Then, make the new server
a
>> global catalogue
>>>and transfer the FSMO roles to the new box. I'd be
>> inclined to leave the
>>>old server running for a few days just to make sure
your
>> backup routines for
>>>the new server are working properly and that
>> everything's OK. Then, you can
>>>dcpromo the old server out of the domain if you wish.
>>>
>>>I wouldn't try a backup and restore to the new server.
>> You'll run into
>>>hardware issues and it's unlikely to boot.
>>>
>>>Hope this helps
>>>
>>>Oli
>>>
>>>
>>>"Dan" <anonymous@discussions.microsoft.com> wrote in
>> message
>>>news:219401c47d31$172c1150$a501280a@phx.gbl...
>>>> Thanks for the reply.
>>>>
>>>> I figured as much.....stupid me :) hehe
>>>>
>>>> I have put the old server back in (all is working
fine
>> as
>>>> i only "stuffed" round with 1 client machine (all
>> others
>>>> were off being a Sunday...lucky))
>>>>
>>>> Im going to attack it again tomorrow but to avoid
>> having
>>>> to stuff round on each client machine i will take
>> another
>>>> approach, which do you think is better?
>>>>
>>>> Firstly both Servers are Windows 2000...... yes i
know
>>>> but it was hard enuf getting em to spring for a
proper
>>>> Dell server (the existing server is just a crap
>>>> desktop "no name" system)....let alone upgrade OS to
>>>> 2003....not a huge demanding network 2k does the job.
>>>>
>>>> Option one is to backup the orignal server and use
>>>> http://support.microsoft.com/?kbid=249694 to restore
>> on
>>>> the new system. There is also
>>>> http://support.microsoft.com/default.aspx?scid=kb;en-
>>>> us;263532&Product=win2000
>>>> Which relates.
>>>>
>>>> This seems perhaps the "simplest" way though does
>> concern
>>>> me a little..... opinions?
>>>>
>>>> Other option is to remove the AD setup from the new
>>>> server and disable DHCP and DNS settings temporarly.
>>>> Then install/add the AD to the new server "adding" it
>> as
>>>> a 2nd Backup DC to the existing server. My
>> understanding
>>>> is it should the gather the AD info over the network
of
>>>> the existing server. I can then use "dcpromo" and
>> demote
>>>> the orignial server, which as i understand should
>>>> automaticly then move the PDC roles over to the new
>>>> server?
>>>>
>>>> From there i should be able to disconnect the orignal
>>>> server from the network (ensuring all data is copied)
>> and
>>>> then rename the NEW server to the old servers name
>>>> ie "SERVER", change the IP to the old servers IP,
>> enabled
>>>> DHCP and DNS with the same settings as he orignal
>> server
>>>> (which im pretty sure i have right) and then it
should
>>>> work?
>>>>
>>>> Do i have a clue or no idea? haha?
>>>>
>>>> Which option do you think is best for a novice,
>>>> the "backup' and "restore" or the AD transition
thingy?
>>>>
>>>> The old server is P4 2.4 on crap ECS MB with PCI Raid
>> IDE
>>>> (2 drives Mirrored) IDE tape (travan ewww).
>>>> New system is Dell 1600SC 2.8P4 Xeon 3x 74gb SCSI
>> (Raid5)
>>>> DAT72 SCSI tape etc.
>>>>
>>>> I'd image maybe some hardware issues with "restore"
>>>> option?
>>>> Im leaning toward this as it does not involve "any"
>>>> possibly to stuff up the existing server....where
when
>>>> in "demote" the existing server something could go
>> wrong
>>>> or similar?
>>>>
>>>> Ideas apreaciated.....thanks again for ya time.
>>>
>>>
>>>.
>>>
>
>
>.
>



Relevant Pages

  • Re: Domain controller name -rename issue
    ... Make sure you have at least a system state backup before starting the rename of the production one. ... The DNS host names of domain controllers in a renamed domain are not ... Windows NT 4.0 primary domain controller to Windows 2000 ... it with dcpromo /forceremoval to member server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Very strange problem with XP machine reporting ERROR_NO_LOGON_SERV
    ... unless DNS is dependent upon kerberos? ... and the DNS server is manually set in the ... rejoining, which I've already done). ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS name and NetBios name differ
    ... It doesn't take a lot more time than two hours to install SBS from 'format ... Once SBS is installed you - can not - rename the server just as you - can ... On a domain NetBIOS is not used, that's what DNS does. ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain controller name -rename issue
    ... The DNS host names of domain controllers in a renamed domain are not ... the domain rename operation is complete. ... with dcpromo /forceremoval to member server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: mycompany.local -> mycompany.com
    ... host an internet-accessible DNS or get your domain registrar to do it. ... The reason to rename the domain and do split DNS would be if you want ... w2k3 server DC, a W2k file/print server and a dozen WinXP ...
    (microsoft.public.windows.server.dns)