A common problem with using a client that multiple users log into is that a sensitive document could be stuck in the local print queue. With law suit heavy lawyers running around, you do not want to put your organization at risk. The below procedure will help to mitigate this issue. (Note: The following procedure is performed and tested on Windows 7) This procedure will set up your clients to clear their print queues when a user logs off. This prevents the printer from coming online and printing sensitive information when another user logs on.
Copy and past the following code:
net stop spooler
net start spooler
Click File \ Save As
In the Save as Type: dropdown box, select All FIles.
In the File name: box, type C:\DeletePrinJobs.cmd.
In a production environment, you may want to put this somewhere other then the C: drive. The above batch file will clear out any stuck printouts in the print queue on the local client when it the batch file is ran. To test this, I created two fictitious printers. One is the default printer, the other is not.
I sent test pages to both. Right now we have documents pending in both queues. When the batch file was ran, both queues emptied. To get this to happen each time a user logs off, you need to place it in a log off script.
You need to save the script in a location that all users will have access to. Also, you want this script replicated to all domain controllers. to do this, save it in the following location on a domain controller
Now, we need to modify a Group Policy to deliver this instruction to your clients.
On a Domain Controller, click Start \ Administrative tools \ Group Policy Management
Expand Forest:<YourDomainName>\Domains\<YourDomainName>\Group Policy Objects
Right click Group Policy Objects and click New
Give the GPO a name.
Right click the GPO you just created and select Edit
Expand User Configuration \ Policies \ Windows Settings
Click Scripts (Logon/Logoff)
Click Double click Logoff
You need to access the script through the namespace of your network. This ensures that any client requesting the script will get it from their local Domain Controller. For example, if your domain is Contoso.com, you would look in the location \\Contoso.com\SysVol\Contoso.com\scripts
Click the script that you created and then click Open
Close the policy.
From here you will have to apply the GPO according to your company policies.
Once the GPO is applied, each time you users log off the client, any printouts in the local print queue will be deleted.