

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Best way to release UFT concurrent license after script execution
I've just discovered that many of our UFT users kick off their test scripts (directly in UFT) just as they leave the office for the night. This is bad practive because once the script has finished running, UFT remains open and is using up one of our licenses unnecessarily.
What's the best solution to this please? I was hoping that changing the <LicenseAutoReleaseInterval> setting in C:\ProgramData\Hewlett-Packard\UFT\License\LicenseSettings.xml to 120 (2 hours) would work, but it doesn't seem to help.
I know that the users could instead use a VBScript script to run their tests from outside of UFT, or of course use ALM, but I'd like to know the best approach that allows maximum flexibility and minimal hassle.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Grahamengland,
Hope you are doing well.
I found below Enhancement Request to add support for: "License auto-release setting should release the license when only UFT is left idle, not the whole system "
this is still under investigation and will be consider for future releases.
At this moment Unified Functional Testing (UFT) by design cannot free up a license as long as it is opened and can communicate with the license server.
Customer Support Engineer
If you find thst aat this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the pond show your appreciation.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
In regards LicenseAutoReleaseInterval setting, it works when there is no user activity, meaning that the computer is not being used at all (it monitors all mouse and keyboard events); just minimizing UFT or having it idle won't work.
Since scripts are running overnight, are the users using any utility like Caffeine to keep the machine awake? This utility sends a keystroke every 59 seconds which avoids the idle state of the machine and will reset LicenseAutoReleaseInterval counter as well.
In the other hand, when running from ALM, you can configure UFT Remote Agent to automatically close UFT. For more information, review remote agent settings:
Kindly,
Alvaro