Introducing DeployR 1.0

After two years of development, the DeployR product is now available to handle those bare metal OS deployment scenarios that you all still need.  For those used to the Microsoft Deployment Toolkit (rest in peace) or Microsoft Configuration Manager, this is designed to feel familiar, while at the same time using current technologies.  No more VBScript, file shares, or MMC snap-ins.

We know that IT admins don’t want a solution that is only half of what they used before.  Even though this is a version 1.0 release, it is filled with features to make the geekiest deployment experts happy: built by deployment experts for deployment experts.

DeployR is built on a modern technology stack.  First, all administrative tasks are performed via a web portal, the “dashboard,” so all you need is a web browser to edit your task sequences; upload content like apps, driver packs, and operating systems; manage boot images; and monitor all ongoing deployments.

Next, we needed a task sequence engine to execute the task sequences.  We created this from scratch, leveraging .NET Core and PowerShell 7, but following the same basic ideas that were first implemented in the older engines: everything is controlled by task sequence variables, which persist through the whole process, from Windows PE into the new OS.  (We even used the same log file format – some things shouldn’t be changed.)

And of course, the task sequences themselves are composed of PowerShell 7 scripts that do the actual work.  We provide a set of templates for you to start from, but you can always start from scratch to create your own.

I’ll be posting more in-depth content on DeployR in the coming days and weeks, but for now you can read more on the product page, in the documentation, and on the pricing pages (for commercial and public sector or non-profit customers)