northben's blog

If you live in the unfortunate world of IIS6, or perhaps you're just masochistic, you're going to use ADSI in PowerShell to work with IIS. A friend of mine showed me a handy way to delete log files older than a certain date using an ADSI query in PowerShell.

Running Server 2008 R2, IIS 7.5, if you get this error in the Application event log:

The Module DLL C:\Windows\System32\inetsrv\logcust.dll failed to load.  The data is the error.

It's kind of an obscure situation. IIS is saying it could not load the logcust module, which is the Custom Logging feature. In my case, I was setting up a development server farm, and had installed this feature on one server. The shared configuration caused IIS to try loading this module on the other server.

I was on the phone with VMware the other day and asked if there was some way to get a list of all the snapshots I have across all of my virtual machines. The VMware rep said no, you have to click on each VM one by one. However, I figured that it could be done. Here's how I did it.
Update: more concise output

I am in the middle of a SQL data conversion project. Amazingly, our *new* SQL Server database requires dates to be stored in Unix format, which is a bigint field with the number of milliseconds since 01/01/1970. Amazing, I tell you.

Here are some queries that I have found useful in this project. I have updated this article to include an alternative that does not involve functions.

Due to unrelenting spammers, I have switched to allowing only Facebook comments on my website. I hope you are all ok with that, you Googlers of the internet!

You may know the convenient feature in Windows 7 to snap windows to the right and left: drag a window all the way to one side of your screen and it will snap to the side of your screen, taking up exactly one half of it. The keyboard shortcut Win+Left (right) arrow does this as well. But how do you snap windows to the top and bottom of your screen? It's easy!

If you are running a Drupal site with Network Solutions hosting, please accept my condolences. And the lack of shell access? The pain of your loss is almost unbearable.

However, thanks to jomariworks on the Network Solutions forums, at least you can enable Clean URLs!

I had some FLAC audio files on my computer that I wanted to convert to a lossy format (AAC, in my case). iTunes won't play FLAC, and VLC wasn't helping me. I ended up calling FFmpeg in a PowerShell script to quickly convert all of the files.

$target = 'J:\FLAC'
$target = $target + "\*.flac"
$files = Get-ChildItem $target

foreach ($file in $files) {
    .\ffmpeg.exe -i $file -acodec libvo_aacenc -b:a 256k -ar 44100 -threads 4 -n $($file.BaseName + ".m4a")
}

I needed to get a file modification timestamp through WMI (for an irrelevant reason, I couldn't use the UNC path and PowerShell's get-childitem cmdlet). So, WMI it had to be...

$file = gwmi -computername remoteComputer -query "select * from cim_datafile where name = 'C:\\file.txt' "
$age = (get-date) - $file.convertToDateTime($file.LastModified)
return $age.seconds

Pretty quick and painless!

Note: you could get (m)any other file attributes by slightly altering these lines. Remember: the get-member cmdlet is your friend!

If you're writing a script that takes parameters with the "param" statement/feature, don't declare any variables before param. It will throw some weird errors! You can put variables in the Begin scriptblock instead.