Stingray
Mon Mar 05 18:57:53 CST 2007
I hope this post isn't too late to help you pdx. I just ran across this 2
part article that talks directly to what you are doing.
http://www.msexchange.org/tutorials/Migrating-Small-Business-Server-2003-Exchange-Standard-Part1.html
Hope this helps and good luck.
"Dave Nickason [SBS MVP]" wrote:
> I think this article gives you all the steps (despite the name, it applies
> equally to adding a ws03 DC to a 2K domain).
>
> How to upgrade Windows 2000 domain controllers to Windows Server 2003
>
http://support.microsoft.com/?id=325379
>
>
> "pdx" <pdx@discussions.microsoft.com> wrote in message
> news:7EA3342A-85AB-45FB-8047-DCE3196AB55B@microsoft.com...
> > Thanks for replying. Apparently there isn't a lot of knowledge available
> > about this issue.
> > Like you stated, from what I've been able to find out, dcpromoing down
> > doesn't seem to be a possibility, so it looks like I'll just shut the
> > machine
> > down when the time comes and use ntdsutil to seize the fsmo roles.
> >
> > KB 216498 explains the process for cleaning the old DC name out of the AD
> > and that seems straightforward (at least on paper).
> >
> > Do you know of any possible issues in adding a W2003 DC to an SBS 2000
> > domain? I know I'll have to run domainprep and forestprep beforehand on
> > the
> > SBS 2000 box since it holds the fsmo roles.
> >
> > "Dave Nickason [SBS MVP]" wrote:
> >
> >> I've been hoping you'd get an answer from someone who had actually done
> >> this. I only see two possible and closely related issues. I don't think
> >> the SBS box will let you dcpromo it down to a member server, and I think
> >> you
> >> may have issues with getting an absent DC out of the AD when you're
> >> finished.
> >>
> >> If the SBS will let you convert it to a member server first, that'll
> >> simplify things. Otherwise, you'll just have to figure out the procedure
> >> for getting a DC out of the AD. This is obviously possible, it's just
> >> not
> >> something I'm familiar with - doesn't come up much in the SBS world.
> >> Don't
> >> forget that if it does let you demote it to a member server, it's going
> >> to
> >> start behaving badly because of that, so you'll probably want to make
> >> sure
> >> you have all your data, app settings, etc. noted beforehand.
> >>
> >> If you get a chance, please post back and let us know how it went, so
> >> we'll
> >> know for next time the question arises.
> >>
> >>
> >> "pdx" <pdx@discussions.microsoft.com> wrote in message
> >> news:432644D8-C472-4A68-BD81-5D8DFDD4BC41@microsoft.com...
> >> > I'm close to migrating from a SBS2000 domain to a full Windows 2003. I
> >> > have
> >> > had Exchange 2003 and SQL 2000 running on different boxes for awhile
> >> > now.
> >> > I
> >> > use a Cisco PIX as my firewall. I don't want to go to SBS2003.
> >> >
> >> > After moving some final data/components off of the SBS2000
> >> > machine/domain
> >> > controller - and a
> >> > few other tasks - I need to retire the SBS2000 machine. My plan is the
> >> > following and I have a few questions that I'd appreciate any help with:
> >> >
> >> > 1) Remove an existing Windows 2000 DC from the network - as a "DC in
> >> > the
> >> > closet" fallback option
> >> > 2) Install a Windows 2003 machine and promote it to a DC in the SBS
> >> > 2000
> >> > domain. Also setup DNS on this machine and make it a GC.
> >> >
> >> > 3) Shutdown the SBS2000 machine and use ntdsutil to seize all FSMO
> >> > roles
> >> > to
> >> > the Windows 2003 DC.
> >> > Q: Would this be the recommended method for getting rid of the SBS2000
> >> > machine?
> >> > Q: Should I dcpromo it then shut it down (if it even can be dcpromo'd)
> >> > or
> >> > just shut it down and remove it from the network?
> >> >
> >> > 4) Use ntdsutil to clean up metadata that refers to the former SBS2000
> >> > machine. Remove references to the old server from DNS.
> >> > Q: What would be the best method for doing the DNS cleanup?
> >> >
> >> > * After the above steps I hope to have the same domain but with the
> >> > SBS2000
> >> > box removed and the domain now running as a full Windows 2003 domain.
> >> > Q: Will the above steps effectively get me to a full Windows 2003
> >> > domain?
> >> >
> >> > Thanks
> >> >
> >>
> >>
> >>
>
>
>