One of my flagship applications, AUP Informant runs at logon to display your acceptable usage policy to users and gather their responses. A basic message can aleady be shown using group policy but the idea behind this program is to extend this and give you:
- A rich, graphical usage policy using webpages that you can customise
- Different usage policies for staff and students
- Log files showing whether users have accepted or declined the policy
- Optional email notifications when a user declines your policy
- The ability to force a logoff if a user declines the policy
- The option to re-show the policy to users when the AUP is modified
How it works
The first time the user logs on, they are presented with your usage policy and asked to either accept or decline. The window cannot be moved or closed and the embedded browser cannot be modified.
If the user accepts, their response is saved to a hidden file and the window closes. However, if they don’t accept the policy, you may choose to receive an email notification, log them off, or both. In any case, the user will be warned of this and prompted to confirm their decision.
If the user has previously responded to the AUP, the window will not appear unless the AUP has been modified since they last gave a response. This automatic re-showing feature can be turned on and off according to preference.
Donate
If you find AUP Informant useful, please show your appreciation with a small donation. Your donation helps not only further development but also my university studies.
Donate £5 via PayPal | Donate £10 via PayPal | Donate £20 via PayPal
Screenshots
Main Window
Confirmation Screen
Downloads - v1.6.0
This is one of the simplest packages to install, requiring only a few steps. The package is entirely self-contained and, once configured, simply needs placing into your Applications folder on the server.
For vanilla networks, an MSI package is available too. It’s adapted from the latest CC3 package but will work fine without any RM software.
The core package includes the program files and a collection of scripts for deployment where central package management isn’t available, for example on imaged workstations.