LAPS!!!!!!!!!

Note: LAPS does not update the FileVault keychain password.
Well this is bummer

Just a heads-up that this new style of post kinda breaks the table a bit, requiring a horizontal scroll. Some cells seem to be just a wee bit too wide.

Thanks for this feedback! 

Is LAPS Solution will only work on pre-stage enrolled machines or can it be used on devices that has not enrolled via pre-stage ? 

Jamf 10.46 on Premise: we're missing the PatchManagement-Section in the Dashboard. It's gone! All our PatchManagement policies couldn't be resolved on the dashboard. What happened to the dashboard? Huge BUG.

Hello @Tanti,

As of now, the LAPS solution will only work for computers enrolled via a PreStage that have the additional admin account also created. That's the account that is able to receive the SetAutoAdminPassword command for the password rotation.

Matt

Hey @jlattke, thanks for the report! Some of our engineers took a look at this behavior (including doing some upgrade testing) and we are unable to replicate this. Has a ticket been opened with Support yet for further investigation? That'd probably be the best way to move forward, perhaps there's a product issue that'll need to be filed.

Aside from the Support route, another suggestion is to try unchecking and then re-checking the "Show in Jamf Pro Dashboard" box for some affected policies - does that get them to show back up and remain? Certainly less than desirable to re-check all of those, but if that'd get things back on their feet that might be worth a try!

@iMatthewCM I am seeing the same thing on my Jamf Pro. Patch Management is missing from the Dashboard. I opened ticket CS0950745.  I am happy to demo it for you if that helps.

Glad that I'm not the only one. Support says the can't reproduce that error … I also have a ticket: 

CS0950108

Having the same issue here. Ticket is open: CS0951776

My support contact suspects it is due to my unsupported mySQL version (8.0.33 instead of the supported 8.0.30). Is it the same for you or do you have other versions?

Jamf wants us to downgrade the SQL DB.

We have 8.0.32. I thought MySQL greater than 8.0.30 are supported since 10.42.0? PI110425 was fixed with this release. 

Can you tell me which version of mySQL you're running? Jamf Support tells me it's about my 10.33 Version which I not officially supported (they go for 10.30)

I really don't know. I think it's a bit annoying that it takes so long for them to support a stable SQL-Version. I've asked dhausman which version he's running. Maybe some new ideas …

System Requirements say 8.0.30. https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/System_Requirements.html

Our enterprise security is pretty insistent that we patch software. So I am running mysql 8.0.33 in both test and dev.  The part that makes that interesting is the dashboard works just fine for me in dev, not in production.  So if they are both running 8.0.33 and the same software version and the same tomcat, why do I get different results in different environments?

A product issue exists now according to support: PI111264

That’s what Michal just wrote me some minutes ago. The case is marked as resolved but it seems it is not …

My guess is that the Ticket is closed because a PI exists. We need to wait now for the next release of Jamf Pro. My ticket is closed as well.

when can we expect the update to hit cloud servers?

What is the ETA as RSR are available and Jamf is not able to report on this (unless I add another EA 🙄) what devices are updated until 10.46

@PCalomeni, any update?

Regarding the issue that is holding back cloud upgrades, is this something that might affect those that self host too?

We have an issue with our instance that requires an upgrade to 10.46 to fix but we're on the cloud version. Any update when this is going to be pushed to cloud users?

I'm in the same boat was told by support to wait till the upgrade so now I'm waiting.