Объявление

Свернуть
Пока нет объявлений.

восстановить сервер epolicy orchestrator

Свернуть
X
  • Фильтр
  • Время
  • Показать
Очистить всё
новые сообщения

    восстановить сервер epolicy orchestrator

    Здравствуйте! Подскажите как можно сделать резервную копию настроек сервера управления продуктами Mcafee - epolicy orchestrator ? Можно ли как то экспортировать настройки?
    Проблема в том что нужно перенести и заодно обновить сервер управления mcafee. Хотелось бы выгрузить настройки, затем все грохнуть и поднять на новом сервере свежую версию ПО, потом импортировать настройки. Интересно так можно?

    #2
    Да. Можно забэкапить и восстановить. Процедура переноса состоит из нескольких этапов. Все расписано в статье:
    https://kc.mcafee.com/corporate/inde...ent&id=kb66616
    Backing up the ePO server
    Use the following to back up the SQL database (normally named ePO_<ServerName>, where the <ServerName> is your ePO server name):
    See article KB52126 for details on backing up the ePO database using SQL Server Management Studio.
    See article KB59562 for details on backing up the ePO database using OSQL commands.

    You must also back up the following folder paths:

    NOTE: The default 64-bit installation path is listed below. However, your installation might differ (for example, the default 32-bit installation path is C:\Program Files\McAfee\ePolicy Orchestrator).
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions
    The default path to ePO software extension information.

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf
    The default path to required files used by the ePO software extensions.

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\keystore
    These keys are for ePO agent-server communication and the repositories.

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software
    All products that have been checked into the Master Repository are located here.

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Keystore
    The agent-to-server communication and Repository Keys that are unique to your installation are located here. Failing to restore this folder will result in all client systems being unable to communicate with the server, and you will have to redeploy the agent to all systems. Additionally, you will have to check in all deployable packages again.

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf
    The server configuration settings for Apache, the SSL certificates needed to authorize the server to handle agent requests, and console certificates are located here.

    NOTE: Failure to back up and restore these directory structures will require a re-installation of ePO to create new ones and possibly require a clean database installation and redeployment of agents to all client systems.

    Recover the ePO server
    Delete the ePO database on the SQL server. If you do not know how to perform the MSSQL operation, refer to http://technet.microsoft.com/en-us/l.../ms177419.aspx or contact Microsoft Support.

    If restoring ePO to the same system, uninstall ePO. Ensure that there is no ePolicy Orchestrator folder in the original installation path after the software is uninstalled.

    NOTE: Renaming the existing ePolicy Orchestrator folder and leaving the old directory in place may interfere with the new installation. Intel Security recommends that you remove the old directory completely.

    Re-install ePO to the same version and patch level as the server you are restoring.

    NOTE: You can verify the ePO patch level by looking at the Version field in the backed up Server.ini file (C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\) and cross-referencing it with article KB59938.

    IMPORTANT: You must re-install ePO to the exact same directory path as the previous installation for this article to apply (or initialization of extensions will fail when the restore is complete). If the installation path is different, follow the steps in article KB71078 instead.

    Apply any additional patches/hotfixes/POCs to ePO that had been previously applied. If you have previously installed Policy Auditor 6.2 for use with ePO, install the same version of Policy Auditor (including any hotfix releases) that had been installed before.

    Stop and disable all ePO services:

    Click Start, Run, type services.msc, and click OK.
    Right-click each of the following services and select Stop:

    McAfee ePolicy Orchestrator Application Server
    McAfee ePolicy Orchestrator Event Parser
    McAfee ePolicy Orchestrator Server

    Double-click each of the following services and change Startup type to Disabled:

    McAfee ePolicy Orchestrator Application Server
    McAfee ePolicy Orchestrator Event Parser
    McAfee ePolicy Orchestrator Server

    Restore the database. See article KB52126 for details on restoring the ePO database using SQL Server Management Studio.

    NOTE: Restore the database so that you do not require the ePO database configuration to be updated (for example, same name, host, port, and so on). Otherwise, you must update the restored DB.PROPERTIES file in C:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion with the new information before starting the server.

    Rename the following folders (for example, rename the extensions folder to extensions_old), and then replace them with the corresponding folders that were backed up earlier in step 2:

    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\conf
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\keystore
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Keystore
    C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf

    Start the McAfee ePolicy Orchestrator Application Server service only.

    Attempt to log on to the ePO console. If you are unable to log on, review all the steps performed in this article and ensure that they have been properly completed. If you cannot resolve the console logon issue, contact Technical Support for further assistance before proceeding.

    {GENAA}

    NOTE: You must be able to log on for the rest of the recovery steps to work.

    Rename the SSL.CRT folder (see path below) to SSL.CRT.OLD and manually create an empty folder named SSL.CRT in the same path; otherwise the setup will fail to create a new certificate:

    64-bit: "C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
    32-bit: "C:\Program Files\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"

    Click Start, type cmd in the search field, right-click and select Run as administrator.
    Change directories to your ePO installation directory.

    Default paths:

    64-bit: Program Files (x86)\McAfee\ePolicy Orchestrator\
    32-bit: Program Files\McAfee\ePolicy Orchestrator\

    Run the following command:

    Rundll32.exe ahsetup.dll RunDllGenCerts <ePO_server_name> <console_HTTPS_port> <admin_username> <password> <"installdir\Apache2\conf\ssl.crt">

    where:

    <ePO_server_name> is your ePO server NetBIOS name
    <console_HTTPS_port> is your ePO console port (default is 8443)
    <admin_username> is admin (use the default ePO admin console account)
    <password> is the password to the ePO admin console account
    <installdir\Apache2\conf\ssl.crt> is your installation path to the Apache folder; Default installation path:

    64-bit: "C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"
    32-bit: "C:\Program Files\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"

    Example
    Rundll32.exe ahsetup.dll RunDllGenCerts eposervername 8443 administrator password "C:\Program Files\McAfee\ePolicy Orchestrator\Apache2\conf\ssl.crt"

    IMPORTANT:
    This command will fail if you have enabled User Account Control (UAC) on this server. If the server is running Windows Server 2008 or later, disable this feature. You can find more information about UAC at: http://technet.microsoft.com/en-us/l...91(WS.10).aspx.
    This command is case-sensitive. The ahsetup.log (found in <installdir\Apache2\conf\ssl.crt>) provides information about whether the command succeeded or failed and will state whether it used the files located in the ssl.crt folder.
    Start the following services:

    McAfee ePolicy Orchestrator Event Parser
    McAfee ePolicy Orchestrator Server

    Look in the DB/logs/server.log to ensure that the Agent Handler (Apache server) started correctly. It should state something similar to the following:

    20090923173647 I #4108 NAIMSRV ePolicy Orchestrator server started.

    If it does not, there will be an error similar to the following:

    20090923173319 E #4736 NAIMSRV Failed to get server key information.

    Комментарий

    Обработка...
    X