Is Powershell a mature enough technology for enterprise use?

Question

Is Powershell a mature enough technology for enterprise use? Are its many benefits significant time and effort to convert existing VBS scripts, or will you only use it for new scripting projects?

We are currently using a mixture of vbs and batch files with a login script, and not with a lot of GPOs. We do not have a large number of .NET programmers, while almost everyone at least knows a little VB.

Answer 1

"Mature enough" is slightly subjective and depends on what you mean.

1) Is he strong enough to do the job? -- Yes. But this is not the best tool for all jobs; I think, choose.

2) Are bugs / problems fixed? - No. To be prepared and informed, you can take a look at some of the most popular errors / issues: https://connect.microsoft.com/PowerShell/Feedback

3) Is it easy to find out? -- It depends; I basically think that this is not easy for non-professional programmers. But it is definitely possible, step by step, with pleasure: http://blogs.msdn.com/b/powershell/archive/2010/03/09/falling-is-learning-just-focus-on-having-fun. aspx

PowerShell . (, VB), PowerShell, . PowerShell.

Answer 2

. PowerShell .NET, COM, WMI .. , 30 , .

Answer 3

, PowerShell - . Microsoft " , powershell" ( MS Exchange, SharePoint 2010). , . - PowerShell, , , .

Answer 4

• Convert only when necessary
• Prefer PowerShell for a new job.
• This venture is ready and there are gotchas as with anything
• Doing work in PowerShell now improves your skills.
• PowerShell execution is now positioned for vNext products included in PowerShell. Big win.