Profile Manager 5.11.1. New bugs/features.

There are even more bugs:

- The payload "app settings" is not working anymore (settings aren't pushed to devices and vanish after reloading PM)

- Some users asigned to devices are shown in pending/finished tasks, some not

- The same apps are pushed again and again to the same devices several times a day

- Same with the settings of some device groups

- All device groups are renamed to "new device group". If one takes a change in the settings in the device group, it gets renamend to the real name, after the push it's renamed to "new device group" again

- Devices don't rename automatically after registering

The arrows are working for some devices, for some not.

I think the question-mark-symbol is a new feature (not checked in for a period of time, as you wrote). There are two other symbols: a exclamation mark in a black triangle and a question mark in a hexagon (don't know their meaning).

Hello, i can confirm almost anything on your list.

This software somehow gets worse and worse. Unassigning device from user is not reflected in device list. The device shows the user name until server restart.

the worst issue is that profile manager randomly stops communicating to devices that have been shut down or offline for some time, all of them DEP enrolled in ABM, supervised and configurated in Profile Manager, we still try figure out a possible pattern. At first we suspected expired Device MDM certificate. If Device was off while cert expired, turn it on, it is not possible to interact with it anymore. Sometimes in this case the complete Remote Management Profile is removed, apps and settings too, sometimes its all still there. But no way to talk to those devices.

Affected devices occurred with expired and also still valid Device MDM certificate. Some were off 3 weeks, some for 3 months. Not even possible to re-enroll them even after wipe until device is deleted in Profile Manager leaving unremovable placeholder, and then adding placeholder manually with device SN, somehow overwriting the old device entry maybe, we dont know.

Beware, be careful, some serious issues may hit you, this software is getting really unreliable, we already look into alternatives, very very angry and disappointed with the current situation.

Hi Loopi

I can confirm the issue with the unassigned devices from users. But I think this is just a display error, so no matter to worry about it.

It is normal, that you can't interact with devices with expired certs - this problem you have in every other MDM too. No existing MDM can communicate with devices with invalid certs. I can't confirm the issue with the placeholder - for me it's always possible to re-enroll devices after wiping (very rarely i have to set back a device to placeholder, but not more).

Yes, it's annoying, but there is a very good communitiy here with good ideas and I think most bugs will be fixed with the next update. And don't forget: macOS Server is very cheap in comparsion with a payed MDM. There you have the same problems, but the one you pay ist solving them for you ;-).