Re: ADMT and SID's

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


"WadeBart" <WadeBart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:06C4B1CA-FE53-4AF4-98EE-6FC53082C731@xxxxxxxxxxxxxxxx
How can I verify the SID history is coming across then?

Sorry, although I use ADMT and can hack through problems with it,
it is not something that most people including me use every day.

I would have to go look to figure that out, and probably look at YOUR
systems.

Try googling for problems with SID history now that you know the difference
between the new SID and the History, something like:

[ site:microsoft.com "SID History" ADMT | "directory migration
tool" ]

Or more widely:

[ microsoft: "SID History" ADMT | "directory migration tool" ]

You might add terms like [ "not copied" | failure | troubleshooting ] if you
don't
get enough specific hits up top.

Or, VERIFICATION, and perhaps "viewing sid history" as a quoted phrase.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


"WadeBart" <WadeBart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E03E13C7-7623-4473-958E-9477487C3461@xxxxxxxxxxxxxxxx
Why would SID's be different for an account that was migrated with the
ADMT.
I compared a source account SID to the migrated account SID and their
different.

Because the SID is created for the new account on the new domain.

I have a trust establed, without SID filtering and I tell the
ADMT tool to migrate the SID history.

Then the SID HISTORY should be there in addition but the new account
will have a NEW SID in the destination domain.

This seems to be only a problem with a
child domain of the source domain, and not with users in the actual
source
domain. I have an external trust setup to the source domain and
another
external trust to the child domain of the source.





.

Relevant Pages

  • Re: sIDHistory & SID Filtering...
    ... If I can remove sIDHistory from AD all together, ... If you have already migrated the user accounts and kept the SID history. ... >successfully completed our migration and no longer require sIDHistory. ...
    (microsoft.public.windows.server.migration)
  • RE: 2003 to 2003 Cross Forest migration
    ... Ok I have enabled the SID history on the ... SID filtering is enabled automatically on any trust relationships created ... even stricter limits on your trust relationships by enabling the Quarantine ...
    (microsoft.public.windows.server.migration)
  • RE: External Trust and Sid Filtering...
    ... is irrelevant since there will be no SID History for these groups. ... SID History is irrelevant and SID Filtering will have no effect. ... I would like to create an external trust with another domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: ACLs and permissions viewed after Migrating from NT 4 domain... The twilight zone?
    ... And if I decomission the old NT4 domain this should ... > (the little problem I have noticed is that if you give permissions to both ... >> to the new w2k user's sid history. ... >> it also checks the sid history when attempting to crack a sid to a user. ...
    (microsoft.public.win2000.security)
  • Re: ACLs and permissions viewed after Migrating from NT 4 domain... The twilight zone?
    ... the NT4 sid that was assigned to him was added ... it also checks the sid history when attempting to crack a sid to a user. ... > we're currently migrating our NT 4 domain to AD using ADMT from Microsoft. ...
    (microsoft.public.win2000.security)