Does this upgrade automatically install version 2.7.11 of the CLI tools on RHEL?

Yikes - still haven't fixed the hanging "change management initialization" bug seen since 10.32?

Same question for all platforms...

Considering the status of database backups, I think this announcement should include a caveat that the jamf-pro binary needs to be updated to 2.7.11 and a fresh backup taken before upgrading.

The release notes say that Jamf Remote will no longer be distributed in a future release. Can we get more details about this deprecation? This is a pretty important tool for us.

@jtrant @JayDuff Unfortunately Jamf Pro 10.34 will not automatically install the latest version on the CLI tools (2.7.11).  The issue was discovered too late in the release process to get it into 10.34.  To avoid backup issues you will need to manually download the latest version here: https://account.jamf.com/products/other/jamf-pro-server-tools.

@mikeh I absolutely agree.  I would also like more details about the deprecation of Jamf Remote as this is an incredibly useful tool for troubleshooting and testing.

Post the SQL commands for all the victims !

Good idea @djdavetrouble. Here's my teams documentation for it:

Since Jamf Pro 10.32.1, after running the Jamf Pro installer and then navigating to the Web UI, the loading bar gets stuck at the “initializing” stage and hangs until the following is completed. No fix from Jamf yet (09/27/21), but has an article here  

• Stop Tomcat on all instances 
• Run the following query in MySQL DB server:  

• use jamfsoftware; 
• truncate change_management; 

• Start Tomcat on MySQL DB server
• Once Jamf Pro is initialized, re-enable 'Use Log File' and 'Use Syslog Server' if needed and modify the Change Management log file location within Settings > System Settings > Change Management to the correct location
  • If re-enabled, it will get stuck at the same progress bar each time Apache Tomcat is rebooted....so be warned.

Same here!  I use it almost daily.

another vote for JAMF remote.  As both a remote screen sharing and immediate remote execution and troubleshooting tool, JAMF Remote is invaluable.  Deprecating this will leave a significant functionality gap in the JAMF mgt ecosystem.   Team Viewer may be touted as the remote screen sharing solution, but what of the other feature set that JAMF remote provides ?

personally would love to see a full end to end support helpdesk with remote access functionality included into the jamf eco system to replace JAMF remote. with ticket system and video/web/app chat, so when X user requests support, IT support have the tools and device information available from jamf pro as they establish a request.

Actually, I've been wondering if that's a minor goal here - for the remote-access solution, use/promote the TeamViewer integrations that have been incorporated, at the very least, as suggested by @RJH . As far as an end-to-end support system with ticketing and the chat features: I would find the chat features useful, but the ticketing would go unused by us, as we already have a ticketing system that is probably never going to hook into Jamf. 😞

I agree with @RJH that remote-access is only part of the benefits of Jamf Remote. On-demand deployment has been highly valued as a feature in the past, ignoring the past 18 months, of course.

I for one don't relish the idea of going back to the dumpster fire that is ARD for on-prem management.

Not to mention the ability to remotely login to the GUI in a separate session from the end user's GUI session as opposed to taking over the end user's session... very useful for performing management tasks that are more easily done in the GUI than the CLI.

+1 for keeping Jamf Remote

I am still missing an option to forcefully update the Macs and iOS/iPadOS devices. 🤔 🤔

iPad, available for managed devices. (providing they have suitable storage, aren't shared devices, and regularly check into the mdm).

Macbook, requires a fair bit more.

Jamf Remote is what we use also add another Vote for keeping Jamf Remote.  We need to know what is going to be deprecated.  

I too would like to know what is happening to Jamf Remote.  I have over 30 building support techs that currently depend on the application to update site computers.

Our team uses Jamf Remote daily too.  Interesting we haven't heard a response considering the amount of concern shared by the community...

same here.  can't live without Jamf Remote. 

Yes, we use Jamf Remote for on demand deployment and testing.  It is more than screen sharing app.

Just wanted to add my voice to this sub thread on Jamf Remote deprecation.

For our computer labs it really helps having a tool like Jamf Remote when deploying. It helps in a way that a policy doesn't as it gives immediate feedback and also shows the log results quickly on one screen. It also lets me change or create local accounts quickly.

Yes policies can be used instead but not as well as Jamf Remote. I was hoping that it would eventually remove the need for Apple Remote Desktop, not make ARD my go to tool

We don't use Teamviewer and to be frank I'm be a bit gun-shy of that product with the number of times it has been used by scammers. Maybe that's unfair but it does seem like every time I see a video on that topic, TeamViewer is the tool of choice. Our Service Desk team does use a remote product for both Apple and Windows - just not TeamViewer and that one integrates to record the remote access in the Service Desk

So - it's the quick ability to deploy or do things with Jamf Remote that I like

Same here, we use Jamf Remote daily for connecting to other macbooks, for pushing out apps, for rejoining devices to the domain, etc. etc.