I saw the same thing today after upgrading to 10.17. Which version did you upgrade to?

@khurram In my experience, after upgrading the Jamf Pro server, the client-side JAMF binary auto-updates when the computer next checks-in.

/usr/local/bin/jamf -version

sudo /usr/local/bin/jamf update -verbose

@jgsims we upgraded from 15 to 17

As pointed out by @dan-snelson, the client binary gets auto-updated when the computer next checks in.

Here's the snippet from my mac's Jamf.log, showing the upgrade on Nov 24th, for context. It's quick (within a minute) and painless. Upgrades the binary, agent, helper and Self Service app.

Sun Nov 24 23:19:07 mymac jamf[2665]: Upgrading jamf binary...
Sun Nov 24 23:19:11 mymac jamf[2665]: The management framework will be enforced as soon as all policies are done executing.
Sun Nov 24 23:19:11 mymac jamf[2665]: Upgrading jamf agent...
Sun Nov 24 23:19:12 mymac jamf[2665]: Upgrading jamfHelper.app...
Sun Nov 24 23:19:12 mymac jamf[2665]: Upgrading JAMF notification service...
Sun Nov 24 23:19:13 mymac jamf[2665]: Upgrading Self Service.app...
Sun Nov 24 23:19:16 mymac jamf[2665]: Setting Self Service icon to custom
Sun Nov 24 23:19:16 mymac jamf[2665]: Upgrading Jamf.app...
Sun Nov 24 23:19:19 mymac jamf[2665]: Policy execution will now restart in the background using the updated JAMF Binary.
Sun Nov 24 23:19:19 mymac jamf[2665]: Removing existing launchd task /Library/Application Support/JAMF/tmp/com.jamfsoftware.task.policy.plist...