Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Zero — Thu, 14 Jun 2012 06:52:00 GMT

Dev Ops is all well and good but the fact that most Devs do not make good Sysadmin and most Sysadmin that a Windows based are so use to the GUI that learning this stuff is going to be hard. I like Powershell and I use it but I have a Unix admin background so I am down with this but Devops is a pipe dream in the Windows world and you will find that the GUI will still get used.

Good luck with this tho :)

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Aleksandar Nikolić — Sat, 02 Jun 2012 14:33:57 GMT

@Jose - Don't download PowerSell 3.0 Beta, Windows Management Framework 3.0 RC is available for download and it contains PowerShell 3.0 RC (the same version you get with Windows 8 Release Preview and Windows Server 2012 Release Candidate) - blogs.msdn.com/.../windows-management-framework-3-0-rc-is-available-for-download.aspx.

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Alvaro — Fri, 01 Jun 2012 18:38:08 GMT

Thanks for the answers ... ill try WS2012 PowerShell included,just wish i had waited 1 day ... just finished downloading the beta to find out that RC is now available...

Ill start downloading again

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Jose — Fri, 01 Jun 2012 03:33:55 GMT

Where can I download Powershell 3.0 Beta? I want to try it, but I can't download Windows 8 at this moment.

Cheers.

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Jeffrey Snover Windows Server — Thu, 31 May 2012 20:18:26 GMT

@alvaro - Most (but not all) of the things you are asking for are available in PowerShell_ISE.

Give it a try - I think you'll like it.

Cheers

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Jeffrey Snover Windows Server — Thu, 31 May 2012 20:15:26 GMT

@alvaro - Attrib and Time are CMD.EXE buildtins and are not available in PowerShel. All the others you mentioned are CLIs and are available from PowerShell. In terms of mapping old to new cmdlets, that sounds like either a great blog post we should write or a WIKI the community should generate/maintain.

Cheers!

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Christian Schindler — Thu, 31 May 2012 19:00:05 GMT

Great Article! For me PS 3.0 was love at first sight :-) I've been using Monad from the early builds on...but what comes with PS 3.0 is what I ever wanted as an admin. Especially the little things make life in production easier: for example the ability to use the TAB key inside a command without loosing all the other parameter...yeah! Or the ability to use the TAB key for parameter values... Etc., etc. Thank you!

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Alvaro — Thu, 31 May 2012 16:29:46 GMT

With 2.4K cmdlets it must be one to take the dog for a walk .... but how do we find the equivalent of and old command or utility???

Some of the likes:

attrib

Chkdsk

Diskpart

dnscmd

Eventcreate

Getmac

Ipconfig

iscicli

Netsh

Netstat

Nslookup

Ping

Shutdown

Tracert

Time

X-copy

Besides Think,Type and Get ... because someone would thing "diskpart", type it and wont get it ....

Maybe a "Get-Command -Equivalent getmac" or build some more aliases (like dir, ls, cd, move ...) so the users could simply type "Get-Alias getmac"

Cheers!

re: Windows Server 2012, PowerShell 3.0 and DevOps, Part 2

Alvaro — Thu, 31 May 2012 15:38:50 GMT

I was told to w8 for this post to answer some question about PS> 3.0 ...

1.Why PowerShell CLI still doesn't have CTRL+C, CTR+V, find &replace, select, drag and drop support?? (the fact that PS is also a PS CLI Shell doesn't mean that has to live with the limitations of legacy CLIs, i think)

2.Why PowerShell CLI still doesn't have Syntax highlighting (color coding)???

3.Why PowerShell CLI doesn't benefit from IntelliSense, snippets, 3rd party extensibility and a Show-Command???

4Is it possible for PS> to get some kind of command-spell-check support?

Ex: PS> Get-Comand -CommandType CMDlet | Sort ShortName, Verb

Did yo mean Get-Command .... (Y)es (N)o??

5.When we get some error... Why dont we get some graphical indicator to point the place... instead of a long error description followed by "At line:1 char:63"???? ( i dont like counting chars for hunting mistakes)

And i still think you need to get behind PowerShell (like making PS> the default shell in WS2012, or at least a opt-in option somewhere). If the organizations want to remove PS and .NET ... the revert to cmd.exe.

Cheers!