DE 
EN Home-office access
An employee can request an authorized office PC before starting the normal remote connection.
Remote Work Without Leaving Office PCs Running 24/7
Solutions · Remote Work / Wake-on-Demand
Remote Work Without Leaving Office PCs Running 24/7
Auto Shutdown Manager (ASDM) by EnviProt adds controlled wake availability to the remote-work process. Authorized employees or support staff can wake permitted office PCs through a self-hosted WOL Portal, then use the organisation’s existing VPN, Remote Desktop, VDI or remote-support tools for the actual session. Endpoints can remain shut down when they are not needed instead of running continuously just in case.
Authorized target lists
SAML SSO or portal login
AD and portal assignments
ASDM Server wake execution
Enterprise WOL infrastructure
Return to power policy
The availability problem
Remote access tools can connect to an office PC. They cannot connect while it is unavailable.
VPN, Remote Desktop, VDI and support tools handle the remote session. They do not by themselves solve the endpoint power-state problem. Wake-on-demand lets IT separate availability from permanent runtime: keep the office PC off when it is not needed, then make it available for an approved remote-work request.
After-hours work
A permitted endpoint can be made available when business access is needed outside its normal runtime.
Helpdesk support
Support staff can assist with a controlled wake request when self-service is not suitable.
Distributed locations
The same managed wake infrastructure can support routed networks, branch sites and other configured locations.
The complete user journey
Authenticate, resolve the allowed PCs, wake the selected endpoint, then connect normally.
The portal controls the wake request. The ASDM Server performs Wake-on-LAN through the configured enterprise wake path. The organisation’s existing remote-access stack continues to control the actual user session.
Step 1
Authenticate
The user signs in through the configured SAML 2.0 flow or through a portal-managed login.
Step 2
Resolve authorized PCs
The portal builds the allowed-target list from Active Directory assignments, portal-managed assignments or both.
Step 3
Select and submit Wake
The user chooses an allowed endpoint and submits the wake request from the portal.
Step 4
ASDM performs Wake-on-LAN
The ASDM Server sends the request through the configured local, proxy, routed or Wake-on-WAN path.
Step 5
Connect through the existing stack
After the endpoint becomes available, the user connects through VPN, RDP, VDI, remote support or another approved solution.
Step 6
Return to policy
After remote use, configured ASDM runtime, idle and shutdown rules can apply again when endpoint conditions permit.
Controlled assignment models
IT decides which users can see and wake which endpoints.
The Advanced WOL Portal can use an Active Directory-first model, direct portal administration or a hybrid of both. The assignment model changes how the allowed-PC list is built; it does not change the ASDM wake path behind the portal.
SAML SSO + Active Directory
Use the authenticated corporate identity and maintain primary user-to-PC assignments in Active Directory where that model is configured.
Portal-managed users and PCs
Manage portal accounts, roles and direct PC assignments inside the portal for non-SSO environments or separate operational workflows.
Hybrid: AD first, portal exceptions
Keep normal office-PC assignments in Active Directory while granting selected users additional lab, shared or exceptional systems through portal administration.
Plan Active Directory integration as an infrastructure change.
Where AD-based assignments are used, validate the attribute design, permissions, replication and rollback approach in a test environment before production rollout. Direct portal assignments remain available where an AD extension is not the preferred model.
Product proof
The user sees permitted targets and receives feedback after submitting Wake.
These are real Advanced WOL Portal screens. They show the controlled target list and the wake-request result without turning this solution page into a second portal manual.
Clear responsibility boundaries
ASDM provides controlled wake availability. Your remote-access platform provides the session.
Keeping these responsibilities separate makes the architecture easier to evaluate: the portal and ASDM decide whether an authorized endpoint should be made available; the existing access stack remains responsible for secure connectivity and user-session controls.
WOL Portal + ASDM wake layer
- Identify the portal user through the configured login flow
- Resolve the endpoints that user is permitted to wake
- Forward the selected request to the ASDM Server
- Perform Wake-on-LAN through the configured enterprise infrastructure
- Allow configured power policies to apply again afterwards
Existing remote-access and security layer
- VPN, RDP, VDI, remote support or application access
- Remote-session authentication and authorization
- Transport security and access logging
- Endpoint protection, patching and hardening
- Application and data-access policy
Why the workflow needs a dedicated wake layer
Remote access solves the connection. ASDM closes the endpoint-availability gap around it.
The operational requirement is not just to send a Magic Packet. IT needs controlled assignments, a workable path through real networks and a way to avoid permanent runtime once remote access is no longer needed.
Requirement
Expose only permitted endpoints
Self-service wake must not become unrestricted access to arbitrary company systems.
Common gap
Remote-session rights do not automatically define wake rights
A VPN or RDP entitlement does not by itself build the portal list of PCs a user is allowed to wake.
ASDM role
Resolve an authorized target list
Use Active Directory assignments, portal-managed assignments or both to build the permitted-PC workflow.
Requirement
Reach the target network segment
The request may need to reach another VLAN, routed site or WAN-connected location.
Common gap
A basic WOL packet may stop at the network boundary
Broadcast assumptions often fail across segmented enterprise networks without a suitable delivery design.
ASDM role
Use the configured enterprise wake path
ASDM can use local WOL, WOL Proxy, routed or Wake-on-WAN patterns where the environment is designed and configured for them.
Requirement
Avoid permanent always-on runtime
Remote availability should not require every office PC to remain powered around the clock.
Common gap
Always-on becomes the fallback when wake is unreliable
Teams may leave endpoints running to avoid a failed remote-access start, even when the PCs are rarely needed.
ASDM role
Wake when needed, then return to policy
After the session, configured idle, runtime and shutdown policies can apply again when user and endpoint conditions permit.
The building blocks
Use the ASDM components that match your users and network topology.
This solution page connects the complete remote-work workflow. The linked Platform and Solutions pages provide the deeper product and architecture detail for each layer.
WOL Portals
Self-hosted user and helpdesk wake workflows with controlled assignments, optional SAML SSO and direct portal administration.
WOL Proxy & Wake-on-WAN
Managed wake delivery for segmented networks, VLANs, sites and other routed environments.
Enterprise Wake-on-LAN
The broader wake infrastructure, monitoring and availability patterns behind managed endpoint wake-up.
Remote PC Power Control
The separate IT-admin workflow for centrally waking, restarting or shutting down managed endpoints.
Validate the complete path, not only the portal screen.
Wake behaviour depends on compatible endpoint hardware, firmware and adapter settings, the current power state, network routing, the configured ASDM wake method and organisational policy. Pilot representative users, endpoints and network segments before wider rollout.
Important boundary
Wake-on-demand is not a remote desktop or endpoint-security product.
The WOL Portal provides controlled wake availability. It does not replace VPN, RDP, VDI, remote-support or endpoint-security systems. Authentication, secure remote sessions, endpoint protection, patching and hardening remain separate responsibilities. Power management is not a security product, although reducing avoidable endpoint runtime can support a smaller operational exposure window.
FAQ
Common questions about remote work and wake-on-demand
Does ASDM replace our VPN, Remote Desktop or VDI platform?
No. ASDM handles controlled endpoint wake availability. Your existing VPN, RDP, VDI, remote-support or application-access solution continues to handle the remote session.
Can users wake only the PCs assigned to them?
The Advanced WOL Portal resolves the targets a signed-in user is permitted to wake from Active Directory assignments, portal-managed assignments or both. The exact rights depend on the configuration chosen by IT.
How can IT manage normal assignments and exceptions?
Primary office-PC assignments can remain in Active Directory where that model is configured. Additional lab, shared or exceptional targets can be assigned directly in the portal, creating an AD-first hybrid model.
Does every VPN automatically provide SAML single sign-on to the portal?
No. SSO applies when the corporate VPN or access flow and the WOL Portal are configured with the SAML 2.0 identity provider. The complete claims and portal integration must be validated in the customer environment.
Can the wake request cross VLANs or reach another site?
Yes, where the appropriate local WOL, WOL Proxy, routed or Wake-on-WAN method is configured and the endpoint hardware, network design and security policies support it.
What happens after the remote-work session ends?
The endpoint can return to the configured ASDM runtime, idle or shutdown policy once the relevant user activity, application and endpoint conditions permit.
Remote availability without permanent runtime
Test the portal, assignments, wake path and existing remote-access connection in your own environment.
Start with representative users, office PCs and network segments. Validate authentication, authorized targets, Wake-on-LAN delivery, the remote session and return-to-policy behaviour before expanding the rollout.
Enterprise Green IT Solutions: Optimized Power Management & Energy Savings
Solutions · Enterprise IT
Enterprise endpoint power management for real IT operations
Auto Shutdown Manager (ASDM) by EnviProt helps enterprise IT teams turn endpoint power control into a managed workflow: shut down safely, wake reliably, support maintenance and remote work, and prove the savings without building another script project.
Safe shutdown
Enterprise Wake-on-LAN
WOL Proxy / Wake-on-WAN
WOL Portals
SCCM/MCM-friendly operations
ROI and CO₂ proof
The enterprise problem
Power saving fails when shutdown, wake and proof are handled separately
Most enterprises already have Windows, Group Policy, Microsoft Configuration Manager, Intune and scripts. The gap appears when endpoint power state becomes a daily operating process across users, maintenance windows, routed networks, remote access and management reporting.
Machines stay on “just in case”
PCs are often left running because IT cannot risk missing maintenance, remote access or support availability. That protects availability, but it also wastes runtime.
Wake-up becomes unreliable at scale
Wake-on-LAN that works in one subnet can fail across VLANs, sites, routers and firewalls unless the wake path is designed as an enterprise workflow.
Scripts become ownership risk
One-off shutdown and wake scripts can work for a while, then become hard to maintain, document, hand over and prove to management.
Visual quick scan
Keep Microsoft endpoint tools. Add the power and wake operating layer.
ASDM does not replace endpoint management. It connects the operational layer around power policy, user safety, wake routing, maintenance readiness, remote availability and savings proof.
Operating model
Where existing tools stop and the ASDM operating layer connects the workflow
Enterprises can keep their Microsoft endpoint tools and still add one coordinated layer for shutdown, wake, maintenance readiness, remote availability and savings proof.
Existing stack
Policy, configuration and deployment
Windows settings, GPO, SCCM/MCM, Intune and scripts remain useful for configuration, compliance, deployment and administration.
Operating gap
Runtime decisions across real users and networks
IT still has to decide when shutdown is safe, when wake-up is required, how remote sites are reached and how savings are proven.
ASDM layer
Shut down safely. Wake reliably. Prove the savings.
ASDM brings shutdown, wake, portals, maintenance windows and reporting into one ready-made enterprise power-management workflow.
ASDM answer
What the enterprise layer adds
The value is not one magic button. It is the operational connection between safe shutdown, reliable wake-up, user protection, maintenance and proof.
User-aware safe shutdown
ASDM helps avoid disruptive shutdowns by considering user activity, configured schedules and operational conditions before power policies take effect.
Explore idle shutdownEnterprise Wake-on-LAN
Central wake requests can be delivered across routed environments using the appropriate wake path for the network design.
Explore Enterprise Wake-on-LANWOL Proxy and Wake-on-WAN
For remote segments and sites, ASDM supports managed wake delivery patterns instead of relying on ad-hoc router exceptions alone.
Explore WOL ProxyWOL Portals for remote users
Authorized users and helpdesk workflows can wake assigned office PCs without leaving machines powered on permanently.
Explore WOL PortalsMaintenance-window readiness
ASDM can help keep endpoints available for patching, scans and support work, then return them to power-saving policy afterwards.
Explore maintenance windowsReporting, ROI and CO₂ proof
Enterprise power management needs proof. ASDM reporting helps estimate, validate and communicate runtime, cost and CO₂ impact.
Calculate ROIOperational exposure reduction
ASDM does not harden endpoints or replace security tools. It can support exposure reduction by helping avoid unnecessary endpoint runtime when devices are not needed.
See Microsoft complement positioningMicrosoft fit
Designed to complement SCCM/MCM, Intune and Group Policy
Enterprise IT does not need another tool that pretends the rest of the stack does not exist. ASDM fits beside Microsoft endpoint management and closes the dedicated power-and-wake process around it.
SCCM / Microsoft Configuration Manager
Configuration Manager can support deployment and maintenance scenarios. ASDM adds the daily power-state workflow around shutdown reduction, wake availability and maintenance readiness.
Explore SCCM/MCM integrationIntune and Group Policy
Intune and GPO are useful for configuration and policy. ASDM adds runtime decisions, user protection, wake routing and savings proof where a dedicated operating layer is required.
Compare native tools and ASDMEnterprise value
One workflow for admins, IT leaders and management proof
For IT admins
Reduce repeated troubleshooting around sleep states, wake paths, late users, maintenance availability and script exceptions.
For IT leaders
Move from scattered policies and scripts to a repeatable operating model that can be piloted, documented and scaled.
For CxO and procurement
Support cost, energy and CO₂ goals with a measurable enterprise tool instead of a long custom project.
Reduce avoidable runtime exposure
Power management is not a security product. But unnecessary runtime can mean unnecessary exposure. ASDM can help reduce avoidable endpoint runtime while preserving wake-up and maintenance availability.
Rollout path
Start small. Validate in your environment. Scale safely.
Endpoint power management depends on real users, real network paths and real maintenance routines. A pilot should prove savings and availability before broad rollout.
1. Pilot a representative group
Select departments, device types and remote segments that reflect your actual operating model.
2. Validate wake and shutdown rules
Check user protection, maintenance availability, Wake-on-LAN paths and exception handling before expanding scope.
3. Prove and scale
Use reporting and ROI estimates to communicate results, then expand policies and wake workflows across more groups.
FAQ
Questions enterprise IT teams ask first
Does ASDM replace SCCM/MCM, Intune or Group Policy?
No. ASDM complements Microsoft endpoint management. SCCM/MCM, Intune and GPO remain useful for configuration, deployment and policy. ASDM adds the dedicated endpoint power and wake workflow around those tools.
Will users be interrupted by shutdown policies?
The goal is controlled, user-aware shutdown, not forced interruption. Policies should be configured and validated in your environment so active users, approved exceptions and maintenance tasks are respected.
Can ASDM wake PCs across VLANs, routed networks and remote sites?
ASDM supports enterprise wake scenarios including WOL Proxy and Wake-on-WAN patterns. Wake success still depends on endpoint hardware, firmware, power state and the available network path.
How does ASDM help with remote work?
WOL Portals can let authorized users wake assigned office PCs when needed, while IT keeps the wake workflow controlled instead of leaving PCs running all the time.
Can ASDM support maintenance windows?
Yes. ASDM can help align endpoint availability with patching, scans and administrative routines, then return devices to power-saving policy after the work is complete.
Is ASDM a security product?
No. ASDM is not an endpoint security product and does not replace endpoint protection, patching or hardening. It can help reduce unnecessary endpoint runtime while preserving wake-up and maintenance availability.
How should an enterprise start?
Start with the 45-day Enterprise Trial, choose a representative pilot group, validate wake reliability and user protection, then use reporting and ROI estimates to decide how to scale.
Can shutdown policies reduce operational exposure?
They can support it, but only as a secondary operational benefit. Power management is not endpoint security. However, if a PC does not need to run overnight or over a weekend, reducing that unnecessary runtime can also reduce unnecessary exposure while patching, endpoint protection and hardening remain separate responsibilities.
Enterprise trial
Turn endpoint power control into a managed enterprise workflow
Use the 45-day Enterprise Trial to validate safe shutdown, reliable wake, maintenance availability and reporting in your own environment.
Advanced Green IT Power Management for Governments, and Education
Solutions · Public sector & education
Endpoint power management for schools, campuses and public-sector IT
Auto Shutdown Manager (ASDM) by EnviProt helps education and public-sector IT teams reduce avoidable PC runtime, keep classrooms and offices ready, wake devices for maintenance, and prove savings without building another script project.
Shut down safely. Wake reliably. Prove the savings.
Safe shutdownEnterprise Wake-on-LANWOL Proxy / Wake-on-WANWOL PortalsMaintenance windowsROI & CO₂ proof
The public-sector IT conflict
Devices should be off to save energy — but awake when students, staff and updates need them
In schools, universities, municipalities and public agencies, endpoint power management fails when shutdown, wake-up, maintenance and reporting are handled as separate tasks.
Classrooms and labs must be ready
Students and staff expect PCs to work at the start of the day. A pure “shut everything down” approach creates friction unless wake-up is managed reliably.
Patch nights collide with energy goals
Leaving PCs on just in case wastes energy. Turning them off without a wake strategy can break maintenance windows and increase manual IT work.
Campuses and sites are routed
VLANs, subnets, branch buildings and distributed campuses make basic Wake-on-LAN unreliable unless the wake path is designed for real networks.
Fast scan
One operating layer for shutdown, wake, maintenance and proof
ASDM connects the daily power workflow around existing endpoint-management tools: Shut down safely. Wake reliably. Prove the savings.
ASDM answer
What ASDM adds to public-sector and education IT operations
Microsoft tools remain valuable. ASDM adds the dedicated endpoint power-and-wake layer that many environments otherwise try to build with scripts, scheduled tasks or manual procedures.
Safe shutdown policies
Shut down unused PCs with rules designed around real users, labs, libraries, shared devices and administrative workstations.
Enterprise Wake-on-LAN
Wake PCs before classes, office hours, patch windows or support sessions so systems are ready when needed.
WOL Proxy / Wake-on-WAN
Support wake-up across routed networks, VLANs and distributed sites where basic broadcast-based Wake-on-LAN is not enough.
WOL Portals and helpdesk wake
Give authorized users or support teams controlled ways to wake assigned PCs without opening broad admin access.
Maintenance-window readiness
Keep devices available for updates and other maintenance work, then return them to the intended power state afterwards.
Reporting, ROI and CO₂ proof
Provide evidence for IT leadership, budget discussions and sustainability reporting instead of relying on assumptions.
Microsoft fit
Complements SCCM/MECM, Intune and Group Policy — it does not replace them
Public-sector IT teams often already have mature Microsoft tooling. ASDM should sit next to that stack as the operational power-and-wake layer, not compete with it.
For SCCM / MECM maintenance
Use Configuration Manager for software deployment and updates. Use ASDM to help devices be awake for the operational window and powered down when the work is done.
For Intune, Group Policy and scripts
Keep policy and configuration management where it belongs. Use ASDM for the recurring power workflow: safe shutdown, reliable wake, portals and proof.
Where it fits
Built for shared devices, distributed sites and accountable IT budgets
The strongest public-sector case is not “turn PCs off.” It is controlled endpoint availability with measurable energy, cost and CO₂ evidence.
Schools and classrooms
Wake labs before lessons and shut down shared PCs after use, while keeping exceptions possible for exams, open days or after-hours work.
Universities and campuses
Coordinate labs, libraries, offices and distributed buildings across routed networks without relying on one-off local scripts.
Municipal and public administration
Reduce avoidable runtime across large PC fleets while preserving supportability, maintenance access and operational oversight.
Proof points
Historical education references — useful proof, not current guarantees
These references are intentionally framed as older proof points. They show that ASDM has been used in education and campus-like environments, but savings, licensing and rollout assumptions still need to be validated in the customer’s current environment.
Mesquite Independent School District
The MISD case study describes a school-district environment with 8,500 PCs across 47 campuses, including coordination with Microsoft SCCM for updates and central power control.
Open school district case studyUC Berkeley / LoCal project
An ENERGY STAR-published historical case reference describes ASDM in the UC Berkeley LoCal power monitoring and conservation project. Treat it as a campus research proof point, not as a current savings guarantee.
Open ENERGY STAR case referenceHerricks Union Free School District
The ASDM brochure describes a school-district classroom scenario where teacher workstations needed controlled logoff and shutdown behavior between classes.
Open ASDM brochureOsnabrück University of Applied Sciences
The ASDM brochure describes a higher-education deployment focused on saving energy, conserving resources and reducing cost without disrupting daily work.
Open ASDM brochureProcurement and proof
Pilot first, validate savings, then scale with evidence
Public-sector adoption needs a cautious path: evaluate in a representative environment, validate wake and shutdown behavior, and use reporting for budget and sustainability conversations.
Representative pilot
Start with a mix of labs, offices and distributed sites. Validate shutdown rules, wake reliability and maintenance-window behavior before broad rollout.
Download 45-Day Enterprise TrialDocumented education references
Use existing education references as proof material, then validate the operational and savings assumptions in your own environment.
Open school district case studyProcurement-ready evidence
Bring measured runtime, energy, cost and CO₂ evidence into budget discussions instead of selling a technical feature list alone.
Calculate ROISecurity guardrail
Unnecessary runtime can mean unnecessary exposure
ASDM is not an endpoint security product and does not replace patching, endpoint protection or hardening. But unnecessary runtime can mean unnecessary exposure. Public-sector PCs that do not need to run overnight or over weekends do not need to stay unnecessarily exposed either.
FAQ
Questions public-sector and education IT teams usually ask
Does ASDM replace SCCM/MECM, Intune or Group Policy?
No. ASDM complements those tools. SCCM/MECM, Intune and Group Policy remain responsible for configuration, policy and deployment. ASDM adds the dedicated workflow for safe shutdown, reliable wake, maintenance availability, WOL Portals and savings proof.
Can PCs still wake for patching and maintenance?
Yes. Devices can be planned around maintenance windows and then returned to the intended power state after the work is complete, where hardware and network conditions allow.
Can this work across campuses, VLANs and routed networks?
ASDM can use WOL Proxy and Wake-on-WAN concepts for environments where basic local broadcast wake-up is not enough. The exact design should be validated against your network topology.
Can helpdesk or remote users wake PCs?
WOL Portals can provide controlled wake options for authorized users or support staff, depending on how the environment is configured.
Will shutdown policies interrupt students or staff?
The goal is controlled shutdown, not blind shutdown. Rules should be piloted with representative users, device types and schedules so labs, libraries and offices remain usable.
Is this a security product?
No. Power management is not endpoint security. But reducing unnecessary runtime can reduce unnecessary exposure. Patch management, endpoint protection and hardening remain separate responsibilities.
How should a public-sector organization start?
Start with a 45-day trial in a representative pilot group. Validate wake reliability, user impact, reporting, ROI assumptions and maintenance-window behavior before scaling.
Are public-sector, education or non-profit terms available?
Current licensing and procurement terms should be confirmed directly with EnviProt. The page should not rely on old pricing assumptions without current proof.
Start controlled
Validate the power and wake workflow before scaling it across your institution
Run a focused trial, calculate the savings potential, and discuss licensing or rollout questions with Sales.