Jump to content

Search the Community

Showing results for tags 'discovery'.



More search options

  • 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
  • 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 4 results

  1. We're running v8.4, Build 8459. We have discovery jobs set to run at specific times (e.g. "Weekly - 01:00"). When running an on-demand discovery, the job's schedule is changed to one minute in the future and the frequency is reset to daily (see example). My feature request: Ability to run on-demand jobs without affecting the previously established schedule. I mean, the workarounds are to create a new discovery job as a one-off, or go back and update the schedule after. Neither is particularly desirable. It would be great if we could run on-demand discoveries while not affecting the defined schedule--or even as a compromise, could the ad-hoc job at least maintain/honor the defined frequency (daily/weekly/etc)? Thanks. -Geoff
  2. Hi guys, Many thanks for all your quick replies and help so far! Sorry for seemingly spamming the boards with my questions I'd like it very much, if the host discovery jobs offered a feature similar to the account discovery jobs: automatically adding the discovered objects to a specific list. For example, I'm working with something like an "Unprocessed" list for newly discovered accounts, so we can have some form of queue for our administrators. I'd like something similar for the hosts. Along other lines, the hosts menu right now only shows hostnames when they're part of a list. Hosts that are not yet in a list don't show up in the menu-bar. Hence why I also would like the option to auto-add to a list. It's not a world-shaking feature and I'm sure my wants stem from an as-of-yet-sub-optimal workflow... But heck, if you can fit it on the backlog somewhere near the bottom, that'd be great
  3. Hi we have some Redhat Linux servers in our AD and they have no OS defined in the AD so we can't auto find them. As we have many such test servers we can't manually input them. As I have to define OU it should be no problem to import all computers found in this OU regardless of OS.
  4. Hi, I am wondering if there is a best practice for this situation: We want to use discovery and automated password management for local admin accounts and resources (service accounts and so on), but unfortunately not all systems can handle automatic password changes. Is there a way to use discovery and manually selecting the accounts that can be managed by the password reset scripts? Thanks in avance, Jasper
×
×
  • Create New...