Provisioning new PCs
From v3.49.0 Control sets up new Windows PCs automatically: install programs, apply Windows settings, write support info, rename by serial number, install Windows updates and reboot. This replaces the old setup script from Tactical RMM.
How it works
- An administrator creates a profile under Automation > Provisioning: a list of steps.
- The profile is assigned: as default, to a customer, a site or a Windows group.
- When a new PC joins with the agent afterwards, Control starts the matching profile on its own. Every step is a script task; the next one only starts once it reports success.
- The host panel shows the progress ("Step 3/9 – Install packages"), the Windows list shows Provisioning 3/9 or, in red, Provisioning failed.
The run is driven by the Control scheduler. If Control restarts in between, provisioning continues afterwards.
When does provisioning start automatically?
Only when all of this applies:
- The PC has been in Control for at most 30 days.
- The PC joined after the assignment that applies and after "Set up new PCs automatically" was switched on for the profile.
- The PC is online, its device type is known and matches the profile (workstation, server, all).
- Provisioning has never run on the PC, not even a cancelled one.
- The PC is not in maintenance, not out of service and not isolated.
Existing PCs are never provisioned automatically, not even when you assign a profile later. For them use … > Start provisioning … in the host panel (permission "Edit" in the Windows module).
Which profile applies?
Exactly one profile applies to a PC, in this order:
- Site of the PC
- Group of the PC
- Customer of the PC
- Default
If there are several profiles on the same level (e.g. two groups), the older assignment wins. Only active profiles count. A PC whose device type is still unknown only gets profiles with device type "All".
Steps
| Step | What happens |
|---|---|
| Install packages | Chocolatey or winget per step. With Chocolatey, type the name (e.g. "irfan") and pick the package from the list, its ID is filled in. The list is sorted by downloads, so the official package is usually on top. Empty version = always the latest. With winget, enter the ID by hand (e.g. 7zip.7zip). If Chocolatey is missing, Control installs it first. Installed packages are skipped. Exit codes 0, 1641 and 3010 count as success, 1641/3010 trigger a reboot. One line per package: PKG <id>: installiert, bereits vorhanden or FEHLER <code>. |
| Apply settings | Fixed list: telemetry off, classic context menu (Windows 11), web search in start menu off, fast startup off, power plan high performance, hide 3D Objects, activity history off, PowerShell module PSWindowsUpdate. |
| Set support info | Windows system information (manufacturer, phone, support URL, support hours). The manufacturer comes from branding unless you enter one in the step. |
| Rename computer | By BIOS serial number or a custom pattern like {{kunde.nummer}}-{{host.id}}. At most 15 characters, only A–Z, 0–9 and hyphen. If the PC already has the name, nothing happens. |
| Run script | A script from the library (Windows module) with arguments, like a normal run. |
| Install Windows updates | Via PSWindowsUpdate (Get-WindowsUpdate -AcceptAll -Install -IgnoreReboot), the module is installed if needed. May take up to 2 hours. |
| Reboot | shutdown /r /t 30. Control waits until the PC is back online and its uptime shows it really rebooted. After 45 minutes without return the step fails. |
User settings (web search, context menu) are written to the Windows default profile and to all currently loaded user profiles, so they apply to existing and new users. The old script wrote them as SYSTEM, i.e. into the wrong profile.
Automatic reboot
If a step reports "reboot required" – rename, packages with code 1641/3010, Windows updates or a custom script printing DZ_REBOOT_REQUIRED – and the next step is not a reboot, Control inserts a reboot right after it (also at the end). The host panel shows it as "Neustart (automatisch)".
Template "Standard workstation"
The button Template standard workstation pre-fills a new profile like the old script:
- Packages (Chocolatey): 7zip, adobereader, notepadplusplus, vlc, irfanview
- Settings: telemetry, classic context menu, web search, 3D Objects, activity history, PSWindowsUpdate
- Support info from branding
- Rename by serial number
- Reboot
- Windows updates
- Reboot
Enter phone, support URL and hours in the support info step. Then save and assign.
In the host panel
- Provisioning box at the top: status, current step, error text. Expand to see all steps with result and output. The panel reloads every 10 seconds while provisioning runs.
- Retry: runs the failed step again; then it continues normally. If a reboot failed by timeout and the PC is back by now, it continues without another reboot.
- Cancel: no further step is started. A step already running on the PC finishes.
- … > Start provisioning …: choose a profile and confirm. Caution: installs software and reboots the PC.
- … > Provisioning report: computer, customer, date, profile, result per step and installed packages. Print opens the print dialog with a clean page (can also be saved as PDF).
Permissions
| Action | Who |
|---|---|
| Create, change, assign, delete profiles | administrators only |
| Start, retry, cancel provisioning | administrators or permission "Edit" in the Windows module |
| See progress and report | anyone allowed to see the host |
Customer-bound users only see and start provisioning on PCs of their customer. MCP tokens cannot start provisioning.
Limits
- Windows only for now.
- winget does not always work as SYSTEM: App Installer must be up to date on the PC, some packages have no machine-wide installer. If in doubt, use Chocolatey.
- Domain PCs usually cannot be renamed as SYSTEM (that needs a domain account) – rename in AD or leave the step out.
- The classic context menu for new users is set at their first sign-in (Software\Classes is not part of the default profile).
- If the agent is reinstalled on an old PC and creates a new host, the PC counts as new.