Can I? Should I?–examples–legacy scripts

In this post I stated that PowerShell isn’t necessarily the right answer to every problem.

I was left a comment asking if I could expand.  I’ll do that over a series of short posts as I think of examples.

One of the first that comes to mind is legacy scripts.

VBScript never really caught on as a mainstream administration tool. There were a number of reasons for this:

  • non interactive
  • harder to use and debug
  • less information
  • less flexible
  • admins addicted to the GUI
  • less pressure on people i.e. more admins

However, a number of organisations created a significant number of scripts and performed some very clever stuff.

Now, the question for those organisations is this –

“PowerShell has appeared. Do I convert all those scripts, that work really well to PowerShell?”


My answer would be no!  Learn PowerShell first . Get really proficient. Develop new stuff in PowerShell and migrate the legacy scripts when they need an over haul (or you get some free timeSurprised smile) that way you get the best of both worlds and run the smallest risk when you come to migrate the legacy scripts.

This entry was posted in Philosophy, PowerShell V2. Bookmark the permalink.

3 Responses to Can I? Should I?–examples–legacy scripts

  1. jkavanagh58 says:

    While I agree, I have to say that I have been able to show the value of Powershell by migrating legacy scripts.

    • My posts on this subject are generalisations and like all generalisations there are exceptions. I would expect there to be a value add by converting but the point I was trying to make is that it isn’t necessarily top of the priority list.

      if it ain’t broke don’t fix it.

      Thanks for the comment though

      • jkavanagh58 says:

        Completely understand that sir. It’s just been my experience that there is still some hesitation when it comes to adopting Powershell. I have the same concerns when policing code… I spend most of my time just getting colleagues to see the power from the CLI and then to be able to show how they can take working vbs code and simplify the code and produce more efficient results is a first step.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s