In order for the agents to function correctly with IIS 7
installations, the IIS 7.0 WMI provider must be installed on the
monitored server. There are two ways to install the WMI provider so
that the Agent will be able to see IIS7:
Install WMI Provider
Install the IIS 7.0 WMI provider by selecting the IIS Management
Scripts and Tools component under Management Tools (or Web
Management Tools). In Windows Vista, this is in the Windows
Features dialog under Internet Information Services. On Windows
Server® 2008, this is in the Server Manager under the Web Server
(IIS) role.
Install WMI Tools (includes CIM Studio)
Install the WMI Tools suite from the Microsoft Download Center
at:
Install the Management Pack and SE-Viewer on the OpsMgr 2007
Server
Identify your OpsMgr 2007 server. This is the server onto which
you installed Operations Manager 2007
Be sure that your system meets the hardware and system
requirements and that you have installed any required management
pack
Double-click the .msi file to launch the wizard to install the
Management Pack
Welcome : The Management Pack
Setup prepares the Install Shield Wizard, which will guide you
through the Management Pack installation process. Click
Next to proceed with the
installation.
License Agreement : Read and
accept the license agreement. Click Next
Customer Information : The
Customer Information window allows you enter your user and
organization name, and to restrict application access if desired.
Enter your user name and organization name. Select whether anyone
other than the user you indicated can access this application.
Click Next
Custom Setup : For a single
server installation, you will install the Management Pack, AVIcode
Intercept SE-Viewer and the Operations Console Components.
Do not de-select any of these options.
By default, the files will be installed to [drive]:\Program
Files\AVIcode\Intercept. Please note that on x64 installation,
the server agent and its associated configuration files may be
found under "Program Files ", while other components will be under
"Program Files (x86)". You may select to unpack the files to
a different destination folder. If you wish to install the files to
a different folder, click Change...,
and browse to the desired folder. You may also use the
'Space' button to check your system
for available storage space for the installation. Click
Next
Configure the Management Pack:
Specify the DNS name of the SE-Viewer location, which for a
single-server installation will be the DNS name of the OpsMgr 2007
server, such as opsmgr.companyname.com . Click Next
If you do not correctly configure the SE-Viewer
location, automatic agent deployment will fail. See the
Troubleshooting" section of this
document for more information.
Discovery and Deployment Group
Configuration- .NET Application
Discovery Group: The .NET Application Discovery group limits
the discovery scope for ASP.NET Applications and Web Services.
After installation the management pack will automatically start
discovery of Enterprise ASP.NET Applications and Web Services on
all computers that belong to the .NET Application Discovery
Group.
Include all Windows computers in the .NET Application Discovery
Group. The Setup will include the "Windows Computers Group" in the
".NET Application Discovery Group".
Configure the .NET Application Discovery group membership
manually. The setup will keep the discovery group empty. You need
to configure membership for the ".NET Application Discovery Group"
manually after the setup.
Discovery and Deployment Group
Configuration- .NET Enterprise
Agent Deployment Group: The .NET Enterprise Agent Deployment
Group limits the deployment of the .NET Monitoring Agent. After
monitoring for a .NET Application is configured using the "Add
Monitoring Wizard", the .NET Monitoring Agent will be deployed to
all computers that belong to the .NET Enterprise Agent Deployment
Group where the configured application is discovered.
Include all Windows computers in the .NET Enterprise Agent
Deployment Group. The setup will include the "Windows Computers
Group" in the ".NET Enterprise Agent Deployment Group".
Configure the Enterprise Agent Deployment Group membership
manually. The Setup will keep the deployment group empty. You will
need to configure membership for the ".NET Application Discovery
Group" manually after the setup using the Operations Manager
Console.
Import XSLT: In order to
display AVIcode events in the SCOM Console, the AVIcode XSLT must
be imported into the SCOM database. This screen is new as of
Version 5.7. Prior to version 5.7 the XSLT was imported under the
user credentials of the user running the installer setup, and tat
user may not have enough permissions to write to the database. This
new screen allows users to specify the credentials under which the
XSLT will be imported. This screen only appears if the Management
Pack feature is selected.
Server Name is the name of root SCOM server computer. This
value is not editable.
Database name is the name of SCOM database. This value is not
editable.
On the right side of the screen, select the credential under
which the XSLT will be written to the SCOM database.
The Test button checks
connection to database under these credentials and the availability
of rights to write to this DB. If an error occurs when testing the
connection, check the permissions for the selected user.
When the Management
Pack is being uninstalled, all actions are performed as the user
running the setup. The XSLT will be left in the SCOM database.
Ready to Install the Program :
Setup now has enough information to install the files onto the
machine. Click Install.
Installing the Management Pack
: Wait for the files to install
InstallShield Wizard Completed
: After the Installer successfully installs the Management Pack
onto the computer, select whether to open the configuration
utility, and click Finish to close
the installation wizard.
Configure the Run As account
The 'Run As
Profile' that discovery runs under must be associated with a domain
'Run As' profile. The Management Pack's default Run As profile is
not configured and by default all discovery runs under configured
Action Profile.
To change profile that will be configures Server Agent settings
you should do the following:
In the Operations Manager Operations console go to "Administration" "Run As Configuration" "Profiles" and check the account you
want to use has been already added, or add it to this list if
necessary.
Select the “Monitoring Agent Configuration Account”
Properties
Select the necessary account and machine, and add a new record.
The account should have local administrative rights because we need
read/write access to registry and program files folder.
Wait while the new account information is receiving by
Operations Manager (1 minute on average). A new event from OpsMgr
that says all accounts were successfully validated should be
appeared in system Event Log.
Install the Management Pack on the OpsMgr 2007 Server
Identify your OpsMgr 2007 server. This is the server onto which
you installed Operations Manager 2007
Be sure that you have already installed the following
Management Packs: Enterprise ASP.NET Applications Library, Web
Application Monitoring Library and Windows Server Internet
Information Services 2003
Double-click the .msi file to launch the wizard to install the
Management Pack
Welcome : The Management Pack
Setup prepares the Install Shield Wizard, which will guide you
through the Management Pack installation process. Click
Next to proceed with the
installation.
License Agreement : Read and
accept the license agreement. Click Next
Customer Information : The
Customer Information window allows you enter your user and
organization name, and to restrict application access if desired.
Enter your user name and organization name. Select whether anyone
other than the user you indicated can access this application.
Click Next
Custom Setup : For a
multi-server installation, you will install only install the
Management Pack on the OpsMgr 2007 server
Disable the installation for AVIcode
Intercept SE-Viewer. By default, the files will be installed to
[drive]:\Program
Files\AVIcode\Intercept. Please note that on x64 installation,
the server agent and its associated configuration files may be
found under "Program Files ", while other components will be under
"Program Files (x86)". You may also use the 'Space' button to check your system for available
storage space for the installation. Click Next
Configure the Management Pack:
Specify the DNS name of the SE-Viewer location, which for a
single-server installation will be the DNS name of the OpsMgr 2007
server, such as opsmgr.companyname.com . Click Next
If you do not correctly configure the SE-Viewer
location, automatic agent deployment will fail. See the
Troubleshooting section of this
document for more information.
Discovery and Deployment Group
Configuration- .NET Application
Discovery Group: The .NET Application Discovery group limits
the discovery scope for ASP.NET Applications and Web Services.
After installation the management pack will automatically start
discovery of Enterprise ASP.NET Applications and Web Services on
all computers that belong to the .NET Application Discovery
Group.
Include all Windows computers in the .NET Application Discovery
Group. The Setup will include the "Windows Computers Group" in the
".NET Application Discovery Group".
Configure the .NET Application Discovery group membership
manually. The setup will keep the discovery group empty. You need
to configure membership for the ".NET Application Discovery Group"
manually after the setup.
Discovery and Deployment Group
Configuration- .NET Enterprise
Agent Deployment Group: The .NET Enterprise Agent Deployment
Group limits the deployment of the .NET Monitoring Agent. After
monitoring for a .NET Application is configured using the "Add
Monitoring Wizard", the .NET Monitoring Agent will be deployed to
all computers that belong to the .NET Enterprise Agent Deployment
Group where the configured application is discovered.
Include all Windows computers in the .NET Enterprise Agent
Deployment Group. The setup will include the "Windows Computers
Group" in the ".NET Enterprise Agent Deployment Group".
Configure the Enterprise Agent Deployment Group membership
manually. The Setup will keep the deployment group empty. You will
need to configure membership for the ".NET Application Discovery
Group" manually after the setup using the Operations Manager
Console.
Import XSLT: In order to
display AVIcode events in the SCOM Console, the AVIcode XSLT must
be imported into the SCOM database. This screen is new as of
Version 5.7. Prior to version 5.7 the XSLT was imported under the
user credentials of the user running the installer setup, and tat
user may not have enough permissions to write to the database. This
new screen allows users to specify the credentials under which the
XSLT will be imported. This screen only appears if the Management
Pack feature is selected.
Server Name is the name of root SCOM server computer. This
value is not editable.
Database name is the name of SCOM database. This value is not
editable.
On the right side of the screen, select the credential under
which the XSLT will be written to the SCOM database.
The Test button checks
connection to database under these credentials and the availability
of rights to write to this DB. If an error occurs when testing the
connection, check the permissions for the selected user.
When the Management
Pack is being uninstalled, all actions are performed as the user
running the setup. The XSLT will be left in the SCOM database.
Ready to Install the Program :
Setup now has enough information to install the files onto the
machine. Click Install.
Installing the Management Pack
: Wait for the files to install
InstallShield Wizard Completed
: After the Installer successfully installs the Management Pack
onto the computer, Click Finish to
close the installation wizard.
Configure the Run As account
The 'Run As
Profile' that discovery runs under must be associated with a domain
'Run As' profile. The Management Pack's default Run As profile is
not configured and by default all discovery runs under configured
Action Profile.
To change profile that will be configures Server Agent settings
you should do next:
In the Operations Manager Operations console go to "Administration" "Run As Configuration" "Profiles" and check the account you
want to use has been already added, or add it to this list if
necessary.
Select the “Monitoring Agent Configuration Account”
Properties
Select the necessary account and machine, and add a new record.
The account should have local administrative rights because we need
read/write access to registry and program files folder.
Wait while the new account information is receiving by
Operations Manager (1 minute on average). A new event from OpsMgr
that says all accounts were successfully validated should be
appeared in system Event Log.
Install SE-Viewer on the Management System
Identify your OpsMgr 2007 server. This is the server onto which
you installed Operations Manager 2007
Double-click the .msi file to launch the wizard to install the
Management Pack
Welcome : The Management Pack
Setup prepares the Install Shield Wizard, which will guide you
through the Management Pack installation process. Click
Next to proceed with the
installation.
License Agreement : Read and
accept the license agreement. Click Next
Customer Information : The
Customer Information window allows you enter your user and
organization name, and to restrict application access if desired.
Enter your user name and organization name. Select whether anyone
other than the user you indicated can access this application.
Click Next
Custom Setup : For a
multi-server installation, you will install only install the
AVIcode Intercept SE-Viewer on the Management System
By default, the files will be installed to [drive]:\Program
Files\AVIcode\Intercept. Please note that on x64 installation,
the server agent and its associated configuration files may be
found under "Program Files ", while other components will be under
"Program Files (x86)". You may select to unpack the files to
a different destination folder. If you wish to install the files to
a different folder, click Change...,
and browse to the desired folder. You may also use the
'Space' button to check your system
for available storage space for the installation. Click
Next
Configure the Management Pack:
Specify the DNS name of the SE-Viewer location, which for a
single-server installation will be the DNS name of the OpsMgr 2007
server, such as opsmgr.companyname.com . Click Next
If you do not correctly configure the SE-Viewer
location, automatic agent deployment will fail. See the
Troubleshooting section of this
document for more information.
Ready to Install the Program :
Setup now has enough information to install the files onto the
machine. Click Install.
Installing the Management Pack
: Wait for the files to install
InstallShield Wizard Completed
: After the Installer successfully installs the Management Pack
onto the computer, select whether to open the configuration
utility, and click Finish to close
the installation wizard.
In the event a
stand-alone installation of AVIcode SE-Viewer is detected during an
upgrade in which the SE-Viewer component has been selected, a
warning will appear that will prompt you to either uninstall the
existing SE-Viewer first, or to uncheck the SE-Viewer installation
selection.
Upgrade from Management Pack versions
prior to 4.1.1 (aka SP1)
Uninstall the current version of the management pack
Now that the earlier management pack has been uninstalled,
please follow the directions above for either single-server or
multi-server installations.
Upgrade from Management Pack versions
4.1.1 (aka SP1)
Run the installer to upgrade the management pack
Check the agent version number under AVIcode .NET Application
MonitoringMonitoring
Agent State. If the agent does not upgrade automatically
within a reasonable time frame, run the task “Upgrade Enterprise
Agent” for monitored machines requiring the upgrade.
Upgrade from Management Pack versions 5.0 and later
Special notes for
upgrading from V5.1 (or V5.5 RC2) to V5.5 RTM and later
The following behaviors are due to the addition of the .NET
Agent Deployment group in V5.1 and the addition of the Discovery
Computers group in V5.5 RC2:
Any modifications made to these two groups, such as the
addition of explicit or dynamic members, will be lost during the
upgrade
During the upgrade setup, only the selection of whether to
populate these groups or not will be applied after the
installation.
If any rules have been overridden, such as the rule to enable
or disable a group, the override will be lost after the upgrade if
it has been stored in the AVIcode Overrides MP, but will be
preserved if it was stored in any other management pack.
Run the installer to upgrade the management pack
Open the Operations Manager 2007 Console.
Go to the "Authoring View"
Navigate to Management Pack Templates
"Enterprise .NET
Executable" or "Enterprise .NET Windows Service" or
"Enterprise
ASP.NET Application" or "Enterprise ASP.NET Web Service"
Select the appropriate application template from the list of
configured templates
Right-click and 'Properties' from the menu
Go to the 'Application Monitoring' tab or the 'Transaction
Monitoring' tab, and click OK
Repeat for each .NET application monitoring template
Upgrade from Stand-alone Intercept Studio
Install the Management Pack on the OpsMgr 2007 Server
Identify your OpsMgr 2007 server. This is the server onto which
you installed Operations Manager 2007
Be sure that you have already installed the following
Management Packs: ASP.NET Applications Library, Web Application
Monitoring Library and Windows Server Internet Information Services
2003
Double-click the .msi file to launch the wizard to install the
Management Pack
Welcome : The Management Pack
Setup prepares the Install Shield Wizard, which will guide you
through the Management Pack installation process. Click
Next to proceed with the
installation.
License Agreement : Read and
accept the license agreement. Click Next
Customer Information : The
Customer Information window allows you enter your user and
organization name, and to restrict application access if desired.
Enter your user name and organization name. Select whether anyone
other than the user you indicated can access this application.
Click Next
Custom Setup : For a
multi-server installation, you will install only install the
Management Pack on the OpsMgr 2007 server
Disable the installation for AVIcode
Intercept SE-Viewer. By default, the files will be installed to
[drive]:\Program
Files\AVIcode\Intercept. Please note that on x64 installation,
the server agent and its associated configuration files may be
found under "Program Files ", while other components will be under
"Program Files (x86)". You may also use the 'Space' button to check your system for available
storage space for the installation. Click Next
Configure the Management Pack:
Specify the DNS name of the SE-Viewer location, which for a
single-server installation will be the DNS name of the OpsMgr 2007
server, such as opsmgr.companyname.com . Click Next
If you do not correctly configure the SE-Viewer
location, automatic agent deployment will fail. See the
Troubleshooting section of this
document for more information.
Discovery and Deployment Group
Configuration- .NET Application
Discovery Group: The .NET Application Discovery group limits
the discovery scope for ASP.NET Applications and Web Services.
After installation the management pack will automatically start
discovery of Enterprise ASP.NET Applications and Web Services on
all computers that belong to the .NET Application Discovery
Group.
Include all Windows computers in the .NET Application Discovery
Group. The Setup will include the "Windows Computers Group" in the
".NET Application Discovery Group".
Configure the .NET Application Discovery group membership
manually. The setup will keep the discovery group empty. You need
to configure membership for the ".NET Application Discovery Group"
manually after the setup.
Discovery and Deployment Group
Configuration- .NET Enterprise
Agent Deployment Group: The .NET Enterprise Agent Deployment
Group limits the deployment of the .NET Monitoring Agent. After
monitoring for a .NET Application is configured using the "Add
Monitoring Wizard", the .NET Monitoring Agent will be deployed to
all computers that belong to the .NET Enterprise Agent Deployment
Group where the configured application is discovered.
Include all Windows computers in the .NET Enterprise Agent
Deployment Group. The setup will include the "Windows Computers
Group" in the ".NET Enterprise Agent Deployment Group".
Configure the Enterprise Agent Deployment Group membership
manually. The Setup will keep the deployment group empty. You will
need to configure membership for the ".NET Application Discovery
Group" manually after the setup using the Operations Manager
Console.
Import XSLT: In order to
display AVIcode events in the SCOM Console, the AVIcode XSLT must
be imported into the SCOM database. This screen is new as of
Version 5.7. Prior to version 5.7 the XSLT was imported under the
user credentials of the user running the installer setup, and tat
user may not have enough permissions to write to the database. This
new screen allows users to specify the credentials under which the
XSLT will be imported. This screen only appears if the Management
Pack feature is selected.
Server Name is the name of root SCOM server computer. This
value is not editable.
Database name is the name of SCOM database. This value is not
editable.
On the right side of the screen, select the credential under
which the XSLT will be written to the SCOM database.
The Test button checks
connection to database under these credentials and the availability
of rights to write to this DB. If an error occurs when testing the
connection, check the permissions for the selected user.
When the Management
Pack is being uninstalled, all actions are performed as the user
running the setup. The XSLT will be left in the SCOM database.
Ready to Install the Program :
Setup now has enough information to install the files onto the
machine. Click Install.
Installing the Management Pack
: Wait for the files to install
InstallShield Wizard Completed
: After the Installer successfully installs the Management Pack
onto the computer, Click Finish to
close the installation wizard.
Select the "State View" for each of the
following: Enterprise .NET Executable Applications, Enterprise .NET
Windows Services, Enterprise ASP.NET Applications, Enterprise
ASP.NET Web Services.
Right-click the current state for each item in the view, and
select 'Tasks''Pause Monitoring Application'
Delete any custom management packs associated with .NET
monitoring. To do this:
Go to the "Administration" View
Select the "Management Packs" node in the
'Administration' tree
Right-click each custom management pack, and select
'Delete'. This action will also delete any custom
objects that were created using the custom management pack
Check that all custom template objects have been deleted and
that none were created based on the 'Default Management Pack'.
Go to the "Authoring View"
Select each of the 'Enterprise...' nodes under the "Management Pack
Templates" node
If any custom template objects are visible, then either the
custom management pack was not deleted or it is based on the
default management pack
If the 'Management Pack' column indicates a custom management
pack, repeat the earlier steps to delete it
If the 'Management Pack' column indicates the 'Default
Management Pack', then return to the "Authoring View", right-click the
custom template objects associated with the default management
pack, and select 'Delete'.
If you created any custom template objects based on the default
management pack, the default MP must be cleaned of any extraneous
references. To do this:
Go to the "Administration" View
Select the "Management Packs" node
Right-click the 'Default Management Pack', and select 'Export
Management Pack...'
Right-click the 'Default Management Pack', and select
'Delete'
Edit the exported default management pack
Delete all sections that reference AVIcode. Be sure to remove
the entire section from the opening to closing tags as in the
example below:
<Reference Alias='AVIcode...
...
</Reference>
Save the file
Return to the "Administration" View
Right-click the "Management Packs" node and select
'Import Management Packs...'
Import the modified 'Default Management Pack'
Remote into each server for which Executable Applications
and/or Windows Services were being monitored. Stop and restart each
monitored Executable Applications and/or Windows Service
Remote into each server that was running a .NET agent. Restart
the OpsMgr Health Service
Return to the Operations Console
Go to the "Monitoring View"
Select the "Monitoring Agent State" node under
the "AVIcode .NET Application
Monitoring" node
Right-click the current state for each item in the view, and
select 'Tasks''Uninstall Enterprise Agent' with the
option 'IISReset = true'
Close (exit) the Operations Console
Go to 'Add/Remove' programs on the Operations Manager
server
Remove the AVIcode .NET Enterprise Management Pack
If you see an
error while uninstalling the management pack, it may be because
either you did not disable monitoring or because there are still
management packs installed based on the Enterprise .NET Executable
Application or Enterprise .NET Windows Service templates. Check the
Windows Event log for an information event generated from the
AVIcode .NET Enterprise Management Pack that says:
Event Type: Information
Event Source: Management Pack
Event Category: None
Event ID: 1005
Description:
Please delete following management packs
before uninstall:
Right-click the current state for each item in the view, and
select 'Tasks''Stop Monitoring for All Applications'
Delete any custom management packs associated with .NET
monitoring. To do this:
Go to the "Administration" View
Select the "Management Packs" node in the
'Administration' tree
Right-click each custom management pack, and select
'Delete'. This action will also delete any custom
objects that were created using the custom management pack
Check that all custom template objects have been deleted and
that none were created based on the 'Default Management Pack'.
Go to the "Authoring View"
Select each of the 'Enterprise...' nodes under the "Management Pack
Templates" node
If any custom template objects are visible, then either the
custom management pack was not deleted or it is based on the
default management pack
If the 'Management Pack' column indicates a custom management
pack, repeat the earlier steps to delete it
If the 'Management Pack' column indicates the 'Default
Management Pack', then return to the "Authoring View", right-click the
custom template objects associated with the default management
pack, and select 'Delete'.
If you created any custom template objects based on the default
management pack, the default MP must be cleaned of any extraneous
references. To do this:
Go to the "Administration" View
Select the "Management Packs" node in the
'Administration' tree
Right-click the 'Default Management Pack', and select 'Export
Management Pack...'
Right-click the 'Default Management Pack', and select
'Delete'
Edit the exported default management pack
Delete all sections that reference AVIcode. Be sure to remove
the entire section from the opening to closing tags as in the
example below:
<Reference Alias='AVIcode...
...
</Reference>
Save the file
Return to the "Administration" View
Right-click the "Management Packs" node in the
'Administration' tree and select 'Import Management Packs...'
Import the modified 'Default Management Pack'
Remote into each server for which Executable Applications
and/or Windows Services were being monitored. Stop and restart each
monitored Executable Applications and/or Windows Service
Remote into each server that was running a .NET agent. Restart
the OpsMgr Health Service
Return to the Operations Console
Go to the "Monitoring View"
Select the "Monitoring Agent State" node under
the "AVIcode .NET Application Monitoring
node"
Right-click the current state for each item in the view, and
select 'Tasks''Uninstall Enterprise Agent' with the
option 'IISReset = true'
Close (exit) the Operations Console
Go to 'Add/Remove' programs on the Operations Manager
server
Remove the AVIcode .NET Enterprise Management Pack
If you see an
error while uninstalling the management pack, it may be because
either you did not disable monitoring or because there are still
management packs installed based on the Enterprise .NET Executable
Application or Enterprise .NET Windows Service templates. Check the
Windows Event log for an information event generated from the
AVIcode .NET Enterprise Management Pack that says:
Event Type: Information
Event Source: Management Pack
Event Category: None
Event ID: 1005
Description:
Please delete following management packs
before uninstall:
Please note that on x64 installation,
the server agent and its associated configuration files may be
found under "Program Files ", while other components will be under
"Program Files (x86)". You may select to unpack the files to
a different destination folder. If you wish to install the files to
a different folder, click Change...,
and browse to the desired folder. You may also use the
'Space' button to check your system
for available storage space for the installation. Click
Next
If you do not correctly configure the SE-Viewer
location, automatic agent deployment will fail. See the
Troubleshooting" section of this
document for more information.
"Administration" 
"Run As Configuration" 
"Profiles" and check the account you
want to use has been already added, or add it to this list if
necessary.
AVIcode .NET Application
Monitoring
Monitoring
Agent State. If the agent does not upgrade automatically
within a reasonable time frame, run the task “Upgrade Enterprise
Agent” for monitored machines requiring the upgrade.
"Authoring View"
Management Pack Templates
"Enterprise .NET
Executable" or 
"Enterprise .NET Windows Service" or
"Enterprise
ASP.NET Application" or 
"Monitoring View"
"Management Packs" node in the
'Administration' tree