Re: How to move the main server (win2003) on another computer?



Is it possible? Yes.

Is it wise? No!

You would be better advised to bring up a new domain controller, migrate the
Global Catalog and all FSMO/DNS/DHCP/etc functions to it, then demote the
original domain controller to a member server. Once that's done you can
migrate applications off it and onto the new server, then re-configure the
applications to see the new server rather than the old one. Then the old
server may be retired and rust (or rest?) in peace.

--
Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"p. Th." <theologos@xxxxxxxxxxxxxxxxxx> wrote in message
news:e9aBzyLoFHA.3236@xxxxxxxxxxxxxxxxxxxxxxx
> Richard G. Harper wrote:
>> No, you don't want to do this. REALLY you don't. Not unless you also
>> want to run a good risk of completely screwing the domain up, that is;
>> certainly you'll have problem with Active Directory and server
>> replication after you're done with it.
>>
>
> So, IOW, we'll be stuck with the old hardware?
> Because all our applications, shortcuts, settings a.s.o. are pointing on
> the server "A". We only wanted to do, let's say, create a server "B", see
> if everything is ok and after that get rid of "A" (format and put winXP on
> it) and after that rename the "B" to "A" and change its IP. Nothing of
> these things is possible?
>
> TIA,
>
> p. Th.


.



Relevant Pages

  • Re: Client performance problem windows 2003 server...
    ... >Subject: Re: Client performance problem windows 2003 server... ... >Deploying Active Directory for Branch Office Environments ... >results from not having a domain controller in a particular site. ... incorrectly applied site coverage will be bad for clients ...
    (microsoft.public.windows.server.networking)
  • Re: Client performance problem windows 2003 server...
    ... Testing server: Verkstadsgatan\VERKTYG ... Deploying Active Directory for Branch Office Environments ... results from not having a domain controller in a particular site. ... incorrectly applied site coverage will be bad for clients ...
    (microsoft.public.windows.server.networking)
  • RE: NTDS.dit file is currupt
    ... "microsoft" wrote:> We are currently facing a serious problem with one our client server. ... > After rebooting the machine in directory services restore mode, I had> followed the steps below; ntdsutil neither defrag Active Directory Database> nor repair. ... Restart the domain controller. ... Check the integrity of the Active Directory database. ...
    (microsoft.public.win2000.active_directory)
  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)
  • Re: Big trouble with DC in China
    ... > Since then, this server has so may errors in the event logs (KCC, ... > DNS, FRS) that I wouldnt know where to start. ... > Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)