Export Registry Printer Information<\/b><\/p>\n
I came across this post http:\/\/www.oncallpros.com\/2011\/11\/02\/powershell-export-your-print-configuration-from-registry\/ on exporting printer information from the registry in PowerShell. I wanted to offer some constructive suggestions but could find no way to comment so I'll do so here.<\/p>\n
First, the article introduces some good PowerShell concepts. I like that he is using Test-Path. Although I'd suggest using Join-Path instead of concatenation. I also like the use of Write-Host to display progress. An even better approach for a future version might be to use Write-Progress. I'm going to see about using that more myself as I think it is a cmdlet that doesn't get the attention it deserves.<\/p>\n
But my main concern with the script is that it feels too much like VBScript and parsing text. He's not really taking advantage of the PowerShell pipeline. The core command can be this one line command.<\/p>\n
get-childitem HKLM:SYSTEMCurrentControlSetControlPrint -Recurse |
get-itemproperty |
select @{Name="RegKey";Expression={Convert-Path$_.pspath}},* -exclude PSParentPath,PSChildname,PSProvider,PSPath <\/p>\n
I wasn't looking for a one line command, it just turned out that way. <\/p>\n
Personally, this is the code that I would put in the script because it writes objects to the pipeline. Now I have options. If I want a formatted text list I can do it:<\/p>\n
PS C:> c:sciriptsget-printerregistry.ps1 | format-list | out-file printers.txt<\/p>\n
Or perhaps today I need it as an xml file I wan reimport later.<\/p>\n
PS C:> c:sciriptsget-printerregistry.ps1 | export-clixml printers.xml<\/p>\n
The point is to offer flexibility and think objects in the pipeline.<\/p>\n
On a more personal (pet peeve) note, if you are going to post code samples more than a few lines long, please, please offer a text file download. Copying and pasting code from websites is ugly and time consuming.<\/p>\n
So, look at the original post and look at my suggestions. What do you think?<\/p>\n
Powershell \u2013 Export your print configuration from registry | On-Call Pros, LLC<\/p>\n
I was asked to produce this script for follow up checking of driver versions later on or possible settings which can cause problems. \u00a0 The idea would be that a master file is updated on a website and ...<\/p>\n","protected":false},"excerpt":{"rendered":"
Export Registry Printer Information I came across this post http:\/\/www.oncallpros.com\/2011\/11\/02\/powershell-export-your-print-configuration-from-registry\/ on exporting printer information from the registry in PowerShell. I wanted to offer some constructive suggestions but could find no way to comment so I'll do so here. First, the article introduces some good PowerShell concepts. I like that he is using Test-Path. Although I'd…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[322,4,110],"tags":[534,560,540],"class_list":["post-1811","post","type-post","status-publish","format-standard","hentry","category-google-plus","category-powershell","category-registry","tag-powershell","tag-registry","tag-scripting"],"yoast_head":"\n