Expiration Date Picker - Custom Entries

Implemented

Expiration Date Picker - Custom Entries

avatar

Good afternoon.

I was wondering if there is a way to change the entries that are provided in RDM.

I manager numerous domains that have different password expiration policies.

Only a couple utilize the "3 months" included. Others utilize policies that are not on the list.

If not, this would be nice if the listed entries available could be changed via one of the PowerShell commands available.

forum image

Have a great evening/

--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM

All Comments (8)

avatar

Hello,

It is possible to update the Expiration date for multiple entries at once using the Edit - Batch - Edit (Special Actions) - Custom PowerShell Command like the following sample.

forum image

Let us know if that could help.

Best regards,

Érica Poirier

avatar

So how do I use powershell commands to modify the following:

Tomorrow = 45 Days
Next Week = 60 Days

There should be availability for the end user to modify those entries to our liking on the list.

Just because the Dev team at Devolutions thinks the entries there are perfect for them, they don't compensate a real-world scenario for IT Support without being able to add / delete / change the ones included.

I don't want to batch edit. I want to be able to pick a selection from a drop down and have it there. I'm sure this is something a lot of other folks watching this thread would appreciate the ability to do. Customize for our real-world environments.

Thank you.

--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM

avatar

Hello,
I'm curious to know which different password expiration policies you have? It's not an easy task to make it customizable, but it could be easy to add the missing ones while hiding the unuseful items.

Regards

David Hervieux

avatar

Thank you, I was writing my question while your were answering. This will be easy to add 45 days and 60 days. This is not perfect and I keep your request in mind.

Regards

David Hervieux

avatar
Thank you, I was writing my question while your were answering. This will be easy to add 45 days and 60 days. This is not perfect and I keep your request in mind.

Regards


This would be nice. And it's not an out of the blue request. CIS (Center for Internet Security) standards are maximum 60 day password expiration, while some STIG (Security Technical Implementation Guide) and Hi-Trust standards are 45 day expiration.

There are thousands of companies that follow one of the above, or all three (as my company does).

Much appreciated for this. 30, 45, 60, and 90 days should cover 99% of all needs for end-user environments.

--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM

avatar

Hello,
Coming in an update soon:

forum image

Regards

David Hervieux

avatar

THANK YOU!!! For those of us who deal with Server Hardening, this makes it so much easier to keep track of expiring passwords.

Also, don't forget to make the w in "weeks" capitalized. :-)

--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM

avatar

Hello,
Indeed there is an issue with the localization weeks. It's now fixed and everything will be in RDM 2022.3.33

Regards

David Hervieux

Ends in 10 days