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
    • Autopilot is not Deployment
    • OneDeploy Sponsoring Workplace Ninjas, Belgium June 26
    • The Latest OneDeploy Release Simplifies Windows Deployment Across ARM and Intel Devices
    • OneDeploy – The Ideal Successor to MDT
    • Why we killed the image
    • How a London Stadium Recovered from the CrowdStrike Outage in Time for a Concert
    • OneDeploy Sponsoring Modern Endpoint Management Summit, Paris
  • 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
    • Autopilot is not Deployment
    • OneDeploy Sponsoring Workplace Ninjas, Belgium June 26
    • The Latest OneDeploy Release Simplifies Windows Deployment Across ARM and Intel Devices
    • OneDeploy – The Ideal Successor to MDT
    • Why we killed the image
    • How a London Stadium Recovered from the CrowdStrike Outage in Time for a Concert
    • OneDeploy Sponsoring Modern Endpoint Management Summit, Paris
  • 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

7
  • How To: Create USB Boot and Deployment Media
  • How To: Create USB Boot Media
  • 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
  • Vendors

Vendors

1 min read

Vendors in OneDeploy let you maintain a standard list of software and hardware suppliers that can be reused throughout the platform.

You can apply Vendors to:

  • Software Packages
  • Device Models

When creating a Software Package for deployment, or defining a particular model of computer, a Vendor must be selected. Setting up Vendors first helps keep your Library organised and consistent.


Viewing Vendors

To view your current Vendor list:

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

The existing Vendors are displayed in a list.  


Adding a New Vendor

To add a Vendor:

  1. Go to Definitions > Vendors
  2. Click the + icon in the column heading
  3. Enter the Vendor name
  4. Click the Save icon to confirm

The Vendor will now be available for selection when creating Software Packages or Device Models.


Hint: Adding Vendors While Creating Software

You can also create a Vendor while adding a new Software item.

  1. When creating Software, locate the Vendor field
  2. Click the + icon on the Vendor line
  3. Enter the Vendor details and save

Any Vendor added here is automatically included in your main Vendor list under Definitions > Vendors.


Common Questions

Do I need to create Vendors before adding Software Packages?

Yes — a Vendor must be selected when creating Software Packages, so it’s recommended to create items in your Vendor list first.

Can Vendors be reused across different items?

Yes — the same Vendor can be applied to multiple Software Packages and Device Models.


Related Articles

  • Device Models
  • Software
  • Software Packages
Updated on February 12, 2026

What are your Feelings

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

Copyright 2026 OneDeploy Ltd Privacy Policy Cookie Policy