Jump to content

Search the Community

Showing results for tags 'script'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Essentials
    • Announcements
  • Passwordstate 9.x
    • General Support
    • General Hints and Tips
    • Known Issues
    • Installing Passwordstate
    • Feature Requests
    • Feature Requests - Completed
    • 3rd Party Hardware/Software Knowledge Forum
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • App Server
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 8.x
    • General Support
    • Feature Requests - Completed
  • 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 3 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. 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
  3. 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...