Re: Migration from SBS2000 to Windows 2000 Server.. by Jeff
Jeff
Thu Jan 27 21:01:25 CST 2005
Imaging the original server isn't the more critical part of the process.
There are several way to protect yourself without having to have the entire
server system drive to image. Another DC, or a System State backup are all
that you need to have. Since 95% of the Swing It!! Kit steps are performed
offline from the domain, this means that the only thing you are protecting
yourself against is the addition of another DC, not any of the changes that
follow.
Theres's a T-shoot item in the kit that explains how to backout the addition
of a DC. I consider the risk to be relatively low, in the minor level.
"Cyber_wizard" <Cyberwizard@discussions.microsoft.com> wrote in message
news:C7EE43BC-441E-41FB-A9C1-B871B0D3314C@microsoft.com...
> How about if I transfered all the data on the PDC to the BDC reset the
> permissions,
> adjusted the logon scipts to refer the BDC, and removed most if to all of
> the reliance of the PDC to apoint it was only in use to authentacate the
> log'ons ?
>
> and at that point turned off the PDC and promoted the BDC to the PDC...
>
> the server name change won't have to much of an impact on anything we do..
>
> other than a couple of applications that will need to be reinstalled on
the
> client side
>
> I have the sbsmigration kit "swing it", however I am unable to image the
> sbs2000's primary partition as its using a 431 array and nothing I have
seen
> supports mirroring a raided drive.(as to be done while reading page
24-25)..
> therefore I am concerned with making changes to the AD with out having a
> really quick and easy way to restore if all turns to do do's
>
> License's won't be a problem we have all the licenses via our select
> agreements with microsoft, being an aquired company our SBS2000 license's
are
> something "we" purchased before we where aquired, and are not really a
loss
> if we don't use these...
>
>
>
>
> "Jeff Middleton [SBS-MVP]" wrote:
>
> > This question is really simple and yet seems to beg for not assuming too
> > much. :)
> >
> > Yes, you can do that, you can either handle that by a Role Seizure or
Role
> > Transfer. However, you should be aware that your licensing may not be
> > adequate to allow you to do that. If you are asking this so that you
could
> > recover from a disaster, then this is part of that concept. If you are
> > trying to replace the SBS Server with that other server, then there are
> > complications due to the fact that your network paths and namespace just
> > changed, it will break things from the client station viewpoint.
> >
> > If you are trying to replace the SBS with a new server and this is only
part
> > of a larger plan you are making, you might want to look at
> > www.SBSmigration.com, my website outlines much of that process for you
to
> > see.
> >
> >
> > "Cyber_wizard" <Cyberwizard@discussions.microsoft.com> wrote in message
> > news:3521BCA3-CDAB-49C4-BF2A-4C61A089FB73@microsoft.com...
> > > HI,
> > > I have a sbs2000 server with an additional Windows 2000 server,
> > > installed as an additional domain controller or backup domain
controller,
> > is
> > > there any reason that I cannot turn the sbs2000 server off and promote
the
> > > BDC to the PDC?
> > >
> > >
> >
> >
> >