In short I needed to use the variable %~dp0 before the items on the distribution point share. For example I changed “\\SCCM\packages\MozillaFirefox\Firefox Setup 3.6.3.exe” in the script to “%~dp0\Firefox Setup 3.6.3.exe.” I tested it with a test script that echoed out the commands instead of running them, and the paths were correct.

The myITforum article goes into further detail about the other uses of this variable. It’s actually a modification of the %0, %1, %2 convention of dos batch files for referencing command-line arguments. %0 references the script itself, including the full drive and path, %1 is the first argument, and %2 is the second, and so on. The “~d” modifier before the number 0 resolves the variable to the drive letter only and “~p” would resolve it to the path only. Combining the two into  “~dp” resolves it into drive and the path, or in this case the full UNC path. More information can be found by typing “FOR /?” from a command prompt.

I found several PowerShell examples on the web for interacting with Microsoft DNS servers, and took a bit from each to come up with this script. It takes the shared printer name and publishes that as the DNS name. This does cause a problem if you have spaces in a share name, but our environment doesn’t, so I didn’t program for that issue.

Here’s the script:

Function Add-ARecord
{
Write-Host -ForegroundColor DarkCyan “Importing Printer information”
# Imports all printers from Print Server
$printers = (get-WmiObject -class $Class -computername $printSvr)
$Arecord = [WmiClass]“\\$dnsSvr\root\MicrosoftDNS:MicrosoftDNS_AType”
$class = 1
$ttl = 3600 # Time-To-Live in seconds

$printers | ForEach-Object{
Get the name of the Shared Printer
$name = $_.ShareName
# Get IP information from TCP/IP port
$address = $_.portname.Replace(“IP_”, “”) # output variables for testing
#write-host -ForegroundColor Yellow $server, $zone, $name, $class, $ttl, $address

# create DNS A Records
$Arecord.CreateInstanceFromPropertydata($server, $zone, $name, $class, $ttl, $address)
}
}

$Class = “win32_printer” # WMI class for printers
# Change to suit your environment
$printSvr = “printsvr” # Print server
$dnsSvr = “dnssvr” # DNS Server
$zone = “dnszone” # DNS Zone

Add-ARecord

[edit] A couple people left comments that this didn’t work for them, and I was unable to get it to work for me again. I swear it worked the day I needed it. If anyone can tell me why it doesn’t work now, I’d appreciate it.

]]> http://www.yakk0.org/2010/03/08/powershell-add-printers-to-dns/feed/ 2 http://www.yakk0.org/2009/05/06/one-line-administration-search-and-delete-computer-accounts/ http://www.yakk0.org/2009/05/06/one-line-administration-search-and-delete-computer-accounts/#comments Wed, 06 May 2009 19:02:29 +0000 Jeremy http://www.yakk0.org/2009/05/06/one-line-administration-search-and-delete-computer-accounts/ Here’s a quick one-line script I’ve been using to clean up some old computer accounts in active directory. It requires the dsquery and dsrm tools from the Server 2003 Admin Pack or the Remote Server Administration Toolkit.

@for /f %%a in ('DSQUERY COMPUTER -NAME *%1') do (dsrm %%a)

Save that in as a batch file and it’ll query Active Directory for computers including the argument passed.  Here’s an example with a naming structure where we have the last 4 digits of the MAC address in the name for uniqueness.

C:\>adrm.cmd 6736
C:\>(dsrm "CN=LABPC6736,OU=Labs,DC=yakk0,DC=org" )
Are you sure you wish to delete CN=LABPC6736,OU=Labs,DC=yakk0,DC=org (Y/N)? y
dsrm succeeded:CN=LABPC6736,OU=Labs,DC=yakk0,DC=org