Brian Desmond
w - 312.625.1438 | c - 312.731.3132
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Joseph L. Casale
Sent: Monday, April 3, 2017 1:42 PM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] Re: SID history report
Brilliant,
That article and
the report
without logical restrictions so it covers all cases.
Thanks a lot!
jlc
From: listsad...@lists.myitforum.com on behalf
of Brian Desmond
Sent: Monday, April 3, 2017 10:13 AM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] RE: SID history repor
. Casale
Sent: Sunday, April 2, 2017 2:47 PM
To: 'ntsysadm@lists.myitforum.com'
Subject: [NTSysADM] RE: SID history report
Hi Brian,
Forgive me, I don't exactly follow.
A user in DomainB could have one of the following scenario's:
1. A sIDHistory entry for DomainA\Gr
m: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Brian Desmond
Sent: Sunday, April 2, 2017 11:25 AM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] RE: SID history report
You really only need to grab this step:
- Enumerate any users in DomainB whose sIDHistory
You really only need to grab this step:
- Enumerate any users in DomainB whose sIDHistory collection contains one or
more of any of the above cumulative SIDs.
SIDHistory in DomainA has the SID of the group in DomainB. You need to find
anyone who is a member of the group in DomainB. That will g
And to add to that, any users in DomainB who have group membership (recursively
as well) in a group that has one of the sids in question.
I think that covers it?
jlc
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Joseph L. Casale
Sent: Thursday, March
6 matches
Mail list logo
