Audience: ClassLink Administrator
Requirement: ClassLink with active directory integration
In order to provide a more seamless and easier experience for younger students, they have the ability to sign into compatible Windows devices with ClassLink QuickCards.
1. ClassLink Management Console -> Single Sign-On ->QuickCard Management -> Windows Setup.
2. Click the Edit button for your domain.
3. Click the blue refresh button to generate an API key, if one has not already been generated. Copy the API key, as it will be needed later on in the Windows setup.
For Windows Username and Password, you have three options:
1. LaunchPad Username/Password
2. Roster Server sourcedId
If the users that will be using this feature have logged into the LaunchPad system previously, then you will want to select LaunchPad Username and LaunchPad Password.
Use the Custom option if you wish to set all users to log into Windows with a single username and password. Using custom is helpful as well if the domain name for your Windows QuickCard is different than the LaunchPad server domain. For example, the LaunchPad server is on domain District.org but the students log in to domain computers on the Student.District.org domain. In the screenshot below, add the domain name (NetBIOS domain name) followed by the username variable. Student\%adusername%
QuickCards for Windows on a Single Machine
To install the QuickCards Agent onto a single machine, you'll need your Tenant API key from the ClassLink Management Console.
1. Download the .MSI package to your desired location.
2. Run the .MSI package and input your API Key when prompted.
3. After installation completes, please restart your computer. When Windows starts up, you will have an option for QuickCard Login.
4. Upon successful login, the default browser will open to a LaunchPad session as the user associated with the scanned QuickCard.
QuickCards for Windows on Multiple Domain Computers
To install the QuickCards Agent onto multiple machines, you can use your preferred device management tool to deploy the MSI package. The MSI must be deployed with the following parameters in order to function as expected:
YOUR_API_KEY is the Tenant API key generated earlier in the ClassLink Management Console.
If you plan on using Group Policy to deploy the MSI package, we recommend creating a standalone policy object and applying it to an Organizational Unit that only contains the machines that will be using the QuickCards Agent.
First, download the MSI package and store it in a location on your domain that can be accessed by the target devices.
For the policy, you will want to set a startup script, found under Computer Configuration->Policies->Windows Settings->Scripts->Startup
Add a new startup script and set the script name field to the path on your domain where you are storing the QuickCardSetup.msi (e.g. NETLOGON)
Set the script parameters to the following, replacing YOUR_API_KEY with the Tenant API key generated earlier in the ClassLink Management Console.
After clicking OK, please allow time for the Group Policy changes to propagate, or run a forced update on the target devices. The target machines will also need to be rebooted.
Updated: Dec 2018