Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Solved
What is the difference between VBS and PowerShell?
Posted on 2011-02-13
Hi,
Could someone can explain what is the difference between VBS and PowerShell? What is the advantages and disavantaged of each one for a Windows System Admin? If I want to learn one of them which will you recommand?
Could someone can explain what is the difference between VBS and PowerShell? What is the advantages and disavantaged of each one for a Windows System Admin? If I want to learn one of them which will you recommand?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4 Comments
Here's a great article on why you would choose Powershell over VBS and the advantages.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_3296-The-Absolute-Beginner's-Guide-to-Powershell.html
And when you're done with that, and you want to know how it can benefit your life as a Server Administrator, you can check out this article:
http://www.experts-exchange.com/Programming/Languages/Scripting/Powershell/A_4327-PowerShell-Where-do-I-start.html
It goes into a little more depth of how you can unlock accounts very easily, reset passwords, and even create accounts. Powershell is the future and it's the "Console" for Exchange 2007, Exchange 2010, and Sharepoint 2010. It's definitely here to stay and made to improve upon VBS with a .Net flair.
HTH,
Dale Harris
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_3296-The-Absolute-Beginner's-Guide-to-Powershell.html
And when you're done with that, and you want to know how it can benefit your life as a Server Administrator, you can check out this article:
http://www.experts-exchange.com/Programming/Languages/Scripting/Powershell/A_4327-PowerShell-Where-do-I-start.html
It goes into a little more depth of how you can unlock accounts very easily, reset passwords, and even create accounts. Powershell is the future and it's the "Console" for Exchange 2007, Exchange 2010, and Sharepoint 2010. It's definitely here to stay and made to improve upon VBS with a .Net flair.
HTH,
Dale Harris
It depends on what you're trying to acomplish. Some older products don't support PowerShell. Since VBS was released first it's supported by most products (Exchange 2003 / SQL 2005). However the newer products are favoring PowerShell over VBS (Exchange 2007 / 2010, SQL 2008 / 2008 R2, SharePoint 2010) . In fact some Exchange functionality is only available via Powershell cmdlets. So unless you have the latest products you may be forced to learn some about VBS and PowerShell in order to do most automation. PowerShell 2.0, the latest, comes with Windows 7 and Server 2008 R2. There are downloads for installed it on Vista, XP, Server 2003 and 2008. VBS support is included with all supported versions of Windows.
Active today
The differences are pretty vast.
VbScript is a difficult one for me to describe, it's a derivative of the Visual Basic programming language, and can make use of COM Objects, such as WScript.Network, WScript.Shell, ADSystemInfo, etc, etc. I believe it's popular for the reason Connectex mentions; it's available regardless of the version of Windows. VbScript was pretty much the language of choice for MS sys admins prior to PowerShell.
I have an easier time describing PowerShell. PowerShell is an Object-Oriented .NET Shell Scripting language. Because it is a .NET language it has an enormous range of native capabilities. PowerShell is the language of choice for almost all of the newer MS products. Most notably Exchange, but also Lync (successor to OCS) and quite a few others.
Personally I've abandoned VbScript in favour of PowerShell, no small change given that I have over 7 years experience with VbScript behind me. But 3 years into my PowerShell / .NET education there's no way you'd make me look back. PowerShell can do everything that VbScript can and a lot more besides.
Pros and cons... I can come up with a list, but it strikes me that MS are pushing PS hard and dropping VbScript and COM Object interfaces. As long as that is the case the choice is simple:
If you wish to script for newer MS systems (Exchange 2007+, MS Lync, SQL, SharePoint, etc, etc) you need to learn PowerShell.
I cannot advise anyone learns VbScript on that basis, but there are caveats, it does depend what you expect to do with the language. If you want to use it as a portal to VBA, then VbScript is a good choice. Or if you deal exclusively with legacy platforms VbScript is a good choice.
Of course, if you're capable of learning both, the both is a good choice too :)
Chris
VbScript is a difficult one for me to describe, it's a derivative of the Visual Basic programming language, and can make use of COM Objects, such as WScript.Network, WScript.Shell, ADSystemInfo, etc, etc. I believe it's popular for the reason Connectex mentions; it's available regardless of the version of Windows. VbScript was pretty much the language of choice for MS sys admins prior to PowerShell.
I have an easier time describing PowerShell. PowerShell is an Object-Oriented .NET Shell Scripting language. Because it is a .NET language it has an enormous range of native capabilities. PowerShell is the language of choice for almost all of the newer MS products. Most notably Exchange, but also Lync (successor to OCS) and quite a few others.
Personally I've abandoned VbScript in favour of PowerShell, no small change given that I have over 7 years experience with VbScript behind me. But 3 years into my PowerShell / .NET education there's no way you'd make me look back. PowerShell can do everything that VbScript can and a lot more besides.
Pros and cons... I can come up with a list, but it strikes me that MS are pushing PS hard and dropping VbScript and COM Object interfaces. As long as that is the case the choice is simple:
If you wish to script for newer MS systems (Exchange 2007+, MS Lync, SQL, SharePoint, etc, etc) you need to learn PowerShell.
I cannot advise anyone learns VbScript on that basis, but there are caveats, it does depend what you expect to do with the language. If you want to use it as a portal to VBA, then VbScript is a good choice. Or if you deal exclusively with legacy platforms VbScript is a good choice.
Of course, if you're capable of learning both, the both is a good choice too :)
Chris
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes. We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
In the absence of a fully-fledged GPO Management product like AGPM, the script in this article will provide you with a simple way to watch the domain (or a select OU) for GPOs changes and automatically take backups when policies are added, removed o…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Suggested Courses
Course of the Month14 days, 2 hours left to enroll
656 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.