DSOS – Deployment Guide for upKeeper Manager

Dynamic Service Operating System (DSOS) enables automated Windows deployment for both new and existing devices in upKeeper Manager.

What is DSOS?

DSOS is the boot and automation environment used in upKeeper Manager for:

• Preparing the device’s disk (UEFI only)

• Communicating with upKeeper Manager during provisioning

• Downloading and applying OS media, drivers, and packages

It can be used on computer for first time installation and re-installation of computers running Windows regardless of how they where installed the first time. 

Improvements DSOS vs SOS

Purpose: More secure, more flexible, future hardware support

Note: SOS and DSOS can mixed in a environment if configuration for both is maintained.

Requirements

Setup Overview (High-Level)

1. Build DSOS boot media (Windows PE + DSOS), both can be downloaded from our FTP.

2. Add Operating System configuration in Platform in upKeeper Manager

3. Add Hardware Profiles and configure with Driver Package

4. Ensure upKeeper Manager client is included as Platform package. 

5. Assign Platform + Hardware to devices

6. Boot device into DSOS (USB or PXE/VDS)

7. Automated provisioning begins ✅

🛠️ Step-by-step configuration

1️⃣ Prepare DSOS Boot Media

• Download our build structure or start from Windows PE (MDT/ADK). 

• Add latest DSOS component

  • To create password file used for entering diagnostic mode (previous named Debu mode)
    Run upKeeper.DSos.exe -Password [your-secret-apssword] 

  • Copy dsos-password file to INI folder so it will be added every time you rebuild DSOS

• Add necessary drivers for network and storage

• Run update script (update_SOS.cmd).

• Copy boot.wim and/or boot.iso to boot function or media.

• Deploy using:

  • USB stick

  • PXE boot via VDS

• Create application package where DSOS is copied to service partition and boot option created.

2️⃣ Configure Platform in upKeeper Manager

• Upload Windows installation media

• Add unattend-settings file
  (copy our defaults, build via Windows Setup toolkit, or auto-generate via AI)

• Add package including upKeeper Manager client (see section below)

3️⃣ Add Hardware Profiles & Driver Packages

1. Define hardware model

2. Upload relevant drivers

3. Create Driver Package (important!)

4. Ensure WIM file for driver are created

📌 If no drivers → No network or storage access

4️⃣ Ensure upKeeper Manager Client package is installed

Packages replace legacy Commands folder and included scripts and files ✅

Example script: (files to be executed most be included in package)

"%~dp0windowsdesktop-runtime-8.0.10-win-x64.exe" /install /quiet /norestart
msiexec /I "%~dp0upKeeper.Manager.Client.amd64.msi" ALLUSERS=1 ENDPOINT1=http://clientAPI.upkeeperdev.local /qb

Apply package:

• Per platform, or

• Globally (recommended)

5️⃣ Assign Configuration to Device Objects

Device object must have:

• ✅ Platform

• ✅ Hardware Profile

• ✅ Application package with DSOS (for re-installation)

Then boot into DSOS and provisioning will begin.

🩺 Troubleshooting

📌 Check DSOS console or boot diagnostic mode for more details and local log files.

✅ Summary for admins