One of many reasons to translate VBScript to PowerShell

I'm wrapping up the deployment of a cross-platform automation tool for our distributed databases(DB2 LUW, SQL Server, Oracle). 

One of our major items to convert is a VBScript that does several post-installation tasks for SQL Server. 

I've decided to take this opportunity to retire as much VBScript as possible. 

Why might you ask? 

Here's my first example...

To check the version of Windows in our VBScript requires twelve lines of code

PowerShell only needs one. 

Well, we'll need two lines to store the Caption and CSDVersion in variables for later use.

I expect I'll have several other great examples to show from this effort.

Get stuff done faster with less code. Use PowerShell.