Remote system monitor server

The Microsoft exam 70-291 measures an individual’s ability to implement, manage, and maintain a Microsoft Windows Server 2003 Network Infrastructure. Before taking the 70-291 exam, you should practice the following: Configure TCP/IP addressing on a server. Manage DHCP clients and leases, DHCP Relay Agent, DHCP databases, DHCP scope options, reservations and reserved clients. Diagnose and resolve issues related to Automatic Private IP Addressing (APIPA) and incorrect TCP/IP configuration. Diagnose and resolve issues related to DHCP authorization and verify DHCP reservation configuration. Diagnose and resolve issues related to configuration of DHCP server and scope options. Verify that the DHCP Relay Agent is working correctly and verify database integrity. Install and configure the DNS Server service. Configure DNS server options, DNS zone options, and forwarding. Configure DNS zone settings, DNS record settings, and DNS server options.Monitor DNS using tools such as System Monitor, Event Viewer, Replication Monitor, and DNS debug logs. Configure Routing and Remote Access user authentication and remote access authentication protocols. Configure Routing and Remote Access policies to permit or deny access.Configure Internet Authentication Service (IAS) to provide authentication for Routing and Remote Access clients.Manage TCP/IP routing. Manage routing protocols, routing tables, and routing ports. Monitor network traffic by using Network Monitor and System Monitor. Manage packet filters, Routing and Remote Access routing interfaces, manage devices and ports, manage routing protocols, and manage Routing and Remote Access clients. Post navigation

Remote System Control (RSC)Remote System Control (RSC) is a secure server management tool that lets you monitor and control your server over modem lines or over a network. RSC provides remote system administration for geographically distributed or physically inaccessible systems. The RSC software works with the System Service Processor (SSP) on the Enterprise 250 main logic board. The RSC and SSP support both serial and Ethernet connections to a remote console.Once RSC is configured to manage your server, you can use it to run diagnostic tests, view diagnostic and error messages, reboot your server, and display environmental status information from a remote console. If the operating system is down, RSC will notify a central host of any power failures, hardware failures, or other important events that may be occurring on your server.The RSC provides the following features:Remote system monitoring and error reporting (including diagnostic output)Remote reboot on demandAbility to monitor system environmental conditions remotelyAbility to run diagnostic tests from a remote consoleRemote event notification for over-temperature conditions, power supply failures, fatal system errors, or system crashesRemote access to detailed event logsRemote console functions on serial and ethernet portsFor information about configuring and using RSC, see the RemoteSystem Control (RSC) User's Guide, provided with the RSC software.

Upon installation, PRTG automatically creates the first probe, namely the local probe in PRTG Network Monitor, and the hosted probe in PRTG Hosted Monitor. They run on the PRTG core server system and monitor all reachable devices, servers, and services from the system, using the sensors you configure.Working only with a local probe should suffice for LAN monitoring with PRTG Network Monitor and if you want to monitor one location only. For LAN monitoring with PRTG Hosted Monitor, at least one classic remote probe is required because the hosted probe can only reach targets that are publicly available via the internet.Scenarios That Require Remote ProbesThere are several situations that make it necessary to work with remote probes in the same LAN or in remote locations:You use PRTG Hosted Monitor and want to monitor your local network.You have more than one location and you need to make sure that services are available from all locations.Your network is divided into several LANs that are separated by firewalls, and the local probe cannot monitor specific services across these firewalls.You want to monitor systems in a secure network and you need a secure connection between the PRTG core server and that network.You want to sniff packets on a different computer.You want to monitor NetFlow data on a different computer.You experience performance issues with CPU-intensive sensors like Packet Sniffer or NetFlow sensors and need to distribute the load among more than one computer.You want to monitor a non-Windows system. This is only possible with a