@ray.henry , I also use Manage Engine's DC and always run into issues using the agent. The only way to fix this issue is by re-packaging the agent on your own, here is what I normally do to package it via Composer:
1- Download the agent from the DC site
2- Open Composer and drag your package from step 1 into it
3- Create a folder structure as you see in the screenshot above
4- Package it 5- Copy the package to to your DP and create your policy
If this is a machine with an existing agent on it, you might want to configure Files and Processes in your policy so that the Agent restarts after the upgrade
And this is how the package looks like in Composer
Hope this helps
Hi, everyone!
I've got instruction from MEDC support how to install MEDC agent via Jamf Pro. Tested and it works. Hope it will be helpful.
Steps:
Using Jamf:
Download Mac agent zip form the server console. It has serverinfo.plist and agent pkg files.
We'll first deploy the below to a test machine.
1. Rename serverinfo.plist to com.manageengine.ems.plist
2. The deployment through Jamf (or any other vendors) should have two steps:
Note: plist and .pkg file names should be exact as mentioned above for the steps to work.
Step 1: Deploy the above plist alone (without changing name (i.e., named com.manageengine.ems.plist ) to /Library/Managed Preferences/ as a separate policy/configuration. For example: "Application & Custom Settings" configuration profile in Jamf.
Step 2: Ensure that the above configuration is deployed to your test machine successfully. You can also check if /Library/Managed Preferences/ folder has com.manageengine.ems.plist file.
Step 3. Deploy the Mac agent pkg (without changing name) as a second policy/configuration. The deployed Mac agent will check the /Library/Managed Preferences directory for com.manageengine.ems.plist to install correctly.
Once this config works on a test machine, we can deploy to all machines in the same order. First, plist config to all machines and then pkg config.
