Align IT with business and deliver better service to networked
users while cutting costs and meeting Service Level Agreement (SLA)
targets – this is a typical dilemma faced by many a Novell
OES/NetWare operations team today.
Yet frequently instead of addressing these higher goals, NetWare
administrators end up struggling with more down-to-earth issues
that keep them stuck in inefficient reactive management posture.
This is because a typical Novell OES/NetWare infrastructure is a
rather complex entity with an intricate legacy of different
versions of NetWare. Adding to the challenge is the fact that
Novell OES/NetWare servers are frequently located in remote or
distributed locations and that almost each flavor of NetWare ships
with its own set of narrow-focused version-specific tools and
utilities, some of which still require error-prone, timeconsuming
manual operation and physical presence by the server console.
In this situation, the ability to centrally perform and automate
multiple-server administration, diagnosis and configuration tasks
is of strategic importance in any NetWare-dependent organization.
Especially in large environments, NetWare administrators need
cost-effective ways to control all aspects of server operation in
order to consolidate and optimize existing server assets.
To help administrators achieve operational excellence in
addressing these issues, in 1998 AdRem Software designed AdRem
Server Manager – an all-in-one tool that provides graphical remote
control over multiple Novell OES/NetWare servers from a Windows
workstation.