🚀 On-prem Staging

This guide outlines the post-imaging standardization and preparation workflow for all end-user devices. The goal is to ensure each workstation is fully identified, visible in remote management, physically labeled, and neatly staged for final deployment. This process minimizes field errors and accelerates rollout.

---

🚚 Step 1: On-Prem Delivery & Staging

When workstations arrive on-site, they should be immediately moved to a secure, wired-accessible staging area.

🧩 Staging Procedure:

• Unbox all devices and perform a visual inspection
• Connect each workstation to power and the local LAN (wired preferred)
• Power on and verify they come online in NinjaRMM or other remote management platforms
• Ensure no setup is blocked by BitLocker, BIOS passwords, or local restrictions

🔒 The staging area should be limited to authorized IT staff to prevent configuration drift or misplacement.

---

🔧 Step 2: Workstation Identity & Visibility

📝 Most of these steps are verification tasks that should have already occurred during the initial post-image setup process. Review and confirm each step to ensure no configuration drift has occurred before final deployment.

Every imaged workstation must be uniquely named, properly labeled, and visible in your monitoring system before it’s considered deployment-ready.

🛰️ 2.1: Confirm NinjaRMM Status

• Verify each device is online and appears in the NinjaRMM dashboard as an individual asset
• Run a basic health check or script push to confirm endpoint communication

💻 2.2: Apply Naming Convention

• Use a consistent role-based hostname format:

  DEPARTMENT-ROLE-XX  (e.g., SALES-WKS-01, ADMIN-01, LAB-03)
  

• Avoid duplicate names and ensure alignment with AD/computer objects if applicable
• Record the assigned name in your asset tracking tool

🏷️ 2.3: Physical Labeling

• Print and apply device labels showing:
  • Assigned hostname
  • Intended user or role (if known)
  • Optional QR/barcode for scanning
• Place labels on a visible surface (e.g., top-left of chassis or monitor bezel)

💡 Use laminated labels or adhesive sleeves for durability and a clean aesthetic.

---

🔁 Step 3: Profile Migration Night Before Deployment

The evening before deployment, perform all user profile migrations.

🧳 Profile Backup and Restore:

• Backup profiles from existing workstations using ForensiT ProfWiz
• Join new workstations to the domain
• Assign new devices to the appropriate Organizational Unit (OU):
  • If AD Workstations or department-specific OUs exist, follow current structure
  • Only deviate from existing structure if the project scope of work explicitly specifies it
• Restore each profile using ProfWiz, mapping to the proper domain user account

🧠 Maintain a backup of each migrated profile for post-deployment support and rollback if needed.

---

🧪 Step 4: Client Application Testing

After profiles are restored and devices are domain-joined, verify the functionality of all required client applications.

🔍 Testing Procedure:

• Reference any existing internal documentation or application guides for test procedures
• If no guide exists, open the application and test using sample or known test data
• Validate that:
  • Application launches correctly
  • Expected modules or workflows are accessible
  • User interface reflects expected configuration or user context
• Record any errors or performance issues for remediation before deployment

✅ Testing ensures readiness of work-critical software and minimizes day-one interruptions.

---

✅ Deployment-Ready Checklist

• Devices delivered and staged on-site
• All systems online and visible in NinjaRMM
• Hostnames assigned per naming convention
• Physical labels applied correctly
• Joined to domain and placed in correct OU
• User profiles restored using ProfWiz
• Client applications tested and validated for each user/device ✔️

---

For project-wide rollouts, this procedure ensures each system is accounted for, documented, and ready for seamless delivery to its final user. Let the deployment begin!