Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PowerShell Command Set-PasswordFilterConfig fails #109

Closed
PVTGoesen opened this issue May 4, 2023 · 3 comments
Closed

PowerShell Command Set-PasswordFilterConfig fails #109

PVTGoesen opened this issue May 4, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@PVTGoesen
Copy link

Version: 1.1.51
I used an elevated shell:

PS C:\...> Import-Module LithnetPasswordProtection
PS C:\...> Set-PasswordFilterConfig -StorePath "C:\LPPforAD"

Set-PasswordFilterConfig : Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
In Zeile:1 Zeichen:1
+ Set-PasswordFilterConfig -StorePath "C:\LPPforAD"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-PasswordFilterConfig], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Lithnet.ActiveDirectory.PasswordProtection.PowerShell.SetP
   asswordFilterConfig

Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. Is german for:
object reference not set to an instance of an object

I tested it on Windows Server 2012R2, 2019 and 2022.

Does this command just change the registry key?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lithnet\PasswordFilter
REG_SZ - Store - C:\...

Or do I need to change something else as well?

@ryannewington ryannewington self-assigned this May 4, 2023
@ryannewington ryannewington added the bug Something isn't working label May 4, 2023
@ryannewington
Copy link
Member

@PVTGoesen
Thanks for reporting this bug and apologies for any inconvenience caused.

If you create an empty registry key HKLM\Software\Policies\Lithnet\PasswordFilter this issue should go away.

We will get a new release published shortly to fix this.

And yes, the PowerShell script just changes that key.

@PVTGoesen
Copy link
Author

Hi, thanks for the answer. I changed it manualy and it works fine.

@ryannewington
Copy link
Member

Fixed in v1.1.53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants