Came across this today when trying to package and install VMware Fusion 11.5.1 in a new lab.
Creating the package in Composer seemed ok, uploaded into the JSS, policy and scope created pointing to the new lab. All failed to install the package with the error below:
Mon Feb 24 12:04:48 ICT-02C102ZJWF2 jamf: Executing Policy ICT-LAB-VMWare Fusion 11.5.1 Mon Feb 24 12:04:57 ICT-02C102ZJWF2 jamf: Installing VMware Fusion 11.5.1.pkg... Mon Feb 24 12:04:58 ICT-02C102ZJWF2 jamf: Installation failed. The installer reported: installer: Package name is VMware Fusion 11.5.1 installer: Installing at base path / installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. The package is attempting to install content to the system volume.)
Decided to see if the same behaviour would occur if the same files were packaged up as a dmg, result below:
Mon Feb 24 13:37:34 ICT-02C102ZJWF2 jamf: Executing Policy ICT-LAB-VMWare Fusion 11.5.1 Mon Feb 24 13:37:41 ICT-02C102ZJWF2 jamf: Installing VMware Fusion 11.5.1.dmg...
The install succeeded and the app runs without errors.
Now if we try installing the same package on a computer with macOS 10.15.2 we do not get the install fail with the error as above. Is there a change in the way macOS 10.15.3 handles install packages created with third party package makers that has not been noticed or reported on? Nothing really has been mentioned that is readily available.
Jamf Pro Suite 10.18
I've had to simply get a little more crafty in building my packages...especially ones that involve the user template. What I've done is handle it in script writing. I lay the files down to a temp location for the user template and have a script that determines the OS version on the target and for 10.15.x that moves them to one location and a different one for 10.14.x and older. Also in my environment, we have things that we typically install to the root of the hard drive with specially configured permissions. With 10.15.x, I still am able to make it appear to the user as being at the root, but have had to change my methods and target paths to get it there.