Skip to main content

Estimating the Run Time for Various Power Options with PowerShell

For my fellow Network Administrators out there, I know you have heard this time and time again.  “Why can’t my battery last longer?”  Well first off, stop playing games.  Second, lets take a look at your Power Options.  You may have various Power Options already programmed into your laptop.   The question now is, how long will my laptop run on each plan?  The following script will only give you an estimated time in minutes that the laptop will remain on while on battery.  You have to remember that if all of the sudden you change work loads, your system will shut down sooner or last longer.  At least you will have an idea of which option will provide the longest battery life based on your laptops current work load.

To get this information, I looked at two WMI libraries; Win32_Battery and Win32_PowerPlan.  The Win32_PowerPlan allows us to collect a list of all configured PowerPlans through the property ElementName.  It also lets us know which one was originally active so we can set it back at the end of the script through the IsActive property. We can use the objects created from this WMI library to set the active power plan with the Activate method.

Win32_Battery gives us the current battery estimated lifetime in minutes through the EstimatedRunTime property.  What I have discovered through testing is that it is best to wait 3 seconds before sampling the estimated battery life. This provides a better estimated time.

Remember to unplug the laptop from external power before proceeding.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

# First detect if the laptop is on battery

 

# This will only allow the script to proceed if the laptop

# is either fully changed and not plugged in, or is

# not in danger of losing power.

$AcceptableBatteryStatus = 1,3

 

If ((Get-CimInstance -ClassName Win32_Battery).BatteryStatus -in $AcceptableBatteryStatus)

{

    # Get all PowerPlans

    $PowerPlans = Get-CimInstance -Namespace "root\CIMV2\power" -ClassName Win32_PowerPlan

 

    # Get the current PowerPlan

    $Current = $PowerPlans |

        Where-Object IsActive -eq $True

 

    # Get a list of all PowerPlans names

    $PPNames = $PowerPlans |

        Select-Object -ExpandProperty ElementName

 

    # Go through each Power Plan and set each one. Then collect

    # estimated runtime information.

   

    $Data = @() # Holds the retuned time estimates.

 

    $NumOfPlans = $PowerPlans.count

    $Count = 0

 

    $Data += ForEach ($PP in $PPNames)

    {

        $Count++

        Write-Progress -Activity "Testing Power Plans" `

                       -PercentComplete (($Count/$NumOfPlans)*100) `

                       -SecondsRemaining (($NumOfPlans+1-$Count)*3)

       

        $PowerPlans |

            Where-Object ElementName -eq $PP |

            Invoke-CimMethod -MethodName Activate |

            Out-Null

 

        # Pause for 3 seconds so the power usage can be estimated.

        Start-Sleep -Seconds 3

 

        Write-output (Get-CimInstance -ClassName CIM_Battery |

            Select-Object -Property EstimatedRunTime,

            @{N="PowerPlan";E={$PP}})

 

    }

    # Reset the origional Power Plan.

    Invoke-CimMethod -InputObject $Current -MethodName Activate | Out-Null

 

    $Data | Where EstimatedRunTime -ne $Null |

        Sort-Object -Property EstimatedRunTime -Descending

} # END: If ((Get-CimInstance -ClassName Win32_Battery).BatteryStatus -in $AcceptableBatteryStatys)

Else

{

    Write-Output "System on AC Power.  Unplug the power cable."

}

 

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.