Re: Migrating User Profiles After Moving To New Domain



ADMT can do it for you:
* move to another domain
* translate security on profiles and other data

have you tried ADMTv3?

Migration high level steps COULD BE:
* Make sure the AD has been configured (sites, subnets, replication, OUs,
GPOs, delegations, DNS, WINS, DHCP, etc.)
* Setup name resolution (WINS or DNS) between source and target
domain/forest
* Setup trusts (if an external trust is configured and sidhistory is used,
disable sid filtering)
* Install and configure migration tooling
* Migrate groups, user accounts with passwords and group memberships (with
sidhistory)
* Migrate clients from the source domain to the target domain, translate
security on the client, and translate profiles (at this moment users start
logging on with their new AD account on the migrated clients that have been
migrated previously to the w2k3 domain)
* Migrate mailboxes if needed
* Migrate servers to the new domain or migrate data to new servers
* Translate security (Re-ACL) of the data/resources from source security
principals to target security principals (replace the security descriptors
from the old domain with the security descriptors from the new domain )
* Cleanup temporary configurations
* Cleanup sidhistory (recommended!). sIDHistory is used to access resources
while those resources still have security descriptors from the old domain.
As soon as all data (file, folders, mailboxes, etc.) have been re-ACL-ed
sIDHistory can be cleaned. Sidhistory should only be used temporary for
migration purposes!
* Remove trusts
* Decommission old domain(s)


For more info on migrating to an AD domain also see:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/default.mspx

ADMTv3 has been out for a while, so be sure to use that version.
(http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en)

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Mike Poe" <trolling4dollars@xxxxxxxxx> wrote in message
news:1154514459.554169.69810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am planning a project where I will need to migrate aprox. 500 users &
computers from one active directory domain to another. A trust exists
between the domains, but they are not part of the same forest.

I'm comfortable using ADMT to move the user accounts. My question is
about the computer accounts & user profiles on the workstations.

If I use ADMT to move computer accounts from Domain A to Domain B, will
I still need to visit each workstation, remove it from the old domain &
join it to the new one - or is that done simply by moving the computer
account with ADMT? Also what about user profiles on the workstations?
When the user logs on to the new domain for the first time, will their
old profile still work (desktop settings / outlook settings / etc)?...
or will I need to copy the existing profile to the user after they've
logged on & set permissions / etc?

I had to do this very thing a long time ago on a much smaller scale -
maybe 10 / 15 users & computers - and as best I can remember I had to
visit each workstation to take care of the user profiles & domain
membership. I guess I'm looking for a way to automate this whole
process to avoid having to visit 500 some machines due to time
constraints.

Thanks for any suggestions.

Mike



.



Relevant Pages

  • Re: Local Profiles and Logins
    ... unless you choose to migrate the profiles. ... fact going to be performing an inter-forest migration. ... security translation on them for the new user's SID). ... deploying directory and security services. ...
    (microsoft.public.windows.server.active_directory)
  • Re: migration of domain and file server from NT 4.0 to 2003
    ... mean users, Group, Computers, Member servers, Profiles, etc. Please specify ... Is there any way so I can rename the username while migration? ... If I use DFS root server for consolidation and File server migration tool ... Translate security of the data from source security principals to ...
    (microsoft.public.win2000.active_directory)
  • Re: I cant select text using word 2007.
    ... With this being a new load with no profiles on the machine, ... Logging in as another user loads templates and add-ins from a different ... It's highly unlikely that the problem is the result of a security patch -- ... If you hover over the scroll bar, ...
    (microsoft.public.word.application.errors)
  • Re: Default User Serurity Permission
    ... and then the [File Security] section. ... and once a new MMC console opens, ... > profiles, I just changed them. ... >>Restore XP to installation Security Defaults ...
    (microsoft.public.windowsxp.security_admin)
  • Re: User Conectivity at Home
    ... systems are all secured via profiles and passwords. ... having a shared folder setup for "everyone" is a breach of such security. ... If your network is behind a NAT router, then your file sharing is more or less ... A designated folder for sharing to "Everyone" isn't a breach of security, ...
    (microsoft.public.windowsxp.network_web)