Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.

Support the ability to use AD Sites and Services for better AD query performance

We have a highly available AD environment with over 40 distributed domain controllers, many in remote sites with slow links connecting them to the data center.

In the current implementation of PasswordSafe, when connecting to AD it does a DNS query to determine the domain controllers for the AD domain. Whether that is a normal A record search or an SRV search, it does not take into account any setup of Sites and Services that may exist. As we do not use Windows for DNS, the results of the DNS query are just a round-robin list of all possible domain controllers for the domain.

Performance could be significantly improved if it was possible to configure each UVM with the appropriate site to use in an SRC record lookup, therefore restricting the searches to those local domain controllers. As it stands, the LDAP lookups for group information can take upwards of 20 seconds across a 600Mbps MPLS link to complete when a local LAN lookup takes less than 2 seconds. This causes considerable delay for users logging into BeyondInsight as well as to each DirectConnect session that they may initiate.

A simple modification to the lookup code to use something like:

nslookup -type=srv _ldap._tcp.<site>._sites.<domain>

Where the domain is a global setting, but the site could be specified on a per system basis.

  • Guest
  • May 13 2021
  • Future consideration
  • Attach files
  • Guest commented
    19 May 03:27am

    PWS does use site awareness. Have your AD Admin check their c:\windows\netlogon.log file for the site matching errors.