Re: Building new domain

Tech-Archive recommends: Fix windows errors by optimizing your registry

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


Date: Fri, 10 Sep 2004 10:18:47 -0400

Should have added that if there are problems with the Active Directory that
you might want to run dcdaig /c /v and netdiag /v as a start. Repadmin
/showreps and repadmin /showconn might be a couple of other things to run.
So would netdom query fsmo. All of these tools are available from the
Support Tools.

HTH,

Cary

"Cary Shultz [A.D. MVP]" <cwshultz@mvps.org> wrote in message
news:ujK4QwzlEHA.2880@TK2MSFTNGP14.phx.gbl...
> Wayne,
>
> What are the reasons that your client wants to rebuild? Maybe this is the
> real issue....
>
> One possible method would be the run ldifde on one of your current Domain
> Controllers with all of the switches to get the user account objects and
the
> correct 'fields' and another time for the groups to .ldf files. You could
> use ExMerge for the mailboxes ( this creates user1.pst, user2.pst,
> user3.pst files ). It is generally suggested to not run ExMerge on the
> Exchange Server itself ( due to the high 'resources' used during ExMerge -
> but if you are doing this after hours.... ). For the user files and
folders
> I suspect that a good backup would be in order. Then you could wipe an
> load. Once you have the Servers set up ( sorry, can not be of any help
with
> SQL ) you would simply import the .ldf files ( which would create your
user
> account objects and your groups - naturally do the users first....and you
> could do this all as one file - I just like to separate them where
> possible ) and import the .pst files ( from the initial ExMerge process )
to
> populate your mailboxes. You could then do a restore from backup ( you
> would simply choose To another location... and then specify the location )
> for the user's files and folders. This would not really help you, though,
> with the permissions that were in-place.
>
> Also, you would have to join each WINNT, WIN2000 and WIN XP Pro system to
> the 'new' domain. Which is going to create a little bit of work for you.
> You could possibly look at netdom ( a part of the Support Tools ) to help
> with this. Additionally, you are going to have a problem with the user
> profiles. Well, actually, this is not a problem. Just make sure that no
> one stores anything locally ( read: that everything is stored on the File
> Server ). You will have to determine if you are going to walk to each
> workstation, log on as user1, then log off as user1 and log on as the
local
> Administrator ( or a member of the Domain Admins ) and - via Windows
> Explorer - copy the user profile for user1 from the 'old' domain to the
> 'new' domain profile. There will invariably be a few little things (
> usually shortcuts ) that will not work.
>
> Again, this is one very simplified version of how you could do this.
>
> By indicating that all of the remote sites are connected via fast links
are
> you saying that you have not set up Sites in the Active Directory Sites
and
> Services? So, you have only the default 'Default-First-Site-Name' and no
> others?
>
> HTH,
>
> Cary
>
>
>
> "Wayne" <anonymous@discussions.microsoft.com> wrote in message
> news:816b01c495b4$9f2599f0$a601280a@phx.gbl...
> > Hi,
> > My client wishes to start over fresh with his AD/domain,
> > that is - rebuild it from the ground up. He has about 80
> > users in the main office, and 3 small remote sites. The
> > remote sites are all on fast links and different subnets,
> > with cisco routers taking care of Nat, so I don't have to
> > deal with setting up sites. He wishes to use his existing
> > domain name, so I do not see how I can build the new AD in
> > parallel with the old. The new system will have 5 DCs, 2
> > at main office and 1 at each remote site. Additionally I
> > have to build a new 2000 exchange server, SQL 7 server and
> > application server to replace his existing machines.
> > So...all DCs and application servers will be replaced, but
> > all workstations will remain. Will I have to remove all
> > of the workstations from the domain and then rejoin them
> > to tne new domain? (the domain name will be the same, but
> > we want a fresh AD) We are going to start fresh for the
> > mailboxes, that is have the users back up to PSTs, build
> > new exchang/mail boxes, then set them up in outlook.
> > Other then involving a bunch of grunt work, what are some
> > of my options? Scripting? - I have very little experience
> > here. Any suggestions for planning, etc will be greatly
> > apprecated.
> > Thanks - Wayne
>
>



Relevant Pages

  • Re: 2003 Migration
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: i got 6 server in company which contains NT4 , windows 2000 , windowser 2003
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: Urgent Advise - [WildPacket]
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)