Quantcast
Channel: Ivanti User Community : Document List - Power Management
Viewing all 68 articles
Browse latest View live

How to remove a LANDesk Power Management Scheme

$
0
0

LDMS 9.0 has a removal task that can be created

 

pmremove.png

 

Turn power management off globally or by group

 

 

 

 

This article describes how to remove a LANDesk 8.8 Power Management Policy from a client computer.

 

Understanding the processes that LANDesk Power Management uses will make it easier to understand the removal process.

 

For details about how Power Management works, see How Power Management Works.

 

 

There are two options to remove the LANDesk Power Policy.

 

Option 1:

 

Redeploy the LANDesk Management Suite agent with the component "Power Management" unchecked.   This will remove the LANDesk Power Management Component and set the client Power Scheme back to the default Windows policy.   However, to use LANDesk Power Management again in the future, the Agent must be reinstalled with the Power Management component option.

 

Option 2:

 

In order to remove the LANDesk Power Policy and Scheme and return control over to the standard Windows Power Schemes, the Local Scheduler Policy must be removed, and a different power scheme set as the active scheme.

 

In order to remove the Local Scheduler Policy, the command "PWMCFG /CLEAR_SCHEDULE" must be run.

 

In order to change the active power scheme from the LANDesk PWM Scheme to another scheme, the Windows powercfg.exe command must be run.

 

 

This can be easily scripted using LANDesk Scripts or Batch files.

 

In either case, the script or batch file should be edited to suit your needs.

 

A seperate script for Windows XP and Windows Vista clients may be necessary as the PowerCFG.exe utility in Windows Vista differes from the PowerCFG.EXE utility in Windows XP.

 

Examples of batch files follow:

 

Windows XP

@echo off
REM - XP Power Management Rollback

"C:\Program Files\LANDesk\LDClient\PWMCfg.exe" /clear_schedule

C:\windows\system32\powercfg /setactive "Home/Office Desk"

 

Windows Vista

@echo off
REM - Vista Power Management Rollback

"C:\Program Files\LANDesk\LDClient\PWMCfg.exe" /clear_schedule

C:\windows\system32\powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

 

Examples of LANDesk Scripts follow:

 

 

 

Windows XP


[MACHINES_WIN]

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\PWMCfg.exe<qt/> /clear_schedule

REMEXEC2=C:\windows\system32\powercfg /setactive "Home/Office Desk"

 

 

Windows Vista

 

[MACHINES_WIN]

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\PWMCfg.exe<qt/> /clear_schedule

REMEXEC2=C:\windows\system32\powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

 

Note: These batch files and scripts need to be run as the local user, as the power scheme settings are set per user.

 

 

After removing a power scheme, if you go back to the regular Windows Power Scheme, the inventory information for the power scheme may not display correctly in inventory until after a sync inventory scan is run.   A regular inventory scan will process changes however it will not remove data.

InventoryInformation.png

In the example above, the area circled in red shows the inventory information for a LANDesk Power Policy - the last deployed date, and the last deployed policy name.

 

If the power settings gathered by inventory do not show the area circled in red and simply show the settings below this area, this is the default Windows power policy information.

 

When removing a LANDesk Power Scheme and going back to a default Windows Power Scheme, the area circled in red will not be updated until a full sync inventory scan is run.   This can be done by adding a "/sync" at the end of the inventory scanner command line.


Created a power policy with a 'turn on' time but the machine never turns on.

$
0
0

Question:  A Power Management Policy has been created which includes a 'turn on' time for all machines.  Although the time has been designated, not all machines are turning on at the given time, why?

 

Answer:  Power Management schedules a machine power on through the machine's bios.  If a machine's bios does not have the ability to have scheduled wake up events or cannot schedule those events through Windows, then the turn on event will remain unscheduled and the machine will not turn on at the designated time.  Possible resolution for this is to enable Plug and Play bios in the bios of the machines, enable events in the bios, or update the manufacturer bios if necessary.  Some system manufacturers and bios' do not support this feature at all.  In that situation, a scheduled task for wake on lan can be used to power on machines at a specific time.

What are the files associated with LANDesk Power Management?

$
0
0

Question:  What are the files on the client and core that are associated with LANDesk Power Management and what function do they perform?

 

Answer:  The answer is written in the bulleted list below:

 

Client:

  • ClientSideEnableWOL.vbs:  Enables the WOL functionality of the client system if it can be enabled.
  • GetInputInfo.exe:  Obtains the input information from the system.
  • ldiscn32.exe:  Collects the current power scheme, deployed power policy information, and time zone data with the inventory scan.
  • LocalWakeUp.exe:  Wake the system up from sleep mode when enabled.
  • poweroff.exe:  Shutdown or reboot the system
  • PWMCfg.exe:  Setting the power of the system.
  • PWMCfg64.exe:  Setting some values of power in a 64 bit system.
  • PWMClientUsageAnalyzer.exe:  Collects and uploads the usage of the client to the core server.
  • PWMProcScipt.ini:  Process list for process-sensitive triggers
  • PWMReservedList.ini:  The ignored process list when sending the insomnia alert.
  • PWMScript.ini:  The power policy that is deployed to the client.
  • PWMWakeUpScript.ini:  The local wake up schedule file.
  • ProcTriggerSvc.exe:  Monitors the CPU, network, and input information to keep the system alive, or terminate processes and send insomnia alerts.
  • tracksvc.exe:  Records the usage and power state of workstation.

Core:

  • PowerManagement.asmx:  Web Service that loads under core.anonymous and allows for reporting of all client usage data.

Database Tables:

  • Computer:  List of all LANDesk Managed Nodes.
  • ConsoleUser:  Users who are allowed to login and perform operations within the LANDesk consoles.
  • CompSystem:  One to One relationship with the computer table.  System information for each computer stored here.
  • PWM_POLICY_DEF:  Policy information is stored in this table.
  • PWM_SCHEME_DEF:  Scheme information is stored in this table.
  • PWM_POLICY_SCHEME_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_SCHEME_DEF
  • PWM_CUSTOM_WATTAGE_DEF:  User defined definition of wattage usage contained with a computer.
  • PWM_BASE_SCHEME_DEF:  Unique entry for each computer.  First information for power state of computer including monitor, disk, system standby, and hibernate.  Stored via inventory scan.  This information is used as base line for each system when generating the savings report.
  • PWM_PROCESS_DEF:  Lists all processes that will be used by a process sensative trigger.
  • PWM_POLICY_PROCESS_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_PROCESS_DEF.
  • PWM_END_PROCESS:  Lists all process that will be ended when there is insomnia.
  • PWM_POLICY_END_PRO_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_END_PROCESS.
  • PWM_CLIENT_INFO:  Client information of Power Management. Inventory Information seen in the tree of the console.
  • PWM_WEEKLY_USAGE:  Keeps the user usage data (active or idle) from each computer, each day.
  • PWM_WEEKLY_HISTORY:  Keeps the time of every power state from each computer, each day.
  • PWM_GROUP_INFO:  Keeps the cost of every group.
  • PWM_IGNORE_PROCESS:  Lists all processes that will be ignored by the insomnia alert viewer.
  • PWM_DETECTABLE_PROCESS:  Lists all processes from received insomnia alerts.
  • PWM_USER_RECORD:  Keeps the last policy and current user operating
  • PWM_RECORD_GROUP_REL:  Relationship between user records and group records.

 

If Power Management is failing to report data accurately or is not showing a process list, the first step to take is verify the correct executables are installed and operational on the client.  Checking the appropriate tables within the database can ensure that the data is being received by the core server.  By default, the local scheduler on each client is setup to run the process for sending up Power Management data once a day when the Power Management client is installed and usage data is collected.  The Power Management web service runs anonymously so there is no need for authentication when the clients report data up.  If user authentication is denied in the web service logs, then there is a security issue or a web site configuration issue that must be addressed to fix the problem.

How does the LANDesk Management Suite Power Management Saving report work to generate the savings numbers and how is the defaultusagetable.xml generated?

$
0
0

Question:  How does the LANDesk Management Suite Power Management Saving report work to generate the savings numbers and how is the defaultusagetable.xml generated?

 

Answer:

 

LDMS 8.8:

 

The defaultusagetable.xml in LDMS 8.8 is standard and non editable through the console UI.  Users can edit the file through Notepad.exe or another like editor but that is advanced work and a backup should be made before attempting this.  The end result file must always be named defaultusagetable.xml or it will not be used by the report in LDMS 8.8.  This file represents the usage of the computers in the group for the whole week.

 

The savings report refers to the base line (defaultusagetable.xml) of each machine, and the applied power policy for the calculated savings report.

 

By default, the xml file has no record for saturday and sunday in the file.  That was by design.  It is editable and other days can be copied to the Saturday and Sunday spots encorportating data for those days.  If work hours must be expanded or Turn on and Turn off times must be changed for example, then the file is editable as well.  Once again, when editing the defaultusagetable.xml, take a backup and make sure that the file to be used is named defaultusagetable.xml.

 

LDMS 9.0:

 

The defaultusagetable.xml is based upon computer data gathered by power management tools on the clients.  An example would be something like this after removing the XML tags:

DayOfWeek name="Monday"

"Inactivity" at="0001" duration="6091"

DayOfWeek name="Tuesday"

DayOfWeek name="Wednesday"

DayOfWeek name="Thursday"

DayOfWeek name="Friday"

"Inactivity" at="0535" duration="1437"

 

Because the machines in this case were inactive for most of the week, the inactive timer was started on Monday at 001 (24 hours) and carried through for 6091 or all the way through Friday sometime and then became inactive again at 0535.  There was no need for any other entries in the file because there was no further activity and the machine stayed inactive for the remainder of the time.  There is a warning often that pops up stating there is no data for entire days of the week when attempting to create the defaultusagetable.xml.  It means that the computer started idle at the beginning of the usage period and remained idle for a long period during the sample time.  The data is accurate, there is just not a lot there.  If a user wants to generate their own data driven xml, they must rename it to defaultusagetable.xml in order for it to be used in report calculation.

 

The defaultusagetable.xml in LDMS 9.0 is also editable by hand.  Inactivity is determined by screen saver, mouse and keyboard movement and input responses received from the machine via power management tools at the workstation level.

8.8 SP4 Power Management - Wake Up Scheduled Tasks don't work if a non-standard WOL port is assigned.

$
0
0

Subject

In LANDesk Management Suite 8.8 you can configure the settings and change the default Wake On LAN (WOL) port to use when running WOL Tasks.  This is normally used when port 0 is blocked by the Network Administration group.  Right-Click functions and directed WOL requests will work over the specified port.  When a Power Management Wake up task is created, the new scheduled task will run but the machine will not wake up.

 

Cause

This issue is caused by the Global Scheduler sending to port 0 regardless of the specialized settings.

 

Resolution

Patch PAT-4913888.4 resolves this issue.

Savings Report Data is incorrect in LDMS 8.8 SP4

$
0
0

Issue:  When altering the DefaultUsageTable.xml file and running the Savings Report in LDMS 8.8 SP4 the savings report does not always come out as accurately as it should.

 

Cause:  Some data was missing/skipped in the DefaultUsageTable.xml

 

Fix:  Call LANDesk Customer Support and request PWM-5033888.4.zip

Power Management Policy calls for hibernate but machines are never hibernating.

$
0
0

Issue:  The power management policy created calls for hibernation after a specified time but the machines are never going into hibernation.  The issue is not insomnia.  Further investigation reveals that hibernation is not available in the control panel even though it should be.

 

Cause:  The wrong powermanagement driver is installed for the machine chipset rendering hibernation unavailable.

 

Resolution:  Obtain the chipset driver from the Manufacturer of the machines in question and install it to obtain hibernation settings for machines.

What is the difference between the "Hard" and "Soft" turn off options in Power Manager?

$
0
0
Question:
What is the difference between the "Hard" and "Soft" turn off options in Power Manager?
The main difference between soft shutdown and hard shutdown is that the soft shutdown will wait for the current logon user’s response to the confirmation of the end session message.

 

Soft shutdown is as same as using the Windows “shutdown.exe” without “-f” option or clicking on Start --> Shutdown.

 

Soft Shutdown
This launches the command "C:\Windows\System32\poweroff.exe /SOFT 30" on the client.   This activity can be seen in the PWMCFG.EXE.LOG file on the client.
PowerOffMessage.png
1. Asks the client user if he wants to shutdown now and
wait for 30 seconds.
a. User selects “shutdown” and then the computer will shut down.
b. User selects “cancel” and then the computer will not shut down.
c. Timeout and then the computer will shut down.

 

After A. or C. a call for a soft shutdown is sent to the operating system.

 

Soft shutdown process:
a. Windows O.S. informs all programs that it will close the session.
b. Programs asks the user when it need user to confirm any unsaved data.
     i. User selects “save” and then the program responds “shut down” to the Windows
     ii. User selects “don’t save” and then the program will send “shut down” to Windows
     iii. User selects “cancel” and then the program sends “Don’t shut down” to Windows
     iv. Wait for user’s response when the workstation is not locked.
     v. Wait for user’s response with a timeout when the workstation is locked. Stop the shutdown process if there is no response.
*Note: Soft shutdown cannot work successfully, if any program hangs during the shutdown process. (For Windows XP and all
versions prior to Windows XP)
Hard Shutdown
This launches the command "C:\Windows\System32\poweroff.exe /FORCE 30" on the client.   This activity can be seen in the PWMCFG.EXE.LOG file on the client.  After the 30 second timeout, a shutdown is forced.   This is not graceful, and any unsaved changes will be lost.
PowerOffMessage.png
1. Informs the user that a Countdown to System Shutdown has begun and gives them the option to Shutdown immediately or Cancel
a. User selects “shutdown” and the computer will shut down.
b. User selects “cancel” and the the computer will not shut down.
c. Timeout and the computer will shut down.
To configure the shutdown delay:
poweroff-delay.png
1. Click on Options
2. Set the "Delay shutdown for second(s)." to the desired value.
The shutdown message presented to the user is also not configurable, but will likely be changed in a future release.

Is the 30 second countdown timer for the Power Management "Hard" Turn Off configurable?

$
0
0

Question:

 

When the "Hard" Turn Off option is selected and the shutdown takes place on the client, the user is presented with the following dialog:

 

PowerOffMessage.png

 

This dialog defaults to a 30 second countdown.   Is this time configurable?

 

Answer:

 

To configure the shutdown delay:
poweroff-delay.png
1. Click on Options
2. Set the "Delay shutdown for second(s)." to the desired value.

How LANDesk Power Management Works

$
0
0

LANDesk clients that have the Power Policy Agent installed have several files in their LDCLIENT directory:

 

 

 

PWMCFG.EXE and PWMScript.ini

 

 

NOTE:LANDesk Power Management is an added feature that comes with LDMS 8.8 SP2.   However, simply installing the SP2 patch to clients does not add the Power Management Agent and pushing Power Policies to clients that do not have the Power Management Agent installed will result in an error message along the lines of "There was an error launching the task on the client".   In order to implement Power Management, you must push an Agent Configuration with the Power Management option checked in the Agents section.

 

 

 

When you create a power policy on the Core Server and then push that policy down to a client, several things take place.

 

 

 

A task is created in the local scheduler to run PWMCFG.EXE /SET.   Each hour the Local Scheduler runs PWMCFG /SET which evaluates the contents of PWMScript.ini and then does one of the following depending on Operating System to create and/or change power policy settings:

 

Windows 2000/XP/Server2003

 

The following registry keys are modified:

 

1.      CurrentPowerPolicy 

HKEY_USERS\[Windows User Security Identifier]\Control Panel\PowerCfg\

2.      Name, Description and Policies

HKEY_USERS\[Windows User Security Identifier]\Control Panel\PowerCfg\PowerPolicies\[Policy index]

3.      LastID

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg

4.      Policies

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg\PowerPolicies\[Policy index]

5.     Policies

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg\ProcessorPolicies\[Policy index]

(everything but Windows 2000)

 

Windows Vista/Server2008/7

 

Power Management functions are manipulated directly as detailed here:

http://msdn.microsoft.com/en-us/library/aa373163(VS.85).aspx

 

 

 

 

 

The contents of PWMScript.ini look something like this:

 

 

Sunday=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

Monday=0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0,0:3:30,0;

Tuesday=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

Wednesday=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

Thursday=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

Friday=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

Saturday=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

 

 

In the actual script it is all on one line, but I have moved each day to a seperate line for clarity.

 

 

My entry for Monday tells me that I have myComputerset toHibernateafter30minutes of inactivity every other hour.  (12am, 2 am, 4 am, etc)

 

 

Each slot between commas relates to an hour period during the day, starting with 12am and ending at 11pm.

 

 

If I had the following settings in a power scheme:

 

 

Hibernate | Computer | After 10 Mins | Plugged In | Mon | 8 am

Standby | Computer | After 5 mins | Plugged In | Mon | 8 am

Turn off | Computer | Hard | Mon | 9 am

Turn off | Computer | Soft | Mon | 10 am

Turn off | Monitor | After 1 min | Plugged In | Mon | 8 am

Turn off | Hard Disks | After 3 mins | Plugged In | Mon | 8 am

 

 

The resulting line in the PWM file for Monday (as I have set all the events for Monday) would look like this:

 

 

Monday=0,0,0,0,0,0,0,0,0:3:10@0:2:5@0:1:1@0:5: 3,4,6,0,0,0,0,0,0,0,0,0,0,0,0,0

 

 

Which says at 8amHibernate the Computerafter10minutes of activity and (@)Standby the Computerafter5Minutes of inactivity and (@)Turn off the Monitorafter1minute of inactivity, andTurn off the Hard Disksafter 3 minutes of inactivity.

 

 

So the following values specify the device and action:

 

 

1 - Monitor : Turn Off

2 - Computer : Standby

3 - Computer : Hibernate

4 - Computer : Hard Turn Off

5 - Hard Disks : Turn Off

6 - Computer : Soft Turn Off

 

 

 

These options use the POWERCFG.EXE standard Windows Utility to change the LANDesk PWM Scheme to reflect the current hours settings.  This is the real intrinsic value of the LANDesk Power Management feature to add Chronological Variability to the Power Schemes.

 

 

NOTE:This is set for the currently logged in user.   If you log off of the current user and in with another user, the power settings will not change for that user until the next allotted time hits and the local scheduler applies the LANDesk PWM Scheme.

 

 

 

At 9 am (the number 4) do a hard shutdown of the computer.

 

At 10 am do a soft (the number 6) shutdown of the computer.

 

 

 

If the PWMCFG utility sees the number 4 in the spot for the current hour it will spawn the LANDesk Shutdown Utility (poweroff.exe located in C:\Windows\System32) with a 30 second countdown with the option to cancel.  If the countdown expires, it shuts the computer off without closing any programs, etc.   This is a hard shutdown.

 

 

 

If the PWMCFG utility sees the number 6 in the spot for the current hour it will spawn the Windows utility "shutdown.exe".   This is the same as if you went to the Start Menu and chose "Shutdown".   If there are open programs it will prompt to save.   If there are other users logged into the computer it will warn that others users are logged in, etc.

 

To configure the shutdown delay see this document: How to Configure the Power Off Delay

 

For schemes that include a "Turn On" option, a separate task is created on the core server and a Wake On LAN Packet is sent to the computer at the designated time.   This is controlled purely on the Core Server side and there are no files or settings sent to the client.

 

 

 

 

Another Tip: In the Power Savings report, at times you may notice that it reports negative values.

 

 

 

The reason this may happen is that the current power settings for the computer(s) in the target query are gathered and stored in the Inventory.   We do not compare the Power Policy settings with an arbitrary number.   We compare the Power Policy settings you intend to push to the client to the current Power Policy in place on the computer.   If for example you set your Power Policy to simply turn off the Monitor and Hard Disks after X amount of minutes, but the existing policy in place on the computer (Windows policy or LANDesk policy, either way) puts the computer into Hibernate or Standby, that would save more power than the Monitor and Hard disks only.

 

 

 

The power policy settings are stored in the Inventory under "Power Management".   If you have an existing LANDesk Power policy you will see "Last Deployed Date" and "Last Deployed Policy".  Along with the current settings. If the system has never had a LANDesk Power Policy deployed, you will simply see the current policy settings.   In either instance you will see what the current settings are as follows:

 

 

 

System Hibernate AC

System Hibernate DC

System standby AC

System standby DC

Turn off hard disk AC

Turn off hard disk DC

Turn off Monitor AC

Turn off Monitor DC

Disable Power Management Via Policy LDMS 9.5

$
0
0

You can create a batch file to schedule as a policy using the commands listed below. It will set the Power Management settings back to what they were prior to deploying the LANDesk Power Policy.

 

cd %LDMS_LOCAL_DIR%

cd ..

pwmcfg.exe /disable

LANDesk Management Suite 9.5 power management documentation

$
0
0

Power management policy set to None

$
0
0

Environment:

LDMS95

 

Description:

You decide to select power management policy in your agent configuration. Since you have not yet defined Power management policy you choose to select " None"

 

powerM.PNG

 

After deploying your agent we notice that a Power management policy is applied to workstations

 

Reason:

If you select " None" the default Power management policy will be deploy with the agent.

 

Solution:

If you plan to use Power management policy in a later time leave the "use power policy on client" clear

What is new in LANDesk Management Suite v9.0 Power Management

$
0
0

See the attached pdf for a description of what is new in LDMS 9.0 power management.

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

$
0
0

Power Management in LDMS 8.8 SP2 uses only WOL.

 

Power Management in LDMS 8.8 SP3 uses WOL and AMT (VPro).

 

Both methods can be used to wake a computer from a Hibernate, Standby, or Power Off State.

 

When using WOL, the Power Management "Turn On" task functions in the same way as right-clicking a computer in the Management Console and selecting "Wake up".

 

However, the scheduled task that the Core Server runs always sends the WOL packet from the core server.   Right-clicking a computer from a Remote Console and selecting "Wake Up" will send the packet from the remote console.   So you may notice times that the Scheduled Task from the core server does not work, and the Right-click "Wake up" option does work, or vice/versa.

 

A broadcast WOL packet is sent from the core server to the target node.

 

Routers in the environment must be configured to pass WOL (Wake On LAN) packets for the Core Server to be able to wake clients on subnets that are on the remote side of the router.

 

The remote computer must also have Wake On LAN capability for this to work properly.

 

This activity can be viewed in the console log in \Program Files\LANDesk\ManagementSuite\Console.exe.log.

 

 

 

Example:

 

7/16/2009 5:11:36 PM : WakeOnLan.Wakeup(): Sending Packet - ipAddress = 192.168.000.045, subnetAddress = 255.255.255.000, macAddress = 000C29B6B108, port = 0

 

This packet is generally sent to the first bound adapter as gathered by the LANDesk Inventory.

 

This shows in the Inventory Tree for a client here:

 

[ComputerName]

             |
     [Network]

             |
       [TCPIP]

             |

[Bound Adapter]

             |

   [IP Address]

 

 

 

Note: When scheduling a Power On task from the Power Manager Tool, it will initially create a task called the name of the Power Scheme name.   After the task has been successfully deployed to a target node, a second task called "Power Scheme Name (power on)" will appear.   This will run regularly on the Core Server according to the schedule set in the Power Policy.

 

A common problem with the Power On task, is if the "Wake up devices - does not apply to unmanaged devices" options gets checked in the Task Properties. This will wake the computer and immediately turn it back off. This is because the default behavior for this wake up option will return the computer to the state it was originally in.

 

WOLcheckbox.png

 

This box must remain unchecked.

 

The Turn On task has a hard-coded wake up function in it, so checking the "Wake up devices" option is not necessary, and as stated, will turn the computer back off.

 

For general wake-on-lan (WOL) information and LANDesk Management Suite, see this article.


32-bit Console clears Power Management Policy when saving Agent Behavior

$
0
0

Issue:

Power Policies are disappearing.

32-bit Console clears Power Management Policy when saving Agent Configuration.

 

Resolution:

Apply patch PWM-4290790.0

How to remove a LANDesk Power Management Scheme

$
0
0

LDMS 9.0 has a removal task that can be created

 

pmremove.png

 

Turn power management off globally or by group

 

 

 

 

This article describes how to remove a LANDesk 8.8 Power Management Policy from a client computer.

 

Understanding the processes that LANDesk Power Management uses will make it easier to understand the removal process.

 

For details about how Power Management works, see How Power Management Works.

 

 

There are two options to remove the LANDesk Power Policy.

 

Option 1:

 

Redeploy the LANDesk Management Suite agent with the component "Power Management" unchecked.   This will remove the LANDesk Power Management Component and set the client Power Scheme back to the default Windows policy.   However, to use LANDesk Power Management again in the future, the Agent must be reinstalled with the Power Management component option.

 

Option 2:

 

In order to remove the LANDesk Power Policy and Scheme and return control over to the standard Windows Power Schemes, the Local Scheduler Policy must be removed, and a different power scheme set as the active scheme.

 

In order to remove the Local Scheduler Policy, the command "PWMCFG /CLEAR_SCHEDULE" must be run.

 

In order to change the active power scheme from the LANDesk PWM Scheme to another scheme, the Windows powercfg.exe command must be run.

 

 

This can be easily scripted using LANDesk Scripts or Batch files.

 

In either case, the script or batch file should be edited to suit your needs.

 

A seperate script for Windows XP and Windows Vista clients may be necessary as the PowerCFG.exe utility in Windows Vista differes from the PowerCFG.EXE utility in Windows XP.

 

Examples of batch files follow:

 

Windows XP

@echo off
REM - XP Power Management Rollback

"C:\Program Files\LANDesk\LDClient\PWMCfg.exe" /clear_schedule

C:\windows\system32\powercfg /setactive "Home/Office Desk"

 

Windows Vista

@echo off
REM - Vista Power Management Rollback

"C:\Program Files\LANDesk\LDClient\PWMCfg.exe" /clear_schedule

C:\windows\system32\powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

 

Examples of LANDesk Scripts follow:

 

 

 

Windows XP


[MACHINES_WIN]

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\PWMCfg.exe<qt/> /clear_schedule

REMEXEC2=C:\windows\system32\powercfg /setactive "Home/Office Desk"

 

 

Windows Vista

 

[MACHINES_WIN]

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\PWMCfg.exe<qt/> /clear_schedule

REMEXEC2=C:\windows\system32\powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

 

Note: These batch files and scripts need to be run as the local user, as the power scheme settings are set per user.

 

 

After removing a power scheme, if you go back to the regular Windows Power Scheme, the inventory information for the power scheme may not display correctly in inventory until after a sync inventory scan is run.   A regular inventory scan will process changes however it will not remove data.

InventoryInformation.png

In the example above, the area circled in red shows the inventory information for a LANDesk Power Policy - the last deployed date, and the last deployed policy name.

 

If the power settings gathered by inventory do not show the area circled in red and simply show the settings below this area, this is the default Windows power policy information.

 

When removing a LANDesk Power Scheme and going back to a default Windows Power Scheme, the area circled in red will not be updated until a full sync inventory scan is run.   This can be done by adding a "/sync" at the end of the inventory scanner command line.

Created a power policy with a 'turn on' time but the machine never turns on.

$
0
0

Question:  A Power Management Policy has been created which includes a 'turn on' time for all machines.  Although the time has been designated, not all machines are turning on at the given time, why?

 

Answer:  Power Management schedules a machine power on through the machine's bios.  If a machine's bios does not have the ability to have scheduled wake up events or cannot schedule those events through Windows, then the turn on event will remain unscheduled and the machine will not turn on at the designated time.  Possible resolution for this is to enable Plug and Play bios in the bios of the machines, enable events in the bios, or update the manufacturer bios if necessary.  Some system manufacturers and bios' do not support this feature at all.  In that situation, a scheduled task for wake on lan can be used to power on machines at a specific time.

What are the files associated with LANDesk Power Management?

$
0
0

Question:  What are the files on the client and core that are associated with LANDesk Power Management and what function do they perform?

 

Answer:  The answer is written in the bulleted list below:

 

Client:

  • ClientSideEnableWOL.vbs:  Enables the WOL functionality of the client system if it can be enabled.
  • GetInputInfo.exe:  Obtains the input information from the system.
  • ldiscn32.exe:  Collects the current power scheme, deployed power policy information, and time zone data with the inventory scan.
  • LocalWakeUp.exe:  Wake the system up from sleep mode when enabled.
  • poweroff.exe:  Shutdown or reboot the system
  • PWMCfg.exe:  Setting the power of the system.
  • PWMCfg64.exe:  Setting some values of power in a 64 bit system.
  • PWMClientUsageAnalyzer.exe:  Collects and uploads the usage of the client to the core server.
  • PWMProcScipt.ini:  Process list for process-sensitive triggers
  • PWMReservedList.ini:  The ignored process list when sending the insomnia alert.
  • PWMScript.ini:  The power policy that is deployed to the client.
  • PWMWakeUpScript.ini:  The local wake up schedule file.
  • ProcTriggerSvc.exe:  Monitors the CPU, network, and input information to keep the system alive, or terminate processes and send insomnia alerts.
  • tracksvc.exe:  Records the usage and power state of workstation.

Core:

  • PowerManagement.asmx:  Web Service that loads under core.anonymous and allows for reporting of all client usage data.

Database Tables:

  • Computer:  List of all LANDesk Managed Nodes.
  • ConsoleUser:  Users who are allowed to login and perform operations within the LANDesk consoles.
  • CompSystem:  One to One relationship with the computer table.  System information for each computer stored here.
  • PWM_POLICY_DEF:  Policy information is stored in this table.
  • PWM_SCHEME_DEF:  Scheme information is stored in this table.
  • PWM_POLICY_SCHEME_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_SCHEME_DEF
  • PWM_CUSTOM_WATTAGE_DEF:  User defined definition of wattage usage contained with a computer.
  • PWM_BASE_SCHEME_DEF:  Unique entry for each computer.  First information for power state of computer including monitor, disk, system standby, and hibernate.  Stored via inventory scan.  This information is used as base line for each system when generating the savings report.
  • PWM_PROCESS_DEF:  Lists all processes that will be used by a process sensative trigger.
  • PWM_POLICY_PROCESS_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_PROCESS_DEF.
  • PWM_END_PROCESS:  Lists all process that will be ended when there is insomnia.
  • PWM_POLICY_END_PRO_REL:  Keeps the relationship between PWM_POLICY_DEF and PWM_END_PROCESS.
  • PWM_CLIENT_INFO:  Client information of Power Management. Inventory Information seen in the tree of the console.
  • PWM_WEEKLY_USAGE:  Keeps the user usage data (active or idle) from each computer, each day.
  • PWM_WEEKLY_HISTORY:  Keeps the time of every power state from each computer, each day.
  • PWM_GROUP_INFO:  Keeps the cost of every group.
  • PWM_IGNORE_PROCESS:  Lists all processes that will be ignored by the insomnia alert viewer.
  • PWM_DETECTABLE_PROCESS:  Lists all processes from received insomnia alerts.
  • PWM_USER_RECORD:  Keeps the last policy and current user operating
  • PWM_RECORD_GROUP_REL:  Relationship between user records and group records.

 

If Power Management is failing to report data accurately or is not showing a process list, the first step to take is verify the correct executables are installed and operational on the client.  Checking the appropriate tables within the database can ensure that the data is being received by the core server.  By default, the local scheduler on each client is setup to run the process for sending up Power Management data once a day when the Power Management client is installed and usage data is collected.  The Power Management web service runs anonymously so there is no need for authentication when the clients report data up.  If user authentication is denied in the web service logs, then there is a security issue or a web site configuration issue that must be addressed to fix the problem.

How does the LANDesk Management Suite Power Management Saving report work to generate the savings numbers and how is the defaultusagetable.xml generated?

$
0
0

Question:  How does the LANDesk Management Suite Power Management Saving report work to generate the savings numbers and how is the defaultusagetable.xml generated?

 

Answer:

 

LDMS 8.8:

 

The defaultusagetable.xml in LDMS 8.8 is standard and non editable through the console UI.  Users can edit the file through Notepad.exe or another like editor but that is advanced work and a backup should be made before attempting this.  The end result file must always be named defaultusagetable.xml or it will not be used by the report in LDMS 8.8.  This file represents the usage of the computers in the group for the whole week.

 

The savings report refers to the base line (defaultusagetable.xml) of each machine, and the applied power policy for the calculated savings report.

 

By default, the xml file has no record for saturday and sunday in the file.  That was by design.  It is editable and other days can be copied to the Saturday and Sunday spots encorportating data for those days.  If work hours must be expanded or Turn on and Turn off times must be changed for example, then the file is editable as well.  Once again, when editing the defaultusagetable.xml, take a backup and make sure that the file to be used is named defaultusagetable.xml.

 

LDMS 9.0:

 

The defaultusagetable.xml is based upon computer data gathered by power management tools on the clients.  An example would be something like this after removing the XML tags:

DayOfWeek name="Monday"

"Inactivity" at="0001" duration="6091"

DayOfWeek name="Tuesday"

DayOfWeek name="Wednesday"

DayOfWeek name="Thursday"

DayOfWeek name="Friday"

"Inactivity" at="0535" duration="1437"

 

Because the machines in this case were inactive for most of the week, the inactive timer was started on Monday at 001 (24 hours) and carried through for 6091 or all the way through Friday sometime and then became inactive again at 0535.  There was no need for any other entries in the file because there was no further activity and the machine stayed inactive for the remainder of the time.  There is a warning often that pops up stating there is no data for entire days of the week when attempting to create the defaultusagetable.xml.  It means that the computer started idle at the beginning of the usage period and remained idle for a long period during the sample time.  The data is accurate, there is just not a lot there.  If a user wants to generate their own data driven xml, they must rename it to defaultusagetable.xml in order for it to be used in report calculation.

 

The defaultusagetable.xml in LDMS 9.0 is also editable by hand.  Inactivity is determined by screen saver, mouse and keyboard movement and input responses received from the machine via power management tools at the workstation level.

Viewing all 68 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>