Platform · Modern Standby / S0 Handling

Modern Standby Driver and S0 Power-State Control

Modern Standby (S0) changes how Windows devices sleep, wake and behave with external displays. Our Auto Shutdown Manager helps IT teams manage this reality with hibernation logic, scheduled wake support and monitor DDC/CI handling for supported external displays.

Modern Standby / S0 Battery drain risk Overheating prevention Scheduled wake support External monitor DDC/CI Optional PC lock

Download 45-Day Enterprise Trial Download S0 Wake Driver Read Modern Standby FAQ

Battery drain

S0 devices can continue consuming power after the screen turns off, especially on mobile devices running on battery.

Heat risk

If a laptop remains active in a closed bag, heat and battery drain become an operational support issue.

Unreliable wake

Scheduled wake events may not behave like classic wake timers on every Modern Standby system.

External displays

External monitors can become part of the power-management problem when PCs run unattended.

Intelligent hibernation logic

For S0-capable systems, ASDM can use configured timers and policies to move from Modern Standby into hibernation where appropriate, helping reduce battery drain and heat risk.

EnviProt S0 Wake Driver

The optional add-on helps scheduled wake events created by ASDM run more reliably on many Modern Standby systems where classic wake behavior is limited.

Monitor DDC/CI management

For S0-based PCs with supported external monitors, ASDM can use DDC/CI to turn external monitors off and on, and optionally lock the PC for improved energy savings and security.

Infographic showing how ASDM handles Modern Standby S0 PCs from screen off through analysis, policy decision, hibernation, S0 Wake Driver, monitor DDC/CI management and controlled power state. — Modern Standby workflow — ASDM evaluates policy and endpoint context, then applies hibernation, scheduled wake support, monitor DDC/CI management or optional PC lock where supported and configured.

Guardrail

Modern Standby behavior depends on hardware, firmware, drivers and policy.

ASDM can help control S0 runtime, hibernation, scheduled wake and external monitor handling where the Windows device, monitor and driver environment support the required actions. Validate the behavior on the target hardware before broad rollout.

Downloadable add-on

The public download package is available as ModernStandByWakeDriver.zip. It is intended for environments that need scheduled wake events on S0-based devices.

Download Modern Standby Wake Driver

Works with ASDM Time Rules

After installation, administrators can configure ASDM Time Rules and wake planning as usual, then validate the behavior on their target hardware.

Important condition

Modern Standby behaviour depends on hardware, firmware, drivers and Windows power policy.

The S0 Wake Driver can help with scheduled wake reliability, but every device model should be tested. BIOS/UEFI settings, Windows power policy, device firmware and driver behaviour can all affect the final result.

Turn monitors off

Reduce external-display runtime during unattended periods where DDC/CI is available and supported.

Turn monitors on again

Bring supported external displays back when the endpoint needs to be available again.

Optional PC lock

For unattended runtime, the PC can optionally be locked to support energy savings and security-oriented operating routines.

Terminology note: The correct standard name is DDC/CI — Display Data Channel Command Interface. The feature depends on monitor, graphics adapter, cable and driver support.

Modern Standby challenge

How ASDM helps

S0 keeps the device active longer than expected

Use timers and policies to move from Modern Standby into hibernation where configured and supported.

Laptops drain battery or heat up with lid closed

Apply AC/DC and lid-closed behaviour so mobile devices can transition to hibernation more safely.

Scheduled wake events are unreliable on S0 systems

Use the EnviProt S0 Wake Driver add-on to improve scheduled wake behaviour where hardware and Windows conditions allow.

External monitors stay on during unattended runtime

Use DDC/CI management to turn supported external monitors off and on, and optionally lock the PC.

Simple sleep settings ignore enterprise context

Combine time rules, idle analysis, user interaction, document protection and reporting in one managed process.

Auto Shutdown Manager idle shutdown timer configuration screenshot. — ASDM idle-shutdown timer configuration, relevant for power-state policy and unattended runtime.

What is Modern Standby / S0?

Modern Standby, also called S0 low-power idle, is a Windows power model where the system can appear asleep while parts of the device remain active. This differs from classic S3 sleep and can create new operational challenges for IT.

Why can Modern Standby cause battery drain or overheating?

If the device does not fully power down, it can continue consuming power. On mobile devices, this can drain the battery or create heat when a laptop is closed and stored in a bag.

What does the EnviProt S0 Wake Driver do?

It is an add-on for ASDM environments where scheduled wake events need to work more reliably on Modern Standby systems. Behaviour still depends on the device model, firmware, drivers and Windows power policy.

Does the S0 Wake Driver work on every Modern Standby device?

Not universally. Modern Standby behaviour is highly dependent on hardware and firmware. The S0 Wake Driver can help, but each device model should be validated before broad rollout.

What is monitor DDC/CI management?

DDC/CI means Display Data Channel Command Interface. Where the monitor, graphics adapter, cable and drivers support it, ASDM can turn external monitors off and on during longer or unattended runtime.

Can ASDM lock the PC when managing external monitors?

Yes, recent ASDM releases describe an optional PC lock when using DDC/CI monitor management for S0-based PCs with external monitors.

CONTROL S0 INSTEAD OF HOPING IT BEHAVES

Test Modern Standby handling before it becomes a fleet-wide support problem.

Start with a representative pilot group of S0 devices, external monitors and common laptop models. Validate hibernation timing, scheduled wake behaviour, monitor DDC/CI support and user impact before rolling out broadly.

Download 45-Day Enterprise Trial Download S0 Wake Driver Contact Support

Platform · MECM / SCCM Integration

MECM (SCCM) Integration for Endpoint Power Management

Microsoft Configuration Manager manages deployments, updates and endpoint operations. Our Auto Shutdown Manager complements it by helping PCs be awake when maintenance or deployments need them — and by returning endpoints to a controlled power state afterwards where configured.

Microsoft Configuration Manager Deployment timing Device Collections On-demand WOL Shutdown actions Complements, not replaces

Download 45-Day Enterprise Trial View Maintenance Windows Compare with SCCM, Intune & GPO

Sleeping endpoints

A deployment window is only useful if the target PCs are actually reachable when the job starts.

Always-on workaround

Keeping PCs powered on just to be safe increases avoidable runtime, costs and operational exposure.

Script sprawl

Wake, shutdown and restart scripts can become fragile when they are not part of a managed power process.

User disruption risk

Maintenance actions should avoid interrupting active users, open work or still-running business jobs.

01

MECM deployment

Software updates, deployments or maintenance work are planned in Microsoft Configuration Manager.

02

ASDM wake timing

ASDM can synchronize wake planning with MECM deployment timing for the affected PCs.

03

Endpoint availability

Wake-on-LAN, WOL Proxies and ASDM policies help make endpoints available for the work.

04

Controlled power state

After the work is complete, endpoints can return to a configured shutdown, standby or runtime policy.

Conceptual workflow showing SCCM MECM deployment schedules synchronized into ASDM, ASDM wake planning, WOL infrastructure, target PCs awake for deployment and return to configured power policy. — Conceptual graphic — not a product screenshot. It shows MECM/SCCM schedule sync, ASDM wake planning, WOL infrastructure, target PCs awake in time and return to power policy where configured.

Schedule in MECM

Deployment timing and Device Collections remain in the Microsoft Configuration Manager workflow.

Wake with ASDM

ASDM builds the wake plan and uses configured WOL infrastructure, including WOL Proxies where required.

Return to policy

After the job, endpoints can follow the configured ASDM power policy instead of staying online by habit.

Operational guardrail: Wake reliability still depends on client state, firmware, adapter settings, WOL Proxy placement, routing and firewall rules. Validate the wake path in your own network before relying on broad rollout.

MECM plugin

Our MECM (SCCM) plugin supports Configuration Manager environments, including SCCM 2012 R2 and newer.

WOL schedule sync

ASDM can synchronize WOL timing with MECM deployment timing so PCs can be prepared before the maintenance work starts.

Device Collections

ASDM handles deployments based on Device Collections, so it fits into existing Configuration Manager workflows.

On-demand Wake-on-LAN

Wake selected endpoints when an administrator needs availability for deployment, support or operational work.

On-demand shutdown

Trigger controlled shutdown actions after work is complete, without turning endpoint power management into ad-hoc scripts.

Important positioning

ASDM complements Microsoft endpoint management. It does not replace it.

Microsoft Configuration Manager, Intune and Group Policy remain responsible for endpoint management, deployment and policy areas. ASDM focuses on the power and wake process around those tools: when PCs should be awake, when they can shut down, and how endpoint availability can be made operationally reliable.

Operational challenge

How ASDM complements MECM / SCCM

PCs are asleep before a deployment starts

Synchronize wake planning with deployment timing so endpoints can be available before the maintenance work begins.

Always-on endpoints waste runtime

Keep PCs available when needed, then return them to configured power policies after work is complete.

Wake commands are handled by scripts

Use ASDM wake infrastructure, WOL schedules, proxies and policies instead of unmanaged one-off scripts.

Admins need action from the Configuration Manager context

Support on-demand WOL and shutdown actions from the MECM console workflow.

Deployments target Device Collections

Use ASDM wake and power handling around the affected devices and collections, where configured.

Auto Shutdown Manager MECM SCCM plugin configuration showing deployment scanner settings and server integration. — MECM (SCCM) plugin configuration with deployment scanner settings.

Microsoft Configuration Manager console screenshot showing Auto Shutdown Manager plugin actions for Wake Client Now and shutdown operations. — Wake and shutdown actions directly in the Configuration Manager console context.

Microsoft Configuration Manager application deployment screenshot with deployment start time for AutoShutdownManager. — Deployment timing in Microsoft Configuration Manager.

Auto Shutdown Manager WOL Scheduler screenshot showing the transferred SCCM deployment schedule as a wake plan. — The deployment schedule transferred into the ASDM WOL Scheduler.

Does ASDM replace MECM, SCCM, Intune or Group Policy?

No. ASDM complements Microsoft endpoint-management tools. MECM, Intune and GPO remain responsible for deployment, configuration and policy areas. ASDM focuses on endpoint power state, wake readiness, controlled shutdown and reporting around those tools.

Can ASDM wake PCs for MECM deployments?

Yes, ASDM can synchronize WOL timing with MECM (SCCM) deployment timing so endpoints can be prepared before software deployments or updates run, where WOL and network conditions support it.

Can administrators trigger wake and shutdown from the MECM console?

Yes. Our MECM (SCCM) plugin supports on-demand WOL and shutdown actions directly from the Configuration Manager console.

Does the integration work with User Collections?

ASDM handles deployments based on Device Collections. Device-based targeting fits the endpoint power-management use case because wake and shutdown actions apply to physical or virtual endpoint devices.

What Microsoft Configuration Manager versions are referenced?

In our current ASDM manual, we document support for Microsoft System Center Configuration Manager / MECM (SCCM) 2012 R2 and newer. Please also validate the exact integration requirements for your MECM environment.

What happens after the deployment is done?

That depends on the configured ASDM policies. Endpoints can remain available, shut down, restart or return to another configured power state where appropriate.

MAKE DEPLOYMENTS POWER-AWARE

Use Microsoft Configuration Manager for deployment — and ASDM for endpoint availability around it.

Start with a pilot around maintenance windows, deployment timing or wake reliability. Validate how ASDM can keep endpoints available for MECM work while reducing unnecessary runtime outside those windows.

Download 45-Day Enterprise Trial View Maintenance Windows Contact Sales

Solutions · Sustainable IT Savings

Sustainable IT Energy Savings with Endpoint Power Management

Auto Shutdown Manager by EnviProt helps organizations reduce avoidable PC runtime while keeping endpoints available for users, remote work, patching, scans and maintenance. The business case is not only the power bill: it also includes less manual IT effort, fewer user interruptions and a more reliable maintenance routine.

Reduce avoidable runtime Safe idle shutdown Reliable wake Maintenance-aware Savings proof ROI validation

Download 45-Day Enterprise Trial Calculate Potential Savings

Unnecessary runtime

Idle PCs can remain on overnight, over weekends or after shared-device use, even when no operational work is planned.

User disruption risk

A power policy that ignores real users, open work, presentations or exceptions can quickly create support tickets and distrust.

Maintenance conflicts

Patch windows, scans, backups and administrative work need the right endpoints awake at the right time.

Unproven savings

Management and procurement need estimates, reports and a pilot path, not vague claims about “green IT”.

UC Berkeley case study

ENERGY STAR case-study material reports that, for a monitored desktop population, UC Berkeley saved about 80% of what would otherwise have been spent for that group with Auto Shutdown Manager.

Read the case study

MISD deployment proof

EnviProt’s ASDM material describes Mesquite Independent School District managing power and updates across 8,500 PCs on 47 campuses, including scheduled wake for updates.

See ASDM PDF

University environment

ASDM case-study material for Osnabrück University describes a deployment for more than 120 PCs and a short payback period in that specific environment.

See ASDM PDF

24/7 operating context

ASDM case-study material for Kliniken Essen-Mitte describes a hospital setting with around 800 PCs and the need to reduce consumption without disrupting clinical workflows.

See ASDM PDF

How to read “up to 80%”

Use strong savings examples as proof of potential, not as a blanket guarantee

“Up to 80%” is a useful proof point when tied to documented scenarios. It should not be presented as a guaranteed result for every customer. The responsible message is: estimate, pilot, measure and validate in your own environment.

Open ROI Calculator

Current ENERGY STAR guidance

ENERGY STAR states that enabling power management on a certified desktop computer can save an office or home office about $15 per year.

ENERGY STAR computers

Historic office benchmark

EPA office power-management material has described potential savings of $25–$75 per computer annually from using standby and hibernate features.

EPA power management PDF

Indirect effects

Lower endpoint runtime can also reduce heat output and cooling load in some environments. Treat this as a supporting benefit unless you measure it locally.

EPA power management PDF

Less manual IT effort

IT can wake, shut down, restart or return selected endpoints to policy without asking someone on-site to press a power button or check a machine.

Better after-hours maintenance

Updates, scans and scheduled maintenance can run outside working hours where wake, network and policy conditions are validated.

Fewer user interruptions

When heavy scans and patching run at better times, employees are less likely to be slowed down by background maintenance during productive work.

ASDM does not replace endpoint protection, patching, hardening or incident response. It can support operational exposure reduction by helping avoid unnecessary endpoint runtime while preserving wake-up, maintenance and remote-access availability.

See Maintenance Windows

Is this mainly about Green IT or about IT operations?

Both can matter, but the operational side must come first. If shutdown breaks patching, remote access or users' work, the savings program will fail. ASDM is positioned as controlled endpoint power management, not generic sustainability marketing.

Does ASDM guarantee a certain saving?

No. Savings depend on device count, current runtime, electricity prices, user behavior, policies, hardware and network conditions. The responsible path is to estimate, pilot, measure and scale.

What does “up to 80%” mean?

It should be read as a documented scenario-specific proof point, not a universal promise. Strong savings examples are useful, but every organization should validate runtime, wake behavior, maintenance windows and electricity assumptions in its own environment.

Can we include IT-admin time and user productivity in the business case?

Yes, but carefully. The power bill is easier to measure. Reduced manual effort, fewer local-hands requests and fewer user interruptions are operational value factors that should be described honestly and validated during a pilot where possible.

Can we still run patching and scans at night?

Yes, where configured policies and environment conditions support the schedule. The goal is to keep endpoints available for planned work and avoid leaving them powered unnecessarily afterwards.

Can remote users still access their PCs?

They can where wake, network and portal scenarios are configured and validated. ASDM is designed to combine runtime reduction with reliable wake availability instead of forcing every PC to stay online.

Does ASDM replace SCCM, MECM, Intune or GPO?

No. ASDM complements Microsoft endpoint management. It adds the operational shutdown, wake, exception-handling and reporting layer around tools that already manage policies, deployments and devices.

Shut down safely. Wake reliably. Prove the savings.

Build the energy-savings case without sacrificing endpoint availability

Start with a controlled pilot, validate wake and maintenance behavior, then use the ROI Calculator and reporting path to decide where rollout makes sense.

Download 45-Day Enterprise Trial Calculate Potential Savings

Platform · WOL Proxy & Wake-on-WAN

WOL Proxy & Wake-on-WAN for Enterprise Networks

Wake-on-LAN becomes an enterprise problem as soon as endpoints live behind routers, VLANs, branch offices and security policies. Auto Shutdown Manager by EnviProt can use WOL Proxies to wake PCs inside remote network segments without turning every router into a directed-broadcast exception.

Routed networks VLANs & subnets Local WOL Proxies Magic Packet in target segment Monitoring & self-healing Raspberry Pi option

Download 45-Day Enterprise Trial Explore Enterprise Wake-on-LAN Wake across sites & VLANs

Conceptual overview

Wake reliability becomes a managed process, not a static exception list.

This is the complete idea in one view: wake requests can come from schedules, admins, portals or management tools; ASDM selects the right WOL Proxy in the target network; the proxy sends the Magic Packet locally; the endpoint wakes and reports back. Proxy hosts can be servers, low-power PCs or Raspberry Pi-class devices, while monitoring and temporary proxy handling improve resilience.

Routed networks

Wake traffic that works locally may not cross routers or VLAN boundaries without a planned WOL approach.

Broadcast restrictions

Directed broadcasts may be unavailable, blocked or unwanted in many enterprise environments.

Remote sites

Branch offices and remote segments need local wake capability without requiring an administrator on site.

Ongoing maintenance

Networks change. Proxy candidates retire, move groups or become unavailable. Manual proxy lists age quickly.

01

ASDM Server

Sends the wake request to the selected proxy for the destination segment.

02

WOL Proxy

Runs inside the target segment and creates the local Magic Packet.

03

Local broadcast

The packet reaches the sleeping PC on the local network where Wake-on-LAN can work.

04

Endpoint wakes

The PC starts and changes status back to available in ASDM.

Analyse the network

ASDM can identify suitable proxy candidates based on network structure and endpoint availability, instead of forcing admins to build every entry by hand.

Respect admin rules

Administrators can exclude notebooks, unwanted segments or groups, prefer selected groups and keep manually selected proxies at the highest priority.

Minimize proxy count

The generator can reduce redundant subnet coverage and prefer clients that can serve multiple segments where this fits the network design.

Preview before rollout

A generated proxy list can be exported as an Excel-compatible CSV preview before changes are applied.

Assign policy groups

Selected proxy clients can be moved into a suitable WOL Proxy policy group so idle timers and time rules do not shut them down accidentally.

Maintain over time

Generation and optimization can be run daily, on a scheduler or manually, helping replace inactive, retired or defective proxy candidates.

01

Monitor active proxies

ASDM can watch configured WOL Proxies and detect when one becomes unreachable.

02

Try to wake the proxy

The server can attempt to reactivate the intended proxy so the designed topology comes back.

03

Use a temporary proxy

If another active PC exists in the same segment, ASDM can use it temporarily to trigger the local wake process.

04

Repair the topology

Scheduled generation and maintenance can replace inactive or unsuitable proxies as the network changes.

Important wording

Self-healing improves resilience. It is not a magic guarantee.

Wake reliability still depends on endpoint hardware, firmware, network policy and local segment conditions. The value of ASDM is that the wake topology can be monitored, repaired and operated centrally instead of being a static list of manual exceptions.

Low runtime footprint

Use an already-on server where available, or a low-power proxy device where that is the better operational choice.

Branch office fit

Small sites often need local wake capability without adding a full infrastructure server.

Optional, not mandatory

Raspberry Pi support is an option for suitable environments. It is not required for every WOL Proxy design.

Special topic: VLANs

One proxy VM can cover multiple VLANs when it is locally present in each one.

In large environments, administrators often ask whether every VLAN needs its own physical WOL Proxy PC. Not necessarily. In a virtualized network, one VM running the normal ASDM Client can serve multiple VLANs when the VM has a separate virtual NIC in each target VLAN and each vNIC has a valid IP address in that subnet.

The ASDM Server sends the wake request to the proxy VM. The proxy VM then sends the Magic Packet as a local Layer-2 broadcast through the vNIC that belongs to the target VLAN. Because the broadcast is created inside the correct broadcast domain, there is no routed broadcast between the server and the sleeping endpoint.

Conceptual architecture showing one ASDM Client proxy VM with multiple vNICs connected to VLAN 10, VLAN 20 and VLAN 30, sending local Wake-on-LAN Magic Packets into each VLAN. — Conceptual architecture pattern — not a product screenshot. A proxy VM can serve multiple VLANs when the hypervisor, vSwitch, 802.1Q trunking, vNICs and IP configuration are designed correctly.

Fewer physical proxy devices

Instead of placing a separate always-on proxy PC in every VLAN, a well-designed proxy VM can be attached to several VLANs.

Local broadcast per VLAN

Each vNIC makes the proxy locally present in that broadcast domain, so the Magic Packet is sent inside the correct target VLAN.

Useful for large networks

This pattern can simplify WOL Proxy planning for enterprises, universities, public-sector networks and large segmented environments.

Architecture guardrail

This is a network design pattern, not an automatic promise.

The VM must really be connected to the required VLANs with the correct vSwitch, tagged port groups, 802.1Q trunking, IP addressing, routing, firewall rules and permissions. Validate the VLAN design in the customer network before relying on it for production wake operations.

Typical gap

ASDM closes the gap

Router or firewall policy blocks simple broadcasts

Use a WOL Proxy in the target segment where directed broadcasts are not appropriate.

Proxy candidates are selected manually

Analyse the network and propose suitable proxy clients with administrator rules and exclusions.

Proxy topology becomes stale

Run generation and optimization daily, by scheduler or manually to replace inactive or unsuitable proxies.

A proxy is powered off or unreachable

Monitor active WOL Proxies, attempt wake-up and temporarily use another active PC in the same segment where possible.

Small sites do not justify a full server

Use an always-on server where available, or a low-power device such as Raspberry Pi where suitable.

Auto Shutdown Manager WOL Proxy configuration overview showing proxy setup for network segments. — WOL Proxy configuration overview.

Auto Shutdown Manager WOL Proxy remote address configuration screenshot. — Remote address and proxy-related wake configuration.

Alternative routing method

Directed broadcast instead of a WOL Proxy?

If the network and security policy permit routed broadcast forwarding, ASDM can reach remote subnets by directed broadcast without a WOL Proxy.

WOL Proxy: when broadcast forwarding is blocked or operationally undesirable.
Directed broadcast: when the network and security teams approve forwarding.
Static ARP or a manual Remote WOL Address: only for special router topologies.

Review Method B: Directed broadcast

When do we need a WOL Proxy?

You need a WOL Proxy when the target PC is in a network segment where simple local Wake-on-LAN traffic cannot reach it and directed broadcasts are not available, not allowed or not desirable.

Is Wake-on-WAN the same as sending a Magic Packet over the internet?

No. In an enterprise ASDM context, the important part is controlled wake across remote or routed network locations. A proxy in the target segment can create the local Magic Packet where the endpoint can actually receive it.

Do we need Raspberry Pi devices everywhere?

No. An always-on server can be the best WOL Proxy if it already exists in the segment. Raspberry Pi or similar low-power devices are useful options where a full server is unnecessary.

Does self-healing guarantee every wake-up?

No. Hardware, firmware, network and policy conditions still matter. ASDM can improve resilience by monitoring proxies, attempting wake-up and using temporary proxy options where possible, but every environment should be validated.

Do we need one physical WOL Proxy PC per VLAN?

Not always. In virtualized environments, one ASDM Client VM can cover multiple VLANs when it has a separate vNIC and valid local IP configuration for each target VLAN. The VM then sends the Magic Packet locally through the matching VLAN interface. This requires proper hypervisor, vSwitch, trunking, routing and firewall design and must be validated in the customer network.

Does ASDM replace SCCM, Intune or GPO?

No. ASDM complements endpoint management tools by handling the power and wake process around maintenance, remote availability and endpoint runtime control.

WAKE RELIABLY ACROSS REAL NETWORKS

Turn Wake-on-LAN from a router exception into a managed enterprise process.

Start with the networks where wake-up is unreliable today: routed VLANs, branch offices, remote sites or places where directed broadcasts are not acceptable. ASDM gives IT a controlled way to design, monitor and maintain WOL Proxy capability.

Download 45-Day Enterprise Trial Back to Enterprise Wake-on-LAN Contact Sales

Solutions · Remote PC Power Control

Remote PC Power Control for Enterprise IT

Auto Shutdown Manager by EnviProt helps IT teams reach, wake, restart and shut down managed PCs across offices, buildings, branches and remote sites. It adds the operational power-control layer around support, maintenance, inventory and urgent response workflows.

Wake remote PCs Restart systems Shut down safely Run configured actions Support maintenance windows Reduce manual site calls

Download 45-Day Enterprise Trial See How ASDM Works

No local hands

Admins should not have to call someone on-site just to press a power button, restart a PC or confirm that a device is online.

Distributed locations

Enterprise PCs may sit in offices, departments, classrooms, labs, branches or remote sites across different network segments and time zones.

Support and maintenance

Remote support, patching, scans, inventory and scripted actions need endpoints to be available at the right time, not running all day and night.

Urgent response

In operational or security-related situations, IT may need to move selected devices into a controlled power state without waiting for local staff.

Once the PC is reachable, your remote support, deployment, inventory, antivirus or maintenance tools can do their job.

04

Return to policy

After work is complete, the endpoint can return to the intended power state and the result can be logged or reported.

Auto Shutdown Manager real-time actions for wake, restart, standby, hibernate and shutdown — Real-time actions support controlled wake, restart, standby, hibernate, logoff and shutdown for selected clients or groups.

Auto Shutdown Manager context menu for wake and shutdown actions — Admins can initiate controlled actions for selected managed endpoints instead of depending on local staff.

Auto Shutdown Manager WOL Proxy support for reaching devices across networks — WOL Proxy scenarios can help reach endpoints across network boundaries where the environment supports it.

Auto Shutdown Manager client monitor for managed endpoint visibility — Central visibility helps IT see managed clients and act on endpoint availability more consistently.

Controlled runtime, not security replacement

Useful in urgent response — but not a substitute for endpoint security

ASDM does not replace EDR, antivirus, patching, hardening or incident-response tools. It can support IT operations by reducing unnecessary runtime and by helping teams move selected endpoints into a controlled power state when an operational or security-related situation requires it.

See Maintenance Windows

Helpdesk escalation

A support engineer needs to wake or restart a user PC in another office before using the existing remote-support tool.

Branch maintenance

IT prepares endpoints in a remote location for updates, scans or inventory without asking local employees to handle power state manually.

After-hours actions

Devices can be made available for planned work and returned to the configured power policy afterwards.

Lab, classroom or shared PCs

Groups of non-personal endpoints can be started, restarted or shut down according to operational need and policy.

Distributed organizations

Sites, departments and time zones become manageable from one operational approach instead of local improvisation.

Urgent offline action

When a device should no longer remain powered, IT can initiate a controlled power action without waiting for someone near the device.

Does ASDM replace VPN, RDP or remote-support tools?

No. Those tools connect to a reachable machine. ASDM focuses on the power-control layer around them: waking, restarting, shutting down and returning endpoints to policy.

Does ASDM replace SCCM, MECM, Intune or GPO?

No. ASDM complements Microsoft endpoint management by helping ensure PCs are available when needed and not left running unnecessarily afterwards.

Can IT control PCs in another building or site?

Yes, where the network, hardware and ASDM configuration support the required wake or power-control scenario. Enterprise networks should validate Wake-on-LAN, Wake-on-WAN and WOL Proxy behavior in their own environment.

Can ASDM shut down PCs after support or maintenance?

ASDM can apply configured shutdown, standby, hibernate, logoff or restart actions according to policy and current endpoint conditions. The exact action should match your operational rules.

Is emergency power-off a security feature?

It is an operational power-control capability, not a replacement for security tooling. In security-related situations it may help IT move selected devices offline faster, while endpoint protection, investigation and remediation remain separate responsibilities.

Shut down safely. Wake reliably. Prove the savings.

Give IT central control over endpoint runtime

Start with a controlled pilot: wake selected PCs, validate network behavior, test remote actions and measure the effect before scaling across sites.

Download 45-Day Enterprise Trial Contact Sales

Solutions · Multi-Site & VLANs

Wake-on-LAN Across Sites, VLANs and Branch Offices

In real networks, energy savings only help if the right PCs can still be reached. Auto Shutdown Manager by EnviProt brings shutdown, wake, maintenance and remote availability into one managed process across VLANs, routed subnets and branch locations.

Routed networks Branch offices VLANs & subnets WOL Proxies Maintenance-aware

Download 45-Day Enterprise Trial Compare Enterprise Wake-on-LAN

Wake packets meet network boundaries

A signal that works in one subnet may stop once VLANs, routers or firewall rules sit between ASDM and the target device.

Sites without local hands

IT still needs to wake machines in branch offices, labs or remote locations where nobody is standing next to the PC.

Network controls are part of the design

Routers and firewalls can block, limit or redirect the traffic that basic Wake-on-LAN tools rely on.

Availability is the real outcome

For IT, the value is not the packet itself. The value is predictable wake, shutdown, maintenance access and proof that the process works.

01 · Network map

Map the endpoint groups

Start by understanding where endpoints actually sit: which site, VLAN, subnet, building, branch or remote-access path they belong to.

02 · Wake reach

Place the wake path close enough

Use WOL Proxies, directed broadcasts or portal-based wake paths where they fit, so target networks can be reached without leaving every PC powered on.

03 · Operations

Operate and prove the process centrally

Bring wake, shutdown, maintenance windows, remote support and reporting into one controlled process instead of letting each site invent workarounds.

Important condition

Be precise about wake reliability.

No Wake-on-LAN product can bypass every BIOS, network adapter, sleep-state, switch, router or firewall condition. ASDM provides the management and wake infrastructure layer; your rollout should still validate the wake path before it becomes operationally important.

View Wake-on-LAN details

Expand only when wake behavior, user impact, maintenance availability and policy return are predictable in your own environment.

Respect routed network design

Routing, VLANs, firewall policy and endpoint configuration remain the foundation. ASDM works with those realities instead of pretending they do not exist.

Complement management tools

SCCM/MECM, Intune, GPO and scripts can stay part of endpoint operations. ASDM adds the dedicated wake, shutdown and runtime-control layer around them.

Enable controlled remote wake

WOL Portals and wake infrastructure can help make distributed endpoints reachable where policy, hardware and network conditions allow.

View WOL Portals

Can Wake-on-LAN work across VLANs and routed networks?

Yes, but it depends on network design, endpoint hardware, firmware, adapter settings and security controls. ASDM provides enterprise wake and power-management capabilities; the actual wake path should still be validated before broad rollout.

Why are WOL Proxies useful?

A WOL Proxy or local wake component can bring wake capability closer to the target subnet or branch site. That reduces dependence on direct broadcast behavior from one central location.

Does this replace SCCM, MECM, Intune or GPO?

No. ASDM complements these tools. They remain important for endpoint management, policy, deployment and compliance. ASDM adds the dedicated wake, shutdown, runtime and reporting layer around them.

Can remote users wake their assigned PCs?

Usually through WOL Portals or related remote-wake scenarios, if the organization allows and validates that workflow. Multi-site wake infrastructure can support it, but portal permissions and network behavior need careful planning.

Should we roll this out everywhere at once?

No. Start with a site or subnet where the network path is understood, validate wake behavior, and then expand by group, site or organizational unit.

Shut down safely. Wake reliably. Prove the savings.

Turn distributed endpoint power control into a repeatable process

Start with a controlled pilot across your real VLANs, sites and branches. Then connect wake reliability with safe shutdown, maintenance windows and remote access workflows.

Download 45-Day Enterprise Trial Contact Sales

Solutions · Maintenance windows

Maintenance Windows for Endpoint Power Management

Auto Shutdown Manager by EnviProt helps IT teams keep endpoints available for patching, scans and admin work, then return them safely to policy afterwards. Where SCCM/MECM maintenance plans are used, ASDM can synchronize scheduled maintenance windows into the power-management workflow so the right devices are awake, protected during the window and shut down again when the work is done.

Scheduled wake SCCM / MECM schedule sync Wake-on-LAN User protection Safe shutdown after work Savings proof

Download 45-Day Enterprise Trial See How ASDM Works

Powered-off endpoints

Night or weekend maintenance can miss PCs that are already shut down, asleep or unreachable across network boundaries.

Wake reliability

Wake-on-LAN becomes more complex across VLANs, subnets and remote sites. A simple magic packet is often not enough in enterprise networks.

User disruption

Automation must not shut down a PC during active work, presentations, remote sessions, backups, scans or other protected tasks.

Always-on fallback

Leaving endpoints powered all night can make maintenance easier, but it wastes energy and creates unnecessary runtime.

01

Sync the plan

Import or synchronize scheduled maintenance windows from SCCM/MECM where configured, or define ASDM maintenance plans directly.

02

Target devices

Apply the window to managed clients, departments, sites or collections instead of treating every PC the same way.

03

Wake before work

Use scheduled wake-up and Wake-on-LAN options so endpoints are available before patching, inventory, scans or support actions start.

04

Keep devices available

SCCM/MECM, Intune, GPO, scripts, antivirus, inventory or backup tools can do their job while the PC is intentionally online.

05

Respect exceptions

Warnings, time rules, idle checks and maintenance controls help avoid false shutdowns while users or protected tasks are still active.

06

Shut down and report

After the window, endpoints can return to a configured power state and reporting can document availability and savings results.

When SCCM / MECM is the source plan

IT can keep defining deployment or maintenance timing in Microsoft tooling. Where the integration is configured, ASDM can synchronize those scheduled windows and turn them into a wake-and-shutdown process around the actual deployment work.

What ASDM coordinates around it

Wake timing, endpoint availability, protected exceptions, controlled post-window shutdown and reporting are handled centrally, so teams do not need to rely on always-on fallback or scattered scripts.

Maintenance Windows workflow for endpoint power management — Workflow overview: synchronize or define the maintenance plan, target the right devices, wake them before the window, keep them available, run maintenance safely, shut down afterwards and report the result.

Auto Shutdown Manager Wake-on-LAN scheduler for planned maintenance windows — WOL Scheduler helps wake managed PCs before planned patching, scans and support work.

Auto Shutdown Manager real-time actions for wake, restart and shutdown — Real-time actions support controlled wake-up, restart, standby, hibernate and shutdown for selected clients or groups.

Auto Shutdown Manager savings report after controlled endpoint runtime — Reporting helps show whether controlled runtime and shutdown policies are producing measurable results.

Requirement

Align with SCCM/MECM schedules

Keep endpoint availability aligned with the planned maintenance window.

Known issue with standard tools

SCCM/MECM can schedule deployments and maintenance windows, but endpoint power state remains a separate operational dependency: devices may be off, asleep, unreachable, or left running after the window.

How ASDM closes the gap

ASDM synchronizes configured SCCM/MECM maintenance windows into the power-management workflow, wakes targeted endpoints before the window, keeps them available during maintenance, and returns them to policy afterwards.

Requirement

Run updates at night

Use off-hours for patching without creating uncontrolled overnight runtime.

Known issue with standard tools

Off-hours maintenance often leads to an always-on fallback because basic policies and scripts do not reliably prepare, protect, and shut down only the right endpoints after the work is complete.

How ASDM closes the gap

ASDM schedules wake-up before the window, keeps endpoints available while deployment tools run, and powers them down again after completion where policy, hardware, and current conditions allow.

Requirement

Reach PCs across sites

Keep distributed devices reachable across real enterprise network conditions.

Known issue with standard tools

Wake-on-LAN across VLANs, subnets, routed networks, and remote sites is fragile. Basic magic packets often stop at network boundaries or require custom handling.

How ASDM closes the gap

ASDM provides enterprise wake patterns with central scheduling and WOL Proxy or Wake-on-WAN scenarios where supported, reducing manual wake work and script sprawl.

Requirement

Avoid user disruption

Keep maintenance practical without interrupting real work or protected tasks.

Known issue with standard tools

Basic shutdown rules or scripts may not know whether a user, backup, scan, presentation, or remote session is still active. False shutdowns create helpdesk friction.

How ASDM closes the gap

ASDM applies policies, idle checks, warnings, exclusions, and maintenance controls before power actions, making automation more predictable and less disruptive.

Requirement

Reduce always-on runtime

Avoid leaving endpoints online longer than the maintenance window requires.

Known issue with standard tools

If maintenance success depends on “keep everything on,” energy cost and avoidable runtime accumulate, and savings are difficult to prove to management or procurement.

How ASDM closes the gap

ASDM returns endpoints to a controlled power state, records availability and savings evidence, and supports ROI reporting for validating the business case.

Groups and scopes

Apply synchronized or manually defined schedules by groups, sites, departments or maintenance collections so each scenario can use the right policy.

Scheduled wake

Wake endpoints before the imported or defined window and combine scheduled wake with WOL infrastructure where conditions allow.

Maintenance protection

Use time rules, maintenance mode and activity checks to avoid interfering with real work or protected operations.

Post-window shutdown

Return endpoints to shutdown, standby or hibernation instead of leaving them online after the update window.

Scripts and remote actions

Run configured scripts or actions before shutdown or after wake-up where policy allows, and centrally wake, restart, log off, hibernate, standby or shut down selected clients or groups.

Reporting

Use reports and savings views to validate runtime reduction and support the business case for controlled endpoint energy management.

Pilot

Select a controlled group

Choose a department, lab, site or test collection where maintenance behavior can be measured safely.

Validate

Test wake and shutdown

Verify Wake-on-LAN, user warnings, exclusion rules and post-maintenance shutdown in your network and hardware environment.

Scale

Expand by policy

Roll out to more groups once availability, disruption protection and reporting meet your operational requirements.

Does ASDM replace SCCM, MECM or Intune?

No. Auto Shutdown Manager complements Microsoft endpoint management. SCCM, MECM and Intune can deploy updates and policies; ASDM focuses on the wake, shutdown, exception handling and reporting workflow around endpoint availability. Where configured, ASDM can also synchronize scheduled maintenance windows from SCCM/MECM into that workflow.

Can ASDM wake PCs before a patch window?

Yes, ASDM supports scheduled wake and Wake-on-LAN scenarios. Success depends on hardware, firmware, network configuration and routing conditions, so the setup should be validated in the target environment.

What happens if a user is still working?

Policies can include warnings, cancellation behavior, idle checks, time rules and exclusions. The intention is controlled power management, not blind forced shutdown.

Can PCs shut down automatically after maintenance?

Yes, ASDM can return endpoints to a configured power state after the maintenance period when policy and current conditions allow it.

Is this useful if we already use GPO or scripts?

Yes. GPO and scripts can solve parts of power management. ASDM is intended to reduce script sprawl and provide a central, repeatable process for wake, protection, shutdown and reporting.

Shut down safely. Wake reliably. Prove the savings.

Test maintenance-window power control in your own environment

Use the 45-day Enterprise Trial to validate scheduled wake, user protection, post-maintenance shutdown and reporting with your hardware, network and deployment tools.

Download 45-Day Enterprise Trial Calculate ROI Explore Central Management

Why Auto Shutdown Manager · Endpoint power management workflow

How Auto Shutdown Manager Works

Auto Shutdown Manager by EnviProt is not just a shutdown command. It is a managed endpoint power workflow: detect real idle, protect users and maintenance tasks, shut down safely, wake endpoints reliably and prove the savings.

Detect real idle Protect work Apply central policy Shut down safely Wake reliably Report savings

Download 45-Day Enterprise Trial Calculate ROI

01

Detect real idle

Idle can be defined with more than keyboard or mouse inactivity: workload, applications, services, network traffic, sessions and other signals can be part of the decision.

02

Protect users and tasks

Warnings, time rules, maintenance mode and pre-shutdown actions help prevent automation from interrupting active work, presentations, scans, backups or IT operations.

03

Apply central policy

Administrators can manage settings, groups, schedules and remote actions centrally instead of maintaining disconnected scripts or desk-by-desk settings.

04

Shut down safely

Depending on policy and environment, endpoints can be shut down, restarted, put into standby or hibernated when they are no longer needed.

05

Wake reliably

Availability is restored through timer wake-up, Wake-on-LAN, WOL Scheduler, WOL Proxy and Wake-on-WAN scenarios where hardware and network conditions allow.

06

Prove the savings

Reports and savings views help turn power management into a measurable business case instead of a hidden background task.

Auto Shutdown Manager central management workflow overview — Central management connects policies, groups, remote actions, maintenance processes and reporting into one operating model.

Auto Shutdown Manager real-time power actions for managed clients — Real-time actions support controlled wake-up, restart, logoff, hibernate, standby and shutdown for selected clients or groups.

Auto Shutdown Manager Wake-on-LAN scheduler — WOL Scheduler helps make endpoints available again for planned work, updates, support and maintenance windows.

Auto Shutdown Manager savings report — Savings reporting helps validate the business case instead of assuming that power policies are producing results.

User activity

Mouse and keyboard activity, active sessions and visible warning/cancel paths help distinguish idle machines from active users.

System workload

CPU, hard-disk utilization, scheduled tasks and sound activity can be considered before a shutdown decision is made.

Applications and services

Selected applications, processes, services and drivers can prevent or prepare shutdown where business workflows require it.

Network context

Network traffic, terminal sessions, printer queues and monitored TCP/IP devices can be part of the idle decision.

Warnings and cancellation

Users can be warned before shutdown, and organizations can define when cancellation should be allowed.

Time rules and core hours

Policies can change by time, day, business hours, night, weekend or maintenance window.

Pre-shutdown actions

Applications or batch files can run before shutdown, documents can be saved and services or drivers can be handled as part of the process.

Maintenance Mode

Maintenance can keep endpoints available while work is still running, instead of fighting a local idle rule.

Groups and exceptions

Different rooms, departments, OUs, user groups or device groups can use different policies instead of one global timeout.

Operational confidence

The goal is not aggressive shutdown. The goal is safe shutdown that IT, users and management can trust.

Timer and scheduled wake

Endpoints or groups can be woken for known schedules, support windows or planned maintenance tasks.

Wake-on-LAN infrastructure

ASDM supports Wake-on-LAN approaches for local networks and routed environments, including WOL Proxy scenarios where required.

Remote availability

Wake-on-WAN concepts and WOL Portals can help remote users or helpdesk teams wake assigned PCs without keeping everything on 24/7.

Important: Wake behavior depends on hardware, firmware, operating-system power state and network configuration. ASDM provides the workflow and tooling; wake behavior should be validated in your own environment.

Settings and groups

Assign power policies to groups instead of maintaining separate local configurations.

Remote actions

Wake, restart, shutdown, hibernate, standby or log off selected clients or groups when the operation requires it.

Client overview

Monitor client status, events and operational conditions to understand what happens across the environment.

What Microsoft tools already do well

Baseline policies and endpoint configuration.
Software deployment, inventory and update workflows.
Device and compliance management.

Where ASDM adds a dedicated workflow

Multi-signal idle detection and safe shutdown decisions.
Wake infrastructure, WOL Scheduler, WOL Proxy and Wake-on-WAN scenarios.
Maintenance-window availability and savings reporting.

Compare ASDM with SCCM, Intune and GPO Compare ASDM with custom scripts

Central savings report

Use reported client and server data to support the energy and cost-saving business case.

Operational events

Events and statistics help IT understand shutdown, wake and client behavior instead of guessing.

ROI validation

Estimate potential savings, validate the result in your environment and use the ROI Calculator as part of the evaluation path.

1

Select a pilot group

Choose a department, lab, classroom, office area or site with measurable runtime and clear availability needs.

2

Model idle and exceptions

Define signals, business hours, protected tasks, user warnings and maintenance windows.

3

Validate wake-up

Test WOL behavior, scheduling, proxy scenarios and remote-access needs where they apply.

4

Measure and expand

Use reports and the ROI Calculator to decide how to scale the workflow across groups and sites.

Does Auto Shutdown Manager replace GPO, SCCM/MECM or Intune?

No. ASDM complements Microsoft endpoint management. Windows policies, GPO, SCCM/MECM and Intune remain important for endpoint configuration, deployment and management. ASDM adds the dedicated shutdown, wake, availability and savings-reporting workflow.

How does ASDM know whether a PC is really idle?

ASDM can consider multiple signals such as user activity, CPU and disk load, selected applications, processes, services, network traffic, sessions, scheduled tasks and other environment-specific conditions.

Can users stop a shutdown?

Depending on policy, users can be warned before shutdown and may be allowed to cancel. Administrators can also use time rules, exceptions and maintenance controls to prevent the wrong shutdown at the wrong time.

Can ASDM wake PCs across VLANs or remote sites?

ASDM supports enterprise Wake-on-LAN approaches such as scheduled wake-up, WOL Proxy scenarios and Wake-on-WAN concepts. Actual wake behavior depends on hardware, firmware, power state and network configuration, so it should be validated in your environment.

How are savings proven?

ASDM provides reporting and savings views that help estimate and validate the business case. For planning, use the ROI Calculator and then compare the estimate with operational reporting from your environment.

Evaluate the complete workflow

Shut down safely. Wake reliably. Prove the savings.

Use Auto Shutdown Manager to test the full endpoint power-management workflow: safe shutdown, reliable wake, maintenance availability, WOL Portals, central management and reporting.

Download 45-Day Enterprise Trial Calculate ROI Explore Central Management

Why Auto Shutdown Manager · Vs. Custom Scripts

Auto Shutdown Manager (ASDM) vs. Custom Scripts for Endpoint Power Management

Custom scripts can solve narrow endpoint power tasks. Auto Shutdown Manager by EnviProt is different: it gives IT a ready-made operating layer for safe shutdown, reliable wake-up, remote availability, maintenance windows and savings proof — without turning endpoint power management into a fragile script stack.

Script stack risk Safe idle shutdown Wake-on-LAN operations Maintenance windows Central reporting Ready-made process

Calculate ROI Download 45-Day Enterprise Trial View Feature List

Fair comparison

Scripts are useful. They are just a weak foundation for a full power-management process.

PowerShell, batch files, scheduled tasks and command-line workflows are valuable tools in an administrator’s toolbox. They can run a defined action at a defined time. The problem appears when the task becomes a daily enterprise process: deciding when a PC may safely shut down, waking it again across real networks, protecting users and maintenance windows, and proving the result.

Where scripts can make sense

One-off administrative tasks.
Small local automations with clear ownership.
Integration hooks around existing tools.
Simple scheduled operations where risk is low.

Where scripts start to break down

Different sites, VLANs, hardware states and user patterns.
Exceptions for business hours, maintenance, backups and active work.
Reliable wake-up for remote users, support and patch windows.
Reporting that proves energy, cost and CO₂ savings.

1. Ownership

A custom script often depends on the person who wrote it. Auto Shutdown Manager provides a documented product workflow with central configuration, policies and operational visibility.

2. Safety

Power actions need context. ASDM is designed around controlled idle detection, user-aware shutdown decisions, business-time rules and maintenance availability.

3. Availability

Saving power is only credible if PCs can return when needed. ASDM connects shutdown with scheduled wake-up, Enterprise Wake-on-LAN, WOL Proxies and self-hosted WOL Portals.

4. Scale

A small script may be manageable for a few PCs. Enterprise environments need groups, policies, rollout control, update management and repeatable administration.

5. Proof

Management needs more than “the script ran”. ASDM supports estimation, pilot validation and reporting for runtime, energy, cost and CO₂ impact.

6. Integration

ASDM does not ban scripts. It can coexist with endpoint-management workflows, scheduled tasks, command-line operations and Microsoft environments where that makes operational sense.

Safe idle shutdown

Script stack: Often starts with timers, scheduled tasks or a shutdown command. Exceptions must be added and maintained manually.

ASDM layer: Provides controlled shutdown policies, idle rules and user-aware behavior as part of the product workflow.

User and workload protection

Script stack: Needs custom checks for active users, open work, business hours, important processes and maintenance situations.

ASDM layer: Focuses on avoiding disruptive shutdowns while still reducing unnecessary runtime.

Wake-up after shutdown

Script stack: Wake-on-LAN often becomes a separate project involving subnets, router behavior, client settings and troubleshooting.

ASDM layer: Connects scheduled wake-up, manual wake, WOL Proxy routing and client-side WOL reliability settings into one operational flow.

Remote users and helpdesk

Script stack: A shutdown script does not solve how authorized users wake assigned office PCs later.

ASDM layer: Self-hosted WOL Portals can provide controlled wake-up paths while IT keeps authentication, assignment and routing under control.

Maintenance windows

Script stack: Requires coordination between shutdown logic, wake timing, patch windows, support work and exceptions.

ASDM layer: Helps keep clients available for planned administration and return them to power-saving behavior afterwards.

Reporting and savings proof

Script stack: Logs usually prove execution, not business value. Energy and cost reporting must be built separately.

ASDM layer: Supports ROI estimation, pilot validation and operational reporting for energy, cost and CO₂ impact.

01

Build

Write shutdown, wake, exception and logging logic for the first environment.

02

Maintain

Keep scripts compatible with OS changes, endpoint tools, permissions and operational requirements.

03

Support

Investigate failed shutdowns, failed wake-ups, user complaints and edge cases across locations.

04

Prove

Collect enough data to justify the project to IT leadership, finance, sustainability or procurement.

Keep useful integrations

Scripts can still support local tasks, exports, scheduled jobs or integration around your endpoint-management platform.

Move risky logic into ASDM

Shutdown safety, wake reliability, user-facing wake-up and savings proof should not depend on undocumented script chains.

Validate before scaling

Use the ROI Calculator and 45-day Enterprise Trial to test behavior, wake reliability and reporting in your own environment.

1

Inventory

List current scripts, scheduled tasks, owners, permissions, logs and known failure cases.

2

Prioritize

Identify where failed shutdowns, failed wake-ups or missing proof create the most operational risk.

3

Pilot

Test ASDM with a controlled group, site, lab or department before rollout.

4

Decide

Keep low-risk scripts where useful. Replace brittle power/wake workflows where a managed product is safer.

Does ASDM replace every custom script?

No. Scripts can remain useful for integration and local automation. ASDM focuses on the operational power-management workflow: safe shutdown, reliable wake-up, user protection, maintenance availability and reporting.

Why not solve shutdown with PowerShell and Scheduled Tasks?

That can work for a narrow case. The challenge is not the shutdown command itself; it is the surrounding logic: when shutdown is safe, when the PC must wake again, how exceptions are handled, and how results are reported.

Can ASDM work alongside existing endpoint-management tools?

Yes. ASDM is designed as a dedicated power and wake layer that can complement existing Microsoft endpoint management, scheduled operations and administrative workflows.

Is this a security product?

No. Power management is not a security product. But unnecessary runtime can mean unnecessary exposure. ASDM can support operational exposure reduction by helping avoid unnecessary runtime while endpoint protection, patching and hardening remain separate responsibilities.

How should we evaluate ASDM against our current scripts?

Start with a small pilot. Validate shutdown safety, Wake-on-LAN reliability, maintenance windows, user impact and reporting in your own environment before scaling.

Keep the useful scripts. Replace the fragile power-management stack.

Evaluate Auto Shutdown Manager where custom scripts usually become expensive to maintain: safe shutdown, reliable wake, remote availability, maintenance windows and proof of savings.

Calculate ROI Download 45-Day Enterprise Trial Contact Sales

Why Auto Shutdown Manager · Enterprise Wake-on-LAN

Enterprise Wake-on-LAN vs. Basic Wake-on-LAN Tools

Basic Wake-on-LAN tools can be useful on a simple local network. Auto Shutdown Manager by EnviProt is different: it connects wake-up with managed endpoint power control, routed networks, WOL Proxy and Wake-on-WAN scenarios, WOL Portals, scheduled wake-up, File Scanner XML jobs and remote availability.

Routed networks VLANs and subnets WOL Proxy WOL Portals Scheduled wake-up Wake-on-WAN XML jobs Remote availability

Download 45-Day Enterprise Trial View WOL Portals

Where basic WOL tools can fit

Small local networks with predictable broadcast behavior.
Manual wake-up of a known device by an administrator.
Occasional troubleshooting or lab use.
Simple environments where clients stay reachable and network routing is not a concern.

Where enterprise Wake-on-LAN is different

Wake-up across VLANs, routed subnets and remote sites.
WOL Proxy, directed-broadcast, Wake-on-WAN or special-case remote-address approaches where the network requires them.
User-facing wake-up through controlled WOL Portals.
Scheduled, portal-driven or XML job based wake-up for maintenance, patching, support and reliable availability after shutdown.

Enterprise Wake-on-LAN architecture showing schedules, File Scanner XML jobs, ASDM Console or CLI, SCCM or MECM, WOL Portal and Remote Work triggers routed through the ASDM Server to managed endpoints — One managed wake workflow: schedules, XML jobs, SCCM/MECM, portals and remote-work requests are routed through ASDM instead of being handled as separate ad-hoc wake attempts.

Route wake-ups through the right site path

WOL Proxy routing helps IT generate the wake packet inside the target network segment where local broadcast is needed.

Auto Shutdown Manager WOL Proxy configuration screen for routing wake-up requests into remote network segments

Support routed broadcast where policy allows it

Directed broadcast remains a network-controlled path. ASDM can fit that path where routers and security policy allow routed broadcast forwarding.

Firewall configuration example for routed Wake-on-LAN traffic

Handle special router cases centrally

Remote WOL Address / Port is available for special router topologies, such as static-ARP or broadcast-target cases, instead of leaving every exception in separate scripts.

Auto Shutdown Manager remote WOL address and port configuration for special routed wake-up scenarios

Reduce client-side wake failures

Wake reliability is not only routing. ASDM helps keep client-side wake settings part of policy instead of repeated per-PC troubleshooting.

Auto Shutdown Manager policy option to fix Wake-on-LAN settings on clients

Less manual scripting

Wake-up becomes part of a managed workflow instead of scattered tools, one-off scripts and remembered router exceptions.

More reliable operations

Routing choices, client readiness and policy control are handled together, which reduces avoidable failure points.

Safer administration

IT can keep endpoint availability without leaving machines powered on simply because wake-up is unreliable.

Professional handover

Admins can explain the wake path, the exception path and the support model without relying on tribal knowledge.

1. Shutdown first

Power savings begin with safely shutting down idle or unused PCs. Wake-up only has value if the device can be brought back when users, admins or maintenance tasks need it.

2. Route the wake request

Enterprise networks often block or limit simple broadcast behavior. ASDM supports WOL Proxy routing, directed broadcast where the network allows it, and Remote WOL Address / Port settings as a special-case override for router topologies that need a static-ARP or broadcast-target path.

3. Keep control local

Self-hosted WOL Portals can let authorized users or helpdesk teams wake assigned PCs without keeping those systems running all day.

4. Align with maintenance

Scheduled, immediate or File Scanner XML job based wake-up helps keep endpoints available for support, patch windows and planned administration without abandoning power-saving behavior.

5. Complement existing management tools

ASDM is not positioned as a replacement for Microsoft Configuration Manager or similar endpoint-management platforms. It can complement them with a dedicated power and wake layer around maintenance, support and availability workflows.

6. Reduce failure points

Client readiness matters as much as network routing. Wake settings, hardware behavior and power states need to be part of the operating model, not left to ad-hoc tools.

7. Prove the result

Wake reliability protects the energy-saving case. If PCs cannot return when needed, the organization will fall back to leaving them on.

Wake across VLANs and routed subnets

Basic WOL tools: Often depend on local broadcast behavior or manual network exceptions.

ASDM layer: Supports enterprise WOL routing approaches so wake-up can fit segmented endpoint networks.

WOL Proxy, directed broadcast and special routing cases

Basic WOL tools: Usually require separate scripts, router-specific exceptions or manual site-by-site configuration.

ASDM layer: Lets IT use WOL Proxy routing, directed broadcast where the network allows it, or Remote WOL Address / Port as a special-case override where the environment requires it.

Remote users and helpdesk wake-up

Basic WOL tools: Give admins a wake command, but do not solve controlled user self-service or remote-work wake-on-demand.

ASDM layer: WOL Portals can let authorized users wake assigned PCs while IT keeps authentication, assignment and ASDM wake routing under control.

Scheduled and automated wake for operations

Basic WOL tools: Often handle manual wake-up, but not the wider maintenance schedule, external job input or automation workflow.

ASDM layer: Supports scheduled, immediate and File Scanner XML job based wake-up as part of central endpoint power-state control.

Existing management-tool fit

Basic WOL tools: May sit beside Microsoft Configuration Manager or other endpoint tools, but usually remain separate one-off wake utilities.

ASDM layer: Complements SCCM/MCM and similar tools with a dedicated power and wake layer instead of replacing endpoint management.

Client readiness and wake reliability

Basic WOL tools: Can send a packet, but do not make firmware, NIC settings, power states or network paths reliable by themselves.

ASDM layer: Keeps client readiness, wake settings and operational validation part of the managed endpoint power process.

Power saving without losing availability

Basic WOL tools: Do not decide when a PC should safely shut down or how to avoid disrupting users.

ASDM layer: Combines shutdown policies, wake reliability and maintenance availability in one power-management workflow.

Operational proof

Basic WOL tools: Usually prove only that a wake command was sent.

ASDM layer: Helps connect power-state control with reporting, ROI validation and a measurable energy-management process.

01

Branch offices

Wake endpoints across segmented locations without treating every router or site as a separate custom project.

02

Patch windows

Wake clients for planned administration, updates and support work, then return to power-saving behavior afterwards.

03

Remote work

Let authorized users wake assigned office PCs on demand instead of keeping those PCs running 24/7.

04

Shared workstations

Keep labs, classrooms and shared endpoints power-managed while still available for schedules and support.

1

Map the topology

List the subnets, VLANs, sites and user groups where wake-up needs to work reliably.

2

Choose the route

Decide where local broadcast, directed broadcast, WOL Proxy routing, Wake-on-WAN or special-case Remote WOL Address / Port settings fit the environment.

3

Protect availability

Connect wake-up with safe shutdown policies, maintenance windows and user or helpdesk access paths.

4

Validate in a pilot

Use a controlled site, lab or department to verify wake reliability before scaling the workflow.

Reduce avoidable runtime

Power-managed endpoints do not need to stay on simply because wake-up is unreliable.

Preserve access

WOL Portals and central wake operations help restore availability when the endpoint is needed.

Keep responsibilities clear

ASDM supports operational exposure reduction, but it does not replace endpoint security tools.

Why are basic Wake-on-LAN tools not enough in many enterprise networks?

Basic tools can work well on a simple LAN. Enterprise networks often include routed subnets, VLANs, branch offices and remote access requirements. Wake-up then needs routing, policy, user control and operational validation.

Does ASDM require every router to be reconfigured?

No single approach fits every network. Auto Shutdown Manager supports practical enterprise WOL approaches such as WOL Proxy scenarios, directed broadcast where the network and security policy allow routed broadcast forwarding, and Remote WOL Address / Port as a special-case override where the environment requires it.

Does ASDM replace SCCM/MCM or Microsoft Configuration Manager?

No. Microsoft Configuration Manager has its own Wake-on-LAN functions for deployment and maintenance scenarios. ASDM should be used as a complementary power and wake layer where endpoint availability, shutdown policy, portals, routing and proof need to be managed together.

Can ASDM create wake jobs from files or external workflows?

Yes. The Auto Shutdown Manager File Scanner can process XML job files, so wake-up can be connected to structured operational workflows instead of only manual button clicks.

Is Wake-on-LAN guaranteed to work in every power state?

No. Wake success depends on compatible endpoint hardware, firmware and NIC settings, the current power state and a working network path. Enterprise Wake-on-LAN reduces operational uncertainty, but it does not remove those technical dependencies.

Can users wake their own office PCs?

Yes, WOL Portals can provide controlled self-service wake-up for assigned PCs. IT keeps control over access, assignment and routing instead of leaving PCs running all day.

How does Wake-on-LAN connect to energy savings?

Energy savings depend on being able to shut down safely without losing availability. Enterprise Wake-on-LAN gives IT a path to wake endpoints again for users, support and maintenance after power-saving shutdown.

Should we replace every existing WOL tool?

Not necessarily. Keep simple tools where they are low-risk and useful. Use ASDM where wake-up is part of a managed endpoint power process with routed networks, remote users, maintenance windows and savings proof.

Stop choosing between power savings and endpoint availability.

Use Auto Shutdown Manager to connect safe shutdown, Enterprise Wake-on-LAN, WOL Proxy and Wake-on-WAN routing, WOL Portals, automation, maintenance availability and reporting in one managed endpoint power workflow.

Download 45-Day Enterprise Trial View WOL Portals Explore Enterprise Wake-on-LAN

Why ASDM · Vs. Native Tools

ASDM vs. SCCM, Intune and GPO for Endpoint Power Management

Windows, Group Policy, Microsoft Configuration Manager and Intune are essential endpoint-management tools. Auto Shutdown Manager does not replace them. It adds the dedicated power and wake layer for organizations that need safe shutdown, reliable Wake-on-LAN, remote user wake-up, maintenance-window availability, measurable savings and less avoidable endpoint runtime.

Complements Microsoft endpoint management Safe idle shutdown Enterprise Wake-on-LAN WOL Portals ROI proof Less avoidable runtime

Calculate ROI Download 45-Day Trial View Feature List

What native tools are good at

Applying baseline policies and settings.
Managing device configuration and compliance.
Running required deployments, updates and task sequences.
Supporting standard endpoint-management operations.

Where ASDM adds value

Deciding when a PC may shut down safely.
Waking PCs reliably for maintenance, support and remote work.
Giving users controlled self-service wake-up paths.
Estimating, piloting and proving energy, cost and CO₂ savings.
Reducing avoidable runtime without losing planned availability.

Infographic showing Group Policy, Intune, SCCM or MECM and scripts feeding into daily admin pain points such as active users, running jobs, maintenance windows, sleeping PCs, remote sites, failed wake-up and proof requirements, then Auto Shutdown Manager closing the gap as a dedicated power and wake operating layer — Keep Microsoft endpoint tools. Add the dedicated power and wake operating layer that turns policies, deployments and scripts into a controlled daily workflow.

Windows power settings / GPO

Policy exists — but runtime decisions still happen elsewhere

Operational friction

Baseline settings do not know whether work is still active, whether an exception is justified, or whether runtime savings are actually being achieved.

ASDM answer

Auto Shutdown Manager adds safe idle detection, user-aware power workflows and central runtime, savings and CO₂ reporting.

SCCM / MECM / Microsoft Configuration Manager

Deployment wake is not the same as daily availability

Operational friction

Maintenance windows need endpoints awake at the right time, while shutdown, wake, support and remote access must not conflict.

ASDM answer

ASDM connects shutdown reduction with scheduled wake, maintenance readiness, WOL Portals, remote availability and proof.

Microsoft Intune

Configuration delivery is not a local wake infrastructure

Operational friction

Cloud policy does not wake sleeping PCs across real network paths, remote sites and routed networks on its own.

ASDM answer

ASDM provides a local and self-hosted wake layer with routed Wake-on-LAN workflows and assigned-PC wake-up paths.

Custom scripts and scheduled tasks

Scripts solve exceptions — then become the operating model

Operational friction

Scripts depend on the people who wrote them. Routing exceptions, retry behavior, handover and reporting stay fragile.

ASDM answer

ASDM turns these exceptions into a supported product workflow with central policies, retries, reporting and less script sprawl.

1

Detect

Is the endpoint really idle, or is work still happening?

2

Protect

Avoid interrupting users, business hours, jobs and maintenance.

3

Shut down

Apply controlled shutdown, sleep, hibernate, restart or logoff policies.

4

Wake

Bring PCs back for updates, support, remote access or scheduled work.

5

Prove

Report runtime, savings, cost and CO₂ impact.

Baseline power policy

Native-tool fit: Strong fit for standard settings and policy distribution.

ASDM added layer: Turns policy into a managed runtime process with decisions, exceptions and reporting.

Safe idle shutdown

Native-tool fit: Basic timers or custom logic may cover simple cases.

ASDM added layer: Adds controlled idle detection, rules and user protection before shutdown.

Maintenance-window availability

Native-tool fit: Supported in some endpoint-management scenarios.

ASDM added layer: Connects reduced runtime with scheduled wake and maintenance readiness.

Wake-on-LAN across real networks

Native-tool fit: Depends heavily on network design and the deployment scenario.

ASDM added layer: Adds enterprise wake concepts for routed networks, sites and daily operations.

Remote users waking assigned PCs

Native-tool fit: Not the main focus of native policy tools.

ASDM added layer: Self-hosted WOL Portals can provide controlled user wake-up paths.

Energy, cost and CO₂ proof

Native-tool fit: Usually not the main focus of configuration tools or scripts.

ASDM added layer: Supports estimation, pilot validation and reporting for management decisions.

Avoidable runtime and exposure window

Native-tool fit: Depends on policy coverage, scripts and operational discipline.

ASDM added layer: Reduces unnecessary runtime while preserving wake-up and maintenance availability. ASDM does not replace endpoint security tools.

Patch and maintenance windows

Endpoint management tasks need PCs to be available at the right time. ASDM helps reduce unnecessary runtime while waking machines when planned work needs them.

Explore remote shutdown and wake-up →

Remote access without 24/7 runtime

Remote access tools solve the session. They do not solve the availability problem before the session starts. WOL Portals help users wake assigned PCs on demand.

Explore WOL Portals →

Savings proof for management

Power management projects need more than assumptions. ASDM supports estimation, trial validation and reporting for energy, cost and CO₂ impact.

Open ROI Calculator →

Less unnecessary runtime

Power management is not a security product. But unnecessary runtime can mean unnecessary exposure for unattended office PCs that do not need to stay online.

Explore safe idle shutdown →

1

Estimate

Use the ROI Calculator to estimate potential energy, cost and CO₂ savings.

2

Pilot

Test with a controlled group, site, lab or department before rollout.

3

Validate

Check shutdown safety, Wake-on-LAN reliability, maintenance windows and user impact.

4

Prove

Use reporting and operational feedback to decide how far to scale.

Does ASDM replace SCCM, Intune or GPO?

No. ASDM is designed to complement existing endpoint-management tools. It adds a dedicated power and wake workflow for safe shutdown, reliable wake-up, user self-service wake and savings proof.

Can Configuration Manager already wake computers?

Yes, Configuration Manager supports Wake-on-LAN for supported deployment scenarios. ASDM focuses on the broader operational workflow: safe shutdown, scheduled availability, routed Wake-on-LAN concepts, WOL Portals and reporting.

Why not solve this with Group Policy?

Group Policy is useful for baseline settings. ASDM adds runtime logic, central operations, Wake-on-LAN infrastructure, reporting and user-facing wake workflows.

Why not script it?

Scripts can solve narrow tasks, but they often become difficult to maintain, audit and scale. ASDM provides a ready-made product with central policies, logs, reporting, portals and a trial path.

Does ASDM replace endpoint security tools?

No. ASDM is not an endpoint security product. It can support operational exposure reduction by helping avoid unnecessary runtime, while endpoint protection, patching and hardening remain separate responsibilities.

Can we test this without a large project?

Yes. Start with the ROI Calculator and the 45-day Enterprise Trial. Validate shutdown behavior, wake reliability, maintenance windows and reporting in your own environment.

Keep Microsoft endpoint management. Add the missing power and wake layer.

Evaluate Auto Shutdown Manager where native tools and scripts usually stop: safe shutdown, reliable wake, remote availability, less avoidable runtime and proof of savings.

Calculate ROI Download 45-Day Trial Contact Sales

Product · Release notes

Auto Shutdown Manager release history

Review new capabilities, improvements and fixes by version. Each release can be opened individually, so IT administrators can reach the relevant technical details quickly.

Open Download Center Read Release 5 Upgrade Guide

Select any release below to view its documented changes.

01

Identify the installed release

Managed clients: On the server, open Client Overview and check the Release column. It shows the currently installed release for each client.

Stand-alone installation or the server itself: Open Auto Shutdown Manager and check the release number in the lower green area of the application window.

02

Review the documented changes

Expand only the versions relevant to your deployment or update path.

03

Continue with the right resource

Use the Download Center for available packages or the upgrade guide for Release 5 preparation.

New Release 5.8.3.17 (Replaces 5.8.3.14) – June 2026

Minor corrections have been made throughout the graphical user interface.
The maximum configurable idle-timer value has been increased from 180 to 480 minutes.
DDC/CI management has been improved: on systems using Modern Standby (S0), Auto Shutdown Manager can switch external monitors on and off through the Display Data Channel Command Interface (DDC/CI).

Release 5.8.3.14 (Replaces 5.8.3.12) – May 2026

Unwanted scheduled tasks or applications that unexpectedly wake PCs can now be permanently disabled or deleted directly in the GUI under Scheduled Tasks.
Server: Settings can now be retrieved from clients to create new settings groups or to add time rules, monitored counters, applications, and IP monitoring clients to existing policy groups.
Added asset reports with export options for PDF, Excel, and CSV.
Assets: Fixed memory reporting for integrated GPUs.
Added monitor DDC management for S0-based PCs / Modern Standby PCs with external monitors. This allows (most) external monitors to be turned off automatically during longer or unattended runtimes, and PCs can optionally be locked for improved energy savings and security.
Fixed a bug in client savings calculations that caused savings to be underreported.

Release 5.8.2.27 – May 2026

Smaller GUI updates and fixes

Release 5.8.2.20 – April 2026

Bug fixes in Asset Management

Release 5.8.2.18 – April 2026

Minor bug fixes and typo corrections
Optimized protocol efficiency

Release 5.8.2.15 – April 2026

Fixed an issue affecting German umlauts on some systems
Resolved minor issues in File Scanner and Asset Management

Release 5.8.2.8 – March 2026

The Auto Shutdown Manager Server now supports both MS SQL and a local SQLite database
New helper tool (wizard) for client deployments
Minor bug fixes

Release 5.8.1.19 – March 2026

Typos corrected

Release 5.8.1.17 – February 2026

Added a new “Populate Demo Data” workflow that creates a full enterprise demo setup, available only when no groups exist yet.

Release 5.8.1.16 – January 2026

Update for Auto Shutdown Manager Server – File Scanner XML jobs:

Bug fix in the TimeRules editor: the time pattern for the last weekdays of a month has been corrected. You can now define entries such as “Force a restart on the last Friday of each month at 03:30 h” without any issues.

Release 5.8.1.15 – September 2025

Update for Auto Shutdown Manager Server – File Scanner XML jobs:

WOL Scheduler Jobs: In addition to individual client names, whole groups are now supported. All clients in the selected groups are added to the WOL list.
Job rules: “Move” and “Delete” jobs can be driven by days of inactivity.Example:Move all clients that have been inactive for more than 10 days from Setting Group A to Setting Group B.
External Browser-based GUI Tool (BETA)EVPJobEditor.zip released (see download page). Browser-based GUI for creating and managing File Scanner XML jobs.Optional user authentication and authorization.Jobs, groups, and files can be limited to specific administrators.

Release 5.8.1.9 – August 2025

Bug fix for the Auto Shutdown Manager Server:

Auto purge of outdated clients has been fixed and should now work even on systems with a modified sliding window (Days for pool license lease).

Release 5.8.1.3 – July 2025

FileScanner

Minor fixes & improvements, enhanced error reporting:Resolved various small bugs to make the FileScanner more robust.

Automatic job processing:Continues to watch a dedicated folder for new or modified XML job files and executes them instantly. Supported operations include:
- Deleting or reassigning clients to other settings groups
- Creating or deleting Wake-On-LAN (WOL) proxies
- Adding WOL schedules to the Wake On LAN Scheduler

Centralized loggingAll processed-job messages, warnings, and errors are listed in Event Viewer under Monitoring.

Release 5.8.1.2 – June 2025

From this version onward, .NET Framework version 3.5 is no longer supported. Instead, .NET Framework 4.x is required, which, however, has already been preinstalled as a standard Windows component since Windows 8.

New feature added: Visual Time Rules Editor, which helps adjust the times of Time Rules via mouse and keyboard. It also provides a better visual overview of days and weeks.

Fix for Devices in Modern Standby:Laptops that are in S0 mode (Modern Standby) will now transition to hibernation more reliably when running on battery power and the lid is closed. This prevents battery drain and overheating.

Release 5.7.8.6 – June 2025

New feature added: Visual Time Rules Editor, which helps adjust the times of Time Rules via mouse and keyboard. It also provides a better visual overview of days and weeks.

Fix for Devices in Modern Standby:Laptops that are in S0 mode (Modern Standby) will now transition to hibernation more reliably when running on battery power and the lid is closed. This prevents battery drain and overheating.

Release 5.7.8.5 (replaces 5.7.7.52) – May 2025

5.7.8.5: Additional internal fixes for safer hibernation from Modern Standby

Fix for Devices in Modern Standby:Laptops that are in S0 mode (Modern Standby) will now transition to hibernation more reliably when running on battery power and the lid is closed. This prevents battery drain and overheating

Release 5.7.7.52 – May 2025

Fix for devices in Modern Standby:

Laptops that are in S0 mode (Modern Standby) will now transition to hibernation more reliably when running on battery power and the lid is closed. This prevents battery drain and overheating.

Release 5.7.7.50 – April 2025

Replaces version 5.7.7.49

Update: Enhanced Time-Rules user interface based on user feedbackIf you are using the EnviProt Modern Standby Wake Driver, please update it to the latest version (1.3) as well. You can find it under Downloads.

Release 5.7.7.46 – March 2025

ADD-ON: Waking Notebooks and PCs from Modern Standby (S0)

Auto Shutdown Manager now includes an S0 Wake Driver to address the difficulties many users have reported when waking from Modern Standby on Windows 11/10. Update to version 5.7.7.46 or later, install the .msix package from ModernStandByWakeDriver.zip (which includes a manual), and then configure TimeRules in Auto Shutdown Manager to schedule wake events from S0 or hibernation as usual.

Release 5.7.7.43 – March 2025

Fix: Asset Management:

Removed clients and their associated resources (monitors, HDDs, RAM modules, GPUs, motherboards, BIOS versions, printers, software, operating systems, etc.) are now immediately reflected in Asset Management.

Release 5.7.7.40 – February 2025

Fixed: The user interface was not loading correctly on some multilingual systems.

Release 5.7.7.39 – January 2025

Fixed: Modern Standby (S0):

Systems that inadvertently wake during Modern Standby will still transition to hibernation after the configured timeout.

This prevents overheating and battery drain, especially for laptops stored in a bag. It also significantly reduces power consumption.

Release 5.7.7.38 – January 2025

Added some minor updates to the GUI.

Release 5.7.7.35 – November 2024

Change in Service Startup from 'Delayed' to 'Automatic'

The Auto Shutdown Manager Client now starts more quickly after a system reboot. This change takes effect only during a fresh installation.

For updates to existing installations, the startup mode remains set to 'Delayed'. If needed, you can manually change this setting by navigating to:

Services ➔ ASDM_Service ➔ PropertiesAdditionally, the recovery action for the first service failure has been set to "Restart the Service". Previously, no action was specified for this scenario.

Releases 5.7.7.34 September 2024

Improved the user interface for editing time rules.Improved overall system stability.

Releases 5.7.7.29 (replaces 5.7.7.12 - *.28) August 2024

New Features:

1) Modern Standby^* (S0iX):

Limited support has been added for low power mode S0, also known as "Connected Standby" or "Modern Standby."

Background: Microsoft is increasingly replacing the traditional Standby (S3) with "Modern Standby" (S0). In S0, the CPU remains active, which, despite operating in a lower power mode, can drain the battery in some mobile devices and cause overheating when the lid is closed, and the laptop is stored in a bag. Modern Standby activates as soon as the monitor is turned off.

The Auto Shutdown Manager now switches the system from Modern Standby to Hibernation after a predetermined period to avoid these issues. The session is fully preserved, similar to Standby. Additionally, the Auto Shutdown Manager can prevent the monitor from turning off if the device is in use or if time rules are defined to prevent automatic shutdown, such as during office hours. After work hours, the system can automatically hibernate or shut down completely.

Features added:

1) Set a timer to hibernate the system after it has remained in Modern Standby for X minutes while running on AC power - for example, 2 hours.2) Set a timer to hibernate the system after it has remained in Modern Standby for X minutes while running on DC power (batteries) - for example, 10 Minutes.3) Option to prevent the screen from turning off to avoid unwanted Modern Standby when the system is needed for productive use (even if users are not actively working).When energy saving is desired (e.g., when the idle timer reaches 0) and the default shutdown mode is set to standby, S0 is used. With the hibernation timers mentioned above, the system can be set to hibernate after a delay. To avoid overheating or drained batteries on mobile devices, set the hibernation time on DC to a low value, such as 5-10 minutes.

^*) Please note that this is currently a BETA feature.

2) Advanced Input Detection:

This new option detects user activities from touch screens, pens, and other input devices, leading to more reliable idle detection.

Fixes:

The user interface is now more responsive to high-resolution displays and zoom values.Some other minor fixes have been added such as better noise detection for example to prevent unwanted shutdowns during phone calls or meetings, Asset Management reports improved and more.

Smaller fixes in Asset Management.

Smaller fixes in user interface (UI).

Releases 5.7.6.8 / 5.7.6.9 May 2024

Bug fixes:Small fix in Asset Management

Release 5.7.6.7- April 2024

Bug fixes:GUI: Completely hide the Auto Shutdown Manager GUI from the ALT-TAB list.

Asset Management: size of GPU Memory fixed

Release 5.7.6.4- November 2023

Feature update:

Remotely restart, shut down, or wake-on-LAN (WOL) PCs from a controlling PC. For instance, in educational settings, you can set up control shortcuts on the desktops of teachers' PCs to remotely restart, shut down, or wake the PCs in the same room as the teacher's PC.

Release 5.7.5.9- August 2023

Fixes:

The idle shutdown timer counted down for the remainder of the minute even if a "Disable Auto Shutdown" Time-Rule was enabled. This was just a lagging display issue that has now been fixed.

Release 5.7.5.7 / 5.7.5.6- May 2023

Features:

Added "Remakrs" column to client overview. Now administrators can add comments or their own notes to each client.

Fix (5.7.5.7):Improved idle analysis of complex performance counters such as video rendering via GPUs.

Release 5.7.5.4- April 2023

Fixes:

Sometimes the screen gets locked if the user logs in a long time after the PC has started up.

Improved performance and reduced load on the database

Descriptions & manuals updated

Release 5.7.4.6- December 2022 (replaces 5.7.4.5)

Minor fixes.

Release 5.7.4.3- July 2022

Fix for the MECM/SCCM plugin. FQDNs are now created even if they are missing. This is important to correctly identify the clients on the Auto Shutdown Manager server to process WOL and shutdown commands directly from MECM/SCCM and for the deployment plans.

Release 5.7.4.1- March 2022

Minor bug fixes

Release 5.7.3.50- Oktober 2021

Minor bug fixes for Asset Management

Release 5.7.3.48- September 2021

Minor bug fixes

The start behavior of the application has been improved

Release 5.7.3.44- July 2021

Replaces 5.7.3.42 / 5.7.3.32 / 5.7.3.31 / 5.7.3.29 / 5.7.3.28

New Features:

PC Asset Management in BETA version. The newly introduced asset management functionality in the Auto Shutdown Manager Management Console helps IT administrators and managers stay up to date on important assets in their IT environment. The asset data is read directly on the clients and automatically updated on the server. PC Assets supportedCurrently, the reports provide detailed information on the following PC assets:• BIOSes ($am.bios) incl. TPM Chip• Computer Models ($am.pcmodel)• Computer Types (Desktops, Mobile, Servers, Workstations,…) ($am.pcmodel.Type)• CPUs ($am.cpu)• Hard drives ($am.nic)• Installed Software ($am.soft)• Monitors ($am.monitor)• Motherboards ($am.mb)• Network Interface Controllers ($am.nic)• Operating Systems ($am.os)• Printers ($am.printer)• Video Controllers ($am.vc)Example Windows 11 TPM: for the upcoming Windows 11, find all clients that do offer the required TPM (Trusted Platform Module) support.To find out, navigate to "Client Overview" and enter the following filter: $am.bios.TPM_Exists = yes All clients that support TPM will be shown. With $am.bios.TPM_Exists = no , all clients that do not support TPM will be shown.Open the client asset details to get more details such as if TPM is enabled, the TPM version, the supported TPM Spec version and more.Further featuresClients can be found by specifying certain asset parameters. For example, find all clients with network drivers older than 10 years:Enter the search filter starting with $am., which stands for asset management: following by the asset category like NIC (network interface controller) followed by the asset detail like DriverDate like this: $am.nic.driverdate < 2011/1/1 (the date format ma depend on your local region)Another example. Find all clients where the Hotfix KB5003637 is currently missing (missing is marked by the ! symbol):$am.soft.version! = KB5003637

Minor Bug fixes: GUI did not start on some systems when there were issues with the config file. This is fixed now.

PLEASE NOTE: WHEN UPDATING THE AUTO-SHUTDOWN-MANAGER SERVER TO THIS RELEASE, PLEASE MAKE SURE THAT ALL CLIENTS ARE AT LEAST AT RELEASE 5.2.3.2 (Build April 2016) or newer

Release 5.6.8.31- October 2020

New Features:

Auto WOL configuration: configure required WOL parameters on clients automatically. Let Magic Packets only wake the PCs to make sure the PCs only wake up when they should. Disable Fast Startup on Windows 10 to avoid general WOL problems. Some other required options are automatically configured to make WOL usage as reliable as possible by minimizing administrative burden.
Limit total time spent on computer per user account (prototype): Enter individual users or AD user groups that should be monitored with regard to their daily PC time usage. Based on an assigned time profile, users are given a certain time per day as well as a certain time window in which they are allowed to use certain PCs.
Windows 10: Locking / Unlocking Computer improved: Now PCs can be locked in sleep mode but will remain unlocked if only the display is turned off.

When using the Windows-Key + L (lock computer), the monitor can be switched off immediately to save energy.
Advanced Time Rules

More complex timing rules can now be created. In addition to the previous format, two other actions have been added:• Run Scripts or Applications at the given time• Change the Idle Timer timing from the given time

In addition to the older “Daily, Weekly, OneTime” patterns, more complex timing patterns can now be used, including:• Run every last day of every x month (e.g. run last day of January, - March, - May, aso.).• Run every last Monday, Tuesday, ..., Sunday every x month• Run every Friday or every x Mon-Fri (e.g. run every second Friday)• Run X times only • Stop after the date (e.q. run daily but stop after December 31 2021)• And more

Time rules can now be modified.A new timing preview window helps check the timing pattern.
Auto Group Assignment: added Active Directory Group selection dialog. This simplifies assigning of client PCs to Setting Groups based on their AD Group membership
New Advanced WOL Portal

A new managed, Active Directory based Intranet / Internet WOL Portal has been added to the download area. Enable home office users to remotely activate their office PCs in a secure and easy way.

Fixes:

Fixed access to: Check for Updates, Open Support Page, Auto Configuration
Update Manager
Asian culture based numeric issues
Online Update did not always work on older, slower PCs
Client connection status sometimes showed Trying to connect server, even the client was already connected. The status is now updated quicker.
Updating energy kWh pricing and CO2 g/kWh data: date from corrected

Release 5.6.7.46 - June 2020 (Update June 22)

New Features:

none

Fixes:

The "Time Limit" function did not shut down the PC
Changing the idle shutdown timer was grayed out on some systems after saving the settings

Release 5.6.7.36 - January 2020

New Features:

EnviProt now supports uninterruptible power supply devices (UPS) from Alltronic Powersystems GmbH. In the event of a power failure in the server room or data center, individual computers and servers - or entire computer groups - can be shut down immediately or with a delay using the UPS Manager. After the power has been restored, selected computers or entire computer groups can be restarted automatically via Wake On LAN.

Fixes:

A few minor fixes within the user interface

Release 5.6.6.12 - September 2019

Fixes:

Under certain circumstances, some clients were locked immediately after logging in. The user had to log in again.

Release 5.6.6.11 - July 2019

Fixes:

The ASDM_Service could stop working after some windows system performance couters were corrupt. This is fixed now.

PLEASE NOTE: WHEN UPDATING THE AUTO-SHUTDOWN-MANAGER SERVER TO THIS RELEASE, PLEASE MAKE SURE THAT ALL CLIENTS ARE AT LEAST AT RELEASE 5.2.3.2 (Build April 2016) or newer

Release 5.6.6.9 - June 2019

Fixes:

Wrong calculation of "Seats in use" on the server in some special cases like after the server ran out of licenses.

Release 5.6.6.8 - June 2019

Fixes:

Auto Group Assignment filters for Active Directory Group membership (@GROUP)
SCCM Bridge – fix an scheduler issue
Server performance increased significantly

New Feature / Improvements:

Client Monitor: Filter/search for messages
Server Manager -> Features & Options : Allow/Forbid waking of clients via the Wake On WAN Tool
Client Overview:Added the info about know broadcast addresses (MAC /BCA)Now, each info like MAC/BCA, Manufacturer, PC Model , Last IP Address and so on can be copied into the clipboard via right click.
Maintenance Manager -> WOL Proxies:Added new feature (BETA) to automatically generate WOL Proxies.This feature will analyze all clients and try to find the best candidates to act as WOL proxies for all relevant subnets/VLANs. The priority is set by: 1) Raspberry PIs (with the Java WOL Proxy Client installed - see downloads) 2) Servers that run 24/7 3) Desktops (with lowest power consumption first) 4) Workstations 5) Mobile Devices and others

Release 5.6.3.8 - January 2019

The tab Client Structure has been removed and replaced by additional Group Filters in Client Overview.

Now clients can be assigned to- or moved between groups much easier.New client search filters added. Find clients now by IP ranges, AdGroup memership, Distinguished Names and much more.Added new Server Monitoring and Server Manger Editor. Now, it is easy to change the default 90 days license lease period for clients

Some other fixed and other minor improvements were added.

Release 5.5.3.21 - July 2018

The Auto Shutdown Manager GUI und Service now start faster on Windows 10 after a system restart.

Release 5.5.3.18 - Build Mai 2018

New minor feature added:

Now, when starting the AutoShutdownManager.exe while it is already running the GUI is shown.

Release 5.5.3.15 - Build Mai 2018

This is a bug fixing release.

Clients that were not assigned to a group and if the "Default Group" wasn't set, the clients were not visible in Client Structure.

Release 5.5.3.14 - Build April 2018

This is a bug fixing release.

Auto Group Assignment Filters for Active Directory Groups (@ADGROUP:) did not work in some circumstances.Some other smaller bugs were also fixed.

Release 5.5.2.9 - Build March 2018

This is a bug fixing release for 5.5.2.8, which should be urgently installed.Background: With 5.5.2.8, there was a file missing called “asdm_ds_s.xml”This file was used in previous versions prior to 5.5.2.8. The previous release 5.5.2.8 expects it to be within the installation folder. If it is missing, saving of client changes, group assignments, licensing data and others will not work properly or could be event reset to default values.

Release 5.5.2.8 - Build March 2018

New feature added.File Scanner: reads external XML based job files to automatically schedule WoL plans, delete or move clients, and add or remove WoL-Proxies.

Release 5.5.0.13 - Build October 2017

In a mixed environment of .NET3.5 and .NET4x based clients some older clients possibly didn’t update setting changes made on a server running the previous release 5.5.0.12. This update solves this issue. It needs to be installed on the server only. Updating the clients isn't necessary.

Release 5.5.0.12 - Build July 2017

Starting with the Auto Shutdown Manager release 5.5 the Microsoft .NET Framework Version 4.x is required for new installations. Updates to clients with the .NET Framework 3.5 only are supported via the internal Auto Shutdown Manager Update Manager.

Release 5.4.1.9 - Build June 2017

Minor internal fix to improve saving of client data.

Release 5.4.1.8 - Build May 2017

+ Performance and stability update: tested with over 30.000 clients per server+ Support for Raspberry Pi as WOL Proxy+ WOL Proxy Monitor: automatically monitor and wake up WOL proxies+ Support for Server Core installations (gui and management console can be made visible via new command line option)+ Minor Bugs fixed

Release 5.4.1.7 - Build April 2017

+ Performance and stability update: tested with over 30.000 clients per server+ Support for Raspberry Pi as WOL Proxy+ WOL Proxy Monitor: automatically monitor and wake up WOL proxies+ Support for Server Core installations (gui and management console can be made visible via new command line option)

Release 5.3.2.4 - Build Dezember 2016

This update includes several internal optimizations and improvements.New search- and timing filters in Clients Overview and Client StructureTurn off the display after computer was locked Lock computer after the turning off the display

Release 5.2.3.2 - Build April 2016

New Wake On LAN feature: FileScannerNow, the Wake on Lan Scheduler on an Auto Shutdown Manager Server can process so called WOL Job files containing information about the timing, recurrence, weekdays, expire timing and lists of PCs to schedule and wake remote PCs. The WOL job files are plain text files following an easy XML format that is explained in the manual.

SCCM Bridge doens't open: The SCCM Bridge didn’t open in some environments. This was a bug and it is fixed now.

Others:Few other minor fixes and improvements

Release 5.2.2.9 - Build February 2016

SCCM:Packages: added support for Package deployment WOL schedules . Now Auto Shutdown Manager Server can be used to wake (WOL = Wake on LAN) SCCM based deployments of Applications,Updates and Packages.SCCM Bridge optimized: now the SCCM bridge is able to limit the deplyoments to a few days in ahead, this reduces the overall overhead.

VM:Fixed VMware Workstation 12Pro support (start, suspend and WOL virtual machines). Start or suspend selected VMs together with the host – or automatically wake VMs per WOL (via magic packet broadcast).

Others news and fixes:Auto saving of open MS Office documents before shut down:Added support for MS Project documents. Now, Auto Shutdown Manager can save open Outlook, Word, Excel, Power Point, Visio and Projekt documents before shutting down or suspending the system. Documents can be saved back to their origin or as a local copy.Some smaller fixes in the user interface

Release 5.0.9.14 - Build November 2015

Fixed: WOL Scheduler Exceptions Days.

Release 5.0.9.12 - Build November 2015

Fixed Windows 10 Timing issues at startup.

Release 5.0.9.5 - Build September 2015

Fixed SCCM WOL issue for SCCM collections which contain clients not connected to ASDM.Now WOL is executed correctly for these collections too, and reports can be found in the Management Console -> Client Monitor.

Release 5.0.9.3 - Build August 2015

Fixed timeout problem at startup for Windows 10Changed code signatures from SHA1 to SHA256Improved auto configuration for installed applications

Release 5.0.8.27 - Build June 2015

Added WOL for Windows Update Plans to SCCM WOL Application Deployment Scanner. In addition to application deployments, now, the Auto Shutdown Manager Server also wakes PCs based on the Windows Update Plans defined in SCCM.

Release 5.0.8.26 - Build June 2015

SCCM WOL Application Deployment Scanner bug fixes and efficiency improvements

Release 5.0.8.18 - Build Mai 2015

Key news and functions:Own Tool (or Application) can now be executed by a time rule to display own messages or just to be started. The application is started in the context of the currently logged on user. Enter the complete application path into the message field of a Display Message Time Rule. Parameters can be added after the application path. Path names with white spaces should be enclosed within quotation marks “”

Mass changes of Remote WOL Address and Remote WOL Port within the Management Console -> Client Details added.

Release 5.0.8.3 - Build April 2015

Key news and functions:WOL for SCCM Application Deployments: WOL via Auto Shutdown Manager now only wakes PCs that are in the selected SCCM Collection. Other PCs that belong to the same Auto Shutdown Manager group won’t be awoken.

(BETA)Own Tool (or Application) can now be executed by a time rule to display messages or just to be started. The application is started in the context of the currently logged on user.Enter the complete application path into the message field of a Display Message Time Rule. Parameters can be added after the application path. Path names with white spaces should be enclosed within quotation marks “”

Release 5.0.7.16 - Build April 2015

Key news and functions:Added filters into Client Monitor (Management Console, only usable with Database).

Release 5.0.7.14 - Build March 2015

Key news and functions:Added SCCM Application Deployment Scanner. Now, the Auto Shutdown Manager Server can be used to process Wake On LAN (using the reliable Auto Shutdown Manager WOL infrastructure incl. WOL Proxies, etc.) scheduled by SCCM application deployments (German: Anwendungsbereitstellungen).Optional: Anotehr SMS Provider can now be addedOptional: further ASDM Server addresses can now be provided

Release 5.0.6.10 - Build January 2015

This update has some internal optimizations and improvements.

Release 5.0.6.6 - Build December 2014

Fixed SCCM Plugin - Default installation path can now be changed correctlyRemote Shutdown of PC-Groups can now be performed form an admin PC other than the ASDM Server. For example a teacher PC can now restart or shutdown all student PCs in the same room.Some other smaller fixes and improvments.

Release 5.0.5.28 - Build August 2014

Some fixes for display handling.

Release 5.0.5.21 - Build June 2014

New functions and features include

WOL for VMs (BETA). Now Auto Shutdown Manager can start VMs when a WOL Magic Packet was received. The virtual machine is identified based on the coded MAC address within the Magic Packet and automatically started like if it was a physical PC.VMware Player is now also supported to start virtual machines.

SCCM 2012R2 Plugin Integration:Auto Shutdown Manager now comes with a Plugin for the Microsoft System Center 2012R2 Configuration Manager©. This PlugIn allows the shutdown and Wake-On-LAN (WOL) of individual PCs or entire collections via the Auto Shutdown Manager Server. This is very helpful to use all the configured WOL capacities like Directed Broadcasts or WOL Proxies within the Auto Shutdown Manager Server to achive a working and reliable WOL system across various IP Networks, VLANs or even the Interent directly from the SCCM Console.

Release 5.0.3.6 - Build March 2014

Added some fixes to the user interface.

Release 5.0.2.29 - Build March 2014

New feature added: Wake On Lan Proxy (WoL Proxy).This feature is helpful in order to wake up PCs via WOL in different IP Segments or VLANs when directed broadcasts can’t be used. In this case one WOL Proxy PC per segment can be setup and kept on running 24/7. Auto Shutdown Manager Server then redirects WoL commands depending on the IP address of the Client to a particular WoL Proxy PC where a local broadcast is being generated. Some smaller modifications of the user interface were implemented.

Release 5.0.2.15 - Build January 2014

Some minor fixes and handling improvments.

Release 5.0.0.100 - Build November 2013

Fixed issues around detection of running applications on some systems.TimeRules are more accurate now.

Release 5.0.0.62 - Build October 2013

Please note that this is the first Auto Shutdown Manager Release 5.

Release 4.9.7.22 - Build February 2013

Several changes have been made to the initial setup and startup process of Auto Shutdown Manager after installation. Also, smaller bugs have been fixed.If a PC Wakeup Time Rule is used to automatically wake up the PC at a specified time, Auto Shutdown Manager always checks if the Windows wake timers are enabled (Vista, Windows 7, Windowds 8, Server 2008R2, -2012) and enables them if needed.

Release 4.5.8.64

- New Update build May 2009New Features added:- Central Database support. Now, all client events and reports can be logged into a central database.- Central report about the overall savings for all clients and servers- Product icon now can be hidden on all clients or specified client groups- Soft-Sleep-Mode: to avoid wakeup problems with some 3rd party Software

Next step

Ready to plan your update?

Check the upgrade prerequisites, then use the Download Center for the currently available installation resources.

Open Upgrade Guide Open Download Center

Nowadays, with energy prices rising continuously, both consumers and enterprises are looking for ways to save energy effectively - but without changing the familiar working style. Most importantly, benefits result from energy - and therefore cost savings. According to several researchers, on average, 20 % of all computers are not shut down at all at night or over weekends. Lunch breaks or long absences from the desk are not even mentioned.

See few examples how easy and flexible Auto Shutdown Manager can be used

Network Uptime Analyzer was designed to help you find out whether and how many PCs, servers and other IP enabled devices are left on overnight or at weekends. It is free - very easy - no installation - no agents. Get enterprise-wide reports about energy costs, energy consumption, and the related CO₂ production.

Auto Shutdown Manager operates even if no users are logged on in a so-called full background or service mode. All operations are supported in this mode, including power up, power down, restart, standby, updates and patches, deployment and receiving of new settings, and the execution of time rules.

Flexible Operation Modes

The operation modes provided by Auto Shutdown Manager are highly flexible.
Depending on the required policies, the system can be configured in a "Can", "Should" or "Must" shutdown mode. Shutdowns can be prevented during core business times or while maintenance tasks are being performed.

Outside of business hours, the idle shutdown timer will start monitoring the PC for productive tasks and active users. If no one can be detected for a specified period, open documents will be saved and the PCs shut down in a default or specified mode such as standby, hibernation, or power off. The default shutdown mode can be specified depending on the time, day of week or date.

This is an example what a day could look like:

RED: The PC will not shut down

GREEN: The PC may shut down (for example, Standby), if detected as idle (not productive)

Light Blue: The server starts the PC for maintenance via WoL

Dark Blue: The PC will shut down

All Systems can be grouped by required policies:

"CAN" - allow shutdown, but respect users

One group of PCs could be configured to be allowed to go into a defined sleep mode
during lunch hours. This means that, if no activities are detected during a defined
period, the systems would be allowed to go into a defined sleep mode such
as Standby.
Thus, the logical rule for lunchtime could be:

Keep running continuously between 7:30 am and 11:45 am (core business time)
Check for user or system activities between 11:45 am and 1:15 pm - if there are no activities for at least 10 minutes - go into Standby...
Wake up at 1:15 pm (if wanted at all)
Keep permanent running between 1:15am until 5:00 pm (core business time)
Check for user or system activities after 5 pm - if there are no activities for at least 10
minutes - go into Hibernation...

"SHOULD" - try to shut down at a specified time, but with a warning message and user decision

Another group of PCs could be set up to go into sleep mode during lunch hours, for example at 12:15 pm, regardless of other options. In this case, the users would receive a warning message notifying them about the planned shutdown. If the users want to continue their work, they just simply disagree and continue their work.
Finally, the idle shutdown timer would shut down the PCs when the users forget to do so after their work is done. Of course, unsaved documents would be saved automatically before the shutdown.

“MUST”- enforce shut down without user interaction

Another group of PCs could be used to display stock prices, for example. This only makes sense until the market closes, plus some extra time for aftermarket deals. Therefore, these PCs could definitely be switched off at 6 pm every day. In this case, the shutdown could be enforced without any user interaction.

Auto Shutdown Manager operates with network awareness

In enterprise environments, as well as in an increasing number of networked homes, - it is essential for the systems to run reliably and to be available during core business hours or whenever needed. Furthermore, systems might depend on each other. For example, clients’ computers cannot be operated properly if their servers are not available. To map these requirements, Auto Shutdown Manager was built with network-aware logic. This means that clients’ computers can wake their servers on demand and keep then running for as long as required. On the other hand, the servers know about the clients and keep up and running until the last client disconnects. In addition, other IP-enabled equipment can be used to control the idle shutdown decision.

See the manual for more details, or get your free 45-day evaluation copy now.

Platform · IT Asset Management

IT Asset Management for Endpoint Power, Stability and Lifecycle Decisions

Auto Shutdown Manager (ASDM) by EnviProt includes practical IT asset inventory for managed clients. It helps IT teams find hardware, driver, operating-system and software conditions that can affect energy efficiency, endpoint stability, security review and lifecycle planning.

Find affected clients Hardware inventory Software versions PDF, Excel and CSV reports

Download 45-Day Enterprise Trial View Central Management Watch Asset Management Video

Find technical conditions faster

Use collected inventory data to narrow down affected clients before troubleshooting power behaviour, driver reliability, software compatibility or hardware refresh questions.

Keep specialist systems in place

ASDM does not replace a dedicated IT asset management suite, CMDB or vulnerability scanner. It provides supporting endpoint inventory for ASDM-managed clients and operational review workflows.

Security and exposure review

Use collected software, driver, BIOS and operating-system data to identify clients that may need closer review by IT security or endpoint management teams.

Power and stability troubleshooting

Outdated drivers and unstable endpoint components can affect sleep, wake, display power handling and user productivity. Asset visibility helps admins find the candidates faster.

Lifecycle and standardisation

Compare PC models, CPUs, disks, memory, network adapters and operating systems to support hardware refresh, standardisation and support planning.

Auto Shutdown Manager Asset Management overview for operating systems and inventory categories — Asset overview: see physical and virtual assets and jump into inventory categories.

Auto Shutdown Manager showing clients affected by a selected asset category — Affected-client view: open an asset category and see which managed clients match.

Auto Shutdown Manager hardware details for a managed endpoint — Hardware details: inspect client hardware, firmware and component information.

Auto Shutdown Manager Executive Asset Management Report dashboard — Executive report: summarise managed devices, asset categories and physical/virtual endpoint split.

Auto Shutdown Manager software details with search for clients with installed or missing software — Software search: find clients with specific installed or missing software entries.

Auto Shutdown Manager warning for an old network adapter driver date — Driver signal: identify endpoints where old network-driver dates may deserve review.

Operating systems and PC types

Review operating-system distribution, desktop/mobile split and physical or virtual endpoint balance.

Hardware components

Inspect PC models, CPU models, disk models, memory modules, monitors, video controllers, printers and motherboards.

Drivers, BIOS and adapters

Use BIOS, network-adapter and driver-related information to support stability reviews and endpoint lifecycle decisions.

Installed software

Search installed software entries and versions to find clients that may need review, cleanup, updates or license discussion.

Regular collection

Asset information is gathered automatically from client systems and updated on the server, reducing manual checks during day-to-day operations.

PDF, Excel and CSV

Asset reports can be exported for operational review, lifecycle planning and management discussions.

Managed devices

Summarise the number of managed endpoints in the selected reporting scope.

Asset categories

Group hardware and software inventory into reportable asset categories.

Physical vs. virtual

Distinguish bare-metal endpoints from virtual machines where the collected data allows it.

Exportable output

Use PDF, Excel or CSV export for IT operations, lifecycle planning or review meetings.

Energy efficiency
Find hardware, drivers or software that may affect sleep, wake or display power behaviour.

ASDM value
Connect asset visibility to managed endpoint power policies and operational troubleshooting.

Stability and support
Identify endpoint groups with ageing drivers, mixed hardware or inconsistent software versions.

ASDM value
Quickly narrow down affected managed clients and review their details in context.

Security review
Asset data can help IT locate outdated software, drivers or system versions for further review.

ASDM value
Provides supporting inventory evidence. It does not replace dedicated vulnerability management.

Lifecycle planning
Compare OS, PC models, CPUs, disks, memory and virtual/physical endpoint distribution.

ASDM value
Exportable reports support refresh planning and standardisation discussions.

Does ASDM replace a dedicated IT asset management or CMDB system?

No. ASDM does not try to replace a dedicated asset management suite, CMDB or vulnerability scanner. Its inventory is focused on managed ASDM clients and supports power management, stability analysis, lifecycle planning and operational troubleshooting.

Can admins find clients with a specific software product or version?

Yes. The software inventory can help identify managed clients with specific installed software entries or versions, where that information is collected and available from the client system.

Can asset data help find outdated drivers or hardware risks?

It can support that workflow. ASDM can show hardware, BIOS, network-adapter and driver-related information that helps IT narrow down clients for further review. Dedicated security or vulnerability tools may still be required for formal risk assessment.

Can the asset inventory be exported?

Yes. Asset information can be exported as PDF, Excel or CSV reports for IT operations, lifecycle planning and management review.

How often is asset information updated?

Asset information is collected automatically from managed client systems and updated on the server. The current page focuses on the operational use of that data; exact collection behaviour should be validated in your ASDM environment.

FIND THE AFFECTED CLIENTS

Use endpoint inventory where it improves power, stability and lifecycle decisions.

Start with a managed group, review collected asset data and validate how ASDM inventory supports your endpoint power-management rollout.

Download 45-Day Enterprise Trial View Central Management View Reporting & CO₂

Central Management

Centralized control for enterprise PC power management

Auto Shutdown Manager’s Management Console gives IT one place to configure power policies, organize clients, run maintenance actions, manage licensing, roll out updates and review operational events.

Groups & policies Remote actions Maintenance wake-up Update rollout Savings overview

Start 45-day Enterprise Trial Read the manual

Manage clients by groups

Assign clients to groups with different power policies, security options and administrative settings. Assignment can be done manually or automated by PC name filters and Active Directory structure.

Run controlled remote actions

Wake, shut down, restart, log off, standby or hibernate selected PCs or complete PC groups directly from the console when operational work requires it.

Central power management workflow with policies, groups, remote actions, maintenance processes and reporting — Central management connects policies, groups, remote actions, maintenance processes and reporting into one operating model.

Client Manager

Create client groups, assign policy sets and organize PCs by function, department or Active Directory structure.

Manual drag-and-drop assignment
PC name filters
Active Directory-based structure
Remote wake and shutdown commands

License Manager

Manage client licensing centrally, either with permanent client licenses or leased licenses from the server.

Central license handling
Server-based lease model
Inactive client license reuse after 90 days
Manual cleanup if needed

Update Manager

Keep Auto Shutdown Manager clients up to date across selected groups after the server has been updated.

Group-based rollout
Transparent update process
Works even when no user is logged on
Designed for large client bases

Maintenance Manager

Wake clients for administration tasks, keep them running while needed and power them down again after maintenance is complete.

Scheduled or immediate wake-up
Wake-on-LAN support
Maintenance availability without 24/7 runtime
Supports advanced WOL scenarios

Client Monitor

Review recent operational events such as wake-ups, shutdowns, client initialization, updates and issues.

High-level event overview
Operational status visibility
Savings overview
SQL database export for deeper analysis

Savings & reporting

Use management data to support the business case for endpoint energy management and to validate savings in your environment.

Client activity events
Shutdown and wake-up history
High-level savings report
Data basis for further analysis

Client Manager showing group-based PC power management — Client Manager: group-based PC power management with policy groups and managed client assignments.

Auto Shutdown Manager Maintenance Manager with scheduled Wake-on-LAN tasks — Maintenance Manager: wake selected groups for maintenance windows and keep endpoint availability predictable.

Auto Shutdown Manager Client Monitor with event history — Client Monitor: review wake-ups, shutdowns, status changes, warnings and operational events from one place.

Auto Shutdown Manager reporting dashboard with uptime, energy, cost and savings charts — Reporting: turn central power-management activity into uptime, energy, cost and savings evidence.

Automatic server provisioning

New client PCs can receive the ASDM server address and TCP port during installation by using a simple server.ini file in the MSI source folder.

Works with existing rollout tools

Use the deployment process you already operate. When file-based provisioning is used, target computers need read access to the shared MSI source folder.

Server and port via command line

For scripted or managed installations, the server name or IP address and port can also be passed directly to the MSI command line, for example through deployment-tool parameters.

Image-based client systems

For provisioning or image-based environments, documented setup strategies cover preserved installation folders, unique client IDs and separate local data paths for session-based data.

Policy targeting

Use groups and automated assignment to apply different power-management behavior to offices, support teams, sales, marketing, laptops or other client sets.

Maintenance windows

Wake clients for maintenance tasks, keep them available while administrative work runs and power them down afterwards where the environment allows it.

Savings proof

Use event and savings reports as a practical basis for rollout validation, ROI discussions and continuous optimization.

Does Central Management replace SCCM/MCM, Intune or GPO?

No. Auto Shutdown Manager is designed to complement existing endpoint-management tools with dedicated power-management operations, Wake-on-LAN workflows, group-based actions and savings visibility.

Can clients be assigned to groups automatically?

Yes. Client PCs can be assigned manually or automated by PC name filters or the Active Directory structure, depending on how you want to organize policies.

Can the console wake PCs for maintenance?

Yes. The Maintenance Manager can wake clients for maintenance tasks, keep them running as long as needed and power them down again after the work is complete.

Can events and savings be analyzed later?

The Client Monitor provides a high-level event and savings overview. Report details can also be written to a Microsoft SQL database for further analysis.

How are ASDM clients deployed and connected to the server?

ASDM clients can be deployed as MSI packages through Group Policy, Microsoft Configuration Manager/SCCM or other MSI-capable deployment tools. During installation, clients can receive the server address and port automatically via a server.ini file or MSI command-line parameters.

START SMALL. SCALE SAFELY.

Pilot endpoint power management without building a custom script stack.

Start with a small set of managed PCs, validate policies in your own environment, then expand by groups, sites or departments.

Download 45-Day Enterprise Trial Estimate savings with the ROI Calculator Contact Sales

ASDM product tour

See Auto Shutdown Manager in action

Auto Shutdown Manager (ASDM) gives IT teams one place to organise endpoints, apply safe shutdown rules, coordinate wake and maintenance workflows, support remote access and verify the results.

Start the 45-day enterprise trial Talk to Sales View deployment guides

The screenshots use demo or anonymised data. Available panels and details can vary by ASDM version and enabled modules.

Monitor client activity and status

Review endpoint events, connectivity and current state from the central management console instead of checking devices one by one.

ASDM central management console showing client monitoring events and endpoint status — Client monitoring brings current activity and connection state into one operational view.

Manage clients through policy groups

Group endpoints by department, location or operational role, then apply the appropriate shutdown, wake and maintenance settings centrally.

ASDM group manager showing endpoint groups and assigned power-management settings — Policy groups keep large endpoint estates manageable without forcing one rule onto every device.

Configure shutdown rules and office hours

Define when time rules apply, how idle devices should react and which safeguards must be respected before a shutdown starts.

ASDM time-rule settings for scheduled and idle shutdown behaviour — Time rules make shutdown behaviour predictable while preserving the conditions that keep users and workloads safe.

Schedule wake events and remote actions

Wake selected groups before updates, maintenance or the start of the working day, then return them to the correct power state afterwards.

ASDM Wake-on-LAN scheduler with planned wake events and target groups — Scheduled wake events connect endpoint availability with update and maintenance routines.

Coordinate the complete maintenance window

Bring wake, readiness checks, patching, reporting and safe shutdown into one controlled sequence instead of treating power management as a separate afterthought.

Maintenance-window workflow showing wake, readiness checks, updates, reporting and safe shutdown — A controlled maintenance workflow keeps endpoints available when IT needs them and powered down when the work is complete.

WOL Portal: assigned computers and live status

Users see the computers assigned to them, their current status and the permitted wake action without receiving access to the full management console.

ASDM WOL Portal listing assigned computers with online status and wake controls — The WOL Portal gives users a focused self-service wake experience governed by IT assignments.

Remote Work / Wake-on-Demand request status

Authorised users can submit a wake request through the web-based experience and immediately see whether the target system was found, requested and brought online.

ASDM remote Wake-on-Demand view showing requested systems, request status and wake confirmation — The remote request view helps users confirm that the correct system was requested and whether the wake action has been processed.

Coordinate ASDM with SCCM/MCM

The workflow connects deployment plans, ASDM scheduling, network wake paths and endpoint readiness without replacing Microsoft Configuration Manager.

Workflow diagram showing SCCM or MECM deployment, ASDM scheduling, wake infrastructure and managed endpoints — ASDM adds reliable wake and power-state control around the existing deployment workflow.

Review deployment plans inside ASDM

Administrators can see the deployment-related schedule and target context used to wake systems before software distribution starts.

ASDM management console showing a scheduled SCCM deployment wake plan — Deployment timing becomes visible in the same operational context as wake scheduling and endpoint groups.

Review runtime, energy and uptime trends

Use central reports to compare activity patterns, runtime and energy-related outcomes across the selected scope.

ASDM reporting dashboard with runtime, uptime and energy-consumption charts — Operational charts help IT show what changed instead of relying on configured policy alone.

Inspect device-level hardware details

Drill into an endpoint when a report, driver issue or deployment question requires more technical context.

ASDM asset details view listing hardware components for a managed endpoint — Device-level inventory supports troubleshooting and targeted follow-up from the same management environment.

Multiple wake sources, routes and endpoint groups

Enterprise Wake-on-LAN architecture showing ASDM server, wake triggers, WOL proxies, directed broadcast and managed endpoints — The managed wake path can adapt to network boundaries while keeping target selection and policy centralised.

User notification and controlled interaction

Before shutdown, ASDM can display an administrator-defined message that includes the company name, the warning text and the support contact details relevant for that environment.

ASDM client shutdown notification with warning message, stop button and countdown timer — Client-side notifications can be customised by IT, including the message, branding and support path shown before the shutdown is enforced.

Need a view that is not shown here?

The trial and sales process can focus on the exact workflow that matters in your environment, including policy exceptions, network wake paths, reporting or deployment integration.

Request a focused walkthrough

Are these real Auto Shutdown Manager screens?

Yes. The screenshots and technical visuals come from real ASDM product views or accepted technical pages. Demo or anonymised data may be used.

Can the interface look different in our environment?

Yes. Available panels, labels and data can vary by ASDM version, enabled modules, permissions and the workflow being configured.

Can we inspect the screens at full size?

Yes. Select any real screenshot to open the full-size image in the site viewer.

How can we see a workflow that is not included?

Use the enterprise trial or contact Sales for a walkthrough focused on your deployment, wake, shutdown, remote-work or reporting requirements.

Evaluate with your own endpoints

Move from screenshots to a controlled pilot

Test the management console, safe shutdown logic, wake reliability and reporting in your own environment before deciding on a wider rollout.

Start the 45-day enterprise trial Calculate ROI Contact Sales

Auto Shutdown Manager feature list

Enterprise PC power management capabilities, organized for real IT operations.

Compare the capabilities available in Auto Shutdown Manager Enterprise, Education/Government/NPO and Free Light editions. The feature set covers safe shutdown, Wake-on-LAN, central policy management, reporting, remote operations and integration with existing endpoint-management workflows.

Download 45-Day Enterprise Trial Calculate ROI Why ASDM?

81 listed capabilities 8 operational groups Enterprise / EDU-GOV / Free Light comparison

Enterprise

For commercial and enterprise environments that need central management, policy control, WOL infrastructure, reporting and rollout support.

81 supported capabilities

Education / Government / NPO

For public sector, education and non-profit deployments with the managed feature set needed for labs, offices and controlled fleets.

81 supported capabilities

Free Light

For private use only. Useful for local power management, but not intended as the managed enterprise deployment edition.

21 supported capabilities

Safe shutdown & wake control 14 capabilities Wake-on-LAN / WAN infrastructure 14 capabilities Central management & policies 12 capabilities Remote power operations 9 capabilities Monitoring, analysis & reporting 16 capabilities Automation & integration 6 capabilities Specific environments & hardware 4 capabilities User access & usage control 6 capabilities

Safe shutdown & wake control Core runtime reduction controls: idle shutdown, document protection, warnings, schedules and wake-up. 14 features

Capability	Enterprise	Education / Gov / NPO	Free Light
Shutdown based on Timer countdown	✓	✓	✓
Forced Shutdown based on Time Rules	✓	✓	—
Time Rules (for further automation, e.g., starting applications, messages, power on/off, stopping/starting shutdown timers, and much more)	✓	✓	—
Detection of running Applications (e.g. PowerPoint)	✓	✓	✓
Wake-Up PC from Sleep	✓	✓	—
Auto shutdown mode selection (e.g. use Standby in the afternoon, Hibernate or PowerOff at night)	✓	✓	—
Dependent on Power mode (AC / DC)	✓	✓	—
Windows Power Management: Respect / Ignore Windows Power Management settings	✓	✓	✓
Screen Saver Management Keep display always on Keep display on while selected applications are running Switch display off after x minutes of PC idle time (optional: and lock PC) Switch display off as soon as PC is locked (WIN+L or by system)	✓	✓	✓
User warnings before Shutdown	✓	✓	✓
Save unsaved documents before shutdown (Word, Excel, PowerPoint, Project, Visio, Outlook, ...)	✓	✓	✓
Business Times Management for example prevent shutdown during core business times	✓	✓	—
Scheduled Shutdown of local or remote PCs	✓	✓	—
Scheduled Wake-Up of local or remote PCs	✓	✓	—

Wake-on-LAN / WAN infrastructure Wake devices reliably across local networks, VLANs, remote sites and WOL proxy scenarios. 14 features

Capability	Enterprise	Education / Gov / NPO	Free Light
MCP Server extends Wake-On-LAN to AI-driven agents (VS Code, N8N, etc.)	✓	✓	—
Wake On LAN - Local Broadcast - Server -> Clients	✓	✓	—
Wake On LAN - Local Broadcast - Clients -> Server	✓	✓	—
Wake On LAN - Directed Broadcast - Server -> Clients	✓	✓	—
Wake On LAN - Directed Broadcast - Clients -> Server	✓	✓	—
Wake On WAN – Remote PC -> Internet -> Server -> Clients, optionally with VPN	✓	✓	—
Wake on Wan Client	✓	✓	—
Wake On LAN/WAN- WOL Proxy (local, segments, VLANs, Internet)	✓	✓	—
Wake On LAN/WAN- WOL Proxy for RaspBerry Pi (Java)	✓	✓	—
Auto-generate WOL Proxies (updates WOL Proxies automatically to ensure reliable WOL after network changes are detected)	✓	✓	—
Wake on LAN Scheduler with exceptions	✓	✓	—
Scheduled Maintenance WoL Wake-Up	✓	✓	—
Support for the free Advanced EnviProt Wake On LAN WEB Portal with AD and SSO support	✓	✓	—
WOL - Start virtual machines via Wake On LAN	✓	✓	—

Central management & policies Manage policies, groups, updates, maintenance windows, licensing and background client/server operation. 12 features

Capability	Enterprise	Education / Gov / NPO	Free Light
Central Management	✓	✓	—
Organize Power Management Policies by Groups	✓	✓	—
Automatically assign PCs to Power Management Policies by: PC Name filters Active Directory Attributes (like OU=, CN=...) Membership in active directory groups	✓	✓	—
Settings Management and remote deployment	✓	✓	—
Centralized Updates	✓	✓	—
Maintenance Manager	✓	✓	—
License Manager	✓	✓	—
Hidden operation on clients	✓	✓	—
Auto Configurator for easiest initial setup	✓	✓	✓
Operation in Background - Windows Service Mode	✓	✓	✓
Operation as Client	✓	✓	—
Operation as Server	✓	✓	—

Remote power operations Start, restart, shut down, hibernate, log off or wake systems remotely when IT needs control. 9 features

Capability	Enterprise	Education / Gov / NPO	Free Light
Remote Power ON / Power Off	✓	✓	—
Remote Management	✓	✓	—
Remote Power On from Shutdown Mode (completely off)	✓	✓	—
Remote Shutdown	✓	✓	—
Remote Standby	✓	✓	—
Remote Hibernate	✓	✓	—
Remote Log-Off users	✓	✓	—
Remote Restart	✓	✓	—
Remote Wake-Up (LAN and WAN)	✓	✓	—

Monitoring, analysis & reporting Use activity, power, hardware, network and runtime signals to decide and prove what changed. 16 features

Capability	Enterprise	Education / Gov / NPO	Free Light
ITAM - IT Asset Management. Collect and report key assets from your client PCs (CPUs, GPUs, RAM, HDDs, serial numbers, drivers, software, and much more)	✓	✓	—
Performance Counters for in-depth system analysis Some examples: Network traffic & utilization Detection of processes and their utilization Active user sessions VPN Tunnel active Backup is going on And many more	✓	✓	—
Analysis of other TCP/IP equipment such as receivers, printers, production machines for shutdown procedures	✓	✓	—
Mouse / Keyboard	✓	✓	✓
CPU Utilization	✓	✓	✓
HDD Utilization	✓	✓	✓
Sound analysis	✓	✓	✓
Log Up and Down times	✓	✓	✓
Power consumption and CO2 reduction analysis	✓	✓	✓
Central Monitoring	✓	✓	—
Protocol stored in Central Database	✓	✓	—
Identify Clients with Power Supply Problems	✓	✓	—
Identify Clients with Thermal Problems	✓	✓	—
Identify Clients with Power Management Problems	✓	✓	—
Detect IP Clients to prevent shutdown	✓	✓	—
Network Clients prevent server shutdown for dynamic servers	✓	✓	—

Automation & integration Integrate with SCCM/MCM, scripts, scheduled tasks, file scanner jobs and command-line workflows. 6 features

Capability	Enterprise	Education / Gov / NPO	Free Light
MEM/SCCM Plug-In - Integration into Microsoft® Endpoint Manager / System Center Configuration Manager®	✓	✓	—
File Scanner: create own XML based jobs to schedule WoL, delete clients or move them to other settings groups, add or remove WoL-Proxies	✓	✓	—
Run Scripts or Application on Startup	✓	✓	✓
Run Scripts or Application before Shutdown	✓	✓	✓
Support Command Line Arguments	✓	✓	✓
Scheduled Tasks analysis	✓	✓	—

Specific environments & hardware Support special IT environments such as UPS, VMware and virtual machine handling. 4 features

Capability	Enterprise	Education / Gov / NPO	Free Light
UPS support (Uninterruptible Power Supply): Automatically switch off selected PCs or PC groups in the event of a power outage, and restart them when power is restored	✓	✓	—
VMware service analysis	✓	✓	—
Start virtual machines at Startup	✓	✓	—
Suspend virtual machines before Shutdown	✓	✓	—

User access & usage control Limit or manage PC access, logon behavior and user runtime policies where needed. 6 features

Capability	Enterprise	Education / Gov / NPO	Free Light
Auto Login User on Startup (Disable / Enable)	✓	✓	✓
Prevent users from blocking public PCs by staying logged in for long times	✓	✓	—
Simple PC time limitation (access protection) Limit the PC time per local user and per day on a local machine	✓	✓	✓
Extended PC time protection	✓	✓	✓
Work safety: Limit total PC usage time per user account and weekday centrally managed and based on Active Directory	✓	✓	—
Maintenance reboot after x sleep states	✓	✓	✓

Next step

Validate the capabilities in your own environment.

The full-featured Enterprise trial lets your team test shutdown behavior, Wake-on-LAN, reporting, document preservation and central management before rollout.

Download Trial Contact Sales

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.

Major-version migrationNew Release 5 license requiredCentral client rolloutConfiguration-preserving install path

Review the Upgrade Steps Discuss Licensing Explore Release 5 Features

Contact Our Sales Team

Modern Standby management

Support scheduled wake-ups and apply dedicated controls for Modern Standby scenarios.

Explore Modern Standby

IT asset intelligence

Report on operating systems, software, BIOS versions, processors, storage, video controllers and other endpoint details.

Explore IT Asset Management

Enterprise Wake-on-LAN

Use WOL scheduling, WOL Proxies, Wake-on-WAN and web-based WOL Portals across supported network scenarios.

Explore WOL Portals

MCM / SCCM integration

Coordinate power actions with Microsoft Endpoint Configuration Manager and System Center Configuration Manager workflows.

View the Feature List

Richer 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 Downloads

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 requirements

3

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.

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.

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.

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.

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.

Discuss Your Upgrade Open Downloads View Feature List

Platform · WOL Portals

Advanced Wake-on-LAN Portal with SAML Single Sign-On

Give authorized users a controlled way to wake assigned office PCs before remote access begins. Deploy the Advanced WOL Portal in your own infrastructure, connect it to SAML 2.0 and Active Directory, manage users and PCs directly in the portal, or combine both approaches for selected exceptions.

Optional SAML 2.0 SSO Active Directory PC assignments Portal-managed users and PCs Hybrid assignment model Self-hosted on IIS ASDM wake infrastructure

Download WOL Portal & Trial See the Remote Work Use Case Explore Enterprise Wake-on-LAN

Assigned-machine access

Users see only the PCs assigned to them instead of receiving unrestricted wake access to every managed endpoint.

Self-hosted control

Deploy the Advanced WOL Portal on Microsoft IIS in your own infrastructure and connect it to your existing identity, network and security controls.

ASDM-routed wake

The portal sends each approved request to the ASDM Server, which uses your configured WOL routing, proxy and Wake-on-WAN components where supported.

Infographic showing SAML and Active Directory assignments, portal-managed users and PCs, hybrid assignments and the common ASDM wake flow — **Assignment overview:** Use Active Directory for standard assignments, the portal for direct administration and exceptions, or combine both approaches. The wake request is executed through ASDM.

Mode 1

SAML SSO + Active Directory assignments

Sign-in: your corporate SAML 2.0 identity provider.

PC assignments: the user’s Active Directory object through the configurable WOLPCNAME attribute, or another attribute name you configure.

Best fit: organizations that keep day-to-day user-to-PC assignments in Active Directory.

Mode 2

Portal-managed users and PCs

Sign-in: the direct WOL Portal login.

PC assignments: maintained directly in the Advanced WOL Portal User Manager.

Best fit: deployments without SAML SSO, smaller scopes, pilots, guests, contractors, or teams that want direct portal-side control.

Mode 3

Hybrid: AD primary PCs + portal exceptions

Sign-in: SAML SSO can remain the normal user path.

PC assignments: primary PCs come from Active Directory, while selected users receive additional PCs or wider wake rights directly in the portal.

Best fit: AD-first organizations that need controlled exceptions for admins, support teams, lab systems, shared PCs or servers.

The important hybrid point

AD-first does not mean AD-only.

Keep the standard workforce aligned with Active Directory and SAML SSO, then use portal management only where extra flexibility is needed. Normal office users can receive their primary PCs from AD, while an administrator or support user can also receive additional lab machines, shared PCs, servers or other explicitly assigned systems.

Identity from the IdP

By default, the portal reads the user-principal-name value from the LoginName claim to identify the signed-in user.

Primary PCs from AD

Store one or more comma-separated PC names in WOLPCNAME, or configure a different Active Directory attribute name.

No duplicate portal record required

SSO users do not need a second portal user record for their normal AD assignments. Add a portal record only when that user also needs additional portal-managed PCs or roles.

Corporate SAML identity provider sign-in screen used before opening the Advanced WOL Portal — **Corporate sign-in:** users authenticate through the organization’s SAML identity provider.

Advanced WOL Portal start screen for waking PCs assigned by the IT department — **Portal after SSO:** the assigned-PC wake workflow opens without a second portal password.

Advanced WOL Portal User Manager showing portal roles and directly assigned PCs — **User Manager:** create portal users, assign roles and maintain the PCs each user may wake.

Advanced WOL Portal Group Status Overview with online and offline counts by policy group — **Group Status:** review online and offline systems by ASDM policy group.

Advanced WOL Portal showing the authorized computer list, online status and a Wake Computer action — **Hybrid result:** standard office PCs can come from Active Directory, while selected users receive additional portal-managed systems and wider wake rights.

1. Identify the user

Use SAML SSO or the direct portal login.

2. Build the allowed-PC list

Combine Active Directory assignments with portal-managed PCs where configured.

3. Forward the wake request

Send the selected PC and authorized user request to the ASDM Server.

4. Confirm the request

Show whether the wake request was accepted and display endpoint status where available.

Wake request confirmation

After the user selects a PC and clicks Wake, the portal submits the request to ASDM and shows whether the request was accepted. Endpoint status can also be displayed when the required status path is available.

Advanced WOL Portal showing a successfully initiated wake request and endpoint status — **Wake request status:** the portal confirms the submitted request and reports the current result.

IIS and Windows Server

Use Microsoft IIS on Windows Server 2016 or newer with the required ASP.NET 4.x application-development features enabled.

.NET Framework

Install Microsoft .NET Framework 4.8 or newer.

SQL Server

Use Microsoft SQL Server or SQL Express 2016 or newer for portal data.

HTTPS

Publish the portal over HTTPS and manage certificate trust and lifecycle through your IIS environment.

ASDM Server

We recommend ASDM Server 5.7.4.x or newer for full compatibility with the current Advanced WOL Portal release.

AD schema planning

For AD-based PC assignments, add the custom user attribute—by default WOLPCNAME—and validate the schema change in a test environment first.

Included portal software

We provide the Advanced and Basic WOL Portal software to ASDM customers at no additional software license cost.

Choose the Advanced Portal for SAML SSO, assigned-PC workflows and enterprise administration. Use the Basic Portal for simpler internal wake scenarios. You provide and operate the Windows Server, IIS, SQL Server, certificates and network infrastructure in your own environment.

Advanced WOL Portal

Choose it for managed enterprise and remote-work scenarios.

Optional SAML 2.0 single sign-on
AD-based primary PC assignments
Direct portal user and PC administration
Hybrid AD-plus-portal assignment workflows
Assigned-machine wake workflow
Group status and administrative views
ASDM WOL routing and proxy integration

Basic WOL Portal

Choose it for limited internal scenarios where entering a workstation FQDN and an optional shared secret is sufficient.

Simple self-service wake request
Smaller administration scope
No SAML SSO or Active Directory assignment workflow

Are the three modes separate portals?

No. They are three administration models for the same Advanced WOL Portal. Choose Active Directory assignments, direct portal administration, or a hybrid of both.

Does SAML SSO mean users never see another portal login?

When configured correctly, yes. The portal can reuse the identity authenticated by your SAML 2.0 provider and open the assigned-PC workflow without a second portal password. The direct portal login remains available for other configurations.

Can we manage PC assignments directly in Active Directory?

Yes. Store the user’s primary PC assignments in a configurable custom attribute on the Active Directory user object. The default attribute name is WOLPCNAME. Plan and test the required AD schema extension before rollout.

Can SSO assignments and portal-managed assignments be combined?

Yes. Keep normal PCs in Active Directory for the SSO workflow, then assign additional PCs or wider wake rights directly in the portal for selected users. This is the hybrid model.

Does the portal itself send the final Magic Packet?

No. The portal submits the authorized request to the ASDM Server. ASDM then performs the wake action through the configured WOL routing and proxy infrastructure.

Is the Advanced WOL Portal cloud-hosted?

No. You deploy the Advanced WOL Portal on your own Microsoft IIS and SQL Server infrastructure.

Does the portal replace VPN, Remote Desktop or endpoint security?

No. The portal manages endpoint wake availability. Your VPN, RDP, VDI, remote-support, authentication and endpoint-security systems continue to handle the remote session and its protection.

Are the WOL Portals included for ASDM customers?

Yes. We provide the Advanced and Basic portal software to ASDM customers at no additional software license cost. You provide and operate the required server, database, certificate and network infrastructure.

Controlled wake access for real environments

Test SSO, AD assignments, portal exceptions and the complete wake path in your own environment.

Start with representative users, PCs and network segments. Verify SAML claims, Active Directory assignments, portal-managed exceptions and ASDM wake routing before expanding the rollout.

Download WOL Portal & Trial Contact Sales

Ready-made enterprise PC power management software

Enterprise PC power management without the project overhead.

Stop leaving PCs on “just in case”. Auto Shutdown Manager is a ready-made tool for automated PC shutdown, reliable Wake-on-LAN, remote user wake-up, maintenance windows and measurable energy savings — built for real IT environments with VLANs, SCCM/MCM, Active Directory, WOL Portals and central reporting.

45-Day Enterprise Trial Automated PC Shutdown Wake-on-LAN Across VLANs WOL Portals SCCM / MCM Integration Modern Standby Wake Driver IT Asset Management ROI Calculator

Calculate ROI Download 45-Day Enterprise Trial View Feature List

Estimate your savings first, then validate ASDM in your own environment with the full-featured 45-day Enterprise trial.

Why common approaches fall short

Windows power policies, GPOs, scripts, basic Wake-on-LAN tools and remote access software can all help with parts of the problem. But they rarely solve the complete operational challenge: shutting down only when users and background jobs are safe, waking PCs for updates and maintenance, handling VLANs and remote sites, giving users secure self-service wake-up, and proving results with usable reports.

Auto Shutdown Manager brings these pieces together in one finished tool. That is the difference: less custom scripting, fewer manual routines, more control, and a faster path from evaluation to measurable savings.

Estimate first

Use the ROI Calculator to estimate potential energy, cost and CO2 savings with your own assumptions before rollout.

Calculate ROI

Test in your environment

Start with the full-featured 45-day Enterprise trial and validate shutdown, Wake-on-LAN, reporting and management workflows on real endpoints.

Download trial

Roll out centrally

Use groups, central settings, Active Directory-based assignment, deployment options, updates and maintenance management from the ASDM Console.

Central Management

Replace fragile scripts

Use a supported product with policies, WOL infrastructure, logging, reporting, portals and IT Asset Management instead of maintaining custom shutdown and wake-up scripts.

Feature List

Cut avoidable runtime

Automatically shut down idle PCs based on real activity and rules instead of leaving endpoints on overnight.

Wake devices when needed

Wake PCs for users, patch windows, maintenance tasks and scheduled operations using Wake-on-LAN, WOL Proxies and wake schedules.

Keep IT in control

Manage policies, groups, settings, updates, deployment and maintenance centrally instead of relying on local manual configuration.

The available MCP Server extends Wake-on-LAN capabilities to AI-driven agents for machine state query and WOL workflows without making the core product experimental.

Learn more

Make the business case before rollout

Energy saving projects often fail when the business case is unclear. ASDM makes evaluation practical: estimate potential savings with the ROI Calculator, test the full-featured Enterprise trial in your own environment, then validate results with uptime/downtime logging, power consumption analysis and CO2 reduction analysis.

FH Osnabrück case study reported ROI in around 4 weeks for its specific rollout.
MISD listed “Best value with easy licensing” among the benefits.
Case study results are environment-specific and not a universal promise.

Windows power policies / GPO

Where it helps: Good baseline for standard settings.

Where it falls short: Limited awareness of real user activity, maintenance workflows, WOL infrastructure and reporting.

What ASDM adds: Intelligent idle detection, warnings, document saving, business rules, central control and reporting.

Custom scripts

Where it helps: Can automate narrow tasks.

Where it falls short: Hard to maintain, fragile, weak visibility, often dependent on one admin.

What ASDM adds: A finished tool with console, policies, logging, WOL infrastructure, reports and supportable workflows.

Basic WOL tools

Where it helps: Can wake devices in simple local networks.

Where it falls short: Often limited to sending Magic Packets and not enough for VLANs, remote sites, scheduling and user self-service.

What ASDM adds: Directed broadcasts, WOL Proxies, Wake-on-WAN, schedules, maintenance wake-up and WOL Portals.

SCCM/MCM-only workflows

Where it helps: Useful for endpoint management and deployments.

Where it falls short: Endpoint power state still needs reliable shutdown and wake orchestration.

What ASDM adds: Dedicated power management plus MEM/SCCM plugin integration and WOL infrastructure.

Remote access tools

Where it helps: Allow access to running PCs.

Where it falls short: They do not solve energy waste if PCs stay on 24/7.

What ASDM adds: Self-service WOL Portal access so assigned PCs can be woken when needed.

Large internal IT project

Where it helps: Can be tailored.

Where it falls short: Slow, expensive in internal time, harder to maintain, reporting and portals must be built separately.

What ASDM adds: A ready-made enterprise tool that can be evaluated with a 45-day trial and ROI Calculator.

8,500 PCs / 47 campuses

Mesquite ISD

Mesquite Independent School District used ASDM to manage power and updates across 8,500 PCs on 47 campuses, integrate with SCCM 2012 R2, divide computers into six groups, shut down systems at 7 p.m. and wake them at 5 a.m. for updates before users arrived.

Value: The case study lists “Best value with easy licensing” among the benefits.

Read MISD case study

ROI in around 4 weeks

FH Osnabrück

The University of Applied Sciences Osnabrück rolled out ASDM to more than 120 computers after a trial period in April 2009. The case study reports a complete return on investment in around 4 weeks and says the solution was stable from day one with very little administration.

Read FH Osnabrück case study

77 PCs directly monitored

UC Berkeley / ENERGY STAR

In the UC Berkeley LoCal project, several hundred computers ran ASDM and 77 were directly monitored with wireless power meters. The ENERGY STAR case study reports that over 60% of PCs with ASDM installed achieved energy savings of 90% or more.

Value: The case study also describes ASDM as much simpler than a home-grown solution.

Read ENERGY STAR case study

Case study results are specific to each environment. Actual savings and ROI depend on runtime patterns, electricity costs, hardware, network configuration and rollout scope.

Nightly shutdown without user disruption

Reduce overnight runtime while checking real activity, applications, business times and user warnings before shutdown.

Idle shutdown

Wake PCs for patch and maintenance windows

Power endpoints down when they are not needed and wake them before planned updates or maintenance tasks.

Remote shutdown & WOL

Let remote users wake assigned office PCs

Avoid leaving office PCs on all the time just for remote access. Let authorized users wake assigned machines through the WOL Portal.

WOL Portals

Manage labs, classrooms, libraries and campuses

Use central policies and group-based management for shared computers in education, government and public-sector environments.

GOV / EDU / NPO solutions

Support VLANs, branch offices and segmented networks

Use WOL Proxies and directed broadcasts where simple local Magic Packets are not enough.

Wake-on-LAN

Reduce unnecessary exposure

Power down abandoned or unused endpoints instead of leaving them running when no user or maintenance task needs them.

Product overview

Measure uptime, power and CO2 impact

Use logs, central monitoring, power consumption and CO2 analysis to document results.

Feature list

Trigger machine readiness from automation workflows

Use the available MCP Server for AI-driven WOL workflows where appropriate.

Downloads

Is Auto Shutdown Manager a finished tool or a custom project?

Auto Shutdown Manager is a ready-made Windows Service-based PC power management tool with standalone and client/server operation, central management, Wake-on-LAN features, reporting, WOL portals and deployment options.

How quickly can we evaluate Auto Shutdown Manager?

The Downloads page offers a free, full-featured Enterprise-Class 45-day trial. Use it with the ROI Calculator before wider rollout.

What makes Auto Shutdown Manager different from Windows power policies?

Windows power policies are useful, but ASDM adds central management, intelligent idle detection, business rules, warnings and document saving, Wake-on-LAN infrastructure, reporting and IT Asset Management.

Can Auto Shutdown Manager wake PCs across VLANs and remote sites?

Yes. ASDM supports local broadcasts, directed broadcasts and WOL Proxies, including WOL across IP segments, VLANs and the Internet where properly configured.

What is a WOL Proxy?

A WOL Proxy helps deliver Wake-on-LAN across local segments, VLANs, remote networks and Internet scenarios where a simple local broadcast is not enough.

Can users wake their own office PCs remotely?

Yes. ASDM provides free self-hosted WOL portals. The Advanced Portal supports Active Directory users and admin-assigned PC access.

Does Auto Shutdown Manager work with SCCM / Microsoft Endpoint Manager?

The feature list includes a MEM/SCCM Plug-In for integration into Microsoft Endpoint Manager / System Center Configuration Manager.

Does Auto Shutdown Manager support Modern Standby / S0 Low Power Idle?

The downloads page provides a Modern Standby Wake Driver for waking notebooks and PCs from Modern Standby / S0 Low Power Idle scenarios.

Will Auto Shutdown Manager interrupt users?

ASDM can check real activity such as applications, CPU/network/HDD activity, background processes, business times and user warnings before shutdown. Policies should be validated in your own environment before broad rollout.

How can we estimate the return on investment?

Use the ROI Calculator to estimate potential energy, cost and CO2 savings, then validate the assumptions with the 45-day Enterprise trial and ASDM reporting.

Is Auto Shutdown Manager affordable?

Auto Shutdown Manager is positioned as a cost-effective enterprise tool that can be tested before rollout. Licensing and exact pricing depend on your environment and edition.

START SMALL. SCALE SAFELY.

Estimate savings. Test the tool. Prove the result.

Use the ROI Calculator to estimate your potential energy, cost and CO2 savings, then validate Auto Shutdown Manager in your own IT environment with the 45-day Enterprise trial.

Calculate ROI Download 45-Day Enterprise Trial View Feature List

Platform · Idle Shutdown

Idle Shutdown for Enterprise Endpoint Power Management

Idle shutdown should not feel like a timer waiting to interrupt people. Auto Shutdown Manager by EnviProt helps IT determine whether a PC is genuinely idle using more than simple mouse and keyboard inactivity, while protecting users, scheduled work, open documents, maintenance windows and the ability to prove savings.

Real idle detection User-aware Maintenance-safe Central policy Savings proof

Download 45-Day Enterprise Trial View Feature List

Idle time is not the same as no keyboard input

A PC may be doing useful work even when nobody touches the mouse or keyboard.

Users still work outside normal hours

Late meetings, webinars, remote access and shift work can make fixed “closing time” rules risky.

Backups and scans need protection

Maintenance jobs can run long after business hours and should not be broken by a blunt shutdown rule.

Always-on becomes the workaround

When shutdown is unreliable, users and IT often choose the safe but expensive habit: leave PCs powered on.

01 · Detect

Define what counts as productive work

Idle rules can consider more than input activity, including workloads such as backups, virus scans, terminal sessions, network activity, printer queues and running processes.

02 · Protect

Prevent unwanted shutdowns

Shutdown decisions should respect productive time windows, active tasks, open documents and organization-specific exceptions so savings do not create support incidents.

03 · Prove

Show that runtime was reduced safely

Idle shutdown becomes easier to scale when IT can connect policy, endpoint behavior and savings proof instead of relying on assumptions.

Important condition

Idle shutdown must be safer than leaving PCs on.

If a shutdown policy interrupts useful work or risks open documents, users will fight it. A good policy starts with cautious rules, visible warnings where appropriate, automatic document saving where configured and validation in the real environment before broad rollout.

Review Maintenance Windows

Auto Shutdown Manager idle shutdown timer configuration screen — Product screenshot — Auto Shutdown Manager idle-shutdown timer configuration.

Warn before action

Give users a visible chance to understand what is about to happen where policy requires it.

Save open documents

Before shutdown, open documents can be saved automatically so idle shutdown does not become a lost-work event.

Respect exceptions

Protect productive tasks, maintenance work and endpoint groups that should not follow the default shutdown rule.

Typical Windows idle logic

“Has someone touched the PC?”

Useful for basic power settings, but too narrow for many enterprise machines, classrooms, labs, kiosks, production environments and maintenance workflows.

ASDM idle analysis

“Is this endpoint still doing useful work?”

ASDM can consider activity beyond mouse and keyboard input, so a PC is not treated as idle just because nobody is typing.

User and session signals

Mouse and keyboard activity, logged-on state and terminal sessions help distinguish absence from active or remote work.

Applications and services

Running applications, services, scheduled tasks, processes and their activity can prevent a false idle decision.

System workload

CPU load, HDD or disk utilization, memory usage and performance counters can show that the endpoint is still busy.

Network and device activity

Network traffic, printer queues and TCP/IP-enabled devices such as machines, multimedia equipment or other endpoints can be part of the shutdown decision.

Environment signal

Where configured, microphone-based volume detection can delay shutdown during calls, presentations or meetings. ASDM measures volume level only; it does not record, store or process sound data.

Admin takeaway

This is where ASDM leaves the “just Windows power settings” category.

The value is not only that ASDM can shut down idle PCs. The value is the broader decision before shutdown: users who work late, applications, performance, network dependencies, devices, sound level, time rules and document protection can all be considered where configured and validated.

View Manual

Policy flow

Keep PCs available, respect late work, then shut down only after useful work is finished.

After hours should not mean a hard cutoff. Time rules can define when idle shutdown is allowed to start working, but Auto Shutdown Manager by EnviProt can still respect users who continue working late, long downloads, active jobs, sessions or device dependencies. When useful work is finished and the endpoint is otherwise idle, documents can be saved and the configured power mode can be applied.

Conceptual diagram showing optional Wake-on-LAN start, protected core hours, flexible late-work handling, after-hours multi-signal idle analysis, productive job handling, document saving and safe shutdown into the configured power mode. — Conceptual process graphic — not a product screenshot. Shows how time rules, late-work flexibility, multi-signal idle analysis, document protection and the selected shutdown mode work together.

Operational requirement

Simple timer / script

Auto Shutdown Manager by EnviProt

Reduce avoidable runtime

Shut down PCs that are no longer doing useful work.

Usually based on a fixed time or a narrow trigger.

Combines schedules with idle detection and centrally managed policy.

Avoid user disruption

Do not interrupt active work, late meetings, remote activity or leave open documents unprotected.

Often lacks enough context to know whether work is still happening.

Allows policy to account for productive times, active tasks, defined exceptions and automatic saving of open documents before shutdown.

Protect background work

Backups, scans, queues and long-running tasks need protection.

May shut down while a productive background task is still running.

Can include process, load, session, network and scheduled-work signals in the idle decision.

Fit maintenance windows

Power savings should not break patching or planned IT work.

Shutdown and maintenance often become separate, conflicting jobs.

Connects shutdown policy with wake, maintenance availability and policy return.

Prove the result

IT leaders need measurable savings, not guesswork.

Usually difficult to connect with business-case reporting.

Supports the broader ASDM savings story across runtime reduction, reporting and ROI validation.

01

Choose a pilot group

Start with a department, site or endpoint group where work patterns and maintenance needs are well understood.

02

Validate idle rules

Check that productive tasks, scheduled work, remote access and user expectations are protected before scaling.

03

Expand by policy

Roll out by group, site or organizational unit when runtime reduction is predictable and support impact is acceptable.

Is this different from normal Windows power management?

Yes. Windows power management is useful for basic idle behavior, but ASDM can include a wider idle analysis: applications, services, performance counters, network activity, terminal sessions, printer queues, TCP/IP-enabled devices, time rules and optional volume-level detection. The exact policy should be configured and validated for the environment.

Is idle shutdown just a fixed shutdown schedule?

No. Fixed schedules can be useful, but the stronger approach is to combine schedules with idle detection and centrally defined exceptions. That is how power savings can coexist with real work patterns.

Can ASDM protect backups, scans and other background tasks?

Auto Shutdown Manager can use signals such as processes, services, system load, network activity, sessions, printer queues and backup or scan activity as part of the idle decision. The exact policy should be validated in your environment.

Does this replace Windows power management, GPO, SCCM/MECM or Intune?

No. Those tools can remain part of endpoint operations. ASDM adds the dedicated idle-shutdown, wake, maintenance and reporting layer around them.

Can users or departments have different rules?

Idle policies should reflect real work patterns. Productive time windows, endpoint groups, document-saving behavior and centrally managed rules can be used to avoid one-size-fits-all shutdown behavior.

What happens to open documents before shutdown?

Auto Shutdown Manager can save open documents automatically before shutdown. This should be part of a cautious rollout: define the policy, validate the behavior with real applications and make sure users understand what happens before broad deployment.

How should we start?

Start with a controlled pilot, choose conservative rules, validate user impact and only then expand by group, site or organizational unit.

Shut down safely. Wake reliably. Prove the savings.

Turn idle shutdown into a controlled endpoint power-management process.

Use Auto Shutdown Manager to reduce avoidable runtime without turning shutdown into a user disruption or a maintenance risk.

Download 45-Day Enterprise Trial Review Features

Auto Shutdown Manager · Remote Operations

Remote endpoint power control for managed IT operations

Give administrators one central way to shut down, restart, log off, hibernate, sleep or wake managed PCs — from planned fleet operations to direct support intervention and controlled remote availability.

Central admin actions Maintenance windows Remote wake-up Wake-on-WAN Tool WOL Portals ROI validation

Start 45-Day Enterprise Trial Estimate ROI

Windows, GPO, SCCM/MCM, Intune and scripts

These tools remain important for endpoint policy, deployment, compliance and administration. But they usually solve only parts of the power-state process: baseline settings, task execution, deployment timing or individual scripted actions.

Auto Shutdown Manager

ASDM adds the dedicated operating layer: safe shutdown rules, central remote actions, scheduled wake-up, Wake-on-LAN infrastructure, user self-service paths and reporting for energy, cost and CO₂ validation.

Prepare maintenance windows

Wake managed PCs before patching, inventory, backups or administrative checks so endpoint management tools can do their work.

Run group and site actions

Apply shutdown, restart, wake-up or logoff actions to selected groups, locations, departments, OUs or test sets from one managed workflow.

Support without walking to the desk

Use direct administrative actions when a specific endpoint must be restarted, logged off, powered down or woken for support or troubleshooting.

Reduce unnecessary runtime

Keep machines available when required, but avoid the default habit of leaving entire fleets powered on overnight.

Control remote availability

Wake selected office PCs for valid remote-access or maintenance scenarios without keeping entire fleets powered on permanently.

Keep the process auditable

Connect power actions to central management, reporting and ROI validation instead of undocumented manual work.

Auto Shutdown Manager context menu for wake, shutdown and remote actions — Direct administrative actions help IT control selected endpoints without desk-by-desk work.

Auto Shutdown Manager time rules for scheduled shutdown — Time rules align endpoint runtime with office hours, rooms, departments or known operating schedules.

Auto Shutdown Manager real-time actions for managed clients — Real-time actions support planned maintenance, support intervention and controlled shutdown after business hours.

Typical WoW scenarios

Home-office access to an assigned office PC.
Overnight maintenance access to a display PC, such as in airports or shop windows.
Rarely turned-on remote clients that must be available temporarily.

How the request is handled

The WoW request is sent to the ASDM Server. The final WOL-based wake command is sent from the server, not directly from the WoW client. The source PC and the target PC must both be valid ASDM clients of the server.

Auto Shutdown Manager Wake-on-WAN Tool — Wake-on-WAN Tool for selected remote-client wake-up scenarios. For regular user self-service, use ASDM WOL Portals.

Central admin operations

Use remote operations for shutdown, restart, logoff, sleep, hibernate, wake-up, scheduled actions and support intervention.

Enterprise Wake-on-LAN

Use the Wake-on-LAN infrastructure when the question is network delivery, WOL proxies, routed wake-up across VLANs, subnets or sites.

Explore Enterprise Wake-on-LAN

WOL Portals

Use WOL Portals for regular user self-service when authorized users should wake assigned office PCs under policy.

Explore WOL Portals

WoW Tool

Use the WoW Tool for specific remote-client scenarios such as home-office access to an office PC or temporary access to a rarely turned-on remote client.

ROI Calculator

Use the ROI Calculator when the question is business case, energy savings, cost savings and CO₂ estimate.

Estimate savings

Enterprise Trial

Validate shutdown behavior, wake reliability, maintenance windows and user exceptions in your own environment.

Download Enterprise Trial

Safer shutdown decisions

Use operating rules, schedules and exceptions so power-down is not just a blind command.

Reliable availability

Wake systems for users, maintenance or IT operations where hardware and network conditions allow it.

Measurable business case

Estimate and validate potential energy, cost and CO₂ savings instead of relying on assumptions.

Is this mainly for controlling one PC?

No. Single-PC actions are useful for helpdesk and troubleshooting, but the main value is central control over groups, schedules, sites, OUs, maintenance preparation and operational policies.

How does this complement SCCM/MCM, Intune or GPO?

Those tools remain important for endpoint management, deployment and baseline policy. ASDM adds the dedicated power-management layer: safe shutdown rules, scheduled wake-up, Wake-on-LAN infrastructure, portals and savings reporting.

How does ASDM avoid unsafe shutdowns?

ASDM should be configured with the organization’s operating rules: idle detection, user sessions, time rules, maintenance windows and exceptions. The objective is controlled shutdown, not blind power-off commands.

Does remote shutdown force applications to close?

When a remote shutdown is executed, running applications are closed. ASDM can be configured to save open documents before shutdown as part of the shutdown workflow, subject to the application behavior and the configured policy.

Can users wake their assigned office PCs?

Yes, where the organization deploys that workflow. For regular user self-service, ASDM WOL Portals are the preferred approach because access can be tied to assigned PCs and policy-controlled wake-up.

When should the WoW Tool be used?

Use the WoW Tool for specific remote-client scenarios, such as home-office access to an assigned office PC, overnight maintenance of a display PC or another rarely turned-on client that must be available temporarily. The request goes through the ASDM Server.

How should we evaluate this safely?

Start with a limited pilot: one department, one room, one site or a defined test group. Validate shutdown behavior, wake reliability, maintenance windows, user exceptions and savings assumptions in your own environment.

Shut down safely. Wake reliably. Prove the savings.

Use the Enterprise trial to validate central remote operations, scheduled wake-up, WoW/WOL Portal scenarios and savings estimates with your own endpoint policies and network design.

Start 45-Day Enterprise Trial Estimate ROI

Auto Shutdown Manager Wake-on-LAN

Enterprise Wake-on-LAN for routed networks

Wake PCs and endpoints across local subnets, VLANs and remote locations without turning every router into a special-case configuration project. Auto Shutdown Manager combines scheduled wake-up, manual remote wake, WOL proxies and client-side reliability settings in one central power-management workflow.

VLANs and routed subnets MCM/SCCM integration WOL proxy routing Self-service wake portals Client-side WOL repair

Explore routing options Improve WOL reliability

Trigger wake-ups from central workflows

Built-in Central Scheduler
XML Job File Scanner
Manual one-click Wake-on-LAN from the console
MCM/SCCM plugin integration

Reach clients beyond the local subnet

Local subnet broadcasts
Directed broadcasts where permitted by security policy
WOL proxy routing for remote locations
Remote WOL address and port configuration

Reduce client-side WOL failures

Helps configure Wake on Magic Packet
Helps handle Windows Fast Startup related WOL issues
Policy-based client settings
Hardware, firmware and network policy may still apply

Enterprise Wake-on-LAN architecture showing Schedule, File Scanner XML jobs, Console or CLI, SCCM or MECM, WOL Portal and Remote Work triggers, routed through the ASDM Server to managed endpoints — Central wake-up control with local routing options for remote network segments.

Enterprise principle: keep Wake-on-LAN inside the management workflow instead of relying on manual support actions and undocumented network exceptions.

Method A

WOL Proxy routing

Place an existing endpoint, server, virtual machine or small Linux relay device — for example a Raspberry Pi in a branch office or remote VLAN — in the target subnet and use it as the local WOL sender. The server communicates with the proxy, and the proxy sends the wake packet inside the local network segment. This avoids broadcast forwarding changes in many deployments.

Works well for routed VLANs and branch locations
Can use lightweight relay devices such as a Raspberry Pi where a full server or VM is not practical
Reduces dependency on router-specific broadcast configuration
Can be managed through the Auto Shutdown Manager workflow

Open WOL Proxy Generator details

Auto Shutdown Manager WOL proxy configuration screen

Method B

Directed broadcast, with static ARP where needed

For remote networks without an assigned WOL Proxy, Auto Shutdown Manager can use directed broadcasts automatically where the network and security policy allow routed broadcast forwarding. This normal directed-broadcast path does not require a manual Remote WOL Address / Port entry.

Where the network and security policy allow it, routers can be configured to forward controlled WOL traffic to a target broadcast address. Static ARP is only needed in special router topologies where a broadcast target must be mapped deliberately.

Special case: router static ARP / broadcast target

configure
set protocols static arp 192.168.20.254 hwaddr FF:FF:FF:FF:FF:FF
commit
save

Auto Shutdown Manager remote WOL address and port configuration — Remote WOL address and port configuration for routed wake-up scenarios.

Special-case override

Remote WOL address / port for routers without remote broadcast support

Use a manual Remote WOL Address / Port entry only for special cases, for example when a router cannot forward remote broadcasts directly and the wake packet must be sent to a configured static-ARP or broadcast target.

For normal directed-broadcast routing, this manual override is not required. For multiple clients, apply remote WOL address and port settings in bulk only where the same special topology is shared.

Wake-on-LAN depends on more than the server. Endpoint firmware, NIC driver settings, Windows Fast Startup, sleep or shutdown state and network policy can all affect whether a client wakes successfully.

Auto Shutdown Manager helps reduce these failures by managing supported client-side WOL settings centrally, including Wake on Magic Packet related settings and Windows Fast Startup handling where supported.

Important: Some devices may still require BIOS or firmware configuration. Wake-on-LAN cannot be guaranteed on unsupported hardware or networks where wake traffic is blocked by policy.

Patch windows and maintenance

Wake endpoints before planned maintenance, updates or software distribution windows.

Branch offices and routed VLANs

Reach endpoints in distributed network segments using proxy or routed WOL approaches.

Labs, classrooms and shared workstations

Prepare PCs before users arrive, then return them to power-saving policies afterwards.

Remote support and helpdesk wake-up

Allow support workflows to bring managed devices online when intervention is needed.

Energy management

Combine scheduled startup with shutdown policies to support predictable endpoint availability.

Self-service wake portals

Provide controlled wake-up options through portal workflows where this is part of the deployment.

Do I need a physical WOL Proxy in every VLAN?

No. A physical device is not required in every VLAN. Depending on your topology, you can use an existing endpoint, server, virtual machine or small Linux relay device in the target network segment. The important point is that the proxy can send the wake packet locally inside the subnet where the target PCs are located.

What is the difference between WOL proxies and directed broadcasts?

Directed broadcasts depend on network devices forwarding wake traffic toward a target subnet or broadcast address. A WOL proxy avoids that router-side broadcast dependency by placing a relay inside the target network segment. The better option depends on your routing design, security policy and operational preference.

Can Auto Shutdown Manager combine WOL proxies and directed broadcasts?

Yes. Auto Shutdown Manager can use both approaches in the same environment. If a WOL proxy is configured for a remote network, wake requests can be routed through that proxy. For remote networks without a configured WOL proxy, ASDM can fall back to directed-broadcast or remote-WOL-address based wake-up routing according to the configured network settings and security policy.

Can I use a Raspberry Pi as a Wake-on-LAN proxy?

Yes. A Raspberry Pi or another small Linux-based relay can be a practical option for branch offices, remote VLANs or locations where running a full server or virtual machine is not necessary. It should still be managed like any other infrastructure component: documented, monitored and placed in the correct target network segment.

How does Auto Shutdown Manager integrate with SCCM or Microsoft Configuration Manager?

Auto Shutdown Manager can support managed wake-up workflows around software deployment and maintenance windows. In environments using SCCM or Microsoft Configuration Manager, this helps align endpoint availability with scheduled updates, deployments and administrative tasks.

Managed endpoint availability

Make Wake-on-LAN part of managed endpoint power control

Use Auto Shutdown Manager to schedule, route and troubleshoot Wake-on-LAN from the same management environment used for endpoint power policies.

Read the technical manual Explore SCCM integration

Reporting, Power and CO₂ Analysis

Show what changed, not just what was configured

Runtime and uptime visibility

Cost, energy and CO₂ estimates

Source-aware savings proof

Reporting inside the ASDM management console

From raw runtime data to management-ready evidence

Who uses the reports?

IT administrators

IT leadership

Finance and procurement

Sustainability teams

Reports document results from your environment.

Reporting & CO₂ questions

Turn endpoint power management into measurable evidence.