DeployR Community

DeployR identifies the make and model from the device firmware and downloads the matching driver pack directly from the OEM, using a catalog that 2Pint keeps updated. The "Inject drivers from cloud" step runs in Windows PE, so the disk and network drivers needed to resume the sequence are in place before deployment continues.

It also works as a safety net: add it alongside your own driver packs with a simple condition, and DeployR will only reach out to the cloud when it has no local drivers for that model.

DeployR Community includes the 2PXE server component of 2Pint Software's iPXE Anywhere, a network booting solution built on the open-source iPXE bootloader for ultra-fast booting over any type of network and faster operating system builds and rebuilds. It runs standalone, so there's no dependency on Configuration Manager or Windows Deployment Services.

iPXE downloads boot images over HTTPS rather than the TFTP used by traditional PXE, which is both faster and more secure, and it boots devices with Secure Boot enabled. Whether you're provisioning new devices, handling break/fix, or rebuilding after a malware incident, the process is the same: boot, select a task sequence, deploy. DeployR takes it from there — OS imaging, driver injection, and app installation.

Where PXE booting isn't practical — remote sites, restricted networks, the occasional one-off rebuild — DeployR can generate media with a single PowerShell command. Standalone media carries the task sequences and all the content items they need, so no communication with the DeployR server is required. Caching media includes a selection of content and authenticates back to the server, so anything not already on the media is downloaded on demand.

Tag your content items to control exactly what gets included, write it to a USB device, or create an ISO to boot virtual machines.