Home Logo logo
  • The OneDeploy Platform
    • Build vs. Image: The Deployment Revolution
    • Scalability and Performance
    • Remote Sites: Deployment without border
    • A Unified Deployment Platform
  • About OneDeploy
  • For MSP’s
  • News and Events
    • Unleashing the Latest Version at Microsoft Ignite 2025
    • Why we killed the image
    • How a London Stadium Recovered from the CrowdStrike Outage in Time for a Concert
  • Support and Resources
    • Videos
    • Documentation
  • Contact
Book a Demo
  • The OneDeploy Platform
    • Build vs. Image: The Deployment Revolution
    • Scalability and Performance
    • Remote Sites: Deployment without border
    • A Unified Deployment Platform
  • About OneDeploy
  • For MSP’s
  • News and Events
    • Unleashing the Latest Version at Microsoft Ignite 2025
    • Why we killed the image
    • How a London Stadium Recovered from the CrowdStrike Outage in Time for a Concert
  • Support and Resources
    • Videos
    • Documentation
  • Contact

Introduction

3
  • What is OneDeploy?
  • Concepts and Planning
  • Getting Started – Technical Onboarding

Using OneDeploy

43
  • Config
    • Windows Autopilot – Getting Started
    • Windows Autopilot Integration – OneDeploy Steps
    • Windows Autopilot Integration – Microsoft Entra
    • Organisations – Summary
    • My Tenant
  • Deployment
    • Builds
    • Devices
    • Deployments
    • Builds
      • Build General Settings
      • Builds Overview
      • Configuring the Operating System(s) for a Build
      • Applying Quality Checks to a Build
      • Configuring the Out of Box Experience
      • Domain and Accounts
      • Assigning Software Packages to a Build
  • Library
    • Library Overview
    • Drivers
      • DriverApps
      • Drivers Overview
      • Drivers Summary View
      • Adding Drivers
      • Driver Properties
    • Operating Systems
      • Adding and Managing Operating Systems
    • Software Packages
      • Software Packaging Best Practices
      • Defining Installation Steps for a Software Package
      • Software Package Steps – PowerShell
      • Software Packages Overview
      • Software Package Steps – Registry (Bulk)
      • Software Package Steps – Registry
      • Software Package Steps – Copy
      • Software Package Steps – MSI
      • Software Package Steps – WinGet
      • Software Package Steps – Execute
      • Software Package Steps – CMD
  • Pre-Deployment
    • Windows PE
    • ADK Versions
    • Boot Profiles
    • Deployment Sources
    • Pre-Deployment Overview
  • Definitions
    • Secrets
    • Software
    • Definitions Overview
    • Device Models
    • Vendors

Reference

5
  • Technical Overview – Windows Autopilot
  • Test formatting page
  • How To: Update a build from 24H2 to 25H2
  • How To: Upgrade Your Windows ADK Version
  • LAN-Based vs USB Deployment Sources
View Categories
  • Home
  • Docs
  • Using OneDeploy
  • Definitions
  • Device Models

Device Models

3 min read

Device Models allow you to define specific hardware models of PCs, laptops, servers, or specialist devices within OneDeploy.

This is an advanced feature that can help organisations manage deployments more tightly in controlled or locked-down environments.


Viewing Device Models

To view your configured Device Models:

  1. In the left navigation pane, expand Definitions
  2. Select Device Models

The current list of Device Models is displayed.


Managing Device Models

From the Device Models list, you can:

Add a New Device Model

  1. Click New
  2. Enter the required device model details
  3. Save your changes

Remove Device Models

  1. Tick the checkbox next to one or more Device Models in the list
  2. Click Delete

Example Device Models

Some common examples might include:

  • Lenovo ThinkPad T14 Gen 4
  • HP ProDesk 600 G6 SFF
  • Oracle MICROS Workstation 655X (no customer display)
  • Oracle MICROS Workstation 655X (with customer display)
  • Dell PowerEdge R750
  • HPE ProLiant DL360 Gen11

Do You Need Device Models?

No — you do not need to set up Device Models to create builds or deploy devices.

OneDeploy is designed around a “One Build, Many Devices” approach by default.

Device Models are intended for more advanced scenarios.


Why Use Device Models?

Defining Device Models can be useful when you want tighter control over what hardware can receive specific builds.

By setting up Device Models, you can:

  • Lock down a build so it can only be installed on approved hardware models
  • Automatically detect a computer’s role during deployment based on its model type
  • Support automated build selection by auto selecting a role based on hardware type when using Matrix Mode

Example Use Cases

You may have a Point of Sale (POS) build that should only be installed on certified POS hardware.

You wouldn’t want that build deployed onto a standard office desktop or laptop.

With Device Models, you can ensure only the correct hardware can receive that build.

Advanced Automation Example (Same Site, Different Roles)

Device Models can also enable smarter automation when combined with Matrix Mode.

For example:

  • At the same physical location, you may deploy different types of machines:

    • A Dell PowerEdge R750 intended to be an on-site server
    • A HP ProDesk 600 G6 SFF intended to be a manager workstation

By using the hardware model as the identifier, OneDeploy can automatically select the correct build:

  • If the device model is Dell PowerEdge R750, deploy the build “On-site Server”
  • If the device model is HP ProDesk 600 G6 SFF, deploy the build “Windows 11 Manager Workstation”

This reduces manual selection and helps ensure the right systems are deployed in the right role every time.


Preventing Unapproved Hardware

Device Models can also help prevent rogue or unauthorised devices from being deployed.

If your Organisation defines a mandated list of approved models, any device that does not match one of the configured Device Models can be blocked from being built using OneDeploy.


Common Questions

Do I need Device Models for standard deployments?

No. Most organisations can deploy successfully without configuring Device Models.

What is the main benefit of Device Models?

They provide tighter control over which builds can be installed on which hardware, especially in secure or regulated environments.

Can Device Models be used for automation?

Yes — Device Models can be used as identifiers for automated build selection when using Matrix Mode.


Related Articles

  • Builds
  • Automated Builds (Matrix Mode)
  • Vendors
Updated on February 12, 2026

What are your Feelings

Definitions OverviewVendors
  • hello@onedeploy.com
  • UK:+44 1462 514624/ US:+1 415 907 7314

Copyright 2026 OneDeploy Ltd Privacy Policy Cookie Policy