Blog Posts tagged with K1000 Monitoring

Ask a question

Windows System Resources Monitoring Log Enablement Package (LEP) Library

    The Windows System Resource Log Enablement Package is a Windows Performance Monitor Template which contains Performance Counters. These counters provide basic threshold monitoring of OS metrics for processor, memory, and disk. All threshold data is sent to the Application Event Logs where the K1's Agent or Agentless component can manage performance data extraction. K1 then displays this data in a single page UI which tracks the overall health of the endpoints being monitored. The Threshold column below displays a Criteria Level of Critical, Warning, or Error. This column should have two values, a Default value and a Threshold value, for records without both, only a Default value of 10000 is set which needs to be reset to an appropriate Threshold value. For instructions related to LEP’s check out How to Edit Windows Monitoring Log Enablement Package(LEP), How to Import Windows Monitoring Log Enablement Package(LEP), and Troubleshooting Windows Monitoring Log Enablement Package(LEP). Detailed instructions on how to configure the K1 to monitor Application or Threshold Monitoring on devices can be found in the Dell KACE K1000 System Management Appliance 6.3 Administrator Guide.



Processor

Performance Counter
Description
Threshold Values
% Processor Time
% Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the percentage of time that the processor spends executing the idle thread and then subtracting that value from 100%. (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It should be noted that the accounting calculation of whether the processor is idle is performed at an internal sampling interval of the system clock (10ms). On todays fast processors, % Processor Time can therefore underestimate the processor utilization as the processor may be spending a lot of time servicing threads between the system clock sampling interval. Workload based timer applications are one example  of applications  which are more likely to be measured inaccurately as timers are signaled just after the sample is taken.

Default>80

Critical>80

Processor
Queue Length

Processor Queue Length is the number of threads in the processor queue.  Unlike the disk counters, this counter counters, this counter shows ready threads only, not threads that are running.  There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent of the workload.

Default>4

Warning>4

Context Switches/Sec
Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another.  Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service.  It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches.  There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

Default>5000

Critical>5000



Memory
Performance Counter
Description
Threshold Values
Available Mbytes
Available MBytes is the amount of physical memory, in Megabytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.

Default<100

Critical<100

Pages Input/Sec
Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of  Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.

Default>10

Critical>10

Page Writes/Sec
Page Writes/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code.  This counter shows write operations, without regard to the number of pages written in each operation.  This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
Default>10000
Page Reads/Sec
Page Reads/sec is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files. Compare the value of Memory\\Pages Reads/sec to the value of Memory\\Pages Input/sec to determine the average number of pages read during each operation.
Default>10000
Pages/Sec
Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays.  It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec.  It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
Default>1000

Critical>1000


Disk I/O

Download Windows System Resource Disk Log Enablement Package for Windows Server 2008 and higher.

Performance Counter
Description
Threshold Values
% Free Space
% Free Space is the percentage of total usable space on the selected logical disk drive that was free.

Default<15

Critical<15

%Idle Time
% Idle Time reports the percentage of time during the sample interval that the disk was idle.

Default<20

Critical<20

Avg. Disk Sec/Read
Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.

Default>25

Critical>25

Avg. Disk Sec/Write
Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.

Default>25

Critical>25

Avg. Disk Queue Length
Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.
Default>20
Cache Bytes
Cache Bytes is the sum of the Memory\\System Cache Resident Bytes, Memory\\System Driver Resident Bytes, Memory\\System Code Resident Bytes, and Memory\\Pool Paged Resident Bytes counters.  This counter displays the last observed value only; it is not an average.
Default>300

Critical>300


Be the first to comment

Internet Information Services Monitoring Log Enablement Package (LEP) Library

        The Internet Information Services Monitoring Log Enablement Package (LEP) is a Windows Performance Monitor Template which contains Performance Counters. These counters provide basic threshold monitoring of Internet Information Service Performance Objects like FTP Services, Web Services, and Internet Information Services Global. All threshold data are sent to the Application Event Logs where the K1's Agent or Agentless component can manage performance data extraction. K1 then displays this data in a single page UI which tracks the overall health of the endpoints being monitored. The Threshold column below displays a Criteria Level of Critical, Warning, or Error. This column should have two values, a Default value and a Threshold value, for records without both, only a Default value of 10000 is set which needs to be reset to an appropriate Threshold value. For instructions related to LEP's check out How to Edit Windows Monitoring Log Enablement Package (LEP)How to Import Windows Monitoring Log Enablement Package (LEP) and Troubleshooting Windows Monitoring Log Enablement Package (LEP). Detailed instructions on how to configure the K1 to monitor Application or Threshold Monitoring on devices can be found in the Dell KACE K1000 System Management Appliance 6.3 Administrator Guide. 



Throughput

Performance Counter
Description
Threshold Values
Files/Sec
The rate at which files are sent and received by the service.
Default>10000
Bytes Received/Sec
Bytes Received per sec is the rate at which data bytes are received by the service.
Default>10000
Bytes Sent/Sec
Bytes Sent per sec is the rate at which data bytes are being sent by the service.
Default>10000
Bytes Total/Sec
Bytes Total per sec is the sum of Bytes Sent per sec and Bytes Received per sec.  This is the total rate of bytes transferred by the service
Default>10000
Files Received/Sec
The rate files are received by the Web service.
Default>10000
Files Sent/Sec
The rate files are sent by the Web service.
Default>10000
Total Files Sent
Total Files Sent is the total number of files sent by the Web service (since service startup).
Default>10000
Total Files Received
Total Files Received is the total number of files received by the Web service (since service startup).
Default>10000
Total Files Transferred
Total Files Transferred is the sum of Files Sent and Files Received (since service startup).
Default>10000


Bandwidth Usage

Performance Counter
Description
Threshold Values
Current Blocked Async I/O Requests
Current requests temporarily blocked due to bandwidth throttling settings.
Default>10000
Measured Async I/O Bandwidth usage
Measured bandwidth of asynchronous I/O averaged over a minute.
Default>10000
Total Allowed Async I/O Requests
Total requests allowed by bandwidth throttling settings (since service startup).
Default>10000
Total Blocked Async I/O Requests
Total requests temporarily blocked due to bandwidth throttling settings (since service startup).
Default>10000
Total Rejected Async I/O Requests
Total requests rejected due to bandwidth throttling settings (since service startup).
Default>10000



Connections

Performance Counter
Description
Threshold Values
Connection Attempts/Sec
The rate that connections to the Web service are being attempted.

Default>20

Critical>20

Current Anonymous Users
Current Anonymous Users is the number of users who currently have an anonymous connection using the Web service.
Default>10000
Current Connections
Current Connections is the current number of connections established with the Web service.
Default>10000
Current File Cache Memory Usage
Current number of bytes used for file cache.
Default>10000
Maximum Connections
Maximum Connections is the maximum number of concurrent connections established with the Web service (since service startup).
Default>10000
Current Files Cached
Current number of files whose content is in the cache for WWW and FTP services.
Default>10000
 Current NonAnonymous Users
 Current NonAnonymous Users is the number of users who currently have a non-anonymous connection using the Web service.
Default>10000
Maximum Anonymous Users
Maximum Anonymous Users is the maximum number of users who established concurrent anonymous connections using the Web service (since service startup).
Default>10000
Maximum NonAnonymous Users
Maximum NonAnonymous Users is the maximum number of concurrent non-anonymous connections to the Web service (since service startup).
Default>10000
Total Anonymous Users
Total Anonymous Users is the total number of users who established an anonymous connection with the Web service (since service startup).
Default>10000
Total Connection Attempts
Total Connection Attempts is the number of connections that have been attempted using the Web service (since service startup).  This counter is for all instances listed.
Default>10000
Total Logon Attempts
Total Logon Attempts is the number of logons attempts to the Web Service (since service startup).
Default>10000
Total NonAnonymous Users
Total NonAnonymous Users is the total number of users who established a non-anonymous connection with the Web service (since service startup).
Default>10000


Requests

Performance Counter
Description
Threshold Values
Get Requests/Sec
The rate HTTP requests using the GET method are made.  Get requests are the most common HTTP request.
Default>10000
Head Requests/Sec
The rate HTTP requests using the HEAD method are made.  Head requests generally indicate a client is querying the state of a document they already have to see if it needs to be refreshed.
Default>10000
ISAPI Extension Requests/Sec
The rate that ISAPI Extension requests are received by the Web service.
Default>10000
Post Requests/Sec
The rate HTTP requests using the POST method are made.
Default>10000
Put Requests/Sec
The rate HTTP requests using the PUT method are made.
Default>10000
Request Bytes In Total
The total size, in bytes, of all requests.
Default>10000
Request Bytes Out Total
 The total size, in bytes, of responses sent to clients. This does not include standard HTTP response headers.
Default>10000
Requests Executing
The number of requests currently executing.
Default>10000
Requests Queued
 The number of requests waiting for service from the queue.
Default>10000
Requests Rejected
The total number of requests not executed because there were insufficient resources to process them.
Default>10000
Requests Succeeded
The number of requests that executed successfully.
Default>10000
Requests Timed Out
 The number of requests that timed out.
Default>10000
Requests Total
The total number of requests since the service was started.
Default>10000
Requests/Sec
The number of requests executed per second.
Default>10000


Errors

Performance Counter
Description
Threshold Values
Errors During Script Runtime
Number of requests failed due to runtime errors.
Default>10000
Errors From ASP Preprocessor
Number of requests failed due to preprocessor errors.
Default>10000
Errors From Script Compiler
Number of requests failed due to script compilation errors.
Default>10000
Errors/Sec
The number of errors per second.
Default>10000
Not Found Errors/Sec
The rate of errors due to requests that couldn't be satisfied by the server because the requested document could not be found.  These are generally reported as an HTTP 404 error code to the client.
Default>10000
Requests Not Authorized
Number of requests failed due to insufficient access rights.
Default>10000
Requests Not Found
The number of requests for files that were no found.
Default>10000
Requests Rejected
The total number of requests not executed because there were insufficient resources to process them.
Default>10000
Requests Timed Out
The number of requests that timed out.
Default>10000
Service Uptime
The length of time the Web Service has been running.
Default>1000000
Total Not Found Errors
Total Not Found Errors is the number of requests that couldn't be satisfied by the server because the requested document could not be found (since service startup).  These are generally reported as an HTTP 404 error code to the client.
Default>10000


ASP Sessions

Performance Counter
Description
Threshold Values
Session Duration
The number of milliseconds that the most recent session persisted.
Default>10000
Sessions Current
The current number of sessions being serviced.
Default>10000
Sessions Timed Out
The number of sessions timed out.
Default>10000
Sessions Total
The total number of sessions since the service was started.
Default>10000

Caching and Memory

Performance Counter
Description
Threshold Values
File Cache Flushes
File Cache Flushes since server startup.
Default>10000
URI Cache Flushes
URI Cache Flushes since server startup.
Default>10000
File Cache Misses
Total number of unsuccessful lookups in the file cache.
Default>10000
URI Cache Misses
Total number of unsuccessful lookups in the URI cache.
Default>10000
Maximum File Cache Memory Usage
Maximum number of bytes used for file cache.
Default>10000
Script Engines Cached
The number of script engines in cache.
Default>10000
Template Cache Hit Rate
Percent of requests found in template cache
Default>10000
Template Notifications
The number of templates invalidated in the cache due to change notification.
Default>10000
Templates Cached
The number of templates currently cached.
Default>10000


ASP Transactions

Performance Counter
Description
Threshold Values
Transactions Aborted
The number of transactions aborted.
Default>10000
Transactions Committed
The number of transactions committed.
Default>10000
Transactions Pending
Number of transactions in progress.
Default>10000
Transactions Total
The total number of transactions since the service was started.
Default>10000
Transactions/Sec
Transactions started per second.
Default>10000











Be the first to comment

How to Edit Windows Monitoring Log Enablement Package (LEP)

    A Monitoring Log Enablement Package is basically a Template file used to configure Windows Performance Monitor and contains Performance Counter, threshold values and other configuration settings. Windows Server 2003 uses a different Template file from that of Windows Server 2008 and Higher and the process to edit and import them are also different. Follow the detailed instructions below on how to edit Windows Server 2003 and Windows Server 2008 and Higher Log Enablement Package.


How to Edit Windows Server 2003 Monitoring Log Enablement Package


  1. Open Performance Monitor and expand the Performance Logs and Alerts section.
  2. Select Alerts and in the details pane right click the desired Log Enablement Package.
  3. If the Log Enablement Package is started select Stop.
sM2yBE.png


4.   Then right click the Log Enablement Package again and select Properties.

xe8rp2.png



5.   The General tab allows you to Add, Remove and configure counters.

EO468O.png



6.    Highlighting the counter displays the performance configuration. An alert can be set to trigger if the

counter value is over or under a set limit. This data can be obtained over a customizable interval in

seconds, minutes, hours, or days. You can change what user the Alerts Settings will Run As, just enter

 a user name and Set Password. Built-in groups have access to the following Performance Monitor features:

 

  • Members of the local Administrators group
  • All performance monitor features are available to this group.



  • Members of the Users group
  • Members of the Users group can change the Performance Monitor display properties while viewing historic data.
  • They can view log files in Performance Monitor.
  • They cannot create an Alert Setting as a member of this group.

 

  • Members of the Performance Monitor Users group
    • Can use all features available to the Users group
    • Can view real time logs in Performance Monitor and alter Performance Monitor display properties in real time.
    • Cannot create or modify Alert Settings.



  • Members of the Performance Log user group
    • Members of this group can use all the features that are available to the Performance Monitor Users group.
    • Members of this group can create and modify Data Collector Sets after the group is assigned the Log on as a batch user.





6.  Clicking the Remove button removes the selected counter and clicking the Add button displays the Add counters dialog.

SEA4K1.png

This dialog is used to select Performance counters based on Performance Objects.


Note. The list of Performance Objects depends on the system resources or applications installed on

the system for example if SQL Server is not installed there will be no SQL Server Performance Objects

and no SQL Server performance counters locally on the system. However counters can be obtained from

a remote computer by Selecting counters from computer and enter the computer name in the text box.

When done Close dialog. All selected counters will be listed under Counters. Click Ok to close the dialog.



7.   Right click the Log Enablement Package and select Start.

QAq6dC.png




How to Edit Windows Server 2008 and Higher Monitoring Log Enablement Package.

1.      Open Performance Monitor and expand Data Collector Set then expand User Defined.

2.      Select the Data Collector Set you would like to edit and if it is running click Stop.

qVkCyh.png



3.     Right click the DataCollector in the right pane and select properties.

BXRViG.png



4.      The DataCollector properties dialog box displays the Alert tab.

PR8zuL.png



The Alerts tab allows you to Add, Remove and configure counters.

Selecting the Performance counter allows you to configure its threshold and interval attributes.

 An alert can be configured to trigger if the counter value is over or under the limit set.

 This data can be collected over a customizable interval seconds, minutes, hours, or days. 

Click the Remove button to remove selected counter from the Performance counters list,

 and click the Add button to displays the Add counters dialog.

 

 

5.      The Add Counter dialog is used to select performance counters based on performance objects.

Performance counters are grouped based on a particular performance objects. For example all counters for Active Server Pages are grouped together.

Only applications installed locally will have performance objects and counters displayed from the local computer. 

Objects and counters from a remote system can be selected here by entering the computer name or Browsing to that computer.

RVy1mQ.png

Once the counters are selected they can be added by clicking the Add>> button and removed by clicking the Remove<< button.



6.     Click Ok once all counters have been added, they will be displayed in the performance counters list on the DataCollector Properties dialog.

KoX1re.png



7.    The Alert Action tab gives the option of sending alerts to the event log and starting a Data Collector Set once an alert is triggered.

nPUP01.png



8.    The Alerts Task allows you to run a task when the alert is triggered.

zxiLJ8.png

Click Ok to complete DataCollector Property changes. If you are satisfied with changes made to the Performance alerts you may start the Data Collector Set by right clicking the Data Collector Set and selecting Start.








Be the first to comment

How to Import Windows Monitoring Log Enablement Package (LEP)



    A Log Enablement Package is basically a Template file used to configure Windows Performance Monitor and contains Performance Counter, threshold values and other configuration settings. Windows Server 2003 uses different Template file from that of Windows Server 2008 and Higher and the process to edit and import them are different. Follow the detailed instructions below to import Windows Server 2003 and Windows Server 2008 and Higher Log Enablement Package.


How to Import Windows Server 2003 Monitoring Log Enablement Package (LEP)


1.    On a windows 2003 system, navigate to Start->Run then type perfmon and press Enter to start the Performance Monitor application.
2.    Expand the Performance Logs and Alerts section and right click on the Alerts label and select New Alerts Settings From…

X6bARc.png




3.    Find the location of the Probe Log Enablement Package (Performance monitor template file) and select it.

GHVA4h.png



4.    Confirm or change the Log Enablement Package name and click Ok. Its recommended to keep the name to help identify what is being monitored

G06zwz.png



5.    The Log Enablement Package property page is displayed. The General tab allows you to add and remove counters and set threshold values over a given interval. Select Ok to close this window.

iYdVxC.png



6.    Right click on Log Enablement Package name and select start. The Log Enablement Package icon will change color from red to green signifying it has started. The alert logs generated can be viewed in the event viewer.

EQtFGn.png



7.    Open the Event viewer and navigate to the Application logs. All performance monitor logs will have their source name identified by SysMonLog.

VY0TBF.png






How to Import Windows Server 2008 and Higher Monitoring Log Enablement Package


1.     Start Performance Monitor and expand the Data Collector Set folder.

BASdr5.png



2.    Right click the User Defined folder then point to New then select Data Collector Set.

W9gGpG.png



3.    Copy the name of the Log Enablement Package into the text field labeled Name.

cjrPxE.png



4.    Ensure the radio button Create From Template (Recommended) is selected then click Next.

5.    Browse to the location of the Log Enablement, select it then click Next.

c7d5f2.png



6.    Specify where you would like the data to be saved or leave the default location then click Next.

h8FM6b.png



7.    By default this Log Enablement Package runs using the System account permissions but to change simply enter a user.

QYthMf.png



8.    Select Save And Close then click Finish.

9.    Under User Defined highlight the Log Enablement Package you just imported then right click on the DataCollector 01 and

       select Properties.

vgd8Sq.png



10.    The Properties dialog is displays. Here you can edit the Log Enablement Package properties and Add or Remove Performance

          Objects and Counters. How to Edit Windows Server 2008 and Higher Monitoring Log Enablement Package. 

s9OwgY.png



11.    If you would like to begin monitoring instead right click the Log Enablement Package and select Start.

5wMyB9.png



12.    Once the Performance Counter Alerts trigger they can be viewed in the Event Viewer at the following location:

          Applications and Services Logs->Microsoft->Windows->Diagnosis-PLA->Operational.


Be the first to comment

How to Import Multiple Windows Monitoring Log Enablement Package (LEP) via GPO Deployment

    

    This process uses a PowerShell script to import and start the Performance Monitor Log Enablement Package

(Templates) via GPOs.  The script runs on Logon/Logoff or Startup/Shutdown via GPO deployment and is

intelligent enough to run on all servers or specific servers to which the GPO is applied. It contains a ServerList

file which is made up of two sections. The first section is called [All_Servers], which is a list of Log Enablement Package that

 will be imported on all servers. The second section is called [Specific _Servers] and it lists the Log Enablement Package to

 be applied to defined servers.  This script will work on all Windows machines running Windows 2008 and

 later.



1                     Download the following files: ImportLEP.PS1, ServerList.txt, and the Performance Monitor

 Log Enablement Package (LEP) you would like import.

2                     For the purpose of this doc the following Log Enablement Package(LEP) will be used:

 WSR_Processor_Alerts, WSR_Memory_Alerts, WSR_Disk_Alerts, AD_AddressBook_Alerts, and AD_AsychronousThreadQueue_Alerts.

3                     Add Log Enablement Package (LEP) that needs to be installed on all servers to the [All_Servers]

 section, and Log Enablement Package (LEP) for specific servers to the [Specific_Servers] section.

 

 

 

[All_Servers]

WSR_Processor_Alerts

WSR_Memory_Alerts

WSR_Disk_Alerts

 

 

[Specific_Servers]

Server1 = AD_AddressBook_Alerts;  AD_AsychronousThreadQueue_Alerts

Server2  = AD_AddressBook_Alerts;  AD_AsychronousThreadQueue_Alerts

Server3  = SQLServer_Workload_Alerts;  SQLServer_DataAccess_Alerts

 

 

 

 

Here is an example of the ServerList.txt file.  [All_Servers] is a list of just Log Enablement Package (LEP) while

 [Specific_Servers] is a list of servers and the Log Enablement Package (LEP). For the [Specific_Servers] list the

 servers are separated from the Log Enablement Package (LEP) by an equal sign (=) and the list of Log Enablement Package

 (Templates) are separated by a semicolon (;). The server name can either be the host name or IP Address.

 

 

4.    Copy the ImportLEP.PS1, ServerList.txt and all the Log Enablement Package (LEP) to a network path

        accessible by all servers.  

Okm8xj.png



5.    Now configure GPO to deploy and execute the script.

6.    Go to Run and type gpmc.msc.

7.    In the left panel click on the plus sign next to Group Policy Objects.

42O5RG.png



8.    Right click on Group Policy Objects and select New. The default Group Policy Object name is

       New Group Policy Object rename to whatever is most appropriate. Import Monitoring Log Enablement Package works for me.

   Irwvd2.png



9.    Link the location you would like the GPO to run against. In this example the KD.com domain

       is selected. Right click the domain branch and select Link an Existing GPO….

eMHl4T.png



10.    Then Select Import Monitoring Log Enablement Package from the Select GPO dialog.

k0612D.png



Us5BnF.png

The linked domain shows up in the Links window.



11    Right click on the newly created GPO Policy Object and select Edit.

KHWsqE.png



12.    In the left panel click on the plus sign (+) next to User Configuration, then the

         plus sign(+) next to Policies, and the plus sign(+) next to Windows Settings and highlight

         Scripts (Logon/Logoff). In the right panel right click on Logon or Logoff, which ever you

         prefer the script to run on, and select Properties.

sSWpJp.png



13.    In the scripts tab click the Add button. The Add a Script dialog is displayed.  Type

         powershell.exe below in the Script Name field and type the following string in the Script Parameters

         field.

         -noninteractive -executionpolicy bypass \\10.9.35.208\sysvol\KD.com\scripts\ImportLEP.PS1

          Update this Script Parameter field to reflect the location of the ImportLEP.PS1

pJD9Bl.png



14.    Click Ok on all Group Policy Open windows.

15.    To import the Log Enablement Package (LEP) on Startup or Shutdown open the Group Policy

         Management Editor. In the left panel click on the plus sign (+) next to Computer Configuration, then

         the plus sign(+) next to Policies, and the plus sign(+) next to Windows Settings and highlight Scripts

         (Startup/Shutdown). In the right panel right click on Startup or Shutdown, which ever you prefer the

         script to run on, and select Properties.

KOSLJ1.png



16.    Repeat step 12 to configure the Add a Script dialog then click Ok to close all Windows.

17.    Logon to a server listed in your Server List file and the Log Enablement Package (LEP) will be imported and started.

yRy0SL.png



18.    Once the Performance Alert thresholds are triggered they will be sent to the Event Viewer, were

          they will be collected and displayed by K1. Applications and Services Logs->Microsoft->Windows->Diagnosis-PLA->Operational.




Be the first to comment
Showing 1 - 5 of 22 results

Top Contributors

Talk About appdeploy-tools