### 1 IMPORTANT: Version compatibility
Migrate within the same versions
If the new server is running another ASDM version, please update the older server (and recommended: all clients) first before you begin the migration.
For full version history, see the Change Log
### 2 Prepare the new server
1. Leave the old ASDM server running.
2. Install Auto Shutdown Manager on the new server.
3. Stop the Windows Service: "ASDM_Service" on the new server.
Wait until `AutoShutdownManager_Service.exe` is no longer visible in Task Manager.
---
### 3 Move configuration files
Copy the following files (if they exist) from the old server’s installation directory
`C:\Program Files (x86)\AutoShutdownManager\` to the identical path on the new server:
- asdm_local_settings.xml
- asdm_pp.xml
- asdm_settings.xml
- autoshutdownmanager.ini
- localtiming_data.xml
Restart the PC (or start the Windows Service: "ASDM_Service" and the AutoShutdownManager.exe) on the new server once the copy is complete.
---
### 4 Update group settings to the new server
- In Management Console on the new server, open Group Settings → select any group → Network Settings.
- Change Server IP/Name to the new server.
- Click on Accept Changes. When the "Apply changes to other Policy Group?" dialog appears, choose Yes, then press Ctrl + A to select all remaining policy groups.
- All groups will automatically be updated with the new server address.
---
### 5 Migrate the clients
While the old server is still online:
- In Management Console on the old server, open Group Settings → select any group → Network Settings.
- Change Server IP/Name to the new server.
- Click on Accept Changes. When the "Apply changes to other Policy Group?" dialog appears, choose Yes, then press Ctrl + A to select all remaining policy groups.
- All Clients in all group will automatically be updated with the new server address and start reconnecting to the new server.
- After every client has appeared in the new server’s console, decommission the old Auto Shutdown Manager Server within three weeks to avoid license conflicts.
If the old server is already offline, the simplest approach is to keep the original server name and update its DNS record so it resolves to the new server’s IP address.
---