NetIQ AppManager

Essentials

Lab Manual
 This page left blank intentionally. Do NOT Print.

ii NetIQ AppManager Essentials

NetIQ AppManager
Essentials

Lab Manual
© 2008 NetIQ Corporation, all rights reserved.

No part of this publication may be reproduced, distributed, transmitted, transcribed, stored in a retrieval system, translated into
any human or computer language, or disclosed to third parties without the express permission of NetIQ Corporation.
NETIQ APPMANAGER ESSENTIALS®: LAB MANUAL 7.01-7, OCTOBER 2008
NetIQ Corporation makes no representations or warranties with respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, NetIQ Corporation
reserves the right to revise this publication and to make changes to its contents at any time, without obligation to notify any
person or entity of such revisions or changes.
Further, NetIQ Corporation makes no representations or warranties with respect to any NetIQ Corporation product, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, NetIQ
Corporation reserves the right to make changes to any and all parts of NetIQ Corporation products at any time, without
obligation to notify any person or entity of such changes.
NetIQ Corporation; 1233 West Loop South, Suite 1800 | Houston, TX 77027

ii NetIQ AppManager Essentials

Contents
Contents

Instructor-Led Exercise 1
Tour of Installation 1

Optional Exercise 1
How to Manually Check-in Deployment Packages to the Web Depot 1

Instructor-Led Exercise 2
Remote Deployment of a Windows Agent 1

Instructor-Led Exercise 3
Log on to the Operator Console 1

Instructor-Led Exercise 4
Discovery 1

Lab 1
Resource Organization 1
Exercise 1: Create a Snapshot View 2
Exercise 2: Create a Dynamic View 2
Task 1: Create Dynamic View Rules 2
Exercise 3: Create a Server Group 5
Task 1: Create the Group 5
Task 2: Remove One Computer from Server Group 6

Lab 2
Jobs and Events 1
Exercise 1: Understand Event Options 1
Task 1: Test Event Conditions 1
Task 2: Test Event Collapsing 3
Task 3: Test State Change Events 4
Exercise 2: Navigate a Complex Console 6
Task 1: Explore Group By Options 6
Task 2: Explore View Options 6
Task 3: Sort by Column Header 6
Task 4: Filter the List Pane by Selected Objects 6
Task 5: Close Unused Views 7
Task 6: Test Split TreeView 7

Contents-iii
Instructor-Led Exercise 5
Chart Console 1

Lab 3
Common Knowledge Scripts 1
Exercise 1: Monitor Server Availability 1
Task 1: Deploy General_MachineDown 1
Task 2: Testing the Knowledge Script 2
Exercise 2: Monitoring the NT Event Logs 2
Task 1: Research the Known Event Occurrence 2
Task 2: Run General_EventLog 2
Exercise 3: Prepare for Scheduled Maintenance 3
Task 1: Prepare the Environment 3
Task 2: Run the Schedule Maintenance Knowledge Script 3
Task 3: Test the Knowledge Script 4

Lab 4
Actions 1
Exercise 1: Write to a TXT File 1
Exercise 2: Reboot a Server 3
Task 1: Configure the Registry to Allow Reboots 3
Task 2: Reboot AM7SQL1 Computer 5

Lab 5
Monitoring by Policy 1
Exercise 1: Create a Monitoring Policy 1
Task 1: Create a Knowledge Script Group 1
Task 2: Create a Monitoring Policy 2
Exercise 2: Modify a Monitoring Policy 3
Task 1: Change a Property Value of a KS in a Monitoring Policy 3
Task 2: Propagate Script Changes to a Monitoring Policy 4

Instructor-Led Exercise 6
Monitoring Cluster Servers 1

Lab 6
Response Time Monitoring 1
Exercise 1: Monitor Network Response Time 1
Task 1: Change the AppManager Service Accounts 1
Task 2: Monitor the Instructor’s Machine for Response Time 2
Exercise 2: Monitor Application Response Time 3
Task 1: Monitor SQL Server for Response Time 3
Task 2: Change the AppManager Service Accounts 4

Contents-iv NetIQ AppManager Essentials

Instructor-Led Exercise 7
Monitoring AppManager 1

Lab 7
Knowledge Script Implementation 1
Exercise 1: Real-World Scenario: Knowledge Scripts 1

Instructor-Led Exercise 8
Create Management Group with Server Group Member 1

Instructor-Led Exercise 9
Create Management Group with Rule-based Member 1

Lab 8
Security Manager 1
Exercise 1: Create an AppManager User Account 1
Task 1: Create a New Role 2
Task 2: Create a Windows Security Group 3
Task 3: Create an SQL Login for the Group 4
Task 4: Give the Group Permissions to the Cache Folder 5
Task 5: Create an AppManager Login 6
Task 6: Test the New User 7
Exercise 2: Synchronize the sa Password 8
Task 1: Run an SQL Knowledge Script 8
Task 2: Add the sa Password 8
Task 3: Change the sa login password 9
Task 4: Verify the Job is No Longer Functioning. 9
Task 5: Synchronize AppManager with the New Password 10
Task 6: Restart the SQL Knowledge Script 10
Exercise 3: Real-World Scenario: Security Manager 11

Instructor-Led Exercise 10
Gathering Data and Running Reports 1

Lab 9
Reporting 1
Exercise 1: Run and View Reports 1
Task 1: Watch List Report 1
Task 2: Performance Overview Report 3
Task 3: Average Value Report 4
Task 4: Data Summary Report 5
Task 5: System Uptime Pie Report 5
Exercise 2: Real-World Scenario: Reporting 6

Contents-v
Instructor-Led Exercise 11
Schedule an SQL Job to Clean the Database 1

Lab 10
UNIX Agent Installation (Optional) 1
Exercise 1: Install a UNIX Agent 1
Task 1: Ensure Connectivity with the AppManager Server 2
Task 2: Install the AppManager UNIX Agent 2
Task 3: Verify that the UNIX Agent is Running 4
Task 4: Add to the Operator Console and Discover the UNIX Agent 4

Appendix A
Answers to Scenario Exercises 1
Lab 7: Knowledge Script Implementation 1
Lab 8: Security Manager 2
Lab 9: Reporting 2

Contents-vi NetIQ AppManager Essentials

Instructor-Led Exercise 1
Tour of Installation

The instructor will guide you through the following exercise.

• Windows Explorer
− \Program Files\NetIQ\AppManager\
− \Program Files\NetIQ\AppManager\DB\Local-Repository.mdb
− \Program Files\NetIQ\AppManager\QDB\KP\
• MS SQL Enterprise Manager
− Databases\QDB
− Logins\netiq login
• Control Panel, Services
• Registry editor
− HKLM\Software\NetIQ\AppManager\4.0\
• Deployment Web Service and Web Depot in IIS
• Log on to the Operator Console
− Start > All Programs > NetIQ > AppManager > Operator Console
− Enter name of SQL Server that manages the repository
− Enter QDB for the repository name
• Console sections overview
• Dragging and dropping a Knowledge Script
− Stopping and starting job
− Modifying a job’s properties
• Viewing events
− Viewing parent and child events
− Acknowledging and closing events

Tour of Installation Instructor-Led Exercise 1-1

Instructor-Led Exercise 1-2 NetIQ AppManager Essentials
Optional Exercise 1
How to Manually Check-in Deployment
Packages to the Web Depot

If instructed, follow along with the instructor and perform the steps below.
1. In the Administration section, on the Packages list screen, right-click and select Check
in Packages.
2. Navigate to the Q:\AM_Updates\NetworkDevice_7.4.18 folder and select the file
AM70-NetworkDevice-7.4.18.0.xml
3. Click Open to check in the package and then OK in the confirmation dialog. You
should see a new Package in the list with a version of 7.4.18.0.
4. Right-click the old Package (version 7.0.43.0) and select Delete Package(s).
It is easy to make deployment mistakes by creating Rules using the old packages. It is a good idea
to delete them from the list (but save them as archives) after you have fully updated your
environment.
Over time, you will frequently check in new packages as NetIQ releases them to keep your
AppManager monitoring infrastructure up to date.

How to Manually Check-in Deployment Packages to the Web Depot Optional Exercise 1-1
Optional Exercise 1-2 NetIQ AppManager Essentials
Instructor-Led Exercise 2
Remote Deployment of a Windows
Agent

Follow along with the instructor and perform the steps below.

Exercise 1: Create Rules to deploy the NetIQ AppManager Windows Agent and the SQL
monitoring module to target virtual machine.
1. In AM7DC, start Control Center – Start > All Programs > NetIQ > AppManager >
AppManager Control Center.
2. Start AM7SQL1 where you will deploy the agent and logon. Use the information provided by the
instructor.
3. Return to Control Center in AM7DC. At the bottom of the Navigation Pane, click
Administration Tab.
4. Expand Deployment tree and click Rules.
5. In the Tasks pane on the right (Tasks tab), click Add Rule… to open Deployment Rule
Wizard.

6. Click Next.
7. Rule Name: Enter a name for your rule (Using an underscore _prefix will help bring your
custom rules to the top of the list). Click Next.

Remote Deployment of a Windows Agent Instructor-Led Exercise 2-1

 8. Packages: Scroll down and select NetIQ AppManager Windows Agent.

9. Below the list of packages see the message - Some Packages Must Still Be Configured.
Click NetIQ AppManager Windows Agent in the configuration window and use the
following settings:
− Accept Install default, click Next
− Accept default installation path, click Next
− Reporting Option and Service Account – leave blank, click Next
− Security level, accept Cleartext default, click Next
− Ports, accept defaults and click Next

− Optional configuration (notice the defaults and click Next)

ƒ Discover this agent automatically – Yes
ƒ Designate management servers – Do this now
ƒ Deployment Web Service – Yes
− Management Server Configuration
ƒ Primary management server – Enter AM7DC and click Next
− Deployment Web Service – Enter AM7DC and click Next
− Configuration Summary
ƒ Verify that your selections are correct
10. Click Finish and Next.
11. On the Credentials screen, default options must be configured.
Click Configure Options.
− User Name: Administrator
− Password: P@ssw0rd
− Domain: AMCLASSROOM
12. Click OK, and then click Next

Instructor-Led Exercise 2-2 NetIQ AppManager Essentials

13. On the Target Computers screen enter:
− Selection Method: Specific Computers
− Add Computer: Click Add. Type AM7SQL1 and press the Enter key.
− Click Next
14. Deployment Rule Inclusion and Exclusion Filters – Leave blank. Click Next on each screen.
15. Deployment Service – Accept default and click Next.
16. Deployment Schedule – Use the currently configured deployment schedule (Deploy upon
approval, Run once every 5 minutes) and click Next.
17. Notification – Leave blank. Click Next.
18. Review summary and click Finish closing the Wizard.
19. In Control Center Console on AM7DC, scroll down through Deployment Rules to display
your Rule. Your rule should be enabled. If it is not enabled, click on your rule and click
Enable Rule(s) in Task Pane.
20. You might want to check for a newly created Task at this point and approve it to speed up
the overall deployment process in class. (See the first few steps of the next exercise.)
21. Now create another Rule similar to the first one that deploys the AppManager for SQL
Server package.
22. To configure this package, accept the default Windows authentication.
23. Make sure the Rule is enabled when you finish creating it.

Remote Deployment of a Windows Agent Instructor-Led Exercise 2-3

 Exercise 2: Approve tasks and deploy the NetIQ AppManager Windows Agent to
AM7SQL1.
1. In the AM7DC Control Center Navigation pane, click Deployment Tasks. In the
Deployment tasks pane, you should see the AM7SQL1 machine name. (This may take a few
minutes to appear.)
2. Expand AM7SQL1 in the Deployment Tasks pane. You should see your Deployment Task
with a status of Waiting for approval.

3. Select your deployment task. In the Tasks pane on the right, click Approve Task(s). You
should see the status change to Active.
4. The task deploys according to the schedule. The default is immediately upon approval.
Check in a few minutes to see the status change to Completed. (This process can take a little
while to complete in the desktop VM environment.)
5. Switch to AM7SQL1. Open the Services control panel and look for the NetIQ services,
NetIQ AppManager Client Resource Manager (NetIQmc.exe) and NetIQ
AppManager Client Communication Manager (NetIQccm.exe.) You can also check
Task Manager, where you might see instances of the msiexec process, indicating the
installation is not 100% complete.
6. Switch back to the Control Center console and watch for another Deployment Task to
install the SQL managed object. Right-click and select Approve Task.
7. When that task has completed, close the Control Center console. File > Exit.
You will learn more about Control Center in a later module.

Instructor-Led Exercise 2-4 NetIQ AppManager Essentials

Instructor-Led Exercise 3
Log on to the Operator Console

Follow along with the instructor and perform the steps below.
1. If not already running, start the primary VM.
(Your instructor will provide specific instructions on how to do this.)
2. In primary VM, click Start > All Programs > NetIQ > AppManager > Operator
Console (Split Tree View)
3. In the AppManager Operator Console Logon dialog box, log into the repository you want to
use with Windows authentication.
After you are logged onto the AppManager repository, data is received dynamically. If you
cannot connect to the AppManager repository or want to use data cached locally from a previous
session, you can click Off Line. Working off-line displays the Operator Console, but, because
you are not connected to the repository, you are not able to manage systems dynamically or view
dynamic information.
Running separate instances of the Operator Console allows different users to access the same
repository from the same console computer. Once you have logged into the Operator Console,
you can switch to another repository. Your AppManager environment must have the same
version of the AppManager repository, management server, console, and Web management
server components. For example, you cannot log on to the repository with an earlier version of
the Operator Console or Web Console.

Log on to the Operator Console Instructor-Led Exercise 3-1

Instructor-Led Exercise 3-2 NetIQ AppManager Essentials
Instructor-Led Exercise 4
Discovery

Follow along with the instructor and perform the steps below.
Add Third Virtual Machine to the Master View

1. Start and log on to the third VM, AM7NT, in which an AppManager agent is already
installed.
2. In AM7DC, launch the Operator Console and click the Master tab to select the Master
view.
3. In the TreeView pane, select the top-level icon, in this case Master, to have the computer
added under the root of the hierarchy. Right-click and then select Add Computer.
4. In the Add Computer dialog box, click the small browse button on the right, then select
AMCLASSROOM from the menu.
5. Select \\AM7NT and then click OK.
6. Click checkbox “Discover Windows objects automatically”. (Selecting this option is the same
as running the Discovery_NT Knowledge Script on the computer.) Click OK.
7. When complete, check for the discovered NT resources in the Treeview. (The process may
take a couple minutes because the management server must first contact the machine and
establish communication with the agent before it can deploy the discovery script.)
8. Drag and drop Discovery_Networks-RT Knowledge Script and wait for job to stop. View
resources.

Discovery Instructor-Led Exercise 4-1

Instructor-Led Exercise 4-2 NetIQ AppManager Essentials
Lab 1
Resource Organization

This lab provides practice in organizing resources in the TreeView pane.

To perform this exercise, you should already have started and logged on to the training virtual
machines (VMs) in the AMClassroom domain. If your VMs are named different, your instructor
will provide the necessary instructions. Enter the VM hostnames below:
a.

Primary VM Second VM Third VM

AM7DC AM7SQL1 AM7NT

Before performing each lab, verify you have performed the prerequisites. If performance is not
an issue with your computer, you can leave all three VMs running.
b.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 The instructor-led exercises from module 2 and

previous sections in this lab manual.

AM7NT Recommended: Optional Exercise from previous

sections in this lab manual to check-in new
NetworkDevice package to the Web Depot (AM7DC)

Required: ILE Exercise 1 (from previous sections in

this lab manual) to Remote Deploy an AM Agent onto
AM7SQL1

Required: ILE Exercise 2 (from previous sections in

this lab manual) to Remote Deploy SQL Managed
Object onto AM7SQL1

Required: ILE beginning (from previous sections in

this lab manual) to discover AM Agent and Networks-
RT Managed Object on AM7NT

Resource Organization Lab 1-1

Exercise 1: Create a Snapshot View
1. Return to the AM7DC Operator Console. In the View menu select View Manager…
2. Click the Snapshot button under New.
3. For Snapshot view name type My_Network.
4. Click Filter.
5. In the Filter dialog, click Clear All, and then select Network and click OK.
6. Under Select the resource objects to display, select only AM7DC. Uncheck any other
resources listed there.
7. Click OK to create the [My_Network] snapshot view.
8. Click OK to close View Manager.
AppManager creates a new [My_Network] view tab, and displays the view in the TreeView
pane.

9. Expand the My_Network snapshot view of AM7DC Network objects.

Note
Snapshot views are static. If you discover a new server with network components, AppManager
will not automatically add the server to this view, nor will changes to already discovered
resources be updated.

Exercise 2: Create a Dynamic View

In this exercise you will create a dynamic view for SQL servers that have 256 MB or more
memory.

Task 1: Create Dynamic View Rules

1. In AM7DC Operator Console, select the Master View tab to return to the Master view in
the TreeView pane.
2. From the View menu, select View Manager.
3. Click the Dynamic button under New.
4. For Dynamic view name, type MySQLServers.
5. In Based on view dropdown, select SQL.
This ensures that your view will include only SQL Servers.
6. Click New View Rule.
7. Click Next and then click Add.

Lab 1-2 NetIQ AppManager Essentials

 8. In the Add Rule Condition dialog, select Object Detail Condition and click OK.
9. In the Rule Wizard dialog, click %NameSpecified%.
10. Use the information in the following table to create a rule that shows only servers with
256 MB or more of physical memory.

Field Value

Object type NT_PhysicalMemObj

Detail name Detail1[Size (KB)]

Operator greater than

Detail value 256000

11. Click OK.

12. Click Next twice. For Rule Name: type “MySQLServersRule”
13. Click Finish to create the Rule.

Resource Organization Lab 1-3

 Create Group Rule:

14. Click New Group Rule, click Next, then click Add.
15. Select Object Name Condition, and then click OK.

16. Click %Value Specified%, type AM7* in the Object Name field and then click OK.
17. Click Next twice.
18. For rule name, type AM7 Machines. For group name, type AM7_SQL.

Lab 1-4 NetIQ AppManager Essentials

 19. Click Finish, and then OK twice to close all dialogs.
AppManager creates a new {MySQLServers} view tab, and displays the view in the TreeView
pane. In less than a minute your servers appear in the view. They should be nested in your
custom, rule-based server group.
Note
Since this view is a dynamic SQL view, AppManager will automatically add any newly discovered
SQL servers to this view if they have 256 MB or more memory. They will also appear in the
appropriate dynamic server groups.

Exercise 3: Create a Server Group

In this exercise you will create a server group including three machines.

Task 1: Create the Group

1. In the Master view of the TreeView pane, select Master.
2. From the TreeView menu, select Create Server Group.
3. For New group name, type Windows.
4. Under Available servers/groups, select any machine and click Add>>. The selected
machine moves to the right-hand member list.
5. Click Add All>>. All machines (and any server groups, if they exist) are moved over.

6. Click OK to create the server group.

AppManager adds the group to the TreeView pane and shows the servers under the group.

Resource Organization Lab 1-5

Task 2: Remove One Computer from Server Group
1. In the TreeView pane, right-click Windows server group and select Properties.

2. On the Server tab, under Available servers/groups, ensure that Master is selected and
then select AM7NT in the right column. Click Remove.
AppManager removes the computer from the Members of this group list.

3. Click OK.
AM7NT now displays directly under Master (root level) again.

Lab 1-6 NetIQ AppManager Essentials

Lab 2
Jobs and Events

This lab demonstrates how to work with jobs and events in the List pane.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 None

AM7NT

Exercise 1: Understand Event Options

Task 1: Test Event Conditions
1. In the AM7DC Operator Console, select the Master view in the TreeView pane.
2. Select the NT tab in the Knowledge Script pane.
3. Drag and drop the NT_CpuLoaded Knowledge Script onto AM7DC, and configure the
following settings:
Note
If a Knowledge Script is missing, you need to check it in from c:\Program
Files\NetIQ\AppManager\qdb\kp.

Tab Setting Value

Schedule Regular intervals Every 10 seconds

Values Monitoring: Threshold – Total system CPU 0

Monitoring Threshold - Processor Queue Length 0

Actions Click New and select ... Action_NTEventLog

Advanced Collapse duplicate events into a single event No (clear the box)

Note
Action_NTEventLog writes an event log message to the Windows NT Event log when the
threshold is exceeded. The local machine log is written to by default.

Jobs and Events Lab 2-1

 What do you think will happen?
4. Click OK on the Properties dialog to start the job.
5. Click Events tab in the List pane.
6. Expand the parent event for the NT_CpuLoaded Knowledge Script that you just ran.
7. Note how many child events are below the parent event.
8. In the Operator Console, from the Extensions menu, select Event Viewer and view the
Application Log.
9. Note how many actions there are for the NT_CpuLoaded job.
You should see one new child event occur every 10 seconds in the Events tab and one
corresponding entry in the Event Viewer (Event Id 260 with source AppManager) every 10
seconds. In this scenario, there is a one-to-one relationship between child events and action jobs.
10. To prepare for the next test, do the following:
• On the Jobs tab, stop the NT_CPULoaded job by right-clicking the parent job and
selecting Stop Job.
• On the Events tab, close the parent event generated by the NT_CpuLoaded job by
clicking the checkbox to the left of the Status column and then clicking Yes.
Next test setting event conditions to 2.
11. On the Jobs tab, double-click the parent NT_CPULoaded job.
12. On the Advanced tab, for Raise event if event condition occurs, type 2.

Lab 2-2 NetIQ AppManager Essentials

 13. After within, type 2 for job iterations.
What do you think will happen?
14. Click OK on the Properties dialog.
15. On the Jobs tab, right-click the NT_CpuLoaded job and select Start. Click Yes after
reading warning screen if presented.
16. Switch between the Events tab and Event Viewer to compare the results. (You may need to
refresh the List pane by pressing F5.)
You should see one new child event occurring every 20 seconds in the Events tab and one
corresponding entry in the Event Viewer every 20 seconds. In other words, you should see one
new child event for every other iteration of the job.
17. To prepare for the next exercise, do the following:
• Stop the NT_CpuLoaded job.
• On the Events tab, close the parent event generated by the NT_CpuLoaded job.

Task 2: Test Event Collapsing

In this task you will set event occurrences to one and experiment with event collapsing.
1. On the Jobs tab of the List pane, double-click the stopped NT_CpuLoaded job.
2. On the Advanced tab, after Raise event if event condition occurs, type 1.
3. After within, type 1, for job iterations.
4. Select Collapse duplicate events into a single event.

Jobs and Events Lab 2-3

 What do you think will happen?
5. In the Properties dialog for Knowledge Script NT_CpuLoaded dialog box, click OK.
6. On the Jobs tab, right-click on the NT_CpuLoaded job and select Start Job.
7. Switch between the Events tab and the Event Viewer to compare the results.
This time you should see only one child event below the NT_CpuLoaded parent event, but you
should see the number of occurrences counting-up the number of times the event has happened.
Likewise, in the Event Viewer, you should see that only one new entry has been logged.
Remember, there is a one-to-one relationship between child events and action jobs.
8. When you are done viewing the job and events,
• Stop the NT_CpuLoaded job.
• On the Events tab, close the parent event generated by the NT_CpuLoaded job.
• Close the Event Viewer.

Task 3: Test State Change Events

In this task you will run a job to generate a state change event.
1. Drag and drop the NT_ServiceDown Knowledge Script onto AM7DC.
2. Use the following settings:

Tab Setting Value

Schedule Regular intervals Every 30 seconds

Values Monitoring: Services list (comma separated) *

Monitoring: Service start type filter Automatic
Start down services No

Actions Click New and select ... Action_NTEventLog

Advanced Generate a new event when original event Yes

condition no longer exists
Automatically close original event Yes

3. Click OK.
4. When the Job starts, open Services (Administrative Tools > Services).

Lab 2-4 NetIQ AppManager Essentials

5. Right-click the Computer Browser service and select Stop.
6. On the Event tab of the Operator Console, notice a new warning event. Right-click the child
event and select Detail Message.

The detail message should indicate that the browser service was stopped.
7. Close the Detail Message screen.
8. Switch to the Services window and start the computer browser service.
9. In the Operator Console, you should get a new warning event with a message of State
Change. The original event closes automatically.

10. In the Operator Console, from the Extensions menu, select Event Viewer.
11. In the Application log, find the event, from Source AppManager and double click on it.

12. Stop the NT_ServicesDown job. Close the warning event. Close the Event Viewer.

Jobs and Events Lab 2-5

Exercise 2: Navigate a Complex Console
The tasks in this exercise demonstrate some ways to modify how the Operator Console displays
information so that the console is easier to navigate.

Task 1: Explore Group By Options

1. Right-click anywhere on the Jobs tab in the List pane, select Group By, and try each of the
options.
2. Test each of the Group By options on the Events tab.
The options differ slightly on each tab.
3. Set the Group By options back to No Grouping.

Task 2: Explore View Options

1. Right-click anywhere on the Jobs tab in the List pane, select View, and try a few of the
options.
2. Test a few of the View options on the Events tab. If you deselect the Closed Events
option, your list will be less cluttered.
The options differ slightly on each List pane tab.

Task 3: Sort by Column Header

1. On the Jobs tab, click the Computer column header and notice the effect.
2. Click the header again to reverse the sort order.
Note
If any parent object is expanded, then only child items are sorted.

Task 4: Filter the List Pane by Selected Objects

1. In the TreeView, right-click a computer and select Filter List Pane by Selected Object.
Text in the List pane changes to blue font and the name of the focus machine shows in the
upper left corner of the List pane.
2. In the TreeView, select another computer and notice the items that display in the List pane.
3. In the TreeView, if you have a server group, select it and notice the items that display in the
List pane.
4. In the TreeView, right-click an object and turn off the filter.
Note
When you use this filter, each time you change focus (for instance, select a different object), the
console rescans the database. Therefore, console performance decreases as the number of
servers increases.

Lab 2-6 NetIQ AppManager Essentials

Task 5: Close Unused Views
1. Open View Manager.

2. Clear all views except the Master view, and then click OK.
The console displays only the Master view. This can dramatically improve Operator Console
performance, especially as the number of managed servers increases!

Task 6: Test Split TreeView

1. From the File menu, select Preferences.
2. On the Console tab, select Split TreeView into two panels, and then click OK. You will be
prompted that you must close and reopen the console for the preference to take effect. Click OK.
3. If you are not already viewing in Split Tree mode, close the console and reopen it.

4. Select a different managed computer in the TreeView and notice how the console displays
the objects.
Note
Split TreeView allows the console to open much faster because the details of each computer are
scanned only after you select the computer. NetIQ Corporation recommends that you use the
Split TreeView option for consoles with over 100 managed computers.

Jobs and Events Lab 2-7

Lab 2-8 NetIQ AppManager Essentials
Instructor-Led Exercise 5
Chart Console

The instructor will lead you through the following exercise:

• Create a chart
• Move the data streams
• Set streams transparent
• Change color schemes
• Rotate chart
• Add high thresholds
• Select data
• Fit data to window
• Aggregate data
• Export to HTML report
• Public views
• Set Chart Console Preferences

Note
Chart preferences cannot be set using the Web Console.

Points to Fetch
Configure this option to specify the maximum number of data points that are returned for
charts. The default is 2,000 data points. If you specify 0 all points are returned. The default
period that the repository keeps data for charts and graphs is 8 days. If a Knowledge Script is
configured to collect data and runs every 10 minutes, the data stream will contain 1152 data
points after 8 days. However if you are running the Knowledge Script every minute it will result
in more than 2000 points and at any given refresh the chart console will fetch only 2000 points.
Charts display the most recently collected data points. You can improve the overall performance
of the Chart Console by configuring this setting to show the optimal number of data points you
need.

Chart Console Instructor-Led Exercise 5-1

Instructor-Led Exercise 5-2 NetIQ AppManager Essentials
Lab 3
Common Knowledge Scripts

This lab demonstrates how to use a few of the most useful Knowledge Scripts –
General_MachineDown (server availability), General_EventLog (Windows event logs),
AMAdmin_SchedMaint (scheduled maintenance mode to suppress alerting).

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 None

AM7NT

Exercise 1: Monitor Server Availability

In this exercise you will use the General_MachineDown KS to monitor availability of AM7NT
and AM7SQL1.

Task 1: Deploy General_MachineDown

1. In AM7DC Operator Console, switch to the Master view.
2. In the Knowledge Script pane, click the General tab to view the knowledge scripts.
3. Drag and drop the MachineDown Knowledge Script onto AM7DC.
Use the following settings:
Schedule: Every 1 minute
Values:
• Under Monitoring section, for Select computers from the Repository, click Browse
button in the Value column.
• Select Master under View and Computer under Filter, and then click Next.
• Select AM7NT and AM7SQL1, and then click Finish.
4. Click OK to deploy the job.

Common Knowledge Scripts Lab 3-1

Task 2: Testing the Knowledge Script
1. Once the job is running, put the AM7SQL1 machine into ad hoc maintenance (right-click
the server in the TreeView and choose Maintenance Mode).
2. Select each of the two monitored servers and shut them down.
3. Switch back to the Operator Console on AM7DC and wait for any events.

Did you get an event for both of the monitored servers? (AM7SQL1 should NOT generate an
event while in maintenance mode with the current job settings.)
4. Restart both of the monitored VMs and switch back to the Operator Console.
5. Take AM7SQL1 out of maintenance mode (right-click on server again).
6. Acknowledge any events from this job.

Exercise 2: Monitoring the NT Event Logs

In this exercise, you will use General_EventLog Knowledge Script to monitor for specific NT
events on all classroom VMs to determine if a certain issue is common on multiple servers in the
environment.
Scenario: your application support team has reported an issue on one of the CRM servers and
needs to know if this is occurring on other servers. The error information is being sent by the
application to the NT Application Log.

Task 1: Research the Known Event Occurrence

First, you will look at the Application event log on AM7DC to see the details of the known
event occurrence. (this is only a demo event)
1. Open the Application log in Event Viewer on AM7DC.
2. Look for entries with a Source of AcmeCRM. There should be several events recorded
around mid-October 2008. The errors that matter to the application support team have
“ConversionFault” in the description.

Task 2: Run General_EventLog

1. Drag and drop General_EventLog onto Master in the TreeView (deploys to all servers).
2. Use the following settings:
Schedule: Run once
Values:
• Log files to filter: Application
• Events in past N hours: -1
• Event source filter: AcmeCRM
• Event ID filter: 269
• Event description filter: ConversionFault

Lab 3-2 NetIQ AppManager Essentials

 3. When the job completes, review the events.
• Did the job return any events where the detailed message contained Application events
not containing the keyword in the description?
• Which servers have experienced this same CRM issue?

Exercise 3: Prepare for Scheduled Maintenance

In this exercise you will configure the Managed Client to suspend jobs so that they do not
conflict with scheduled maintenance. You will deploy the AMAdmin_SchedMaint KS.

Task 1: Prepare the Environment

First, start a job to demonstrate how it is affected by the SchedMaint Knowledge Script.
1. Drag and drop NT_ServiceDown onto AM7DC.
2. Use the following settings:
Schedule: Regular Intervals, Every 20 Seconds
Values:
• Monitoring, Services list: Browser
• Monitoring, Service start type filter: Automatic
• Start Down Service?: Yes
3. Click OK.

Task 2: Run the Schedule Maintenance Knowledge Script

1. Drag and drop AMADMIN_SchedMaint onto AM7DC.
2. Use the following settings:
Schedule:
• Daily frequency, Every 5 Minutes (this setting is always ignored for this job)
• Start at 8:00 AM
• End at 6:00 PM
Values:
• Knowledge script category to block: *
3. Click OK.
4. Expand the NT_ServiceDown job to view the effects of putting the machine in
maintenance mode.
• The child job should have a Running (Inactive) status.
• The Server icon in the TreeView should also change, indicating that the server is in
maintenance mode.

Common Knowledge Scripts Lab 3-3

Task 3: Test the Knowledge Script
1. On AM7DC, open the Services dialog (Start > Administrative Tools > Services).

2. Stop the Computer Browser service.

The ServiceDown job will not restart the service because it is Running (Inactive).
3. In the Operator Console, stop the AMADMIN_SchedMaint job on AM7DC.
AppManager now restarts the Computer Browser service because the machine is no longer
in maintenance mode and the NT_ServiceDown enters a Running (Active) state.
4. Stop the NT_ ServiceDown job.

Lab 3-4 NetIQ AppManager Essentials

Lab 4
Actions

This lab demonstrates using Action Knowledge Scripts.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7NT None

AM7SQL1

Exercise 1: Write to a TXT File

In this exercise you will create a job to monitor folder size. When the folder size exceeds the
threshold, AppManager writes a message to a text file.
1. In the NT view, drag and drop NT_FolderSize onto AM7DC.
2. Modify the Event Notification values as follows:

Parameter Value

Create event if threshold exceeded? Yes

Create event if path does not exist? Yes

3. For Data Collection, set Collect folder count data to Yes.

4. Modify the Monitoring values as follows:

Parameter Value

Logical Drive letter to search C:

Root folder to begin the search Documents and Settings

Filenames *.*

Folder size threshold 1 megabytes

Actions Lab 4-1

 5. Under File Filters > File Size Filter, check Yes for Apply file size filter?, and then type 1
for the threshold file size.
6. On the Actions tab, click New and select Action_WriteMsgToFile.

7. Click Properties to configure the action.

a. Note that the path to the file is c:\temp\NetIQAct_Dump.txt.
b. Expand Standard Message Options and select all options.
c. Click OK.
8. Click OK to start the job.
9. Switch to the Jobs tab in List pane and observe NT_FolderSize running.
10. Switch to the Events tab and review and close the detailed message.

Lab 4-2 NetIQ AppManager Essentials

 11. On AM7DC, open C:\Temp\NetIQAct_Dump.txt to view data collected by the job
when the action was triggered.
12. Stop the NT_FolderSize job.

Exercise 2: Reboot a Server

This exercise shows how to use a Knowledge Script to configure AM7SQL1 to allow reboots.
Then you will use an Action Knowledge Script to reboot the AM7SQL1 virtual machine.

Task 1: Configure the Registry to Allow Reboots

1. In the Operator Console, drag and drop NTAdmin_RegistrySet onto AM7SQL1
computer.
2. Use the following settings:
Schedule tab:
• Run once
Values tab:
• Root Key: HKEY_LOCAL_MACHINE
• Path Name: Software\NetIQ\AppManager\4.0\NetIQmc\Security
• Key Name: AllowReboot
• Key Type: REG_SZ (case sensitive)
• Value of the key: *
Note
This reconfigures AppManager on AM7SQL1 computer so that it can be rebooted with the
Action_RebootSystem Knowledge Script sent by any management server (*). You could
enter a specific management server computer name rather than an asterisk. By default,
AppManager is configured to prohibit the computer from being rebooted by the agent.

Actions Lab 4-3

 3. Click OK.
4. On AM7SQL1, using Start > Administrator Tools > Services, stop and start the NetIQ
AppManager Client Resource Monitor Service (NetIQmc).
The registry setting does not go into effect until the service is restarted!

Lab 4-4 NetIQ AppManager Essentials

Task 2: Reboot AM7SQL1 Computer
1. In the Operator Console on AM7DC, drag and drop NT_LogicalDiskSpace on to
AM7SQL1.
2. On the Schedule tab, select Run Once.
(Resist the temptation to run this Knowledge Script every minute!)
3. On the Values tab, for Threshold, Used space %, enter 1
4. On the Action tab, add Action_RebootSystem and set the Location to managed client.
(If the location is not set to managed client, this action will fail.)
5. Click Properties to open the Action Properties dialog.
6. For shutdown message to be displayed, type:
All your base are belong to us!
7. Leave the default time for the shutdown message to be displayed (60) which is the minimum.
8. Click OK to close the Action Properties dialog.
9. Click OK to start the job.
The AM7SQL1 machine will display the custom shutdown message and then reboot 60 seconds
later.
Note
An action Knowledge Script can be initiated only from a monitoring Knowledge Script like
NT_LogicalDiskSpace. You cannot drag and drop an Action Knowledge Script onto a server.

Actions Lab 4-5

Lab 4-6 NetIQ AppManager Essentials
Lab 5
Monitoring by Policy

This lab demonstrates creating and editing monitoring policies.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7NT None

AM7SQL1

Exercise 1: Create a Monitoring Policy

In this exercise you will create a monitoring policy on the AM7DC and AM7SQL1 machines to
monitor and collect data for the following:
• CPU usage
• Logical disk space usage
• Physical memory, virtual memory, and paging files
• Traffic on network interface cards
• System up time

Task 1: Create a Knowledge Script Group

1. In Master View, from the Knowledge Script menu, select Create Knowledge Script
Group.
2. For Name type Class_CoreKS.
3. For Description type Core NT jobs for all Windows servers.
4. From the Regular KS list, expand NT and select the following Knowledge Scripts:
• NT_CpuLoaded
• NT_LogicalDiskSpace
• NT_MemUtil
• NT_NetworkBusy
• NT_SystemUpTime

Monitoring by Policy Lab 5-1

 5. Click Add.

6. Under Members of this Knowledge Script Group, double-click NT_CPULoaded to

open the Properties dialog.
7. On the Values tab, expand Data Collection and check yes for Collect total system
utilization data. Click OK.
8. Similarly, change the Collect Data value to y (or checked) for the other members of the
Knowledge Script Group.
9. Click OK to create the Knowledge Script Group.
This should create a new Knowledge Script tab named Class, in which the new KSG appears.

Task 2: Create a Monitoring Policy

Now that you have created a Knowledge Script Group, you are ready to deploy the monitoring
policy to your file servers.
1. Switch to the NT View. (If the view tab is not available, go to View > View Manager and
check the box to display NT view.)
2. Create a server group with the following parameters:
− Name: FileServers
− Computers: AM7DC and AM7SQL1
3. In the Treeview, right-click the FileServers group and select Monitoring Policy.
4. Select Class_CoreKS and click Add.
5. Click OK to create the monitoring policy.
6. Switch to the Jobs tab in the List pane.
In about a minute you should see several monitoring policy jobs in the NT view.

Lab 5-2 NetIQ AppManager Essentials

Exercise 2: Modify a Monitoring Policy
This exercise demonstrates how to change Knowledge Scripts in a monitoring policy. First you
will change the physical memory threshold of the MemUtil Knowledge Script in your monitoring
policy. Then you will edit MemUtil to return a more detailed event message and propagate the
edit to your monitoring policy.

Task 1: Change a Property Value of a KS in a Monitoring Policy

Perform the following procedure to change the physical memory threshold of the MemUtil
Knowledge Script in the new monitoring policy. For demonstration purposes, you will set the
maximum physical memory threshold in NT_MemUtil to 1%. This ensures that AppManager
generates events.
1. On the Class tab of the Knowledge Script pane, double-click CoreKS.
2. Double-click NT_MemUtil and modify the settings as follows:

Tab Setting Value

Schedule Regular intervals Every 1 minute

Values Maximum physical memory threshold 1

3. Click OK to accept the changes.

4. Click OK to close the Properties window for the Knowledge Script Group.
Since this Knowledge Script Group is used in a policy, the changes affect the policy jobs in less
than a minute.
5. Double-click the policy NT_MemUtil job and check the values and the schedule.
The changes you just made should show in the Properties dialog.
6. On the Events tab, double-click one of the child events generated by the NT_MemUtil
job.

7. View the information on the Message tab. The message should be similar to this.

Monitoring by Policy Lab 5-3

Task 2: Propagate Script Changes to a Monitoring Policy
Now edit the Knowledge Script to return a more descriptive event message when physical
memory exceeds the threshold. To do this, you will:
• Edit the MemUtil Knowledge Script to return an event message similar to the following:

• Propagate the new script code to the Knowledge Script Group associated with the
monitoring policy.
1. On the NT tab of the Knowledge Script pane, create a backup of the MemUtil Knowledge
Script
a. Right-click MemUtil and select Copy Knowledge Script.
b. Accept the default name and click OK.
2. Check out NT_MemUtil.
a. Right-click MemUtil and select Check Out Knowledge Script.
b. Save the Knowledge Script as NT_MemUtil.qml on AM7DC desktop.
The Knowledge Script opens in the AppManager Developer’s Console.
3. Find the following lines:
If DO_EVENT_Physical = "y" And PhysicalMemory > TH_Physical Then
longm = "Physical Memory Usage% is " & Format$(PhysicalMemory,
"0.00") & "%, which exceeds the threshold of " &
Cstr(TH_Physical) & "%"
MSActions Sev_Physical, "Physical Memory Usage exceeded
threshold", AKPID, "NT_PhysicalMemObj = " +
NT_PhysicalMemObj, longm

End If

4. Replace the string in quotes shown in bold font in the preceding step, “Physical Memory
Usage% is ” with the following string:

"The monitored memory utilization is a shocking "

5. Save and close the Knowledge Script.
6. In the Operator Console, from the KS menu, select Check in Knowledge Script.

Lab 5-4 NetIQ AppManager Essentials

 7. Select the modified KS stored on the desktop and click OK.
AppManager displays a message acknowledging that the Knowledge Script was successfully
checked in.
If instead you receive an error message, return to the Developer’s Console and verify that you
typed the edit correctly. Then try again to check in the Knowledge Script.
8. Click OK to continue.
The Knowledge Script is now modified to display a new detailed message for the event. Next
propagate the changes to the jobs being used in the policy without over-writing the parameters.
9. Right-click the newly checked in MemUtil Knowledge Script and select Properties
propagation > Knowledge Script Group Members.
The Properties propagation dialog box appears.
Note
If you had created MemUtil jobs by dragging and dropping the Knowledge Script on one or a
group of servers, you would select Propagate properties > Ad hoc jobs.

10. Clear Properties.

Since all the jobs in the policy may have different values for thresholds, etc, you want to
propagate only the script.

11. Click OK.

AppManager restarts the NT_MemUtil jobs based on the policy and displays a new event.

12. On the Event tab, view the information on the Message tab of the new event. The message
should be in your new, amusing format.
13. Edit the NT_MemUtil Knowledge Script in the Class_CoreKS Knowledge Script Group
to run every 5 minutes with a physical memory threshold of 90 (basically, reset the defaults).
This is a simple example of how you can use Properties Propagation to deploy Knowledge Script
code changes to different types of jobs running in a small or large AppManager environment.
Propagation of Knowledge Script values can be done similarly.

Monitoring by Policy Lab 5-5

Lab 5-6 NetIQ AppManager Essentials
Instructor-Led Exercise 6
Monitoring Cluster Servers

The instructor will lead you through the exercise below.

1. In AM7DC Operator Console, create a group in the Master view called Cluster and add
AM7DC and AM7SQL1 computers to this group.
2. Stop the messenger service on AM7DC.
3. Copy NT_CPULoaded to Cluster_CPULoaded.
4. Drop the AMAdmin_SetResDependency to the Cluster group with the following
parameters:
• Knowledge script category: Cluster
• Required active services: messenger
5. Drop Cluster_CPULoaded on the Cluster group.
Expand this job and notice that the job runs on AM7SQL1 machine in the active state, while
the job running on AM7DC is inactive.
6. Stop the messenger service on AM7SQL1 and start it on AM7DC.
Notice that the job switches to running active on AM7DC and inactive on AM7SQL1.

Monitoring Cluster Servers Instructor-Led Exercise 6-1

Instructor-Led Exercise 6-2 NetIQ AppManager Essentials
Lab 6
Response Time Monitoring

This lab demonstrates monitoring network and application response time. In both exercises, you
will initiate a response time monitoring job to view the response time from your third VM to
your primary VM.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 None

AM7NT

Exercise 1: Monitor Network Response Time

In this exercise you will test the “network” response time from one VM to another VM on your
host machine. This is only a simulation using the virtual machines on one desktop host, but it
gives you a working feel for how to setup and run Networks-RT jobs.

Task 1: Change the AppManager Service Accounts

1. In AM7DC, select Start > Administrative Tools > Services.

2. Stop both of the agent services, NetIQ AppManager Client Resource Monitor and
NetIQ AppManager Client Communication Manager.
3. Double-click the NetIQ AppManager Client Resource Monitor (NetIQmc) service to
open the Properties dialog.
4. On the Log On tab, select Local System account for the log on as, and then click OK.
5. Double click the NetIQ AppManager Client Communication Manager (NetIQccm)
service.
6. On the Log On tab, select Local System Account for the log on as, and then click OK.
7. Start both of the agent services.

Response Time Monitoring Lab 6-1

Task 2: Monitor AM7DC for Response Time
1. In the new Networks-RT view, drag and drop Networks-RT_[ResponseTime] to
AM7NT.
2. Schedule the job to run every 30 seconds.
3. On the Values tab, data is collected by default, so leave this enabled.
4. For Select endpoints to run the test to, click […].
5. In the Select a View dialog, select Networks-RT to view the servers in the Network-RT
view; then click Next.
6. In the Select Desired Computers page, select AM7DC and click Finish.
7. On the Values tab, for Response Time threshold, enter 0.1. Click OK.
8. Once the job starts running and has collected some data, create a chart (right-click) for the
data stream with legend Response Time (AM7NT to AM7DC).
You will notice that your network response time is extremely good with values probably
below 2 milliseconds (0.002 seconds).

9. Close the Chart Console and then stop the RT job.

Lab 6-2 NetIQ AppManager Essentials

Exercise 2: Monitor Application Response Time
In this exercise, you will monitor SQL Server on AM7DC for response time from AM7NT.
Then, when you are finished experimenting with response time monitoring, you will return the
NetIQ services to run as the windows service account.

Task 1: Monitor SQL Server for Response Time

1. In the Master view, drag and drop Discovery_SQL-RT on AM7NT, with the default
values. Wait for the job to stop and the new View tab to appear.
2. In the SQL-RT view, drag and drop the SQL-RT_ADOQuery on AM7NT, and use the
following settings:
Schedule: Every 30 Seconds
Values:
• Response Time > Threshold: 0.5
• Server and instance name: AM7DC
• Database name: QDB
• SQL Statement: Select * from KS
• Integrated Security: Yes
• Run As > Username: Administrator
• Run As > Password: P@ssw0rd
• Run As > Domain: AMClassroom
3. After the job starts running, create a chart showing the SQL response time data.

The response time should be good, with values below 0.75 seconds.
4. Close the Chart Console and then stop the SQL-RT job.

Response Time Monitoring Lab 6-3

Task 2: Change the AppManager Service Accounts
1. In AM7DC, select Start > Administrative Tools > Services.
2. Stop both agent services.
3. Double-click NetIQ AppManager Client Resource Monitor to open the properties
dialog.
4. On the Log On tab, type AMClassroom\administrator (confirm the account name with your
instructor) with a password of P@ssw0rd.
5. Repeat steps 2 and 3 for the NetIQ AppManager Client Communication Manager
service.
6. Start both services.

Lab 6-4 NetIQ AppManager Essentials

Instructor-Led Exercise 7
Monitoring AppManager

In this exercise, you will practice using NT_RemoteServiceDown to monitor AppManager

itself.
1. If necessary, change the agent service accounts to amclassroom\administrator in order to do
remote monitoring.
2. Drag and drop NT_RemoteServiceDown on AM7SQL1 to monitor NetIQms service.
3. Configure an action of Messenger with the computer to receive the message as AM7DC.
− Remember to do it as a managed client action.
4. Stop the NetIQ AppManager Management Service (NetIQms) service on AM7DC.
In this case the job running on the AM7SQL1 server detects that the management server service
(on AM7DC) is stopped, and sends a messenger message announcing that fact to the
AM7DC server.
5. The job will automatically restart the NetIQms service, so the event is delayed getting
written to the database. If you disable the auto-restart option, then you would not see the
event in any consoles until the service was restarted, allowing the agent to report the
information.

Monitoring AppManager Instructor-Led Exercise 7-1

Instructor-Led Exercise 7-2 NetIQ AppManager Essentials
Lab 7
Knowledge Script Implementation

Exercise 1: Real-World Scenario: Knowledge Scripts

Required VMs If Performance Prerequisites
Allows
(preferred)

AM7DC AM7SQL1 None

AM7NT

Work in pairs or small groups to discuss how to implement the following scenario requirements.
Be prepared to show the rest of the class how to implement your plan.
When implementing your plans, put all Knowledge scripts for California Traders on the
CATraders tab, with the exception of action Knowledge Scripts, which should remain on the
Action tab.
Note
Some of the requirements in this lab require an Exchange server. Therefore, if your lab
environment does not include an Exchange server, the SMTP mail action scripts will fail.
However, configure them anyway so that you become familiar with using those Knowledge
Scripts.

Knowledge Script Implementation Lab 7-1

 Requirement 1
California Traders management has requested the following:
• Monitor the following components on all servers every 15 minutes, and collect data every 30
minutes for reporting purposes:

CPU Alert only if over 90% 3 times in a row

Memory Alert only if over 90% 2 times in a row

Logical disk space Alert immediately

• All services set to “automatic” startup should be in running state to start up automatically
except the SQL services. (Alert immediately.)
• If any of the above is over the threshold, email the following groups via SMTP Mail:
− Level1Support for new events, all hours
− Level2Support when event occurs 2 times, 7 AM to 7 PM
− Level3Support when event occurs 4 times, all hours
Hint
Copy and customize the Action Knowledge Script, Action Schedule.

• If the NT_CPULoaded or NT_MemUtil script goes over the threshold, it should initiate the
TopCPUProc Knowledge Script and TopMemoryProcs Knowledge Scripts. These
Knowledge Scripts should have actions associated with them to email Level1Support for
new events at all hours of the day.
Hint
Copy and customize Action_RunKS for each of the above.

Lab 7-2 NetIQ AppManager Essentials

Requirement 2
All SQL Server must be monitored for the following:
• Accessibility
• DBSpace 80%
• Monitor SQL Server and agent services

Requirement 3
Management expressed a need for several SQL Servers to have their SQL agent jobs monitored
to see if the job started successfully. If an SQL Server agent does not complete a certain job,
management would like the following groups to be notified via SMTP pager:
• SQL DBA Group for new events, all work hours
• Help Desk Group, for new events, non-work hours

Requirement 4
Management wants you to monitor remotely the three NetIQ services on the Management
Server so that the AMAdmins group will be notified of failure at all hours via SMTP Mail.

Requirement 5
Management wants to ensure that the following routers are being monitored for availability:
• 10.21.10.1
• 10.21.10.100

Knowledge Script Implementation Lab 7-3

Lab 7-4 NetIQ AppManager Essentials
Instructor-Led Exercise 8
Create Management Group with Server
Group Member

Note
Lab 5 is a prerequisite for this instructor-led exercise.

Create a management group

1. In the Control Center Console, right-click the top-most AppManager icon in the Enterprise
Layout pane.
2. Select New > Management Group.

3. In the New Management Group Properties dialog box, enter FileServers as the
Management Group Name.
4. Click the Members tab and then click Add.
5. In the Management Group Members dialog box, under Type, click Server Group.
6. Under Server Groups, click NT\FileServers.
7. Click OK to add the member.
8. Click OK to close the dialog box and create the Management Group.
It may take a few minutes before the two servers appear in the Servers view. The default
behavior when creating new Management Groups is to automatically generate four standard
views – Jobs, Events, Servers, Knowledge Scripts.

Create Management Group with Server Group Member Instructor-Led Exercise 8-1
Instructor-Led Exercise 8-2 NetIQ AppManager Essentials
Instructor-Led Exercise 9
Create Management Group with Rule-
based Member

Follow along with the instructor to perform this exercise.

Creating Rule-based Management Group using a Custom Property

Task 1: Create Custom Property

In order to configure a rule-based management group to select computers based on custom
property information, you must first define the custom properties you want on each
managed client computer.
1. In the Master Management Group, select the Servers view.
2. Select the AM7DC computer in the list of computers.
3. Select the Custom Properties tab in the lower half of the grid pane, and then click New.

4. Create the Custom Property with these entries:

• Name: AppVersion
• Format: String
• Value: AM7

5. Click OK to create the Custom Property for AM7DC.

Create Management Group with Rule-based Member Instructor-Led Exercise 9-1

 Task 2: Create the Rule

Using the Rule Wizard, you can easily configure expressions to select the computers you want.
1. Right-click the FileServers Management Group and select Properties.
2. Click the Members tab, then select the Server Group entry and click Remove.
3. Click Yes to confirm the removal. You will now use a Rule to set the membership.
4. Click Add.
5. Click Rule in the list of Member types, and then click Create.
6. In the Name field, enter AM7Servers.
7. In Expression Templates, expand Custom Properties.
8. Select Compare String.
9. Click Add to Rule (you may have to click a second time).
10. Click the first [String] and select AppVersion from list.
11. Click the second [String] and enter AM7.

Instructor-Led Exercise 9-2 NetIQ AppManager Essentials

12. Click OK three times to close all dialogs.
You should see that the AM7SQL1 machine is removed from the Servers view. Due to VM
performance latency, it may take a few minutes for the console to update. You may also see both
machines temporarily disappear from the list as membership changes are processed.

Create Management Group with Rule-based Member Instructor-Led Exercise 9-3

Instructor-Led Exercise 9-4 NetIQ AppManager Essentials
Lab 8
Security Manager

This lab demonstrates how to use Security Manager to control user access to AppManager and
update AppManager with new passwords needed to run Knowledge Scripts.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 None

AM7NT

Exercise 1: Create an AppManager User Account

A fellow NT administrator named Frodo would like to start using AppManager. To help him,
you will create an AppManager user account for him. You will configure AppManager to make
sure Frodo’s account meets the requirements listed below:
• Frodo will log into AppManager using his Windows account.
• Frodo is allowed to monitor a computer with the following restrictions:
− Frodo cannot drop jobs on your machine.
− Frodo cannot modify or delete existing jobs on your machine.
− Frodo cannot place your machine into maintenance mode.
− Frodo is allowed to view the NT and IIS objects on your machine
− Frodo is not allowed to wear the ring
− In the NT and IIS views, you would like Frodo to view only the NT and IIS Knowledge
Script categories. He is not allowed to view any other categories (such as General,
NTAdmin, etc.)

Security Manager Lab 8-1

Task 1: Create a New Role
To complete the requirements, first create a new role named “AMApprentices,” and configure
the security profile.
1. In the AM7DC Operator Console, from the Extensions menu, select Security Manager.
The Security Manager console opens.
2. Right click AppManager Roles and select Add Role.
The Add Role dialog box appears.

3. For Role name, type AMApprentices, and then click OK.

4. In the left pane of Security Manager, expand AppManager Roles and select
AMApprentices.
5. On the Views tab, select Role has access to only selected views.
6. Clear all views except NT and IIS.
7. On the Exceptions tab, click Select Computers.
The Select Computers dialog box appears.
8. Click AM7DC, and then click OK.
9. Check the box next to AMApprentices – Exceptions.

Lab 8-2 NetIQ AppManager Essentials

 10. On the Knowledge Scripts tab, select Role has access only to selected Knowledge
Scripts and then check only IIS and NT.

11. Click Apply to create the role.

12. Close Security Manager

Task 2: Create a Windows Security Group

Since Frodo will be using his Windows account to log onto AppManager, you will create a
special Windows security group for AM users and include Frodo as a member.
1. In AM7DC virtual machine and from the Start menu, select All Programs >
Administrative Tools > Active Directory Users and Computers.
2. In the left pane, right-click the Training OU and go to New > Group.
3. For Group name, type AMUsers, and then click OK.
4. In the Training OU, right-click the new group, AMUsers, and select Properties.
5. Click Members tab, then click Add.
The Select Users, Contacts, or Computers dialog appears.
6. Type frodo in the object names window and click Check Names.
7. If the name is confirmed, click OK twice to close the dialogs, and then close AD Users and
Computers.

Security Manager Lab 8-3

Task 3: Create an SQL Login for the Group
Next, use SQL Server Management Studio to create an SQL login that maps to the group and
grant the login database access to the QDB.
1. From the AM7DC Start menu, select All Programs > Microsoft SQL Server 2005 > SQL
Server Management Studio.
2. Expand > Security > Logins.
3. Right-click Logins, and select New Login.
The New Login dialog appears.
4. For Login name, type amclassroom\AMUsers and confirm that Windows authentication
is selected.

5. Click on User Mapping under Select a page on the left. Check the box in the Map
column next to QDB on the right.
6. Click OK and then close SQL Server Management Studio.
7. Close Enterprise Manager.

Lab 8-4 NetIQ AppManager Essentials

Task 4: Give the Group Permissions to the Cache Folder
Now grant the new group write permission to the Cache folder so that members can create and
delete the cache files required to log onto the Operator Console.
Note
In a production environment, perform this task only on the machine where the operator console
is installed. However, this is not necessary for Web Console users.

1. In Windows Explorer, navigate to C:\Program Files\NetIQ\AppManager\bin\Cache.

2. Right-click the Cache folder and select Sharing and Security.
The Cache Properties dialog box appears.
3. On the Security tab, click Add.

4. Type AMUsers and click Check Names to confirm. If okay, click OK.

5. On the Security tab, select AMUsers, and then under Permissions, for Write check
Allow.
6. Click OK.

Security Manager Lab 8-5

Task 5: Create an AppManager Login
Now add the new user to AppManager and assign the AMApprentices role.
1. Open Security Manager from the AM7DC Operator Console.
2. Right-click the AMApprentices role, and select User Setup.
In the User Setup dialog, the AMUsers SQL login appears under SQL users.
3. Select AMUsers and click Add to move it to the AppManager users list.

4. To assign a role, click in the Security Role column, and then select AMApprentices.
5. Click OK.
6. Close Security Manager.

Lab 8-6 NetIQ AppManager Essentials

Task 6: Test the New User
Use the Run As feature to log onto the Operator Console as Scott. Ensure that Frodo can log on
using Windows authentication and that his user account has the correct security profile in place.
1. Close the Operator Console if it is open.
2. From the AM7DC Start menu, select All Programs > NetIQ > AppManager. Hold the
Shift key down, right-click Operator Console, and select Run as.

3. Click the radio button The following user, enter credentials for Frodo and click OK.

4. In the login screen, type AM7DC for the database server and then wait for the screen to
update (repository name is populated automatically.) Select Use Windows authentication
and click Logon.

In the Operator Console, only the NT view and IIS views should be present.
5. Try to send a job to AM7DC. You should not be able to do so.
6. Try to send a job to another computer. You should be able to do so.
7. When you are finished testing, close the Operator Console.

Security Manager Lab 8-7

Exercise 2: Synchronize the sa Password
In this exercise you will change the sa account password on AM7DC, verify that the SQL KSs
that are using the sa account no longer work, and then synchronize the sa password in Security
Manager.

Task 1: Run an SQL Knowledge Script

1. On AM7DC, log in to the Operator Console using Windows authentication.
2. In the Knowledge Script pane, go to the SQL tab and drag and drop TopCPUUsers onto
AM7DC.
3. Use the following settings:
• Schedule: Every 10 seconds
• Values:
− Collect data?: y
− SQL Server login: sa
Note
No field is available to enter the password for the sa login because the password is stored in the
AppManager repository using Security Manager.

4. Click OK.
5. On the Events tab of the List pane, view the message indicating that there was an error
getting Top CPU Users information since the login failed for User sa.
Note
During Installation you did not enter the password for the sa login. Therefore, it is not available
yet in the KPW table.

Task 2: Add the sa Password

1. Open Security Manager from the Operator Console.
2. Expand Computers and select AM7DC.
3. In the right pane on the SQL tab, click Logon.
This authenticates the current logged on Windows user account to the SQL server.
4. Right-click sa and select Password.

Lab 8-8 NetIQ AppManager Essentials

 5. For SQL password, type P@ssw0rd and click OK.

6. Click OK.
7. Close Security Manager.
8. In the Operator Console, stop and start the SQL_TopCPUUsers job.
9. On the Graph Data tab, right-click the SQL_TopCPUUsers data stream and select Create
Chart.
10. Accept the default title and color scheme and click Finish.
The Chart Console opens.
11. Select the TopCPUUsers chart.
You should now have data in the graph indicating the AppManager can connect to the SQL
server to retrieve the necessary information.

12. Minimize the Chart Console.

Task 3: Change the sa login password

1. Launch SQL Server Management Studio.
2. Expand Security and select Logins.
3. Right click the sa login, and select Properties.
4. In Login properties – sa dialog, enter password2 into both password fields. Deselect the
option Enforce password policy and then click OK.
5. Close SQL Server Management Studio.

Task 4: Verify the Job is No Longer Functioning.

1. Switch to the Chart Console.
Notice that the graph is no longer showing data for TOP CPU users because the Knowledge
Script no longer has the rights to access the SQL Server for this information.

Security Manager Lab 8-9

 2. Minimize the Chart Console.

Task 5: Synchronize AppManager with the New Password

1. Open Security Manager.
2. Expand Computers, and select AM7DC.
3. On the right side of the dialog, select the SQL tab.
4. Click Logon.
5. Right-click sa, and select Password.
6. For SQL password, type password2, and then click OK.
7. Click OK in the confirmation dialog, and then close Security Manager.

Task 6: Restart the SQL Knowledge Script

1. In the Operator Console, stop and start the SQL_TOPCPUUsers job.
2. Switch to the Chart Console and view the chart again.
The graph should now show the data for CPU users again.

3. Close the Chart Console and stop the SQL job.

Lab 8-10 NetIQ AppManager Essentials

Exercise 3:
Real-World Scenario: Security Manager
Work in pairs or small groups to discuss how to implement the following scenario. Then
implement your plan on at least one of your machines.

Scenario
Management would like to be able to log in to the Web Console reports section without having to
type in a username and password.
They also want permissions to log in to the Operator Console with read-only rights and rights to
only the NT, SQL, and IIS views.
Hint
Create a management read-only account, and then modify autologinreports.asp.

Security Manager Lab 8-11

Lab 8-12 NetIQ AppManager Essentials
Instructor-Led Exercise 10
Gathering Data and Running Reports

Follow along with your instructor to perform this exercise.

To become familiar with reporting, start with a basic AppManager Environment report,
Inventory. (Make sure to run the demo data script “AM7Ess_Reporting.bat” in Q:\LabFiles prior to
beginning Lab 9 on Reporting.)
1. In the Operator Console Discovery Knowledge Script tab, drag and drop ReportAgent to
AM7DC.

2. After discovering the reporting agent on your machine, drag and drop Inventory on your
AppManager repository on the report agent.
3. Choose the desired servers and accept all default properties.
This creates a Windows NT/2000/XP/2003 inventory report.

4. Choose Extensions > Report Viewer and view the report.

Now that you know the basics of reporting, create a report involving data collected by a
monitoring job. Create this report based on the data collected in previous exercises.
5. In the Report View, drag and drop AvgMaxMinValue on your repository.

Gathering Data and Running Reports Instructor-Led Exercise 10-1

 6. Change the following values. Your instructor will explain each value that you change.
− Select data wizard > MasterView, Computer > your machine > By Data Stream >
Check NT_CpuLoaded Processor Utilization > Finish
− Select time range > Sliding 3 days end now > Daily peak time 8:00 AM to 5:00 PM
− Select peak weekdays > default
− Aggregation > Default
− Chart style > Area with a Threshold
− Series style(Average) > Line
− Select output folder > Specific name of folder > AvgMaxMin
− Properties > Author <yourname> > Company NetIQ > Custom1 <location of your
server > Add time Stamp > y
7. Run the report and view it in the Report Viewer.

Instructor-Led Exercise 10-2 NetIQ AppManager Essentials

Lab 9
Reporting

This lab provides practice in running, viewing, and customizing reports.

Note
Before you can complete the exercises in this lab, you must complete the instructor-led exercise
to discover the reporting agent on AM7DC and run the demo data script.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 No additional ILE required.

AM7NT 1) Discover the Reporting Agent on AM7DC (make

sure there is one!)
2) Shut down AppManager Operator Console.
3) Run the "AM7ESS_Reporting.bat" batch job on
AM7DC in the "Q:\LabFiles\AM7Ess - DemoData"
folder.
4) Restart the Operator Console.

Exercise 1: Run and View Reports

This exercise guides you through creating several service level and capacity planning reports.
Complete as many of the tasks as you can in the time allotted by your instructor.

Task 1: Watch List Report

For this task, you will create a Watch List report to help evaluate computers in regard to
upgrades and load balancing performance.
1. In the Report view, drag and drop ReportAM_WatchList onto your reporting agent.
2. On the Values tab of the properties dialog, accept the default settings for:
• Top or bottom
• Number N
• Number or percent
• Top or bottom by

Reporting Lab 9-1

 3. For Select data wizard, click […], and then use the information in the following table to
complete the wizard.

Wizard page Notes

Add Data For Views, select Master

For Filter, select Computer

Select Computer(s) Select all your computers

Select Data Select By Data Stream

Select Data Streams(s) Select Demo_NT_CPULoaded and

Demo_NT_MemUtil for MemPhysUsage

4. On the Values tab, for Select the style, select By Knowledge Script.
5. For Select time range, click […], and specify the date and time range:
• For Select Date/Time range options, select Specific date/time range and accept
defaults.
• For Daily Time Range, select Select daily peak time range, and then accept the
default range of 8:00 AM to 5:00 PM.
6. On the Values tab, under Report settings, for Include table/chart/both, select Both.
7. On the Values tab, under Report settings, for Select properties, click […], and then for
Title, type Top CPU and Memory Users.
8. Click OK to run the report job.
9. When the job stops, from the Extensions menu, select Report Viewer and review the
report you just created.

Lab 9-2 NetIQ AppManager Essentials

Task 2: Performance Overview Report
For this task, you will create a Performance Overview report to review the average CPU and
physical memory usage of several demo machines. You will create the chart to show one data
point for every 15 minutes of data.
1. In the Report view, drag and drop ReportAM_PerfOverview on your reporting agent.
2. Use the information in the following table to complete the select data wizard:

Wizard page Notes

Add Data For Views, select Master

For Filter, select Computer

Select Computer(s) Select DC02, EXCH01, FILE01

Select Data Select By Data Stream

Select Data Streams(s) Select Demo_NT_CPULoaded and

Demo_NT_MemUtil for MemPhysUsage %

3. For Select time range, select a sliding time range of 1 Day, don’t select end now.
4. For Aggregation by, select Minute.
5. For Aggregation interval, select 15.
6. On the Values tab, under Report settings, for Include table/chart/both, select Both.
7. Under Report settings, for Chart style, click […], and then specify the chart settings as
follows:
• For Style, select Line.
• On the Threshold tab, for Value, enter 75, and select Enable Threshold.
8. Under Report settings, for Select properties, name the report Overview of Mem and
CPU. Click OK and run the report.

9. When the job stops, go to Extensions > Report Viewer and review your report.

Reporting Lab 9-3

Task 3: Average Value Report
In this task, you will create an Average Value report to see the average hourly physical, virtual,
and page file memory usage of several machines.
1. Drop ReportAM_AvgValueByHr on your reporting agent.
2. Complete the select data wizard using the following information:

Wizard page Notes

Add Data For Views, select Master

For Filter, select Computer

Select Computer(s) Select 3 or 4 demo computers

Select Data Select By Knowledge Script

Select Data Streams(s) Select Demo_NT_MemUtil (This KS includes three

data streams: physical, virtual, and page file
memory)

3. Configure a sliding time range of 7 Days, ending now. Set the daily peak time range from
8:00 AM to 5:00 PM.
4. On the Values tab, under Report settings, for Include table/chart/both, select Both.
5. Create a line chart.
6. Name the report Memory Usage Summary. Run the report.
7. When the job stops, view the report.

8. Open the job properties, change the time setting to focus on 7:00 AM to 7:00 PM, and then
run the report job again.

9. View the report to see the differences.

Lab 9-4 NetIQ AppManager Essentials
Task 4: Data Summary Report
In this task, you will create a Data Summary report to view a summary of the changes in disk
space on demo machines. Then you will modify the report to see the average usage of either
CPU or physical memory.
1. Drop ReportAM_DataSummary on your reporting agent.
2. Complete the Data source select data wizard using the following information:

Wizard page Notes

Add Data For Views, select Master

For Filter, select View

Select Data Select Data Stream

Select Data Streams(s) Select Demo_NT_LogicalDiskSpace for % used

3. For Select the style, select By computer and legend.

4. Under Data settings, for Statistics to show, select Change.
5. For Select sorting/display option, select Sort.
6. Name the report Disk Usage Summary and then run the report.
7. View the report.
8. Modify the report settings in the job as follows:
• Using the data wizard, focus on Demo_NT_CpuLoaded or Demo_NT_MemUtil for
physical memory.
• Change Statistics to show to Average.
• Rename the report depending on which data stream you choose.
9. Run the report job again.
10. View the report to see the differences.

Task 5: System Uptime Pie Report

In this task, you will create a pie chart that shows the up and down time of the demo machines.
1. Drop ReportAM_SystemUptimePie on your reporting agent.
2. Use the Data source data wizard to set the view to Master and filter by View.
3. Select time range, select a sliding date range of 3 Days, ending now.
4. Select computer(s), check off two or three.
5. Set the uptime threshold to 99.9.
6. Make sure to configure report settings to include both table and chart.
6. Review the report.

Reporting Lab 9-5

Exercise 2: Real-World Scenario: Reporting
Work in pairs or small groups to discuss how to implement the following scenario. Then
implement it on at least one of your computers.

Scenario:
Your manager would like the following reports:
• Performance report by computer
− CPU
− Memory
− Logical Disk Space
− System Up Time
These reports should be created with the following specifications:
• For all the servers you manage.
• Every week.
• She would like to see the reports on Monday morning for the last week.
• She would like to receive an email indicating that the reports have been generated with a
URL link to the reports.
• Your manager would like the report formatted in the following way:
− With your company logo.
− With a message stating This Report is generated by the <Your Company>’s IT
services Team using NETIQ AppManager.

− With a link to your company’s Web site.

Lab 9-6 NetIQ AppManager Essentials

Instructor-Led Exercise 11
Create a SQL Job to Prune Archive
Data from the Repository

Follow along with the instructor.

Rather than aggregating data that will eventually build up and not be used, the preferred way is to
use a stored procedure and create a SQL job to clean the database. This will make the
ArchiveData table a FIFO table.
1. Open SQL Server Management Studio and click Connect when prompted.
2. Expand SQL Server Agent and click on the Jobs folder.
3. On the right side you will see all the jobs that maintain AppManager. Right-click and choose
New Job.
4. Name it NetIQ Delete Old Archive Data.
5. Click on Steps in the left pane and select the New button at the bottom.
6. Name the step Delete.
7. Make sure the Database is set to QDB (or the name of your AppManager database).
8. In the Command box, type: exec DeleteOldArchiveData 40 and then click OK.
In a large enterprise, you should tune the QDB to about 1 month of data and then use
Analysis Center for long term reporting needs. Setting the QDB for 40 days still lets you do
monthly reporting with a 10 day window to reprocess reports if needed.
9. Click on Schedules on the left and select the New button at the bottom. Create a daily
schedule. Avoid running this job between 1:30 AM and 2:30 AM. This is when several of our
jobs already run. Also, make sure this job does not conflict with a backup window or
maintenance plan in your environment.
10. Click OK to close the New Job window and you will see the new job in the list. Now your
archive data maintenance is automated.
11. If you want to be sure the job will run okay, right-click it and choose Start Job at Step… to
give it a test run. Make sure it completes successfully.

Create a SQL Job to Prune Archive Data from the Repository Instructor-Led Exercise 11-1
Instructor-Led Exercise 11-2 NetIQ AppManager Essentials
Lab 10
UNIX Agent Installation (Optional)

Exercise 1: Install a UNIX Agent

This optional lab demonstrates installing an agent on a UNIX server so that you can monitor
that server. Perform this lab only if you are interested in gaining experience in monitoring UNIX
servers.
You will install the AppManager agent on a Linux virtual machine (VM). The VM contains the
agent install files in the /root/NetIQAgent directory.
Note
Some classes may have different versions of the software or different locations for the
AppManager agent software. Confirm the location of the software for this lab with your
instructor.

Required VMs If Performance Prerequisites

Allows

AM7DC AM7SQL1 None

LinuxAS21 AM7NT

UNIX Agent Installation (Optional) Lab 10-1

Task 1: Ensure Connectivity with the AppManager Server
1. Launch the Linux VM. (Follow instructions given by the instructor.)
2. Once the Linux VM boots up, click in the login field and log in as root, with password
P@ssw0rd.

3. When the VMware Tools Properties dialog appears, minimize it.

4. Right-click on the desktop and select New Terminal.
5. Test connectivity between your AppManager server and the Linux VM by issuing the ping
command on both servers.
− On Linux, ping AM7DC (Press ctrl+c to stop the ping.)
− On Windows, ping LinuxAS21.
Do not proceed to Task 2 until you can successfully ping on both machines. Check with
your instructor if you need help.
Note
If you are using a configuration other than the recommended lab setup and the IP addresses
of the two systems are not on the same network, make sure that you change your Linux VM
to get an IP address in your windows network (use DHCP, if possible). You can do this on
Linux by issuing the netconfig command.

Task 2: Install the AppManager UNIX Agent

1. Navigate to the Directory containing the UNIX Agent install files.
cd /root/NetIQAgent/UnixClient

Note
Remember, all UNIX commands, file names and folder names are case sensitive.

2. Start the installation program by issuing the following command:

./netiq_agent_install
3. Press enter to continue.
4. For Do you want to read the agreement now, type n for no.
5. To agree with the license agreement, press Enter.
Installation verifies the system environment for the installation.
6. Press Enter to continue.
Installation performs a system configuration check to ensure that your system meets all the
hardware and software requirements for the installation.
7. When asked to inherit settings from previous installation, answer n for no.
8. Press Enter to continue.
9. For the name of your management server, type the hostname of the machine hosting the
management server (AM7DC).
10. For the port number of the management server, press Enter to use the default value of
9001.
11. For the type of communication security, press Enter to accept clear text messages.

Lab 10-2 NetIQ AppManager Essentials

12. For Do you want to allow this agent to communicate with other Management
Servers, press Enter (this default restricts management server communication).
13. For Enter a name for agent computer, press Enter to accept the default hostname
(LinuxAS21).
When installation adds this machine to the TreeView pane of the console, it uses this entry as the
machine name. If your environment does not include a DNS server, you must enter the IP
address (or create a host entry, as has been done in the VM).
14. To use the default destination path of /usr/netiq, press Enter.
15. For the user name that runs the NetIQ UNIX Agent, enter netiq.
The AppManager UNIX agent does not need to run as a root account. This machine already has
a non-root user account called netiq to use for the agent install.
16. For Do you want to give netiq the root privileges, press y for yes.
17. For Do you want to Add/Modify Unix agent startup options, press Enter for no.
18. When prompted to stop the running agent so the install can proceed, press Enter to accept
the default [y].
19. To confirm that you are ready for the install, press Enter for yes.
Installation unpacks and installs the agent.
20. When the installation is complete, press Enter to continue.
21. For Do you want to install NetIQ Unix Application Management components, press
Enter for yes.

This allows you to detect and install AppManager components for selected applications.
22. Press Enter to continue.
Installation performs a preinstall check for application components.
23. When the preinstall check is complete, press Enter.
24. To not install WebSphereAppSrv managed components, press n.
If any other component prompts occur, press n to skip installation.
25. To start the UNIX agent, press Enter for yes.
26. To perform auto discovery, press Enter for yes.
27. When prompted to keep a backup copy of the previous installation, answer n for no. (For
the VM in the classroom, doesn't matter what you answer here).
The installation of the NetIQ AppManager UNIX agent is complete.

UNIX Agent Installation (Optional) Lab 10-3

Task 3: Verify that the UNIX Agent is Running
1. Verify that the nqmagt process is running, by issuing the following command.
ps –ef | grep nqm
If your results are not similar to the example shown below, notify your instructor and verify
that the nqmdaemon is started.

2. In the Operator Console on the host machine, verify that the UNIX agent shows in the
TreeView and has been discovered.
− If the UNIX machine shows in the console, you have completed this exercise.
− If the UNIX machine is not showing, proceed to the next task.

Task 4: Add to the Operator Console and Discover the UNIX Agent
Complete this task only if the UNIX machine is not showing in the TreeView of the Operator
Console.
1. In the Operator console, from the TreeView menu select Add Computer.
2. Select Unix Computer and type the hostname of the Linux agent from Task 1. Make sure
Discover Unix objects automatically is checked.
3. Click OK.
AppManager adds the Linux machine to the Operator Console. The machine is grayed out
initially. In less than a minute the discovery job should run on this computer.
Note
The UNIX agent gets the job only when the agent sends a heartbeat, which by default is
every 30 seconds.

Lab 10-4 NetIQ AppManager Essentials

Appendix A
Answers to Scenario Exercises

Lab 7: Knowledge Script Implementation

Requirement 1
1. Create a KSG called NT Core Policy and apply policy on NT Group/View:
• NT_CPULoaded
• NT_Memory,
• NT_DiskSpace
• NT_ServiceDown
2. Set schedule for every 15 minutes
3. Collect Data
4. Specify actions to reflect the following:
• LEVEL1SUPPORT: New Events (7am-7pm)
• LEVEL2SUPPORT: Event occurs 2 times (7pm-7am)
• LEVEL3SUPPORT: Event occurs 4 times (All Hours)
5. On the Advanced tab specify to collect data every second iteration.
Requirement 2
Create a Knowledge Script Group called Core SQL Scripts and apply policy on SQL
Group/View:
• SQL_Accessibility
• SQL_DB Space (80%)
• NT_ServiceDown (SQL Services only)

Requirement 3
1. Add the following actions to SQL_MonitorJobs Knowledge Script:
• SQL DBA GROUP for New Events (Work Hours)
• HELP DESK GROUP for New Events (Non-Work Hours)

Answers to Scenario Exercises Appendix A-1

 Requirement 4
1. Add the RemoteServiceDown Knowledge Script to CATraders tab.
2. Within CATRADERS, include:
• NETIQMC
• NETIQCCM
• NETIQMS
3. Include Action SMTPMAIL_AMADMINS
Requirement 5
1. Copy the NT_PingMachine Knowledge Script and add it to the CATraders tab.
2. Enter the addresses to ping.
Note
Although it was not stated in the directions, adding an action would be a good thing.

Lab 8: Security Manager

1. Use Security Manager to create a SQL account called manager that is an AppManager user.
Copy the Read-Only User Role, restrict the Views and then assign manager to this new Role.
2. Edit the autologinreports.asp file with the appropriate login parameters (make sure to set the
NT Authentication to 0). Management will use the following URL to access reports:
http://AM7DC/netiq/autologinreports.asp
3. Test to ensure that Management can access the Web Console reports section without
password and that the manager login can access the Operator Console.
4. The account should have the following permissions:
• View only NT, IIS, and SQL
• Read-only rights

Lab 9: Reporting
1. Create daily and weekly reports for CPU and Memory data streams with actions
SMTPMail_ITManagers.
2. In Custom 1, add the location of the servers.

Appendix A-2 NetIQ AppManager Essentials