Frequently Asked Questions
To download and install Remote Desktop Audit please visit our Download page.
The latest version of Remote Desktop Audit supports the following Windows platforms:
Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012R2, Windows 10, Windows Server 2016, Windows Server 2019
To install and run Remote Desktop Audit, your computer will need the following minimum requirements based on your operating system:
No. To correctly install Remote Desktop Audit you must have administrative privileges. If you are going to use Remote Desktop Audit only on a local computer you must have local admin's privileges. If you are going to use Remote Desktop Audit throughout your network you must have domain admin's privileges.
Well, there are no functional limitations for unregistered versions and you may use Remote Desktop Audit (during the evaluation period) as a fully registered program but only on one computer in the network. In addition, unregistered versions of Remote Desktop Audit display nag screens.
The easiest way to purchase Remote Desktop Audit is to buy pay via one of our payment options and download the software immediately.
After making your purchase you will receive an e-mail with a registration number which you will use to activate your copy of Remote Desktop Audit. Click here to be directed to the ordering page.
For every installation on a separate machine an additional license is required.
If you have lost your license code you may request a copy be sent to you.
Please fill out the registration information request form.
Microsoft-Windows-TerminalServices-LocalSessionManager/Operational chanel is not available for Windows 2008.
Remote Desktop Audit supports Windows 2008R2 or newer.
By default, only administrators can view security event log. If you want to allow other users or group to view security event log, just add them to “BUILT IN\Event Log Readers” group and the task is accomplished.
If you want to view who has access to a given event log, try the below command
wevtutil gl security
wevtutil gl Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Also you may use SDDL to modify channelAccess according to your requirements.
However please read the following usefull article https://support.microsoft.com/en-ca/help/323076/how-to-set-event-log-security-locally-or-by-using-group-policy
There is no limitation to number of computers.