Loading Staff - AD Batch Staff Load Program

            VisitorRego has made available a program to batch load staff from your company's Active Directory using a scheduled background windows task.

            To use this program, the PC you are wanting to use to run this program will need to be able to 'talk' to both your Active Directory AND the VisitorRego database.

            The program is part of the VisitorRego install set. You can download this set

            (See: Install Section for a guide to installing Visitorrego)

            Install Visitorrego
            In the directory C:\Program Files\VisitorRego.NET, there are two files:
            1. ADUpdate.exe
            2. ADUpdate.cmd
            If you look in the .cmd file, you will see the parameters that the .exe accepts.

            "C:\Program Files\VisitorRego.NET\ADUpdate.exe" "SiteID=0" "ADDomain=dc=VisitorRego,dc=local" "LDAPQ=(&(objectCategory=user)(objectClass=user)(l=Auckland))" "DELETE=YES" "LOGGING=YES"

            These parameters are:


            This is the SiteID that staff will be loaded into. SiteID "0" is the Site where in a multi site database, all staff are loaded and referenced by all sites - Load Staff Across All Sites. If you are loading to a specific site then you need to know the SiteID from the site table in the database.


            Specifies the name of the AD domain.


            Specifies the LDAP query.


            YES= when finished loading staff, delete any staff records that haven't been updated. This allows you to run ADUpdate any number of times with "DELETE=NO"; then on the last run specify "DELETE=YES" to delete staff that are no longer in the Active Directory.


            YES= Write logging information to the Windows Aplication log file.

            You will notice that there is no database information in the parameter list. this is because ADUpdate.exe reads the file DBPara.dll which contains all the database connection and credentials information.

            This file can be opened using Notepad. We use this file to hold database connection and credentials as we want this information to remain the same across local user profiles.

            To Test - Install and open VisitorRego on a local PC (not the VisitorRego appliance) and point it to a local Microsoft Access database - this process with update the connection string in the DBPara file.

            Then test ADUpdate.

            Updated: 14 Jul 2018 09:35 AM
            Help us to make this article better
            0 0