Training Scenario for Power Management - Power policy configuration and deployment

Version 7

    Verified Product Versions

    LANDESK Management Suite 9.5LANDESK Management Suite 9.6LANDESK Management Suite 2016.x


    The purpose of this document is to take you through a simple scenario of the deployment and use of LANDESK Power management within a simple test environment of a core and a single test machine. It is recommended that you perform this in a virtual environment, so if you wish to repeat any actions, you can do so easily by using a virtual snapshot and rolling back to it.

    I will be using some information from the help pages to help with this as well.


    Pre-requisites for this Scenario:

    A core to test with. This can be a production one, however,  a test one is recommended.

    A test client machine to test with. A physical one is ideal as you be able to test the power management Wake-on-LAN functionality but a virtual machine will work just as well.



    =========================================Start Here=========================================


    Basic use of Power management and deployment

    First things first:

    Before we go ahead and deploy a power management  we need to create a power manager policy:

    Create a power management policy


    Once you have done this you can either deploy this new power management as part of an agent configuration as below:

    agent power management option.png

    Select Power management in the Agent compionent to install


    agent power management option2.png

    Then select power management in the side column (1), tick the use power policy on client option (2) and select the policy you just created (3)


    Or use the information from the help page here to deploy the power policy to a machine which already has the power management component installed on them.

    Deploy a power management policy


    Once you have deployed the power policy onto the client you can check that its been installed by checking the inventory of the machine.

    Read this article on the differences between power management being installed and not

    Where is the Ivanti Power Policy information stored in Inventory?


    Once installed we will now go through the various methods we can use to remove it. This can be for a number of reasons. For example, You wish to change the power policy in use, a presentation machine keeps logging off, you wish to remove power policy to troubleshoot etc


    This article contains the information you need to do this :

    How to turn off Ivanti Power Management on a client or group of clients


    Along with this help file URL page,

    Remove a power management policy


    Once removed using your preferred method redeploy ready for the next part of the training.

    If you wish to find out more about how the power management policies are applied to the client machine in more detail, read this article for a more detailed explanation of the deployment and setting of the power management setting on the client:

    About Ivanti Power Management


    Advanced use and deployment of Power Management

    In the next steps we are going to look at the finer points of the power management


    For this next part we will be looking at the settings located in this locations:

    agent power management advanced options.png



    Read the following page from the help site to get an overview of these settings

    Managing applications that conflict with power policies

    A detailed explanation for each setting can be found under these setting. This is particular hard to train with as predicting issues in advance can be impossible to duplicate.

    It is recommended that you become familiar with these settings for any future issues regarding this deployment of the power policy.


    Once you have imported or created these settings for the 'process-sensitive triggers and processes to terminate at shutdown these can be added to the power policy within the areas indicated below.


    Console component areaArea in Power Policy configuration
    process sesnstive trigger list core.pngprocess sesnstive trigger list client.png
    end process list.pngend process client.png


    Finally in these options you have the option to ignore any reoccurring alert log which has been resolved or has been accounted for.


    Identify processes to ignore in exception (alert) logsAlert log in power management component
    processe to ignore.pngalert logs core.png


    WOL - Wake On LAN


    One more feature to learn about and most probably the best ones you will have as an IT administrator or manager of an environment. With this feature you can turn on your machines or servers at certain times overnight and have them patching automatically or performing other maintenance task on the machines. These will save on down time as you will be able to patch client machines during the night when they are not in use instead of during the day distributing them and upsetting your client base. You can also use this feature to turn the machines on in the morning ready for the clients to use so there is no waiting for the machines to load or complaints at slow bootup times.


    This setting needs to be turned on here in the power policy:

    wol option in power policy.png


    And options configured on the main power configuration window of the power policy here:

    wol option in power policy2.png

    More infomation oninformationworks can be found here in this detailed article:

    How does the Power Management "Turn On" task work?

    and on the help pages here


    Your Turn:

    Test this with you test machine setting the power off to the hour you are currenlty on and the wake up to the next hour. Please be aware that this will not work on a virtual machine machine as the 'Turn on' functionlaity configures the BIOS to turn the machine on.

    If this is not possible from your client machine then you will have to use the remote wake up feature loacted here in the power management window:

    schedule wol.png

    A more detailed explanation as to why this maybe an issue and the alternive method can be found on this artilce:

    How does the Power Management "Turn On" task work?

    And on the help pages here.