How can I move the Auto Shutdown Manager Server to a new PC?

To migrate the Auto Shutdown Manager Server, you need to follow these main steps: 1. Stop the 'Auto Shutdown Manager Server' service on the old server. 2. Copy the database file 'AsmSrv.db' from the old server's installation directory (e.g., C:\Program Files\Auto Shutdown Manager Server) to a temporary location. 3. Install Auto Shutdown Manager on the new server but do not start the service immediately. 4. Replace the newly created AsmSrv.db file on the new server with the one you copied from the old server. 5. Start the 'Auto Shutdown Manager Server' service on the new server.

Do I need to do anything with the license during migration?

The license key is stored within the AsmSrv.db database file. Therefore, by copying this file to the new server, the license is automatically migrated along with all other settings. No separate license transfer is needed.

What happens to the clients after the server is migrated?

After the server migration, the clients will automatically find the new server in the network. This is typically achieved via a UDP broadcast mechanism. Once the new server is running and reachable on the network, the clients will connect to it without requiring manual reconfiguration.

Support · FAQ

Migrate Auto Shutdown Manager Server and clients safely

Move the Auto Shutdown Manager (ASDM) Server to a new PC without losing policy settings or stranding clients. Keep the old server online, migrate configuration files, update group settings, then let clients reconnect to the new server.

Server migrationClient reconnectPolicy groupsVersion compatibility

Quick answer

Use a controlled handover: same ASDM version, old server still online, configuration copied, groups pointed to the new server.

The safest migration starts by updating the old server first if versions differ. Install ASDM on the new server, stop its service, copy the configuration files, start the new server, update the new server’s group settings, then point clients from the old server to the new server address.

✓

Match versions first

If the new server runs a different ASDM version, update the older server first. Recommended: update clients too before starting migration.

↔

Keep the old server online

Clients can receive the new server address only while the old server is still reachable and managing their policy groups.

Decommission last

After all clients appear in the new console, remove the old ASDM Server within three weeks to avoid license conflicts.

Prepare the new server

Leave old server runningDo not take it offline yet.

Install ASDMInstall Auto Shutdown Manager on the new server.

Stop serviceStop ASDM_Service on the new server.

Wait for process exitConfirm the ASDM service process is no longer visible in Task Manager.

Copy configuration files

Copy the files that exist from the old installation directory to the identical path on the new server:

C:\Program Files (x86)\AutoShutdownManager\asdm_local_settings.xml
C:\Program Files (x86)\AutoShutdownManager\asdm_pp.xml
C:\Program Files (x86)\AutoShutdownManager\asdm_settings.xml
C:\Program Files (x86)\AutoShutdownManager\autoshutdownmanager.ini
C:\Program Files (x86)\AutoShutdownManager\localtiming_data.xml

Restart the PC or start ASDM_Service and AutoShutdownManager.exe once the copy is complete. The service process check from the preparation step refers to AutoShutdownManager_Service.exe.

Update group settings on the new server

Open group settingsIn Management Console on the new server, open Group Settings and select any group.

Network SettingsChange Server IP/Name to the new server.

Accept changesWhen asked to apply changes to other policy groups, choose Yes.

Select all groupsUse Ctrl + A to select all remaining policy groups so they are updated automatically.

Migrate the clients from the old server

Use old server consoleWhile the old server is still online, open Group Settings there.

Change Server IP/NamePoint policy groups to the new server.

Apply to all groupsChoose Yes, then Ctrl + A to update all remaining policy groups.

Watch reconnectClients should start reconnecting and appear in the new server console.

Preferred pathOld server online, clients receive the new Server IP/Name through group policy settings.

Offline fallbackKeep the original server name and point DNS to the new server IP.

ValidationConfirm clients appear in the new server console before decommissioning the old server.

License safetyAfter client migration, decommission the old ASDM Server within three weeks.

Can I migrate to a new server with a different ASDM version?

Do not start the migration with mismatched versions. Update the older server first, and preferably update all clients before migration.

Why must the old server stay online?

The old server can update client policy groups with the new Server IP/Name. If it is offline, clients may not receive the new address automatically.

Which files should I copy?

Copy the existing configuration files from the old installation directory to the identical path on the new server: asdm_local_settings.xml, asdm_pp.xml, asdm_settings.xml, autoshutdownmanager.ini and localtiming_data.xml.

How do I update all policy groups?

After changing Server IP/Name for one group, accept the dialog to apply changes to other policy groups and use Ctrl + A to select all remaining groups.

What if the old server is already offline?

Use the original server name and update DNS so it resolves to the new server IP.

Shut down safely. Wake reliably. Prove the savings.

Need help planning a controlled ASDM migration?

Use the migration checklist to prepare the new server, move settings, update policy groups and verify client reconnect before decommissioning the old server.

Contact Support Talk to Sales Back to FAQ Support