← sources

When Tribal Knowledge Becomes IT Policy

source: reddit (reddit:sysadmin)published 2026-11-11 02:55ingested 2026-11-12 02:41

retained text

Our IAM team uses SailPoint ISC to manage AD accounts. ISC automatically enables new employees' accounts 7 days before their official start date.

However, a "lifer" on our desktop support team insists that IAM configure specific AD logon hours so he can log in interactively using the employee's credentials and create their local Windows profile before shipping the laptop.

He'll request something like Tuesday–Friday. I followed those instructions once, only to discover the employees actually started Monday. Naturally, they couldn't log in.

There's no documented policy requiring these restrictions. He believes they're necessary for profile creation.

I've floated the idea of just enabling it for his profile creation (Which I do regardless) then disabling it when he's done.  But it always goes back to login hours.

Why not use SCCM/MECM to deploy the golden image, install applications, join the domain, and configure the workstation? ISC already handles identity provisioning and account enablement.  (They used to have a process for that not anymore)

My boss actually agrees with me that this process is archaic and dumb, but some people are set in their ways and resistant to changing established procedures.

Am I overlooking a legitimate technical reason for this, or is this just an outdated process nobody has bothered to modernize? Lol.  

To make matters worse a co-worker backs the Desktop support guy in this, which makes things worse. Im at the point where I might aswell just go along with it.

Anyone experience this or something similar?

document fetched 2026-11-12 00:39 · canonical https://reddit.com/r/sysadmin/comments/1xt6lnm/when_tribal_knowledge_becomes_it_policy