Embed Size (px)
Citation preview
1
Release Notes Version 10 SP1
What is N-central? N-central is the #1-rated remote monitoring and management automation platform 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 Monday, August 24, 2015. It includes the upgrade procedure, new features and fixed bugs, and known problems for the following release:
• N-central 10 SP1 (General release)
What's New in N-central Welcome to N-central 10 SP1, the latest release of SolarWinds N-able's flagship remote monitoring, management and automation platform. The release provides updates to the following areas:
Windows 10
• Official support will be announced once testing successfully completes on the RTM build of Windows 10. N-central has currently been tested on the Windows 10 Enterprise and Pro Insider Preview. This includes running the N-central web console using the Microsoft Edge browser. We are offering the ability to run discovery capabilities for correct classification of Windows 10 devices.
Chrome Support In September 2015 Google Chrome is making important changes to the technologies they are allowing to run. The following changes have been made to N-central in order to maintain support for Google Chrome browser: • Direct Connect: Direct Connect can now optionally be launched using a downloadable
executable, on the technician machine, as an alternative to the NPAPI plugin. This change allows us to maintain support for the Google Chrome browser.
• Java: As of this release, N-central no longer checks to see if java is installed before allowing download of the Java remote control connector (JNLP). As a result Chrome users will no longer be asked to activate java on N-central login.
2
Behavioral Analysis Support for Servers • AV Defender protection for Windows Servers now includes support for the Behavioral
Analysis module. This provides an additional layer of protection for next generation threats. To enable this module, your endpoints must be updated to the latest base version.
Monitoring Services New services have been included that allow you to monitor:
• F-Secure You will now have insight into Definition Age, Results from Scans, the Protection Level, and many more details for F-Secure AV.
• Exchange Service Enhancements
Exchange 2013 monitoring will automatically discover the database name for easier configuration of monitoring.
• Windows License Status
N-central can now detect the current license status of a Windows device and notify on situations where the OS is not active.
• Microsoft SharePoint
Monitoring has been added for verification of the health of SharePoint 2013, along with critical Windows Services, to ensure SharePoint is functioning.
• Microsoft Lync
Monitoring for the health of Lync 2013 is now included, as well as critical Windows Services to ensure Lync is functioning.
• Report Manager
Report Manager monitoring has been enhanced with additional Log Expressions and Database Statistics.
Password Reset • If the login password is forgotten, N-central users now can request a temporary
password which will be sent to their email.
3
Fixed Issues
Agents and Probes Description Bug
An issue where the ShadowProtect job was showing as ‘not active’ in N-central monitoring has now been resolved.
67211
Error – Packet was unable to be decoded at the agent when using SNMP v3 SNMP service. 73973
An issue where cim_customermachine was not reporting the same data in cim_memory has been resolved.
72881
An issue with MAC agent not showing in the installed Application List has now been resolved. 73609
Automation Manager Description Bug
An issue where “Failed to retrieve policy” message provided when attempting to browse N-central and open an AMP has been resolved.
71836
AV Defender Description Bug
An issue with Out of Memory caused due to a large quantity of AVD Quarantined items in the Database table has been resolved.
73405
An issue where Scheduled Full scans were running sporadically has been resolved. 73752
Backup Manager Description Bug
An issue where the N-central Backup was not able to start via FTP due to a special character in the password has been resolved.
74396
Devices Description Bug
An issue where devices could not be auto-imported has been resolved. 74119
4
N-central Server Description Bug
Service instance notification triggers are not propagated properly to the Customer Level as it is at the Service Organization level.
74795
An issue where attempting to update the Asset information for a device the Application Compliance Service was not showing any Discovered Applications and has been resolved.
74300
An issue where bulk modifying custom device properties to a blank value was not accepted has been resolved.
74562
A problem where Self-Healing was sending HTML notification as text has been resolved. It now adheres to notification preferences.
73680
Libssl library used by Agent/Probe for SNMP v3 has been updated to adhere to security standards.
75379
Discovery auto-import failing due to device previously discovered in unmanaged state. 73470
An issue where the monitoring for SQL Express was monitoring the incorrect WMI class. 72114
Receiving “4100 Invalid parameters” when clicking on Update Now has been resolved. 74336
An issue where TeamViewer for MAC was failing has been resolved. 74568
License Compliance page issue where page is not showing detected installations has been resolved.
73279
An issue where Scheduled Task Execution start was delayed and caused a reboot has been resolved.
74768
Warranty not showing proper expiry issue has been resolved. 73990
License Compliance report issue where it was reporting the same Software package multiple times has been resolved.
75043
System Error when accessing Script/Software Repository at the SO level has been resolved. 72882
API additions: DevicePropertyModify and DevicePropertyList 74606
Discovery job failing to run SNMP portion has been resolved. 73315
A propagation issue where when setting the Automatic Workstation Disconnection does not occur on all devices has been resolved.
74788
DeepLinkActions URLs causing all future navigation to use the same default tab when opening a new device has been resolved.
74007
An issue where the incorrect MAC address was provided in an export to ConnectWise has been resolved.
72465
During upgrade, an issue with the Static IP having changed has been resolved. 74388
VMware temperature service issue where it was stale in some cases has been resolved. 74622
Customer User account could not acknowledge alerts via bulk-action method and has been resolved.
74103
An issue where the LDAP timeout was not significant enough to get a response has been resolved.
73550
5
Description Bug
An issue where the Preview Report does not allow opening via PDF has been resolved. 72983
Update Warranty connection was failing and is now resolved. 74635
An issue where the OS displayed incorrectly for Microsoft Windows 8.1 has been resolved. 74828
Connectivity for devices showing failed but actually they are connected and not monitoring. The issue has been resolved.
69058
An issue where the filters for one Service Organization can also be seen by other Service Organizations has now been resolved.
73563
An upgrade message was added to warn the user that an upgrade to the current running version has already occurred. Resolved by version checking in upgrade.
72616
An issue where Asset information for Printer Port displays ‘0’ instead of the information from the database has been resolved.
74648
Probes were not upgrading to the latest version due to an association with AV Defender tasks that were in progress.
74107
An issue where the ‘Enable Direct Support’ functionality was not enabled but the correct license mode (Professional) was listed.
73595
A problem when sometimes a proxy exists in an environment and blocks communication to the probe/agents has been resolved. The problem occurred and required an update to the configuration file for the Agent to connect.
72631
When adding, with the public API, Enable Warranty Export was not inheriting the setting from the parent on Service Organization/Customer.
74430
Internet Explorer 11 was not parsing the N-central Login User Interface correctly and an update to the libraries were needed.
73608
An issue where the Notification trigger for monitoring a service was not saved and has been resolved.
74434
An issue, in Mobile Devices, occurred where a System Error was provided when clicking on the Sample .csv in the Mobile Device invite User Interface has now been resolved.
74723
An issue where updating the device class provided a System Error to the user has been resolved.
73934
System Error ID given when clicking on a Device has been resolved. 73454
An issue where logs were showing passwords in plain test in the Probe has been resolved. 75227
Self-Healing action on the Widows Service “AppAssure Agent Service” was set to retry but only verified once and notification sent of failure without retrys. This issue has been resolved.
72640
An issue where the N-central Executive Summary report populates with Notification sent information when it is not selected has been resolved.
74936
A problem where there is a rule associated with a device but the filter does not apply to it has been resolved.
71108
An issue where a special character in the Login Name Label on branding caused the Login page login credentials section to not render and has now been resolved.
74186
Windows license key listed in the Asset Operating System widget has been added back into 73686
6
Description Bug
N-central.
An issue with Certificate Generation has been resolved. 72932
A string tokenization loop in EDFSubmit method has been resolved. 73404
A System Error notification when clicking on a device in the UI has been resolved. 74436
An issue where a System Error is thrown in the UI when accessing Add or Delete tasks has been resolved.
74926
A problem where when trying to update the Agent/Probecredentials at the Customer Level Administrator, the user is presented with a System Error. This is resolved.
75309
A System Error when manually creating a device issue has been resolved. 75074
An issue where reboot message does not always reboot due to faulty branding logo has been resolved.
73768
Low XMPP session was reported due to IPv6 and has been resolved. 75115
An issue where exception handling for N-central server has been updated. 70096
An issue where HTTP-XML notifications were not being sent has been resolved. 73049
An upgrade failure has been resolved. The BackupRestore during upgrade was causing failures as the logging was not being ignored.
74726
An issue where in older versions it was possible to filter for a device by device version and was not possible in version 10.
75127
A problem where the Web Server was exposing internal IP addresses through its HTTP headers has now been resolved.
73977
HTTP XML Notification method was not sending the notifications. 69450
The filter "Devices without PowerShell v2" does not return devices without a version of PowerShell reported.
73267
An issue where on changing the OS of the Thin Client throws SYSTEM ERROR has been resolved.
75101
ServerUI:deviceConfigDowntime causing deadlock in agent has been resolved. 72598
An issue where the export was failing due to timeout limit being reached has been resolved. 73350
Notification shows primary notification recipient at SO level but not at Customer level 74105
When NTR was not available login to N-central was being halted. This issue has been resolved.
73902
An issue where Autodesk license keys were not updated in the license keys configuration file has been resolved.
72749
An issue where missing data from graphs for ESXI guests occurred has now been resolved. 74438
Clarification on error messaging when there is not sufficient available space on the backup partition.
74725
An issue where an Acknowledgement emails were not sent has been resolved. 71347
7
Description Bug
Clicking on a mobile device just processes a page with a spinning wheel when there is a special character in the device name.
74244
An issue where Data Export is failing from N-central to Report Manager has been resolved. 74538
Exports are not completing and stopping on the NotificationLog has been resolved. 73468
Process lsass.exe was not found despite it being listed in Direct Support. 74999
Patch Management Description Bug
A problem where the cim_patch table was not updating for newly discovered devices that were unmanaged has been resolved.
72845
Missing Patches (Summary) report not showing patches Installed With Errors. 73462
An issue where for newly discovered devices that were unmanaged the cim_patch variable was not being updated, has now been resolved.
72845
A Mixed status was being shown when patches were declines with the option to apply to children and after a re-evaluate the device levels.
75358
A problem where probe Server was not able to download patches due to proxy requiring Authentication.
72840
An issue where Missing Patches (Summary) report was not showing patches “Installed With Errors” has been resolved.
73462
Manually declined patches re-approving automatically has been resolved. 73745, 73120
PSA Integration Description Bug
A problem where the Submit Queue and PSA Queue were in deadlock has been resolved. 75192
An issue where ticket creation should be noted on the N-central notes tab where the ticket was created offline and was not updated in ConnectWise has been resolved.
73472
Autotask ticket not mapped to a device class and therefore not able to export. The issue was resolved by creating the ticket to the customer and not the device.
74942
An issue where an export profile shows failed devices from another SO has been resolved. 73345
An error where under PSA Integration – Mapping Customers, was showing an error in communication and could not retrieve the Customer list has been resolved.
72988
An issue where Help Desk Manager ticket was not created when a service failed as per the ticketing recipient profile forcing to close the ticket manually has been resolved.
74712
When adding a new or editing a ticketing recipient, the Service item drop down stays empty 74921
8
Description Bug
and after synchronizing shows ‘—‘
A System Error was provided when running an ‘Export Now’ on Autotask Export Devices profile. This issue has been resolved.
74724
Remote Control Description Bug
An edge case deadlock in RemoteControlTaskAdd.submitSSHConfigData() has been resolved.
72634
After an upgrade, devices were changed to RSM remote control as default. 73672
An issue where changing the default Device Remote Control to another does not propagate correctly has been resolved.
72378
A problem where Remote Control via SSH was not sending the SSH username has been resolved.
73696
An issue where User accounts with Attended Remote Control permission was unable to log into N-central has now been resolved.
74166
Service Templates Description Bug
An issue where the thresholds for Windows Server Clock Drift could not be changed has been resolved.
75013
An issue where Citrix Archive Backup is misconfigured in the Veeam Job Monitor has been resolved.
73461
A problem where Service template was failing to apply due to no asset information has been resolved.
74744
Service Template problem where it was not being applied to a device has been resolved. 73525
Importing custom services stripped the OID from the SNMP query leaving the value as NULL in the UI. This was resolved by having the value rendered correctly.
73020
When trying to create a Service Template at the device level, an error that the Service does not have a unique Service identifier was received. This issue has been resolved.
70124
Services Description Bug
An issue where running a custom AMP for monitoring Windows Server 2008 throws a LatErrorDescriptionStsus unknown error has been resolved.
72985
9
UI Description Bug
An issue where the scroll bar was missing on the Scheduled Reports Page has been resolved. 74423
A problem where TeamViewer password lock was not locking has been resolved. 74897
An issue where the Backup Exec does not allow you to select options other than the default has been resolved.
73956
Filter columns were fixed. This issue has been resolved by allowing the column widths to be adjusted.
73989
Known Limitations
Active Issues Description Bug
When exporting a large list of Active Issues items to PDF format at either the System or Service Organization level, the server may fail. Exporting to CSV format does not cause this problem.
62860
Agents and Probes Description Bug
An issue with the deprecation of support for SSL v3 may cause the upgrading of Linux 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 N-central online help.
71680
Communication issues may be encountered for N-central Probes installed on Windows servers that have multiple NICs. For more information, refer to "KBA20020: Configuring A Server With Multiple NICs" in the N-central online help.
67778
Automation Manager Description Bug
Running Automation Manager Policies created using Automation Manager 1.6 or earlier may result in Failed to create an '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.
65712
Backup Manager Description Bug
ShadowProtect Data Reader service is using high CPU due to large amount of historical data as part of the backup.
74971
N-central 10.0 supports CA ARCserve D2D R17 but that version of D2D does not support Windows XP.
68435
10
Description Bug
The About Backup Manager dialog box no longer indicates whether or not the Backup Manager software is licensed.
68226
Custom Services Description Bug
Custom services may appear as misconfigured when the system locale of the device is not 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 Technical Support.
65288
Dashboards Description Bug
Modifying a Dashboard that is associated with a large number of services may cause performance issues when using the Firefox browser.
70326
N-central Server Description Bug
With the complete removal of support for Security Manager - Endpoint Security as of December 31, 2014, upgrading to N-central 10.0 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.0 to succeed. For more information, refer to "KBA91005: Preventing Failed Upgrades to N-central 10.0" in the N-central online help.
73491
This issue has been resolved. Please review "KBA70003: Direct Connect failure to connect" in the online help. Chrome 42.x does not support NPAPI plugins which means that Java and DirectConnect 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.
Java and DirectConnect should now function properly.
73359
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 as the default community string ("public") is no longer valid. For more information, refer to "SNMP Community String" in the Software Requirements section of these Release Notes.
n/a
11
Patch Management Description Bug
If the device with the N-central Probe is using a version of Windows 2003 that does not 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.
68390
Configuring automatic Third Party software patch approval for devices that use Windows XP® 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.
62277
Microsoft Security Bulletin MS14-045 announced the withdrawal of four individual Windows updates due to security issues. This security bulletin applies to:
• Windows RT and Windows RT 8.1 • Windows Server 2012 and Windows Server 2012 R2, • Windows 8 and Windows 8.1, • Windows Server 2008 and Windows Server 2008 R2, • Windows 7, • Windows Vista, and, • Windows Server 2003.
The following updates were withdrawn: • 2982791, • 2970228, • 2975719, and, • 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.
67830
It is strongly recommended that your Update Server not be a device that requires uninterrupted disk access (for example, an Exchange server or a web server) as update functionality can be disk-intensive.
n/a
PSA Integration Description Bug
In some instances, tickets closed in PSAs are not being cleared in N-central. This is likely 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.
65620
UI Description Bug
Product Key Card versions do not get picked up by the License Key Inventory. As 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 storing the Product Key in the registry.
61453
12
Description Bug
System errors or timeout errors may prevent very long lists of domain users from being displayed properly in the Domain User Management screen.
NID-63
When displaying Services in the Tools tab, the Click to try again feature to refresh the service display may not function properly when using Internet Explorer 9 or Internet Explorer 10.
70965
After re-naming, the Names of files or Registry entries may not be displayed properly in the File System window and the Registry window of the Tools tab when using Internet Explorer.
68149
13
Hardware Requirements For the minimum hardware requirements for the N-central 10.0 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:
• RAM: 512 MB • Disk space: 500 MB • 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 Number
PORT LOCATION Description
N-central Server Managed Device
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.
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-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.
14
Port Number
PORT LOCATION Description
N-central Server Managed Device
Inbound Outbound Inbound Outbound
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. Port 443 is the TCP port needed for SSL (HTTPS) connections. The firewall must be configured to allow access from the Internet 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 managed 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.
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 notifications to APNS servers at gateway.push-apple.com.akadns.net.
2196 Used to send Mobile Device Management notifications 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 control 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 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
15
Port Number
PORT LOCATION Description
N-central Server Managed Device
Inbound Outbound Inbound Outbound
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 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:
• 80 • 443 • 2195 • 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:
• 443 (TCP) • 5222 (TCP) • 5223 (TCP) • 5228 (TCP and UDP)
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 DirectConnect remote control sessions will not function properly. The N-central server and Windows Probes must be able to resolve the following domain name:
• sis.n-able.com
The N-central server must be able to resolve (and access using port 443) the following domain names:
• update.n-able.com • feed.n-able.com • servermetrics.n-able.com • push.n-able.com • scep.n-able.com • licensing.n-able.com
16
• updatewarranty.com • apieu.ntrglobal.com • microsoft.com
For Third Party Patch Management to function properly, your network firewall must be configured to allow access to the following web sites:
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 Probe • Server In The Sky (SIS) - http://sis.n-able.com • Adobe Acrobat - http://ardownload.adobe.com • Adobe Reader - ftp://ftp.adobe.com/ • Adobe Air - http://airdownload.adobe.com/ • Apple Products - https://secure-appldnld.apple.com • Flash - http://download.macromedia.com/ • Foxit - http://cdn01.foxitsoftware.com/ • Google Products - https://dl.google.com • Java - http://javadl.sun.com/ • Mozilla Products - https://download-installer.cdn.mozilla.net • Notepad++ - http://download.tuxfamily.org/ • Opera - http://get.geo.opera.com/ • Shockwave - http://www.adobe.com/ • Skype - http://download.skype.com/ • WinRAR - http://www.rarlab.com/ • WinZip - http://download.winzip.com/ • VLC - http://download.videolan.org/
Device with Agent • 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 • Server In The Sky (SIS) - http://sis.n-able.com • Adobe Acrobat - http://ardownload.adobe.com • Adobe Reader - ftp://ftp.adobe.com/ • Adobe Air - http://airdownload.adobe.com/ • Apple Products - https://secure-appldnld.apple.com • Flash - http://download.macromedia.com/ • Foxit - http://cdn01.foxitsoftware.com/ • Google Products - https://dl.google.com • Java - http://javadl.sun.com/ • Mozilla Products - https://download-installer.cdn.mozilla.net • Notepad++ - http://download.tuxfamily.org/ • Opera - http://get.geo.opera.com/ • Shockwave - http://www.adobe.com/ • Skype - http://download.skype.com/ • WinRAR - http://www.rarlab.com/ • WinZip - http://download.winzip.com/ • VLC - http://download.videolan.org/
17
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.
Software Requirements
Supported Platforms and Browsers N-central is supported on the following browsers:
• Internet Explorer®, versions 10.x and later • Mozilla Firefox®, versions 35.x and later • Google Chrome®, versions 40.x and later
Notes
• Chrome 42.x does not support NPAPI plugins which means that Java and DirectConnect 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.
Java and DirectConnect should now function properly.
• N-central is not supported on Internet Explorer in Compatibility View mode.
• Attended Remote Control and DirectConnect remote control connections are not supported on 64-bit browsers.
Agents and Probes Microsoft .NET Framework To function on a managed device, N-central Agents require the following versions of Microsoft .NET Framework to be installed:
• Microsoft .NET Framework 2.0.50727 (or later), and, • Microsoft .NET Framework 4.0.x.
Agents will not function properly on devices that only have Microsoft .NET Framework 4.0.x installed.
.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).
18
Supported Mobile Device Operating Systems N-central's Mobile Device Management supports the following:
• iOS 6.1.x and later • 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:
• Java 6 Update 20 or greater
Report Manager If using Report Manager, you must upgrade to Report Manager 4.3 SP1 or later after upgrading to N-central 10.0.
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.
Upgrading to This Release To upgrade, your N-central server must be running one of the following versions:
• For N-central 10.0.x, build 10.0.0.1685 and later. • For N-central 9.5.1, build 9.5.1.243 and later.
Advisory Notices
Warning! If you are using Backup Manager, please note that this version does not certify Windows 10 support at time of this release.
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 Community > 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).
19
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).
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 (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 SolarWinds N-able Technical Support at 1-877-655-4689, by email at [email protected] , or by accessing the self service portal at http://support.n-able.com.
20
Review the following checklist before proceeding with upgrading to this release.
Category Notice Reviewed
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]. To manually configure the Enable Direct Support option, refer to "Properties" in the N-central online help.
Agents Mac and Linux® Agents can only be upgraded automatically if they are of the following versions:
• Mac Agent - 9.0.0.84 or later • 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. 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 Manager
An issue with N-central 10.0 prevents the AV Status service from being added to devices that use Essential Mode licenses.
Security Manager
With the complete removal of support for Security Manager - Endpoint Security as of December 31, 2014, upgrading to N-central 10.0 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.0 to succeed. For more information, refer to "KBA91005: Preventing Failed Upgrades to N-central 10.0" in the N-central online help.
You can upgrade to N-central 10.0 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.
21
Upgrade Procedure You must perform the following to upgrade to N-central 10.0:
Step One: Backing Up the N-central Server on page 21 Step Two: Installing the N-central 10.0 Upgrade on page 23 Step Three: Post-installation Steps on page 25
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 Data
Select this check box to include historical data in the backup. This 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 And Script Repository Data
Select this check box to include the software and script repository data in the backup.
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
Type Select the type of schedule for regularly performing the database backup from one of the following options:
• Off • Daily • Weekly • Monthly
Start Time The time at which the backup will be started.
Days of the Week
The weekdays on which the backup will be performed. Note: This option is only available for Weekly backups.
Days of the Month
The specific dates on which the backup will be performed. Note: This option is only available for Monthly backups.
22
Backup Destination FTP Server
Upload copy of Backup to FTP Server.
Enables the uploading of copies of the backup file to an FTP server.
Keep Previous Backup Archive
Retains existing backup files stored on the FTP server.
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/
23
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 Email Address
The email address from which the notification will be sent.
Recipient Email Address
The email address to which the notification will be sent.
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.
Step Two: Installing the N-central10.0 Upgrade You can upgrade to N-central 10.0 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.
24
To install the downloaded N-central 10.0 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 from local repository.
b. Select the upgrade File.
Example 10.0.0.xxx
a. Select Install upgrade remotely.
b. Specify the Location of the system upgrade file or click Browse to navigate to the file.
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.
25
Step Three: Post-installation Steps After you have installed N-central 10.0, 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-10.0.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.
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
software 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
software 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.
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:
26
Check items as they are completed
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:
• Upgrade Agent • Upgrade Remote Support Manager • 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:
• Reports >Administrative > Remote Support Manager
• Reports >Status > AV Defender 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.
Rebuilding or Migrating Your N-central Server There may be circumstances in which you need to rebuild or migrate your N-central server:
• your N-central server is not functioning properly or starting successfully, • an upgrade has failed but you can still log in to N-central • 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/.
27
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. SolarWinds N-able Technical Support can confirm the version of N-central that last communicated with SolarWinds N-able if your server is not functioning properly or cannot 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 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 "System Restore" in the N-central online help.
5. When the system restore is completed, please contact SolarWinds N-able to have your N-central server activated. For more information refer to "Activating N-central" in the N-central Installation Guide.
28
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.
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 "System Restore" in the N-central online help.
5. When the system restore is completed, please contact SolarWinds N-able to have your N-central server activated. For more information refer to "Activating N-central" in the N-central Installation Guide.
29
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:
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
30
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 "System Restore" in the N-central online help.
5. When the system restore is completed, please contact SolarWinds N-able 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 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/.
Platform Support
Supported Operating Systems for Agents
Microsoft Windows (WindowsAgentSetup.exe) Microsoft .NET Framework To function on a managed device, N-central Agents require the following versions of Microsoft .NET Framework to be installed:
• Microsoft .NET Framework 2.0.50727 (or later) • 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® 2012
• Microsoft Windows Server 2012 R2 Datacenter • Microsoft Windows Server 2012 R2 Datacenter 64-bit Edition • Microsoft Windows Server 2012 R2 Essentials • Microsoft Windows Server 2012 R2 Essentials 64-bit Edition • Microsoft Windows Server 2012 R2 Foundation • Microsoft Windows Server 2012 R2 Foundation 64-bit Edition • Microsoft Windows Server 2012 R2 Standard • Microsoft Windows Server 2012 R2 Standard 64-bit Edition • Microsoft Windows Server 2012 Datacenter 64-bit Edition • Microsoft Windows Server 2012 Essentials 64-bit Edition • Microsoft Windows Server 2012 Foundation 64-bit Edition • Microsoft Windows Server 2012 Standard 64-bit Edition • Microsoft Windows Storage Server 2012 Enterprise 64-bit Edition • Microsoft Windows Storage Server 2012 Express 64-bit Edition • Microsoft Windows Storage Server 2012 Standard 64-bit Edition • Microsoft Windows Storage Server 2012 Workgroup 64-bit Edition
Windows Server 2008 • Microsoft Windows 2008 • Microsoft Windows 2008 Datacenter Server • Microsoft Windows 2008 Datacenter Server without Hyper-V • Microsoft Windows 2008 Datacenter Server without Hyper-V 64-bit Edition • Microsoft Windows 2008 Datacenter Server 64-bit Edition • Microsoft Windows 2008 Enterprise Server • Microsoft Windows 2008 Enterprise Server without Hyper-V • Microsoft Windows 2008 Enterprise Server without Hyper-V 64-bit Edition
31
• Microsoft Windows 2008 Enterprise Server 64-bit Edition • Microsoft Windows 2008 Essential Business Server • Microsoft Windows 2008 Essential Business Server 64-bit Edition • Microsoft Windows 2008 Foundation Server • Microsoft Windows 2008 HPC Server • Microsoft Windows 2008 R2 Datacenter Server • Microsoft Windows 2008 R2 Enterprise Server • Microsoft Windows 2008 R2 Foundation Server • Microsoft Windows 2008 R2 Standard Server • Microsoft Windows 2008 R2 Web Server • Microsoft Windows 2008 Small Business Server • Microsoft Windows 2008 Small Business Server 64-bit Edition • Microsoft Windows 2008 Standard Server • Microsoft Windows 2008 Standard Server without Hyper-V • Microsoft Windows 2008 Standard Server without Hyper-V 64-bit Edition • Microsoft Windows 2008 Standard Server 64-bit Edition • Microsoft Windows 2008 Web Server • 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.
• The operating system must be Windows Server 2008 R2 Server Core 64-bit Service Pack 1 or later.
• .NET Framework 4 for Server Core (64-bit) must be installed. • .NET Framework 2 must be enabled using the command: start /w ocsetup NetFx2-
ServerCore-WOW64
Windows Server 2003 • Microsoft Windows Storage Server 2003 R2 • Microsoft Windows Server 2003 • Microsoft Windows Server 2003 for Small Business Server • Microsoft Windows Server 2003 for Small Business Server 64-bit Edition • Microsoft Windows Server 2003 SP1 • Microsoft Windows Server 2003 64-bit Edition • Microsoft Windows Server 2003 Web Edition
Windows Server 2000 • Microsoft Windows 2000 Advanced Server • Microsoft Windows 2000 Data Center • Microsoft Windows 2000 Professional • Microsoft Windows 2000 Server • 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 • Microsoft Windows Hyper-V Server 2008 • Microsoft Windows Hyper-V Server 2008 R2 • Microsoft Windows Hyper-V Server 2012 64-bit Edition
32
Windows 8 • Microsoft Windows 8.1 Enterprise • Microsoft Windows 8.1 Enterprise 64-bit Edition • Microsoft Windows 8.1 Professional • Microsoft Windows 8.1 Professional 64-bit Edition • Microsoft Windows 8 Enterprise • Microsoft Windows 8 Enterprise 64-bit Edition • Microsoft Windows 8 Professional • Microsoft Windows 8 Professional 64-bit Edition • Microsoft Windows 8 64-bit Edition
Windows 7 • Microsoft Windows 7 Enterprise • Microsoft Windows 7 Enterprise 64-bit Edition • Microsoft Windows 7 Home Basic • Microsoft Windows 7 Home Premium • Microsoft Windows 7 Professional • Microsoft Windows 7 Professional 64-bit Edition • Microsoft Windows 7 Ultimate • Microsoft Windows 7 Ultimate 64-bit Edition
Windows Vista® • Microsoft Windows Vista Business • Microsoft Windows Vista Business 64-bit Edition • Microsoft Windows Vista Enterprise • Microsoft Windows Vista Enterprise 64-bit Edition • Microsoft Windows Vista Home • Microsoft Windows Vista Home 64-bit Edition • Microsoft Windows Vista Ultimate • Microsoft Windows Vista Ultimate 64-bit Edition
Windows XP • Microsoft Windows XP • Microsoft Windows XP Embedded • Microsoft Windows XP Home • Microsoft Windows XP Professional • Microsoft Windows XP Professional 64-bit Edition • Microsoft Windows XP Tablet PC Edition
Other Windows versions
• Microsoft Windows NT 4.x 32-bit • Microsoft Windows NT Server • Microsoft Windows Embedded Standard • Microsoft Windows Home Server 2011 • Microsoft Windows Small Business Server 2011 • Microsoft Windows Storage Server 2003 R2 • 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.
33
Red Hat® Enterprise/CentOS Linux nagent-rhel_64.tar.gz • CentOS 5 64-bit Edition
• CentOS 6 64-bit Edition • CentOS 7 64-bit Edition • RedHat Enterprise Linux 5 64-bit Edition • RedHat Enterprise Linux 6 64-bit Edition • RedHat Enterprise Linux 7 64-bit Edition
nagent-rhel.tar.gz • CentOS 5 32-bit Edition • CentOS 6 32-bit Edition • CentOS 7 32-bit Edition • RedHat Enterprise Linux 5 32-bit Edition • RedHat Enterprise Linux 6 32-bit Edition • RedHat Enterprise Linux 7 32-bit Edition
Mac® OS X® Agent OSXAgent.tar.gz • Apple Mac OS X 10.10 Server
• Apple Mac OS X 10.10 • Apple Mac OS X 10.9 Server • Apple Mac OS X 10.9 • Apple Mac OS X 10.8 Server • Apple Mac OS X 10.8 • Apple Mac OS X 10.7 Server • Apple Mac OS X 10.7 • Apple Mac OS X 10.6 Server • Apple Mac OS X 10.6
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 • Microsoft Windows XP SP3 • Microsoft Windows Vista SP1 • Microsoft Windows 7 • Microsoft Windows 8 • Microsoft Windows 8.1
Tablet and Embedded Operating Systems • Windows XP Tablet PC Edition • Windows XP Embedded SP2 • Windows Embedded Standard 2009 • Windows Embedded POSReady 2009 • Windows Embedded Enterprise 7 • Windows Embedded POSReady 7 • Windows Embedded Standard 7
Server Operating Systems • Microsoft Windows 2003 Server SP1 • Microsoft Windows Server 2003 for Small Business Server • Microsoft Windows Storage Server 2003 R2
34
• Microsoft Windows Server 2003 SP1 • Microsoft Windows 2008 • Microsoft Windows 2008 Server • Microsoft Windows 2008 R2 • Microsoft Windows Small Business Server 2011 • Microsoft Windows Home Server 2011 • Microsoft Windows 2012 Server • 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:
• 32-bit edition of Windows XP • 32-bit and 64-bit editions of Windows Vista • 32-bit and 64-bit editions of Windows 7 • 32-bit and 64-bit editions of Windows 8
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 Type
Remote System
Technician Remote System
Technician Remote System
Technician
Attended Remote Control1
DirectConnect1
Generic
Remote Desktop 2
Remote Support Manager
3
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.
35
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:
N-central Version CA ARCserve D2D Version Already Installed
N-central 9.0 SP1 and later Note: After integration with this version of N-central, the CA ARCserve D2D software will automatically be upgraded to R16 Update 6.
R16
R16 Update 1
R16 Update 2
R16 Update 3
R16 Update 4
R16 Update 6
N-central 8.2 to N-central 9.0 Note: After integration with these versions of N-central, the CA ARCserve D2D software will automatically be upgraded to R16 Update 4.
R16
R16 Update 1
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:
Operating System Operating System Variant
Microsoft Windows Server 2012 • Foundation • Essentials • Standard • Datacenter
Microsoft Windows 7 • Ultimate (32-bit and 64-bit) • Enterprise (32-bit and 64-bit) • Professional (32-bit and 64-bit) • Home Premium (32-bit and 64-bit) • Home Basic (32-bit) • Starter edition (32-bit)
Microsoft Windows Vista • Ultimate (32-bit and 64-bit) • Home Basic (32-bit) • Home Premium (32-bit and 64-bit) • Business (32-bit and 64-bit) • Enterprise (32-bit and 64-bit)
36
Operating System Operating System Variant
Microsoft Windows Server 2008 R2 • R2 Enterprise (64-bit) • R2 Standard (64-bit) • R2 Datacenter (64-bit) • R2 Web Server (64-bit) • R2 Server Foundation (64-bit) • R2 Core (64-bit) • R2 Storage Server (64-bit)
Microsoft Windows Server 2008 • Enterprise (32-bit and 64-bit) • Standard (32-bit and 64-bit) • Datacenter (32-bit and 64-bit) • Web Server (32-bit and 64-bit) • Storage Server (32-bit and 64-bit) • Core (32-bit and 64-bit) • Server Foundation (64-bit) • Windows Server 2008 Hyper-V (64-
bit) – physical only • Windows Server 2008 R2 Hyper-V
(64-bit) – physical only • Windows Small Business Server 2008
(SBS 2008) • Windows Small Business Server 2011
(SBS 2011)
Microsoft Windows XP
Warning! CA ARCserve D2D R17 does not support Windows XP.
• Professional (32-bit and 64-bit) • Home Edition (32-bit)
Microsoft Windows Server 2003 R2 • R2 Enterprise Edition (32-bit and 64-bit)
• R2 Standard Edition (32-bit and 64-bit)
Microsoft Windows Server 2003 Service Pack 1 or Service Pack 2
• Enterprise Edition (32-bit and 64-bit) • Standard Edition (32-bit and 64-bit) • Web Edition (32-bit and 64-bit) • Datacenter (32-bit and 64-bit) • Storage Server R2 • Windows Small Business Server R2
37
Supported Applications for Recovery Backup Manager also supports the following for application recovery:
Application Application Variant
Microsoft Exchange Server
• Microsoft Exchange Server 2003 Service Pack 1 or Service Pack 2 Standalone
• Microsoft Exchange Server 2007 Standalone or Cluster Continuous Replication (CCR) configuration
• Microsoft Exchange Server 2010 Standalone or Database Availability Group (DAG) configuration
Microsoft SQL Server • Microsoft SQL Server 2005 Express, Standard, Workgroup, or Enterprise
• Microsoft SQL Server 2008 Express, Web, Standard, Workgroup, or Enterprise
• 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.
Disk (Volume) Type As Backup Source
As Backup Destination
Bare Metal Recovery Support
Data Volume
System and boot volume
GPT Disk 1
System Reserved Partition (Windows 2008 R2 Boot Manager)
1 n/a
Mounted Volume (No drive letter/NTFS formatted)
RAW Volume (No drive letter/Not formatted)
VHD Mounted Volume (Windows 2008 R2)
2
Dynamic Disk
No RAID 3
Software RAID
RAID-0 (Stripe)
RAID-1 (Mirrored)
RAID-5
Hardware RAID (Include Embedded RAID)
38
Disk (Volume) Type As Backup Source
As Backup Destination
Bare Metal Recovery Support
Data Volume
System and boot volume
File System Format
FAT/FAT32 4
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 one or more devices open the following link to troubleshooting instructions: http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=3138
39
Licensing and Support Information
Agent/Probe Installation Software N-central 10.0 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/ © 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.
