Jump to content

jack

Members
  • Content Count

    24
  • Joined

  • Last visited

  • Days Won

    1

jack last won the day on March 10

jack had the most liked content!

About jack

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Again, So I've managed to edit the password reset script, but how do i edit the discovery script? If i go into "Test this script manually" and make the following changes, it works. Script: "Discover Windows Local Admin Accounts" Changes: Line 181 and 188 Add -UseSSL after "-Authentication 'Default'". It works in the test screen, but how do I save the script permanently. If not i get a WinRM error, obviously as it's trying over HTTP which isn't enabled. Edit: I managed to get it to work, but i don't think it's supported I edited the source file here: E:\passwordstate\setup\scripts\Get-LocalAdminAccounts.ps1 Then I went into the Script section of the website and pressed the button "Restore default script" and my edit is noe ready for use and works well.
  2. Hi, I see that Passwordstate relies on a HTTP listener for password resets for Windows computer. My environment is 100% HTTPS listeners. So I thought I'd update the default scripts with the "-UseSSL" parameter for any New-PSSession commands. I'm just wondering if my changes will be overwritten when i for example upgrade Passwordstate to a new version? Edit: Actually I've just now seen i can't edit the inbuilt scripts. So I'll just copy them and make my changes and add as a new script. So problem solved i guess Thanks.
  3. Hello, From what I can see we can only register 1 Yubikey at a time. If a user loses their Yubikey does an admin have to then turn off 2FA for their account to allow access again? Maybe it's possible to register multiple Yubikeys to get around this problem, but i couldn't find any documentation to suggest that.
  4. Ah i see. I thought the drop down was a theme. Live and learn :). Thanks Support and Fabian.
  5. Hi, I do "Choose my own". Here is a video. It's horrible quality, but good enough to show you how to go about changing the colour. https://sourcenix.com/nextcloud/index.php/s/w8Vof4k5pibSGos Could i have done something in system settings to force it to always be "System Default" maybe?
  6. Hi again, When i go to my user preferences and select "Color Theme" i can't seem to get a chosen theme to be saved. For example: I "Choose my own" Select a theme Save and Exit - It doesn't seem to be saved even though I'm told it has been successfully saved. When I navigate back to my preferences the colour settings are back to the default - System Wide. Firefox v55 PasswordState: v8 (8071) Any thoughts?
  7. I just installed the new version and everything is working. Thanks again, much appreciate.
  8. This really does show dedication to the product and is immensely appreciated. I'll test the build as soon as it's available.
  9. A small recap then: I can reproduce the error with the following server setup. All system are Windows Server 2016 Server Core WebServer Language: English - United States Time and Currency Format: Norwegian - Bokmål Keyboard: Norwegian - Bokmål (I don't think the keyboard layout matters) SQL Server Language: English - United States Time and Currency Format: Norwegian - Bokmål Keyboard: Norwegian - Bokmål SQL Server default collation: Danish_Norwegian_CI_AS The error is gone on the folowing setup WebServer Language: English - United States Time and Currency Format: English - United States <--- Difference Keyboard: Norwegian - Bokmål SQL Server Language: English - United States Time and Currency Format: Norwegian - Bokmål Keyboard: Norwegian - Bokmål SQL Server default collation: Danish_Norwegian_CI_AS Conclusion As it stands, it seems the error is because of the time and date settings used when installing Windows Server. Please don't hesitate to contact me if i can help in anyway. I hope you are able to reproduce this error on your end!
  10. Hi, I updated the files are per your instructions, but i still get the same error at the admin creation screen. This is what i did Created a new server Installed passwordstate Setup SSL Checked that the site worked Stopped the PWS service Did a manual overwrite of the file with the zip you gave me Started the PWS service Went through the setup Failed with the exact same error on the admin creation screen and was logged in the PWS debug log in the database I did a reboot of the server and tried again Same error.
  11. Yes, that server is using the same culture and language settings as the new server. PS F:\Backup\passwordstate_upgrade\passwordstate> get-host Name : ConsoleHost Version : 5.1.14393.1532 InstanceId : 5f7a71e2-0fbf-4ea2-9cb7-90f811b499c3 UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : nb-NO CurrentUICulture : en-US PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy DebuggerEnabled : True IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace I hadn't updated to the latest bugfix version, so the preferences pane wasn't available (server error). So before I updated I tested changing the user password via the Administration > Users screen. It worked fine. Then I updated to the latest bugfix version 8065. I logged in after the update I then clicked on my username and the preferences panel come up (Yay!) I then went to Authentication Options I changed my password Clicked save Got en ERROR - The same error as on the new server 1768 2017-08-17 14:39:18.000 General Error Error Code = The statement has been terminated. The conversion of a nvarchar data type to a smalldatetime data type resulted in an out-of-range value., StackTrace = at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) at System.Data.OleDb.OleDbCommand.ExecuteNonQuery() at Passwordstate.User.ResetUserPassword(String Password, String FormsPassHistory, Int32 PasswordStrengthIndex) Error
  12. No rush. Glad to help. Feel free to put debug info or anything else that might be useful. The database is empty, it's a fresh install.
  13. No problem. Just let me know what you need done and I'll do it. I'll have to do it later on tonight (my time) as I've got some family business to attend to. I'll send you my email in a private message and you can send me what needs to be done there.
  14. Hi again, Did you reinstall the web server from scratch or just change the culture via Powershell? The reason i ask is because i tried to change the culture on the server installed with the nb-NO culture to en-US via powershell (system wide) . Although it seemed to be applied system wide I still got the error when installing Password state. When i reinstalled the webserver from scratch and choose English - United States at the start of the Windows Setup everything worked as intended. So if your server was installed with en-US as the culture then I would presume everything would still work even if you changed the culture via Powershell to nb-NO. Anyhow. I have now tested by reinstalling the server (2016 server core) with our usual settings (English, Norwegian Bokmål, Norwegian). The database is using the Danish_Norwegian_CI_AS collation as before. Here is a Get-Host of the server. PS F:\Backup> Get-Host Name : ConsoleHost Version : 5.1.14393.206 InstanceId : 05f6fb6c-4a82-41a0-b32b-5e1ff62a2afb UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : nb-NO CurrentUICulture : en-US PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy DebuggerEnabled : True IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace CurrentCulture = nb-NO CurrentUICulture = en-US This time i didn't join the server to the domain in case there was some strange GPO at work. I then reinstalled passwordstate and i get the same error as before on the admin creation page. The conversion of a nvarchar data type to a smalldatetime data type resulted in an out-of-range value. I really have no idea. But seeing as you cannot reproduce the error even with a server installed with my culture settings I think we should just cut our losses and move forward. Having the server installed with en-US as the primary culture is fine. As i mentioned above it didn't cause any problems during testing yesterday, so I don't expect any problems going forward. I really do appreciate you taking the time to troubleshoot on your end. But I'm fully aware that Cultures and Languages other than English are not supported. I'll reinstall (yet again :)) with United States as the primary culture and get our new server up and running.
×
×
  • Create New...