đ§ End-to-End Workstation Deployment Process
Introduction
Workstation Lifecycle: The ImageâŻPlaybook is DTCâs noânonsense recipe for shepherding a workstation from âin productionâ to âon the shelfâ without dataâloss drama. The whole flow is anchored by MSP360 Backup, steered through a single NinjaRMM script, and rounded out with a bootable recovery environment you can fire up from USBâor, soon, straight off the network.
Our approach has four actionable pillars:
Pillar | What Happens | Why It Matters |
---|---|---|
Capture | A pointâinâtime image is created before lifecycle day. | Gives us a clean restore target even if the device blows up tomorrow. |
Protect | That image backs up nightlyâcloud, local, or bothâuntil the project wraps. | We always have a âlatestâ snapshot. No retention fuss; keep all versions until the new box is live. |
Restore | We boot a recovery ISO/USB (and, in the future, a netboot.xyz entry) and push the image back. | Bench at Ridgebrook or onâsiteâsame end result. |
Generalize (Optional) | Sysprep cleanup for goldâimage scenarios. | Modern EFI + Intune/Ninja handle cloned disks fine, so skip it if youâre just swapping hardware. |
Note on Restore Docs: Clickâbyâclick guides for OnâSite Restoration Imaging and Ridgebrook Bench Imaging are still being written. Conceptually, itâs simple: pick the right repository, hit Restore, done.
The Workhorse Script: âWorkstationâŻLifecycleâŻââŻStepâŻ1âŻCaptureâ
Deployed via NinjaRMM, the script:
-
Installs MSP360 if missing.
-
Signs the agent into our staging account (
[email protected]
). -
Creates one backup job per run:
-
StagingâŻJobâŻâď¸ (cloud to Ridgebrook)
-
StagingâŻJobâŻLocalâŻđ (SMB share onâsite)
Reârun to add the second pathâboth jobs live happily together and run every night.
-
Once the first backup completes successfully, we consider that workstation protected. Every subsequent nightly backup is gravy; we keep every version until the replacement project is finished.
Recovery Environment
Our custom DTCBeSure ISO/USB includes:
-
MSP360 restore console
-
Dell Family Driver Pack (current at time of ISO creation)
-
Optional Sysprep automation script
We show you exactly how to inject fresh drivers, but thereâs no scheduled âannual refreshâ yetâjust rebuild the ISO whenever you need newer drivers.
Whatâs on the Roadmap
-
netboot.xyz Entry â A menu option to PXEâboot the same recovery image when USB sticks arenât handy. (Planned, not live.)
-
Detailed Restore Chapters â Stepâbyâstep for both onâsite and Ridgebrook workflows.
-
Automation Tweaks â If EFI/management behavior changes, weâll revisit whether the Generalize step stays optional.
Current ToâDo List đ ď¸
Status | Task |
---|---|
âł | Build latest MSP360 recovery ISO and test it (USB boot). |
âł | Draft OnâSite Restoration Imaging guide. |
âł | Draft Ridgebrook Bench Imaging guide. |
đď¸ | Prototype netboot.xyz integration (upload ISO, add menu entry, labâtest PXE). |
đ | Rebuild ISO when a new Dell Family Driver Pack is released or hardware requires it. |
Where Weâre Headed
By the end of this playbook youâll have a rinseâandârepeat workflow that:
-
Captures every workstation before retirement.
-
Backs up the image nightly with zero fuss.
-
Restores it on your bench or in the fieldâUSB today, network boot tomorrow.
Letâs dive into ChapterâŻ1: Capture and get those first images rolling. đ