Drive a new or re-imaged workstation from bare hardware to user-ready against a consistent build standard, with a single verification trail. This skill produces a checklist, verification, and handoff — it does not push software, run scripts, or deploy policy through the RMM.
1. Establish the target: client, assigned user (if any), device model, and whether this is a fresh build or re-image. Pull the client's build standard from the documentation (IT Glue) and any build guide from the knowledge base; if none exists, say so and use the generic checklist below rather than inventing client-specific steps.
2. Confirm the deployment method before starting. For modern Windows fleets the path is usually Autopilot + Intune — hand that portion to the m365-administration autopilot/intune skills rather than duplicating it. Note in the ticket which method applies (Autopilot/Intune, manual image, or MDM for Mac).
3. Walk the build checklist and record each item as done / N/A / blocked:
- Naming: hostname per the client's convention; asset tag recorded.
- OS baseline: current OS build, firmware/BIOS updated, disk encryption enabled (BitLocker/FileVault) with the recovery key escrowed to the correct store.
- Management: RMM agent installed and checking in; enrollment (Autopilot/Intune or MDM) completed; endpoint security/EDR agent installed.
- Identity: joined to the correct directory (Entra/AD) and the right groups; user profile signed in and synced.
- Apps: baseline app set plus any role-specific apps from the client standard.
- Data: user data/profile migration if this is a replacement; verify before wiping any source device.
- Peripherals/printers/drive mappings per the user's role and site.
4. Verify the device is actually managed: look it up in the RMM by hostname and confirm from its details that it is checking in, encrypted, and shows the expected agents (don't trust a class filter — confirm in the details). Reconcile the RMM record against documentation so the asset is tracked, not orphaned.
5. Update the asset record in documentation (owner, serial, warranty, deploy date).
6. Output a completion summary: checklist with each item's state, any blocked items with the reason, a deep link into the device in the RMM for the tech, and remaining handoff steps. Offer to leave it as a plain-text note (no markdown/emojis), or open a ticket if this build has none yet.
Guardrails: never wipe or re-image a source device until data migration is confirmed complete and verified. Do not fabricate a client build standard; if documentation has none, state that and use the generic baseline. Confirm the assigned user and site before joining directory groups or mapping resources — wrong-group placement is an access issue. If the RMM or documentation is absent, degrade to the checklist only and say the verification step could not be completed.
Magic Library