{"id":53733,"date":"2009-05-18T15:23:00","date_gmt":"2009-05-18T15:23:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2009\/05\/18\/hey-scripting-guy-how-can-i-document-printer-usage-on-client-workstations\/"},"modified":"2009-05-18T15:23:00","modified_gmt":"2009-05-18T15:23:00","slug":"hey-scripting-guy-how-can-i-document-printer-usage-on-client-workstations","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-how-can-i-document-printer-usage-on-client-workstations\/","title":{"rendered":"Hey, Scripting Guy! How Can I Document Printer Usage on Client Workstations?"},"content":{"rendered":"

\"Hey, <\/h2>\n

Hey, Scripting Guy! I am tasked with the problem of documenting printer use on our client workstations. I must be able to determine whether someone prints directly to a printer, or if they are printing through our print servers. This is important because we have purchased a print monitoring software package that is used to back-charge the departments for their printer usage. This software runs on the printer servers. If someone prints directly to a network printer through the IP address, the print job does not go through the print server, and therefore we lose the billing. I would love to spend a week going around to each client in our office building, chatting with the users, and looking at their printer settings. Unfortunately, the boss nixed that idea. I told him the revenue we regained would pay my salary for the week, but he was not swayed. He suggested I contact you and ask for help with script ideas.<\/p>\n

– LB<\/p>\n

\"Spacer\"\"Hey, <\/p>\n

Hi LB,<\/p>\n

What a refreshing e-mail message. It sounds as if you are serious that you would enjoy a week spent talking to users, you would be surprised how many e-mail messages we receive from IT pros who seek to avoid users. Even your boss seems to be a wise and wonderful person. Last week was a rather eventful week at Tech\u00b7Ed. Ed gave a Windows PowerShell presentation on Friday. Both Ed and Craig talked to thousands of adoring fans and were hounded by autograph seekers all week (some of this sentence uses exaggeration). Needless to say, we are beat. So we are catching up on e-mail, and Ed is mellowing out sipping an excellent cup of Darjeeling tea<\/a> perfectly brewed in my little tea pot with freshly drawn spring water. Two spoons of fresh leaves, seasoned with a stick of Ceylon cinnamon<\/a>. Ed is also listening to Earth, Wind & Fire<\/a> on his Zune. Life is good.<\/p>\n\n<\/thead>\n\n\n
\n

This week we will examine printing. There are lots of resources related to printing on the TechNet Script Center. There is a collection of Hey, Scripting Guy! articles<\/a> that lists 24 articles relates to both server-side and client-side printing. We have almost 50 scripts in the printer section<\/a> of the Script Center Script Repository<\/a>. There are also almost 50 scripts in the printer section<\/a> of the Community-Submitted Scripts Center. We have some good technical information about printing in the Scripting Guide<\/a>. All those resources are in VBScript. To use them in Windows PowerShell, you would have to translate the scripts into PowerShell. The Microsoft Press book, Windows PowerShell Scripting Guide<\/a>, has a whole chapter devoted to printing.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/div>\n

You can use WMI to get the printer information that you must have. We wrote a script named GetLocalAndNetworkPrinters.ps1<\/b> in Windows PowerShell for you. A VBScript that provides a similar capability is developed in the \u201cHow Can I List All the Printers on a Remote Computer?\u201d<\/a> Hey, Scripting Guy! article. The complete GetLocalAndNetworkPrinters.ps1<\/b> script is seen here:<\/p>\n

$computer = \"localhost\"Write-Host -foregroundcolor Yellow \"Printer report for $computer...\"Get-WmiObject -class Win32_Printer -computername $computer|Foreach-Object -Begin {$NetworkPrn=$localPrn = @{\"Name\"=\"PortName\"} } ` -Process {  if($_.Local)    {       $localPrn += @{ $_.name = $_.portname }    } #end if if(-not $_.Local)   {   $NetworkPrn += @{ $_.name = $_.portname } } #end if} #end foreach-object process# *** Generate Report ***if($localPrn.count -gt 1){ Write-Host -foreground cyan \"There are $($localPrn.count -1) Local printers on $computer\" $localPrn | Format-Table -auto -Hide -wrap}Else { \"No local printers detected on $computer\" }if($networkPrn.count -gt 1) {  Write-Host -foregroundcolor green \"There are $($networkPrn.count -1) Network printers on $computer \"  $networkPrn | Format-Table -auto -Hide -wrap }Else { Write-Host -foregroundcolor red \"No network printers detected on $computer\"} #end else<\/pre>\n
Are you still here? Good, let’s dig into the GetLocalAndNetworkPrinters.ps1<\/b> script and see whether we can determine what makes it tick. The first thing we have to do is create a variable $computer<\/b> to hold the name of the computer. We set the default value to localhost<\/b>. This is a better name to use for the local computer than the period (“.”) that is frequently seen in WMI scripts. This is because, when the report is displayed, a printer report for localhost<\/b> reads better than a printer report for a “period.” We use the Write-Host<\/b> cmdlet to print the text in yellow:<\/p>\n
$computer = \"localhost\"Write-Host -foregroundcolor Yellow \"Printer report for $computer...\"<\/pre>\n
Now we use WMI to obtain the printer information. The Win32_Printer<\/b> WMI class provides this information. To query from WMI, use the Get-WmiObject<\/b> cmdlet. More information about WMI can be found in our new WMI Scripting Hub<\/a>. The resulting management objects are pipelined to the ForEach-Object<\/b> cmdlet:<\/p>\n
Get-WmiObject -class Win32_Printer -computername $computer|<\/pre>\n
Next we use the ForEach-Object<\/b> cmdlet to work our way through the detailed printer information that was returned from the Win32_Printer<\/b> WMI class. We use the \u2013Begin<\/b> parameter from the ForEach-Object<\/b> cmdlet to perform an action once for the entire pipeline. We create two hashtables. One is stored in the $networkPrn<\/b> variable and the other in the $localPrn<\/b> variable. The hashtables contain one key and one value: Name<\/b> and PortName<\/b>. We will use these for column headers in our report:<\/p>\n
ForEach-Object -Begin {$networkPrn=$localPrn = @{\"Name\"=\"PortName\"} } `<\/pre>\n
The tasks that will be performed once for each item on the pipeline go into the \u2013process<\/b> parameter of the ForEach-Object<\/b> cmdlet. Inside the \u2013process<\/b> parameter, we examine the value of the Boolean property Local<\/b>. If the Local<\/b> property is set to true, it exists. This is shown here:<\/p>\n
 -Process {  if($_.Local)    { <\/pre>\n
We add the name of the printer and the port name to the hashtable stored in the $localPrn<\/b> variable if the Local<\/b> property is set to true. To add items to the end of the hashtable, we use the +=<\/b> operator. This is seen here:<\/p>\n
      $localPrn += @{ $_.name = $_.portname }    } #end if<\/pre>\n
If the Local<\/b> property does not exist, it means the printer is a network printer: <\/p>\n
 if(-not $_.Local)   {<\/pre>\n
Again, we have to add the name of the printer and the port name to the hashtable. This time, the hashtable is stored in the $networkPrn<\/b> variable. This is seen here:<\/p>\n
   $networkPrn += @{ $_.name = $_.portname } } #end if} #end foreach-object process<\/pre>\n
After you create the two hashtables, it is time to produce the report. Each hashtable is seeded with the name<\/b> and the portname<\/b> strings in the first row of the hashtable. This means that if no printers are found, the hashtable will have a count of 1. If the hashtable has a count greater than 1, a printer is detected and we want to display the report. This is seen here:<\/p>\n
if($localPrn.count -gt 1){<\/pre>\n
Then we use the count<\/b> property from the hashtable<\/b> object to provide information about how many printers are defined on the computer. We must use $localPrn.count-1<\/b> because of using the first row of the hashtable as a header for our report. We have to use a subexpression, which is a $()<\/b> around the $localPrn.count<\/b> to force the evaluation of the count<\/b> property before trying to display it as a string. If we did not do this, we would be greeted with something that looks like this:<\/p>\n
There are System.Collections.Hashtable.count -1 Local printers on localhost<\/pre>\n
This is also known as unraveling<\/i> because the name of the object that is displayed in the variable is displayed instead of the value that is contained in the variable. The subexpression is one way to deal with the problem. This is seen here:<\/p>\n
 Write-Host -foreground cyan \"There are $($localPrn.count -1) Local printers on $computer\"<\/pre>\n
The other way to deal with the problem of unraveling is to avoid it completely and use concatenation on a literal string instead of using the expanding string. The confusing aspect is that, because you are using the Write-Host<\/b> cmdlet, you do not have to use the concatenation operator (+<\/b>). This is seen here:<\/p>\n
Write-Host -foreground cyan 'There are ' ($localPrn.count -1) ' Local printers on ' $computer<\/pre>\n
To display the printer information, we use a really cool trick. We pipeline the hashtable<\/b> object to the Format-Table<\/b> cmdlet. This will enable us a measure of control over the display. In particular, we want to automatically size it, hide the table headers, and wrap the long field printer port names to avoid cutting them off on the display. This is shown here:<\/p>\n
 $localPrn | Format-Table -auto -Hide -wrap}<\/pre>\n
If no local printers were detected, we display a message telling the user that there are no local printers:<\/p>\n
Else { \"No local printers detected on $computer\" }<\/pre>\n
Now we perform the identical steps for the network printers:<\/p>\n
if($networkPrn.count -gt 1) {Write-Host -foregroundcolor green \"There are $($networkPrn.count -1) Network printers on $computer \" $networkPrn | Format-Table -auto -Hide -wrap }Else {Write-Host -foregroundcolor red \"No network printers detected on $computer\"} #end else<\/pre>\n
That is all the moving parts involved in the script. When you run it, you are greeted with a display that resembles the one shown here (of course, the display that is seen after you run the script depends on your printer configuration):<\/p>\n
\"Image <\/p>\n
 <\/p>\n
Well, LB, that is all there is to producing a listing of local and network printers from your workstation. It should work on a remote computer as well as on a local computer. You just have to change the name of the destination computer. I have to go unpack, and then I plan to hit the treadmill. Too much good Tech\u00b7Ed food. See you tomorrow when Printer Week continues. Until then, peace.<\/p>\n
 <\/p>\n
Ed Wilson and Craig Liebendorfer, Scripting Guys<\/b><\/p>\n","protected":false},"excerpt":{"rendered":"
Hey, Scripting Guy! I am tasked with the problem of documenting printer use on our client workstations. I must be able to determine whether someone prints directly to a printer, or if they are printing through our print servers. This is important because we have purchased a print monitoring software package that is used to […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[445,404,3,5,45],"class_list":["post-53733","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-client-side-printing","tag-printing","tag-scripting-guy","tag-vbscript","tag-windows-powershell"],"acf":[],"blog_post_summary":"
Hey, Scripting Guy! I am tasked with the problem of documenting printer use on our client workstations. I must be able to determine whether someone prints directly to a printer, or if they are printing through our print servers. This is important because we have purchased a print monitoring software package that is used to […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/53733","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=53733"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/53733\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=53733"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=53733"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=53733"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}