[BUG] ERAS 5.0.119.0 - Password protected setups

[Megachip]

Can't disable or change the password on V4 clients

[Megachip]

Same for V5

[Marcos]

Works fine here. Marked the "Password to unlock" item in the Configuration Editor, left no password set and then pushed the configuration to a client. Password protection was disabled on the client then.

[RJK3]

Maybe check your spelling - you may have spelled the passwort wrong

[Megachip]

Originally Posted by Marcos

Works fine here. Marked the "Password to unlock" item in the Configuration Editor, left no password set and then pushed the configuration to a client. Password protection was disabled on the client then.

exactly what i'm doing... on diffent clients with diffent versions... also tried 1234 (not possible to missspell it), didn't work too

task was successfull, but viewing the updated config shown that there is still a password... checking on client, there is the still the old password... all other configuration parameters seems to be work

[Marcos]

I was able to change the password as well as remove password protection completely on ESET Endpoint Security using ERA v5 fine. Perhaps a remote session or at least a video demonstrating the issue would give us a clue if you're doing it properly.

[Megachip]

All fine... we (the german support and i) discovered, that the default policy has even overwritten the password disable task cause in the default policy is a password set.

Possible ERAS could warn when setting up a configuration task that policy will overwrite it.