Requirements
Make sure you are connected to the primary node and not the secondary node when working with a Jamf Cloud-hosted or clustered on-premise instance because the primary node is responsible for running volume purchasing related processes and where log errors display if they exist. To identify the node you are connected to, perform the following:
Open either the Safari or Chrome web browser.
Press Shift+⌘+N to open either of the following browser tabs:
Private Browsing for Safari
New Incognito for Chrome
- On the right side of either browser tab title, do the following if there is a:
Single asterisk (*) displayed, you are in the secondary node and you need to press Shift+⌘+Nagain to open another tab displaying two asterisks (**) indicating a primary node.
Double asterisk (**) displayed, you are already in primary mode and proceed to the steps below.
- In Jamf Pro sidebar, click Settings.
- In the search bar, enter
server log. - Select the Jamf Pro server logs option.
- Click the Volume Purchasing Logs tab.
- Search for code block using either of the following methods:
- Download and search the log.
- Use .