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. It does not replace Group Policy, MECM/SCCM or other software-distribution platforms.
Choose your path
Start small or deploy across managed Windows clients
Use the path that matches your current stage. The same ASDM installer supports a direct pilot, a central client/server setup and automated rollout through existing enterprise tools.
Standalone or pilot installation
Install ASDM directly on one Windows PC to evaluate local power-management behavior before introducing central management.
Client/server deployment
Install and configure the ASDM Server first. Then install clients so they can connect, retrieve their first settings and receive central policies.
Automated MSI provisioning
Provide the server address and TCP port through a two-line server.ini file or through MSI command-line parameters.
Existing enterprise deployment tools
Distribute the MSI with Windows Group Policy, MECM/SCCM or another established software-deployment workflow. The manual also documents options for image-based systems.
Deployment workflow
From installation source to centrally managed endpoints
The rollout is designed around a clear sequence: prepare the server, distribute the installer, establish the first connection and then manage clients 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 source file or command line.
Complete the first connection
After installation, the client connects to the server and retrieves its initial configuration. The manual notes that this can take up to ten minutes.
Assign groups and policies
Manage settings, configuration changes and later client updates centrally from the ASDM Server.
Preflight
Check network access and rollout boundaries first
A short preflight prevents the most common provisioning failures and keeps the first deployment controlled.
Server and network
- Install and configure the ASDM Server before deploying clients.
- Use a stable DNS name or server IP address.
- Allow one incoming TCP port on the server; the default is 8088 and can be changed.
- No incoming port is required on ASDM clients for normal operation.
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.
Automatic provisioning
Avoid entering server data manually on every client
ASDM supports two documented 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.
Windows Group Policy
A controlled GPO rollout in six steps
The dedicated guide documents a computer-based software installation with security filtering, staged membership and optional removal when a client falls outside the managed scope.
Prepare the share
Store the MSI and optional server.ini in a UNC-accessible source with the required read permissions.
Create a security group
Create a dedicated Active Directory security group for the computers included in the rollout.
Create and link the GPO
Link a dedicated Group Policy Object at the intended domain or OU scope.
Assign the MSI package
Add the package under Computer Configuration, Software Settings, Software Installation.
Add pilot computers
Start with a limited group of domain computers and verify share access before the first boot-triggered installation.
Validate and scale
Confirm installation and client registration, then expand group membership in controlled stages.
Detailed procedure
Use the PDF for the complete Group Policy walkthrough
The guide includes the original GPO screens, security-filtering sequence, package assignment, client membership and uninstall workflow.
Technical resources
Use the overview here, then open the source that matches your task
The landing page provides orientation. The manual, GPO guide and setup video remain the detailed working references.
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.
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.
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.
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 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. The manual notes that the first provisioning process can take up to ten minutes.
Can ASDM be used in image-based client environments?
Yes. The manual documents 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
Validate the deployment path in your own Windows environment
Use the 45-day Enterprise Trial to test server setup, MSI provisioning, client registration and central policy delivery before a wider rollout.