Watchman Monitoring creates a URL to link to a computer's record in its JSS.
We're currently using the format:
[jamf server]:[port]/computers.html?id=[jss computer id]
Given that the computer id isn't on the filesystem, we need to run a [lengthy] recon on first run to learn the right ID.
An alternate URL, such as a search by serial number, might be as-effective, but to continue this path with a recon, we'd have to have the ID written to the filesystem.
The goal of this issue is to find a script which could be made a part of a regular JSS checkin that runs this command on an enrolled computer:
defaults write /Library/MonitoringClient/PluginSupport/check_jamf_information_settings JSS_ComputerID "###" (where ### is the Computer ID)
Watchman Monitoring creates a URL to link to a computer's record in its JSS.
We're currently using the format:
[jamf server]:[port]/computers.html?id=[jss computer id]
Given that the computer id isn't on the filesystem, we need to run a [lengthy] recon on first run to learn the right ID.
An alternate URL, such as a search by serial number, might be as-effective, but to continue this path with a recon, we'd have to have the ID written to the filesystem.
The goal of this issue is to find a script which could be made a part of a regular JSS checkin that runs this command on an enrolled computer:
defaults write /Library/MonitoringClient/PluginSupport/check_jamf_information_settings JSS_ComputerID "###"(where ### is the Computer ID)