Re: Migrate to 2003

From: Jeff Mackeny (me_at_me.com)
Date: 06/18/04


Date: Fri, 18 Jun 2004 17:47:54 -0400

Herb, Ok you guys are freaking me out, I thought its a straight forward
procedure, upgrade is not an option because the reason for the migrate is
hardware fault, the entire hosting is currently on an old clone box which
must be replaced with a new box, will the ADMT utility do any good for me
(keep in mind AD is not installed on this server, will restoring to a new
box the system state blue screen the new sever since its totally different
hardware, please make it as lease complex as you can, why does MS have to
make everything so complex?

Please advice, thanks for your time and help
Jeff

"Herb Martin" <news@LearnQuick.com> wrote in message
news:uTPxTyVVEHA.3788@TK2MSFTNGP12.phx.gbl...
> "Jeff Mackeny" <me@me.com> wrote in message
> news:uadkpJNVEHA.3428@TK2MSFTNGP12.phx.gbl...
> > This for a hosting company, they are hosting a few hundred sites on a
2000
> > box, they want upgrade to a new box and 2003, the 2000 box does not have
> AD
> > on it just DNS with hundred of entries for all domains they host, so
> > basically the main thing I need to move over and migrate is all the DNS
> > entries and IIS setting and site folders, what's the best method of
> > accomplishing this, also can anyone point me to a good tech note on how
to
> > properly configure DNS for a hosting company.
>
> Have you considered just UPGRADING the machine to Win2003?
>
> If you have new hardware then you can backup the machine (System
> State will get most of the "settings" including DNS but not the data
> such as the web sites themselves so do both a System State and data
> backup), and reload this on the new "Machine."
>
> You will probably have to boot in "VGA" or even safe mode to
> straighten out the video and some drivers -- you may even need to
> do a "repair install" (from the CDROM) if their is a difference in
> SCSI drivers or something so critical, but still it should be possible
> to migrate using a backup/restore.
>
> Then upgrade it. If it works (it almost always will) then you proceed;
> if it doesn't you haven't lost anything.
>
> Someone else suggested "make the new machine a secondary" which
> I too will sometimes suggest but that is tedious for hundreds of sites
> and doesn't handle the IIS metabase as well.
>
> There is another poster here who has created a migration too for the
> DNS but you still have to fool with the IIS parts.
>
> My vote is for the backup/restore/upgrade -- at least try it.
>
> --
> Herb Martin
>
>
> >
> >
> >
> >
> >
>
>



Relevant Pages

  • Re: Migrate to 2003
    ... be the same OS, Server2000->Server2000 then upgrade. ... Herb Martin> ... >>> basically the main thing I need to move over and migrate is all the DNS ... >> If you have new hardware then you can backup the machine (System ...
    (microsoft.public.win2000.dns)
  • Re: Replacing running Win2000 DC with new Win2003 DC
    ... I've generally favoured separate DNS for small Domains. ... say that, Herb? ... Upgrade isn't impossible in that case but you really should consider ... Replication of DNS changes is another, and maybe the main reason people ...
    (microsoft.public.win2000.active_directory)
  • Re: speech recognition & e-mail messages probs !!!
    ... it's just the periodic upgrade to DNS ... During the installation process you activate it over the ... With regard to the KnowBrainer program, it will work exactly the same ...
    (microsoft.public.windows.vista.general)
  • RE: NT 4.0 to Windows Server 2003 Upgrade
    ... When I start the upgrade process ... | would it be better to configure DNS through the AD wizard? ... My question is, when should I add my static servers, ...
    (microsoft.public.windows.server.migration)
  • Win2kAdv upgrade hints from NT done sucessfully - Thank You
    ... The server is a fully integrated W2KADV AD DNS Server. ... When upgrading, before you upgrade, update the Server bios with the ... Nics on the inside have to resolve to ...
    (microsoft.public.win2000.dns)