I'm trying to deploy a package via jamf cloud to install the Symantec
Management Agent on machines. This is not SEP The file from the server
downloads as a zip, with a .pkg and additional resources folder I
understand these need to be put into a DMG ...
Not sure if anyone else is running into this, but when creating a new
local account through Users & Groups in Catalina, that account when
logging in receives messages that it cannot access or create a new
keychain. If I try to access the keychains fo...
Does anyone have a solution for deploying Adobe CC packages on Catalina?
I just created a new package from the Admin Console today, since I
thought the old one wasn't compatible and uploaded it, but the policy
fails during enrollment, check-in, or ma...
This should be pretty simple, but just curious if this is the best
method for enrolling our user's company issued phones without having to
wipe them. All phones are in DEP through ASM, but not enrolled in
jamf.From what I can see the solution would b...
I'm looking to replace a non-app store installed version of Slack with a
version I've set up through the App Store and VPP. The VPP version is
already published in Self Service, and is set to Auto-Update but that
wouldn't affect any users that had do...
So I am using the following jamf script below and everything works
except at some point I noticed Self Service would fail to quit
preventing the OSInstall process. It's hit or miss and sometimes works
and sometimes doesn't. I'm guessing I could just ...
I'll try the PPPC fix, but as a few of you have asked, the .pkg inside
the build folder is what I am trying to upload, and yes that .pkg
installer runs just fine on Catalina if I manually install it. It's when
I try to deploy the composer package thr...
Yes that is the .pkg file i am trying to upload to either JAMF Admin or
the cloud server (the .pkg inside the build folder) but both methods add
.zip to the end of it. Making the package and policy useless. However if
I create the package in Composer...
Trying to upload the downloaded package to either the cloud server or
through jamf admin results in the package being converted to a zip file.
Even though the zip file uploads, it immediately causes the policy to
fail when trying to run it.