DE 
EN 
Resources · Deployment Guides
Deploy Auto Shutdown Manager across your Windows environment
Install the server first, provision clients through your existing MSI deployment workflow, and bring endpoints under central configuration after their first connection.
Auto Shutdown Manager (ASDM) works with the deployment processes you already use. Group Policy, MECM/SCCM and other software-distribution platforms are supported.
Preflight
Check network access and pilot scope
Check server access, MSI source permissions and the pilot PC list before deploying clients.
Server and network
- Install and configure the ASDM Server before deploying clients.
- Use a stable DNS name or server IP address.
- The required incoming TCP port is automatically allowed in Windows Firewall on the server. Port 8088 is used by default and can be changed if needed. If you use a firewall other than Windows Firewall, you may need to configure the corresponding port rule manually.
- No incoming port is required on ASDM clients for normal operation.
- Review supported Windows versions, .NET, database options and virtualization in the system requirements.
Source and pilot group
- Ensure target computers can read the MSI deployment source.
- For service-based deployment, grant the domain computer accounts read access.
- Begin with a controlled computer group or OU.
- Validate installation, first connection, policy delivery and removal behavior before scaling.
Deployment workflow
Step-by-step deployment guide
Set up the server, deploy the MSI to a pilot group and check that the clients connect. Then expand the rollout and manage settings centrally.
Install the ASDM Server
Install the server before the clients and complete its basic configuration.
Prepare the deployment source
Place AutoShutdownManager5.msi in a readable network source and add provisioning data when required.
Deploy with your standard tool
Use GPO, MECM/SCCM or another MSI-capable deployment process already established in your environment.
Provision the server connection
The client reads the server DNS name or IP address and the configured TCP port from the "server.ini" source file or the MSI parameters.
Complete the first connection
After installation, the client connects to the server and retrieves its initial configuration. This can take up to ten minutes; see our manual for further details.
Assign groups and policies
Manage settings, configuration changes and later client updates centrally from the ASDM Server.
Automatic provisioning
Avoid entering server data manually on every client
ASDM supports two methods for supplying the server connection during MSI installation.
Method A: server.ini
Place a file named server.ini beside the MSI in the deployment source. It contains exactly two lines: the server DNS name or IP address, followed by the TCP port.
asdm-server.example.local
8088Do not add comments or extra lines. Clients read the file from the installation source during setup.
Method B: MSI command line
Pass the same server and port information as installation parameters when your deployment system builds the MSI command.
msiexec.exe /i AutoShutdownManager5.msi server="ASDMCTRL" port=8088Use your actual server name or IP address and the port configured on the ASDM Server.
Technical resources
Installation guides and video
The manual, GPO guide and setup video explain installation and configuration.
Auto Shutdown Manager Manual V5
Full reference for installation, server/client configuration, MSI provisioning, image-based environments, updates and administration.
Windows Group Policy Deployment
Step-by-step reference for preparing the source, security filtering, computer assignment, distribution and removal.
Advanced Client/Server Setup Guide
Watch the installation overview covering the key concepts for standalone and client/server setups.
Image-based systems
Auto Shutdown Manager supports image-based systems. See the manual for further deployment details.
FAQ
Deployment questions from IT administrators
Does every ASDM client require manual server configuration?
No. During MSI installation, clients can receive the server address and port from a server.ini file in the installation source or from command-line parameters. See automatic provisioning for details.
Which firewall rule is required?
The ASDM Server requires one incoming TCP port for client connections. The default is 8088, but it can be changed. Normal client operation does not require an incoming client-side port. See Server and network for details.
Which accounts need access to the MSI source?
The computers or security context performing the installation must be able to read the deployment source. For service-based deployment without a logged-in user, the target domain computer accounts need read permission.
Can we deploy ASDM with GPO, MECM/SCCM or another software-distribution platform?
Yes. The client installer is an MSI file and can be distributed through the usual MSI deployment process. ASDM complements those platforms by handling its own client/server connection and central power-management configuration after installation.
What happens immediately after client installation?
The client uses the supplied server information, initiates its first server connection and retrieves its initial configuration. Our manual notes that the first provisioning process can take up to ten minutes.
Can ASDM be used in image-based client environments?
Yes. In our manual, we describe several strategies for environments in which operating-system or application data is reset from a standard image. Review that section before building ASDM into a master image.
How should we begin a larger rollout?
Use a controlled pilot group or OU first. Verify installation-source access, server connectivity, first policy delivery and the intended removal path before expanding to additional clients.
Start with a controlled pilot
Test client deployment in your environment
Use the 45-day Enterprise Trial to test server setup, MSI provisioning, client registration and central policy delivery before a wider rollout.