For any scenario, create a default User, and apply the default policy. It's advised that this user should be named according to the site name.

Scenario A 

Apply default policy to all users

STEP 1

1.1 Configure the default user which will be named according to the site name.

 - Make sure the policy is set to the default policy.

 - Make sure there is no IP set as this will then be defaulted to the dynamic IP.

STEP 2

2.1 Configure the default blocking policy in Protect Console>Policies.

STEP 3

3.1 Use the token ID for the default User (Created in Step 1), in the Protect Agent cfg.properties file.

STEP 4

4.1 Restart the Protect Agent service.

Scenario B 

Allowing access to everything for certain users and applying default policies to the rest of the LAN users.

STEP 1

1.1 Configure the default user which will be named according to the site name.

 - Make sure the policy is set to the default policy.

 - Make sure there is no IP set as this will then have defaulted to the dynamic IP.

STEP 2

2.1 Create the policy that will allow all. (Lets call it Directors)

STEP 3

3.1 Configure the Director user that will have access to everything.

 - Assign the Director policy to the Director user.

 - Add the IP's of the users that will have access to all.

 - Make sure the users have a static IP set.

STEP 4

4.1 Use the token ID for the default User (created in Step.1), in the Protect Agent cfg.properties file on the host server.

STEP 5

5.1 Restart the Protect Agent service.

Scenario C 

Have multiple sites you wish to configure on the same Protect Console (let's say 2 sites)

STEP 1

1.1 Configure the Protect Agent on all sites A and B.

STEP 2

2.1 Configure 2 users on the Protect Console - Name these users after each site.

*You are able to create different policies for each site or you can assign the default policy for each site.

STEP 3

3.1 Take site A Token ID and configure it in the cfg.properties file on site A.

3.2 Do the same with Site B.

STEP 4

4.1 Once all the sites tokens have been configured with the relevant site user, restart the Protect Agent for all the sites.