Getting ready

To deploy a printer to a client, you first need a client computer system. Our demo lab includes a Windows 10 Enterprise client (SG-CL1), which we use in this recipe. To test this recipe, you need the client computer, the print server (PSVR), and the domain controller (DC1).

Once you create the client, you can run the following commands to add it to the domain in the Sales OU (created separately):

    $Cred = Get-Credential 'Reskit\administrator' 
    # you enter the password
    $OUPath = 'OU=Sales, DC=Reskit,DC=Org'
    Add-Computer -DomainName 'Reskit' `
                 -DomainCredential $cred

Next, you need a Group Policy object that deploys the logon script. The easiest way to create this Group Policy Object (GPO) is to use the GUI-there are no PowerShell cmdlets (or WMI/.NET objects) that can help.

To create the GPO, you use the Group Policy Management Console (GPMC) tool. This tool is part of the management tools for Active Directory, and is also part of the Remote Server Admin Tools (RSAT) that you can download for client systems. Once you install the GPMC, you can run it and expand the domain to make our Sales OU visible:

Next, you right-click the Sales OU, specify the Group Policy Name, and click OK:

With the GPO created, right-click the GPO and select Edit:

This brings up the Group Policy Management Editor. Select the User Configuration | Windows Settings | Scripts (Logon/Logoff):

Then double-click Logon to bring up the Logon Properties dialog, and then click on the PowerShell Scripts tab:

From this dialog, click on Add to bring up the Add a Script dialog:

From this dialog, enter the Script Name Sales Group Logon Script.ps1, then click on OK, which brings up the Logon Properties box with the script shown here:

Note the file name in this dialog box. This file (Sales Group Logon Script.ps1) is a file within the Logon Script folder inside the GPO object in your SYSVOL folder on your domain controller. The path for the Logon Script folder was Reskit.Org\SysVol\Reskit.Org\Policies\{CF4F8264-0FD7-4D21-8267-8F36D7CE3DCF}\UserScripts\Logon. If you are testing this, you should see a different GUID in this path.

From the Logon Properties dialog, click OK to close the dialog, then close the GPMC editor. These steps have created an empty logon script. You can add the content for this logon script by going through the following recipe.