Release Notes Version 9.5 SP1 N-central 9.5 SP1 Release Notes

What is N-central?

N-central is the #1-rated remote monitoring and management automation solution for Managed Service Providers and IT professionals. N-central features a flexible license model, the ability to select which modules you want to use, and is available either as on-premises software or as a hosted service. N-central is used by thousands of IT service providers worldwide to automate their processes, improve their technician utilization rates, and deliver proactive and managed services to small and mid-sized businesses.

Remotely and securely from a single management console, N-central enables you to monitor your customer devices, proactively fix issues on their desktop and server systems, and automate patches, software updates, and other routine tasks.

About this Document This document is current as of Wednesday, August 12, 2015.

It includes the upgrade procedure, new features, fixed bugs, and known problems for:

l N-central 9.5 SP1,

l N-central 9.5 SP1 Hotfix 1,

l N-central 9.5 SP1 Hotfix 2, and

l N-central 9.5 SP1 Hotfix 3

- 2 - N-central 9.5 SP1 Release Notes

What's New in N-central

Welcome to N-central 9.5 SP1, the latest release of N-able Technologies' flagship remote monitoring, management and automation software.

SNMP Enhancements

l Agents can now perform SNMP discoveries.

l When Professional Mode devices are imported to N-central and SNMP is successfully discovered on the device, SNMP will now be enabled automatically.

l N-central Probes now support discovery and monitoring of Network Devices using SNMPv3.

For more information, refer to "SNMP and N-central Devices" in the N-central online help.

Usability Enhancements

l A device's given name can now be updated automatically if the discovered name changes.

For more information, refer to "Discovery Jobs" in the N-central online help.

Maintenance Window Enhancements

l The message displayed to end users when their computer is about to be restarted can now be cus- tomized.

For more information, refer to "Maintenance Windows" in the N-central online help.

Monitoring Templates and Services

l iDRAC

l SQL 2014

l Veeam

l Windows Backup

l Registry Key (Integer, String)

l Windows Firewall Status

l Windows UAC Status

l Windows Action Center Status

l Windows Reboot Needed Status

AV Enhancements

l AV Defender Profiles now include the option to copy a file to quarantine before disinfection.

- 3 - N-central 9.5 SP1 Release Notes

For more information, refer to "Settings Module" under AV Defender Security Modules in the N-central online help.

API Enhancements

l Custom Device properties can now be retrieved through N-central APIs.

For more information, refer to "Web Service APIs" in the API Level Integration Guide.

Other Changes

l Service Template propagation is now displayed in the Job Status view.

l Various supportability enhancements.

Browser All testing and software development related to Internet Explorer 9 will be Support discontinued with the next major release of N-central. Some N-central features may Notice continue to function with Internet Explorer 9 but that version of the browser will no longer be officially supported. Users may experience issues with Internet Explorer 9 and certain elements of N-central after support is discontinued.

- 4 - N-central 9.5 SP1 Release Notes

Fixed Issues

Issues Resolved in N-central 9.5 SP1 Hotfix 3 (Version 9.5.1.951)

Agents & Probes

DESCRIPTION BUG #

A problem where the probe logs were showing plain text passwords has been resolved. 72558

An issue where the MAC agent was not upgrading after a server upgrade has been 75431 resolved.

A problem where Discovery jobs were staying in progress in the UI and were unable to 75160 modify anything has been resolved.

N-central Server

DESCRIPTION BUG #

An upgrade issue where an empty region exception occurred has be resolved. 75354

An issue where despite a maintenance window being set the Windows Event Log service 75162 still sent notifications.

A service displayed as failed however the value returned for the failure falls within the 75165 normal threshold value due to localized data.

A noticed increase in CPU usage across all devices has been resolved. 75166

An issue where devices were being re-discovered with incorrect MAC Addresses has been 75159 resolved.

- 5 - N-central 9.5 SP1 Release Notes

Patch Management

DESCRIPTION BUG #

A problem where patches could not approved due to no entry for the patch in the cim_patch 71563 table for the device has been resolved.

In issue where patch cache downloads were not being initiated has been resolved. 75164

Patch files not being after a successful install has been resolved. 75158

PSA Integration

DESCRIPTION BUG #

In issue where PSA failed to create or update a ticket has been 75175 resolved.

Issues Resolved in N-central 9.5 SP1 Hotfix 2 (Version 9.5.1.450)

Agents & Probes

DESCRIPTION BUG #

The network communication code for N-central Probes has been enhanced to improve 72399 stability and reduce memory corruption errors.

A problem with the management of Agent config files that prevented the Agents from being 71681 upgraded has now been resolved.

N-central Mac OS X Agents have been enhanced to support Apple Mac OS X 10.10 Server 71660 and Apple Mac OS X 10.10.

A data communication error that incorrectly caused Agent status to be reported as Normal 71449 while services were transitioned to a Stale state has now been corrected.

A problem that caused services that were monitored by Probes to incorrectly transition to a 71447 Stale state has now been resolved.

An issue with Agent communication to the N-central server that prevented Scheduled Tasks 71446 from being run on a device has now been corrected.

- 6 - N-central 9.5 SP1 Release Notes

Automation Manager

DESCRIPTION BUG #

An access-denied error when N-central's Automation Manager attempts to run scripts has 72491 been resolved by ensuring that the \Windows Agent\Temp\Script\AutomationManager folder is accessible to authenticated users.

A problem with a custom service based on an Automation Manager policy incorrectly 71634 downloading the policy every time it needed to be run has now been resolved.

Devices

DESCRIPTION BUG #

A problem that incorrectly prevented the modification of devices from Essentials 72423 License Mode to Professional License Mode has now been resolved.

Removing a Professional Mode license from a device no longer incorrectly generates 72023 system errors.

Propagating the Unscheduled Downtime option to managed devices no longer 71364 incorrectly causes services to remain in a Disconnected state after the Agent has successfully reconnected.

Enabling a Professional Mode License on a Switch/Router class device no longer 71350 incorrectly generates system errors.

Discovery Jobs

DESCRIPTION BUG #

An issue with port access that prevented the monitoring of ESXi servers has now been 71297 corrected.

An error that caused discovery jobs to remain in an In Progress state without completing 70301 has now been fixed.

- 7 - N-central 9.5 SP1 Release Notes

Documentation

DESCRIPTION BUG #

The text for the Hint Help on the Targets tab of the AV Defender Custom Scan Task 71414 screen has been revised.

Omissions in the documentation for Windows Backup and Veeam services have now been 71289 corrected.

N-central Server

DESCRIPTION BUG #

Removing service templates prior to upgrading N-central no longer incorrectly causes the 71977 upgrade to fail.

An error with duplicate asset discovery jobs that prevented successfully upgrading N- 71496 central has now been corrected.

An error with data exports that caused backup jobs to fail has now been fixed. 71396

Software patches have been applied to address the Linux GHOST vulnerability (CVE-2015- 71352 0235).

A problem with duplicate data table names being used for custom services that prevented 71292 upgrading to N-central has now been corrected.

A problem that incorrectly prevented XMPP connections from being established following a 71268 change in the endpoint address of the N-central server has now been resolved.

Patch Management

DESCRIPTION BUG #

An issue with applying software patches that incorrectly caused devices to restart multiple 71796 times has now been corrected.

A problem with the caching of software patches that prevented applying the patches to 71116 large numbers of devices has now been resolved.

- 8 - N-central 9.5 SP1 Release Notes

PSA Integration

DESCRIPTION BUG #

Clicking on a service ticket in N-central to access Help Desk Manager now displays the 72265 correct Help Desk Manager ticket.

When migrating from one PSA solution to another, an issue that caused the mapping of N- 72083 central Customers or Sites to PSA customers to fail has now been corrected.

Exporting devices to Help Desk Manager no longer incorrectly omits some of the targeted 72032 devices.

Data exports from N-central server no longer cause issues with Device Model data in Help 72031 Desk Manager.

A problem that incorrectly prevented Downtime from being configured on devices for 71411 Customers mapped to an Autotask Customer has now been resolved.

Remote Control

DESCRIPTION BUG #

An issue preventing Remote Desktop remote control sessions from being established with 71442 target devices has now been resolved.

Scheduled Tasks

DESCRIPTION BUG #

Modifying the schedule for running an Automation Manager policy in a Scheduled Task no 72030 longer incorrectly generates system errors.

An error causing Automation Policy tasks to continue running after the associated 71551 Automation Manager policy script was deleted has now been corrected.

- 9 - N-central 9.5 SP1 Release Notes

Security Manager

DESCRIPTION BUG #

A problem that prevented AV Defender Profiles from being applied correctly to devices that 72172 had been manually added prior to N-central 9.3 Hotfix 2 has now been resolved.

Full AV Defender scans can now be run on devices even when they are disabled in the 71444 Scheduled Task profile.

The management of multiple AV Defender update servers in a single Customer or Site has 65361 now been enhanced to improve the use of system resources.

Services

DESCRIPTION BUG #

A problem with a custom service based on an Automation Manager policy incorrectly 72034 downloading the policy every time it needed to be run has now been resolved.

Custom Syslog services no longer incorrectly report malformed data to their corresponding 71728 log files.

An issue has been resolved that caused system errors when attempting to display the 71550 Logical Drive service on devices for which the operating system was not identified.

A problem that incorrectly caused the Patch Status service to transition to a Misconfigured 71440 state and displaying the error message: 201 The type initializer for 'com.nable.agent.framework.PatchManagement.Managers.ThirdPartyMngr' threw an exception. Please see KBA #10018 in the N-central online documentation. has now been resolved.

Configuring a custom service to use a calculation that measures a change in data no longer 71223 incorrectly returns an error that the operation is not allowed.

The Asigra Backup service no longer incorrectly transitions to a Failed state and reports an 71219 incorrect time for when the last backup job was run.

- 10 - N-central 9.5 SP1 Release Notes

UI

DESCRIPTION BUG #

Clicking the status icon in a Dashboard no longer incorrectly causes a system error. 71858

Modifying limits on a Customer or Site no longer incorrectly generates system errors. 71467

Displaying a ConnectWise Ticket Profile no longer incorrectly generates system errors. 71253

Attempting to simultaneously acknowledge multiple notifications on the Active Issues 71224 view no longer incorrectly causes all of the notifications to be acknowledged when the screen is refreshed.

A discrepancy that incorrectly caused differences between the list of approved patches and 71038 a list displayed for confirmation has now been resolved.

An error that prevented the Use Discovered Name feature from being deselected in the 71037 Properties tab of a device has now been fixed.

Issues Resolved in N-central 9.5 SP1 Hotfix 1 (Version 9.5.1.353)

Agents & Probes

DESCRIPTION BUG #

Mac Agents will now upgrade properly following an upgrade to N-central 9.5 SP1 Hotfix 1. 70904

An intermittent issue with network communication code no longer causes memory 70432 corruption and the subsequent failure of N-central Probes.

The Update Monitoring Software option for devices no longer incorrectly switches from 70366 Now back to Never if the device is disconnected at the time that the modification is made.

Automatic re-starting of Agents and Probes when system resource overload causes the N- 70001 central server to become unresponsive has been improved.

- 11 - N-central 9.5 SP1 Release Notes

Automation Manager

DESCRIPTION BUG #

An issue with the \Windows Agent\Temp\Script\AutomationManager folder not being 70436 accessible by authenticated users has been resolved so that it no longer causes access- denied errors when N-central's Automation Manager attempts to run scripts.

Backup Manager

DESCRIPTION BUG #

Monitoring Asigra Backup on a device no longer fails producing the error message: 70431 "Asigra: Could not establish connection with DS-Client. The listening IP or port may be misconfigured."

Devices

DESCRIPTION BUG #

Configuring a Printer device to use an Essentials Mode license no longer incorrectly 70290 disables the use of SNMP in monitoring the device.

N-central 9.5 SP1 Hotfix 1 now supports using TeamViewer Version 10 for remote control 69613 connections to managed devices.

Discovery Jobs

DESCRIPTION BUG #

Router interfaces may not be discovered correctly even if the required SNMP OIDs are 70439 returned normally.

N-central Server

DESCRIPTION BUG #

N-central has been updated to use the latest CentOS 5 kernel to improve software 70847 performance.

An issue causing the RSS feed to become unresponsive has now been corrected. 70443

- 12 - N-central 9.5 SP1 Release Notes

Patch Management

DESCRIPTION BUG #

Software patches are now downloaded correctly when they are not found in the software 70437 patch cache.

PSA Integration

DESCRIPTION BUG #

A problem with exporting data to Help Desk Manager that prevented System Manufacturer 70438 data from being included has been solved.

Reports

DESCRIPTION BUG #

A problem causing the Missing Patches report to not accurately display the target devices 70444 has now been resolved.

Security Manager

DESCRIPTION BUG #

E-mailing a scheduled AV Defender Threats report no longer incorrectly displays no data 70435 when manually generating the same report would display the data.

Security scans no longer incorrectly start outside of the configured schedule during which 70434 they were supposed to start.

Service Templates

DESCRIPTION BUG #

Cloning the "Servers - ESXi" Service Template now functions properly and does not 70409 generate system errors.

- 13 - N-central 9.5 SP1 Release Notes

Services

DESCRIPTION BUG #

Services monitored by Probes no longer incorrectly transition to a Stale state when large 71013 numbers of Service Templates are re-applied or the properties of Service Templates are modified.

A problem with the Veeam Job Monitor service that prevented upgrades to N-central 9.5 70940 SP1 Hotfix 1 has been resolved.

The Veeam Job Monitor service no longer incorrectly displays the Time Since Last 70319 Run (Hours) value as 31,000.

The Veeam Sure Job Monitor service will now be added to a managed device properly 70058 when it is included with a service template that is associated with the device.

UI

DESCRIPTION BUG #

An issue preventing the All Devices view from displaying any devices for individual 70880 Customers or Sites has now been resolved.

The Monitored By property for managed devices is now displayed consistently. 70583

Issues Resolved in N-central 9.5 SP1 General Release (Version 9.5.1.243)

Automation Manager

DESCRIPTION BUG #

A problem with the Backup Windows Event Log Automation Policy that prevented the 68793 deletion of old backup folders has now been resolved.

Running an Automation Policy with empty parameters that are not required no longer 68625 causes a system error.

Automation Manager Policies no longer incorrectly remain applied to devices that have been 68537 changed from Professional Mode to Essential Mode.

N-central no longer incorrectly identifies the version of Powershell installed when verifying 67903 the availability of Automation Manager Policies.

- 14 - N-central 9.5 SP1 Release Notes

Branding

DESCRIPTION BUG #

An issue preventing account names in customized branding from using apostrophe 66175 characters in the name has been resolved. For example, a Service Organization with the name: Heather's PC Repair will now be able to log in to an N-central with customized branding.

Branding changes to the Login Name Example field are now applied correctly. 66126

Modifications to the 'Login Name Example' property in the Manage Product Branding 66126 Settings screen no longer fail to be saved.

Custom Services

DESCRIPTION BUG #

Importing a custom service created with the original N-central SDK now automatically 68979 converts the HOUR data type to the HOURS data type for compatability with the new integrated custom service creation feature in N-central.

Using bracket characters () for calculation formulae in custom services now functions 68531 normally.

An issue with the N-able Certified Custom service 'Load Average' using an incorrect data 68521 type has been corrected so that the service functions properly.

Modifying the threshholds for an SNMP Custom Service now functions correctly. 68313

An issue with the N-able Certified Custom service 'Clustered Failover Status (NetApp)' 67341 using an incorrect OID in its calculation formula has been corrected.

Custom services will no longer incorrectly transition to a Misconfigured state when the 65288 system locale of the device is not set to English.

- 15 - N-central 9.5 SP1 Release Notes

Devices

DESCRIPTION BUG #

Devices now correctly remain in downtime during a configured Maintenance Window when 66412 Agents restart.

A problem that caused warranty information for managed devices to not be updated 67952 correctly has been resolved.

An issue preventing the use of DirectConnect for remote control sessions has been 67914 corrected.

Configuring a scheduled start date for a recurring discovery job now functions normally. 67637

Upgrading TeamViewer software on a managed device no longer causes issues with 65591 attempting to use TeamViewer to establish a remote control connection.

Links to the HP warranty web site have been updated to the correct address so that 63920 warranty information for HP devices can be verified correctly.

Discovery Jobs

DESCRIPTION BUG #

An issue with the ifAlias OID that prevented discovery jobs from correctly identifying 66014 interfaces on Switch/Router devices has now been resolved.

Documentation

DESCRIPTION BUG #

KBA80002: Permitting Our IP addresses to Reach Your Server for Maintenance and 67640 Support' has been updated to include the IP address for the N-able Support Staff section in Manila.

The documentation for Maintenance Windows has been revised to clarify the behavior when 66084 an Agent re-starts during a scheduled downtime.

- 16 - N-central 9.5 SP1 Release Notes

Maintenance Windows

DESCRIPTION BUG #

A problem causing the 'User can delay reboot' feature for Maintenance Windows to not use 67715 the correctly configured value for the time limit has been resolved.

N-central Server

DESCRIPTION BUG #

Upgrading to N-central9.5 SP1 no longer fails as the creation of custom device 69903, 70016 classes with a name longer than thirty (30) characters now functions properly.

An issue with MMS has been resolved that had prevented the proper monitoring of 69348 devices by the N-central server.

Upgrading N-central no longer automatically erases the syslog configuration for 68685 Probes so that previous configurations can continue to be used.

A problem with Openfire, messaging software used by N-central, has been 68462 corrected.

An error causing the default settings for 'Upgrade Windows Probes' on some 66886 Probes to switch from 'Never' to 'Always' during the upgrade of certain N-central configurations has been corrected.

Instructions provided for re-starting the Windows Agent service have been 66348 corrected to remove any reference to using quotation marks in the command line parameter.

Using an account name with an apostrophe character no longer incorrectly 66175 prevents the account from logging in.

A problem preventing the archive folder in the N-able Technologies installation 65918 directory from being automatically cleared has been resolved so that the folder will not take up excessive disk space.

Newly-created Customer/Admin accounts will no longer incorrectly generate 65215 system errors when attempting to log in as the timeout configured for account settings can no longer exceed 24 hours.

- 17 - N-central 9.5 SP1 Release Notes

Notifications

DESCRIPTION BUG #

A database table error that intermittently prevented modifications to Notifications from 66987 being saved has now been corrected.

Notifications will now be transmitted properly when Datastore services transition to a Failed 65626 state.

Patch Management

DESCRIPTION BUG #

Patch approvals performed against Service Organization Rules are no longer 70354 incorrectly removed after upgrading to N-central 9.5.0.353 or later.

Approved patches will now download and install correctly when FIPS compliance is 66004 enabled so that manually enabling FIPS compliance on Windows 7 devices is no longer required.

Closed tickets in ConnectWise in certain configurations are no longer incorrectly 66485 being updated/reopened when a new ticket should have been created.

When a ticket recipient is set to Reopen Tickets, multiple tickets are no longer 66455 incorrectly being generated and not auto-closing.

Scrolling on the Patches Approve/Decline Patches screen now functions 64911 properly so that if you have already made selections, one or more of the already selected items will no longer incorrectly become de-selected.

The Patch Status service now reports the status of software updates and patches 69880, 69914 correctly after upgrading to N-central9.5 SP1 even if monitoring Agents have not been upgraded.

Patch Management Profiles are now being applied correctly following an upgrade to 69894 N-central 9.5 SP1.

A problem preventing Patch Management from installing Windows Updates due to 68566 the age of the Windows Update Agent on the target device has now been resolved.

- 18 - N-central 9.5 SP1 Release Notes

DESCRIPTION BUG #

Modifying the Device Class Filter in the Approve/Decline Patches screen no longer 67368 incorrectly retains the configuration from previous patch approval sessions.

A problem causing approved software patches to not be downloaded or installed on 66004 devices that are FIPS (Federal Information Processing Standard) compliant has been resolved.

An error causing queries to servers with Probes configured to cache software patch 65828 installation files being directed to the wrong NIC address has been corrected.

N-central now correctly processes and displays software patches that are 65624 'Approved For Removal' from a device even when they have not previously been installed on the device.

PSA Integration

DESCRIPTION BUG #

N-central is now able to correctly distinguish between Service Sub Types belonging 65848 to different Service Boards now prevents Service Sub Types from appearing on more than one Service Board.

A previously implemented increase to the limit on appending notes to PSA tickets to 70030, 69976 100 notes no longer fails during high use of system resources.

Once an Autotask ticket has been closed, N-central will no longer incorrectly 70037 attempt to update the ticket.

Mapping an N-central Customer or Site to Autotask customers with similar names 68415 now functions properly.

A problem that prevented configuring the 'Return To Normal' option to 'Do Not 68285 Change the Ticket Status' from functioning properly has been resolved.

A problem with configuring ConnectWise Ticketing Recipients has been resolved so 65848 that the ConnectWise heirarchy of Service Board > Service Type > Service Sub Type > Service Item is recognized correctly by N-central.

Tickets manually configured in PSA solutions as 'Resolved' are no longer incorrectly 65840 being re-opened by N-central, marked as 'Resolved', but then not being re-closed.

- 19 - N-central 9.5 SP1 Release Notes

Reports

DESCRIPTION BUG #

Sorting the AV Defender Status report by 'Thread Definition Age Days' now functions 68733 properly.

The maximum number of records to be displayed by the System Audit Report has been 68040 reduced so that the report no longer causes the N-central server to run out of memory.

When generating the Warranty Expiry report, selecting the specific Customers or Sites to 67889 be included in the report now functions normally.

Rules

BUG DESCRIPTION #

An issue causing Rules to incorrectly be associated with Customers or Sites to which they 69978 should not has now been corrected.

An issue causing duplicate Agent identifiers to be associated with devices (and subsequent 68639 problems with managing devices that appear to have multiple Agents installed) has been corrected.

Deleting a Filter will no longer incorrectly cause customer-specific Rules to be applied or 68305 associated with another Customer or Site's managed devides.

Incorrect processing of Rule deletions has been corrected so that error messages are no 67679 longer displayed when deleting a device that had previously been associated with the deleted Rule.

- 20 - N-central 9.5 SP1 Release Notes

Scheduled Tasks

BUG DESCRIPTION #

The Shadow Protect script used to test backup and disaster recovery software no longer 68412 incorrectly provides NULL values.

Selecting all of the Scheduled Tasks for deletion when there are Profile-Based tasks 67929 included no longer incorrectly causes system errors.

The Shadow Protect script no longer generates incorrect script errors when run on a device 67427 that does not have Shadow Protect installed.

End time cannot be before start time' errors are no longer incorrectly generated when 66279 attempting to run Scheduled Tasks once.

An issue causing scripts that use task or device credentials to continue running without 65392 being completed has been resolved.

Security Manager

BUG DESCRIPTION #

The scan log for Full AV Defender scans has been improved to provide readable text strings 68660 instead of numeric values for the Resolved Issues section.

An issue preventing the 'Install Security Manager' check box from being displayed on the 68101 Properties tab of Microsoft Hyper-V Server 2008 R2 devices has been corrected.

Using the 'Search by Custom' feature to filter the list of Security Events now functions 67780 normally.

Disabling AV Defender no longer incorrectly prevents the application of configured 66737 exclusions when performing On-Demand scans.

- 21 - N-central 9.5 SP1 Release Notes

BUG DESCRIPTION #

A problem preventing Security Manager software from being uninstalled when an Agent is 65184 removed from the device has now been corrected.

A new 'File Deletion Settings' option has been added to the Advanced tab of the Settings 65007 Module for AV Defender allowing users to select either 'Move file to Quarantine' or 'Delete file permanently' as the action to be performed when files are disinfected or deleted.

Service Templates

BUG DESCRIPTION #

Applying service templates to devices that include the Interface Health or Traffic services 67259 no longer configures incorrect interface properties.

When adding the AV Defender Security Event service to a new service template, the 67078 'Phishing Webpage Blocked' option is no longer incorrectly prevented from being included in the list of Monitoring Actions.

Services

BUG DESCRIPTION #

CPU and Memory services will now correctly update report graphs as data is being 70028 collected.

A problem causing the Exchange 2003 service to incorrectly transition to a Misconfigured 69979 state has now been resolved.

An error in one of the calculation formulae for the Disk (SNMP) service has been corrected. 69920

AV Status services running on devices using Windows XP are no longer incorrectly 68636 transitioning to a Misconfigured state after upgrading to N-central 9.5.

Disabling the scaling of thresholds for a service now functions properly. 68608

- 22 - N-central 9.5 SP1 Release Notes

BUG DESCRIPTION #

A problem that caused some services monitored by Agents to transition to a Stale state has 68139 been resolved.

Modifying the 'Retry Monitoring' property for the Self-Healing configuration of a service no 68110 longer incorrectly causes system errors.

Changing the monitoring Probe for the Interface Health and Traffic services now functions 67376 properly.

Service status charts displayed for the Process service are now sorted in the correct order. 67355

Duplicate email notifications are no longer incorrectly transmitted when a service that is 67199 part of a Service Grouping transitions to a Failed state.

After the unsuccessful removal of third-party security software and the installation of AV 67131 Defender on a device, the AV Defender Status service no longer incorrectly remains in a No Data state.

An issue with the detection of duplicate security events no longer causes the AV Defender 66922 Security Event service to incorrectly send notifications of event types for which it is not configured.

During a scheduled downtime, a failure of the Agent to communicate with the N-central 66412 server will no longer cause the Agent Status service to transition to a Failed state as the service will now continue to remain in a Disconnected state.

Scaled units are now correctly displayed for the status details of the Traffic service. 65600

The Asigra Backup service reporting has been improved upon in order to correctly report 64527 errors and warnings during the completed backup.

Two-Factor Authentication

BUG DESCRIPTION #

The error message displayed when expired passwords are attempted to be used for Two- 63051 Factor Authentication has been revised to more accurately describe the error and not confuse the problem with server communication issues.

- 23 - N-central 9.5 SP1 Release Notes

UI

BUG DESCRIPTION #

The characters 'asdf' are no longer incorrectly displayed at the top of the AV Defender 69368 Threats Report screen.

The 'Available Scan Types' list no longer incorrectly displays Boot Sectors as 'Booth Sectors' 69295 in the Custom AV Defender screen.

If an N-central Agent is being installed on a managed device but the installation has not yet 68416 been completed, attempting to modify properties of the device no longer incorrectly generates a system error.

The 'Update Now' feature on the asset tab of a device now functions correctly to update 68289 asset information.

Displaying the Reports tab of the AV Defender Behavioral Scan Event service no longer 67965 incorrectly causes system errors.

The 'View All' feature on the License Compliance screen now displays the list of detected 67445 installations correctly.

The PSA Mappings screen now displays properly. 67349

An issue with incorrect device identifiers preventing the UI from accurately displaying the 67156 start time for completed Scheduled Tasks has now been resolved.

Clicking the Remote tab for a device using a Customer Admin account now displays the 67094 Remote Control Settings screen properly.

- 24 - N-central 9.5 SP1 Release Notes

BUG DESCRIPTION #

The 'State' column in the Security Events screen now displays properly at different screen 67081 resolutions.

An issue with PSA contract identifiers that caused modifications to Customers or Sites to 67036 generate system errors has been corrected.

A problem that caused the Remote Control button to incorrectly be displayed for 67003 disconnected devices or devices in downtime has now been resolved.

Scrolling in the Approve/Decline Patches screen no longer causes a screen refresh which 64911 no longer incorrectly causes previously selected items from becoming de-selected.

- 25 - N-central 9.5 SP1 Release Notes

Known Issues

Note: Changes made to the Connectivity service for N-central 9.5 have modified how the service tolerates dropped data packets. If previously modified to be more tolerant of dropped data packets, existing deployments of the Connectivity service may need to be revised if they are overly tolerant of lost packets as these tolerances will be cumulative with the modifications made to the service.

Active Issues

BUG DESCRIPTION #

When exporting a large list of Active Issues items to PDF format at either the System or 62860 Service Organization level, the server may fail. Exporting to CSV format does not cause this problem.

Agents and Probes

BUG DESCRIPTION #

If N-central is upgraded to 9.5 SP1 but Agents and Probes are not upgraded, attempting to 69395 configure a device to use SNMP v3 will result in the SNMP service transitioning to a Failed state with the status message: "205 Unsupported SNMP Version :3". To resolve this issue, upgrade all Agents and Probes immediately after upgrading to N-central 9.5 SP1.

Communication issues may be encountered for N-central Probes installed on Windows servers 67778 that have multiple NICs. For more information, refer to "KBA20020: Configuring A Server With Multiple NICs" in the N-central online help.

Automation Manager

BUG DESCRIPTION #

Running Automation Manager Policies created using Automation Manager 1.6 or earlier may 65712 result in Failed to create a 'EndDate'... errors if the Policies are run on a computer using a different date format. This issue does not affect Policies created using Automation Manager 1.7 or later.

- 26 - N-central 9.5 SP1 Release Notes

Backup Manager

BUG DESCRIPTION #

Monitoring Asigra Backup 12.2 may fail due to issues with connecting to the DS-Client, a 70431 component of the Asigra backup software.

StorageCraft ShadowProtect backup jobs may experience issues when the monitored drive 67211 has multiple volumes resulting in N-central reporting that the 'Job is not active'. This can cause Report Manager to ignore ShadowProtect backup jobs for which the status of one or more volumes could not be obtained.

Custom Services

BUG DESCRIPTION #

Custom services may appear as misconfigured when the system locale of the device is not set 65288 to English. For example, in Portuguese the default decimal in c#/.net is not a period, ".", it is a comma, ",". If you are having this issue, please contact N-able Technologies Technical Support.

Default Properties

BUG DESCRIPTION #

The default license mode option may incorrectly be missing in Administration > n/a Defaults > Discovery Defaults.

- 27 - N-central 9.5 SP1 Release Notes

Patch Management

BUG DESCRIPTION #

If the device with the N-central Probe is using a version of Windows 2003 that does not have 68390 recent updates installed, it may not be able to establish a secure connection which will result in it not being able to download Third Party software updates.

Configuring automatic Third Party software patch approval for devices that use Windows XP® 62277 for their operating system may result in an excessive amount of time being taken before the patches are approved. This is due to an issue with how Microsoft® manages patch approval for Windows XP devices. For more information, refer to http://tech.slashdot.org/story/13/12/16/1959259/exponential-algorithm-in-windows- update-slowing-xp-machines.

Microsoft Security Bulletin MS14-045 announced the withdrawal of four individual Windows 67830 updates due to security issues. This security bulletin applies to:

l Windows RT and Windows RT 8.1

l Windows Server 2012 and Windows Server 2012 R2,

l Windows 8 and Windows 8.1,

l Windows Server 2008 and Windows Server 2008 R2,

l Windows 7,

l Windows Vista, and,

l Windows Server 2003.

The following updates were withdrawn:

l 2982791,

l 2970228,

l 2975719, and,

l 2975331.

If any of these updates have been installed on managed devices, refer to the security bulletin for more information on how to resolve any potential security risks.

Filtering the list of patches to be approved may not function properly based on the text typed 57202 into the Enter search criteria field of the Approve/Decline Patches screen. Typing a whole word (for example, "Defender") may not filter the list properly but typing a partial word (for example, "Defende") will filter the list properly.

It is strongly recommended that your Update Server not be a device that requires n/a uninterrupted disk access (for example, an Exchange server or a web server) as update functionality can be disk-intensive.

- 28 - N-central 9.5 SP1 Release Notes

PSA Integration

BUG DESCRIPTION #

Changing the contact name for a Customer may cause the Customer to no longer be displayed in 70441 the UI.

In some instances, tickets closed in PSAs are not being cleared in N-central. This is likely 65620 because the ticketing recipient profile in N-central has Do not change the Ticket Status selected (in order to manually configure tickets). Then, when the ticket is removed in the PSA, N-central will not be able to update/resolve the ticket's status and new tickets cannot be created for the same issue. Until a solution is available through the UI for this situation, the work around is to set a Return to Normal status and set a non-used status in the 'updatable statuses' section or set the same status as the return to normal one. This will cause N-central to add a note to the ticket on return to normal but will not alter the ticket's status. This will allow the stale ticket check to remove the ticket from the system.

Remote Control

BUG DESCRIPTION #

For Windows Vista and Windows 7, the Remote Control Launcher may not be able to 37303 automatically open a browser window or any other application needed for remote control if the user account does not have Administrator privileges. This will be recorded in the Remote Control Launcher log file (found in %TEMP%/N-ableTechnologies/RemoteControl/logs) as "...is not executable due to Java security".

Remote Desktop connections will fail if the target computer requires Network Level 59122 Authentication and the originating computer cannot support this (for example, if the originating computer uses Windows 2003). Attempts to establish Remote Desktop connections in this situation will display the error message: The remote computer requires Network Level Authentication, which your computer does not support.

DirectConnect remote control connections are not supported for Safari 6.x and later. It is 56392 strongly recommended that Firefox for OS X be used to initiate DirectConnect remote control connections.

If TeamViewer has been installed on a target device using a remote control connection, 63722 subsequent asset discovery of the device may fail to correctly identify the TeamViewer Device ID which can prevent TeamViewer remote control connections from being established.

- 29 - N-central 9.5 SP1 Release Notes

BUG DESCRIPTION #

Propagating TeamViewer as the default remote control type may not work if one of the target n/a devices is using an Essential license.

Scheduled Reports

BUG DESCRIPTION #

Scheduled Reports may only be sent to one recipient if multiple recipients are n/a configured.

Security Manager

BUG DESCRIPTION #

Configuring an AV Defender Custom Scan as part of a Scheduled Task Profile may result in 70445 target files and folders being unable to be selected.

Security scans may incorrectly start outside of the configured schedule during which they 70434 were supposed to start.

Services

BUG DESCRIPTION #

The Veeam Sure Job Monitor service may not be added to a device even after a service 70058 template that is associated with the service is applied to the device.

- 30 - N-central 9.5 SP1 Release Notes

Hardware Requirements

For the minimum hardware requirements for the N-central 9.5 SP1 central server, browse to http://www.n-able.com/N-central_System_Requirements/.

Devices The following are the minimum hardware requirements for devices that will have N-central agents and probes installed on them:

l RAM: 512 MB

l Disk space: 500 MB

l Processor: x86 or x64

Note: N-central agents and probes are not supported on systems using Itanium processors.

Port Access Requirements Access must be permitted to the following ports:

PORT LOCATION

Port N-central Server Managed Device Description Number

Inbound Outbound Inbound Outbound

20 Used for FTP connections, particularly when con- figured for backups.

21 Used for FTP connections, particularly when con- figured for backups.

22 SSH - used for remote control sessions. The fire- wall must be configured to allow access from the Internet to this port on the N-central server.

25 SMTP - used for sending mail.

53 Used for DNS.

- 31 - N-central 9.5 SP1 Release Notes

PORT LOCATION

Port N-central Server Managed Device Description Number

Inbound Outbound Inbound Outbound

80 HTTP - used for communication between the N- central UI and Agents or Probes. The firewall must be configured to allow access from the Inter- net to this port on the N-central server. This port must also be open for outbound traffic if the N- central server is monitoring the HTTP service on a managed device.

Note: Inbound access to port 80 on the N-central server can be blocked provided that all Agents are configured to use HTTPS and the N-central server is accessed over port 443 using HTTPS.

123 Used by the NTPDate service which keeps the server clock synchronized. Normally using UDP (although some servers can use TCP).

135 Used by Agents and Probes for WMI queries to monitor various services.

139 Used by Agents and Probes for WMI queries to monitor various services.

443 HTTPS - used for communication between the N- central UI and Agents or Probes. The firewall must be configured to allow access from the Inter- net to this port on the N-central server. This port must also be open for outbound traffic if the N- central server is monitoring the HTTPS service on a managed device.

445 Used by Agents and Probes for WMI queries to monitor various services.

1433 * * * Outbound on the N-central server, port 1433 is used by Report Manager for data export. On man- aged devices, it is also used by Agents (inbound) and Probes (outbound) to monitor Backup Exec jobs.

* Port access is only required if you have installed the corresponding product. For example, access to port 1433 is only required if you have installed Report Manager or if you are managing Backup Exec jobs.

- 32 - N-central 9.5 SP1 Release Notes

PORT LOCATION

Port N-central Server Managed Device Description Number

Inbound Outbound Inbound Outbound

2000 Used for Remote Support Manager connections locally on the computer. Traffic is mapped to port 2000 locally and transmitted to the N-central server through port 22.

2195 Used to send Mobile Device Management noti- fications to APNS servers at gateway.push-apple.- com.akadns.net.

2196 Used to send Mobile Device Management noti- fications to APNS servers at gateway.push-apple.- com.akadns.net.

8008 By default, Remote Support Manager uses port 8008 on the target device to establish remote con- trol connections.

8014 N-central's Backup Manager requires access to port 8014. This value cannot be modified.

10000 HTTPS - used for access to the N-central Admin- istration Console (NAC). The firewall must be con- figured to allow access from the Internet to this port on the N-central server.

10004 N-central Agents must be able to communicate with a Probe on the network over port 10004 in order for Probe caching of software updates to function properly.

11438 To use DirectConnect or Attended Remote Control for remote control connections, port 11438 on the target device must be accessible for outbound traffic.

15000 For downloading software patches, port 15000 must be accessible for inbound traffic on the Probe device while it must be accessible for out- bound traffic on devices with Agents.

MDM Port Requirements N-central requires the following TCP ports to be open (outbound) in order to send push notifications:

- 33 - N-central 9.5 SP1 Release Notes

l 80

l 443

l 2195

l 2196

Note: Access to ports 2195 and 2196 must be granted to gateway.push-apple.com.akadns.net.

The network to which mobile devices are connected must have the following ports open in order to receive push notifications:

l 443 (TCP)

l 5222 (TCP)

l 5223 (TCP)

l 5228 (TCP and UDP)

Firewall Configuration Requirements Secure Shell access is required for N-able Technologies to sign in and provide you with technical support as well as for remote control functionality.

Firewall configurations should not prevent outbound HTTPS connections from the N-central server or DirectConnect remote control sessions will not function properly.

The N-central server and Windows Probes must be able to resolve the following domain name:

l sis.n-able.com

The N-central server must be able to resolve (and access using port 443) the following domain names:

l update.n-able.com

l feed.n-able.com

l servermetrics.n-able.com

l push.n-able.com

l scep.n-able.com

l licensing.n-able.com

l updatewarranty.com

l apieu.ntrglobal.com

l microsoft.com

For Third Party Patch Management to function properly, your network firewall must be configured to allow access to the following web sites:

- 34 - N-central 9.5 SP1 Release Notes

If a Probe has patch caching enabled When patch caching is enabled, the Probe must have full access to web sites so that it can download installation software. In this configuration, Agents only require access to the Server In The Sky.

Device Type Vendor - Web Site URL

Device with l Server In The Sky (SIS) - http://sis.n-able.com

Probe l Adobe Acrobat - http://ardownload.adobe.com

l Adobe Reader - ftp://ftp.adobe.com/

l Adobe Air - http://airdownload.adobe.com/

l Apple Products - https://secure-appldnld.apple.- com

l Flash - http://download.macromedia.com/

l Foxit - http://cdn01.foxitsoftware.com/

l Google Products - https://dl.google.com

l Java - http://javadl.sun.com/

l Mozilla Products - https://download-installer- .cdn.mozilla.net

l Notepad++ - http://download.tuxfamily.org/

l Opera - http://get.geo.opera.com/

l Shockwave - http://www.adobe.com/

l Skype - http://download.skype.com/

l WinRAR - http://www.rarlab.com/

l WinZip - http://download.winzip.com/

l VLC - http://download.videolan.org/

Device with l Server In The Sky (SIS) - http://sis.n-able.com Agent

- 35 - N-central 9.5 SP1 Release Notes

If no Probes have patch caching enabled

Device Type Vendor - Web Site URL

Device with l Server In The Sky (SIS) - http://sis.n-able.com

Agent l Adobe Acrobat - http://ardownload.adobe.com

l Adobe Reader - ftp://ftp.adobe.com/

l Adobe Air - http://airdownload.adobe.com/

l Apple Products - https://secure-appldnld.apple.- com

l Flash - http://download.macromedia.com/

l Foxit - http://cdn01.foxitsoftware.com/

l Google Products - https://dl.google.com

l Java - http://javadl.sun.com/

l Mozilla Products - https://download-installer- .cdn.mozilla.net

l Notepad++ - http://download.tuxfamily.org/

l Opera - http://get.geo.opera.com/

l Shockwave - http://www.adobe.com/

l Skype - http://download.skype.com/

l WinRAR - http://www.rarlab.com/

l WinZip - http://download.winzip.com/

l VLC - http://download.videolan.org/

Security Manager - AV Defender Hardware Requirements Devices on which the AV Defender software is to be installed must have a minimum of 1 GB of free disk space on the drive where the root directory (%programfiles%) is located.

Devices that are to be configured as AV Defender Update Servers must have a minimum of an additional 6 GB (for a total of 7 GB) of free disk space on the drive where the root directory (%programfiles%) is located.

For more information, refer to "AV Defender" in the N-central online help.

- 36 - N-central 9.5 SP1 Release Notes

Software Requirements

Supported Platforms and Browsers N-central is supported on the following browsers:

l Internet Explorer®, versions 9.x and later

l Mozilla Firefox®, versions 4.0 and later

l Google Chrome®, versions 27.x and later

Notes 1. N-central is not supported on Internet Explorer in Compatibility View mode.

2. Attended Remote Control and DirectConnect remote control connections are not supported on 64-bit browsers.

Browser All testing and software development related to Internet Explorer 9 will be Support discontinued with the next major release of N-central. Some N-central features may Notice continue to function with Internet Explorer 9 but that version of the browser will no longer be officially supported. Users may experience issues with Internet Explorer 9 and certain elements of N-central after support is discontinued.

Agents and Probes N-central 9.5 SP1 supports agents and probes from N-central 8.2 and later.

Note: Upgrading N-central Agents and Probes from versions earlier than N-central 7.1 will be attempted but may require manual intervention or re-installation as they are no longer supported. We strongly recommend that you upgrade your Agents and Probes with every new release to avoid any potential issues.

Microsoft .NET Framework

If it is not already configured, Microsoft .NET Framework 4.0.x will be automatically installed on those devices that can be upgraded to N-central 9.5 SP1.

Versions of Windows Agents earlier than N-central 9.1 will not function properly on devices that only have Microsoft .NET Framework 4.0.x. They will function properly if the device has both Microsoft .NET Framework 4.0.x and Microsoft .NET Framework 2.0.50727.

Versions of Windows Agents earlier than N-central 9.1 will function properly on devices using the following operating systems:

l Microsoft Windows 2000 Advanced Server

l Microsoft Windows 2000 Data Center

l Microsoft Windows 2000 Professional

- 37 - N-central 9.5 SP1 Release Notes

l Microsoft Windows 2000 Server

l Microsoft Windows 2000 Server Appliance

Versions of Windows Agents from N-central 9.1 and later will not function on devices using the operating systems listed above.

If Remote Support Manager (RSM) is enabled on a device, it must have both Microsoft .NET Framework 2.0.50727 and Microsoft .NET Framework 4.0.x.

Agent Agent .NET Framework on device Probe (no RSM) (+RSM)

only Microsoft .NET Framework 2.0.50727

only Microsoft .NET Framework 4.0.x

both Microsoft .NET Framework 2.0.50727 and Microsoft .NET Framework 4.0.x

Note: For Windows 2003 devices, installing .NET Framework 4.0.x requires the Windows Imaging Component (for more information, refer to http://msdn.microsoft.com/en- us/library/8z6watww.aspx).

Supported Mobile Device Operating Systems N-central's Mobile Device Management supports the following:

l iOS 6.1.x and later

l Android 2.2.x and later

For more information, refer to "Mobile Device Management" in the N-central online help.

Remote Control Remote control connections require the following software on the computers that initiate remote control connections:

l Java 6 Update 20 or greater

Report Manager If using Report Manager, you must upgrade to Report Manager 4.3 Hotfix 1 (or later) after upgrading to N-central 9.5 SP1.

- 38 - N-central 9.5 SP1 Release Notes

Upgrading to This Release

Upgrade Paths To upgrade N-central, your N-central server must be running one of the versions listed in the table below:

Version and build to upgrade from...

Version to upgrade to... N-central 9.5 Gen- N-central 9.5 SP1 N-central 9.4.x eral Release

N-central 9.5 SP1 General 9.5 SP1 Beta 9.5 GA (9.5.0.353) 9.4 Hotfix 5 Release (9.5.1.243) (9.5.1.233) and later and later (9.4.0.678) and later

N-central 9.5 SP1 Hotfix 1 9.5 SP1 Beta 9.5 GA (9.5.0.353) n/a (9.5.1.353) (9.5.1.233) and later and later

N-central 9.5 SP1 Hotfix 2 9.5 SP1 Beta 9.5 GA (9.5.0.353) 9.4 Hotfix 5 (9.5.1.450) (9.5.1.233) and later and later (9.4.0.678) and later

Advisory Notices Warning! If you are currently monitoring StorageCraft backups using the custom service provided on the N-able Resource Center (referred to as StorageCraft ShadowProtect - Standalone), you may experience lost data in your Report Manager Executive Summary and Data Protection reports after upgrading to N- central 9.5 from an N-central release earlier than Version 9.4. This is due to the transition in monitoring between the custom service and the integrated version of the service.

To avoid any potential loss in data, perform the following:

1. Before upgrading N-central:

a. Ensure that you are using the most current version of the monitoring service and script found on the N-able Resource Center (under Com- munity > Custom Services > StorageCraft ShadowProtect - Standalone).

b. Upgrade Report Manager to Report Manager 4.2 Hotfix 2.

c. Ensure that ETL is scheduled in Report Manager for every hour (for more information, refer to "ETL Configuration" in the Report Manager Administration Console online help).

- 39 - N-central 9.5 SP1 Release Notes

Warning! d. Ensure that data exports are taking place normally.

e. Configure the automatic update settings for your Agents to Never (for more information, refer to "Update Monitoring Software" in the N-central online help).

2. Upgrade your N-central server.

3. Configure your managed devices in N-central such that there is a period of time when no backups will take place. This time period must be at least two (2) hours in duration and can be referred to as a "No Backup window".

4. Wait one (1) hour to ensure that all data has been exported.

5. Select several devices.

6. For the selected devices, disable all StorageCraft ShadowProtect monitoring services using the Active Issues view at the beginning of the "No Backup" Maintenance Window (for more information, refer to "Active Issues View" in the N-central online help).

7. For the selected devices, upgrade your Agents (for more information, refer to "Update Monitoring Software" in the N-central online help).

8. Confirm that the Agents have been upgraded and allow the new monitoring service to be applied.

9. Once this is confirmed, delete the superseded service that has been disabled.

Note: If you are concerned with historical data, delay this step for as long as required.

10. If any Agent has not been upgraded and the new service was not added before the end of the "No Backup" Maintenance Window, you will need to re- enable the monitoring service and cancel the Agent upgrade in order to avoid any potential data loss.

11. If you have any questions or concerns about this procedure, please contact N-able Technologies Technical Support at 1-877-655-4689, by email at sup- [email protected] , or by accessing the self service portal at http://support.n- able.com.

- 40 - N-central 9.5 SP1 Release Notes

Review the following checklist before proceeding with upgrading to this release.

Reviewed Category Notice

Agents Scheduled Tasks may expire if the Agent on an associated device is being upgraded when the task is scheduled to be completed. Agent upgrades are normally short in duration but may be delayed if a re-start of the device is pending.

Agents Upgrading Agents from 9.0 to 9.1 or later may fail if Microsoft .NET Framework 4.0 cannot be installed on the target device. .NET Framework 4.0 may be prevented from being installed on the device if the Windows Imaging Component has not been installed. For more information, refer to http://www.microsoft.com/en-us/download/details.aspx?id=32. It is strongly recommended that target devices have the latest Windows Service Packs and critical updates installed before upgrading Agents in order to avoid this issue.

Security For those upgrading from N-central 9.2 or earlier, N-central 9.3 introduced Manager - a new integrated antivirus solution, Security Manager - AV Defender, Endpoint based on the award winning Bitdefender engine. Existing Security Security Manager - Endpoint Security licenses, based on the Panda antivirus engine, will continue to function until December 31, 2014. However, N- central 9.5 SP1 will not allow new deployments, or re-deployments, of Security Manager - Endpoint Security. This means that once you have upgraded to N-central 9.3 or later, any new integrated antivirus deployments, or re-deployment, will only deploy Security Manager - AV Defender. If you have deployed Security Manager - Endpoint Security and require the ability to deploy Security Manager - Endpoint Security, as opposed to Security Manager - AV Defender, please do not upgrade to N-central 9.3 or later and contact N-able Technologies Technical Support to discuss migration planning.

You can upgrade to N-central 9.5 SP1 through the N-central Administrator Console (NAC) under Setup > Central Server > Version Management. This allows you to upgrade either by using the system upgrade file that has been automatically downloaded by the N-central server or by downloading the appropriate .nsp file from the N-able Resource Center at https://nrc.n-able.com/ under Support > Software Downloads.

Upgrade Procedure You must perform the following to upgrade to N-central 9.5 SP1:

Step One: Backing Up the N-central Server on page 42

- 41 - N-central 9.5 SP1 Release Notes

Step Two: Installing the N-central 9.5 SP1 Upgrade on page 45

Step Three: Post-installation Steps on page 46

Step One: Backing Up the N-central Server Note: If N-central has been installed as a guest on an ESX or Hyper-V server, it is strongly recommended that you record a snapshot of the guest before upgrading the N-central software. In the event that the upgrade fails, this will allow you to restore the guest back to the snapshot image.

1. In the navigation pane, click Administration > System Backup and Restore > Configure Backups.

2. In the Configure Backups screen, configure the following properties:

Backup Details

Backup File Name The identifying name of the backup file.

Note: The yyyymmdd-HHMMSS.tgz suffix is automatically appended to the name.

Include Historical Select this check box to include historical data in the backup. This data Data includes statistics on device statuses and system events and is the bulk of the data used for reports.

Note: Do not select this checkbox if you are only backing up the configuration or if you want to reduce the size of the backup file.

Include Software Select this check box to include the software and script repository data in the And Script backup. Repository Data Note: You must select this if you intend to restore the software and script repositories.

Warning! This step may considerably affect the size of the backup, depending on the combined size of the stored scripts and software packages in the repositories.

Backup Schedule

- 42 - N-central 9.5 SP1 Release Notes

Type Select the type of schedule for regularly performing the database backup from one of the following options:

l Off

l Daily

l Weekly

l Monthly

Start Time The time at which the backup will be started.

Days of the The weekdays on which the backup will be performed. Week Note: This option is only available for Weekly backups.

Days of the The specific dates on which the backup will be performed. Month Note: This option is only available for Monthly backups.

Backup Destination FTP Server

Upload copy of Backup to FTP Enables the uploading of copies of the backup file to an FTP Server. server.

Keep Previous Backup Retains existing backup files stored on the FTP server. Archive

Server Address The FQDN or IP address of the FTP server.

Username The name of the FTP server account.

Password The security password of the FTP server account.

Directory The path to the folder on the FTP server in which the backup file will be stored.

Example: /home/test/backup/

- 43 - N-central 9.5 SP1 Release Notes

Notifications

Notify On Select Success to send a notification upon the success of the backup. Select Failure to send a notification upon the failure of the backup.

Sender The email address from which the notification will be sent. Email Address

Recipient The email address to which the notification will be sent. Email Address

3. Click Save and Run Backup.

During the backup, N-central creates a backup file and a backup digest file. The backup file contains all of the information needed to restore the system. The SHA1 file contains a SHA1 checksum of the backup file and verifies that the backup file is not corrupted. For example, it considers the backup file corrupt if any changes have been made to the backup file.

4. Wait for the system to send you a notification informing you of the backup success or failure.

Note: If the backup failed and the error cannot be corrected, contact N-able Technologies Technical Support.

If the backup succeeded and you did not configure it to be uploaded to an FTP server, manually download the backup image from the N-central server to a safe location by performing the following:

a. In the navigation pane, click Administration > System Backup and Restore > Download Backups.

b. Click Download Backup beside the name of the backup file that you would like to download.

c. When prompted by the browser, save the backup file to the location you would like to use for storing backup files.

d. If required, click Download Digest beside the name of the backup file for which you would like to download the digest file.

e. When prompted by the browser, save the digest file to the location you would like to use for storing backup files.

Note: The downloaded files can now be used to restore the database.

- 44 - N-central 9.5 SP1 Release Notes

Step Two: Installing the N-central 9.5 SP1 Upgrade You can upgrade to N-central 9.5 SP1 by installing the upgrade file that has been downloaded to your N- central server.

Warning! Do not reboot the N-central server during the upgrade process even if it appears unresponsive.

Usually the average N-central server upgrade takes approximately 30 minutes but the upgrade process can take several hours depending on the size of your database. If five hours have passed after the upgrade and you have not received a notification, contact N-able Technologies for assistance.

If you are unsure of the status of the upgrade, please call N-able Technologies Technical Support, and they will be able to advise you of the current upgrade status.

To install the downloaded N-central 9.5 SP1 upgrade

1. On the Administrator Console menu bar, select Setup.

2. Under the Central Server heading in the Setup screen, click Version Management.

3. In the Version Management screen, perform one of the following:

Automatic upgrade Manual upgrade

a. Select Install upgrade a. Select Install upgrade remotely. from local repository. b. Specify the Location of the system upgrade file or click b. Select the upgrade File. Browse to navigate to the file.

Example: 9.5 SP1.0.xxx

4. Type an e-mail address in the Notify this email address when complete field.

5. Click Install.

6. In the confirmation screen, click Yes.

The server will restart. After the installation is completed, the version and upgrade information will be updated.

- 45 - N-central 9.5 SP1 Release Notes

Step Three: Post-installation Steps After you have installed N-central 9.5 SP1, you must perform the following post-installation steps.

Note: Our recommended best practice is to upgrade probes, agents and related software on a customer-by-customer basis. Ensure that each customer is completely upgraded before moving on to the next customer. If you are monitoring your internal network, this should be the first "customer" attempted.

Post-installation Checklist

Check items as they are completed

Verify the version of N-central by signing into the UI and clicking Help > About on the menu bar. The Associated Upgrades displayed must read Applied-update-9.5.1.xxx-b9_5_1_xxx, where xxx is a number.

Verify the Network Settings and Default Settings in the NAC.

Verify that the user accounts exist and are accessible.

Verify that the customer profiles are complete and accurate.

Verify that the devices are present.

Verify that the services for each device are reporting correctly.

Verify that all of the notification profiles are present.

Verify that the reports generate and display the accurate historical data.

- 46 - N-central 9.5 SP1 Release Notes

Check items as they are completed

At the Service Organization level in the N-central UI, perform the following to automatically upgrade all of the Probes and Agents installed on your customers' remote computers.

1. In the navigation pane, click Administration > Defaults > Appliance Settings. 2. Select the Upgrade Windows Probes option as either Never (the Probe software will not ever be upgraded) or Always (the Probe software is always upgraded). 3. Select Propagate to distribute this configuration setting to existing devices. 4. Select Reboot device if necessary to automatically restart devices after the Probe soft- ware has been upgraded. 5. Select the Upgrade Agents option as either Never (the Agent software will not ever be upgraded) or Always (the Agent software is always upgraded). 6. Select Propagate to distribute this configuration setting to existing devices. 7. Select Reboot device if necessary to automatically restart devices after the Agent soft- ware has been upgraded. 8. Click Save.

Note: You can perform the above procedure for specific Customers/Sites by navigating to the Customer/Site level first. You will have to repeat the procedure for each Customer/Site that you want to automatically upgrade their Windows Probes and Windows Agents.

Once the upgrade procedure has been completed, generate an Agent/Probe Overview report by clicking Reports >Administrative > Agent/Probe Overview in the navigation pane. This will allow you to verify that all probes have been updated.

Note: After upgrading an Agent that monitors the Asigra Backup service or the XiloCore Backup service, you will need to stop the Windows Agent services, place the Asigra .DLL files to the Agent's bin directory and re-start the Windows Agent services.

- 47 - N-central 9.5 SP1 Release Notes

Check items as they are completed

Upgrade your monitoring software automatically for specific Service Organizations, Customers or Sites:

Upgrade your monitoring software automatically for specific Customers or Sites:

Upgrade your monitoring software automatically for specific devices:

1. In the navigation pane, click All Devices.

2. Select the Service Organizations, Customers or Sites, or devices for which you would like to upgrade monitoring software.

3. Click Upgrade Monitoring Software.

4. In the Upgrade Monitoring Software dialog box, select Now for the monitoring software you want to upgrade from the following:

l Upgrade Agent

l Upgrade Remote Support Manager

l Upgrade Backup Manager

l Upgrade Endpoint Security

5. Click Save.

Note: Upgrading Endpoint Security on devices will cause them to reboot twice: once after the existing software is removed, and again after the new software has been installed.

Once the upgrade procedure has been completed, generate reports by clicking the following:

l Reports >Administrative > Remote Support Manager

l Reports >Status > Endpoint Security Status

This will allow you to verify that all devices have been updated.

You must upgrade both your N-central server and your Windows Agents to a minimum of Version 9.2 or later in order to perform Patch Management through N-central. The Patch Status, CPU, Memory and Process services will report a Misconfigured status if you have not upgraded.

As Windows, Mac and Linux agents are automatically updated, the Patch Status, CPU, Memory and Process services will automatically transition from a Misconfigured state to a Normal/Warning/Failed state.

After you have upgraded to N-central 9.2 or later, please review any Patch Management Profiles (available under Configuration > Patch Management > Profiles) that you had previously configured, as there are new settings in those Profiles that must be configured before Patch Management will function properly.

If you absolutely need to approve or decline patches but the devices that you wish to target have not yet upgraded their Agents to Version 9.2 or later, please sign in directly to the appropriate WSUS server and approve or decline patches from that application.

- 48 - N-central 9.5 SP1 Release Notes

Rebuilding or Migrating Your N-central Server

There may be circumstances in which you need to rebuild or migrate your N-central server including:

l your N-central server is not functioning properly or starting successfully,

l an upgrade has failed but you can still log in to N-central, or,

l you are migrating an existing N-central server to another computer (for example, if disks are full or new hardware has been procured).

Before attempting to rebuild or migrate your N-central server, it is strongly recommended that you verify that the server meets the requirements of the version that you are installing. For more information, refer to the "N-central System Requirements" which are available on the N-able Resource Center at https://nrc.n-able.com/.

The following procedures describe the best way to rebuild or migrate your N-central server based on specific situations.

Scenario A: Server is not Functioning Properly or Starting Successfully

1. Verify the build (version) of your N-central server. N-able Technologies Technical Support can confirm the version of N-central that last communicated with N-able Technologies if your server is not functioning properly or can not successfully be re-started.

2. Locate the last valid backup of your N-central server. Your N-central server software will automatically record backups but these will be saved to the same local hard drive as the server software itself which may make retrieval more difficult. Some options that may be used to retrieve a backup in this situation are:

a. You had previously downloaded a recent backup file in .TAR or .SHA1 format.

b. You had configured N-central to automatically send backups to an FTP server from which they can be obtained.

c. You have a snapshot of your N-central server recorded by a virtualized host (Hyper- V or VMWare). If this is the case, the following steps will not apply as you can restore your server using the snapshot.

Note: It is strongly recommended that snapshots of the N-central server should not be taken on a short-term schedule as this can affect system performance (and N-central records its own backups).

d. If the server can be partially re-started, your N-able Technologies Technical Support representative may be able to retrieve the recent backup by remotely accessing port 22 on your server.

3. Install the version of N-central that you were previously running.

- 49 - N-central 9.5 SP1 Release Notes

For your convenience, you can quickly re-install N-central to the exact version that you were using previously by downloading the ISO for that build (in an ISO file, not NSP). This allows you to install the ISO and then restore your backup. The following is an example of an ISO file available for download from http://nrc.n-able.com:

File: N-central 9.5 HF2 (9.5.0.574) ISO

MD5: 4f0ac4baab9146cb0caeb1b63127cc35

Size: 695 MB

Note: This image should only be used for new installations of N-central. This image is not intended for upgrading an existing N-central server.

4. Restore the backup that you located in Step #2 above. For more information, refer to "Sys- tem Restore" in the N-central online help.

5. When the system restore is completed, please contact N-able Technologies to have your N-central server activated. For more information refer to "Activating N-central" in the N- central Installation Guide.

Scenario B: An Upgrade has Failed but You Can Still Log In

1. Verify the build (version) of your N-central server. In the navigation pane, click Help > Version Information to display your N-central current version.

2. Locate the last valid backup of your N-central server. Your N-central server software will automatically record backups but these will be saved to the same local hard drive as the server software itself which may make retrieval more difficult. Some options that may be used to retrieve a backup in this situation are:

a. Download the most recent backup that was made prior to the upgrade attempt.

i. In the navigation pane, click Administration > System Backup and Restore > Download Backups.

ii. Click Download Backup beside the name of the backup file that you would like to download.

iii. When prompted by the browser, save the backup file to the location you would like to use for storing backup files.

iv. Click Download Digest beside the name of the backup file.

v. When prompted by the browser, save the digest file to the location you would like to use for storing backup files.

- 50 - N-central 9.5 SP1 Release Notes

b. You had configured N-central to automatically send backups to an FTP server from which they can be obtained.

c. You have a snapshot of your N-central server recorded by a virtualized host (Hyper- V or VMWare). If this is the case, the following steps will not apply as you can restore your server using the snapshot.

Note: It is strongly recommended that snapshots of the N-central server should not be taken on a short-term schedule as this can affect system performance (and N-central records its own backups).

3. Install the version of N-central that you were previously running.

For your convenience, you can quickly re-install N-central to the exact version that you were using previously by downloading the ISO for that build (in an ISO file, not NSP). This allows you to install the ISO and then restore your backup. The following is an example of an ISO file available for download from http://nrc.n-able.com:

File:N-central 9.5 HF2 (9.5.0.574) ISO

MD5:4f0ac4baab9146cb0caeb1b63127cc35

Size:695 MB

Note: This image should only be used for new installations of N-central. This image is not intended for upgrading an existing N-central server.

4. Restore the backup that you located in Step #2 above. For more information, refer to "Sys- tem Restore" in the N-central online help.

5. When the system restore is completed, please contact N-able Technologies to have your N-central server activated. For more information refer to "Activating N-central" in the N- central Installation Guide.

Scenario C: Migrating an Existing N-central Server to Another Computer

1. Verify the build (version) of your N-central server. In the navigation pane, click Help > Version Information to display your N-central current version.

2. Locate the last valid backup of your N-central server. Your N-central server software will automatically record backups but these will be saved to the same local hard drive as the server software itself which may make retrieval more difficult. Some options that may be used to retrieve a backup in this situation are:

- 51 - N-central 9.5 SP1 Release Notes

a. Create a new backup in order to minimize data loss.

i. In the navigation pane, click Administration > System Backup and Restore > Configure Backups.

ii. Click Save and Run Backup.

Note: Backing up the N-central database will typically take several minutes to an hour.

b. Download the most recent backup.

i. In the navigation pane, click Administration > System Backup and Restore > Download Backups.

ii. Click Download Backup beside the name of the backup file that you would like to download.

iii. When prompted by the browser, save the backup file to the location you would like to use for storing backup files.

iv. Click Download Digest beside the name of the backup file.

v. When prompted by the browser, save the digest file to the location you would like to use for storing backup files.

c. You had configured N-central to automatically send backups to an FTP server from which they can be obtained.

d. You have a snapshot of your N-central server recorded by a virtualized host (Hyper- V or VMWare). If this is the case, the following steps will not apply as you can restore your server using the snapshot.

Note: It is strongly recommended that snapshots of the N-central server should not be taken on a short-term schedule as this can affect system performance (and N-central records its own backups).

3. Install the version of N-central that you were previously running.

For your convenience, you can quickly re-install N-central to the exact version that you were using previously by downloading the ISO for that build (in an ISO file, not NSP). This allows you to install the ISO and then restore your backup. The following is an example of an ISO file available for download from http://nrc.n-able.com:

File:N-central 9.5 HF2 (9.5.0.574) ISO

MD5:4f0ac4baab9146cb0caeb1b63127cc35

- 52 - N-central 9.5 SP1 Release Notes

Size:695 MB

Note: This image should only be used for new installations of N-central. This image is not intended for upgrading an existing N-central server.

4. Restore the backup that you located in Step #2 above. For more information, refer to "Sys- tem Restore" in the N-central online help.

5. When the system restore is completed, please contact N-able Technologies to have your N-central server activated. For more information refer to "Activating N-central" in the N- central Installation Guide.

For assistance with this procedure, please contact the N-able Technologies Technical Support team at 1- 866-302-4689 (US/CAN), +800 6225 3000 (International), or (613) 592-6676 (Local). You can also create a support case on the N-able Resource Center at https://nrc.n-able.com/.

- 53 - N-central 9.5 SP1 Release Notes

Platform Support

Supported Operating Systems for Agents

Microsoft Windows (WindowsAgentSetup.exe) Microsoft .NET Framework

If it is not already configured, Microsoft .NET Framework 4.0.x will be automatically installed on those devices that can be upgraded to N-central 9.5 SP1.

Versions of Windows Agents earlier than N-central 9.1 will not function properly on devices that only have Microsoft .NET Framework 4.0.x. They will function properly if the device has both Microsoft .NET Framework 4.0.x and Microsoft .NET Framework 2.0.50727.

Versions of Windows Agents earlier than N-central 9.1 will function properly on devices using the following operating systems:

l Microsoft Windows 2000 Advanced Server

l Microsoft Windows 2000 Data Center

l Microsoft Windows 2000 Professional

l Microsoft Windows 2000 Server

l Microsoft Windows 2000 Server Appliance

Versions of Windows Agents from N-central 9.1 and later will not function on devices using the operating systems listed above.

If Remote Support Manager (RSM) is enabled on a device, it must have both Microsoft .NET Framework 2.0.50727 and Microsoft .NET Framework 4.0.x.

Windows Server® l Microsoft Windows Server 2012 R2 Datacenter

2012 l Microsoft Windows Server 2012 R2 Datacenter 64-bit Edition

l Microsoft Windows Server 2012 R2 Essentials

l Microsoft Windows Server 2012 R2 Essentials 64-bit Edition

l Microsoft Windows Server 2012 R2 Foundation

l Microsoft Windows Server 2012 R2 Foundation 64-bit Edition

l Microsoft Windows Server 2012 R2 Standard

l Microsoft Windows Server 2012 R2 Standard 64-bit Edition

l Microsoft Windows Server 2012 Datacenter 64-bit Edition

l Microsoft Windows Server 2012 Essentials 64-bit Edition

l Microsoft Windows Server 2012 Foundation 64-bit Edition

l Microsoft Windows Server 2012 Standard 64-bit Edition

l Microsoft Windows Storage Server 2012 Enterprise 64-bit Edition

l Microsoft Windows Storage Server 2012 Express 64-bit Edition

l Microsoft Windows Storage Server 2012 Standard 64-bit Edition

l Microsoft Windows Storage Server 2012 Workgroup 64-bit Edition

- 54 - N-central 9.5 SP1 Release Notes

Windows Server l Microsoft Windows 2008

2008 l Microsoft Windows 2008 Datacenter Server

l Microsoft Windows 2008 Datacenter Server without Hyper-V

l Microsoft Windows 2008 Datacenter Server without Hyper-V 64-bit Edition

l Microsoft Windows 2008 Datacenter Server 64-bit Edition

l Microsoft Windows 2008 Enterprise Server

l Microsoft Windows 2008 Enterprise Server without Hyper-V

l Microsoft Windows 2008 Enterprise Server without Hyper-V 64-bit Edition

l Microsoft Windows 2008 Enterprise Server 64-bit Edition

l Microsoft Windows 2008 Essential Business Server

l Microsoft Windows 2008 Essential Business Server 64-bit Edition

l Microsoft Windows 2008 Foundation Server

l Microsoft Windows 2008 HPC Server

l Microsoft Windows 2008 R2 Datacenter Server

l Microsoft Windows 2008 R2 Enterprise Server

l Microsoft Windows 2008 R2 Foundation Server

l Microsoft Windows 2008 R2 Standard Server

l Microsoft Windows 2008 R2 Web Server

l Microsoft Windows 2008 Small Business Server

l Microsoft Windows 2008 Small Business Server 64-bit Edition

l Microsoft Windows 2008 Standard Server

l Microsoft Windows 2008 Standard Server without Hyper-V

l Microsoft Windows 2008 Standard Server without Hyper-V 64-bit Edition

l Microsoft Windows 2008 Standard Server 64-bit Edition

l Microsoft Windows 2008 Web Server

l Microsoft Windows 2008 Web Server 64-bit Edition

There are a number of requirements in order to install Windows Agents on a server using Windows Server 2008 R2 Server Core 64-bit.

l The operating system must be Windows Server 2008 R2 Server Core 64-bit Service Pack 1 or later.

l .NET Framework 4 for Server Core (64-bit) must be installed.

l .NET Framework 2 must be enabled using the command: start /w ocsetup NetFx2-ServerCore-WOW64

Windows Server l Microsoft Windows Storage Server 2003 R2

2003 l Microsoft Windows Server 2003

l Microsoft Windows Server 2003 for Small Business Server

l Microsoft Windows Server 2003 for Small Business Server 64-bit Edition

l Microsoft Windows Server 2003 SP1

l Microsoft Windows Server 2003 64-bit Edition

l Microsoft Windows Server 2003 Web Edition

Windows Server l Microsoft Windows 2000 Advanced Server

2000 l Microsoft Windows 2000 Professional

l Microsoft Windows 2000 Server

- 55 - N-central 9.5 SP1 Release Notes

Hyper-V l Microsoft Windows Hyper-V Server 2008

l Microsoft Windows Hyper-V Server 2008 R2

l Microsoft Windows Hyper-V Server 2012 64-bit Edition

Windows 8 l Microsoft Windows 8.1 Enterprise

l Microsoft Windows 8.1 Enterprise 64-bit Edition

l Microsoft Windows 8.1 Professional

l Microsoft Windows 8.1 Professional 64-bit Edition

l Microsoft Windows 8 Enterprise

l Microsoft Windows 8 Enterprise 64-bit Edition

l Microsoft Windows 8 Professional

l Microsoft Windows 8 Professional 64-bit Edition

l Microsoft Windows 8 64-bit Edition

Windows 7 l Microsoft Windows 7 Enterprise

l Microsoft Windows 7 Enterprise 64-bit Edition

l Microsoft Windows 7 Home Basic

l Microsoft Windows 7 Home Premium

l Microsoft Windows 7 Professional

l Microsoft Windows 7 Professional 64-bit Edition

l Microsoft Windows 7 Ultimate

l Microsoft Windows 7 Ultimate 64-bit Edition

Windows Vista® l Microsoft Windows Vista Business

l Microsoft Windows Vista Business 64-bit Edition

l Microsoft Windows Vista Enterprise

l Microsoft Windows Vista Enterprise 64-bit Edition

l Microsoft Windows Vista Home

l Microsoft Windows Vista Home 64-bit Edition

l Microsoft Windows Vista Ultimate

l Microsoft Windows Vista Ultimate 64-bit Edition

Windows XP l Microsoft Windows XP

l Microsoft Windows XP Embedded

l Microsoft Windows XP Home

l Microsoft Windows XP Professional

l Microsoft Windows XP Professional 64-bit Edition

l Microsoft Windows XP Tablet PC Edition

Other Windows ver- l Microsoft Windows NT 4.x 32-bit

sions l Microsoft Windows NT Server

l Microsoft Windows Embedded Standard

l Microsoft Windows Home Server 2011

l Microsoft Windows Small Business Server 2011

l Microsoft Windows Storage Server 2003 R2

l Microsoft Windows Unified Data Storage Server 2003

- 56 - N-central 9.5 SP1 Release Notes

Note: Windows Agents must be installed manually on devices that use Microsoft Windows 7 Home due to issues with joining the devices to a domain.

Red Hat® Enterprise/CentOS Linux

nagent-rhel5.1_64.tar.gz l CentOS 5 64-bit Edition

l CentOS 6 64-bit Edition

l RedHat Enterprise Linux 5 64-bit Edition

l RedHat Enterprise Linux 6 64-bit Edition

nagent-rhel5.1.tar.gz l CentOS 5 32-bit Edition

l CentOS 6 32-bit Edition

l RedHat Enterprise Linux 5 32-bit Edition

l RedHat Enterprise Linux 6 32-bit Edition

Mac® OS X® Agent

OSXAgent.tar.gz l Apple Mac OS X 10.9 Server

l Apple Mac OS X 10.9

l Apple Mac OS X 10.8 Server

l Apple Mac OS X 10.8

l Apple Mac OS X 10.7 Server

l Apple Mac OS X 10.7

l Apple Mac OS X 10.6 Server

l Apple Mac OS X 10.6

- 57 - N-central 9.5 SP1 Release Notes

Supported Operating Systems for Endpoint Security

Supported Platforms Endpoint Security software can only be installed on devices that use the following supported operating systems:

l Windows NT 4.0 SP6 Terminal Server, Domain Controller, Small Business Server, and Cluster

l Windows 2000 Professional, Terminal Server, Domain Controller, Stand Alone, Cluster and Small Business Server

l Windows 2003 Server SP1 and SP2 Terminal Server, Enterprise Edition, Small Business Server, Unified Data Storage Server, Cluster, and Web Edition (both 32-bit and 64-bit versions)

l Windows XP Tablet PC Edition

l Windows XP Professional SP3 (32-bit version)

l Windows XP (64-bit version)

l Windows Vista Home, Business, Enterprise and Ultimate SP1 (both 32-bit and 64-bit versions)

l Windows 2008 Standard Server and Small Business Server (both 32-bit and 64-bit versions)

l Windows 2008 Standard Server, Enterprise Server, Datacenter Server, Web Server, and Found- ation Server R2

l Windows 7 Professional, Enterprise, and Ultimate (both 32-bit and 64-bit versions)

l Windows 7 Home Basic and Home Premium

Note: The TruPrevent module is only supported with 32-bit versions of Windows operating systems.

Non-Supported Platforms Endpoint Security software cannot be installed on devices that use the following operating systems:

l Windows 95

l Windows 98

l Windows ME

l Windows NT 3.x, 4.x Alpha, 4.x x86, and Server

l Windows 2000 Data Centre, Server Appliance, and Advanced Server

l Windows XP Embedded and Home Edition

- 58 - N-central 9.5 SP1 Release Notes

Supported Operating Systems for AV Defender

Supported Platforms AV Defender software can only be installed on devices that use the following supported operating systems:

Workstation Operating Systems

l Microsoft Windows XP SP3

l Microsoft Windows Vista SP1

l Microsoft Windows 7

l Microsoft Windows 8

l Microsoft Windows 8.1

Tablet And Embedded Operating Systems

l Windows XP Tablet PC Edition

l Windows XP Embedded SP2

l Windows Embedded Standard 2009

l Windows Embedded POSReady 2009

l Windows Embedded Enterprise 7

l Windows Embedded POSReady 7

l Windows Embedded Standard 7

Server Operating Systems

l Microsoft Windows 2003 Server SP1

l Microsoft Windows Server 2003 for Small Business Server

l Microsoft Windows Storage Server 2003 R2

l Microsoft Windows Server 2003 SP1

l Microsoft Windows 2008

l Microsoft Windows 2008 Server

l Microsoft Windows 2008 R2

l Microsoft Windows Small Business Server 2011

l Microsoft Windows Home Server 2011

l Microsoft Windows 2012 Server

l Microsoft Windows 2012 Server R2

Note: For Microsoft Windows XP Embedded SP2 and Microsoft Windows Embedded Standard 7, TCP/IP, Filter Manager, and Windows Installer must all be enabled.

The Behavioral Analysis module is not supported on devices using the 64-bit edition of the Windows XP operating system. The module is supported on devices using:

l 32-bit edition of Windows XP

l 32-bit and 64-bit editions of Windows Vista

l 32-bit and 64-bit editions of Windows 7

l 32-bit and 64-bit editions of Windows 8

- 59 - N-central 9.5 SP1 Release Notes

Supported Operating Systems for Remote Control The availability of different types of remote control connections will vary based on the operating systems of both the client and target devices.

Windows Linux Mac OS X

Remote Control Remote Remote Remote Technician Technician Technician Type System System System

Attended Remote Control1

DirectConnect1

Generic

2 Remote Desktop

3 Remote Support Manager

SSH

TeamViewer

Telnet

Web

Notes 1. Attended Remote Control and DirectConnect remote control connections are not supported on 64- bit browsers.

2. Remote Desktop connections can be initiated from Mac OS X devices provided that the CoRD remote desktop client has already been installed on the Mac device from which you are initiating the connection. You cannot rename the application as the name must remain as "CoRD".

3. Remote Support Manager will allow you to connect to a device from a Mac OS X client but remote control features will not function.

- 60 - N-central 9.5 SP1 Release Notes

Backup Manager Support

Integration with CA ARCserve D2D N-central Backup Manager supports integration with devices that have the following versions of CA ARCserve D2D already installed:

CA ARCserve D2D Ver- N-central Version sion Already Installed

N-central 9.0 SP1 and later R16

Note: After integration with this version of N-central, the CA R16 Update 1 ARCserve D2D software will automatically be upgraded to R16 Update 6. R16 Update 2

R16 Update 3

R16 Update 4

R16 Update 6

N-central 8.2 to N-central 9.0 R16

Note: After integration with these versions of N-central, the CA R16 Update 1 ARCserve D2D software will automatically be upgraded to R16 Update 4. R16 Update 2

R16 Update 3

R16 Update 4

Warning! Backup Manager does not support integration with CA ARCserve D2D R16 Update 5 due to potential issues with password validation.

Supported Operating Systems N-central Backup Manager is supported on devices using the following operating systems:

- 61 - N-central 9.5 SP1 Release Notes

Operating System Operating System Variant

Microsoft Windows Server 2012 l Foundation

l Essentials

l Standard

l Datacenter

Microsoft Windows 7 l Ultimate (32-bit and 64-bit)

l Enterprise (32-bit and 64-bit)

l Professional (32-bit and 64-bit)

l Home Premium (32-bit and 64-bit)

l Home Basic (32-bit)

l Starter edition (32-bit)

Microsoft Windows Vista l Ultimate (32-bit and 64-bit)

l Home Basic (32-bit)

l Home Premium (32-bit and 64-bit)

l Business (32-bit and 64-bit)

l Enterprise (32-bit and 64-bit)

Microsoft Windows Server 2008 R2 l R2 Enterprise (64-bit)

l R2 Standard (64-bit)

l R2 Datacenter (64-bit)

l R2 Web Server (64-bit)

l R2 Server Foundation (64-bit)

l R2 Core (64-bit)

l R2 Storage Server (64-bit)

- 62 - N-central 9.5 SP1 Release Notes

Operating System Operating System Variant

Microsoft Windows Server 2008 l Enterprise (32-bit and 64-bit)

l Standard (32-bit and 64-bit)

l Datacenter (32-bit and 64-bit)

l Web Server (32-bit and 64-bit)

l Storage Server (32-bit and 64-bit)

l Core (32-bit and 64-bit)

l Server Foundation (64-bit)

l Windows Server 2008 Hyper-V (64- bit) – physical only

l Windows Server 2008 R2 Hyper-V (64-bit) – physical only

l Windows Small Business Server 2008 (SBS 2008)

l Windows Small Business Server 2011 (SBS 2011)

Microsoft Windows XP l Professional (32-bit and 64-bit)

l Home Edition (32-bit)

Microsoft Windows Server 2003 R2 l R2 Enterprise Edition (32-bit and 64- bit)

l R2 Standard Edition (32-bit and 64- bit)

Microsoft Windows Server 2003 Service Pack 1 or l Enterprise Edition (32-bit and 64-bit)

Service Pack 2 l Standard Edition (32-bit and 64-bit)

l Web Edition (32-bit and 64-bit)

l Datacenter (32-bit and 64-bit)

l Storage Server R2

l Windows Small Business Server R2

Supported Applications for Recovery Backup Manager also supports the following for application recovery:

- 63 - N-central 9.5 SP1 Release Notes

Application Application Variant

Microsoft l Microsoft Exchange Server 2003 Service Pack 1 or Service Pack 2 Stan- Exchange Server dalone

l Microsoft Exchange Server 2007 Standalone or Cluster Continuous Rep- lication (CCR) configuration

l Microsoft Exchange Server 2010 Standalone or Database Availability Group (DAG) configuration

Microsoft SQL l Microsoft SQL Server 2005 Express, Standard, Workgroup, or Enter- Server prise

l Microsoft SQL Server 2008 Express, Web, Standard, Workgroup, or Enterprise

l Microsoft SQL Server 2008 R2 Express, Web, Standard, Workgroup, or Enterprise

Supported Disk Types Note: The following information is based on CA Technologies' Knowledge Base Article #TEC523227.

Backup Manager supports the following types of disks as backup sources, backup destinations, and for use with Bare Metal Recovery.

Bare Metal Recovery Sup- port As Backup As Backup Disk (Volume) Type Source Destination Data System and Volume boot volume

1 GPT Disk

1 System Reserved Partition (Windows n/a 2008 R2 Boot Manager)

Mounted Volume (No drive letter/NTFS formatted)

RAW Volume (No drive letter/Not format- ted)

2 VHD Mounted Volume (Windows 2008 R2)

3 Dynamic No RAID Disk

- 64 - N-central 9.5 SP1 Release Notes

Bare Metal Recovery Sup- port As Backup As Backup Disk (Volume) Type Source Destination Data System and Volume boot volume

Software RAID-0 RAID (Stripe)

RAID-1 (Mirrored)

RAID-5

Hardware RAID (Include Embedded RAID)

File System Format

4 FAT/FAT32

File System Share Type

Windows Shared Volume

Linux Shared Volume (samba shared)

Is File System Temporary?

Removable Disk (for example, Memory Stick, RDX)

Notes:

1. Backup Manager only supports BIOS systems as uEFI systems are not supported. 2. The VHD mounted volume used as a backup destination should not reside on a volume that is selected as a backup source. 3. Spanned volume cannot be used as boot volume. 4. FAT/FAT32 file systems cannot hold a single file larger than 4 GB. If the D2D file is larger than 4 GB after compression (because the source is very large), the backup will fail.

Note: If you cannot successfully remove Backup Manager software from a device (or multiple devices), please refer to the following for troubleshooting instructions: http://www.arcserve- knowledgebase.com/index.php?View=entry&EntryID=3138

- 65 - N-central 9.5 SP1 Release Notes

Licensing and Support Information

Agent/Probe Installation Software N-central 9.5 SP1 uses the 7-Zip file archiver for installing agents and probes. 7-Zip is free software redistributed under the terms of the GNU Lesser General Public License as published by the Free Software Foundation. For more information, see http://www.7-zip.org.

COPSSH License Copyright 2003-2007 Tevfik Karagulle ([email protected]). All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 35428

Customer Support Toll Free: 1-866-302-4689

Web Page: www.n-able.com

Technical Support Self-Service Portal: http://www.n-able.com/support/

- 66 - 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: [email protected].

About N-able Technologies

N-able Technologies is the global leader in remote monitoring and management software for managed service providers and IT departments. N-able’s award-winning N-central platform and complementary toolsets, backed by best-in-class business and technical services, are proven to reduce IT support costs, improve network performance and increase productivity through the proactive monitoring, management and optimization of IP-enabled devices and IT infrastructure. N-able is 100% channel-friendly and maintains operations in North America, the U.K., the Netherlands and Australia.

Copyright © 1990-2015 N-able Technologies Inc. All rights reserved.

This document contains information intended for the exclusive use of N-able Technologies' personnel, partners, and potential partners. The information herein is restricted in use and is strictly confidential and subject to change without notice. No part of this document may be altered, reproduced, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of N-able Technologies.

Copyright protection includes, but is not limited to, program code, program documentation, and material generated from the software product displayed on the screen, such as graphics, icons, screen displays, screen layouts, and buttons.

N-able Technologies, N-central, and Report Manager are trademarks or registered trademarks of N-able Technologies International Inc., licensed for use by N-able Technologies, Inc. All other names and trademarks are the property of their respective holders.