DE 
EN Release 4 → Release 5
Upgrade to Auto Shutdown Manager Release 5 with confidence
A practical migration guide for existing Release 4 environments: understand the license change, prepare the required Microsoft .NET Framework, upgrade the server first, and then move managed clients in controlled groups.
Important upgrade note
Release 5 is a major upgrade
A Release 4 license does not activate Release 5. Obtain a valid Release 5 license before changing the server or a stand-alone installation. For current upgrade options, contact our Sales Team.
Why upgrade
More control, visibility and automation
Release 5 expands Auto Shutdown Manager beyond scheduled power actions. These highlights help administrators manage modern endpoints, segmented networks and larger rollouts from one operating layer.
Modern Standby management
Support scheduled wake-ups and apply dedicated controls for Modern Standby scenarios.
Explore Modern StandbyIT asset intelligence
Report on operating systems, software, BIOS versions, processors, storage, video controllers and other endpoint details.
Explore IT Asset ManagementEnterprise Wake-on-LAN
Use WOL scheduling, WOL Proxies, Wake-on-WAN and web-based WOL Portals across supported network scenarios.
Explore WOL PortalsMCM / SCCM integration
Coordinate power actions with Microsoft Endpoint Configuration Manager and System Center Configuration Manager workflows.
View the Feature ListRicher reports
Review client timing, power consumption and savings data with more detailed central reporting.
Explore Reporting & CO₂Automation-ready workflows
Extend scheduled operations with XML job files and use the available MCP Server for supported AI-agent workflows.
See Current DownloadsBefore installation
Prepare the environment first
A short preflight keeps the server change predictable and makes the client rollout easier to control.
1
Confirm licensing
Have the new Release 5 license available before upgrading the server or a stand-alone PC. Ask our Sales Team for the currently available upgrade option.
2
Check Microsoft .NET
Install the framework required by the exact Release 5 build on the server and clients before deploying the software.
See the .NET requirements3
Plan controlled client groups
Schedule the rollout and divide clients into manageable groups. The existing guidance recommends group-by-group updates to reduce network load.
Migration sequence
Upgrade the server, then the clients
Use this order for an Auto Shutdown Manager Server or a stand-alone installation, followed by centrally managed clients.
01
Prepare the server or stand-alone PC
Confirm the new license and the required Microsoft .NET Framework. Record the existing installation directory before making changes.
02
Remove Release 4
Uninstall the old version through Windows Control Panel → Programs. Do not begin until the Release 5 license and prerequisites are ready.
03
Install Release 5 in the previous directory
Use the same installation directory to retain the existing configuration and settings, then enter the new license key to register Release 5.
04
Update managed clients centrally
Open the Management Console on the Auto Shutdown Manager Server and use Update Manager. Process clients group by group rather than upgrading the entire estate at once.
Runtime prerequisite
Microsoft .NET requirements at a glance
The framework requirement depends on the exact Release 5 build being installed.
5.5.x+
Microsoft .NET Framework 4.x
Release 5.5.x and newer require Microsoft .NET Framework 4.x on the Auto Shutdown Manager server and clients.
5.4−
Microsoft .NET Framework 3.5
Release 5.4 and earlier require Microsoft .NET Framework 3.5 on the server and clients.
Post-upgrade acceptance
Validate a small group before broad rollout
After the server upgrade, confirm the essential management path with a controlled client group before expanding deployment.
Console and registration
Confirm that the Management Console opens, the new license is registered and existing settings are present.
Client communication
Update a small group first and verify that those clients reconnect and report their expected state.
Core workflows
Test the power actions, schedules, WOL path and reports that matter to your environment before continuing.
FAQ
Release 5 upgrade questions
Can a Release 4 license activate Release 5?
No. Release 5 is a major upgrade and requires a new Release 5 license. Contact our Sales Team for the current upgrade options.
Can the existing configuration be retained?
The current upgrade guidance says to install Release 5 in the previous installation directory to retain the existing configuration and settings.
Do all clients need to be reinstalled manually?
The documented upgrade path uses Update Manager in the server's Management Console to upgrade managed clients centrally.
Should every client be upgraded at once?
No. The existing guidance strongly recommends processing clients group by group to reduce network bandwidth and keep the rollout controlled.
How can I identify the installed release?
Open Auto Shutdown Manager and check the release number shown in the lower green area of the application window.
Ready to migrate?
Plan the license, prepare the server, then roll out with control.
Talk to our team about the right Release 5 upgrade option, review the current feature set, and prepare the required installer before changing your environment.