OSManagerCLI (prerelease)
What is OSManagerCLI?
Section titled “What is OSManagerCLI?”Disguise OSManagerCLI is a command-line interface (CLI) that enables users to reimage any Disguise media server or node from a Windows computer, and achieves this over a local network.
OSManagerCLI works by ingesting the OS of a Disguise media server or node onto a Windows machine, which connects to the servers running in session via d3net. Users can then choose the media server(s) or node(s) that they want to reimage, and the process will complete.
OSManagerCLI reduces the number of required steps taken to complete a reimage when compared to the current USB Redisguise method. It also reduces the time spent on reimaging multiple servers or nodes at any one time as it can reimage one-to-many.
OSManagerCLI is self-contained, so it can also run from a large USB drive or external SSD. Your ingested OS Library travels with it, and it should “just work” when plugged into any Windows laptop. Just make sure the drive is large enough for all your OS images.
Getting started
Section titled “Getting started”You will need:
- A Disguise media server or node running Designer software version r30.2 or above and be using a supported OS version. These can be seen in the table below:
| Server | OS version |
|---|---|
| EX 2 | 25Q3 or later |
| EX 2C | 25Q3 or later |
| EX 3+ | 25Q3 or later |
| GX 3 | 25Q2 or later |
| VX 1 | 25Q1 or later |
| VX 2 | 25Q1 or later |
| VX 4 | 25Q1 or later |
| VX 4+ | 25Q1 or later |
- A Windows laptop/machine (also running Designer version r30.2 or above), on the same network (d3Net) as the servers you want to reimage. Administration access must be authorised, and there must be sufficient disk space for the OS images that need to be ingested (each is typically 10 GB or more).
OSManagerCLI hosts a Windows network share from your laptop (eg \\<your-laptop>\d3OsDeploymentShare) that your servers pull the OS from during their reimage. The first time it runs, it checks (and, if needed, adjusts) a couple of Windows file-sharing settings for you so this works smoothly.
First time installation
Section titled “First time installation”- Download and extract: Download the latest OSManagerCLI_v1.12.zip and extract
OSManagerCLI.exefrom it. That single file is all you need. - Install and run: Save
OSManagerCLI.exeinto any folder on your Windows laptop (or even an external SSD), then double-click it. On first launch it sets everything up for you, creatingconfig,logs,resourcesandd3OsDeploymentSharefolders alongside the exe, and adds a shortcut to your Start Menu. - Ingest an OS: Download the Hardware OS Images that you need. Then press the letter
Oto select Choose OS, then ingest an OS image - Choose your server: Press
Ato select Choose Actor. OSManagerCLI scans d3Net and lists the servers it finds (you can also add one directly by hostname or IP). - Start a Redisguise: With an OS and a server selected, press
Rto select Start a Redisguise. The server reboots, pulls the OS from your laptop over the network, and reimages itself. Keep your laptop powered on and connected to the network until the Redisguise finishes. The server pulls the OS from it during its reimaging cycle.
Upgrading to newer OSManagerCLI versions
Section titled “Upgrading to newer OSManagerCLI versions”We will be updating OSManagerCLI from time to time. Please follow these steps to update:
- Delete the old
OSManagerCLI.exefile and drop the new version in its place. - Leave everything else (your
config,logs, ingested OS Library, etc) untouched.
See the Release notes for what’s changed in each version.
Giving feedback
Section titled “Giving feedback”OSManagerCLI is under active development and your feedback directly shapes it. We’re especially keen to hear about usability, anything that confuses you, and of course any bugs.
Please share any feedback with product-team@disguise.one. When you get in touch, please:
- Describe what you were doing, what you expected, and what actually happened.
- Zip up your
logsfolder (it sits next to the exe) and attach it. It helps us get to the bottom of issues quickly.
See also
Section titled “See also”- Command line & exit codes — advanced/automated use and what each exit code means.
- Release notes — what’s new in each version.