This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SID History and Source Resources

I am testing migrations with a few test accounts and I log on to a source workstation with a source account and I can access home drive and shares. I then migrated the same account, logged onto a source workstation with the target account and can no longer access home drive or shares, get access denied message.

I am in a full forest trust, I can see the SID history on the target object. By Dell's doc I do not have to run the netdom command to disable sid filtering in a forest trust. But obviously the SID is not being accepted by the source from the target account. Any ideas?

0 Jeff Shahan over 7 years ago

I don't know what Dell documentation you are reading, but it clearly states that you have to disable sid filtering on page 13 of the Preparing Migration 8.12 Installation Guide.

Here is a link to that section of the documentation documents.software.dell.com/.../disabling-sid-filtering
Cancel
Up 0 Down

Cancel
0 rreda over 7 years ago

I am reading the documentation in the 8.12 install guide under prerequisites and it states here:

Disabling SID Filtering

By default, SID filtering is turned on.

Note: You do not need to disable SID filtering if you have established a forest trust between source and target forest.

I do have a full 2 way forest trust.
Cancel
Up 0 Down

Cancel
0 Jeff Shahan over 7 years ago

You still need to disable filtering. External trusts is done one way, Forest trusts it is done another way. Netdom is used reguardless of the trust is external or forest. The only difference is the switches that you use.

technet.microsoft.com/.../cc794801(v=ws.10).aspx

Netdom trust <TrustingDomainName> /domain:<TrustedDomainName> /enablesidhistory:Yes /userD:<DomainAdministratorAcct> /passwordD:<DomainAdminPwd>
Cancel
Up 0 Down

Cancel
0 rreda over 7 years ago

Thanks for the response I will give it a try. This has to be the problem.
Cancel
Up 0 Down

Cancel
0 Jeff Shahan over 7 years ago

This is the problem. What your are doing it how I test this at the start of every migration.
Cancel
Up 0 Down

Cancel
0 Jeff Shahan over 7 years ago

Did this solve your issue?
Cancel
Up 0 Down

Cancel
0 rreda over 7 years ago

Yes the issue was the enablesidhistory:yes syntax. This could be explained a little better in the manual but it now works as expected. It is explained in the KB article.

support.software.dell.com/.../14247
Cancel
Up 0 Down

Cancel