Logon Analyzer
Active Directory based!
Deployed in minutes!

Copyright © 2015 by VisionIT  · Privacy Policy · Terms Of Service ·  E-Mail: support@vision-it.org
THE CLIENT AS A POLICY OVERVIEW

The Logon Monitor Client can run as a process on one or more computers in your Active Directory. This process is started at boot time via a group policy in your Active Directory.

The Logon Monitor Client can be distributed over a workstation (windows XP, windows 7, windows 8 or windows 10), or a server (windows 2000, windows 2003, windows 2008 or windows 2012).

In order to create a policy that will distribute the Logon Monitor Client over one or more computers, you need to have the right to create that policy in your Active Directory, so first make sure you have started the console with enough rights (if need be, start the console via 'Run As' with high enough credentials).

First, if your forest consists of more than one domain, decide in which domain you want to create the Logon Monitor Client policy.

Then open 'Settings'. You have to provide the following information:

-- Policy Name. The name of the policy you are about to create.
-- Link To. You are going to apply the policy to computer objects in your Active Directory. Enter the Organizational Units in which these computers reside.
-- Apply To. Either enter the computers on which you want to apply the policy you are about to create, or click on 'Domain Computers' to apply the policy on all the computers in the Organizational Units you've entered under 'Link To'.
-- Logon Monitor Server. Enter the DNS Hostname of the Logon Monitor Server you have already created. The computers that get the policy applied, and start running the Logon Monitor Client as a process will send their information to this Logon Monitor Server.
-- Port Address. Here, enter the port address over which you want the Logon Monitor Clients to communicate with your Logon Monitor Server.

The computer part of policies are not refreshed. They are only implemented at boot time. And so, make sure that the computers you apply the policy to are rebooted. Only after a reboot will the Logon Monitor Client start running  as a process on the computers you selected.

Best practice: although you can create Logon Monitor Clients before installing your Logon Monitor Server, we recommend that you first install your Logon Monitor Server.

P.S.1 The option to enter alternative credentials does not allow you to create a policy under those new credentials. If you are logged on to your computer with credentials that do not allow you to create a policy in your Active Directory, restart the console via 'Run As' with credentials that will allow you to do so.

P.S.2 Make sure that you configure the firewall on your Logon Monitor Client computers so that they allow both inbound and outbound IP traffic over the port you select.