|
Answer/Solution: Ipswitch WhatsUp Professional 2005
(SP1a) Release Notes
============
- Description
- New Features
- Fixes
- Installation
- Uninstalling
- Importing WhatsUp Gold Configuration Information
- Application Notes
- Known Issues
- For More Information
Description
===========
WhatsUp Professional is a powerful, yet easy to use Network Monitoring
application. You will be up and running within minutes with WhatsUp
Professional's easy installation and intuitive interface. In a few
simple steps, you will be able to:
- Auto-discover devices on your network.
- Set up notifications to alert you the moment that WhatsUp Professional
detects a problem.
- Generate out-of-the box reports to help you analyze your network
uptime and response time.
In addition, WhatsUp Professional allows users to view the status of a
network from a web browser. With WhatsUp Professional, you have a robust
tool that offers the essential functionality to ensure that you stay on
top of your network resources.
Supported operating systems are:
- Windows 2003 Server
- Windows XP SP1 or later
- Windows 2000 SP4 or later
Installation Requirements
-------------------------
You will need up to 256 MB of disk space free before installing
WhatsUp Professional.
To install the ecommerce version of the application, you will need an
active internet connection.
New Features In SP 1
====================
- Active Discovery allows you to scan your network on a regularly
scheduled basis.
- Reports now can now display times using a 24 hour clock, and can be
configured to display alternative date formats.
- Groups of devices can be edited at once with the Bulk Field Change
feature.
- You can limit web users access to specific device groups.
- Active Monitors can be tested before being associated to devices.
- Multiple Blackout periods can be configured for all actions.
- Up Actions can be defined to only fire after a specific Down state has
been reached.
- A new logging system, incorporating several new system level reports.
- Enhanced migration utility that allows you to import data from WhatsUp
Gold at any time.
- Acknowledgement system integrated to warn you when any past down state
has occurred.
- Database backup and restore menus added to the main console.
- Added support for comprehensive MIB browsing within SNMP Monitors.
- NT Service Monitor and Service Restart Action now use WMI for service
management.
- Web Server now supports internationalized data input. ASP pages can now
be translated to multi-byte languages such as Japanese.
Major Fixes Included in SP 1a
=============================
- Custom Links in the web interface have been updated to allow for
& and = characters.
- In SP1, a problem occurred when there was a partial registry setting
for either the single device or the regular discovery. A failure could
occur without an error message. This has been fixed for SP1a.
- Installation was modified to fix a problem with SNMP Monitors when
upgrading from the 2005 release to 2005 SP1.
- The %device.status Action variable has been changed to act as it
did in the initial version of WhatsUp Professional 2005.
- Added an option in the configuration dialog for beepers to specify the
characters used to end the transmission. (For example, this allows users
in Japan to specify ## instead of #)
- Records in the ActiveMonitorSampleData table are now reused instead of
deleted. This keeps sqlserver.exe from reaching 100% memory usage when
under heavy statistical gathering loads.
- MaxNumberOfRetries and RetryDelay values have been exposed in the
registry for Beeper/SMS/Pager Actions. The number of retries has been
increased from 10 times to 30 times once per minute. RetryDelay is set
in the registry in ms (1000ms = 1 sec)
HKLM\Software\Ipswitch\Network Monitor\WhatsUp Plugins\ActBeeper
HKLM\Software\Ipswitch\Network Monitor\WhatsUp Plugins\ActPager
HKLM\Software\Ipswitch\Network Monitor\WhatsUp Plugins\ActSMS
- MaxNumberOfRetries and RetryDelay values have been exposed in the
registry for SMTP email actions. The defaults for email actions is to
retry 10 times once per minute.
HKLM\Software\Ipswitch\Network Monitor\WhatsUp Plugins\ActSMTPMail
- WhatsUp Engine Service does not start on reboot. In some occasions
during reboot (especially when there is anti-virus software installed
on the system) SQL Server on 2003 server starts but is not initially
ready to accept connections. To account for this extra delay WUP 2005
SP1a tries to connect to SQL server for configurable time during
startup before giving up. (60 sec by default)
This timing can be further adjusted in the registry.
HKLM\Software\Ipswitch\Network Monitor\WhatsUp Engine\2005\Settings\SQL
Server Connection Delay Start.
- Up actions fire after a device comes out of Unknown state (and
maintenance). The Polling Engine now keeps an internal history of the
states for the devices and monitors, and based on the history decides
to fire or not the Up actions. The history is cleared when the actions
on a given states get executed. The unknown state is never recorded in
this history.
-Correction to SQL Injection Vulnerability on login found by iDEFENSE Security Advisory [IDEF0952] and Secunia Research [Ref No:1-19781] (http://secunia.com/advisories/15503/)
Major Fixes Included in SP 1
============================
- The WhatsUp Gold Data Migration Application has been removed from the
Install and has been reworked such that it can now be run at any time.
This is accessible from the Console Tools menu. This also allows you
to mount your WhatsUp Gold installation directory as a remote drive
and import configuration and map data to a local test machine.
Multiple improvements to definition transforms.
- Correction to a potential security vulnerability in the configuration
of Actions in the web interface.
- The Device State Change Timeline will show past statistical data for
all Monitors even if they are disabled.
- Improved the speed with which library console dialogs close and commit
their changes. For example: the Passive Monitor Library Dialog and
the Device Types Dialog.
- There is a correction to group and device states when taking a device
out of maintenance when the device had no enabled active monitors.
- Discovery now names additional interfaces correctly when Resolve
host names is turned off.
- Discovery of TCP services causes false Downs on polled devices under
heavy polling loads. Specific only to Windows XP SP2.
- The use of the default HTTP content scan can max out the CPU. The
definition of the default monitor often required expensive use of
regular expressions, this has been corrected.
- Text in the reporting charts can now support multi-byte characters
- The date time range selector was added to group reports: Performance,
Availability, and State Change Timeline.
- Passive Monitor Reports will indicate whether a Passive Monitor server
is on and accepting messages.
- Added the "home group" functionality. Home group will shortcut users
to a specific group when logging in via the web interface.
- ASP pages now compatible with IIS when using virtual directories.
- Added additional monitor details to device Availability, Performance,
and Health reports.
- Significant upgrades to Active Monitor status in State Change Timeline
reports.
- SNMP community strings that include a quote character now work
correctly, without a SQL error.
- The Device Health Report now appends the comment to the Active Monitor
name. This results in better identification.
- The various log tables are cleaned up based on an expiration timeout.
- Discovery now treats ping as a true Active Monitor. In other words,
if ping is not selected in the Discovery then no pinging is attempted
on any of the discovery devices.
- In Map view you can move the mouse over a device and it will show its
current status on the console's status line.
- "Add New Device" dialog now allows better definition of Discovery
parameters. It allows for SNMP read community, hostname resolution,
and identifying devices via SNMP,
- Added support for additional Action % variables for Passive Monitors:
SNMP PhysicalSource, SNMP LogicalSource and Eventtype (general).
- LinkUp trap was identified as linkDown and linkDown trap was
identified as LinkUp in the SNMP trap log report.
- SNMP "rate of change" and "range of values" monitors can now monitor
"timeticks" objects.
- Received SNMP Trap with agent-addr field different than the network
source address will now trigger an Event on the device with network
address bound to network source if the agent-addr IP address is not
monitored by WhatsUp.
- Made it possible to monitor hexadecimal octet string (such as Mac
address) using SNMP.
- When a Monitor changes internal state the time is recorded in
dLastInternalStateTime. At the same time a record in the
ActiveMonitorStateChangeLog is generated and the two times are now
the same.
- The error and activity logs have been redesigned and separated in
different log tables. Actions and Monitors provide more detailed
explanations of the errors.
- Although WhatsUp Professional records WinEvent log messages with the
same EventID, the generated messages are now distinguished by
category: Service, Console, Active Monitor, Passive Monitor, Action,
Web Server.
- The "Check Now" function in the console has been improved for SNMP
monitoring using "Rate of Change".
- WMI is now used for querying the NT Services state. This requires
users to specify monitor login credentials in order to function
properly.
- The engine no longer fires Actions on Passive Monitors when the device
is in maintenance mode.
- Devices in scheduled Maintenance will resume the Maintenance schedule
after an engine restart.
- The Passive Monitor servers will log their configuration parameters,
as well as port conflicts. The Web server will also log port conflicts
on startup.
- Added the helper script (upgrade_db.vbs) that can be used for manually
upgrading WhatsUp Pro 2005 database schema to WhatsUp Pro 2005 SP1
database schema.
Installation
============
To install Ipswitch WhatsUp Professional:
- If you purchased a WhatsUp CD-ROM, insert the CD-ROM into the
appropriate drive. If it does not run automatically, click Start,
select Run, and then enter the CD path followed by AUTORUN.EXE
For example: D:AUTORUN.EXE
- If you downloaded WhatsUp from our web site, run the downloaded
installation application.
During installation, Microsoft Server 2000 Desktop Engine (MSDE-2000)
will also be installed on your computer.
NOTE: Microsoft has issued a patch to MSDE-2000. Go to the Microsoft
website for more information, and for instructions on how to download
this patch.
NOTE: Due to a known issue, WhatsUp Professional should not be installed
on a Domain Controller.
http://support.microsoft.com/?kbid=815495
Potential Windows XP (SP2) Errors
---------------------------------
Microsoft Windows XP Service Pack 2 (SP2) includes Windows Firewall
Windows Firewall is an enhanced version of Internet Connection
Firewall (ICF). Windows Firewall is a host-based, stateful, filtering
firewall that discards unsolicited incoming traffic through TCP/IP
version 4 (IPv4) connections and through TCP/IP version 6 (IPv6)
connections. By default, Windows Firewall is enabled on computers that
are running Windows XP SP2.
Because Windows Firewall is enabled, Microsoft SQL Server cannot
listen to the network, even if it was previously configured to do
this.
Click the following link to view Microsoft Knowledge Base articles
that you can use to help you configure Windows Firewall to permit
access for SQL Server.
http://support.microsoft.com/default.aspx?scid=kb;en-us;841249
MSDE Information
----------------
Software and System Requirements
MSDE 2000 requires Microsoft Internet Explorer 5.0 or later be
installed. A minimum installation is sufficient, and Internet
Explorer does not have to be the default browser.
File and print sharing must be active to run Desktop Engine Setup.exe.
To verify:
1. In Control Panel, double-click Network Connections.
2. On the Advanced menu, click Advanced Settings.
3. On the Adaptors and Bindings tab, ensure that File and Print
Sharing for Microsoft Networks is selected.
A MSDE 2000 Release A installation will fail if either of the
following security policies has been set to 'Do not allow
installation':
- The Devices: Unsigned driver installation behavior local security
policy for Windows XP.
- The Unsigned non-driver installation behavior local security
policy for Windows 2000.
If you use the 'Do not allow installation' setting, you must change it
to Silently succeed before installing MSDE 2000 Release A. If
necessary, you can return the policy to its previous setting after the
installation is complete.
Note: Do not allow installation is not the default setting for these
security policies.
To set these policies:
1. In Control Panel, double-click Administrative Tools.
2. Double-click Local Security Policy.
3. Expand Local Policies.
4. Select Security Options.
5. Ensure that the following option in the right pane is set to
Silently Succeed before installing MSDE 2000 Release A:
- On Windows XP and Windows 2003: Devices: Unsigned driver
installation behavior.
- On Windows 2000: Unsigned non-driver installation behavior.
Microsoft Data Access Components
--------------------------------
MSDE 2000 Release A includes updates to Microsoft Data Access
Components (MDAC). When you install MSDE 2000 Release A, MDAC 2.7
SP1a is also installed unless Setup detects the same version or a
newer version of MDAC.
When installing MSDE 2000 Release A on a computer running Windows XP,
MDAC 2.7 will not be updated to MDAC 2.7 SP1a. If your system requires
any of the fixes included in MDAC 2.7 SP1a, you must first apply
Windows XP SP1 before you install MSDE 2000 Release A. Windows XP SP1
will install MDAC 2.7, and then MSDE 2000 Release A will apply the
patches needed for that release.
Services
--------
Stopping Services Before Installing MSDE 2000 Release A
You can install MSDE 2000 Release A without shutting down services.
If you do not shut down services, the Ipswitch WhatsUp Professional
2005 setup will attempt to shut down the following services prior to
MSDE 2000 installation. The setup will attempt to restart the services
following installation. You should confirm that all services restarted
following MSDE 2000 installation. You may be prompted to reboot the
computer when Setup is complete. Without rebooting, the following
services will fail to start:
- Microsoft Distributed Transaction Coordinator (MS DTC) and the
Microsoft Search and MSSQLServerOLAPService services.
- Microsoft Component Services, Microsoft Message Queuing, and
Microsoft COM Transaction Integrator.
You can reduce the possibility of having to restart your computer
after installing MSDE 2000 Release A by stopping these services and
applications before running Setup.
MSDE Memory Usage
-----------------
When WhatsUp Professional installs and configures a new instance of
MSDE then the default memory usage is set at 64MB. If the install
detects that an existing instance of SQL Server exists, or during a
manual installation, the memory limit is not set.
Potential Installation Errors
-----------------------------
- MSDE-2000 Installation Failure with "1639" Error Code
There are several potential causes for this error;
o Ensure that all pre-requisites listed above have been met:
(File and Printer Sharing enabled, Server Service is started,
Local Security Policies set, etc.).
o A previous install of MSDE-2000 that failed or was removed.
The MSDE install does not completely clean up behind itself,
and Microsoft recommends manual clean-up prior to
re-installation.
o Using Terminal Services Remote Desktop for the installation.
Check "ERRORLOG.DAT" from the Server "Logs" directory. The log
will have the following lines near the end of the log:
2005-01-27 17:33:16.48 spid4 Warning: override, autoexec
procedures skipped.
2005-01-27 17:35:20.37 spid4 SQL Server is terminating due
to 'stop' request from Service Control Manager.
o Check other Services that may be running and Stop the Service
during the install operation. These services include:
- Microsoft SQLServerAgent (for the "WhatsUp" instance)
- Microsoft COM Transaction Integrator
- Microsoft Distributed Transaction Coordinator (MS DTC)
- Microsoft Message Queuing
- Microsoft Search
- MSSQLServerOLAPService
- If there was a previous, non-default, installation of WhatsUp
Professional 2005 that has been removed, a "WhatsUp" Data Source
(DSN) may still exist. The DSN may point to a "WhatsUp" database
The user must decide between two courses of action:
1. Leave the WhatsUp Data Source intact, and use the existing
database. This means that the user will need to manually
configure or upgrade the WhatsUp database to a version
compatible with the installed application.
C:\Program Files\Ipswitch\WhatsUp Professional 2005\DB Scripts\Upgrade Scripts
2. Remove the WhatsUp DSN, and allow the install to configure a
default database, or upgrade an existing "WhatsUp" database
residing on the "WhatsUp" MSDE-2000 instance.
NOTE: Only default instances will be upgraded by the install.
- During upgrade, WhatsUp Professional may determine that your Active
Monitor Data Table is too large for normal processing. If this
warning is displayed, truncating the data in the SQL data table or
manually running the upgrade scripts found in the
DB Scripts\Upgrade Scripts folder. See the DB_Upgrade.txt file in
the Upgrade Scripts folder for more information. If you manually
run the scripts without truncating the data, the upgrade process
will take longer to complete.
For More Configuration Information
----------------------------------
Refer to the readme.txt file in the DB Scripts folder in the WhatsUp
Professional 2005 directory for information on how to Configure
WhatsUp Professional to work with Microsoft SQL Server or other
instances of MSDE-2000.
For more information on manually upgrading the database from WhatsUp
Professional to SP1, see the DB_Upgrade.txt file in the
DB Scripts\Upgrade Scripts folder.
Visit the Ipswitch Knowledge Base at
http://support.ipswitch.com/kb/ for the most up-to-date version of
these files. If you need to review the scripts before installing,
search the Knowledge Base for the DB_Upgrade.txt file.
Uninstalling
============
Go to the Windows Add/Remove application and select Ipswitch WhatsUp
Professional. Select 'Remove' when prompted.
You can also run the Ipswitch WhatsUp Professional install and select
`Remove'.
Migrating WhatsUp Gold Configuration Information
================================================
This WhatsUp Gold Data Migration utility migrates data from WhatsUp
Gold 7 or 8 into to WhatsUp Professional 2005 SP1. The following is a
list of the items that are migrated with this utility:
- Maps
- Service Definitions
- Events Library Definitions
- Notification Library Definitions
- Custom Device Type Definitions
- Trap Definitions
This utility can be run at any time during the operation of WhatsUp
Professional, and can be run multiple times. Each time the utility is
run, imported maps and devices will be duplicated each time, but
duplicate definitions are not imported or updated. If XYZ is exists in
the database, XYZ is ignored, even if the definition was updated in
WhatsUp Gold in the meantime.
Backup and Restore
------------------
Before you use the migration utility, we recommend that you back up
your WhatsUp Professional database, using the Back Up SQL Database Tool.
Nothing harmful happens to your database as a result of this migration,
though results may be a bit confusing if you are not familiar with the
new application and terminology.
Note: As soon as the migration utility is run, items added to the
database begin polling, even if the migration wizard has not been
completed.
Application Notes
=================
- WUP now uses WMI to monitor and restart NT Services.
Credentials for each NT Service Active Monitor and each Service
Restart Action must now be supplied. Credentials used must have
administrative privileges on the remote server. Local accounts with
credentials that match remote accounts are no longer required to
monitor remote servers.
On Windows XP Workgroup systems, existing NT Service Active
Monitors may not work with the previously used credentials.
On Windows XP systems, when you enter the user name, you must
now add the workgroup, for example: workgroup\user name
The use of WMI could have some implications if the users target
devices are behind a firewall. In order to successfully monitor
and/or restart NT services the users have to modify their firewall
settings to allow access to the target devices.
1. The RPC port (135) has to be open for connections
1.1 Modify your firewall settings to allow connections to port
135 on the target devices
2. The DCOM port range has to be defined and open for connections on
the target devices
2.1 On the target machine in a command prompt execute
dcomcnfg. On Windows XP and up that will start "Component
Services" management console. On Windows XP you can start
the "Component Service" management console from "Control
Panel"->"Administrative Tools". Then expand "Computers"
tree, right click on "My Computer" and select "Properties".
This will open a configuration dialog
2.2 On Windows 2000 the configuration dialog will open when you
start dcomcnfg
2.3 Choose "Default Protocols" tab
2.4 If the displayed list already contains
"Connection-oriented TCP/IP skip to 2.6
2.5 Click the "Add" button and in the opened dialog select
"Connection-oriented TCP/IP" from the combo box, and click
OK.
2.6 Select "Connection-oriented TCP/IP" from the list and click
"Properties..."
2.7 In the opened dialog click "Add..." and define a portrange
to be used by DCOM, and click OK, OK, and OK.
2.8 Modify your firewall settings to allow connection for TCP
protocol on the defined range of ports that you configured
in the previous step.
Known Issues
============
- Certain virus scan software programs have difficulty working with
WhatsUp Professional when script scanning is turned on. This causes
a memory leak (100% CPU usage) in WhatsUp Professional. For more
information, consult the Ipswitch Knowledgebase.
- Text to Speech Actions require SAPI v5.1. SAPI v5.1 comes by default
with Windows 2003 and Windows XP. SAPI 5.1 can be downloaded from:
http://www.microsoft.com/speech/download/sdk51/
- The use of the Device Discovery Wizard feature for cases that include
TCP service checks is artificially slowed down on Microsoft Windows
XP SP2 operating systems. Within XP SP2, Microsoft is actively
limiting the rate of outbound TCP connections in an attempt (we
believe) to control potentially malicious software (worms and virii)
on Desktop class operating systems. As a result, WhatsUp
Professional must change its discovery strategy in order to remain
reliable; this results in a slower Device Discovery Wizard on this
operating system. If this slowness is an issue, we recommend that
you install WhatsUp Professional on a server class operating system.
For additional detail or post-release news on this issue consult the
Ipswitch Knowledgebase. This is not an issue on XP SP1.
For More Information
====================
For additional information visit:
http://www.ipswitch.com/support
Download the WhatsUp Professional 2005 Getting Started Guide at:
http://www.ipswitch.com/support/whatsup_professional/index.asp |
