Jump to content

Search the Community

Showing results for tags 'powershell'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Essentials
    • Announcements
  • Passwordstate 8.x
    • General Support
    • Feature Requests
    • Feature Requests - Completed
    • Known Issues
    • Installing Passwordstate
    • 3rd Party Hardware/Software Knowledge Forum
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • Mobile Client
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 7.x
    • General Support
    • Known Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google Plus Account


Location


Interests


Biography


Location


Interests


Occupation

Found 10 results

  1. Dear clickstudios team, could you please update your Powershell scripts to use HTTPS (-useSSL) as the default WinRM connection method and only fall back when the connection is not successful. Cheers Sebastian
  2. If you need to import all of your data from KeePass into Passwordstate, this is the preferred process due to the below Powershell script keeping the correct format of your KeePass database. We'd like to thank one of our customers Fabian Näf from Switzerland for writing this script for us. He did a great job and it's helped out many of our customers. This import process will create a Folder with the same name as the XML file you export from KeePass, and it will then replicate the KeePass structure beneath this. For customers not familiar with Passwordstate, the equival
  3. UPDATE: We have created a new thread that is a cut down version of this one, which is much simpler to follow. Please use this thread instead to import your KeePass data: https://www.clickstudios.com.au/community/index.php?/topic/2303-new-import-keepass-powershell-script-2018/ Purpose: The process below will import all of your KeePass data into Passwordstate. We highly recommend taking a backup of your Passwordstate database prior to performing this import. You can either use the automatic backup feature within Passwordstate, or possibly use SQL Management Studio To
  4. Hi again. As you have seen in today's other thread, I'm working on getting the password resetting for Windows to work without using local admin privileges. Whilst doing so, I've stumbled upon an error in the Windows local account password reset script "Set-WindowsPassword.ps1". I'm working with build 8180. After reducing the Powershell code to its bare essentials and running it on one of my test boxen, I've found that the relevant ScriptBlock contains a Write-Output that it really shouldn't, or that the test is written badly. Its current state leads to false positives.
  5. Hi just wanted to share my powershell script for importing passwords from Passwordmanager XP. We have a lot of passwords so we wanted to create different password lists depending on the folder structure in Passwordmanager XP. Make sure the first line is mapping the values to this line, you can change the Notes to Description if you prefer that. Title;Username;Account;URL;Password;Modified;Created;Expire on;Notes;Modified by But the only values we import is actually Title;UserName;Password;Description;URL;Notes they don't need to be in any particular order.
  6. This post describes how to set up an Active Directory account in Passwordstate, configured for Automatic Resets: Powershell Script: $PasswordstateAPIURL = "https://fabrikam.com/api/passwords" $jsonString = ' { "PasswordListID":"9914", "Title":"SCCM Service Account", "Username":"sccm_admin", "GeneratePassword":"False", "Password":"Welcome01", "APIKey":"63fca2537db89e4fb329546d7e83cab6", "ValidatewithPrivAccount":"False", "AllowExport":"True", "PasswordResetEnabled":"True", "EnablePasswordResetSche
  7. Purpose: Updates to the Chrome browser in the first half of 2017 has generated security warnings, if using the Self Signed certificate supplied with your original install of Passwordstate. This process generates and binds a new Self-Signed certificate that overcomes these new security warnings. Prerequisites: - Windows 8.1 or higher, Server 2012 or higher - Powershell 4.0 must be installed on your web server, preferably Powershell 5.0. To check which version you are running, open Powershell and type in $host. If you need to upgrade Powershell, you c
  8. Hello all. We have recently been reviewing our PowerShell scripts and decided to come up with a function our support staff can use when they want/need a password to be retrieved from Passwordstate. Now the below assumes you have the appropriate IP/Subnets defined and an appropriate API key to retrieve records. This is nothing special, but thought it may help others who are unaware the ease of retrieving records via Passwordstate. This requires PowerShell v3 to leverage 'Invoke-RestMethod' cmdlet. function Get-Password { <# Requires PowerShell v3 for Invoke
  9. Hi, I've been working with passwordstate and powershell to create an automated password management script. I've so far been able to create, retrieve, and delete passwords from our server, but am unable to update an existing password. I've been using the following code: $JSONSTRING = @{ "PasswordID"=$PWD_ID "PasswordListID"=$PWD_LIST_ID "GenericField2"="Active" } Invoke-Restmethod -Uri "$PASSWORDSTATE_SERVER/api/passwords" -Method PUT -ContentType "application/json" -Header @{"APIKey"=$APIKEY} -Body $JSONSTRING This syntax works for all the othe
  10. Hi, I'm wondering if the get-resources.ps1 discovery script is run from the database or from the c:\inetpup\passwordstate\setup\scripts folder. Reason I ask is because I want to change it by adding IncludePortInSPN parameter to the script, like this: $PSSessionOption = New-PSSessionOption -OpenTimeOut 3000 -IncludePortInSPN Only reason is because some applications need to have spn for http and when a remote powershell session is trying to open a connection to those computer it fails because the SPN points to port 80 for http instead of 5985. I've verified this by reg
×
×
  • Create New...