It sounds like you are saying that the profiles are not moving to new
machines, only that the machines are moving to a new domain.
If that's the case, there shouldn't have to be a transfer of profiles.
Are the users moving from one domain to another?
If they are moving from the NT domain to the AD domain, then migration tools
should be used to migrate their accounts, if not the machines as well. MS
has the free Active Directory Migration Tool. Quest and other 3rd parties
have tools that may be better, but aren't necessarily free. If the accounts
are migrated properly and the machines are prepared properly using the tools,
you won't have to do anything else.
In any case, the 2 domains are going to have to establish a trust with each
other or you won't be able to do much of anything.
If those things are unacceptable, then you can use a Windows Resource Kit
utility called "subinacls". It should be a free download from the MS
Website. That utility can be used for example, to search for a domain name
and replace it with another domain name in the ACLs of the profiles. That
way, as long as there is a trust between the domains and the new user
accounts in the AD domain have the same names as the old ones, the ACLs
should get updated. It basically does a "human name to SID translation".
If the user accounts are not going to be in a new domain, that changes
everything. In that case, as long as the NT and AD domains trust the domain
that the accounts are in, you don't have to do a thing. Machines in both
domains will recognize those accounts.
Let us know if in fact the users are getting new machines. Then, of course,
it would involve a profile transfer.
