I have installed a plugin for my blog that will allow you to view it on your iPhone with no scrolling or scaling required.  Check out the screenshot: This is a cool feature that makes the blog very easy to read and navigate from your iPhone.

Ever wanted to know what IP addresses are being used on a particular subnet and what each IP address resolves to which hostname, if any?  This script accomplishes just that. # Continue to run script when an error occurs$ErrorActionPreference = “SilentlyContinue” # Process through the loop of IP addresses 1-2541..254 | foreach -Process `{ # We’re combining the contents of different objects, so create our own $obj = New-Object PSObject; # Perform the Ping using WMI $ping = get-WmiObject -Class Win32_PingStatus -Filter (“Address=’10.10.2.” + $_ + “‘”); # Put the IP Address into our object $obj | Add-Member NoteProperty IPAddress($ping.Address); # Take the Ping Status Code that is returned (0 = pingable) $obj | Add-Member NoteProperty StatusCode($ping.StatusCode); # If we can ping the address, let’s try to resolve the hostname if($ping.StatusCode -eq 0) { # Record that the ping was successful $obj | Add-Member NoteProperty Status(“Online”); # Try to resolve the…

We all know that most test domains are the perfect breeding ground for non-standard practices.  This includes the lack of managing user accounts, computer accounts, DNS records and the like. ADSI scripting has always been challenging, but I did do some of it back in my IT days when writing code in VBScript.  I wanted to try to tie in to a test domain to determine what computer accounts hadn’t had their password changed in the last 90 days.  By default, Windows machines will talk to the domain in which they have a computer account in and change their password every 30 days.  With that in mind, we can look for computer accounts who haven’t changed their computer account password in the last month. We probably want to allow a little more than 30 days; perhaps computer accounts might be considered stale after 60 or 90 days.  That means that…

This week we announced the availability of the Storage Center Command Set for Windows PowerShell as a free download for Compellent customers. PowerShell is the powerful, new scripting interface from Microsoft with support for Windows Server 2008 (including Hyper-V), Windows Server 2003, Windows XP, and Windows Vista.  We’ve integrated PowerShell automation with our Command Set scripting shell. From Command Set, IT pros can  automate administration tasks on the Windows platforms for their Compellent Storage Center. We’ve integrated PowerShell automation with our Command Set scripting shell. From Command Set, IT pros can automate administration tasks on the Windows platforms for their Compellent Storage Center. We’ve exposed over 60 cmdlets that you can use to manage different objects within Storage Center including the controllers, servers, volumes, and alerts in addition to features like Copy-Mirror-Migrate (CMM). With the installation of the Command Set, we also include a few samples scripts to get you…

My last post touched on automating the installation and creation of a failover cluster on Windows Server 2008.  In this post, I want to touch on adding additional redundancy by installing Multipath I/O.  With MPIO, you can have multiple paths to your disk that are masked together to provide high availability and redundancy in your cluster configuration. In Windows 2008, you can use ServerManagerCmd to automate the installation of the MPIO feature from the command line: C:\> SERVERMANAGERCMD.EXE -install Multipath-IO Once the role is installed a reboot will be required, but if you have additional configuration that you want to do with MPIO before that reboot, you can do that first. Interestingly enough I was looking for a way to add the hardware vendor ID for MPIO disk devices.  You can pre-configure MPIO to look for particular disk devices based on their hardware ID to automatically use MPIO on those…