Migration from ADLink to Windows Agent
SchoolProtect Previous Setup
SchoolProtect previously used an application called ADLink. This was a previous version that schools pushed out via Group Policy, or by other methods, such as AD logon scripts. This has been replaced with the Windows Agent which brings improved performance, reliability and support for Intune-managed devices.
We strongly recommend that schools using ADLink migrate to the Windows Agent by following these steps.
The previous setup looked like the below, this is a Group Policy stating the logout, and an AD login script specifying the login:
To get a clean slate, it's advised firstly to remove the login.bat and the logout.bat from AD and GPO respectively. Once the Group Policy Object and the AD login script are gone, you can then import the files needed to set up the new workstation agent.
When editing, please note, if your domain controller is set up to read ADMX files from the local computer, you will need to change this to be from a central store. This is done by copying the Policy Definitions folder to the SYSVol folder on the domain. More information can be found in the official Microsoft guidance. You can tell if you're using a central store or local computer, by editing any GPO (Group Policy Object), then checking under Policies - Administrative Templates, to which you'll see the below:
To get the files you need to set up the new Workstation Agent, you can download the files you need from here.
Once you've got the files you need, you will have a folder, as per the below screenshot:
You then need to move the two ADM files across to your Policy Definitions:
In the SchoolProtect console, go to Policies - Policy Configuration, then either create a new policy, or you can edit an existing one. You'll need to set the target to Windows (Intune/GPO).
Once that's done, you'll see the config below your group:
Now back in your Group Policy, create a new Group Policy Object, and go to Computer Configuration - Policies - Administrative Templates. In here you'll see the object of LGfL. Open this up and you'll see the policy, which you can then import that config into.
New Group Policy Created called Workstation Agent:
Inside the Group Policy Object:
Adding the settings and Enabling the Group Policy Object:
Under the same group policy, if you go to Computer Configuration - Software Settings - right click New - Package, then point it to the msi that came with the group of files, you can installed the agent:
If you already have filtering specific security groups, to treat users differently in the same OU, you will need to do security filtering on your GPO's, to maintain this.