|T O P I C R E V I E W
||Posted - 02/22/2012 : 11:08:55 AM
Don had mentioned Powershell for topic suggestions to see covered at this years TechEd 2012.
|22 L A T E S T R E P L I E S (Newest First)
||Posted - 05/05/2012 : 9:04:49 PM
Just to be correct on the power shell help.
They are not shipping help in the Beta/ CTP/ Bla bla bla as there is a disconnect in the code and when it goes to localisation and what is actually published in the RTM ( can be up to 10 months between the code for all MS products goes to localisation and launch) and this caused issues.
The help files are available as a download, and will be sent to PoSH 3 installs as MS updates, or available on demand with "get-update help" (I think is what the command is) every 24 hours. there is a -force or -donotcheck command to over-ride the check once every 24 hours.
This will allow the help files to truely reflect the contents allowing updates in the future to the bad help info.
As to Wes' comments on the oddities in PoSH, yup I agree. but it also in cmd commands, vb, linux and unix. Thats why there tends to be decent help files and PoSH 3 has a better way of accessing it. Now try to tell one of my lecturers that hand writing in an end of year exam, the syntax of commands is........Squirrel
||Posted - 05/05/2012 : 12:54:25 PM
Thanks, Dennis! Yes, I found in my notes where Don pointed that out. I'm just so used to seeing "click here for kindle edition" on amazon's page.
||Posted - 05/04/2012 : 7:23:49 PM
Originally posted by JamesNT
Where is the Kindle version?
James, if you buy the book directly from the http://www.manning.com/jones/ website, the mobile formats include a Kindle version (as well as the PDF version). Also, if you buy the hard cover book, you get the eBook for free.
||Posted - 05/04/2012 : 7:19:55 PM
From what Don said at the forum meet, PowerShell V3 doesn't have the Help installed. Once you open PowerShell, you run a command and it installs the most recent version of Help with any updates. On previous versions, because it was built into PowerShell, once they locked the code, they couldn't make changes to the Help since it was part of PowerShell and the code was locked. By not having the Help built into PowerShell V3, they can still made changes to the Help document up until PowerShell actually shipped. They can also make changes after it ships and people can get the most recent version by running the command to update the Help information
||Posted - 05/04/2012 : 2:09:52 PM
Where is the Kindle version?
||Posted - 05/04/2012 : 09:03:17 AM
All kidding aside James GET THIS BOOK! Learn Windows PowerShell in a Month of Lunches
There are SO many AH HA! Moments that I cannot figure out where to begin. You get this and understand each chapter as you go, the light will suddenly go on and you will be blown away at how easy it has been the whole time...
||Posted - 05/04/2012 : 08:58:23 AM
As soon as I get a new server, I'm going to set up a new Windows Server 2012 machine with no GUI and just learn PowerShell. Period. Per Don's recommendation, I'll also have a Windows 7 client to use as a management station so I can do remoting.
In my opinion, sometimes the only way to guarantee you learn something is to put yourself into the position of where you just have to.
||Posted - 05/04/2012 : 04:23:31 AM
OK, I'm convinced.
||Posted - 05/03/2012 : 11:48:28 AM
There is definitely a lot of power there! Just looking forward to a more unified, better documented experience some day!
||Posted - 05/03/2012 : 11:47:02 AM
Since I have been focusing on Exchange and Lync they have been pretty spot on, with one exception that was the result of me not having access rights to the Transport Server's.
The only other thing that I have run into with Lync is a cmd that was not to be found in Google but, lo and behold it was in Nathan's Mastering Microsoft Lync Server 2010 book.
If I am digging around in AD I will use the Quest tools as well, if messing with VMware I will always have PowerCLI going.
There is still a lot of growing pains in Microsoft between departments but the bottom line is IF you are using it you can figure out why something works here and not there.
Also, IF you are using Posh now, you know who "THE Claus", Jeffery Hicks, Ed Wilson (and wife), Jeff Wouters, Don Jones, Hal Rottenberg, Jeffrey Snove, etc are,,, since it seems to be a close knit group. Which means you can reach out to them for assistance.
I only write this since I am still meeting people that just shake their head and say NO THANKS! I just say Ok,,, and walk away...
EDIT - Added link and spelling.
||Posted - 05/03/2012 : 11:32:32 AM
Is it just me or is there a LOT of inconsistency re: powershell commandlets and syntax across the various products? I have lost count of how many times I'll try to apply concepts I learn from one source to another and end up frustrated and asking for poor Claus' help - and he'll smile and pat my head and say "weeeeeelllll because of blah blah blah you have to do blah blah blah instead." Also it seems that around 60% of what we try to do ends up requiring the Quest powershell add-on...
||Posted - 05/03/2012 : 10:56:08 AM
when do we P2A them?
||Posted - 05/03/2012 : 10:41:02 AM
The things I dream about... <g>
So as of this morning this is about as basic as I can put the need to learn Powershell.
Posh V1 = Like learning to read See Dick and Jane. Was a good foundation with basic verbiage to get you interested.
Posh V2 = See Dick and Jane go off to college and the zany life lessons they learned. Great stuff and a huge WOW factor of what we can do with ease via the Shell.
Posh V3 = See Dick get a divorce from Jane for sleeping with her insanely good looking sister Jennifer and Jane goes off the deep end and sells Dick's Corvette for $1000.00 all they while Dick is being investigated for embezzlement while working at Lehman Brothers Brothers and YES! Jane is pregnant...
So if you are thinking of "just waiting for V3" you may find yourself asking "Who The H*** is this Dick and Jane? How am I ever going to catch up to people that have been doing this for a long time?"
Again, Saying I don't want to learn Powershell because I can use the GUI, is like saying I don't want to learn to read because I can watch TV...
||Posted - 02/24/2012 : 09:44:32 AM
Also Tim I have to say that I am using it everyday now, espcially since getting into an Exchange 2010 role with Lync right around the corner.
As a side note, our Tech Team where I am currently contracting, is using Nagios for monitoring and they have built several hundred Powershell snap-ins that have enhanced it's ability.
Example: a short simple script where you enter the server name that you need to reboot, for what ever reason, then the script turns off those alerts and emails the rest of the team that YOU are rebooting for whatever reason. Then once the server is back up you run the 2nd part of the script and alerts are back on and email is sent to that affect.
No more searching and clicking and hunting and clicking in the application.
That may be a bit simplistic, but I think it is a great example of how many things you can touch with Powershell.
If you are a VMware shop PowerCLI is simply amazing! The free snap-ins from PowerGUI are fantastic!
The only limitation is your imagination. Once WIN 8 Server comes out there will be thousands of new options at your finger tips.
I am not saying that you will have to be an expert, but IF you are comfortable with your skills now, the upgrade will be painless and pretty much seem-less.
You can learn V2 and add V3 later. Or you can start from scratch with V3 and be way behind the learning curve.
As I stated on my article here Why Should I Learn PowerShell? Real World Example Saves the Day!
"How many of us can reach out to a Windows PowerShell MVP that “may” be available to assist you with management’s emergencies?"
Just my .02
||Posted - 02/24/2012 : 09:42:35 AM
Simply put, for Windows, PowerShell is to CMD.EXE and COMMAND.COM as ksh and csh are to sh for UNIX
||Posted - 02/24/2012 : 09:20:45 AM
If it gives you any clue about the importance of PowerShell, and I don't think this is coincidental, Jeffrey Snover, the driving force behind PowerShell is holds the rare title of Distinguished Engineer and is the lead architect on Windows 8 Server. Ya think PowerShell will play a role??!!
||Posted - 02/24/2012 : 07:31:46 AM
I understand that, but I'm still not 100% convinced.
||Posted - 02/24/2012 : 04:52:44 AM
Because this is the first time MS really promotes a cross software control mechanism.
And IF they are doing this again with another product in 3 years, you'd learn it again :)
If you hesitate to learn you are in the wrong businiss :)
||Posted - 02/24/2012 : 03:21:22 AM
I have that Powershell book on my desk at the moment. It's on my list of things to learn.
I can't help but feel that in three years' time Microsoft will turn round and say "you know that Powershell thing? Well guess what we have now......." and we'll have to learn things all over again.
Am I being cynical?
||Posted - 02/23/2012 : 1:38:13 PM
It's just another third party opportunity to build a GUI around powershell for management.
||Posted - 02/22/2012 : 4:01:46 PM
The company I am contracting with now has started a learn Powershell at lunch course each Wednesday using Don's Learn Powershell in a Month Of Lunches as a reference.
They have some GREAT tech's involved and it is making learning a blast!
||Posted - 02/22/2012 : 3:28:21 PM
So PowerShell is here for more than five years now and direct from the start it was very clear that PowerShell would become the major management and scripting interface for all Microsoft servers and server applications. I would say that PowerShell should be considered common knowledge by now, and for those who didn't had the chance to get familiar with it there is plenty of information, howto's, tutorials, examples and other information available on the web. Not to mention books.
Let's put it in another way. Do you guys expect a session about Windows Server, Exchange, SharePoint, Hyper-V, deployment, SQL, Office 365, Azure or any other topic *without* talking about PowerShell? :)