Re: Migrating Windows 2003 to Dissimilair Hardware

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Robbie Wallis (robbie.wallis_at_virgin.net)
Date: 02/06/04 

Date: Fri, 6 Feb 2004 09:50:19 -0000

Hello
not a domain controller but standalone web server

Robbie

"SaltPeter" <SaltPeter@Jupiter.sys> wrote in message
news:ueGUb.7117$ZN1.611489@news20.bellglobal.com...
> "Robbie Wallis" <robbie.wallis@virgin.net> wrote in message
> news:e9QEJzD7DHA.1636@TK2MSFTNGP12.phx.gbl...
> > Hello,
> > We are in the process of upgrading our hardware range which requires us
to
> > move windows 2003 installations from single p4 IDE systems to Dual Xeon
> RAID
> > SATA systems
> >
> > We are aware of this article
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;249694
> >
> > A straight ntbackup failed with reboot loop and also a veritas restore
> with
> > just SAM/SECURITY Hives failed
> >
> > Any ideas if the procedure above for win2k will work in this situation?
> Any
> > advice?
> >
> > Thanks
> >
> > Robbie
> >
>
> Benny Hill use to say when u "assume", U make an ASS out of U and ME. So
> i'll be an ASS and assume we are talking about domain controllers. Note
that
> the article specifies that the HALs must be similar.
>
> You'll probably save yourself a lot of trouble by installing W2K3 servers
> while specifying mass storage controllers on new systems. Joining the
> domain, promoting the servers to DC if that is your intention. Transfer
the
> FSMO roles off the "soon to be retired" DCs. Double check that the
procedure
> was completed properly (ntdsutil, netdom, dcdiag). Wait a week and then
> decommision the extra servers via dcpromo. Double check then triple check.
>
> You can also install old OS on new systems, join, promote, upgrade to
W2K3,
> transfer FSMOs and demote old servers later.
>
> Installations don't take that long, and there is no excuse as far as
> sharenames and name resolution since DNS and login scripts should easily
> rectify any URL the old systems were sharing out to clients.
>
>
>
>
>

Relevant Pages

  • RE: Strange Irregular DNS/Networking Problems
    ... Never heard about this kind of problem with IPv6, but think this is because it is not used so much until now. ... What i heard is that firefox or some other not MS browsers and addons make problems with DNS resolving after changing DNS servers. ... After resetting the domain controller and booting up things are back ...
    (microsoft.public.windows.server.dns)
  • Re: Authentication problems when DC is down
    ... Please post an unedited ipconfig /all from the 3 DCs and the SQL server, so we can exclude DNS as a problem. ... have narrowed this down specifically do the domain controller holding ... DC2, DC3), all run AD and DNS and all are GC servers ... any SQL servers using Windows ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication Issues with A/D
    ... site link BRIDGING is that is connecting the spokes together and because ... Site A's subnet can talk with ALL subnets in our network ... the first problem I have is that Site D's domain controller (it ... "All servers in that can replicate partition ...
    (microsoft.public.windows.server.active_directory)
  • Re: machine account password replication not working
    ... This is checking FRS replication. ... > Install the Support Tools on each Domain Controller and on each Member ... Run netdiag /v on all servers. ... The member servers reported access denied ...
    (microsoft.public.win2000.active_directory)
  • Re: No logon server available - Windows 2003 Trust Issue? NS Issue?
    ... If this computer is a domain controller for the specified domain, ... NetBIOS Remote Cache Name Table ... NetBIOS which use WINS or lmhosts is necessary in NT 4.0. ... as secondary DNS servers on each W2k3 DC. ...
    (microsoft.public.windows.server.networking)