9 Replies Latest reply on Oct 27, 2014 12:45 AM by cpcit

    ePO upgrade from 5.0.1 to 5.1 fails

    cpcit

      We are trying to do an inplace upgrade from 5.0.1 to 5.1 and setup fails and the log file has the following error messages "Setup has failed while trying to migrate server tasks to the new server", "Setup has failed while trying to create the agent package", "Setup has failed while trying to check-in a package to the repository". Can anyone please point in the right direction to complete this upgrade? We have followed the upgrade guide for 5.1.

       

      Thanks.

        • 1. Re: ePO upgrade from 5.0.1 to 5.1 fails
          M Bagheryan M

          The recommended Solution by my side is this below mentioned method :

          [Green] https://kc.mcafee.com/agent/index?page=content&id=KB82126&actp=null&viewlocale= en_US&showDraft=false&platinum_st…

          Environment

           

          McAfee ePolicy Orchestrator (ePO) 5.x, 4.6.x

           

           

          Summary

          There may be times when you need or want to perform a side-by-side upgrade of the ePO server, meaning you install a newer version of ePO on a separate server from your existing ePO server and transfer all possible configurations from the source ePO server to the new target, upgraded ePO server. For example, you may want to test the new version of ePO while still maintaining the operational integrity of the existing ePO version.

           

           

          Solution

          Use the following steps to perform a side-by-side upgrade of ePO:

           

          1. Install a different ePO version on the target ePO server.
          2. Export the following configuration information from the source ePO server:
            • System Tree:
              1. Log on to the source ePO server.
              2. Click System Tree from the toolbar on the top.
              3. Click System Tree Actions, Export Systems, and save the file.
            • Policies and Policy Assignments:
              1. Click Menu, System Tree, Assigned Policies.
              2. Click Actions, Export All Assignments.
              3. Click Download and save the file.
            • Client Tasks and Assignments:
              1. Click Menu, System Tree, Assigned Client Tasks.
              2. Click Actions, Export All Assignments.
              3. Click Download and save the file.
            • Server Tasks:
              1. Click Menu, Automation, Server Tasks.
              2. Click Select All.
              3. Click Actions, Export Tasks.
              4. Click Download and save the file.
            • Automatic Responses:
              1. Click Menu, Automation, Automatic Responses.
              2. Click Select All.
              3. Click Actions, Export Responses.
              4. Click Download and save the file.
            • Rogue System Detection (RSD):
              1. Back up the RSD server settings:
                1. Log on to the ePO console.
                2. Click Menu, Configuration, Server Settings.
                3. Make a note of any custom configuration in the following categories:
                  • Detected System Compliance
                  • Detected System Exception Categories
                  • Detected System Matching
                  • Detected System OUIs
                  • Rogue System Sensor
              2. Export the RSD exceptions:
                1. Log on to the ePO console.
                2. Click Menu, Systems, Detected Systems.
                3. Click Import/Export Exceptions under the Overall System Status dashboard header.
                4. Click the Export Exceptions tab, then click here to download exceptions entry.
                5. Click Save and save the file.
                  NOTE: Exporting Exceptions does not export Exception Categories. You have to manually recreate Exception Categories after reinstalling the RSD extension.

              3. Export the RSD blacklist:
                1. Log on to the ePO console.
                2. Click Menu, Systems, Detected Systems.
                3. Click View Blacklist under the Rogue System Sensor Status dashboard header.
                4. Click Actions, Rogue Sensor, Export Blacklist.
                5. Click Save and save the file.
            • Security Keys:
              1. Click Menu, Configuration, Server Settings.
              2. Click Security Keys, Edit.
              3. Click Back Up All, type a password (optional), click OK, and save the file.
            • Any Custom Reports:
              1. Click Menu, Reporting, Queries and Reports.
              2. Select the query.
              3. Click Actions, Export Definitions.
              4. Click Download and save the file.
            • Export any other Point Product specific settings.

          3. Import the configuration information into the target ePO server:
            • System Tree:
              1. Log on to the target ePO server.
              2. Click Menu, System Tree, New Systems.
              3. Import systems into the current group (My Organization), but do not push agents. Select the file to import and click OK.
            • Policies and Policy Assignments:
              1. Click Menu, System Tree, Assigned Policies.
              2. Click Actions, Import Assignments.
              3. Select the file to import.
              4. Leave all product policies to import selected, leave all policy assignments selected, and click OK.
            • Client Tasks and Assignments:
              1. Click Menu, System Tree, Assigned Client Tasks.
              2. Click Actions, Import Assignments.
              3. Select the file to import.
              4. Leave all product tasks to import selected, leave all task assignments selected, and click OK.
            • Server Tasks:
              1. Click Menu, Automation, Server Tasks.
              2. Click Actions, Import Tasks.
              3. Select the file to import, click Import All, and click OK.
            • Automatic Responses:
              1. Click Menu, Automation, Server Tasks.
              2. Click Actions, Import Responses.
              3. Select the file to import, click Import All, and click OK.
            • Rogue System Detection (RSD):
              1. Import the RSD exceptions:
                1. Log on to the ePO console.
                2. Click Menu, Systems, Detected Systems.
                3. Click Import/Export Exceptions under the Overall System Status dashboard header.
                4. Select By File and select the file to import.
                5. Click Import Exceptions.
              2. Import the RSD blacklist:
                1. Log on to the ePO console.
                2. Click Menu, Systems, Detected Systems.
                3. Click View Blacklist on the Rogue System Sensor Status page.
                4. Click Actions, Rogue Sensor, Import Blacklist.
                5. Select Import file with list of systems to add to the Sensor Blacklist.
                6. Select the file to import.
                7. Click Import.
            • Security Keys:
              1. Click Menu, Configuration, Server Settings.
              2. Click Security Keys, Edit.
              3. Click Restore All, select the file to import, type the password (if previously specified), and click OK.
            • Any Custom Reports:
              1. Click Menu, Reporting, Queries and Reports.
              2. Click Actions, Import Definitions.
              3. Select the file to import and click Save.

          4. Point existing clients to the new target ePO server:
            1. Log on to the source ePO server.
            2. Click Menu, Configuration, Agent Handlers.
            3. Click Handler Status, Agent Handlers.
            4. Select the target ePO server.
            5. Type the target ePO server FQDN in Published DNS Name.
            6. Type the target ePO server IP address in Published IP Address.
          Systems should now communicate with the target ePO server:
          • When clients communicate with the source ePO server, they will get a new SiteList.xml with a new published DNS name and IP address that point to the target ePO server.
          • At the next communication after receiving the new SiteList.xml, clients will use this information to communicate with the target ePO server and communication will be successful because of the import of the agent-to-server communication keys from source ePO server to the target ePO server.
          • 2. Re: ePO upgrade from 5.0.1 to 5.1 fails
            justav

            Not quite sure, but wasn't there a patch that 5.01 needed to upgrade to 5.1.x?

            Also assuming you upgrade straight to 5.1.1 and not 5.1.0?

            • 3. Re: ePO upgrade from 5.0.1 to 5.1 fails
              M Bagheryan M

              This method is working and I suggest you to do the steps as it is written.

              • 4. Re: ePO upgrade from 5.0.1 to 5.1 fails
                cpcit

                Thanks for your reply. The steps mentioned are to migrate to a new installation not an inplace upgrade. We want to do an inplace upgrade to 5.1.

                • 5. Re: ePO upgrade from 5.0.1 to 5.1 fails
                  M Bagheryan M

                  Your Welcome. This is just the safe way to do without loosing a part.

                  • 6. Re: ePO upgrade from 5.0.1 to 5.1 fails
                    JoeBidgood

                    In this case, I'd disagree - the OP is specifically trying to do an in-place upgrade, and there's no reason why this shouldn't work.

                    The side-by-side method is certainly a valid approach, but it's a lot more work if all you want to do is a straight upgrade.

                     

                    Regards -

                     

                    Joe

                    • 7. Re: ePO upgrade from 5.0.1 to 5.1 fails
                      JoeBidgood

                      Could you zip up and attach the entire McAfeeLogs folder from the server? This contains all the logs of the upgrade attempt and will help work out what went wrong.

                       

                      Thanks -

                       

                      Joe

                      • 8. Re: ePO upgrade from 5.0.1 to 5.1 fails
                        M Bagheryan M

                        JoeBidgood wrote:

                         

                        In this case, I'd disagree - the OP is specifically trying to do an in-place upgrade, and there's no reason why this shouldn't work.

                        The side-by-side method is certainly a valid approach, but it's a lot more work if all you want to do is a straight upgrade.

                         

                        Regards -

                         

                        Joe

                        More Work, More Safe!

                        • 9. Re: ePO upgrade from 5.0.1 to 5.1 fails
                          cpcit

                          Thanks for all your replies. McAfee support had responded with the following KB https://kc.mcafee.com/corporate/index?page=content&id=KB71825. Following this article sorted out the issue.