Skip to main content

Capture With MSP360

In our workstation lifecycle strategy, the Capture phase ensures every device has a valid, restorable image leading up to its scheduled replacement. We automate this through MSP360 and a custom script deployed via NinjaRMM, enabling us to capture the current state of a workstation and continuously back it up until lifecycle day.

🔧 Script Overview: “Workstation Lifecycle: Step 1 Capture”

Deployed from our RMM at:

👉 https://dtcinc.rmmservice.com

Script name:

📜 Workstation Lifecycle: Step 1 Capture

When executed, the script:

  1. Installs MSP360 if it isn’t already installed.
  2. Signs into the staging backup account:
    staging@dtctoday.com
  3. Creates one backup job, based on the selected mode:
    • Staging Job (☁️ Cloud): Used for Ridgebrook bench recovery.
    • Staging Job Local (📂 Local SMB): Used for on-site restore.
💡 Note: The script creates only one backup job per run, either cloud or local.
However, both can coexist — you can run the script again to add the second job if needed. Each job remains persistent and runs nightly once configured.

▶️ How to Run the Script from NinjaRMM

Follow these steps to deploy the backup job on a workstation:

1. Open NinjaRMM and Locate the Device

Search for or navigate to the device under the Client → Site structure.

📸 [Insert Screenshot – Device selection screen]

2. Run the Script

Click on “Run Script” from the device action panel.

📸 [Insert Screenshot – Script execution button]

3. Select: “Workstation Lifecycle: Step 1 Capture”

Choose the script from your library. You can filter by category or search.

image.png

image.png

image.png

4. Fill Out Script Parameters

You’ll be prompted to enter:

  • Client Name 🏢
  • Site Name 📍
  • Backup Type (Cloud or Local)
  • If Local:
    • LocalStoragePath (e.g., \\192.168.1.100\Backups)
    • NetworkShareUsername (e.g. DOMAIN\user)
    • NetworkSharePassword (e.g. sdjfkalfjoeifie)
    • The rest of the fields are already filld out and not required.

These inputs are used to generate unique, readable MSP360 repository and job names under the staging account.

image.png

5. Launch and Confirm

Once inputs are set, click Run. The script:

  • Installs/configures MSP360
  • Registers the agent under staging@dtctoday.com
  • Creates the appropriate backup job
  • Schedules it to run nightly
  • Triggers the first backup immediately

image.png

image.png


🔁 Continuous Nightly Backups

The selected job (cloud or local) will now back up the device every night until the device is decommissioned.

To create both backup paths (for redundancy or flexibility), simply run the script again with the other backup type selected. Both jobs will coexist and continue running nightly.

🔍 Daily Monitoring

We recommend checking backup job status daily using MSP360’s management console. A failed backup should be addressed and re-run prior to restore day to ensure image freshness.

⏭️ What’s Next: The Restore Phase

With reliable images in place, we transition to the Restore chapter — where we walk through recovery methods using either the cloud-based image at Ridgebrook or the on-site local SMB copy.

Back to top