Introduction
This is a guide to deploying the Quickpass Agent via Microsoft Group Policy for On Premise Active Directory Environments via Command Line
Prerequisites
- Customers created in the Quickpass Dashboard
- Group Policy Understanding
- Domain Admin rights to the Domain you are configuring the Group Policy
- Modify the attached script and confirm it works for your customer.
- Update the InstallToken and AgentID IDs hard coded PER Customer
- Ensure that you have reviewed and understand the Install Token and Agent ID Values
https://support.getquickpass.com/hc/en-us/articles/360061942274-Export-Customers-List-Status-and-Agent-ID-s - Review the Scripted Agent Installation KB Article to understand what each Powershell Parameter will do
https://support.getquickpass.com/hc/en-us/articles/4413576799639-Scripted-Agent-Installation
- This process describes how to use the "System" Account to Install as Administrator however any account can be used that has Administrator Privileges.
Implementation
Prepare the script
- Copy and modify the script here.
- Alter the "OUTPUTPATH" value to a Folder you want to store the installer EXE
- Alter lines 9 & 10 with the InstallToken and Client Agent ID values.
- Copy that script to a File Share or use a GPO Startup Script Location
- If using a File Share make sure that the DOMAIN COMPUTERS security group has access to that Share and Folder
- You can use the SysVOL share which all Domain joined systems have access to. See the Group Policy section (Step 7) below for these instructions.
Create a GPO to Push to Domain Systems via Command Line
- Log on to a Domain Controller as a Domain Admin
- Open the Group Policy Management Console for the Domain
- Decide what OU level you want this to be configured for
- You can use a Sub OU to run a test on a sample set of Computers (this is a Computer Based Group Policy) or you can set the Policy at the Root of the Domain and specify a Security Group Containing the computers you want to trial this for.
- Once your Proof of Concept has been confirmed to work, then you can add the Group Policy to other OUs or add additional computers to the Defined Security Group
- Right click the location you want to start configuring this Policy on and select "Create a GPO in this Domain and Link it Here
- Name the GPO something appropriate for what you are trying to accomplish
- Right Click that new GPO that you created and Select Edit
- If you want to use the SysVol location to store the PowerShell script to execute, please follow these steps. If using a File Server/Shared Folder please move on to Step 8.2
- Expand Computer Configuration -> Policies -> Windows Settings -> Scripts (Startup/Shutdown)
- Double Click Startup
- Click Show Files
- Paste the tested script into this Folder and close the File Browser window
- Click Add Button -> Browse
- If you are using SYSVOL/GPO folder click on the file that appears (it should be there because you pasted it in on step 7.4)
- If you are using a File share to store the script file - browse to that location VIA UNC Path (Drive Map/File Path will not work)
- Click OK until you have cleared all the open Windows and then close the Edit GPO screen.
- You can limit the Security Filtering for this Start Up Script if you want to further limit which systems you are applying this to.
- You can also use WMI Filtering if you are familiar with the configuration.
- Now you can test on a sample set of systems in that OU by restarting them
- Create a Security Group and add a few Computers to that Group (remember this Policy applies to the Computer not the user)
- In the Security Filtering section of the Policy you just created click ADD and add that newly created Group to the list.
- Once you have tested that this works on those machines, you can remove the Group entirely from the Security Filtering List or add additional machines to the Group or Link the GPO to other OUs.
Troubleshooting
- This script will check and output to a log file in the path you specified for the installer to be stored.
- Does the Quickpass Agent Service exist (it doesn't check if it's running)?
- If so it skips the entire process - this makes sure it doesn't install over and over again. This overwrites the log file.
- Outputs all steps performed to the Log file. Review this if you have any challenges.
- Does the Quickpass Agent Service exist (it doesn't check if it's running)?
Comments
0 comments
Please sign in to leave a comment.