Active Directory help desk tasks are repeated identity and access requests: unlock an account, reset an expired password, correct a user attribute, update approved group membership, create a new starter, and disable a leaver. Each task is simple only after the technician verifies the requester, reads the approved values, and knows where Tier 1 authority stops.
The six directory tickets you will see most
- Account lockout. The account is locked after repeated bad passwords. Unlock it, and find out what locked it before you close.
- Expired or forgotten password. Reset it, and decide whether it has to change again at next sign in.
- Attribute correction. A title, department, office or telephone extension that no longer matches reality.
- Group membership. Access follows groups, so joining a team or leaving one is a membership change, not a permissions change on a folder.
- New starter. Create the account in the right organizational unit, with the right naming convention and the right starting groups.
- Leaver. Disable the account, remove the access, and leave the object in place so the audit trail survives.
How to work a directory ticket end to end
- Confirm who you are talking to before you touch the account. An unlock request is the oldest trick there is, and identity verification is the one step nobody can do for you afterwards.
- Find the account, not a similar one. Two people called J Murphy is normal in any company of size, so match on the logon name in the request rather than on the display name.
- Read the request for the exact approved values. On an attribute ticket the values are the whole job, and they are usually four strings buried in a paragraph of prose.
- Make the change on the tab it belongs to, and make only that change.
- Verify from the console rather than from memory. Reopen the account and read back what you set.
- Tell the requester what changed and what they need to do next, such as signing out and back in before a new group takes effect.
The habit worth building early is reading the whole request before opening the console. Directory work is fast and it is permanent, and the most common way it goes wrong is not difficulty. It is doing three of the four approved changes because the fourth was in a sentence you skimmed.
The second habit is knowing where your authority stops. Protected groups exist so that a Tier 1 account cannot quietly grant privileged access, and a console that refuses you is usually right. Escalate with the request, the account name and what you were asked to change, and let the team who owns that group make the call.