Auto deploying warp configuration with mdm hexnode not executed

Hi All ,

I’m looking for some assistance after 20 hours of banging my head on the desk!

Has anyone had experience deploying Warp Configuration files with MDM products on Mac OS ?

I’m attempting to configure( via XML) the automated setup of WARP via Hexnode MDM and the attachment to a Cloudflare Teams account without the user having to join via the WARP Client preferences panel.

I’m following the Docs here

The WARP software deploys as per the MDM and I’ve configured the XML as per the examples above

Does this look correct ? (values substituted)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "">
<plist version="1.0">
      <true />
      <false />

When I check the PLIST files, they just hold the default values as if none of my configuration values are present.

Any assistance would be greatly appreciated !!



I’ve also seen references to the plist file being ignored by the WARP client

Any experience of this ?

What is the exact name of the plist file your MDM is creating?

Hi csharff


is the only file in the LauchDaemons directory.

its content is

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "">
<plist version="1.0">

This is a screen shot of the Profile values as configured in the MDM and pushed to the machine,

OK , so i was directed to this section in the docs

Any script or management tool that can place a com.cloudflare.warp.plist file in /Library/Managed Preferences on a supported macOS device. Additionally this plist can be wrapped in a .mobileconfig.

In the /library/managed preferences I located an encoded version of my XML file with the correct values in the com.cloudflare.1dot1dot1dot1.macos.plist file.

So the XML values are on the machine , but the WARP client doesn’t seem to be using them.

The plist file name is incorrect. Look at the documentation and the file name you posted. The file name needs to match the documentation exactly. That is what Warp uses to enforce a configuration (same with any other app using a plist)

Hey , Thank you that makes a lot of sense :slight_smile:

… One problem, i don’t control the name of the plist file , its part of the MDM package deployed by hexnode and it’s associated with the profile snap shot ( above) .

Any ideas, apart from trying to modify the plist file post deployment ?

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.