Deploying myQueue with Group Policy
Install a myQueue for every user of your domain-joined Windows computers with a Group Policy startup script, using the installer script from the PriApps CloudPrint Console.
If your Windows computers are joined to an Active Directory domain, you can install a myQueue on them with Group Policy. A computer startup script runs the myQueue's installer script when each computer starts. Startup scripts run under the Local System account, which has the administrator rights the installer script needs, so the myQueue is installed for all users of the computer. If the myQueue is already installed, the script leaves it as it is.
Computers that are only Microsoft Entra joined don't receive Group Policy. Use Microsoft Intune for those. See Deploying myQueue with Microsoft Intune.
Before you begin
- Download the myQueue's installer script from the PriApps CloudPrint Console. See Deploying myQueue with Microsoft Intune, steps 1–3.
- You need to be a member of the Domain Admins group to add scripts to the domain controller's NETLOGON share and to create and link Group Policy Objects (GPOs).
Steps
Copy the script to NETLOGON
Copy the .ps1 file to the NETLOGON shared folder on your domain controller, for example \\yourdomain.com\NETLOGON.
Create a GPO
Open Group Policy Management. Right-click the organizational unit (OU) that holds the computers that should have this myQueue, for example the computers at one site, and select Create a GPO in this domain, and Link it here. Name the GPO, for example after the myQueue.
Open the startup scripts
Right-click the new GPO and select Edit. Go to Computer Configuration › Policies › Windows Settings › Scripts (Startup/Shutdown), and double-click Startup.
Add the script
On the Scripts tab, select Add, and enter:
| Field | Enter |
|---|---|
| Script Name | %SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe |
| Script Parameters | -NoProfile -ExecutionPolicy Bypass -File "\\yourdomain.com\NETLOGON\<script name>.ps1" |
The installer script isn't signed. -ExecutionPolicy Bypass lets it run, for this run of PowerShell only. Select OK, then OK again.
Restart the computers
The script runs the next time each computer in the OU starts. To test it on one computer first, run gpupdate /force on that computer, then restart it.
Check that it worked
On a computer in the OU, the myQueue appears in Printers & scanners for every user. To confirm the GPO was applied, run gpresult /r and look for it under Computer Settings. A job printed to the myQueue waits in the hold queue until the user releases it, and you can see it in Held Jobs. See Viewing held jobs.
The script doesn't make the myQueue the default printer. Users can do that in Printers & scanners. See Deploying myQueue manually.
-ExecutionPolicy Bypass. Make sure it allows the installer script to run on these computers.Related articles
Deploying myQueue with Microsoft Intune
Download a myQueue's PowerShell installer script from the PriApps CloudPrint Console and deploy it to your Windows computers as an Intune platform script.
Deploying myQueue manually
Install a myQueue on a Windows computer by hand, using its IPP address from the PriApps CloudPrint Console, so the user can print to it.
Creating hold queues
Create myQueue hold queues in PriApps CloudPrint, so users' print jobs are held securely in your cloud storage until they release them at a printer.