An HLK user account is automatically created for the person who installed the HLK Controller, and that account is granted administrator privileges within HLK. A person who has a HLK user account with administrator privileges is called a HLK administrator.
HLK administrators can create new HLK user accounts or modify the permissions of existing HLK user accounts.
Important
To create an HLK user account for a domain user, as opposed to a user account for a local user, you must be logged on to the HLK Studio computer as a domain user with administrator rights on the local machine.
If you try to create an HLK user account for a domain user while you are logged on as a local user with administrator rights, an error message will appear informing you that the user for whom you are trying to set up permissions does not exist in the domain. The domain referred to in the error message is the local machine and not the domain to which it is connected.
Assigning Roles
When you create a new user account for an HLK user, you must also assign a datastore role for the user.
The following is a list of the HLK datastore roles that you can assign a user when you create the new user account.
Role
Description
hlk_DSGuests
With a guest user account, you can log in without having a user account to access the HLK datastore. This level of access is very restricted and only allows the user to view the results of a job.
hlk_DSUsers
To obtain access to a Microsoft SQL Server database, you must have a corresponding user account for that database.
This user account allows the HLK user to perform several of the basic tasks associated with logo testing. See the permissions table that follows for more details
hlk_DSAdministrators
If a user is assigned this role, that user has administrator privileges on the local system and is able to install a system. Additionally, if the host computer is part of a Windows domain, the Administrator account usually has domain-wide privileges as well.
hlk_DSOwners
The datastore owner is a user that has permission to perform all activities in the database. See the permissions table that follows for more details.
To the HLK Studio user interface, the HLK_DSOwners and the HLK_DSAdministrators roles are the same. However, the level of access a user has to the HLK datastore itself when he or she is assigned the HLK_DSOwners role far surpasses the level of access a HLK_DSAdministrators user has. As such, you must only assign the HLK_DSOwners role to users who are very knowledgeable about Microsoft SQL Server.
Permissions Table
hlk_DSGuests
hlk_DSUsers
hlk_DSAdministrators
hlk_DSOwners
Schedule/Run jobs
X
X
X
Create Jobs
X
X
X
Edit Jobs
X
X
X
View Results
X
X
X
X
Delete Jobs
X
X
Cancel Jobs
X
X
Add Users
X
X
Remove Users
X
X
Creating a HLK User Account
From your controller, select Start>All Programs> Windows Kits>Hardware Certification Kit>HLK Manager.
Select Tool>Management Console.
In the left pane, expand Console Root.
For each of the listed datastores (WTTIdentity and HLKJobs), do the following:
Expand the datastore, right-click Users, and then click New User.
In the Datastore User Properties - New User dialog box, in the top pane, type the user name of the person you are creating a HLK user account for using the format domain\username, where domain is the user's domain or workgroup name, and username is the user's user name.
Note
If you are creating multiple user accounts, separate each user with a semicolon.
In the Datastore Role pane, select the HLK_DSOwners check box.
Warning
You can assign multiple roles to a new user at the same time. To grant this user administrator privileges, select the hlk_DSAdmins check box also.
Click OK.
Granting Permissions
Complete the following procedure to grant a HLK user permission to run jobs on a machine pool.
From your controller, select Start>All Programs> Windows Kits>Hardware Certification Kit>HLK Manager.
Select Explorers>Job Monitor.
Select your HLK controller from the drop-down list box at the upper-left corner.
In the Machine Pool pane, expand the machine pool hierarchy, right-click the machine pool that you want the user to be able to run a job on, and then click Properties.
On the Security tab, click Add.
In the User List dialog box, click the user name, and then click OK.
Warning
If the user name does not appear in the user list, the user does not have a HLK user account. Create the user account, and then give the user permission to run jobs.
In the bottom pane of the Properties dialog box, select the Execute Jobs check box and clear any check boxes for permissions that you don't want the user to have, and then click OK.
Protect your Active Directory environment by securing user accounts to least privilege and placing them in the Protected Users group. Learn how to limit authentication scope and remediate potentially insecure accounts.
As a Windows Server hybrid administrator, you integrate Windows Server environments with Azure services and manage Windows Server in on-premises networks.