J
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!
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!