System information

Chapter 2. NT Systems Management Functions

This chapter shows examples of TME 10 NetFinity for NT systems management

functions, as well as built-in systems management functions of NT.

2.1 System Management Functions Provided by TME 10 NetFinity

Within this chapter we describe all the different TME 10 NetFinity functions

available under NT with the appropriate definitions and menu descriptions. There

are two different products available for TME 10 NetFinity.

1. TME 10 NetFinity Services

TME 10 NetFinity Services should be installed on all clients to provide both

local TME 10 NetFinity support as well as to enable remote TME 10 NetFinity

functional support. Enabling remote support means that it will respond to the

requests of the manager and send the requested information to the manager

workstation. TME 10 NetFinity Services will not let you access other

workstations to do management functions. You will need to be a manager to

do that.

2. TME 10 NetFinity Manager

TME 10 NetFinity Manager needs to be installed if remote access to the

workstations or servers is required in the case of systems management. It is

also possible to run all functions locally or remotely and request all

information from a remote workstation. The TME 10 NetFinity Manager

product is a combination of the NetFinity Services and Manager product.

When using a Windows NT 3.51 server noone has to be logged on at the server

itself for the NetFinity services functions to be active. For example, this means

that the time and date controlled services using the event scheduler can run,

even if nobody is logged on. Also the NT server′s NetFinity services may be

accessed by another TME 10 NetFinity Manager over any transport protocol,

even if no one is logged on. It can also be done over an intranet or the Internet

using the Webability feature of TME 10 NetFinity as discussed in Chapter 6,

“Webability” on page 145. The TME 10 NetFinity network interface

(NETFBASE.EXE) is automatically started and becomes active during the

Windows NT 3.51 startup with all the transport protocols that were defined in the

driver configuration.