If you upgrade from 5.4.0 or earlier, Enterprise Console may have problems communicating with computers running older versions of Sophos Remote Management System. See knowledgebase article 124873 .

Note:

Note: If you are upgrading from Enterprise Console 5.0, 5.1, 5.2.0, 5.2.1, 5.2.1 R2, 5.2.2, 5.3.0,

5.3.1, 5.4 or 5.4.1, changes to the database component are required. For more information, go to knowledgebase article 125687

Note: If you want to upgrade the Sophos databases manually by running the database install scripts, see knowledgebase article 116768 .

If you are using Enterprise Console 4.x or Enterprise Manager 4.7, you will need to upgrade in two steps: first upgrade to Enterprise Console 5.1 and then upgrade to Enterprise Console 5.4.1.

If you are using Sophos Control Center 4.0.1 or 4.1, you will need to upgrade in two steps by following one of the supported upgrade paths:

■

Upgrade to Enterprise Console 5.1 and then upgrade to Enterprise Console 5.5.

Upgrade to Enterprise Console 5.2.2 and then upgrade to Enterprise Console 5.5.

Note: Alternatively, you could use Sophos Central to manage your computers. To find answers to frequently asked questions about Sophos Central, see knowledgebase article 119598 . For information about migration to Sophos Central, see knowledgebase article 122264 .

See also knowledgebase article 119105 for more information about different upgrade paths.

The installers for earlier versions of Enterprise Console are available from the Sophos Enterprise

Console Downloads page

( http://www.sophos.com/en-us/support/downloads/console/sophos-enterprise-console.aspx

upgrade guide

Do I need to upgrade the databases separately?

If your databases are local (on the same computer as the management server component), they will be upgraded automatically when you follow the steps in this guide.

If your databases are on a remote or clustered SQL Server, you must upgrade them first. If you're upgrading from Enterprise Console 5.2.1 or later, see knowledgebase article 33980 . If you're upgrading from an earlier version and want to upgrade the Sophos databases manually by running the database install scripts, see knowledgebase article 116768 .

Unix endpoints

You may need to upgrade Sophos Anti-Virus on managed UNIX endpoints after you upgrade to

Enterprise Console5.5.

Sophos Enterprise Console

3 Sophos Disk Encryption

There is no upgrade for Sophos Disk Encryption 5.61. The product has been retired. If you use

Sophos Disk Encryption and manage it via the Full disk encryption policy in Enterprise Console, we recommend that you do one of the following:

■ Upgrade Sophos Disk Encryption to SafeGuard Enterprise 6.10.

Note: A direct upgrade to SafeGuard Enterprise 7 is not supported.

■ Uninstall Sophos Disk Encryption.

3.1 Upgrade Sophos Disk Encryption 5.61 to SafeGuard

Enterprise

Migration from Sophos Disk Encryption 5.61 to SafeGuard Enterprise 6.10 involves the following steps:

1. Export the SEC company certificate: In Enterprise Console on the Tools menu, click Manage

Encryption and select Backup Company Certificate. Select a destination directory and file name and enter a password for the .P12 file when prompted.

2. Install SafeGuard Management Center and SafeGuard Enterprise Server.

Note: If you have the SEC management server with encryption installed on this server, install

SafeGuard Enterprise on a different server.

For detailed information on SafeGuard Enterprise installation, see the SafeGuard Enterprise

6.1 installation guide. SafeGuard Enterprise documentation is available at www.sophos.com/en-us/support/documentation/safeguard-enterprise.aspx

3. In the SafeGuard Management Center configuration wizard, select a new database to be created and import the company certificate exported before.

4. In SafeGuard Management Center, create the endpoint configuration package: On the Tools menu, click Configuration Packages Tool. Select Managed client packages, make your edits and create the configuration package.

5. Deploy the configuration package to the endpoints. After the endpoints have received it, they are able to connect to SafeGuard Enterprise Server. From that time on, the endpoint can be managed by SafeGuard Management Center.

6. To prevent a communication issue that causes endpoint computers to communicate with both the new SafeGuard Enterprise Server and the old Sophos Enterprise Console, see knowledgebase article 121160 .

7. In SafeGuard Management Center, create and assign policies as desired.

The migrated endpoints remain visible in Enterprise Console as "managed by SafeGuard

Enterprise". All non-encryption related tasks can still be performed on them.

upgrade guide

3.2 Uninstall Sophos Disk Encryption

1. In Enterprise Console, check which full disk encryption policy is used by the group(s) of computers you want to migrate. In the Groups pane, right-click the group and click View/Edit

Group Policy Details. In the group details dialog box, you can see the policies currently used.

2. Open the Full disk encryption policy you want to disable and deselect all the options under

Volumes to encrypt.

3. Under Power-on Authentication (POA), clear the Enable Power-on Authentication check box. Click Yes in the confirmation message. Click OK.

Make sure the updated policy is applied to the endpoints. (In the computer list, the Policy

compliance status changes to “Awaiting policy transfer”, and then back to “Same as policy” when the updated policy is applied to the computers.)

4. On the endpoint, if tamper protection is enabled, disable it.

Note: You can also disable tamper protection in Enterprise Console for a group or groups of computers. In the respective Tamper Protection Policy, clear the Enable tamper protection check box and make sure that the updated policy is applied to the computers.

5. Make sure that an update is not currently being performed.

a) Check the updating status by right-clicking the Sophos shield in the notification area in the taskbar and ensuring that View updating status is grayed out and cannot be selected. If an update is currently in progress, wait for it to complete before continuing.

b) Open Windows services. Depending on your operating system, click Start > Run and type

“services.msc”, or click Start, type “services.msc” in the Start menu search box, and then press Enter.

c) Right-click on the Sophos AutoUpdate Service and select Stop.

Note: Stopping the Sophos AutoUpdate Service prevents an update from occurring during the uninstallation. If the service is not stopped and the uninstallation of Sophos

SafeGuard is delayed for a period longer than the update interval, then Sophos SafeGuard could be re-installed.

6. In Control Panel, depending on your operating system, double-click Add/Remove Programs or click Programs and Features.

7. Uninstall Sophos SafeGuard 5.61.0 Client.

Encrypted drives on the computer are decrypted during the uninstallation.

8. Uninstall Sophos SafeGuard 5.61.0 Preinstall.

9. Restart the computer.

Sophos Enterprise Console

4 Tool version compatibility for Enterprise

Console

The following table shows version compatibility between Enterprise Console tools and Enterprise

Console.

Important: After an upgrade to Enterprise Console 5.5 reinstall Sophos Cloud Migration Tool and Virtualization Scan Controller, and restart the Reporting Log Writer service. This enables these tools to work.

The Enterprise Console tools are available for download from https://www.sophos.com/support/downloads.aspx

Table 1: Tool version compatibility for Enterprise Console

5.5.0

5.4.1

5.4.0

5.3.1

5.3.0

5.2.2

5.2.1 R2

5.2.1

5.2

5.1

Enterprise Console Reporting Interface

5.1*

5.1

Reporting Log Writer Virtualization Scan Controller

2.0

1.0

2.0

* Since version 5.1, Reporting Interface database objects are installed as part of the Enterprise

Console database installation, and the standalone installer on the Sophos Reporting Interface download page includes only Reporting Log Writer.

Important: If you installed Reporting Interface separately with an earlier version of Enterprise

Console, uninstall it before upgrading that version.

5 What are the steps in upgrading?

Upgrading involves the following steps.

■ Check the system requirements.

■

Check the accounts you need.

Check whether you need to change your software subscriptions.

■

Download the installer.

Upgrade Enterprise Console.

upgrade guide

Sophos Enterprise Console

6 System requirements

.NET Framework installation

The installer installs .NET Framework 4.5.2, unless version 4.x is already installed.

Important: As part of the .NET Framework 4.5.2 installation some system services (such as IIS

Admin Service) may restart.

After .NET Framework 4.5.2 is installed, you may receive a message asking you to restart your computer. If you do, we recommend that you restart the computer immediately or shortly after the installation.

For a full list of system requirements, see the system requirements page of the Sophos website http://www.sophos.com/en-us/products/all-system-requirements.aspx

6.1 Free disk space requirements

The amount of free disk space you need to upgrade Enterprise Console depends on the size of the Enterprise Console database files (.mdf files) and transaction log files (.ldf files) that are currently in use.

Tip: The file names begin with "SOPHOS" and usually contain Enterprise Console version number.

For information about the database file names for different console versions and how to locate the database files on disk, see Sophos knowledgebase article 17323 .

To ensure that you have sufficient disk space to upgrade Enterprise Console, do the following:

■

Check the disk drive on which the database files (.mdf files) are deployed and ensure that it has free capacity of at least three times the current size of the .mdf files.

Check that the disk drive on which the transaction log files (.ldf files) are deployed and ensure that it has free capacity of at least eight times the current size of the database files (.mdf files).

■ If both .mdf and .ldf files are deployed on the same disk, ensure that it has free capacity of at least 10 times the current size of the .mdf files.

If you have upgraded Enterprise Console in the past, you may still have old Enterprise Console databases that are no longer required. You may consider deleting those databases to free up disk space. For more information, see Sophos knowledgebase article 17508 .

upgrade guide

7 The accounts you need

Accounts required to perform the upgrade

Ensure that the user logged on to and running the upgrade on the management server has sufficient rights to all Sophos databases. The user running the management server upgrade should be a member of the "db_owner" role on each of the Sophos databases (members of the server role "sysadmin" would implicitly have sufficient rights to all databases). These rights are only required temporarily during the upgrade, to check that the new databases have been created and to migrate the data.

Note: For a list of database names per version of the console, see Sophos knowledgebase article

17323 .

Sophos database account

When you upgrade your management console, you might be asked for details of a database account. This happens if your existing account no longer meets the requirements.

Ensure you have an account that:

■ Can log onto the computer where the management console is installed. For distributed installations of Enterprise Console, the account must be able to log onto the computer where the Sophos Management Server component is installed.

■

Can read and write to the system temporary directory e.g. "\windows\temp\". By default, members of "Users" have this right.

Has a UPN (User Principal Name) associated with the account if it is a domain account.

All other rights and group memberships that the account needs are granted automatically during the upgrade.

Sophos recommends that the account:

■ Is not set to expire and does not have any other logon restriction.

■

Is not an administrative account.

Is not changed after the upgrade.

For more information, see Sophos knowledgebase article 113954 .

Sophos Enterprise Console

8 Will I get the same updates as before?

Since version 5.2.1, Enterprise Console supports new options for getting your automatic updates from Sophos and doesn't support some of the old ones. If you are upgrading from an earlier version, depending on the software packages you selected when you installed Enterprise Console, you may need to change your software subscription settings before you upgrade.

To open an endpoint software subscription, on the View menu, click Update Managers. In the

Software Subscriptions pane, double-click the subscription you want to check.

To open an update manager software subscription, in the Update managers view, double-click the update manager you want to check. In the Configure update manager dialog box, go to the

Advanced tab.

The following matrix shows whether you can or cannot upgrade with your current settings.

Table 2: Upgrading with different software subscriptions

Advice, if applicable Software package Upgrade possible

Endpoint

Recommended (default)

Oldest

Extended Maintenance

Recommended

Yes

Extended Maintenance Previous Yes

Extended Maintenance Oldest No

Yes

Fixed (e.g. 10.3.15 VE3.60.0) Yes

Resubscribe to a different package, for example,

"Previous".

Resubscribe to a different package, for example,

"Extended Maintenance Previous".

Enterprise Console uses fixed packages. For more information, see the Sophos Enterprise Console Help,

Fixed version software packages .

Update Manager

1 Recommended (default)

Preview

Yes

upgrade guide

Software package

Extended

1 Previous

1 Oldest

Fixed (e.g. 1.5.4.11)

Upgrade possible

Yes

Advice, if applicable

Resubscribe to "1 Recommended". For more

information, read About Sophos Update Manager upgrade

(page 13).

If your software package is no longer supported and you don't change your subscription before upgrading, the installer will warn you about the unsupported subscriptions and you won't be able to proceed with the upgrade. For more information about software packages, see Sophos knowledgebase article 112580 .

8.1 About Sophos Update Manager upgrade

Since version 5.2.1, Enterprise Console supports only one, recommended Sophos Update Manager software package. If you are upgrading from a version earlier that 5.2.1, Update Manager (and any additional Update Managers, if you use them) must be subscribed to the "1 Recommended" package. Otherwise, you won’t be able to upgrade.

If you are not subscribed to the "1 Recommended" package, you will need to subscribe to it and ensure that Update Manager has been updated to the latest recommended version before upgrading Enterprise Console.

If the Update Manager installer in the share \\Servername\SUMInstallSet on the computer where Enterprise Console management server is installed is earlier than the latest recommended version, the installer will be updated during the upgrade.

Sophos Enterprise Console

9 Download the installer

Note: You can download the installers at any computer and then copy them to the computer where you will use them.

1. Log in to https://www.sophos.com/en-us/support/downloads.aspx

with your Sophos ID.

Note: If you need help with your Sophos ID, see Sophos knowledgebase article 111195 .

2. If you have logged in for downloads before, you see the Product Downloads and Updates page.

Note: If this is your first time, you see your profile. Click Endpoint and Server Protection and then Downloads and Updates.

3. Under Console, click the link for Sophos Enterprise Console and download the installer.

upgrade guide

10 Upgrade Enterprise Console

10.1 Back up Enterprise Console data and configuration

Before you upgrade Enterprise Console, use the DataBackupRestore.exe tool to back up:

■ Databases: Enterprise Console (core) - SOPHOS5x, Patch - SOPHOSPATCH or

SOPHOSPATCH5x, and Auditing - SophosSecurity.

■

Registry settings

Account information

■ Configuration files

Important: The DataBackupRestore.exe tool will back up the Sophos management server's configuration only from a default installation location. Backing up or restoring the configuration files will fail if you have installed Enterprise Console to a non-default location. The default location is:

■

Windows 64-bit: %programfiles(x86)%\Sophos\Enterprise Console\

Windows 32 and 64-bit: %programfiles%\Sophos\Enterprise Console\

If you use a non-default installation location, see Sophos knowledgebase article 114299 for advice.

If Enterprise Console databases are on a remote server, you can use Sophos tools BackupDB.bat

and RestoreDB.bat to back up and restore the databases. For more information, see Sophos knowledgebase article 110380 .

To back up the Enterprise Console data and configuration:

1. Log on as the Administrator to the computer where the Enterprise Console management server is installed.

2. Open Command Prompt (click Start, Run, type cmd, and then press Enter).

3. Browse to the folder containing the tool.

■ In Windows 64-bit, type: cd "C:\Program Files (x86)\Sophos\Enterprise Console\"

■ In Windows 32-bit, type: cd "C:\Program Files\Sophos\Enterprise Console\"

4. To back up everything, type:

DataBackupRestore.exe -action=backup

To display the usage options, type:

DataBackupRestore.exe -?

For more information about using the tool, see also Sophos knowledgebase article 114299 .

You are now ready to upgrade Enterprise Console.

Sophos Enterprise Console

10.2 Upgrade Enterprise Console

Important:

If you have the Sophos Management Database component installed on a separate server, you must upgrade the database component first before upgrading the management server.

You must not make any changes in Enterprise Console (for example, change policy settings) between upgrading the database and upgrading the management server.

For more information about upgrading the database on a remote server, including upgrading on a secure server using a script and upgrading in a clustered SQL Server environment, see Sophos knowledgebase article 33980 .

To upgrade Enterprise Console:

1. At the computer where you want to upgrade Enterprise Console, log on as an administrator:

■

If the server is in a domain, use a domain account that has local administrator rights.

If the server is in a workgroup, use a local account that has local administrator rights.

2. Find the Enterprise Console installer that you downloaded earlier.

Tip: The installer file name includes "sec".

3. Double-click the installer.

4. A wizard guides you through the upgrade.

5. Complete the wizard.

Important: The Sophos Auditing database, SophosSecurity, must be present and running side by side with the other Enterprise Console databases, even if you don't intend to use the Sophos

Auditing feature. This is because the database is used for enhanced access control as well as for logging audit events.

10.3 Enhance database security

Audit the database

In addition to the protection built into the Enterprise Console databases, we recommend setting additional protection at the SQL Server instance level (if not already in place) to audit user activities and changes on your SQL Server.

For example, if you are using an Enterprise edition of SQL Server 2008, you can use the SQL

Server Audit feature. Earlier versions of SQL Server support login auditing, trigger-based auditing, and event auditing by using a built-in trace facility.

For more information about features that you can use for auditing activities and changes on your

SQL Server system, see the documentation for your version of SQL Server. For example:

■

SQL Server Audit (Database Engine)

Auditing (Database Engine), SQL Server 2008 R2

Auditing in SQL Server 2008

upgrade guide

■ Auditing (Database Engine), SQL Server 2008

Encrypt connections to the database

We strongly recommend that you encrypt connections between any clients and the Enterprise

Console databases. For more information, see the SQL Server documentation:

■

Enable Encrypted Connections to the Database Engine (SQL Server Configuration Manager)

Encrypting Connections to SQL Server 2008 R2

How to enable SSL encryption for an instance of SQL Server by using Microsoft Management

Console

Control access to the database backups

Ensure proper, restrictive access control to any database backups or copies. This will ensure that unauthorized users cannot access the files, tamper with them, or accidentally delete them.

Note: The links in this section lead to information maintained by third parties and are provided for your convenience. Although we try to review the accuracy of the links periodically, the links may change without our knowledge.

10.4 Check existing policies

10.4.1 Check policy settings

Note: If you use role-based administration, you must have the Computer search, protection

and groups right to perform these tasks. For more information, see the Enterprise Console Help,

"About roles and sub-estates" .

To check that your policy settings have been preserved after upgrading Enterprise Console:

1. Start Enterprise Console.

2. In the Policies pane, double-click a policy type (for example, Anti-virus and HIPS).

3. Double-click the policy you want to check.

4. In the dialog box that is displayed, review the policy settings.

10.4.2 Check policies applied to computer groups

Note: If you use role-based administration, you must have the Computer search, protection

and groups right to perform these tasks. For more information, see the Enterprise Console Help,

"About roles and sub-estates" .

To check that your groups have the correct policies applied to them after upgrading Enterprise

Console, do the following.

Sophos Enterprise Console

Note: Features not included in your license, which were displayed in previous versions of

Enterprise Console, may no longer be displayed.

1. Start Enterprise Console.

2. In the Groups pane, right-click a group, and then click View/Edit Group Policy Details.

3. In the Group Details dialog box, verify that the group is assigned the right policies. If not, for a policy type, select a different policy from the drop-down list.

You have finished upgrading Enterprise Console.

upgrade guide

11 Enable Malicious Traffic Detection

Enterprise Console 5.3.0 introduced support for Malicious Traffic Detection, which detects communications between endpoint computers and command and control servers involved in botnet or other malware attacks. If you upgraded from a version earlier than 5.3.0, or haven’t enabled this feature before, you need to enable it after the upgrade to benefit from it.

Note: Malicious traffic detection is currently supported only on Windows 7 and later non-server operating systems and is first available in Endpoint Security and Control 10.6.0.

1. Check which anti-virus and HIPS policy is used by the group or groups of computers for which you want to enable the new feature.

In the Groups pane, right-click the group. Select View/Edit Group Policy Details. In the group details dialog box, you can see the policies currently used.

2. In the Policies pane, double-click Anti-virus and HIPS.

3. Double-click the policy you want to change.

The Anti-Virus and HIPS policy dialog box is displayed.

4. In the On-access scanning panel, make sure the Enable behavior monitoring check box is selected.

5. Beside Enable behavior monitoring, click Configure.

6. In the Configure Behavior Monitoring dialog box, make sure the Detect malicious behavior check box is selected.

7. To enable malicious traffic detection, select the Detect malicious traffic check box.

Note: Malicious traffic detection uses the same set of exclusions as the Sophos Anti-Virus on-access scanner (InterCheck ™ ).

Sophos Enterprise Console

12 Technical support

You can find technical support for Sophos products in any of these ways:

■ Visit the Sophos Community at community.sophos.com/ and search for other users who are experiencing the same problem.

■

Visit the Sophos support knowledgebase at www.sophos.com/en-us/support.aspx

Download the product documentation at www.sophos.com/en-us/support/documentation.aspx

Open a ticket with our support team at https://secure2.sophos.com/support/contact-support/support-query.aspx

upgrade guide

13 Legal notices

Copyright © 2013–2017 Sophos Limited. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise unless you are either a valid licensee where the documentation can be reproduced in accordance with the license terms or you otherwise have the prior permission in writing of the copyright owner.

Sophos, Sophos Anti-Virus and SafeGuard are registered trademarks of Sophos Limited, Sophos

Group and Utimaco Safeware AG, as applicable. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.

ACE

™

, TAO

™

, CIAO

™

, DAnCE

™

, and CoSMIC

™

ACE

™

, TAO

™

, CIAO

™

, DAnCE

™

, and CoSMIC

™

(henceforth referred to as "DOC software") are copyrighted by Douglas C. Schmidt and his research group at Washington University , University of California, Irvine , and Vanderbilt University , Copyright (c) 1993-2014, all rights reserved. Since

DOC software is open-source, freely available software, you are free to use, modify, copy, and distribute—perpetually and irrevocably—the DOC software source code and object code produced from the source, as well as copy and distribute modified versions of this software. You must, however, include this copyright statement along with any code built using DOC software that you release. No copyright statement needs to be provided if you just ship binary executables of your software products.

You can use DOC software in commercial and/or binary software releases and are under no obligation to redistribute any of your source code that is built using DOC software. Note, however, that you may not misappropriate the DOC software code, such as copyrighting it yourself or claiming authorship of the DOC software code, in a way that will prevent DOC software from being distributed freely using an open-source development model. You needn't inform anyone that you're using DOC software in your software, though we encourage you to let us know so we can promote your project in the DOC software success stories .

The ACE , TAO , CIAO , DAnCE , and CoSMIC web sites are maintained by the DOC Group at the

Institute for Software Integrated Systems (ISIS) and the Center for Distributed Object Computing of Washington University, St. Louis for the development of open-source software as part of the open-source software community. Submissions are provided by the submitter "as is" with no warranties whatsoever, including any warranty of merchantability, noninfringement of third party intellectual property, or fitness for any particular purpose. In no event shall the submitter be liable for any direct, indirect, special, exemplary, punitive, or consequential damages, including without limitation, lost profits, even if advised of the possibility of such damages. Likewise, DOC software is provided as is with no warranties of any kind, including the warranties of design, merchantability, and fitness for a particular purpose, noninfringement, or arising from a course of dealing, usage or trade practice. Washington University, UC Irvine, Vanderbilt University, their employees, and students shall have no liability with respect to the infringement of copyrights, trade secrets or any patents by DOC software or any part thereof. Moreover, in no event will Washington University,

UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages.

Sophos Enterprise Console

DOC software is provided with no support and without any obligation on the part of Washington

University, UC Irvine, Vanderbilt University, their employees, or students to assist in its use, correction, modification, or enhancement. A number of companies around the world provide commercial support for DOC software, however. DOC software is Y2K-compliant, as long as the underlying OS platform is Y2K-compliant. Likewise, DOC software is compliant with the new US daylight savings rule passed by Congress as "The Energy Policy Act of 2005," which established new daylight savings times (DST) rules for the United States that expand DST as of March 2007.

Since DOC software obtains time/date and calendaring information from operating systems users will not be affected by the new DST rules as long as they upgrade their operating systems accordingly.

The names ACE

™

, TAO

™

, CIAO

™

, DAnCE

™

, CoSMIC

™

, Washington University, UC Irvine, and

Vanderbilt University, may not be used to endorse or promote products or services derived from this source without express written permission from Washington University, UC Irvine, or Vanderbilt

University. This license grants no permission to call products or services derived from this source

ACE

™

, TAO

™

, CIAO

™

, DAnCE

™

, or CoSMIC

™

, nor does it grant permission for the name

Washington University, UC Irvine, or Vanderbilt University to appear in their names.

If you have any suggestions, additions, comments, or questions, please let me know.

Douglas C. Schmidt

Apache

The Sophos software that is described in this document may include some software programs that are licensed (or sublicensed) to the user under the Apache License. A copy of the license agreement for any such included software can be found at http://www.apache.org/licenses/LICENSE-2.0

Boost Software License

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT

SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE

FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR

OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR

THE USE OR OTHER DEALINGS IN THE SOFTWARE.

upgrade guide

Common Public License

The Sophos software that is referenced in this document includes or may include some software programs that are licensed (or sublicensed) to the user under the Common Public License (CPL), which, among other rights, permits the user to have access to the source code. The CPL requires for any software licensed under the terms of the CPL, which is distributed in object code form, that the source code for such software also be made available to the users of the object code form. For any such software covered under the CPL, the source code is available via mail order by submitting a request to Sophos; via email to [email protected]

or via the web at https://www.sophos.com/en-us/support/contact-support.aspx

. A copy of the license agreement for any such included software can be found at http://opensource.org/licenses/cpl1.0.php

ConvertUTF

This source code is provided as is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. If this file has been purchased on magnetic or optical media from Unicode, Inc., the sole remedy for any claim will be exchange of defective media within 90 days of receipt.

Unicode, Inc. hereby grants the right to freely use the information supplied in this file in the creation of products supporting the Unicode Standard, and to make copies of this file in any form for internal or external distribution as long as this notice remains attached.

Loki

The MIT License (MIT)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL

THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR

OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,

ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR

OTHER DEALINGS IN THE SOFTWARE.

Sophos Enterprise Console

Microsoft Public License (MS-PL)

This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.

1. Definitions

The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law.

A "contribution" is the original software, or any additions or changes to the software.

A "contributor" is any person that distributes its contribution under this license.

"Licensed patents" are a contributor's patent claims that read directly on its contribution.

2. Grant of Rights

(A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create.

(B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software.

3. Conditions and Limitations

(A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks.

(B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically.

(C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software.

(D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license.

(E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

A copy of the MS-PL terms can be found at https://opensource.org/licenses/MS-PL .

OpenSSL Cryptography and SSL/TLS Toolkit

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually

upgrade guide both licenses are BSD-style Open Source licenses. In case of any license issues related to

OpenSSL please contact [email protected].

OpenSSL license

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the OpenSSL

Toolkit. ( http://www.openssl.org/ )”

4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]

5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the OpenSSL

Toolkit ( http://www.openssl.org/ )”

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANY EXPRESSED

OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR

ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

This product includes cryptographic software written by Eric Young ( [email protected]

). This product includes software written by Tim Hudson ( [email protected]

Original SSLeay license

This package is an SSL implementation written by Eric Young ( [email protected]

). The implementation was written so as to conform with Netscape’s SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4,

RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this

Sophos Enterprise Console distribution is covered by the same copyright terms except that the holder is Tim Hudson

( [email protected]

Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

“This product includes cryptographic software written by Eric Young ( [email protected]

)”

The word “cryptographic” can be left out if the routines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory

(application code) you must include an acknowledgement:

“This product includes software written by Tim Hudson ( [email protected]

)”

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN

NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,

OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE

USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]

WilsonORMapper

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

■ Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

upgrade guide

■ Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS

IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Windows Template Library (WTL)

The use and distribution terms for this software are covered by the Common Public License.

Source code for this component is available here: https://sourceforge.net/projects/wtl/files/

zlib data compression library

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly [email protected]

Mark Adler [email protected]

Reklama

Sophos Enterprise Console upgrade guide

Product version: 5.5

Contents

1 About this guide

2 Which versions can I upgrade from?

Do I need to upgrade the databases separately?

Unix endpoints

3 Sophos Disk Encryption

3.1 Upgrade Sophos Disk Encryption 5.61 to SafeGuard

Enterprise

3.2 Uninstall Sophos Disk Encryption

4 Tool version compatibility for Enterprise

Console

5 What are the steps in upgrading?

6 System requirements

.NET Framework installation

6.1 Free disk space requirements

7 The accounts you need

Accounts required to perform the upgrade

Sophos database account

8 Will I get the same updates as before?

8.1 About Sophos Update Manager upgrade

9 Download the installer

10 Upgrade Enterprise Console

10.1 Back up Enterprise Console data and configuration

10.2 Upgrade Enterprise Console

10.3 Enhance database security

Audit the database

Encrypt connections to the database

Control access to the database backups

10.4 Check existing policies

10.4.1 Check policy settings

10.4.2 Check policies applied to computer groups

11 Enable Malicious Traffic Detection

12 Technical support

13 Legal notices

ACE

, TAO

, CIAO

, DAnCE

, and CoSMIC

Apache

Boost Software License

Common Public License

ConvertUTF

Loki

Microsoft Public License (MS-PL)

OpenSSL Cryptography and SSL/TLS Toolkit

WilsonORMapper

Windows Template Library (WTL)

zlib data compression library

Související

Sophos Enterprise Console Upgrade Guide

Sophos Enterprise Console quick Startup Guide

Sophos Enterprise Console Quick Startup Guide

Sophos Enterprise Console Quick Startup Guide

Sophos Enterprise Console Quick Startup Guide

Sophos Enterprise Console quick Startup Guide

Sophos Enterprise Console advanced Startup Guide

Sophos Anti-Virus for UNIX Startup Guide

Sophos Enterprise Console 5.1 Guide: AI Chat & PDF

Cisco T27LDSP32CP21 Manual: AI Chat & PDF Access

SafeGuard Easy Administrator Help

Sophos Enterprise Console server to server migration Guide