Jamf Pro 11.3 Now Available

Is US-East-2 supposed to be US-East-1 or is US-East-1 not included?

@csummerville Thanks for the question, In late December 2023, we made us-east-2 our new default east region.  

Good to know!  We've been US-East-1 all along and didn't know there was a change.  Also, the link provided in the 11.3 email about Jamf Cloud Hosted Data Regions (https://learn.jamf.com/bundle/technical-articles/page/Jamf_Cloud_Hosted_Data_Region_Information.html) does not list US-East-2, just US-East-1.

Apologies for that feeling like it was a sudden change.  Thanks for the documentation call-out as well.  We have a few other spots we updating and will get this added to the list. 

Updated our sandbox environment yesterday. Glad to see LAPS passwords now available in the GUI. 

I have however noticed that the Enrollment Method is not displayed if the device is enrolled using Prestage enrolments.

Not sure if others are seeing the same behaviour.

@M4tr1xN3o We are seeing the same.

@M4tr1xN30 - thanks for sharing this. Are you using Enrollment Customization by chance? I've gotten a couple reports of this with enrollment customization enabled and are working on our end to reproduce.

Hey @austin_stewart - Thanks for replying. 

No enrollment customisations here. Just a standard prestage enrollment profile.

Thanks for confirming @M4tr1xN3o , I'll add that to our notes as we look at it.

@austin_stewart Thanks 🙌

Does the Enrollment issue affect scoping or only the UI?

Looks like the release notes say Java 21 is recommended and preferred. I work in a Windows environment, I removed Java 11 and installed 21.  When I run the Jamf windows installer, it complains about Java because it is expecting Java 11.  I called support and got a ticket entered, and for the time I re-installed Java 11, but I suspect the documentation related to Java 21 does not apply to 11.3.

Hopefully this saves someone a little time when upgrading. 

@dhausman confirmed for Linux based installations too.

So either the installers are buggy or the documentation is incorrect at this time... 

Should I have the ability to upgrade my instance via my jamf account. I don't seem to have the option.

as @eric-holtam said.. "Does the Enrollment issue affect scoping or only the UI?"

If it effect scoping.. bad things may happen..

@jamf-42  and @eric-holtam  scoping is NOT affected.  Its just UI.

You announce but don’t release ( I know we can do it ourselves) due to bugs but then are not transparent about issues and give no further timelines of fix. This also happened with 11.2 release.

Hey @PCalomeni ,

I'm really curious... the cloud team started on us-west-2 at 11pm PST on 3/8... which means you started at 0700 UTC on 3/9... which is the second time they've started an hour early. The email said 0700 UTC, but this notice says 0800. 

Can we figure out if the Cloud team is just jumping the gun, or we're posting the wrong start times here?

even more interesting... we didn't get updated. we're still on 11.2.1... 

@rstasel Good morning that was just a cloud typo setting up the automated emails, this page was correct. In standard mass upgrades, we set them up for your hosted regional midnight. If your server was not upgraded please get in touch with your support resource and ask them to open a cloud ticket. 

@shawn_eberle Thanks. So you're saying the emails went out an hour early but they didn't actually start until 0800 UTC?

And yes, we have an email in with support. Our customer service rep confirmed a small number of instances seem to have been skipped or... something. =(

@rstasel Correct the email went out an hour early, the upgrades were at 0800 UTC, and thank you!

Great, thanks! This also happened with the 11.2.1 upgrade... emails stated 0700. Is there some more systemic issue here?

@dhausman

We also stayed on Java 11 as per PI116512.

Out of interest, are your Jamf Pro Server Tools also showing Tomcat as "Not Running" even though it is?