Power Chute shutdown over network

[Anonymous user]

Hello, I'm having an issue with Power chute shutting down over a network, my setup is as follows

Smart-UPS 2200 connected to the network to 4 PCs (windows 7) also connected to the network. 

Power chute is setup and configured throughout all the PCs, everything is good and they can see each other and the UPS, its a beautiful thing

Each PC runs a software that controls our plant called Sattline (and old product from ABB), so the way it works is that you have to log in with administrator credentials and shut it down using the prompts in the pull down menu. I developed a script through a program using a program called Perfect Automation (www.perfectautomation.com) which generates and exe file. It does all the accessing the pull down menus using the generated script.  I have tested it using command line and it works fine, log in and then calls the shutdown of the sattline program and exits to the windows desktop. 

My issues is, in the power chute  software, under configure events. I have it configured to "Runtime  remaining below threshold" and "UPS on Battery", we tested and it didn't seem to call the script. I then did some more research and found that it should be calling a command file then the command file should call the exe. So we tried that and it still doesn't call the script file.

Ideally what I want to happen is, if there is a instance where there is a power loss and PC's switch to the UPS for power then Powerchute should call the script and gracefully exit the Sattline program before the UPS shuts down the PCs 

Any assistance on this would be greatly appreciated 

thanks in advance 

[BillP · Accepted solution]

Hi,

PowerChute is running on the system as a service and based on Windows security settings is running in session zero. In earlier versions of Windows all services run in Session 0 along with applications. This situation poses a security risk. In Windows Vista, and later versions of Windows, the operating system isolates services in Session 0 and runs applications in other sessions. PowerChute is run in Session 0 so if a command file launches a .exe that .exe will be launched in Session 0 and not visible to the logged in users. To verify that the .exe has launched open Task Manager and review the list of Processes running. More information on Windows Session can be found at http://blogs.technet.com/b/askperf/archive/2007/04/27/application-compatibility-session-0-isolation...

A work around can be found in this forum thread posted by Kennath on 4/26/2015

https://community.exchange.se.com/t5/Datacenter-Forum/bd-p/datacenter-forum