Features of the MasteriDesk workstation imaging software
Six key functions to prepare your devices hands-free: from PXE detection to BitLocker encryption, the features of the MasteriDesk workstation imaging software cover the entire deployment of your Windows systems, whether as a ‘Clean’ installation or by image cloning. Accessible directly from the SecuriDesk panel, the solution identifies the model of each device and automatically injects the right drivers.
Functional scopeWorkstation imaging software for your on-network and offline deployments
MasteriDesk orchestrates the automated deployment of your Windows images over the local network (PXE) or via standalone USB media. Drivers for Dell, HP and Lenovo business ranges are retrieved automatically from the manufacturers’ catalogues. The deployment engine itself remains independent of the device brand.
PXE network boot
The local probe acts as a PXE server or DHCP proxy, in both UEFI and Legacy BIOS mode.
‘Clean’ installation or image cloning
Deployment of a .WIM or .ISO system image onto a GPT-partitioned disk.
Standalone USB media
A USB stick protected by a time-limited password, prepared for a specific target model.
Dell, HP and Lenovo drivers
Driver packages for business ranges, retrieved from the manufacturers’ enterprise catalogues.
BIOS, TPM 2.0 and battery
Manufacturer hardware optimisations: BIOS update, TPM 2.0 activation and battery profile.
Other hardware
Self-built PCs or consumer ranges: you add the driver package to your library yourself.
Would you like to check that your device models are supported? Let’s talk about it on a video call. Book a video call
The 6 key features of the workstation imaging software
Each feature covers one step in preparing your devices. First, PXE detection identifies each machine. Next, the deployment wizard and automatic driver management prepare an installation tailored to the model. Finally, hardware optimisation, 9-step monitoring and the local cache secure and speed up every deployment.
Detect devices automatically
MasteriDesk processes batches of devices simultaneously on the same network segment, with no physical intervention on each device.
Plug in your devices: they boot from the network and automatically join the staging area, the ‘Sas’.
- PXE interception: the local probe provides the device with a network boot file, compatible with UEFI or Legacy BIOS, which loads a lightweight Windows environment (WinPE).
- Hardware identification: under WinPE, WMI queries extract the manufacturer and exact model of the device before any action is taken.
- Reporting in the interface: the MAC address, model and status of each device are displayed in the interface.
Configure the installation in three steps
Native support for ADBA or KMS activation removes the need to manage product keys manually, device by device.
Select your devices, then let the wizard guide you.
- Image and licences: choice of system image and licence activation method (ADBA, local KMS or MAK key).
- Drivers and hardware: validation of driver injection and manufacturer optimisations (BIOS update, TPM 2.0 activation, battery profile).
- Domain and security: local account configuration, domain join and activation of BitLocker encryption.
In the Settings screen, you define your global standards: licence activation, BIOS passwords and BitLocker encryption algorithm.
Stop hunting for drivers
You no longer have to hunt down, download, extract and sort the drivers for your business ranges, or manage subscriptions to the manufacturers’ XML feeds.
MasteriDesk detects the model, then automatically injects the right driver package.
- Central repository: a qualified global catalogue of ready-to-use driver packages, regularly synchronised with the Dell, HP and Lenovo enterprise catalogues.
- On-demand enrichment: when a model appears whose package has never been retrieved before, the repository downloads it from the manufacturer’s catalogue, qualifies it, then makes it available.
- Targeted injection: drivers are applied offline to the Windows image using the DISM tool.
- Centralised library: a single screen brings together your OS images and your driver packages.
For example, when a manufacturer launches a new range, its models are added during the nightly synchronisation. The first device from that range plugged in the next day then receives its drivers without any human action.
Three more features of the workstation imaging software
Hardware optimisation and BitLocker, 9-step monitoring, local cache and USB media — the rest of your deployment journey.
Secure every device from installation onwards
BitLocker encryption is built into the deployment and is conditional on the decryption key being automatically backed up to Active Directory.
Beyond simply copying files, MasteriDesk also prepares the hardware.
- BIOS update via the manufacturers’ utilities, with integration of BIOS/UEFI compliance rules.
- TPM 2.0 activation, essential for Windows 11.
- Battery profile: charging can be limited to 80% for devices on docking stations.
- BitLocker encryption enabled automatically during post-installation, once prerequisites such as an active TPM 2.0 chip have been validated.
On first restart, the probe runs the finalisation sequence: manufacturer utilities (for example Dell Command or HP BCU), Active Directory join, then BitLocker initialisation.
Track every deployment in 9 steps
MasteriDesk aims to cut the average time needed to prepare a device from 2 hours to under 20 minutes, without constant supervision.
Launch the deployment: it runs autonomously, and you follow its progress device by device.
The interface displays detailed progress in 9 steps for each device:
- PXE
- BIOS & TPM
- Formatting
- Windows copy
- Drivers
- Finalisation
- Domain
- Activation
- BitLocker
- Detailed or grid view to track the progress of an entire batch of devices.
- Precise diagnostics: you identify exactly which step a deployment failed at, for example an activation failure or a BitLocker failure.
- Targeted retry of failed installations only.
Deploy anywhere without saturating your network
For 10 Lenovo ThinkPad T14 laptops deployed at a remote site, only the first device triggers the download of the 500 MB driver package. The other 9 use the local cache.
Heavy files are distributed as close as possible to the devices, over your wired network.
- Smart local cache: if the drivers for the detected model are missing, the local probe downloads them just once from the central repository, then serves them to every device on the site.
- Internet connection preserved: OS images and drivers travel locally, without saturating your Internet access.
- Standalone USB media: for a site without a PXE server, you create a password-protected USB stick from the Library, set its expiry date (for example 7 days), then send it to the local technician.
Three building blocks for hands-free workstation imaging
MasteriDesk handles each task in the right place: control in the SecuriDesk panel, heavy files as close as possible to the devices, and the driver catalogue in a shared central repository.
The SecuriDesk panel
- Library: OS images, driver packages and USB media creation.
- Settings: licence standards, BIOS passwords and encryption.
- Tracking: device-by-device progress and retry of failures.
The local probe
- Background service: PXE, WinPE, WMI identification.
- Driver cache, image deployment and DISM injection.
- Reports the inventory (MAC, model, status) and receives deployment orders.
The central repository
- Global catalogue of ready-to-use driver packages.
- Secure, short-lived download links to your probe.
- The same package is not downloaded again for each customer.
Resilience: if a manufacturer changes its catalogue, the adaptation is made just once on the central repository, and service is restored for all customers at the same time.
FAQ: the MasteriDesk workstation imaging software
Scope of the workstation imaging software
Which hardware does MasteriDesk support?
Driver packages for Dell, HP and Lenovo business ranges are retrieved automatically from the manufacturers’ catalogues. The deployment engine, based on WMI and DISM, remains brand-independent. For a model that is not in any manufacturer catalogue, such as a self-built PC or a consumer range, the interface displays ‘No associated package’: you then import the driver package into your library yourself.
Can a device be deployed without a PXE server?
Yes. From the Library, you create standalone, password-protected USB media for a specific target model. You therefore need to know the exact computer model in advance, so that the right drivers and optimisation settings can be included.
Which licence activation methods are supported?
MasteriDesk supports ADBA activation, local KMS and MAK keys. ADBA activation does, however, require the devices to join the company domain.
Do the BIOS optimisations work on all devices?
No. BIOS updates and the battery profile rely on manufacturer-specific utilities (Dell, HP, Lenovo). These options therefore do not apply to unsupported hardware.
Workstation imaging day to day
What happens when a new model joins the fleet?
If its driver package is already in the central repository, the probe receives it immediately. Otherwise, if it is listed in the manufacturer’s catalogue, the repository downloads it, qualifies it, then makes it available. This very first detection may therefore take a little longer, while the package is downloaded from the manufacturer.
How does MasteriDesk preserve bandwidth?
Thanks to the local probe’s ‘Just-in-Time’ cache: a driver package is downloaded only once per site, then served locally to all devices of the same model. Heavy files therefore travel over your wired network rather than your Internet connection.
How is BitLocker encryption managed?
BitLocker is enabled automatically during post-installation, once prerequisites such as an active TPM 2.0 chip have been validated. It is conditional on the decryption key being automatically backed up to Active Directory, so the devices must join the domain. You also choose the encryption algorithm in the Settings screen.
How do I diagnose a failed deployment?
The interface shows the exact step, out of the 9, at which the deployment stopped, for example activation or BitLocker. You then retry only the failed installations.
What are the prerequisites for the local probe?
Its storage must be able to hold the OS images, which weigh several gigabytes, as well as the cache of driver packages for the models present on the site (generally between 300 MB and 2 GB per model). Automatic purging must be configured to prevent the disk from filling up.
Industrialise the preparation of your devices with our workstation imaging software
Let’s discuss your context and see together how MasteriDesk automates your deployments, from PXE boot to BitLocker encryption.