Interesting remark on the Windows Powershell blog:

"While the end of life for VBScript has been announced (don't freak out – it is going to be supported for a long time but the clock has started (it will become an optional component, then a web download, then a memory)), [...]"

Windows legacy technologies tend to be around quite long for backward compatibility, and I agree that this will probably the case for VBScript, too, but the signs are clear. VBScript is done. Every new "investment" in VBScript should be questioned and newer technologies should be preferred.