IT Departments debate over Server-based and IP-based direct printing. I use IP-based printing as a way to lower WAN traffic, negate at least two points of failure, and speedup user response/print time. Microsoft has developed some fine printer scripts they introduced in Windows XP. They further polished these scripts in Windows 7 and placed them into their own printing_admin_scripts subfolder. I'm sharing my sample script and giving a quick explanation of each command. For more details about the Microsoft VB script switches, visit Microsoft's TechNet site or use Notepad to read the syntax notes placed inside each VBS file.
REMARK --- Start of Script ---
REMARK Added a script title so I know what printer I'm installing
echo *** Installing Canon iPF720 Plotter ***
REMARK Remove old printer presence via PowerShell registry search
PowerShell "if (test-path 'hklm:\software\microsoft\windows NT\currentversion\Print\Printers\HP DesignJet 1050C Plotter'){cscript c:\windows\system32\printing_admin_scripts\en-us\prnmngr.vbs -d -p 'HP DesignJet 1050C Plotter'}"
REMARK Checking for processor type then installing appropriate driver
REMARK AMD64 works with all typical Windows useable 64-bit processors
if %processor_architecture% equ AMD64 (cscript c:\windows\system32\printing_admin_scripts\en-us\prndrvr.vbs -a -m "Canon iPF720" -h "\\server\share\Printers\Drivers\Canon iPF720\64-bit\Driver" -i "\\server\share\Printers\Drivers\Canon iPF720\64-bit\Driver\6WJF02M.INF") else (cscript c:\windows\system32\printing_admin_scripts\en-us\prndrvr.vbs -a -m "Canon iPF720" -h "\\server\share\printers\Drivers\Canon iPF720\Driver" -i "\\server\share\printers\Drivers\Canon iPF720\Driver\2WJF02M.INF")
REMARK Adding the IP port the new printer will use
cscript c:\windows\system32\printing_admin_scripts\en-us\prnport.vbs -a -r "CanoniPF720" -h 192.168.1.100 -o raw -n 9100
REMARK Putting the Friendly name, driver, and port together
cscript c:\windows\system32\printing_admin_scripts\en-us\prnmngr.vbs -a -p "Canon iPF720 Plotter" -m "Canon iPF720" -r "CanoniPF720"
REMARK Added a 10 second pause so I can chain install scripts together yet still monitor each installation progress
timeout /t 10
REMARK --- End of Script ---
I also thought about adding an audible prompt when things go right or wrong. This would lessen the need to physically watch the install but rather allow multitasking by listening out for the correct sounds after each install while performing other duties.
I learned how to insert Headers into an Inoke-RestMethod request in order to pull music information from an online database. Afterwards, I can insert the received objects into MP3 ID3 tags using methods mentioned in my previous posts (including album covers). I recently started using Decibel for grabbing music information (even though indications are that they're going to a pay-only API). As of now, they have a free version and two paid versions which allow more information about each query. When you create a free account, you'll be requested to make an application. I called my application "PowerShell." The system generated an Application ID & Key. New to me was having to pass this Application ID, Application Key, and Date/Time via a header request when making my PowerShell queries. After many web searches and trying different script methods, I'm sharing my successful script:
#Replace the x's with your Applications information
#Using an artist like "Fine Young Cannibals" will search for artists
#that have any or all of those three words
$DAppID = "xxxxxxxx"
$DAppKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
[string]$DTimeStamp = get-date -format "yyyyMMdd HH:mm:ss"
$Artist = "Metallica"
#Decibel documention
#I requested all albums that have Metallica in the artists name field
$query = invoke-restmethod http://api.decibel.net/v1/albums?artist=$Artist `
-headers @{"DecibelAppID"=$DAppID;"DecibelAppKey"=$DAppKey;"DecibelTimestamp"=$DTimeStamp;} `
-method get
$result = $query.AlbumQueryResult.ResultSet.album
# I filtered for only Metallica album names
foreach ($r in $result){$r.Name|where-object{$r.Artists -eq $Artist}}
I needed to bundle the SCCM/SMS 2007 ConfigMgr web reporting results into PowerShell or Excel. The SMS Web Reporting has a great export-to-CSV tool on each page but runs Java in the background and requires a confirmation click and a subsequent filename before being able to download the CSV file. Once downloaded, it quickly becomes a PowerShell object via import-csv. After lots of searching, I compiled a method to automatically download and save the CSV file so it can be used by PowerShell.
#Set the variables
$xhttp = $nul
$stream = $nul
$username = "domain\username"
$password = "password"
$url = 'http://sccmserver/SMSReporting_bob/Report.asp?ReportID=386&Name=MyPcName'
$destination = "c:\users\myname\desktop\MyPcName.csv"
#Start XML
$xhttp = new-object -com msxml2.xmlhttp
$xhttp.open("Post",$url,$false,$username,$password)
$xhttp.setrequestheader("Content-Type","application/x-www-form-urlencoded")
#this sends the request to perform a CSV export
$xhttp.send("export=yes")
#This line's not needed but I use it to get confirmation
#that the download is queued correctly. If not OK then
#I know to check the above part of this script
$xhttp.statustext
#Now grab the file in the buffer and save it to disk
$stream = new-object -com ADODB.Stream
$stream.open()
$stream.type = 1
#Connect the buffer to the downloaded file
$stream.write($xhttp.responsebody)
$stream.savetofile($destination,2)
$stream.close()
$stream = $nul
References:
http://myitforum.com/cs2/blogs/jnelson/archive/2008/04/02/114527.aspx
http://www.greyhathacker.net/?p=500
http://scriptolog.blogspot.com/2007/08/query-http-status-codes-and-headers.html
This technique bypasses the need to load the Active Directory module and has been tested in PowerShell 2.0 & 3.0. The CN= reference can be either a computer or user. This script connects to your domain and searches for an object you assign via the variable $oldcomp. You can also change the objects properties once found in AD. That's described in the second part of the script.
#Grab your local domain for ADSI
$searcher = [adsisearcher][adsi]""
#Create $oldcomp however you like then use it as input for the ADSI searcher
$searcher.filter ="(cn=$oldcomp)"
#Search Active Directory for the current location of the computer object
$searchparm = $searcher.FindOne()
#Assign $deleteoldcomp to the found path
$deleteoldcomp = $searchparm.path
#Assign the ADSI object to a variable
$delcomp = [adsi]("$deleteoldcomp")
#I used the Try/Catch sequence in case the computer wasn't found in AD.
#the deletetree() removes the object from the domain, not the computer
#itself. Stop here if you only want to find the object and then edit its
#properties. If you wish to delete it, then add this next line:
try {$delcomp.deletetree()}catch{}
After you have found the computer object, you are able to edit its properties. If you take the $delcomp object and type $delcomp|format-list * then you'll see information about your object. To change your computer object properties:
#To change the computer description property
$delcomp.description = [string]"Whatever String Value you want"
#To assign a technician in the ManagedBy property, copy/paste the
#technicians user object
$delcomp.managedby = "CN=TechnicianUserID,OU=..."
Use the same technique to assign other property values. When you are finished, you'll need to save your changes back to the computer object. Ensure your account has the correct credentials.
$delcomp.setinfo()
This stunning illustration summarizes how death occurred during the 20th century. With numerous advances in the medical/technological fields, we'll see a vast reduction of health-based deaths in the 21st Century. Already there are great strides taken to create 3D printed replacement tissue and organs. We can convert skin cells into stem cells and use them to repair body components. Combined with technological breakthroughs with nanobiotics, the likelihood of dying from "natural" causes will dwindle as the century advances on. It is my hope that these advances will motivate societies to quit destroying each other (or themselves) and focus on humanity and the advancement of it.
Visit Data is Beautiful for more information about this chart.