When installing the WARP client on MacOS using a script, it doesn’t use the plist file. The script creates the plist file in /Library/Managed Preferences/ directory, converts it into binary format, and then installs WARP from the pkg file. Since the plist file isn’t being used, the WARP client is deployed like a standalone client, instead of being associated with our Teams organization.
Hi Cathy, Did you get any resolution on this issue ? I’m seeing something similar and was wondering if they were connected .