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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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 .

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...