Re: Migrating NT 4.0 SBS Domain to Win2003 Std Ed. server and Active Domain

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Cary Shultz [A.D. MVP] (cwshultz_at_mvps.org)
Date: 05/05/04 

Date: Wed, 5 May 2004 07:28:04 -0400

Chriss,

The problem with running SBS is that you can not have any trust at all! So,
changing the Admin password - while an excellent idea normally - will
probably not help in this situation ( this is one of the limitations to
SBS! ). However, this is an excellent idea. There are just a few things
that are a bit different when dealing with SBS. Now, when going to SBS2003
there is that seven day grace period in which you can have a trust
established - exactly for this sort of thing ( when migrating and using
ADMT - or some other third party software - you will need that trust ).
However, I am not sure that this applies when going from SBS 4.5 to SBS2003.
I know that it applies from SBS2000 to SBS2003. Do you have that info?

Jim,

I might suggest that you post this in the SBS newsgroup. There are some
really smart people in there who have probably faced this before and will be
able to give you some first hand experience.

I really hope that you are going to need to spend the $245.00 with MS to get
that magic egg beater. Not yet, anyway.

I might look into the temporary trust that SBS2003 allows for migrations
from previous versions. I do not know if it applies to SBS 4.5...I know
that you mentioned SBS running NT4. I assume that you mean SBS 4.5???

HTH,

Cary

"Chriss3" <noSpamHere@chrisse.se> wrote in message
news:um0Q1JfMEHA.1032@tk2msftngp13.phx.gbl...
> Jim one trick that have worked for me some times when migrating from
> NT4.0 -> 2003 is to change the Administrator account password to match in
> both domains during the migration process.
>
> --
> Regards
> Christoffer Andersson
>
> No email replies please - reply in the newsgroup
> ------------------------------------------------
> http://www.chrisse.se - Active Directory Tips
> "Jim" <nobodyhome@antispam.tv> skrev i meddelandet
> news:uTbfwadMEHA.1348@TK2MSFTNGP10.phx.gbl...
> > We have a small business runing NT 4.0 SBS (service pack 6a) with one
> > Win2000 file server and we need to upgrade to Win2003 Std. Edition
Server.
> > The domain controller is an old server (> 7 years old, tired, out of
> > waranty, and obsolete) and I can't seem to do *anything* with mirgrating
> the
> > accounts off it to a new domain controller.
> >
> > I have a brand spanking new server with Win 2003 Std. edition server in
> it's
> > own domain.
> >
> > I want to migrate the users over to this new domain, then have the file
> > server join the new domain with security intact.
> >
> > I have looked at the Active Directory Migration Tool V2. But I can't
get
> it
> > to work, presumably because I can't get it to establish a trust with the
> new
> > domain ("Access Denied" whenever I try to establish the trust), though I
> > easily established a trust relationship on the new domain to the old.
> When
> > I run ADMTV2 from the target domain (the new one), I get "access denied,
> > error code-5, domain=olddomain). If I try to be clever and run ADMTV2
on
> > the old domain (the 2000 server), the message get is "network path not
> > found, error code=53, domain=newdomain."
> >
> > I've also tried to use ClonePrincipal but it doesn't seem to understand
or
> > like the Win2003 active directory.
> >
> > I'm flumoxed.
> >
> > NT 4.0 SBS *won't* let me add a new domain controller. Nor will it let
me
> > run the migration tool to move the accounts to the new domain. I can't
> > experiment with trying to upgrade the SBS server to win2003 Std. Edition
> > because if that fails, I've got a dead domain and a business shut down.
> >
> > We do NOT want to upgrade to 2003 Server SBS because not-so-distant
plans
> > include additional domain controllers in one or more remote offices as
the
> > business grows and SBS "don't play that game."
> >
> > I inherited this system from a contractor who undoubtedly did a "quick
and
> > dirty" install of "everything in a can" SBS and now I can't upgrade it
> > (except to 2003 SBS - in place on the same machine, apparently), or get
it
> > off the old, tired, out of warranty equipment.
> >
> > Does anybody have any insight on how I can get out of this box. Are
there
> > any MS White Papers on this that I haven't been able to find? Or am I
> going
> > to have to spend hundreds of bucks with Microsoft support and pay for
the
> > privillage of buying the magic "easter egg" for this.
> >
> > Help!
> >
> >
> >
>
>

Relevant Pages

  • Re: Migrating NT 4.0 SBS Domain to Win2003 Std Ed. server and Active Domain
    ... > The problem with running SBS is that you can not have any trust at all! ... > established - exactly for this sort of thing (when migrating and using ... > I might suggest that you post this in the SBS newsgroup. ...
    (microsoft.public.win2000.active_directory)
  • Re: customized administrator privelages
    ... with SBS - which is a totally different animal from the 'regular' ... trust: either they trust you or they do not. ... I have started working at a new company as the IT administrator. ... The SBS Server is used as the file server and there is a particular folder ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k Domain -> SBS2k3 Domain
    ... Windows Small Business Server 2003. ... explains the use of ADMT in relation to SBS migration. ... the target may be configured to trust the source domain. ... it is not required to finish the ADMT ...
    (microsoft.public.windows.server.sbs)
  • RE: Creating Trust
    ... I'm not migrating from SBS. ... I would like create a trust between them. ... > relationship because this is not used for a Windows Small Business Server ... > Migrating from Small Business Server 2000 or Windows 2000 Server to Windows ...
    (microsoft.public.windows.server.migration)
  • Re: Trust Relationships
    ... The SBS box must also be the PDC (primary domain controller) - it can't be ... > and indeed I can now create a trust. ...
    (microsoft.public.backoffice.smallbiz)