Tactical migration
Administration › Tactical migration moves computers from Tactical RMM to Control. You mark a client or single computers, and every computer migrates on its own as soon as it is online. Workstations that only run now and then come along without any follow-up work. The page is for admins only.
Steps per computer
| Step | What happens |
|---|---|
| online | Control loads the computer list from Tactical every 5 minutes. As soon as Tactical reports a marked computer online, the migration starts. |
| install | Control sends the install command for the Control agent through Tactical. It contains an installer link for customer and site. There is no reboot, and the user notices nothing. |
| connected | As soon as the computer registers in Control, a 30-minute waiting time starts. If the connection drops during that time, the waiting time starts over. |
| Tactical removed | After 30 minutes of stable connection, Control deletes the computer in Tactical, and Tactical uninstalls its agent and Mesh. For this the computer must also be online in Tactical. |
If a step fails, Control tries again after one hour, at most five times. If the computer went offline again before the command ran, that does not count as a failed attempt; it simply keeps waiting. If the agent does not register in Control within 20 minutes after the installation, that counts as a failed attempt. Show output then shows what the installation reported.
If the target customer already has a Control computer with the same serial number (or, without a serial number, the same name), the installation is skipped and the computer goes straight to connected. The same name with a different serial number counts as a different computer. Placeholders like To be filled by O.E.M. do not count as serial numbers, which mostly affects VMs.
Without a serial number only the name at the target customer counts. If several computers there have the same name, the IP address decides (Tactical reports the local IPs). If it is still not unique, Control does not guess: the computer is shown as Problem and nothing is installed for now. Delete the duplicate computer in Control and then click Retry now.
Control compares the IP address with all addresses of the Control computer's network adapters, not just the displayed IP. For many computers that is the public address, while Tactical only knows the LAN addresses.
Computer is already in Control: link it
If Control does not detect a computer by itself, for example because it has a different name in Control, belongs to another customer or has no serial number, click Link to Control computer in its row. The dialog suggests Control computers with the same serial number, the same name or the same LAN IP, across all customers. You can also search by name, customer or IP at the top.
After linking, Control installs nothing. The migration then belongs to the customer of the chosen Control computer and is at connected. Tactical including Mesh is removed once the Control computer has been connected for 30 minutes. Remove Tactical immediately skips the wait. If the Control computer is offline right now, Control still waits until it is online. Remove from migration undoes a link as long as Tactical has not been removed yet.
If both the Tactical and the Control computer have a real serial number and they differ, or the Control computer is already linked to another Tactical computer, Control asks first (Link anyway). The audit log records both serial numbers.
List
- Computers are grouped by Tactical client. Clicking the client row expands or collapses it. Clients with a running migration are on top and expanded.
- The tiles at the top and the filter chips show Not marked, Waiting, Running, Migrated and Problem.
- Below them you filter by Status (online/offline in Tactical) and Type (workstation/server). The filters can be combined. Start migration in the client row then takes only the filtered computers, e.g. only servers that are online right now.
- The search finds computer, client, site, serial number, logged-in user and operating system.
- The Steps column shows how far the computer is. The step that failed last is shown in red.
- already in Control at … (same serial number) means the same computer already has a Control agent, possibly at another customer (e.g. Onboarding). Check this before starting.
- same name already at … in Control – check only appears if the target customer has a computer with that name. Identical server names (e.g.
SRV01) at other customers do not count. - The client row shows which Control customer the Tactical client corresponds to. Control determines this in this order: assigned manually, migrated there before, same or uniquely similar customer name, only then the computer names (most computer names are already at that customer, at least 2 and at least half of the computers that already exist in Control, e.g. “KBM” → Kuratorium Bayerischer Maschinenringe). Scheme names like
srv01,kasse1orremote01that exist at several customers only count partially – otherwise e.g. one pharmacy would be suggested the customer of another pharmacy. If that is wrong or the row says no Control customer detected, set it with Assign customer. The assignment is stored and is also the default when starting a migration. - n× in Tactical means the same name appears several times at this Tactical client, usually leftovers after a reinstall. Take the entry that is online right now.
- Finished migrations stay in the list even after the computer was deleted in Tactical.
- Column widths can be dragged at the edge of the column header.
Start a migration
Tick computers, or click Start migration in the client row. A start always covers one Tactical client.
| Field | Meaning |
|---|---|
| Customer in Control | Target customer. Control suggests it by name, or uses the customer this Tactical client was migrated to before. |
| Sites | Each Tactical site is mapped to a Control site. Missing sites are created at start (create “…”). |
| Customer contracts | The ticked contracts apply to the whole customer, so the new computers get their policies right away. If you leave the selection unchanged, Control does not change the contracts. |
| Remove Tactical after the migration | On by default. Off = the migration ends after the stable connection and Tactical stays installed. |
| Migrate servers only after approval | Servers wait until you start them one by one with Approve in their history. |
Computer history
Clicking a computer that is being migrated opens its history on the right, with all steps and errors. It has these buttons:
- Retry now: resets the waiting time after an error. After five failed attempts the count starts over.
- Approve: starts a server that is waiting for approval.
- Remove Tactical now: removes Tactical in the next run without waiting the 30 minutes.
- Remove from migration: the computer stays in Tactical. Anything already installed stays installed.
- Show output: shows what the installation reported. The installer token is masked.
- Open in Control: opens the computer in Control once it has registered.
Tactical access
Under Tactical access you enter the Tactical API address (e.g. https://api.example.com, not the web UI) and an API key. You create the key in Tactical under Settings › Global Settings › API Keys. Control checks the access when you save and loads the computer list. The key is stored encrypted (SCRIPT_VAULT_KEY) and never shown again. To change only the address, leave the key field empty.
The base_url setting must also be set, i.e. the address at which the computers reach Control.
Audit
Start, approval, retry, removal from the migration and every removal of Tactical are written to the audit log. The installer links of a migration are named Tactical-Umzug. They are valid for 90 days and appear in the customer panel under Installer links.