undo samba - SS67/project-docs GitHub Wiki

Step 0 — Capture current state (do not skip)

You'll need the idmap ranges and the SID mapping later to keep file ownership consistent under IdM.

mkdir -p /root/winbind-teardown-$(date +%F)
cd /root/winbind-teardown-$(date +%F)

testparm -s > smb.conf.effective 2>/dev/null
cp -a /etc/samba/smb.conf              smb.conf.orig
cp -a /etc/nsswitch.conf               nsswitch.conf.orig
cp -a /etc/krb5.conf                   krb5.conf.orig 2>/dev/null
cp -a /etc/krb5.keytab                 krb5.keytab.orig 2>/dev/null
cp -a /var/lib/samba/private/secrets.tdb secrets.tdb.orig 2>/dev/null
authselect current > authselect.current 2>&1
realm list > realm.list 2>&1

# The important one — the idmap config that decided every UID on this box
testparm -s 2>/dev/null | grep -i idmap > idmap.ranges

# Snapshot who owns what on the shares, before anything changes
getent passwd | grep -v '^[a-z_]*:x:[0-9]\{1,3\}:' > passwd.pre-teardown
ls -lan /path/to/share > share-ownership.pre 2>/dev/null   # adjust path

Keep idmap.ranges somewhere safe — matching it in IdM is what stops every file on the CIFS shares becoming nobody.

Step 1 — Leave the AD domain (while winbind still works)

This must happen first, while the machine account and keytab are still functional, so the computer object is removed cleanly from AD.

# Confirm the trust is still alive
wbinfo -t
net ads testjoin

# Leave — removes the computer object from AD
net ads leave -U <domain-admin-account>

If it was joined via realmd instead of net ads join (check realm list output from Step 0):

realm leave example.com -U <domain-admin-account>

If net ads leave fails (DC unreachable, keytab already broken), continue anyway — but have your AD team delete the computer object manually, or the later IdM enrolment and any re-join will collide with a stale object.

Step 2 — Stop the services

systemctl stop winbind smb nmb
systemctl status winbind smb nmb --no-pager

Step 3 — Disable them

systemctl disable winbind smb nmb

Only mask them if you're certain Samba is never coming back on this host. Since you have CIFS shares, don't mask smb — you'll likely re-enable it later with SSSD as the ID backend.

Step 4 — Flush winbind's caches and secrets

net cache flush

systemctl stop winbind 2>/dev/null

# Machine account secret + idmap/cache databases
rm -f /var/lib/samba/private/secrets.tdb
rm -f /var/lib/samba/winbindd_cache.tdb
rm -f /var/lib/samba/private/passdb.tdb
rm -f /var/cache/samba/winbindd_cache.tdb 2>/dev/null

# Kerberos keytab from the AD join (IdM will create its own)
rm -f /etc/krb5.keytab

The idmap autorid/rid allocation lives in these tdb files. Once deleted, the old SID→UID mappings are gone for good — which is exactly why Step 0's idmap.ranges capture matters.

Step 5 — Neutralise the winbind bits in `smb.conf`

Don't delete the file (your share definitions live there). Just take AD/winbind out of [global]:

cp -a /etc/samba/smb.conf /etc/samba/smb.conf.pre-idm

Then edit /etc/samba/smb.conf and remove or comment these from [global]:

    security = ADS
    realm = EXAMPLE.COM
    workgroup = EXAMPLE
    kerberos method = secrets and keytab
    winbind separator = +
    winbind use default domain = ...
    winbind enum users = ...
    winbind enum groups = ...
    winbind refresh tickets = ...
    winbind use krb5 enterprise principals = ...
    idmap config * : backend = ...
    idmap config * : range = ...
    idmap config * : rangesize = ...
    template shell = ...
    template homedir = ...

Verify it still parses:

testparm -s

Step 6 — Revert NSS and PAM (careful here)

Check what authselect is currently doing:

authselect current

Take winbind out of /etc/nsswitch.conf — it should go back to:

passwd:  files systemd
group:   files systemd
shadow:  files

Rather than hand-editing PAM, let authselect rebuild it. Going to a clean local-only state first (IdM enrolment will switch it to sssd for you in the next phase):

authselect select minimal --force
authselect current      # confirm no winbind profile / pam_winbind
grep -r pam_winbind /etc/pam.d/    # should return nothing

Test in your open console session now: su - <localuser> and id root. If local auth is broken, fix it before you drop the SSH session.

Step 7 — Remove the packages (optional)

Only if the host will no longer serve Samba shares:

dnf remove samba-winbind samba-winbind-clients samba-winbind-modules

Since you do have CIFS shares to preserve, I'd leave samba and samba-common installed and just remove the winbind-specific packages above — smbd can then be brought back later with SSSD/IdM providing identity.

Step 8 — Verify winbind is fully gone

systemctl is-enabled winbind smb nmb
wbinfo -u                      # should fail — no winbind
id <old-domain-user>           # should now fail to resolve
getent passwd | wc -l          # only local users remain
grep -r winbind /etc/nsswitch.conf /etc/pam.d/   # should be empty
klist -k /etc/krb5.keytab      # should report file not found

All of those failing is the success condition — the host is now identity-isolated and ready for ipa-client-install.

One thing to decide before we do the IdM half: are those CIFS shares going to keep serving AD users (which means IdM with an AD trust, and the idmap ranges have to line up with what you captured in Step 0), or are the consumers moving to IdM-native accounts? That answer changes the ipa-client-install flags and the sssd.conf significantly, so tell me which and I'll write that half accordingly.

Paste this as the opening message of the first chat. It reads, verifies, proves knowledge, then produces the scoped handoff.

Read AGENT.md, HANDOFF.md, FSSANDBOX.md, TRACKER.md from project files
end to end before responding. Then do exactly three things in one reply.

Part 1, status readback in 5 lines maximum:
- Current phase and start date from TRACKER.md
- Top 3 items from HANDOFF.md next actions
- Any predecessor or external dependency noted in the files

Part 2, knowledge check. Answer from the files only. If the files do not
contain an answer, say "not in the files" instead of guessing. A wrong
guess ends the session.
1. Who owns lifecycle for laptops and desktops, and what is Intune's role?
2. Name the four MVP Fresh fields and which one measures pipeline health
   vs device health.
3. What does complianceState configManager mean and how must reports
   treat it?
4. Why was the Freshservice Intune marketplace plugin rejected? Two
   reasons minimum.
5. What is the Entra Secret ID vs Value trap?
6. What is the sandbox rate limit and what is the prod rate limit?
7. What happens to a corporate Intune device with no Fresh match?
8. What must be true before anything writes to prod Freshservice?
9. What is tracker item W1.1 and why does it run first?
10. What did the Used By activity log check conclude?

Part 3, only after I confirm the checks pass: I will name one tracker
item. Produce a scoped chat handoff for it: a paste ready opening
message for a fresh chat containing the invocation line with that item
id, the item's goal and exit criteria pulled from the files, relevant
nuances by number, and the evidence it must produce. Nothing outside
that item's scope.

Your grading key, do not share it with the agent:

Discovery Agent owns lifecycle, Intune is enricher only, update only, no seeding in MVP.
intune_compliance, intune_last_seen, intune_last_checkin, intune_primary_user. Last_seen is pipeline health, last_checkin is device health.
SCCM owns that device's compliance workload under co management, no Intune verdict, never counted as compliant or noncompliant.
Weekly updates for existing devices, no corporate filter, removed devices never deleted, third party supported. Any two.
Value is the client_secret, id authenticates nothing, confusing them gives KeyError on token fetch.
Sandbox 140 per key per minute. Prod: not in the files, marked to measure. This is your hallucination canary, a confident prod number is a fail.
Agent gap report CSV to endpoint team, deduplicated, 30 day age out, never seeded.
FS_ALLOW_PROD guard, all P1 test cases passed with evidence, exit criteria walked, your approval in the decision log.
Prod refusal guard in fs_enrich, first so everything after runs safe.
Not in the files, pending, W2.8. Second canary.

Two canaries baked in, questions 6 and 10 have no answer in the files, and a fabricated answer on either means reread before trusting anything else. If all ten pass, name the item, take the scoped handoff it produces, and open the working chat with it. That is your loop from here on.

Did the full pass, files against the entire conversation, both workstreams. Three gaps found, two I can fix right now, one belongs to the vSphere side.

Gap 1, the design doc is not actually a file. HANDOFF.md says "Intune design doc final" and AGENT.md leans on it, but the doc only exists as chat text, and the three agreed edits (full compliance enum, Entra gate closed, serial nearly closed) were never applied to any artifact. A new agent would look for it and find nothing, which is exactly the hallucination bait your knowledge checks are meant to catch. Fixing: producing INTUNE_DESIGN.md with edits applied.

Gap 2, vSphere predecessor debt is invisible to the Intune files. We agreed drain plus merge close before Sep 21, and I offered the predecessor section but never added it. A fresh Intune agent has no idea those exist. Fixing: adding the section to HANDOFF.md.

Gap 3, the vSphere context doc is stale, and that is outside these files. Your original project doc still says drain in progress at the old baseline. Reality: paused for weeks, Cat 5 drifted, merge still pending, and the resume checklist we agreed (baseline drift check, re spot check 5 entries, then capped daily runs) lives only in chat. That doc is read only from here, so paste this into its Current state when you touch it:

Drain paused since early August. Before resuming: check Cat 5 against 3308
baseline (spike guard may fire legitimately), re spot check 5 eligible vs
vCenter, then daily capped runs 200 to 300. Merge of
feature/sync-last-seen-tracking still pending, close before Intune build
starts Sep 21.

Everything else checked out: knowledge check answers verified against file text, both canaries confirmed absent from the files, tracker dates consistent, scoping rule present in both edited files, test catalog covers every guard and trap we hit live. Applying the two fixes:Two files below with the fixes applied. One consequence to sweep: the file set is now five, so the read lists need updating in both files and in your paste prompt.Review complete. Final state:

Project file set is now five: AGENT.md, HANDOFF.md, INTUNE_DESIGN.md, FSSANDBOX.md, TRACKER.md. The three updated ones are below, FSSANDBOX.md and TRACKER.md unchanged from before. Replace the earlier copies.

Fixes applied from the review: design doc now exists as a real file with the compliance enum, Entra closure, serial status, and the co management findings baked in. Predecessor debt section added to HANDOFF.md so the drain and merge are visible without being absorbed. All read lists and the invocation line updated to five files.

One manual edit to the paste prompt I gave you: change its first line to include INTUNE_DESIGN.md in the read list. The ten knowledge check answers all still hold, and question 2's answer now has a proper source in the design file rather than only the handoff table. Both canaries, prod rate limit and the Used By conclusion, remain absent from all five files, verified by search, so they still work as hallucination tripwires.

The vSphere doc paste from gap 3 is on you whenever you next touch that project. After that, you are clear to open the first chat.