Backing Up Siemens TIA Portal Licenses via Automation License Manager
Siemens automation software (STEP 7, TIA Portal, WinCC, PCS 7, SINAMICS Startdrive, SIMOTION Scout) is protected by license keys bound to a hardware container (USB stick) or a software container (virtual hard-disk key). When the original media fails, is lost, or the engineering PC is rebuilt, recovering the runtime capability of the engineering station (ES) or operator station (OS) requires a verified backup or a formal recovery request to Siemens Industry Online Support. This reference documents the practical backup procedure using the Siemens Automation License Manager (ALM), the certificate of license (CoL) workflow, the command-line backup path, and the recovery procedure when no backup is available.
1. Why a License Backup Is Mandatory
Siemens license keys are non-reproducible cryptographic objects generated against a unique order number and a unique license certificate number. Once issued:
- The same license serial number cannot be duplicated onto a second container.
- If the host PC is rebuilt without first exporting the key, the key is lost with the drive.
- Re-issuance is a manual process that requires the original Certificate of License (CoL) and verification by Siemens.
- Lead time for verified re-issuance runs typically 5 to 10 working days plus courier transit.
Backups are the only way to eliminate this downtime window.
2. License Types and Container Formats
| License Type | Container | Transferable | Backup Method |
|---|---|---|---|
| Single License | USB stick or local hard-disk key | Yes (with deactivation) | ALM export or COA image |
| Floating License | Network license server | Yes (server-to-server) | ALM server-side export |
| Trial License | Local hard-disk key | No | Not required (expires) |
| Upgrade License | USB or local | Yes (paired with base) | ALM export |
| ES/OS Runtime License (WinCC) | USB or local | Yes (deactivation required) | ALM export |
Verify the installed license set on the engineering station before initiating backup. Open ALM, expand the host node, and note the part numbers (e.g., 6AV2 100-0AA00-0AA0 for WinCC ES, 6ES7 822-1AA03-0YA5 for STEP 7 Professional Combo). These part numbers are required when re-ordering a replacement or when generating a recovery request.
3. Prerequisites
- Automation License Manager installed. ALM is installed by default with TIA Portal, STEP 7, WinCC, and Startdrive. Standalone installer available from the Siemens support portal as SIMATIC Automation License Manager.
- Local administrator rights on the engineering PC (required to read/write the protected license vault).
- A known secure destination path for the backup file (network share, secondary drive, or encrypted external media). Do not store the backup on the same physical drive as the original key.
- Certificate of License (CoL) document for every license in scope. The CoL is the printed or PDF document shipped with the original media; it carries the license certificate number required by Siemens support.
- If the engineering station runs floating licenses, access to the license server (default TCP/4410 for the ALM RPC channel) and administrative credentials for the server account.
4. ALM Backup Procedure – Local License Keys
4.1 Launch the Automation License Manager
From the Windows Start menu launch Siemens Automation License Manager (executable: almsrvapp.exe, normally located at C:\Program Files\Siemens\AutomationLicenseManager\Bin or C:\Program Files (x86)\Siemens\AutomationLicenseManager\Bin). Connect to the local PC.
4.2 Identify the License Holders
- In the left pane, expand the local host entry (e.g.,
PC-ENG-01 [local]). - Expand the License Keys node. All currently installed keys are listed with part number, license name, and validity date.
- For each key, right-click and select Properties to capture: part number, certificate number, and expiration. Record this data in a license inventory file for audit purposes.
4.3 Export the License Key
- Right-click the target license entry.
- Select Back up license key (or Export > License key in newer ALM versions).
- Choose a destination folder. The ALM writes a
.ziparchive containing the encrypted key (file extension.licbin) and a metadata file (.xml) carrying the part number, certificate number, and binding hash. - Repeat for every key in the inventory.
4.4 Verify the Backup
After export, perform a round-trip verification:
- Copy the backup archive to a scratch directory on a different PC that has ALM installed.
- Open ALM on the scratch PC, right-click the local host, and select Import license key.
- Point to the exported
.zipfile. ALM extracts and validates the key. A successful import displays the license under the local host. - Deactivate or delete the test key immediately after verification to keep the certificate unique to the original host.
5. ALM Backup Procedure – Floating License Server
For a centralized license server (recommended for plants with 5+ ES/OS seats), the backup is performed on the server side:
- Connect ALM to the license server using Connect to remote computer and enter the server hostname or IP.
- Stop the ALM service on the server:
sc stop "almsrv"from an elevated command prompt. This prevents key corruption during export. - Right-click each license in the server inventory and select Back up license key.
- Restart the service:
sc start "almsrv". - Validate that floating clients can re-checkout the license by opening a TIA Portal instance on a sample client.
6. Command-Line Backup (Silent / Scripted)
For scripted, repeatable backups (e.g., scheduled task), ALM ships a console executable. The path is typically:
C:\Program Files\Siemens\AutomationLicenseManager\Bin\almcl.exe
Common command-line operations:
| Operation | Command Syntax |
|---|---|
| List all installed keys | almcl.exe -list -host local |
| Export a key by certificate number | almcl.exe -export -cert <CertNo> -path D:\LicenseBackups |
| Import a key | almcl.exe -import -path D:\LicenseBackups\<CertNo>.zip |
| Deactivate (return to container) | almcl.exe -deactivate -cert <CertNo> |
| Service status | sc query almsrv |
Example scheduled task (PowerShell) to back up all local keys nightly:
$dest = "\\fileserver\licbackup\$env:COMPUTERNAME-$((Get-Date).ToString('yyyyMMdd'))"
New-Item -ItemType Directory -Force -Path $dest
& "C:\Program Files\Siemens\AutomationLicenseManager\Bin\almcl.exe" -exportall -path $dest
7. ES and OS Specific Considerations (WinCC / PCS 7)
WinCC Engineering Stations (ES) and Operator Stations (OS) ship with their own license parts. In PCS 7 environments, the OS runtime license is bound to the OS server. When backing up:
-
WinCC ES licenses (
6AV2 100-...series) must be backed up from each engineering PC. They cannot be pooled on a single workstation. -
WinCC RT / OS Server licenses (
6AV2 101-...series) are activated on the runtime server. Activation must be deactivated (returned to the container) before the container is exported, otherwise the license remains in use on the source host. - AS Engineering (STEP 7 / TIA Portal) licenses can be moved freely with ALM deactivate-then-activate sequence, but PCS 7 AS bundle licenses often ship as a combo key covering multiple components; back up the entire key, not individual components.
8. License Recovery When No Backup Exists
If a backup is not available, the only path is a formal recovery request through Siemens Industry Online Support. Expect the following workflow:
- Open a support request at the Siemens Industry Online Support portal. Category: Licensing / License recovery.
- Provide scanned copies of: the original Certificate of License (cover page) showing the certificate number; the original USB stick or floppy label; a recent ALM log file (ALM > Help > Save log) proving the key is defective or missing.
- Siemens verifies the certificate number against the original order record. Confirmed requests are escalated to license fulfillment.
- A new USB key with the same certificate number is shipped via DHL / FedEx. Standard lead time: 5 to 10 working days after verification. Hot cases (production-down) are routed via the support hotline and have been delivered in 24 to 48 hours in documented cases.
- On receipt, install the new key via ALM > Connect target computer > Install license.
9. Transferring Licenses Between Stations
When migrating a license from one ES to another (e.g., hardware refresh):
- On the source PC, open ALM and select the key.
- Click Transfer license (or Deactivate on older ALM versions). The key is returned to the original USB container or to a transferable archive.
- Move the USB stick to the target PC, or copy the archive to the target PC.
- On the target PC, connect ALM, plug the USB stick, and click Activate. The key is now bound to the new host.
License transfer works only if the original certificate number remains unique. The deactivation step must complete successfully; if ALM reports a defective or unreachable container, escalate to Siemens support immediately.
10. Verification Checklist
| Check | Method | Pass Criteria |
|---|---|---|
| All keys exported | ALM > Compare host vs. backup file count | Counts match inventory |
| Backup file integrity | Import on scratch PC, then deactivate | Import succeeds, key recognized |
| CoL on file | Manual file check | One CoL per certificate number |
| Service health (server) | sc query almsrv |
STATE = RUNNING |
| Client check-out (floating) | Open TIA Portal on client | License acquired, no dialog warning |
| Backup stored off-host | Path verification | Not on C:\ of source PC |
11. Troubleshooting Matrix
| Symptom | Root Cause | Resolution |
|---|---|---|
| ALM shows no keys after rebuild | Key lost with old drive | Restore from backup or open recovery request |
| Export fails: "License is in use" | Application (TIA Portal, WinCC) is open | Close all Siemens apps, stop almsrv, retry |
| Import fails: "Certificate mismatch" | Wrong CoL or duplicate key | Verify CoL number; contact Siemens if duplicate |
| USB stick not detected | Driver / port issue | Reinstall ALM; try different USB port; check Device Manager for "SafeNet" or "Siemens USB License Key" |
| Floating client cannot reach server | Firewall blocking TCP 4410 | Open inbound 4410/tcp on server; verify with Test-NetConnection -Port 4410
|
| ALM "almsrv" service will not start | Corrupt installation or missing license vault | Repair ALM via Programs and Features; check C:\ProgramData\Siemens\AutomationLicenseManager
|
| Recovery request rejected | CoL not provided or unreadable | Resubmit with clear scan of cover page and S/N of USB stick |
12. Storage and Retention Recommendations
- Retain license backups for the full lifecycle of the engineering PC plus the standard retention policy of the plant (typically 7 years for GMP / regulated industries).
- Encrypt backup files at rest (BitLocker on the storage volume or 7-Zip AES-256).
- Include a license inventory sheet (CSV or XLSX) in the same folder. Columns: Hostname, Part number, CoL number, Export date, Expiry, Notes.
- For multi-site deployments, replicate backups to a central secured share with read-only ACLs for the engineering group.
For environments using Siemens Desigo CC building automation, license management is handled by the License Management Utility (LMU) with a separate backup tree under Settings > Backup (see Siemens LMU Engineering documentation). The principle is identical: secure the key outside the host, retain the certificate document, and verify import on a scratch host.
Where does Automation License Manager store the license key on a local hard-disk container?
The default vault is under C:\ProgramData\Siemens\AutomationLicenseManager. The actual key file carries the certificate number in its name. Use ALM's export function rather than copying the vault directly; direct copy will not be recognized as a valid transferable key.
Can a single CoL be used to re-issue a license more than once?
No. Siemens records a one-to-one mapping between CoL and issued certificate number. A second claim on the same CoL is treated as license fraud unless the original key is provably destroyed and the requester supplies a statutory declaration.
How long does a Siemens license recovery request take?
Standard verified recovery is 5 to 10 working days plus courier transit. Documented production-down escalations routed through the support hotline have been fulfilled in 24 to 48 hours. Maintaining a current CoL binder is the single largest factor in reducing this time.
Is a drive-image (ghost) backup a valid substitute for ALM export?
For software-container keys (hard-disk license), yes, a drive image captures the key. For USB-dongle keys, no — the dongle must be backed up via ALM export. A combined strategy of ghost image plus ALM export is the recommended best practice.
Which ALM version pairs with which TIA Portal?
ALM 6.0 ships with TIA Portal V17; ALM 6.1 with V18; ALM 6.2 with V19. Older TIA Portal versions (V15, V16) use ALM 5.x. Newer ALM versions are backward compatible with older TIA Portal projects but cannot back up keys generated by a newer ALM if the receiving host runs an older ALM. Keep the ALM version aligned with the highest TIA Portal in your fleet.