Hello Mike,
You must have Administrator privileges in the source domain.
If the target is Windows 2000, you must have Domain Admins privileges in
the target domain
If the target is Windows Server 2003, you must have either Domain Admins
privileges or the delegated extended right “Migrate sIDHistory” in the
target domain
Built-in and well-known groups are not migrated by ADMT.
If necessary, you can add the sID from a source principal to the
sIDHistory of a target principal if you meet the same prerequisites as
above by using sidhist.vbs.
Please note that sIDHistory carries with it the potential for complicating
resource administration & exploit by nefarious administrators and is not
intended to be a long-term strategy for managing resource access. See
289243 MS02-001: Forged SID Could Result in Elevated Privileges in Windows
2000 for more information.
Rather than relying long term on sIDHistory, you should be encouraged to
follow Best Practices suggestions for configuring resource permissions &
group memberships.
Thank You.
Diana.
(E-Mail Removed)
This posting is provided "AS IS" with no warranties, and confers no rights.