Ryan Run Book v2

Ryan Run Book v2
This guide is designed to describe an example N-central

v6.7 server configuration as well as customer deployment.
This guide will serve as an example of N-central Best
Practice configuration. The topics covered within this
document are:
Contents
System Level N-central Defaults ................................................................................................................... 2
System Level Service Templates ................................................................................................................... 4
SO Level Service Templates .......................................................................................................................... 4
SO Level Notifications ................................................................................................................................... 6
SO Level Folder Templates .......................................................................................................................... 16
Customer Deployment ................................................................................................................................ 31
Customer Network Preparation.............................................................................................................. 31
N-central Deployment ............................................................................................................................ 32
Troubleshooting: ..................................................................................................................................... 34
Additional Troubleshooting .................................................................................................................... 39
Activate Notifications.............................................................................................................................. 41
Day-to-Day Use Case(s): .............................................................................................................................. 43
Modification Template Use Cases .......................................................................................................... 43
Add Monitoring Services: .................................................................................................................... 43
Modify Monitoring Services: ............................................................................................................... 44
Remove Monitoring Services: ............................................................................................................. 46
Troubleshooting Modification Template Use Cases: .......................................................................... 46
Notification Templates Use Cases .......................................................................................................... 49
Gold Service Contract Notification Strategy: ...................................................................................... 49
Silver Service Contract Notification Strategy: ..................................................................................... 54
Ryan Run Bookv2 1|Page

Bronze Service Contract Notification Strategy: .................................................................................. 57
Folder Template Use Cases ..................................................................................................................... 60
Customer specific Folder Template to contain only VOIP Phones: .................................................... 61
System Level N-central Defaults

System Level N-central Defaults dictate behavior of the N-
central server when setting up monitoring for customer
devices. The Assigned services here will be applied to
customer devices based on probe based discovered asset
information.
- Choose System Level of navigation tree
- Choose Setup > Defaults
- Choose Discovery Defaults
o Remove all WMI and TCP port monitoring
services from Assigned Services Listing leaving
only SNMP based monitoring services

System Level Service Templates
System Level Service Templates are used as default
monitoring templates by all Technicians to set the
monitoring configuration standard for all customers.
These templates can only be adjusted by the
productadmin@n-able.com account. As technicians will
have SO level accounts, they will not be able to adjust the
system level service templates. This allows you a method
of securing your monitoring templates to be used as a
monitoring standard by all technicians for all customers.
Additional services templates can be found at https://nrc.n-
able.com within the Community tab. Download and
Extract any required service templates to the local
computer.
System Level of Navigation Tree:
- Setup > Service Templates
o Import
o Browse to Service Templates
o Import Services Templates
o Import > OK
SO Level Service Templates

SO Level Service Templates will be used to globally
manipulate applied monitoring services to customer

devices. These templates can be adjusted by any SO
Level Admin or Technician Account.
Four additional Service Templates will be created at the
SO Level which will serve as Modification Templates.
Modification Templates will be used to Add, Add or Modify,
Modify or Remove applied monitoring services to
customer devices. For usability examples of Modification
Templates; see Day-to-Day Use Case(s) section of this
document.
SO Level of Navigation Tree:
- Setup > Service Templates
- Add
- In Name field, *** Servers Modification Template ***
- In Class drop-down box, Windows Server
- Save
- Add
- In Name field, *** Workstation Modification Template
***
- In Class drop-down box, Windows Workstation
- Save
- Add
- In Name field, *** Network Device Modification
Template ***
- In Class drop-down box, Switch/Router
- Save
- Add
- In Name field, *** Printer Device Modification
Template ***
- In Class drop-down box, Printer
- Save
SO Level Notifications
SO Level Notifications will serve as notification templates
of all or any customers. These notification templates
should reflect the different Managed Services Programs of
your organization. For the purpose of this document, we
will create a notification template for a single Managed
Service Program that all customers are enrolled in. For
additional Notification Template examples for multiple
Managed Services Programs, see Day-to-Day Use
Case(s) section of this document.
- Setup > SO Accounts
o Add
o In Email Field, enter username of account to be
notified
o In Password Field, enter password (must contain
3 special characters)
o In First Name Field, enter Surname
o In Last Name Field, enter First name
 This will display account Firstname,
Lastname everywhere in N-central
o Save and Continue
o In Email Address Field, enter valid email to be
notified
o Save
Notifications will be prioritized into 3 main categories:
1. Priority1 – 0 minute delay
a. Availability of critical devices and applications
2. Priority 2 – 30 minute delay
a. Performance of critical devices and applications
3. Priority 3 – 90 minute delay

a. Availability of less-critical devices and
applications
- Setup > Notifications
o Place Checkmark beside Default notification and
choose Delete
o Ensure Propagate is selected and choose Yes
o Choose Add Notification
 In the Name Field, enter Priority 1 – 0min
delay
 Select, Single Device, Multiple Service
Notifications
 In Primary Notification Delay, enter 0
minutes
 Leave Notification Recipient Blank
 Notifications will be activated once
monitoring has been deployed and
finalized for a customer. This is
described in the Customer Deployment
section of this document
o Choose Save and Continue

o In the Trigger Name Field, enter N-central Probe
Failure
o In State drop-down, select Failed
o In the Service box highlight:
 Probe Status
o Choose Add Trigger
o In the Trigger Name Field, enter Server
Availability Failure
 Connectivity
 Disk
 Exchange 2003 and/or Exchange 2007
 Process
 Windows Service
Hardware Availability Failure
o In State drop-down, enter Failed
 Fan Status (Dell)
 Fan Status (HP)
 Physical Drive (Dell)
 Physical Drive (HP)
 Power Supply (Dell)
 Power Supply (HP)
 RAID Status (Dell)
 RAID Status (HP)
 Server Temp (Dell)
 Server Temp (HP)
o In the Trigger Name Field, enter Network Device
 Connectivity
o Choose Finish
Ryan Run Bookv2 10 | P a g e

delay

Notifications
minutes

Performance Failure

 CPU
 Disk Queue Length
 Memory
 SMTP Queues
 Traffic
Performance Failure
 Traffic
o Choose Finish

delay
Notifications
minutes

o In the Trigger Name Field, enter Workstation

Failure
 AV Security Center
 Disk
o In the Trigger Name Field, enter Printer Failure

 Toner Level
o Choose Finish
SO Level Folder Templates

Folder Templates are groupings of devices. N-central
comes with many stock Folder Templates that will contain
different types of devices. New Folder Templates can be
created to contain a specific Class or device and/or
specific Operating System and/or specific device name.
Folder Templates can be used to automatically associate
devices to service templates as well as notification
templates. Best Practices would dictate associating
service templates and notification templates that are
relevant for each type of device within each customer, as
specific service templates and notification templates can
be associated at each customer level. Within this setup,
Folder Templates will be configured to associated default
monitoring and notifications for typical customer devices.
For additional Folder Template examples, see Day-to-Day
Use Case(s) section of this document.

- Setup > Folder Templates
- Choose SBS Servers folder
- Choose Smart Folder Details
o In Match, ensure All is selected
o In Device Classes, ensure Windows Servers is
selected
o In Operating System, ensure:

 Microsoft Windows 2008 Small Business
Server
 Microsoft Windows 2008 Small Business
Server x64 Edition
 Microsoft Windows 2003 for Small Business
Server
 Microsoft Windows 2003 for Small Business
Server x64 Edition
- Choose Folder Details tab

- Scroll Down to Notification Profiles section
o Choose
 Priority 1 – 0min delay – Server Availability
Failure
 Priority 1 – 0min delay – Server Hardware
 Priority 2 – 30min delay – Server
Performance Failure
- Scroll Down to Service Templates section
o Choose
 Active Directory
 Exchange 2003 OR Exchange 2007
 IIS v6
 Windows Servers
 *** Windows Servers Modification Template
***
o Choose Save

- Choose Network Devices folder
o In Device Classes, ensure Switch/Router is
selected
o Choose
 Priority 1 – 0min delay – Network Device
 Priority 2 – 30min delay – Network Device
Performance Failure
o Choose
 Network Device
 *** Network Device Modification Template ***
o Choose Save

- Choose Windows Servers folder
o In Device Classes, ensure Windows Servers is
selected
o Choose
 Priority 1 – 0min delay – Server Availability
Failure
 Priority 1 – 0min delay – Server Hardware
 Priority 2 – 30min delay – Server
Performance Failure
o Choose
 Windows Servers
 *** Windows Servers Modification Template
***
o Choose Save

- Choose Windows Workstation folder
o In Device Classes, ensure Windows Workstation
is selected
o Choose
 Priority 3 – 90min delay – Workstation
Failure
o Choose
 Windows Workstation
 *** Windows Workstation Modification
Template ***
o Choose Save

- Choose Windows Laptops folder
o In Device Classes, ensure Windows Laptop is
selected
o Choose
 Priority 3 – 90min delay – Workstation
Failure
o Choose
 Windows Workstation
 *** Windows Workstation Modification
Template ***
o Choose Save

- Choose Printers folder
o In Device Classes, ensure Printer is selected
o Choose
 Priority 3 – 90min delay – Printer Failure
o Choose
 Printers
 *** Printer Devices Modification Template ***
o Choose Save

The steps outlined above have allowed you to configure
your N-central server with new Service Templates,
Modification Service Templates, Notification Templates
and Folder Templates and you are now ready to deploy N-
central to your customer environments.
Customer Deployment
This section will describe an example of best practices
when deploying a customer and will be broken in these
sections:
- Customer Network Preparation
- N-central deployment
- Finalize Monitoring
o Troubleshooting
- Activate Notifications
Customer Network Preparation

It is strongly suggested to enable SNMP on all routers,
switches, printers and servers within the customer
environment. Please stipulate the same SNMP Read
community string on all devices. This should be
completed before deploying the N-central probe or agents
to the customer’s environment.

N-central Deployment
N-central can be deployed through 3 different methods,
Probe based deployment, Group Policy Deployment
and/or Manual Device creation. For the purpose of this
document, we will use a Probe based deployment.
- Through existing remote access or physical access,
logon to the device you wish to install the probe
application on within the customer’s environment
- Open a web-browser and logon to your N-central
server https://<n-centralFQDN>
- Choose SO level of navigation tree
- Select customer wizard from bottom-left of UI
- Stipulate customer name
- Maintain defaults for Auto-import options and install
agents on Windows Workstation and Windows
Servers
- Maintain defaults for Remote Control Settings and
install Remote Support Manager
- Choose Save and Continue
- Choose Download Windows Probe
- Begin installer of Windows Probe
- Within Windows Probe Installer, you will be asked for
Proxy information, domain administrator account and
private IP range to scan for devices as well as SNMP
community string.
- Complete Windows Probe installer

- After approximately 2 – 10 minutes the probe will
have discovered all devices within the customer’s
environment. Due to the default auto-import options,
you will see Windows Servers and Windows
Workstations begin to populate the Customer specific
All Devices View.
- Please choose device names to review automatic
monitoring that has been established through the use
of Folder Templates
- Once all Windows Servers and Windows
Workstations have been imported you are free to
establish environment specific monitoring for the
customer if required.
Customer Level of Navigation Tree
- Choose customer specific All Device View
- Choose Folder to View at the top of UI
o Choose Windows Servers
- Place a check mark beside any servers that require
additional monitoring
- Select the More Actions drop-down box
o Choose Apply Service Templates
- Select any multiple of service templates that are
relevant for the selected devices

Troubleshooting:
This section will provide examples of how to achieve
monitoring and management for devices that have not
been initially discovered as Windows devices,
Switches/Routers or Printers.
Windows Devices Not Initially Discovered Properly
There are many reasons why a windows device has not
been discovered properly. Some common reasons are
that a software firewall has blocked remote queries from
the probe, the device is not joined to the Microsoft name
(therefore the probes credentials are not valid for that
device) or the device has the Vista operating system
installed. Vista’s UAC (user-access control) can block
remote queries from the probe. By installing Agents on
the windows workstations, will achieve all the monitoring
and management you require for the device.
Choose customer specific All Devices View
- Choose Import button
o This will display all discovered devices that have
not been imported into N-central
- Based off your knowledge of the customers network
or from device naming you can determine which are
Windows Devices.
- Place a check mark beside all assumed Windows
Devices and Choose Import.
- Choose Continue from next screen
- With all to be imported devices listed and selected,
choose Edit Devices
- Choose Windows Workstation in the Device Class
field
- Choose OK
- Choose Edit Devices
- Choose Windows XP Professional
o It will be no problem if you do not know the actual
installed Operating System, once the Agent in
installed, the asset information will be updated to
reflect the installed Operating System
- Choose install Agent check box
o Choose Install Using check box
- Choose Save
- You are returned to the to be imported devices listing
and choose Finish
- Choose the Windows Workstation dashboard within
the navigation tree
- Within approximately 5 minutes you will see all agents
be successfully installed on workstations and
monitoring be applied.
- To ensure all monitoring is applied to these devices,
choose the customer specific All Devices View.
- Choose Folder to View
o Choose Windows Workstations
- Place a check mark beside all Windows Workstations
- Choose Apply Service Templates from the More
Actions drop down menu
- Select Windows Workstation Service Template and
choose Apply
Network Devices Not Initially Discovered Properly
Switches, routers and printers that have not been
discovered properly may not have SNMP enabled or
SNMP is enabled but with a different community string
than the SNMP community string entered in the probes
initial network discovery job. To achieve the monitoring
you require, the SNMP community string will have to be
adjusted or enabled. This can usually be done remotely
with N-central.
- Choose customer specific All Devices View
- Choose Import button
o This will display all remaining discovered devices
that have not been imported into N-central
- Based off your knowledge of the customer’s network
or from device naming/IP you can determine which
are Network Devices.
- Place a check mark beside all assumed Network
Devices and Choose Import.
- Choose Continue from next screen
- With all to be imported devices selected
- Choose edit devices
- Select SNMP enabled
- Choose OK
- Choose Finish
o Choose Other
- This will list all assumed network devices
- Place a check-box beside each of the assumed
network devices
- From the more-actions drop down list
o Choose add service
- Ensure the windows probe is listed at the top of the
screen and place a 1 beside HTTP, HTTPS, SSH and
Telnet
- Choose OK

- This will establish monitoring of HTTP, HTTPS, SSH
and Telnet on each device
- Please select into one of the assumed network
devices and from the services tab you should see one
or multiple of the port monitoring services you added
in a normal status.
- With this information, choose the remote control tab
and select the appropriate SSH, Telnet or Web-Page
remote control method
- Choose save
- Choose Launch Remote control button at top of
device
- Through the remote control you can enable SNMP on
the device
- Disconnect your remote control session
- Choose the Discovery tab of the device
- Place a check-box beside discover SNMP interfaces
- Ensure the SNMP community string is correct
- Choose ok
You can repeat these steps for all other assumed network
devices. Once completed
o Choose Other
- This will list all assumed network devices

- Place a check-box beside each of the assumed
network devices
- From the more-actions drop down list
o Choose Edit Device
- Change the device class to Switch/Router or printer
Additional Troubleshooting
This section will assist in troubleshooting specific
monitoring services. Our Agents and Probes perform
many different WMI based queries to Microsoft devices.
The WMI namespace can fall out of sync for many
difference reasons and are bound by security permissions.
We have built within every N-central server a Renew WMI
Counters script. This script will be used to resolve issues
with monitoring service with an error message of:
“201 There is no information found for this WQL Query:
…”
If this error is found:
- Choose the affected customer within the navigation
tree
- Choose setup > Management Tasks
- Choose Add
- Select Scripting task
- Label the task

- Select Renew WMI Counters from Script repository
- Choose the affects device
- Choose Execute
- Choose Yes
“103 Unauthorized access when connect to Host = …”

If this error is found:
This is caused by the probe not have the appropriate
security permissions to remotely query that aspect of the
device.
- Within the affected monitoring service
- Choose Service Details
- Change the monitored by option to the local agent
- If no Agent is installed on the device, please install
the agent
- If this error is found when being monitored by the
probe and the agent, we must adjust the WMI security
permissions on the device
- Choose launch remote control for the affected device
to gain access to the console
- Once at the console of the device:
o Choose Start > Run
o Type wmimgmt.msc and choose OK
o Right-click WMI Control (Local) and select
Properties.

o Select the Security tab.
o Expand the Root folder.
o Highlight the CIMV2 portion of the WMI
namespace
o Select the Security button at the bottom-right
o Ensure the credentials the probe is using and the
Local System accounts have full privileges
By this time you have prepared the customers network
and deployed monitoring to all devices. We have setup
additional monitoring and ensured all monitoring is setup
correctly. At this point the customer is complete and ready
to activate notifications.
Activate Notifications
- Choose customer from navigation tree
- Choose Setup > Notifications
- Choose Priority1 – 0 minute delay
o Select the recipient to receive notifications for this
customer
o Choose Trigger Details
o Choose N-central Probe Failure Notification
Trigger
o Highlight all Probes with Probe box
o Choose Modify Trigger

- Choose Save
- Choose Priority 2 – 30 minute delay
customer
- Choose Save
- Priority 3 – 90 minute delay
customer
- Choose Save
Day-to-Day Use Case(s):

Modification Template Use Cases
As mentioned earlier within this Document, Modification

Service Templates can be used to Add, Modify,
Add/Modify and Remove monitoring services from
associated devices. Troubleshooting of this Use Case will
be found below all Modification Service Templates Use
Cases. This section will describe examples of how
Modification Service Templates can be used:
Add Monitoring Services:

This Use Case describes adding monitoring of the Print
Spooler Windows Service on all Windows Servers.
- Choose Windows Servers Modification Template
- From the drop-down list, select Windows Service
- Choose Add
- Deselect Use Defaults check box
- Insert Print Spooler in the Service Name Field
- Choose Save
- Ensure Add is selected within the Action drop-down
list
- Choose Associated Devices Tab
- Select the top check box or select multiple servers to
apply this monitoring to
- Choose Save and ReApply Service Template
- This action will Add the monitoring of the Print
Spooler Windows Service on all selected servers
Modify Monitoring Services:

This Use Case describes modifying the Disk monitoring
service on all Windows Servers. This modification will be
to disable the Disk Usage threshold as well as customize
the Disk free space threshold.
- From the drop-down list, select Disk
o Disk – is the Agent based monitoring service
o Disk WMI – is the Probe based monitoring
service
o Disk SNMP – is the Agent or Probe SNNP
monitoring service
o Typically Disk or Disk WMI is used to monitor
Disk space on a Windows Server. If you are
unsure if Agents or Probes are being used to
monitor Disk space on your customer’s server,
add both the Disk and Disk WMI services to the
Modification Template and adjust thresholds
within each Disk monitoring service.
- Choose Add
- Choose the Thresholds Tab
- Change the Disk Usage threshold to Off
- Change the Disk free space threshold to Custom
o The defaults of the Disk free space threshold is to
reach a failed status when there is less that
1048576 KB (1GB) of remaining Disk space. For
this Use Case it is required to have the Disk
monitoring service reach a failed threshold when
there is less than 2097152KB (2GB) of remaining
Disk space.
- Adjust all Disk free space threshold to reflect:
o Normal = 3000000 – 18446744073709551614
o Warning = 2000000 – 3097152
o Failed = 0 – 2097152
- Choose Save
- Ensure Modify is selected within the Action drop-down
list

- This action will Modify the thresholds of all Disk
Monitoring services on all selected servers
Remove Monitoring Services:

This Use Case describes Removing the HTTP monitoring
service from all Windows Servers.
- From the drop-down list, select HTTP
- Maintain all defaults within service Details and
Thresholds tab
- Choose Save
- Ensure Remove is selected within the Action drop-
down list
- This action will Remove the HTTP monitoring service
from all selected servers
Troubleshooting Modification Template Use Cases:

When choosing the Save and Reapply Service
Template button to Add, Modify, Add/Modify or Remove
action, you will receive a report on whether the action
you specified could be completed successfully. The
actions of Add, Modify, Add/Modify or Remove
monitoring services can only be preformed if there is
relevant asset information found on the device you are
applying the Modification Template too.
- You cannot add the monitoring of the Print Spooler
Windows Service if that specific windows service is
not found on the device or formatted differently.
o Common resolution; if you know the Print Spooler
Windows Service is found on the Windows
Servers and you have confirmed the format of
Print Spooler Service Name within the
Modification Template is identical to as it is listed
on the Windows Servers. N-central may not be
unaware that of the Windows Service “Print
Spooler” is found on the machine. Probes and
Agent will continually re-scan assets for new
information according to a schedule. You may
choose to wait until the next scan of that asset is
completed or choose to rescan the device for
asset information now.
 If Agent is installed
 Navigate to device and select device
name
 Choose Agent tab
 Adjust Asset Scan schedule accordingly
 If probe is used for Monitoring

 Choose Customer Name from
navigation tree
 Choose Setup > Asset Management
Tasks > Discovery Jobs
 Select Initial Asset Discovery Job
 Adjust Asset Scan schedule accordingly
- You cannot Modify the Disk monitoring service if no

Disks are currently being monitored on the Windows
Server
o Common Resolution; add Disk monitoring service
to the effected Windows Server.
 Choose effected customer from navigation
tree
 Navigate to device and select device name
 Choose Service Template Tab
 Select Windows Server check box
 Choose Reapply Service Template
 If No Asset Information error is returned
 The probe does not have the correct
WMI security permissions to query the
server for disk metrics
o Common Resolution; install an
Agent on the Device and once
installed repeat the reapplication of
the Windows Servers Service

Template to establish Disk
monitoring for that server
- You cannot Remove the HTTP monitoring service if
HTTP is not being monitored on the Windows Server
o Common cause; HTTP service has been
removed manually previously
Notification Templates Use Cases

Best practices for Notifications are to Prioritize
Notifications based on delay. This Use Case will describe
examples of notification templates for three different levels
of customer Service Contracts.
This Use Case will describe configuring notifications to
reflect three different customer Service Contracts; Gold,
Silver and Bronze.
Gold Service Contract includes monitoring and
management for all Servers, Switches, Routers, Printers
and Workstations
Silver Service Contract includes monitoring and
management for all Servers, Switches and Routers.
Bronze Service Contract includes monitoring and
management for all Servers only.
Gold Service Contract Notification Strategy:

1. Gold Priority1 – 0 minute delay
2. Gold Priority 2 – 30 minute delay
3. Gold Priority 3 – 90 minute delay
a. Availability of less-critical devices and
applications
delay
Notifications
minutes
Failure
 Probe Status
 Connectivity
 Disk
 Process
 Windows Service
 Fan Status (HP)
 Connectivity
o Choose Finish
delay
Notifications
minutes
Performance Failure
 CPU
 Memory
 SMTP Queues
 Traffic
Performance Failure
 Traffic
o Choose Finish
delay
Notifications
minutes
o In the Trigger Name Field, enter Workstation
Failure
 AV Security Center
 Disk
o In the Trigger Name Field, enter Printer Failure
 Toner Level
o Choose Finish
Silver Service Contract Notification Strategy:

1. Silver Priority1 – 0 minute delay
2. Silver Priority 2 – 30 minute delay

delay
Notifications
minutes

Failure
 Probe Status
 Connectivity
 Disk
 Process
 Windows Service
 Fan Status (HP)
 Connectivity
o Choose Finish
delay
Notifications
minutes
Performance Failure
 CPU
 Memory
 SMTP Queues
 Traffic
Performance Failure
 Traffic
o Choose Finish
Bronze Service Contract Notification Strategy:

1. Silver Priority1 – 0 minute delay
2. Silver Priority 2 – 30 minute delay

delay
Notifications
minutes
Failure
 Probe Status
 Connectivity
 Disk
 Process
 Windows Service
 Fan Status (HP)
o Choose Finish
delay
Notifications
minutes
Performance Failure
 CPU
 Memory
 SMTP Queues
 Traffic
o Choose Finish
Folder Template Use Cases

As stipulated earlier within this document Folder
Templates are simply groupings of devices. These
groupings can contain devices based on Class of device,
operating system installed and/or device name. This
section will contain a Use Case for a separate grouping to
contain all VOIP phones. This configuration will depend
on if the grouping of devices is relevant for all or one
customer. If this grouping is valid for all customers,
complete the steps below at the SO level of the navigation
tree. If this grouping is valid for only one customer,
complete the steps below at the customer level of the
navigation tree.
Customer specific Folder Template to contain only VOIP Phones:

For this Use Case, it is required to have a grouping for one
customer to only contain VOIP phones we will have to rely
on an existence of a standard VOIP phone naming
convention. An example of this standard VOIP phone
naming convention will be that all VOIP phone have a
DNS name of VOIP1, VOIP2, VOIP3 …
- Choose the customer level of the navigation tree
- Choose Setup > Folders
- Choose Add
- Label the folder accordingly (eg: VOIP Phones)
- Choose Smart Folder check box
- Associate the folder to an appropriate dashboard (eg:
Network devices)
- Associate any relevant notification templates (eg:
Network Device Availability Failure)
- Associate any relevant Service Templates if available
or required

o Connectivity monitoring service will be added
automatically regardless if any service templates
are associated to this folder or not
- Choose Continue
- Select All within the Match Criteria
- Do not select any device class or operating system
- Type VOIP* within the Device Name Matching field
- Choose Finish
I really hope you have found this document informative

and was able to address the “how” questions you have
when using N-central v6.7. As N-central is a very dynamic
and robust monitoring and management solution, there
are many of methods of achieve the monitoring and
management configurations required to uphold your
Managed Services contracts. This document is to serve
as an example of best practices, when using N-central
v6.7. Other examples, methods and best practices can be
addressed by contacting the Solution Architect team by
submitting a case within the N-able Partner Portal at
https://nrc.n-able.com.
Sincerely,
Ryan Vallee


Ryan Run Book v2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ryan Run Book v2

Загружено:

Авторское право:

Доступные форматы

Ryan Run Book v2

This guide is designed to describe an example N-central

Ryan Run Bookv2 1|Page

System Level N-central Defaults

Ryan Run Bookv2 2|Page

SO Level Service Templates

Ryan Run Bookv2 4|Page

Ryan Run Bookv2 7|Page

Ryan Run Bookv2 8|Page

Ryan Run Bookv2 10 | P a g e

Ryan Run Bookv2 11 | P a g e

o In the Trigger Name Field, enter Server

Ryan Run Bookv2 12 | P a g e

Ryan Run Bookv2 13 | P a g e

Ryan Run Bookv2 14 | P a g e

o In the Trigger Name Field, enter Workstation

Ryan Run Bookv2 15 | P a g e

SO Level Folder Templates

SO Level of Navigation Tree:

Ryan Run Bookv2 17 | P a g e

- Choose Folder Details tab

Ryan Run Bookv2 18 | P a g e

Ryan Run Bookv2 19 | P a g e

Ryan Run Bookv2 21 | P a g e

Ryan Run Bookv2 23 | P a g e

Ryan Run Bookv2 25 | P a g e

Ryan Run Bookv2 27 | P a g e

Ryan Run Bookv2 29 | P a g e

Customer Network Preparation

Ryan Run Bookv2 31 | P a g e

Ryan Run Bookv2 32 | P a g e

Ryan Run Bookv2 33 | P a g e

Ryan Run Bookv2 37 | P a g e

Ryan Run Bookv2 38 | P a g e

Ryan Run Bookv2 39 | P a g e

“103 Unauthorized access when connect to Host = …”

Ryan Run Bookv2 40 | P a g e

Ryan Run Bookv2 41 | P a g e

Day-to-Day Use Case(s):

As mentioned earlier within this Document, Modification

Add Monitoring Services:

Modify Monitoring Services:

Ryan Run Bookv2 45 | P a g e

Remove Monitoring Services:

Troubleshooting Modification Template Use Cases:

Ryan Run Bookv2 47 | P a g e

- You cannot Modify the Disk monitoring service if no

Ryan Run Bookv2 48 | P a g e

Notification Templates Use Cases

Gold Service Contract Notification Strategy:

Silver Service Contract Notification Strategy:

- Choose SO level of navigation tree

Ryan Run Bookv2 54 | P a g e

Bronze Service Contract Notification Strategy:

Ryan Run Bookv2 57 | P a g e

Folder Template Use Cases

Customer specific Folder Template to contain only VOIP Phones:

Ryan Run Bookv2 61 | P a g e

I really hope you have found this document informative

Ryan Run Bookv2 62 | P a g e

Вам также может понравиться