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

[Jim]

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!

 

[Chriss3]

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.

 

[Cary Shultz [A.D. MVP]]

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]

Cray thanks for the information, much appreciated that.

--
Regards
Christoffer Andersson

No email replies please - reply in the newsgroup

 

[Cary Shultz [A.D. MVP]]

Not a problem, Chris.

You can not know everything! The only question is that is this seven-day
temporary Trust available when going from SBS 4.5 to SBS2003 like it is when
going from SBS2000 to SBS2003. I have not had any time to really look that
up.

Cary

 

[Jim]

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

We want to move to standard edition 2003 server, not SBS server 2003. I
can't believe that once you go SBS you can NEVER, EVER upgrade to standard
edition. What do other companies do that successfully grow out of SBS?

Thanks for your advice about going to the SBS newsgroup.

 

[Cary Shultz [A.D. MVP]]

Sorry,

Well, you did state that in the subject line. Definitely missed that.
Maybe I need to take off my glasses!

You are correct. There is a migration package ( if that is the correct
term ) for going from a SBS environment to a "standard edition" environment
when you 'outgrow' the SBS constraints.

I would have to look this up on how to best proceed. You might want to go
to the SBS newsgroup and post that question in there and I will work on it
from this end. It might take until tomorrow for me to have some sort of
answer for you.

Cary