Link to home
Start Free TrialLog in
Avatar of Jarrod Adams
Jarrod AdamsFlag for United States of America

asked on

specific detailed ADMT 3.0 instructions...

Hi-
I've got two 2003 servers.  One has the correct domain set-up for users and roaming profiles but a non-optimal domain name (server A).  The other server is set-up properly as a child to our main domain (server B).  I figured the best way to handle would be to use ADMT 3.0 to migrate the current domain set-up with profiles on server A to the server with the proper domain naming set-up on Server B.

I had some limited success transferring over test user and computer items, but my results were far from optimal.

I would like someone to tell me or point me to an article that describes exactly what the ADMT procedure should be.  How to prep the servers, what files to transfer over first and how to do it.  How specifically to handle or move the roaming profiles folders or should ADMT do it for me?  That type of specific detail, with the goal of moving the domain and objects over "perfectly."  I'm willing to follow just about any instructions to the letter.  I just want to get it right and understand it.

thanks
J  
ASKER CERTIFIED SOLUTION
Avatar of Bartender_1
Bartender_1
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jarrod Adams

ASKER

I've read numerous links and articles from these links, and I'm still frustrated.
So many questions.
How to establish and test an RPC?  Do RPC's need to be in place prior to "the migration"?  What is "the migration", anyway?  What part should be done first?  the users? The computers?  Do all of the users get transferred at once, or do they have to be done one-at-a-time? Should I even bother with the ADMT or is it a lame tool and should I use a better easier faster more reliable 3rd party tool?  Do I need to transfer FSMO roles prior to the migration?  Can I install the ADMT on multiple machines, or is it best to only install it on the destination domain controller machine?  If it doesn't work from that machine, what have I not done to prepare or make these two computers communicate fully?  Should I just recreate the users and network from scratch on the new server and call it a day?

IS this supposed to be a super easy or a super hard task.  I don't think I have crazy old or unorganized or misconfigured servers or networks.  Why isn't this easier to facilitate?  I've been doing this long enough to believe that if the instructions are bad it's usually because you don't need them or noone is able to write them.

Any more help? please

thx
J
I solved my issue by "demoting" the server whose name and domain I wanted to keep.  I made this 2003 server a "roleless" server and added then joined it to the original domain as a general workstation.  Once I had this relationship establish (either bypassing or solidifying the rpc's and trust relationships and connectivity) I then installed Active Directory on the new server 2003 machine and created it as the domain I wanted to move into.  The act of creating this domain, disengaged the new server machine from the old domain, but the relationship/trust/conectivity remained and allowed for ADMT to be used without flaw.  I happened to migrate users first, then computers.