Quick Reference Guide

6 | Chapter 1: Overview
NMS200 Quick Reference Manual
Note: Windows Terminal Server is not supported. The installer becomes
non-responsive with Data Execution Prevention enabled. This option
is disabled by default on Windows Server 2008, but is enabled on a
Windows Server 2008 machine running Terminal Server.
• Microsoft Windows XP (Professional) with current patches applied, including SP3.
• Microsoft Windows Vista (Business and above)
• Windows 7
CAUTION:
You must disable User Access Control if you are installing on Vista,
Windows Server 2008, or Windows 7. Also: Installer may halt when
pre-existing bash sessions or cmd sessions are open. Close all such
sessions. Also: This application cannot co-exist with other installations of
Cygwin on the same Windows computer. Do not install it where Cygwin is
already installed, either separately or as part of another application. If
Cygwin is already installed, remove it before installing this application. If
you do not see any obvious indication Cygwin is installed (like an icon on
the desktop or program list, or a directory named c:\Cygwin), but suspect it
is, you can open the registry (Start > Run, then type
regedit ), and look for
HKEY_CURRENT_USER > Software > Cygnus Solutions > Cygwin.
Hardware Recommendations
NETGEAR® ProSafe® NMS200 Network Management Software contains an Application
Server that runs continuously in the background, and a Client (the user interface you actually
see). You can start and stop the client portion of the software without impacting the
application server. Device monitoring stops when you stop the application server or turn off its
host machine. The client can also be on a different machine than the application server.
Hardware recommendations are based on the different types of installation available:
Full Installation (Application server + Client) — Pentium 4, 3.2 GHz CPU, 2G RAM, and
20G available disk space.
Client only — Pentium 4, 2.8 GHz, 2G RAM, and 1G available disk space.
Basic Network Considerations
The Network Management software communicates over the network. The machine it is on
must be connected to a network for the application to start successfully. Normally the client
and server portions of the management system will be installed on the same system. The
system where the management server is installed must be configured with a static IP