Release Notes Version 10.1 N-central 10.1 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, a selection of modules, and is available as on-premises software or as a hosted service. N-central is used by thousands of IT service providers worldwide 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, December 23, 2015. It includes the upgrade procedure, new features and fixed bugs, and known problems for the following releases:

l N-central 10.1

- 2 - N-central 10.1 Release Notes

What's New

N-central 10.1 includes the following new and improved functionality:

Windows 10 The N-central agent has been certified and tested on operating systems. Support has been added for Windows 10 Professional, Enterprise, and Education editions.

Edge (Spartan) and IE Browser Support The N-central UI has been tested and certified to work with the Edge browser included with Windows 10. IE 11 will continue to be supported.

Customer Sites To better manage your Customer's physical locations and logical device grouping, you can now create "Sites." You can map sites to different accounts in MSP Manager, Help Desk Manager, Autotask and ConnectWise. Virtually all customer level features can also be configured at the Site Level.

Moving Devices To leverage Customer Site functionality, devices can be moved from Customer to Customer, Customer to Site, Site to Site, and Site to Customer. You can create test sites or customers and move them to a different customer or site later. The ability to move devices is a grantable user permission.

Probe Assignment For small sites without a where a probe can be installed, you can now share a Probe from the Customer Level with a site or from a Site to a Parent Customer or Sibling Site.

Monitoring Assignment For easier management of Probe-based monitoring services, you can now assign Probes per devices from the All Devices View on a per device basis.

Global Notifications You can now disable notifications during an upgrade or onboarding a prospect with a single click. Disable alerts for Test Sites or turn off alerting for Prospects to reduce the number of notifications to your OC Team. Sites or Customers settings are saved, so that if you disable at a higher level, your settings are retained.

- 3 - N-central 10.1 Release Notes

New Integration Points for MSP Manager We have added integration points for our newest integration of MSP Manager, including:

l Asset Synchronization (Export)

l Automatic Ticket Creation and Closure

l Manual Ticket Creation

l Manual Ticket Updating

l Service Item Update (Billing)

l Time Entry updates

Mac Agent A new Mac agent makes the install process easier for technicians and end users by no longer requiring N- central details to be entered during the install.

Patch Management

Patch On Demand You can now initiate a patch cycle on one or more devices outside of your regular schedule or "On Demand". This lets you patch customers without a set install schedule and update outlying systems that are only available during random intervals.

Patch Schedules through Maintenance Windows Patch events, including detection, download, install and reboot, can now be scheduled in Maintenance windows for added flexibility and control.

Patch On Boot Written An option has been introduced to your Patch Profile that instructs devices that have missed their scheduled patch window to begin a full patch installation cycle on their next system startup. Reboot post patching will not be triggered and can be controlled by your Reboot maintenance windows.

Patch Setup Wizard A new wizard has been added to simplify setting up new patch cycles. This wizard lets you select an existing profile, create a new profile, configure patch windows, and generate your final rule with ease.

Patch Status Service Message Enhancements Messaging for patch sources has been enhanced to more accurately identify where Windows and third party patches originate.

Add Task Drop-down for Patch A new Add Task drop-down feature (located above All Devices, Active Issues and Device) lets you aggregate many of your most common tasks for devices, including File Transfer, Automation and Scripting, AV Scans, Maintenance, and Patch Management.

- 4 - N-central 10.1 Release Notes

Patch Cache Control Caching can now be targeted at specific N-central Probes, providing greater control over which probes are allowed to host the patch cache.

Automation Manager

Branding Automation Manager Designer has been enhanced to match the overall new look and feel of N-central.

Redrag and Drop To enhance the user experience when building policies, now you can drop an object into a policy and later drag and drop it as elsewhere required.

Training Videos New users of Automation Manager wanting to review help videos can now launch a Window from within Automation Manager Designer which will host Training Videos and Webinars from SolarWinds N-able's YouTube channel. Videos are structured in a play list and new videos will automatically appear as they are posted.

Watermarking You now have example text input for all Automation Manager Objects. This will eliminate guesswork when formatting an input parameter or what an object is expecting.

Inline Help If you have a question about how an object works, or how to use the output, a new help icon will open a pop-up to provide useful tips. The pop-up can be moved around and left open if you need it.

Direct Support Scripting Tasks The Automation Policies tab has been renamed to "Scripting" and can run all scripting tasks. This lets your technicians use the full arsenal of scripts and executables to resolve customer problems on demand.

- 5 - N-central 10.1 Release Notes

Fixed Issues

N-central Server

Script/Software repository restore from backup is now successfully upgrading. 76137

An issue where new rule and service template are incorrectly associated. 76725

The Heartbeat of Agent problem is resolved. 76739

The spinning wheel seen when trying to load the device page now works as expected. 76531

Threshold in SQL service buffer manager reverted. 76387

Dell RAID Status service reporting correctly. 76659

Dell Raid Status on upgrade to 10.1 don't use Asset Info. 76715

Failed upgrade from b10_0_0_1844 to b10_0_1_274- 10.0.0.1844. 76593

SO User/SO Tech accounts not retaining customer access visibility after saving. 76824

System Error will not appear on screen when doing nothing in the UI. 76348

Device Move Wizard - License Limits are fixed. 76729

Filter for F-Secure flags all Workstations and Laptops. 76668

All Devices sort icon is reversed. 76738

ForEach object breaks when linking List Network Shares. 76459

AMP uninstall software object doesn't work. 76645

Visual bug on License Limits screen no long visible. 76769

Executive report running properly. 76405

Customer list is sorting correctly. 76522

Customers not longer out of order on the Global Notifications Page. 76598

Administrative Report no longer missing devices in sub-site. 76667

A system error is no longer being generated when adding a second instance of service to tem- 76800 plate.

- 6 - N-central 10.1 Release Notes

If you attempt to upgrade MAC agents to 10.1 with the Log Analysis service enabled, the NCCC-86 upgrade will fail. To upgrade successfully, delete this service and then upgrade. You can add the service after the upgrade. However, service information will date only from the time of the upgrade. No previous data for the service is retained.

When moving a device, after the move, all associated tickets are lost. NCPM-1708

When you move a device, add a note indicating that after the move, all trouble tickets will be NCPM-1709 disassociated with the device.

With the addition of the PSA submit queue, the queue will reach a limit (usually due to NC-596 exports) and may reject new items. This tends to happen when exports are done on a large number of devices.

It is possible to receive multiple notifications for the same failure due to a null value in the 76006 notification buffer.

Windows Clock Drift service flips between misconfigured and green. 75678

In some cases the Self-healing notifications are not being generated. 75896

System Warranty for HP devices is not updating on new devices 75511

When editing the SO level notification Priority 2 alerts and adding the services to the Hard- 75648 ware Warning trigger, once saving receive System Error.

Upgrade failure if /opt partition exists 75226

Importing SNMP devices causing SNMP OIDs index value to be added to the discovered 60806 names.

Default email message templates showing specific example data and not the variables as it 75252 should.

System Error generated on Custom Service view. 75642

In some cases the probe can crash with an out of memory exception against KERNELBASE.dll. 75433

Log capture on Essential licenses is not available. 75728

Ability to select not possible as the device list not showing in some report creations. 75970

CA Replication events service showing misconfigured. 75740

AMP Password parameter base64 encoding is not consistent for scheduled tasks. 75757

In some cases user permissions may not be correct when clicking on a device in the Dash- 75614 board and details may not be able to be retrieved.

- 7 - N-central 10.1 Release Notes

An issue preventing the data submission to N-central based on one VMware disk failure may 75810 occur.

An issue may occur where Domain User Management malfunctions when there the same 74453 Domain appears under multiple customers.

Installed Patch not showing under Asset-> Patches. 74949

A System Error can occur when logging in with a Remote Control user and using the icon to 75870 manage the account.

Added more auditing and cleanup for NPB - NP - NT links. Notification totals are now accur- 72067 ate.

MAC agent monitored services are now reporting in correctly and no longer reported as stale. 75526

SNMP Time out 31040 is now fixed when using the process name. 75925

Process monitoring for lsass.exe and MDR Capture.exe no longer fails. 76019

You will no longer receive a system error when adjusting thresholds in the Log Analysis 76051 Appended service.

You will no longer receive a system error when you set a customized system email in the cus- 76182 tomer level using an SO Tech account and save it.

An issue where some devices were not available for deletion and a System Error was given 76244 has been resolved.

For TeamViewer Custom Service, the variable is read as a string in N-central. 74958

You will no longer receive a system error if you double-click on the "Navigate to SO Level" 76189 link.

Task Profiles that include properly-configured Rules and profiles are now correctly being 73143 associated to a device.

Openfire Database corruption caused due to small size and causing Jetty reboots has now 75156 been resolved.

An issue where a WMI-based service was being discovered incorrectly has been resolved. 73606

You can manually input information for SNMP devices that fail to include information added 75016 during device discovery.

An issue where an agent redirect was redirecting incorrectly has been resolved. 75138

Veeam Job Monitor/Veeam Sure Job Monitor services are not configured to allow use of asset 72990 information has been resolved to allow the use of asset Information

- 8 - N-central 10.1 Release Notes

An issue where Service metrics that were turned off still showed in the report has been 74746 resolved.

An issue where Enabling "Update Monitored Address" option does not add the "LocalIP" ser- 75145 vice has now been resolved.

AV Defender Security Event showed in a failed state and never returned to normal after the 75404 event was blocked.

An issue where a Caps Lock warning was available and enabled when it should not have been 74846 has been resolved.

When attempting to configure a SSH username and click save the changes do not take effect. 74853 This issue has now been resolved.

When attempting to configure the Setting Mail relay to not use a relay, a sendmail failure 74879 occurred. This has now been resolved.

An issue when opening Domain Management at the Service Organization level and the Cus- 75503 tomer Level was producing a System Error has been resolved.

When trying to add an Windows Event Log Service, in some cases, the service template was 74882 sending an Event log error.

An issue where a System Error was produced when trying to sort in the Scheduled tasks 75508 screen at the Service Organization level has been resolved.

An issue where some Scheduled Reports were not showing the correct background has been 74954 resolved.

An issue where N-central status of a server was showing normal but was not has been 74273 resolved.

An issue where it was no longer possible to see when a device was added to N-central has 75543 been resolved.

Windows Event Log IDs were mistakenly listed under "Event Source Exclude Filter" instead of 75117 under "Event ID Include List".

When trying to customize the text in the NCentral Executive Summary report, it fails to show 75576 those changes in the displayed report. This issue has been resolved.

When editing a notification trigger for “Windows Event Log," modifying the originally chosen 75137 selection for when the notification is triggered from “Service changes state” or “Service Instance changes state” to the other, the new selection is now applied.

After upgrade, monitoring of the disk information on a CentOs device was going stale. This 75353 has been resolved.

- 9 - N-central 10.1 Release Notes

For devices that cannot load SnmpComp.dll or one of its dependencies, use the SolarWinds 70700 SNMP library for discovery and monitoring of devices that use SNMP v1 and v2.

You can now email reports to multiple email addresses using comma-separated addresses. 75438

To update a service in a service template, replace the '/' with a valid file name character when 75472 unzipping the service template.

You will not receive a System error when you attempt to log in following an upgrade. 75542

CPU service tabs are now loading properly when drilling into the CPU service. 75553

The Asset information OS Features/Roles is now available on the Asset>Operation System 74934 tab.

The Service Template output is now displayed as string in N-central. 74958

A System error is no longer thrown when changing the network address of a device. 75624

Memory capacity for ESX is no longer reporting memory size incorrectly. 74972

If you create and export a Service Template bundle, you can now successfully import it again. 75068

When adding devices, you will see a list of Custom Device Properties at the System level. 75873

Reboot Required service was added to N-central, it was erroneously given 100 for Max 75709 Instances. Max Instances is only 1.

Automation Manager

Description Bug

The AMP Output Parameter HardwareDeviceCheckOutput displays numbers correctly. 76435

An issue when executing an Automation Policy using PowerShell not installed on the C: drive 71353 has been resolved.

When rebuilding an Amp and error to access path was thrown and this issue has now been 71967 resolved.

While uploading policy to N-Central the upload timestamp is not set correctly. AM-1207

Backup

Description Bug

An enhancement has been provided so that during a backup, the FTP session is left open 71737 using NOOP.

- 10 - N-central 10.1 Release Notes

Backup Manager

Description Bug

An issue where in backup Manager, clicking on a device caused a System Error to occur has 74363 now been resolved.

N-central Backup failed to create the tar file in some cases due to start time of the backup not 75314 being valid. This issue has been resolved.

An issue may occur on upgrade of Backup agent upgrade where Backup Manager status goes 75861 misconfigured until intervention and refresh.

Direct Support

Description Bug

On the task execution, Direct Support tool, when you run a scripting task that returns char- 76178 acters, the HTML encoding displays correctly in the results preview.

An issue where Remote Control Management was being cleared up has been resolved. 75362

An issue where trying to configure Remote Control settings to use the Ip address instead the 75494 Fully Qualified Domain Name has been resolved.

An issue where selecting any Android device and clicking on an Application caused the link to 75557 the Application to go to a generic URL, and has been resolved.

The IP address in the Remote Control settings web page may not be saved. 75798

When HTTP protocol chosen it forces port 443 under the Web Page Default Connection type in 75641 the Remote Control Defaults.

Documentation

Description Bug

An issue where there was a bad link in the product linking to the Online help has now been 73201 resolved.

- 11 - N-central 10.1 Release Notes

Mobile Manager

Description Bug

MDM view correctly shows device is roaming. 75545

You will no longer receive a System error when trying to remove a device listed in the import 75579 device list (mobile devices).

If you cannot import MDM devices due to a lack of licenses, an error is returned. 75140

Patch Management

Description Bug

Patch detected in line with patch detection schedule. 70772

Patch installed immediately. 76750

Patch Management filter no longer malfunctioning. 76700

Patch Management: Add Reboot Window: Remove "Yes" from right of check boxes. 76710

N-central Missing Patch report is out of alignment. 75936

Patch is now being downloaded as defined by the workflow. 75520

After setting a patch for removal, the patch does not show on the device as approved. 76073

An issue where the Patch Summary window was not showing the same information as the 75125 Patch Status Serivce for the device has now been resolved.

A resolution has been provided for an issue where patches are shown as missing when they 74693 are actually Installed but with errors.

An issue where once trying to approve patches the page does not refresh and does not come 75155 back. This issue was found to the an empty ProductID and a check has been added.

When exporting to .csv the missing patch summary report is adding additional product 75169 information in the product column. This issue has been resolved.

An issue where in some cases Patch Management appeared to be trying to install Windows 73960 Update manager continually has been resolved.

An issue where the Patch Management pop up to allow installation of patch was not allowing 74243 install has been resolved.

- 12 - N-central 10.1 Release Notes

Description Bug

An issue where some patches were showing as missing when they were actually approved for 75269 removal has been resolved.

Notepad++ is failing to transfer from the probe, resulting in the patch status stuck in pro- NCPM-2113 gress.

Patch Install Immediately' + 'Patch Pre-Download Immediately' + 'on schedule' approval = NCPM-2115 Patch downloads + No Install.

If install Window (NOW) + Approval (Scheduled) = Patch Installation does not start. NCPM-2112

Very slow to filter patches for "No Approval". 76426

PSA

Description Bug

AV Defender Security Events all going to ticket. 76122

PSA Ticketing Recipient not giving a System Error. 76391

No system Error when creating a new PSA Integration > Ticketing Recipient. 76555

In some cases the system does not allow us to save the changes made in the PSA ticketing 75604 recipients profile and may not get past loading when clicking on the save button.

PSA configuration links not appearing at customer level for new customers. 75806

An issue where the trying to setup an Autotask integration to UI will not allow you to display 75666 the Account Name list.

The Device Location Field in AutoTask is no longer blank after a exporting a device. 76316

An issue where a "deviceid" was found to be null when creating ticket for Autotask has been 73201 resolved.

An incorrect ticket creation date was displayed in the UI and has been resolved. 74710

Recent Tickets for device not showing up because of NullPointer Exceptions when getPSATick- 75602 ets is called has been resolved.

Tickets deleted in Connectwise no long appear in N-central. 76712

- 13 - N-central 10.1 Release Notes

Remote Control

Description Bug

When attempting to access "printers" in the Reactive tools, an error of "An unexpected 75689 response was received. Click to try again."

Security Manager

Description Bug

Rules take 2-4 minutes to load. 75240

Custom Service : HP ProCurve Switches | cannot be Imported. 75540

AV Defender Server profiles are deployed instead of individual profiles. 75843

Anti-phising module cannot be removed from the profile settings. 75454

A "Now" option for the upgrade for AV Defender does not trigger an immediate upgrade. 75878

“Initial profile has not yet been applied” error after AVD upgrade has been resolved. 76251

An issue where the N-central agent RemoteService for AV Defender was being blocked has 70363 been resolved.

Anti-phishing type is no longer showing an incorrect value during notification. 75488

Allow Remote Control Option is no longer locked out in N-central at the Customer/SO level. 75691

UI

Description Bug

Stock branding image for a reboot request has not yet been updated. NSBM-664

When the reboot message is displayed, it is on top of all active windows so the user can see 76325 the message and not in the background.

The Create ticket panel is no longer grayed-out. 75551

An ability for the SO User to modify the threshold of Services has been resolved. 75230

An issue where the email body text was not included in the email for Service Metrics has 75297 been resolved.

- 14 - N-central 10.1 Release Notes

Known Issues

Automation Manager

Description Bug

Automation Manager Prompt object incorrectly reporting click result. 76866

Get Info on all Office 365 Mailboxes Automation Manager Policy does not work. 73981

Exchange Database statistics - incorrect output types. 71801

Automation Manager Object "Disable USB Devices" also disables printers. 69403

Mobile Manager

Description Bug

MDM profiles failing to apply. 74052

Remote Control/Direct Support

Description Bug

Direct Connect does not connect to this device. 75465

Connection Type is Locked to Direct Connect but user can remote control using other methods. 74112

RDP session using port as network address, when different port is setup for 443. 76825

Discrepancy in how Applications are listed. 75613

An issue where remoting into device is not valid if the device is down. 76918

- 15 - N-central 10.1 Release Notes

N-central Server

Description Bug

In some cases Stale Services may occur. Workaround to disable and re-enable a service. 76728

System error when try to edit threshold in custom service Hyper-V virtual machine replication. 76623

Patch data may be incorrect in Report Manager. 76490

Discovery Job not discovering Interfaces. 76828

Backup Failed - Postgres logs are blank. 76928

Disabled Scheduled AMPs still running on agent. 76793

Patch Scan running at unexpected time. 75020

DataQueueThread got stuck after service postgresql reload. 75284

Submit queues overload due to errors in API calls. 76170

Office 2010 Volume License Key detected as OEM/Retail. 76503

Total disk size is 0 in hardware inventory report. 76806

Popup description does not move with related field. 71906

Running the details status report without a service selected causes system error. 74950

Export to PDF not sorted. 76751

System Error Generating Scheduled Task Summary Report. 76891

Incorrect Disk Usage % Formula. 76589

System Change service failed after upgrade to 10 SP1, new Network Adapters detected. 75858

Managed device removed at '2015-03-08 03:03:30' by MaintDataExpiry.DeleteStaleAssets(). 72459

InstallDotNet64.vbs doesn't seem to silently install. 76565

Multiple same Service template application may cause the Submit queue to perform poorly during 71556 the application of the Service Template.

Missing details for mac devices for hardware inventory report. 71498

Unable to delete CDP - "Patch Approval - Desktop". 72405

- 16 - N-central 10.1 Release Notes

Description Bug

Very slow RemoteExecutionTask.List(). 73077

Server offline due to whitelisted a URL on the global AV profile. 75510

HTTPS service failed when URL has valid SSL certificate. 76126

Sørensen appears as Sørensen in browser tab. 74274

Stock Defrag.vbs script does not take Windows 2012 servers into account. 73724

Veeam job V2 service metric result different from the Veeam console. 75665

Cannot add SYSLOG custom service to Storage Device Class System. 76194

In the Moving Devices Wizard, the devices list is expanded by default. NCPM-1706

When moving a device, ticket tables need to be cleaned up for Report Manager. NCPM-1710

Two customers under the same SO may discover the same device. NCPM-1602

Handle profile-based tasks of non-moving devices when probe returns. Scheduled Task items NCPM-2000 from Scheduled Task Profiles that require a Probe to execute are removed when no remaining Probes are available at origin (due to move).

You may not add a custom SYSLOG service to storage devices that can send SNMP traps using NCPM-1839 the Storage Device Class.

Export Logic not setting AuditorEnabled to false if export is more than 2months. There is an issue NCPM-1823 with the export logic not respecting the two time entries in AuditorSettings and SysConfig tables. Contact Support if you see this issue.

Scheduled AMP tasks still run after disabled. 76576

Export up to a specific date functionality was changed unexpectedly. 76872

An issue where discovery of OS X 10.11.1 may be experienced. 77055

OS HyperV 2012R2 does not show properly. 77056

Performance for Maintenance Delete tables may be slow due to cim tables. 77059

Warranty Expiry report not emailing properly. 76957

System Error may occur on a server if the disk is full. 76885

Old password is used when using Save Me. 76847

- 17 - N-central 10.1 Release Notes

Description Bug

Mail Logging may grow too quickly in some circumstances. 77249

If applying a code drop it is possible some of the files are not dropped due to services already run- 76745 ning.

Notification – TaskTriggeringScanDetail can be slow and there by slowing the sbmit queue in 77001 some cases.

System Error may be experienced when clicking on a device. 77012

On a Server system change it may be possible that the System change server does not update 76999 the new baseline.

Moving Customer to Site’s resets the settings. 76689

System Error may occur when viewing a report due to incorrect permissions handling. 76890

An issue where sequencing during the upgrade procedure may cause the upgrade to stop. 76849

Patch Management

Description Bug

When setting an installed windows 10 update to "Approved for Removal," the following note is NCPM-2008 included in the Patchinstall.log: "The parameter is incorrect." The patch should be removed.

Exports failing on historical_cim_patch. 76065

Patch On Boot does not check for a previously missed install schedule. If this function is N/A enabled your devices will check for, and install, any pending approved patches on system star- tup. It is recommend you not use this feature for any mission critical or sensitive devices as they may experience an unexpected patch install cycle and longer reboot times due to patch detection.

- 18 - N-central 10.1 Release Notes

PSA

Description Bug

Multiple N-central Customers mapped to single PSA customer causes Billing profile to not 74027 update counts as expected.

PSA Integration not updating billing profile with multiple customers and filter selected. 76836

Error exporting devices to MSP Manager. 76763

Ticket won't clear out of N-central. 75698

Ticket was not closed after service transitioned to normal. 76002

System Error shows when clicking Add button in Device Class Mappings in PSA Integration. 76343

Security Manager

Description Bug

AV Defender Status Report: Installation Status Failed has a Count of 5 but Failed Installation 76023 Details has a Count of 3.

AV Defender - Scan new device. 76680

AV Defender - Firewall - settings page fails to load. 76131

AV Defender Scans not running. 76749

AV Defender - Scan - Scheduled Scan Task expired. 76427

UI

Description Bug

Lync Services missing help text. 76798

A System Error may occur when accessing version information in the UI. 75622

- 19 - N-central 10.1 Release Notes

Known Limitations

Active Issues

Description Bug

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

Agents & Probes

Description Bug

An issue with the deprecation of support for SSL v3 may cause the upgrading of Linux 71680 agents from 9.5.x to 10.x to fail. To resolve this issue, refer to "KBA20021: Upgrading Linux Agents from 9.5.x to 10.x" in the online help.

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

Automation Manager

Description Bug

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

Backup Manager

Description Bug

ShadowProtect Data Reader service is using high CPU due to large amount of historical 74971 data as part of the backup.

The About Backup Manager dialog box no longer indicates whether or not the Backup 68226 Manager software is licensed.

N-central 10.1 supports CA ARCserve D2D R17 but that version of D2D does not support 68435 Windows XP.

- 20 - N-central 10.1 Release Notes

Customer Services

Description Bug

Custom services may appear as misconfigured when the system locale of the device is not 65288 set 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 SolarWinds N-able Tech- nical Support.

Dashboards

Description Bug

Modifying a Dashboard that is associated with a large number of services may cause per- 70326 formance issues when using the Firefox browser.

N-central Server

Description Bug

With the complete removal of support for Security Manager - Endpoint Security as of 73491 December 31, 2014, upgrading to N-central 10.0 will now fail if any Endpoint Security ele- ments (including associated services) are present on devices managed by N-central. To avoid this issue, all installations of Endpoint Security software on managed devices must be removed. In addition, all services related to Endpoint Security must also be removed from managed devices in order for the upgrade to N-central 10.0 to succeed.

This issue has been resolved. Chrome 42.x does not support NPAPI plugins which means 73359 that Java and Direct Connect will not function with that browser version. When attempting to open remote control connections in Chrome 42.x, users will be repeatedly prompted to install either Java or the NTRglobal plugin with no successful connections made. To resolve this issue, perform the following: 1. In the Chrome address bar, type chrome://flags/ 2. Under Enable NPAPI, click Enable. 3. Restart Chrome.

When monitoring the N-central server using SNMP, the community string to be used for n/a SNMP queries to the server must use the required string value as the default community string ("public") is no longer valid.

An issue where Apple is no longer allowing Services to make calls for Warranty Inform- n/a ation of a device has been noted. You will no longer get the Warranty Information for MAC devices.

- 21 - N-central 10.1 Release Notes

Patch Management

Description Bug

If the device with the N-central Probe is using a version of Windows 2003 that does not 68390 have 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 62277 XP® for their 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.

Microsoft Security Bulletin MS14-045 announced the withdrawal of four individual Win- 67830 dows updates due to security issues. This security bulletin applies to: • Windows RT and Windows RT 8.1 • and and Windows 8.1 • and The following updates were withdrawn: •2982791 •2970228 •2975719 •2975331 If any of these updates have been installed on managed devices, refer to the security bul- letin for more information on how to resolve any potential security risks.

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

- 22 - N-central 10.1 Release Notes

PSA Integration

Description Bug

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 nor- mal 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.

UI

Description Bug

Product Key Card versions do not get picked up by the License Key Inventory. As 61453 Microsoft changes there licensing model, this information is not available any longer in the OS to be picked up and processed from the registry key. Microsoft is no longer stor- ing the Product Key in the registry.

System errors or timeout errors may prevent very long lists of domain users from being NID-63 displayed properly in the Domain User Management screen.

When displaying Services in the Tools tab, the Click to try again feature to refresh the 70965 service display may not function properly when using Internet Explorer 9 or Internet Explorer 10.

After re-naming, the Names of files or Registry entries may not be displayed properly in 68149 the File System window and the Registry window of the Tools tab when using Internet Explorer.

- 23 - N-central 10.1 Release Notes

Hardware Requirements

For the minimum hardware requirements for the N-central 10.1 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: 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 configured for backups.

21 Used for FTP connections, particularly when configured for backups.

22 SSH - used for remote control sessions. The firewall 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.

- 24 - N-central 10.1 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 Internet to this port on the N-cent- ral 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 quer- ies to monitor various services.

139 Used by Agents and Probes for WMI quer- ies to monitor various services.

443 HTTPS - used for communication between the N-central UI and Agents or Probes. Port 443 is the TCP port needed for SSL (HTTPS) connections. 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 quer- ies to monitor various services.

- 25 - N-central 10.1 Release Notes

PORT LOCATION

Port N-central Server Managed Device Description Number

Inbound Outbound Inbound Outbound

1433 * * * Outbound on the N-central server, port 1433 is used by Report Manager for data export. On managed devices, it is also used by Agents (inbound) and Probes (out- bound) 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.

2000 Used for Remote Support Manager con- nections locally on the computer. Traffic is mapped to port 2000 locally and trans- mitted to the N-central server through port 22.

2195 Used to send Mobile Device Management notifications to APNS servers at gate- way.push-apple.com.akadns.net.

2196 Used to send Mobile Device Management notifications to APNS servers at gate- way.push-apple.com.akadns.net.

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

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

- 26 - N-central 10.1 Release Notes

PORT LOCATION

Port N-central Server Managed Device Description Number

Inbound Outbound Inbound Outbound

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

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

11438 To use Direct Connect 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 outbound 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:

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)

- 27 - N-central 10.1 Release Notes

Firewall Configuration Requirements Secure Shell access is required for SolarWinds N-able 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 Direct Connect 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

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.

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

- 28 - N-central 10.1 Release Notes

Device Type Vendor - Web Site URL

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

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 Agent l Server In The Sky (SIS) - http://sis.n-able.com

If no Probes have patch caching enabled

Device Type Vendor - Web Site URL

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

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.

- 29 - N-central 10.1 Release Notes

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.

- 30 - N-central 10.1 Release Notes

Software Requirements

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

l Internet Explorer®, versions 10.x and later

l Mozilla Firefox®, versions 35.x and later

l Google Chrome®, versions 40.x and later

Notes

l Chrome 42.x does not support NPAPI plugins which means that Java and Direct Connect will not function with that browser version. When attempting to open remote control connections in Chrome 42.x, users will be repeatedly prompted to install either Java or the NTRglobal plugin with no successful connections made.

To resolve this issue, perform the following:

1. In the Chrome address bar, type chrome://flags. 2. Under Enable NPAPI, click Enable. 3. Restart Chrome.

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

l Attended Remote Control and Direct Connect remote control connections are not supported on 64-bit browsers.

Agents and Probes Microsoft .NET Framework

To function on a managed device, Agents require the following versions of Microsoft .NET Framework to be installed:

l Microsoft .NET Framework 2.0.50727 (or later)

l Microsoft .NET Framework 4.0.x

Agents will not function properly on devices that only have Microsoft .NET Framework 4.0.x installed.

- 31 - N-central 10.1 Release Notes

.NET Framework on device Probe Agent

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 10.1.

SNMP Community String When monitoring the N-central server using SNMP, the community string to be used for SNMP queries to the server must use the required string value: N-central_SNMP.

Note: The default SNMP community string (public) is no longer valid for SNMP queries to the N-central server.

- 32 - N-central 10.1 Release Notes

Upgrading to This Release

To upgrade, your N-central server must be running one of the following versions:

l N-central 10: 10.0.0.1722+

l N-central 10 SP1: 10.0.1.274+

l N-central 10.1: 10.1.0.145+

Before you upgrade, make sure you back up your data consistent with a date range for your Report Manager and N-central servers.

Important Upgrade Notices Please note the following important notices before upgrading to N-central 10.1.

Windows 10 Support If you are using Backup Manager, note that N-central 10.1 does not certify Windows 10 support at time of this release.

Patch Schedules through Maintenance Windows Patch events can now be scheduled in Maintenance windows for added flexibility and increased control. Please note the following:

l When you upgrade to 10.1, any scheduling currently done through Patch Profiles are transitioned into Maintenance Windows automatically. If you had applied your profile using a Rule, the win- dows will be created in that Rule and distributed accordingly. If you have applied a Patch Profile manually, the windows will be created at the device level.

l If you have accidentally targeted two or more Patch Profiles at a given device you will find multiple patch windows applied to your devices. To avoid this, review your Patch Profile distribution before upgrading. If your upgrade results in device level Patch windows being applied to some devices, they can be cleared along with all other device level Maintenance Windows from the All Devices view under Add Task > Maintenance > Clear Device Level Maintenance Windows.

- 33 - N-central 10.1 Release Notes

Warning! If you are currently monitoring StorageCraft backups using the custom service provided on the N-able Resource Center, 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 mon- itoring service and script found on the N-able Resource Center.

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

c. Ensure that ETL is scheduled in Report Manager for every hour.

d. Ensure that data exports are taking place normally.

e. Configure the automatic update settings for your Agents to Never.

- 34 - N-central 10.1 Release Notes

Warning! 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.

7. For the selected devices, upgrade your Agents.

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 SolarWinds N-able 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.

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

- 35 - N-central 10.1 Release Notes

Reviewed Category Notice

Agents When upgrading the Agent on a device with a Professional Mode license from 9.5 to 10.0, the Enable Direct Support option will automatically be enabled. When upgrading the Agent on a device with an Essentials Mode license from 9.5 to 10.0, the Enable Direct Support option will not be enabled and must be configured manually after purchasing a Direct Support license. To purchase licenses for N-central features, contact your Partner Development Specialist (PDS). You can look up your PDS and their contact information in the N-able Resource Center under My Account. You can also send an email to [email protected].

Agents Mac and Linux® Agents can only be upgraded automatically if they are of the following versions:

l Mac Agent - 9.0.0.84 or later

l Linux Agent - 9.0.1.113 or later

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. Ensure that the target devices have the latest Windows Service Packs and critical updates installed before upgrading Agents in order to avoid this issue.

Security An issue with N-central 10.0 prevents the AV Status service from being Manager added to devices that use Essential Mode licenses.

Security With the complete removal of support for Security Manager - Endpoint Manager Security as of December 31, 2014, upgrading to N-central 10.1 will now fail if any Endpoint Security elements (including associated services) are present on devices managed by N-central. To avoid this issue, all installations of Endpoint Security software on managed devices must be removed. In addition, all services related to Endpoint Security must also be removed from managed devices in order for the upgrade to N-central 10.1 to succeed.

- 36 - N-central 10.1 Release Notes

You can upgrade to N-central 10.1 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.

- 37 - N-central 10.1 Release Notes

Step One: Backing Up the N-central Server If N-central has been installed as a guest on an ESX or Hyper-V server, we recommend that you record a snapshot of the guest before upgrading. Should the upgrade fail, 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

- 38 - N-central 10.1 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/

- 39 - N-central 10.1 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 SolarWinds N-able 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.

- 40 - N-central 10.1 Release Notes

Step Two: Installing the N-central Server Upgrade You can upgrade to N-central 10.1 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 SolarWinds N-able for assistance.

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

To install the downloaded N-central 10.1 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: 10.1.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.

- 41 - N-central 10.1 Release Notes

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

Note: SolarWinds N-able recommends that you upgrade probes, agents and related software on a customer-by-customer basis. Ensure that each customer is 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-10.1.0.xxx-b10_0_0_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.

- 42 - N-central 10.1 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.

- 43 - N-central 10.1 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

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 > AV Defender Status

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

l You must upgrade both the N-central server and Windows Agents to version 9.2 or later. The Patch Status, CPU, Memory and Process services will report a Misconfigured status if you have not upgraded.

l Because 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.

l After you upgrade to N-central 9.2 or later, review all previously-configured Patch Man- agement profiles. There are new settings in profiles you must configure before Patch Man- agement will work properly.

l To approve or decline patches with devices that have not yet upgraded their Agents to Ver- sion 9.2 or later, sign in directly to the appropriate WSUS server and approve or decline patches there.

- 44 - N-central 10.1 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:

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

l you are migrating an existing N-central server to another computer

Before attempting to rebuild or migrate your N-central server, ensure that you verify that the server meets the requirements of the version that you are installing.

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

Scenario A: Server is not Functioning Properly or Starting Successfully

1. Verify the version of your N-central server. SolarWinds N-able Technical Support can con- firm the version of N-central that last communicated with SolarWinds N-able 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 SolarWinds N-able 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.

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

- 45 - N-central 10.1 Release Notes

allows you to install the ISO and then restore your backup. The following is an example of an ISO file available for download at 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.

5. When the system restore is completed, please contact SolarWinds N-able to have your N- central server activated.

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

1. Verify the version of your N-central server. 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. 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.

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

- 46 - N-central 10.1 Release Notes

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.

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 lets you install the ISO and then restore your backup. Here 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. It is not intended for upgrading an existing N-central server.

4. Restore the backup that you located in Step #2 above.

5. When the system restore is completed, please contact SolarWinds N-able to have your N- central server activated.

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

1. Verify the version of your N-central server. 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. Create a new backup in order to minimize data loss.

i. Click Administration > System Backup and Restore > Configure Backups.

ii. Click Save and Run Backup.

- 47 - N-central 10.1 Release Notes

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

b. Download the most recent backup.

i. 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, save the digest file to the location used 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. This can affect system performance.

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 lets you install the ISO and then restore your backup. The following is an example of an ISO file available at 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.

- 48 - N-central 10.1 Release Notes

5. When the system restore is completed, please contact SolarWinds N-able to have your N- central server activated.

For assistance with this procedure, please contact the SolarWinds N-able 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/.

- 49 - N-central 10.1 Release Notes

Platform Support

Supported Operating Systems for Agents

Microsoft Windows (WindowsAgentSetup.exe)

Microsoft .NET Framework

To function on a managed device, Agents require the following versions of Microsoft .NET Framework to be installed:

l Microsoft .NET Framework 2.0.50727 (or later)

l Microsoft .NET Framework 4.0.x

Agents will not function properly on devices that only have Microsoft .NET Framework 4.0.x installed.

Windows Server® l 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

- 50 - N-central 10.1 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

- 51 - N-central 10.1 Release Notes

Windows Server 2000 l Microsoft Advanced Server

l Microsoft Windows 2000 Data Center

l Microsoft Windows 2000 Professional

l Microsoft Windows 2000 Server

l Microsoft Windows 2000 Server Appliance

Warning! Refer to the notes at the beginning of this list for limitations on the versions of N-central Agents that are compatible with Windows Server 2000.

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 10 l Microsoft Windows 10 Enterprise

l Microsoft Windows 10 Enterprise 64-bit Edition

l Microsoft Windows 10 Professional

l Microsoft Windows 10 Professional 64-bit Edition

l Education editions

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

- 52 - N-central 10.1 Release Notes

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 2011

l Microsoft Windows Small Business Server 2011

l Microsoft Windows Storage Server 2003 R2

l Microsoft Windows Unified Data Storage Server 2003

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-rhel_64.tar.gz l CentOS 5 64-bit Edition

l CentOS 6 64-bit Edition

l CentOS 7 64-bit Edition

l RedHat Enterprise Linux 5 64-bit Edition

l RedHat Enterprise Linux 6 64-bit Edition

l RedHat Enterprise Linux 7 64-bit Edition

nagent-rhel.tar.gz l CentOS 5 32-bit Edition

l CentOS 6 32-bit Edition

l CentOS 7 32-bit Edition

l RedHat Enterprise Linux 5 32-bit Edition

l RedHat Enterprise Linux 6 32-bit Edition

l RedHat Enterprise Linux 7 32-bit Edition

Mac® OS X® Agent

- 53 - N-central 10.1 Release Notes

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

l Apple Mac OS X 10.10

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

- 54 - N-central 10.1 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

l Microsoft Windows 10

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 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 running Windows XP (64-bit). It is supported on devices running:

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

- 55 - N-central 10.1 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 Sys- Remote Remote Technician Technician Technician Type tem System System

Attended Remote Control1

Direct Connect1

Generic

2 Remote Desktop

3 Remote Support Manager

SSH

TeamViewer

Telnet

Web

Notes 1. Attended Remote Control and Direct Connect 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.

Remote Control OS Requirements For remote control operations, the default application varies based on your operating system and remote control type:

- 56 - N-central 10.1 Release Notes

Remote Control Type Windows Mac OS X

Custom n/a n/a

Direct Connect see note below see note below

Remote Desktop Mstsc n/a

Remote Support Manager Web Browser Web Browser

SSH PuTTY n/a

TeamViewer see note below see note below

Telnet PuTTY n/a

Web Web Browser Web Browser

- 57 - N-central 10.1 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.

Note: If you are using Backup Manager, note that N-central 10.1 does not certify Windows 10 support.

- 58 - N-central 10.1 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)

- 59 - N-central 10.1 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) Warning! CA ARCserve D2D R17 does not support Windows XP.

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:

- 60 - N-central 10.1 Release Notes

Application Application Variant

Microsoft Exchange l Microsoft Exchange Server 2003 Service Pack 1 or Service Pack 2 Stan- 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

- 61 - N-central 10.1 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 selec- ted 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

- 62 - N-central 10.1 Release Notes

Licensing and Support Information

Agent/Probe Installation Software N-central 10.1 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.

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/

- 63 -

© 2015 N-able Technologies, Inc.

All rights reserved. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of N-able Technologies, Inc. (“N-able Technologies”). All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of N-able Technologies and its respective licensors.

N-ABLE TECHNOLOGIES DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL N-ABLE TECHNOLOGIES, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The N-ABLE TECHNOLOGIES and N-CENTRAL marks are the exclusive property of N-able Technologies and its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other N- able Technologies trademarks, service marks, and logos may be common law marks, registered or pending registration in the United States or in other countries. All other trademarks mentioned herein are used for identification purposes only and may be or are trademarks or registered trademarks of their respective companies.

Feedback

SolarWinds N-able (formerly known as 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 SolarWinds N-able

SolarWinds N-able is the global leader in remote monitoring and management software for managed service providers and IT departments. SolarWinds 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. SolarWinds N-able is 100% channel-friendly and maintains operations in North America, the U.K., the Netherlands and Australia.