Hi Jeff,
This message will appear after you have configured Samba AD.
It’s an orange banner which will disappear after you will change the Administrator’s password for Samba AD.
It’s something like that from the attached print screen but for Samba AD Administrator account.
Hi @JeffBales , can you please test this or did you test it:
add a user to a group and change the password expiration on/off several times.
I had the failure only when the user was added to a group.
I just want to be sure, that my system is not the only one with this issue, because it’s a vm and vm have their own behavior sometimes. 
thx in advance.
Let’s circle back to the issue 
I think everybody here confirms the original problem is solved.
@flatspin could you label it “verified”? I’d like to release the fix today, before beta2 is officially announced! We’re currently waiting to release two important fixes for nethserver-dc 5099, 5103.
Of course you can keep on digging, probably we’ll find other bugs (hopefully not)!
just done.
Kudos to everyone who helped chasing and correcting the bug, also a big thank you to the quality team for the excellent work! 
I seen that reminder in NethServer 6.8 to change the admin password but I have not seen that message in the NS 7 beta, before and after the bug fix.
Off-of-the-this-bug note: I’m using VM (vmplayer) and when am trying to making a new NS beta2 server to check again if the Dashboard gives a reminder to change the administrator password again I get this:
I did a “yum clean all” and I get the same error message. This has happened 4 or 5 times in the past, and I had start NethServer over again. And I briefly did a google “NethServer Clear yum cache” but have not find an answer. It seems to only happen when I installed NS 7 (b1 or b2) and shut if off, and come back to it later on to check to Software center.
I clicked on “Clean Yum Cache”, rebooted, shutdown, “yum clean all”, shutdown, rebooted. The same.
I had a similar problem and had to change epel repo to baseurl in yum.repos.d. Then the message was gone.
Try to do yum chek-update on commandline. Then you maybe can see what the error causes.
@JeffBales @flatspin @GG_jr @fasttech
Such a great list of tests guys! Thanks for your help, you’re making a great job here!
You really deserve a meme!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
