Escolar Documentos
Profissional Documentos
Cultura Documentos
Version 7.2
Contents
DNS Configuration 5
Discovering Devices 7
Firewall Monitoring 8
Application Monitoring 9
Patch Management 10
Probe Notifications 10
Endpoint Security 10
Management Tasks 10
Testing Notifications 11
Reporting 11
Appendix 12
Working with Proxy Servers 13
Troubleshooting 17
Troubleshooting Discovery and Agent deployment 17
Troubleshooting Notifications 18
N-central 7.2 Gettting Started
After you have set up your first network, there are a number of additional resources available to you to
show you how to setup additional features and use N-central to manage your customer networks.
Other Resources
Product Documentation
The N-central product documentation includes many additional searchable resources and trou-
bleshooting tips. Access product documentation by clicking Online Help in the N-central main menu.
-4-
N-central 7.2 Gettting Started
Best Practice Create a new Domain Administrator account that will be used only for the probe.
For more information on setting up and configuring Domain Administrator accounts, refer to Microsoft
technical documentation.
DNS Configuration
The Windows Software probe requires that DNS be configured properly in order for it to function.
Note: In DHCP networks, it is strongly advised to verify that the Domain Name System does not con-
tain duplicate addresses for workstations and laptops. Duplicate entries will cause problems when
installing agents and for N-central to function properly. To resolve the issue, configure DNS scav-
enging following the instructions provided in Configuring DNS Aging And Scavenging on page 14.
-5-
N-central 7.2 Gettting Started
5. In the Allow unsolicited incoming messages from: text field, input * to accept messages from
anyone, or the IP address of your Windows Probe.
6. Click OK.
7. Close the Group Policy Object Editor window.
8. Close the Active Directory Users and Computers window.
For more information, please refer to Microsoft's document: Enable or Disable the Remote Admin-
istration Exception.
Note: Any changes made to the group policy of a domain will not be applied by members of the domain
until one of the following conditions is met:
(Information regarding the group policy update interval and the gpupdate command is from the Micro-
soft knowledge base document titled Group Policy does not refresh.)
Before you go further, you may wish to view a few short videos about N-central network features and
other useful configuration information. These are available through the Getting Started Wizard, which
is located in the bottom left corner of every screen.
2. In the left navigation pane, select the name of the service organization for which you would like to
create a customer.
3. In the bottom left-hand corner, select the Customer Wizard.
4. In the Company Name field, enter the name of your customer and leave the default import
options as they are.
Congratulations! You have created your first customer.
-6-
N-central 7.2 Gettting Started
The reason for this is that Windows XP, Vista or Windows 7 limit the number of outbound con-
current connections. When the number of outbound concurrent connections is limited, this
impedes the ability of the Windows Probe to discover and monitor devices.
1. On the Customer Wizard screen, under Recommended Discover and Import Device, click
Download the Windows Probe Software.
Tip: For a step by step guide to downloading and installing the Windows probe software, click
Detailed installation instructions.
2. After you have started the probe installation from within the Customer Wizard, you will be prompted
to select the setup language. Select the setup language from the drop-down list and click OK.
3. The InstallShield installer will perform a check on the environment that will warn you of any
issues it may find related to the functionality of the probe within your network. These warnings or
failures should be addressed before proceeding.
4. Select the location where you would like to install the N-central probe software. Click Next to con-
tinue.
5. If you need a proxy string, select I need to use a Proxy Server and specify the proxy infor-
mation, if you need help, refer to Working with Proxy Servers on page 13.
6. Click Next.
7. On the next screen, do one of the following:
l If the probe is being installed in a workgroup, select Workgroup User, otherwise
l Select Domain User, specify the Domain Administrator credentials.
8. Click Next.
9. On the AMT Datastore Registration screen, you can optionally provide the credentials to be used
with Intel® vPro™-based devices.
10. Click Next.
Discovering Devices
1. On the Network Discovery screen, enter a name for the discovery job in the Discovery Name
field and then click Add. After you have clicked Add, you can edit the other fields on this screen.
2. In the Target Network section, select IP Range and enter the IP range (for example,
192.168.1.1-254) in which the probe will be installed.
3. Enter the SNMP Community String, which will allow for the discovery of routers, switches and
printers.
-7-
N-central 7.2 Gettting Started
4. If you want to add another discovery job, click Add; otherwise, click Next.
5. Click Install.
Note: The instructions above refer to Windows devices. Non-Windows devices need to be imported.
Congratulations, you have now created a customer, installed a probe and configured the Windows probe
to discover your customer's network. As the probe discovers devices, it will automatically install Windows
agents and import the Windows Workstations and Windows Servers that it finds – these devices can be
viewed through your customer's All Devices View.
5. Click OK.
Firewall Monitoring
N-central can monitor the following elements on most firewalls:
-8-
N-central 7.2 Gettting Started
l CPU,
l Connections,
l Memory,
l Traffic, and
l Syslog messages.
This requires SNMP and Syslog configuration changes on the firewall and asset discovery must be per-
formed again. The procedure for this is documented in "Configuring Firewall Services" available on the
N-able Resource Center under Support > Product Documentation.
This requires the installation of management agents from the appropriate vendors. SNMP must also be
configured and asset discovery performed again. The procedure for this is documented in "Configuring
Servers for Hardware Monitoring" available on the N-able Resource Center under Support > Product
Documentation.
Application Monitoring
By default, N-central has applied service templates (groups of services) to the managed devices based on
their folder membership. This will be the baseline for monitoring. Some servers will have unique appli-
cations running on them and to monitor the applications, you will need to apply the appropriate service
template.
1. Click All Devices View in the navigation pane.
2. Select the check box next to the device on which you want to monitor an application.
3. Select Apply Service Templates from the drop-down list.
4. If required, click Expand to display service templates that correspond to the device class.
5. Select the service templates as required.
6. Click > to move them one at a time or click >> to select and move all the service templates.
7. Click Apply.
8. Expand the tree in the Service Template Application Report screen to view any messages.
9. Click OK.
-9-
N-central 7.2 Gettting Started
Note: Additional Service Templates are available on the N-able Resource Center.
Patch Management
By default, the Patch Status service has been added to all Windows devices that have an agent installed.
This service monitors for missing patches. The patch management feature in N-central is an integration
with Microsoft WSUS and Microsoft Windows Update. For more information on configuring this feature,
please refer to "Providing Patch Management With N-central" available on the N-able Resource Center
under Support > Product Documentation.
Probe Notifications
By default, you will not receive an alert if the Windows Software Probe stops working. To configure noti-
fications for the Probe Status service, perform the following for each customer:
1. In the navigation pane, select the appropriate customer.
2. On the menu bar, click Setup > Notifications.
3. In the Name column, click O Minute Delay.
4. Click Trigger Details.
5. Select Servers (Applications).
6. Select the Probe.
7. Click > to move the probe to the right-hand column.
8. Click Save.
Endpoint Security
The Endpoint Security feature is powered by Panda Security applications and provides comprehensive
antivirus and anti-malware protection for Windows Workstation and Windows Servers. Endpoint Security
can also be configured for Microsoft Exchange 2003 and 2007 servers to provide integrated Anti-Virus,
Anti-Spam and Content Filtering capabilities specifically for Exchange mail servers. Endpoint Security can
be fully deployed and managed from within N-central. For more information, refer to "Endpoint Secu-
rity" in the N-central technical documentation.
Management Tasks
You can configure Management Tasks to automate routine maintenance tasks.
The following tasks can be configured for Windows devices:
l Endpoint Security Scans
l File Transfers
l Executing scripts
l Software Distribution
l WSUS server cleanup
- 10 -
N-central 7.2 Gettting Started
To access this feature, select the appropriate customer in the navigation tree and select Setup > Man-
agement Tasks.
Testing Notifications
By default, N-central is configured with a very capable notification system. In order to make sure that
your notifications are working properly, perform the following:
1. Click Service Organization in the navigation pane.
2. Click Setup > Notifications.
3. Click 0 Minute Delay.
4. Verify that the correct recipients have been configured for the notification.
5. Click Save (or Cancel if no changes have been made).
6. Select the check box next to 0 Minute Delay.
7. Click Test Notification.
You should receive an e-mail notification within a few minutes. If you do not receive a notification, fol-
low the instructions provided in Troubleshooting on page 17.
Reporting
Sample reports can be downloaded from the following link:
l http://download.n-able.com/documentation/reports/nable_reports.exe
This self-extracting executable contains a spreadsheet describing all of the available reports and the cor-
responding PDF reports.
- 11 -
N-central 7.2 Gettting Started
Appendix
The following documents provide background information to some of the procedures in the Getting
Started Guide.
l Working with Proxy Servers on page 13
l Configuring DNS Aging And Scavenging on page 14
l Troubleshooting on page 17
- 12 -
N-central 7.2 Gettting Started
If a proxy server resides on your customer’s network, you may need to configure the N-central 7.2
agent/probe software so that it can pass information through the proxy server and on to your N-central
7.2 server.
To configure an agent/probe to use a proxy string, specify the proxy string during the creation of the
agent/probe in the N-central 7.2 UI. The information below will outline the appropriate proxy string to
enter based on the type of proxy server implemented in your customer’s network.
Non-authenticating Proxies
The proxy string must have the following format:
Example: https://192.168.0.10:8080
Example: https://username:Password@192.168.0.10:8080
Example: https://OFFICE\username:password@192.168.0.10:8080
Note: Basic HTTP authentication must be activated for this to work. For more information, refer to the
Microsoft Knowledge Base document: How to Allow Third-Party Internet Application Connections
through ISA Server 2000 (specifically, Method 2: Enable Basic Authentication for Outgoing Web
Requests).
- 13 -
N-central 7.2 Gettting Started
Warning! The procedures explained above and in the Microsoft KB document should be reviewed,
approved and implemented by a Microsoft Certified Professional holding a Microsoft Certified
Systems Engineer + Internet or equivalent designation or experience.
Confirm with your customer that the operations described above are considered permissible. Do not pro-
ceed without customer consent.
It is also possible to configure an ISA server to permit direct access that will allow the agents and probes
to communicate with the N-central 7.2 server. For the steps required to make this configuration
change, please refer to the isaserver.org document: Configuring Web Proxy Clients for Direct Access.
- 14 -
N-central 7.2 Gettting Started
- 15 -
N-central 7.2 Gettting Started
5. Click OK.
6. Select Apply these settings to the existing Active Directory integrated zones.
7. Click OK.
8. Right-click the domain under the Forward Lookup Zones.
9. Select Properties.
10. Select Aging.
11. Repeat the procedure from step 4 to step 7 above.
- 16 -
N-central 7.2 Gettting Started
Troubleshooting
To change the device class and install the Windows Agent without relying on WMI, try the trou-
bleshooting procedures described below.
- 17 -
N-central 7.2 Gettting Started
Troubleshooting Notifications
Troubleshooting notifications is common in order to discover why a notification was not sent. There are
a number of potential causes for a notification not being transmitted that need to be reviewed. New noti-
fications are triggered on state changes, escalation and repeat notifications are triggered on an elapsed
time from the initial state change.
To troubleshoot notifications
1. Review the Incident Summary Report and examine the lists of all of the incidents and associated
escalations that trigger notifications, the acknowledgments, and the resolution times over a spec-
ified period. If the specific incident is listed in this report, N-central has detected a state change in a
service that is associated with a notification profile.
2. Review the Notifications Sent Report (it displays a copy of the notifications that were sent to a spe-
cific user). If the notification is listed in this report, N-central transmitted the notification. Based on
this information, you should:
a. Verify the mail relay server settings in the NAC (only if no notifications are received).
b. Verify that the message is not still with the mail relay server.
c. Verify the user's spam filter.
3. Review the User Notification Method (it determines a user's email address that is used for noti-
fications as well as the associated schedule). Based on this setting, you should:
a. Verify that the email address is correct.
- 18 -
N-central 7.2 Gettting Started
b. Verify that the schedule includes the time that the incident happened. If the incident occurred
outside the user's schedule, the incident will be listed in the Incident Summary report and no
notification will be listed in the Notification Sent report.
4. Send a test notification by performing the following:
a. Navigate to the appropriate customer.
b. Select the All Devices View.
c. Click the device that you would like to use for the test in the Name column.
d. Select the Associations tab.
e. Verify that the correct notification profiles are associated with the device.
f. Select the Status tab.
g. In the Service column, click the service that you would like to use for the test.
h. Select the Thresholds tab.
i. Reverse the values for one of the threshold settings.
j. In the navigation pane, select NOC View.
k. After a moment, the incident should be displayed and the notification email received.
5. Review the Detailed Status Report (it presents a detailed overview of the service state changes on a
device over time) and verify the time of the incident to confirm whether the service was in a Failed
state. If the service was not in a Failed state, verify that the thresholds have been configured cor-
rectly.
6. Review the Raw Monitored Data Report (it provides detailed information for a particular service):
a. Review the time period when you expected an incident.
b. Verify how long the service was in a Failed state.
c. Note the duration that the service was in a Failed state.
7. In the notification profile, review the Notification Profile Delay (the amount of time that a service
must be in a specified state before a notification is sent). If the duration that the service was in a
Failed state is less than the delay configured in the profile, you may need to adjust the delay value.
8. Verify the default Notification Profile-Triggers that are associated with the relevant folders by per-
forming the following:
a. Navigate to the appropriate customer in the navigation pane.
b. On the menu bar, click Setup > Notifications.
c. Click 0 Minute Delay.
d. Select the Trigger Details tab.
e. Verify that the service you are troubleshooting is displayed in the appropriate trigger with the cor-
rect state.
f. Verify that the service you are troubleshooting is associated with the folder to which the device
belongs.
- 19 -
Disclaimer
This document may include planned release dates for service packs and version upgrades. These dates are based on our current
development plans and on our best estimates of the research and development time required to build, test, and implement each of
the documented features. This document does not represent any firm commitments by N-able Technologies Inc. to features and/or
dates. N-able Technologies will at its best effort, try to meet the specified schedule and will update this document should there be
any significant changes. N-able Technologies reserves the right to change the release schedule and the content of any of the
planned updates or enhancements without notice. Publication or dissemination of this document alone is not intended to create and
does not constitute a business relationship between N-able Technologies and the recipient.
Feedback
N-able Technologies is a market driven organization that places importance on customer, partner and alliance feedback. All feedback
is welcome at the following email address: feedback@n-able.com.