How can we verify access during an AD migration after a merger?

November 17, 2026 5 answers
Asked by _w68!coppervisor.3

After a merger, we're moving users to another organization's Active Directory for ERP single sign-on. Some file servers will stay in the original domain, and a migration team plans to rely on SID history and a trust rather than changing their permissions.

How can we check whether access will actually work, and what should we ask the consultants to document?

Answers

_n53!orbitgrommet.7

Run a pilot against the actual servers before deciding either way. A matching account name alone does not grant access, but SID history can allow a migrated account to match permissions assigned to an old SID. That does not mean every access path will work automatically.

Have the team show which SIDs are in the user's access token, including the relevant group SIDs, and check whether SID filtering or other trust settings affect them. Test both share and NTFS permissions with migrated users, including nested group access and any explicit denies. Record the expected and actual results for representative folders, not just an administrator account.

8n~radarcradle_362:

Include a fresh sign-in when checking tokens. A session established before group or SID history changes may not reflect the current setup.

Reply to this answer
_j67~quibletap.5

Ask for a written permission strategy for the servers that are staying behind. Is SID history a temporary bridge, or is it expected to remain indefinitely? Who owns converting the old domain groups on the share and NTFS ACLs, and what happens when the trust is eventually removed?

Also get a rollback plan and a list of dependencies before changing ACLs. Replacing entries without understanding how the groups are used can break access just as effectively as leaving them alone.

Reply to this answer
4f!clovernotch_857

The privileged access deserves its own review. Get the consultants to explain why each service account and human account needs its assigned rights, how long it needs them, and who approved them. Log the activity, agree on an end date, and remove the access when the work is done.

Domain administrator access may be needed for particular migration steps, but it should not just become an open-ended project default.

Reply to this answer
Tavelo.4q

Make the consultants own a test plan and an issue register. Log failures with the affected account, resource, time, and expected access, then assign them to the migration team for investigation. Keep the project manager informed and be clear about what help internal IT can provide.

That gives support a route for real user problems without turning every issue into an argument over whose migration tool should have been used.

Reply to this answer
_c47~ledgercrayon.9

The custom scripts might still be useful as a reference or fallback, but don't assume a tested script is automatically ready for the whole migration. Agree on scope, review and approval before spending more time on it. The selected tool still needs pilot results and a reconciliation of accounts and permissions after each batch.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions