-
Seeing the same exact issue in a previously closed github issues thread #171
Testing super 4.0.2, all OS updates and Upgrades work perfectly except the non-system software updates. super log recogn…
-
**Describe the issue**
Patcher configuration is not working as it is unable to get the token from Jamf Pro cloud environment
**To Reproduce**
How can this issue be replicated? Provide the steps t…
-
After updating to 4.1.1, currently saved server info is viewable but getting errors that it's not all filled out properly.
attempted to delete them all and rebuild them. After clicking the Connect bu…
-
Hi, jamfcpr 4.0.2 is showing us less than half of the packages in the GUI.
In the log, the JSON looks complete and it starts loading the metadata until it can't talk to the server anymore.
Firs…
-
Hi, my package list is empty at one instance, but they are read out in the logged json.
Can't find any error/failure in the logs, but there are many apparently cropped lines, such as these (marked bo…
-
Env:
Jamf Pro 11.2.1
AutoPkg 3.0.0RC2
macOS 13.6.4 (on GitHub Actions Runner)
API client ID associated with this run has all permissions documented in the wiki
Source recipe: https://github.com/m…
-
During the OS 14.2.1 rollout I'm seeing some odd logs involving the Restart Validation workflow that is supposed to submit inventory to Jamf after the install/reboot. It looks like it is now kicking …
KUSU2 updated
4 weeks ago
-
### What were you trying to do?
OSX: 10.15.6
minikube: 1.15.1 (--driver virtualbox)
virtualbox: 6.1.16
debug using --swap-deployment
### What did you expect to happen?
not to crash
##…
-
UPDATE: Closed this story and filed a testing ticket instead (https://github.com/fleetdm/fleet/issues/21294). We discovered that the MDM protocol allows users to set computer name, serial number, and …
-
Package metadata creation fails when `JSS_URL` contains a trailing slash (`https://acme.jamfcloud.com/`). Removing the trailing slash from `JSS_URL` allow the package metadata to be created successful…