">
 
 
 
 
Home » Agent migration from Patch Manager Plus to Endpoint Central
 

How to migrate agents from Patch Manager Plus?

Note: You can seamlessly migrate from Patch Manager Plus On-Premise to Endpoint Central On-Premise by just applying the Endpoint Central On-Premise license to Patch Manager Plus On-Premise. Refer to this page.

  • Windows
  • Mac
  • Linux

Windows Agent Migration

  1. Download the new agent package

    Note: Kindly download the destination agent.

    • Open the EndpointCentral web console.
    • Navigate to Agent → Computers.
    • Select the required remote office.
    • Click the Download Agent button.
    • Rename the file to LocalOffice_Agent.exe and save it in a folder.

    download-agent

  2. Download the zip

    Download the zip file, extract and copy the contents to the previously created folder.

  3. Generate AgentCleanupToolClient

    Note: For cloud, please reach out to support with agent registry export to generate the clean-up tool. Refer this page for more.

    • Follow the steps in the Patch Manager Plus server machine to which the agent belongs to generate the cleanup tool.
    • Copy the generated AgentCleanupToolClient.exe to the same folder. The folder should contain the below files.

    migration-folder

    • Open command prompt with Admin rights and run ExeCreation.bat. This will generate Agent.exe.

    agent-exe

  4. Add the script to the repository in Patch Manager Plus
    • Open Patch Manager Plus console.
    • Navigate to Deployment → Script Repository → Add Script.

    add-script

    script-repository

    • Navigate to Deployment Policies and click Create Policy.

    deployment-policy

    • Select the required deployment schedule.
    • In Pre-deployment Activities, drag and drop the Custom Script.

    custom-script

    • In Script Name, select MigrateAgent.bat.
    • In Dependency files, upload the previously created Agent.exe file.

    upload-script

    • Once done, Save and Continue, and create the policy.
  5. After creating a deployment policy
    • Create a Manual deployment for patch ID 105979 (Fix Component Store Corruption) with the newly created deployment policy as shown below:

    patch-id

    • Select the Target and click on Deploy Immediately.
    • Check whether the agent is shown in the Endpoint Central console.
    • If Devices for Approval is enabled, you can find it under approval section.

Mac Agent Migration

Follow the steps below to migrate the Mac agent from PMP/VMP to EC/PMP/VMP (Cloud or On-Premise).

  1. Set up AgentMigration.zip
    1. Download AgentMigration.zip and extract its contents.
    2. Download the Mac Agent zip from the EC/PMP/VMP server.
    3. mac-agent-download

      Note
      • Seamless migration can be suggested for On-premise migration.
      • These steps are applicable to both On-Premise and Cloud.
      • Please disable Agent Uninstallation Restriction (TOTP) if enabled before proceeding.
    4. Extract the Mac Agent zip and copy all the contents from the extracted folder.
    5. mac-migration-step1

      mac-migration-step1

    6. Place the copied contents into the UEMSMacAgent folder located inside the AgentMigration folder.
    7. mac-migration-step2

      mac-migration-step3

    8. Compress the Migration.app and UEMSMacAgent folder together and rename the compressed file as AgentMigration.zip.
    9. mac-migration-step1

  2. Host AgentMigration.zip

    Host the AgentMigration.zip file in a location accessible to all agents and Distribution Servers, and note the download link.

  3. Upload the patch to the PMP server
    1. Go to Patches → Downloaded Patches.
    2. Change the filter from Missing Patches in Network to All Patches.
    3. Search for patch ID 602701.
    4. Upload the hosted AgentMigration.zip link and its checksum as an External URL.
    5. Deploy the patch to the target machines on which migration has to be done.

    mac-migration-step1

Note: Test on a few Mac machines before deploying to all. It is recommended to deploy in batches.

Linux Agent Migration

Note
Kindly download the destination agent.
  1. Download the agent package
    • Open the EndpointCentral web console.
    • Navigate to Agent → Computers.
    • Select the required remote office and Linux as OS Platform
    • Select the relevant Domain or Workgroup and processor.
    • Click the Download Agent button.

    linux-migration-step1

  2. Note
    • Seamless migration can be suggested for On-premise migration.
    • These steps are applicable to both On-Premise and Cloud.
    • Please disable Agent Uninstallation Restriction (TOTP) if enabled before proceeding.
    • copyAgentFiles.bash and LinuxAgentInstaller.bash are available at the link.
  3. Add the script to the repository
    1. Navigate to Deployment → Script Repository → Add Script.
    2. Upload the script copyAgentFiles.bash (available at the link above) to the Script Repository and click Add.
    3. linux-migration-step1

  4. Create a Deployment Policy
    1. Navigate to Deployment → Deployment Policies → Create Policy and configure the deployment window based on your preferred schedule.
    2. In Pre-deployment Activities, add Custom Script and click Save and Continue.
    3. In Script Name, select copyAgentFiles.bash.
    4. In Dependency Files, add the following files:
      • DesktopCentral_LinuxAgent.bin / UEMS_LinuxAgent.bin — available in the zip file downloaded from the Cloud console.
      • serverinfo.json — available in the zip file downloaded from the Cloud console.
      • LinuxAgentInstaller.bash

      linux-migration-step1

    5. Click Save and Continue through the remaining pages and save the deployment policy.
  5. Deploy to Linux machines
    1. Navigate to Deployment → Manual Deployment → Install/Uninstall Patch → Linux.
    2. Under Install Linux Patch, click Add Patches, search for patch ID 890003 and click Add.
    3. In Apply Deployment Policy, select the deployment policy created above.
    4. Set the target as the Linux machines on which migration has to be done.
    5. Select Deploy Immediately.

    linux-migration-step2

Note
After the pre-deployment configuration is successfully applied, it will take a maximum of 10 minutes to install the new agent. It is recommended to apply and test on a few machines first before deploying to all.