PowerShell Class

I have just spent 5 complete days in an on-line Administering Windows with PowerShell class. My head didn't explode, but there was some knowledge that leaked out my ears. That's to be expected. I find PowerShell knowledge to be very helpful in my line of work -- I'm primarily a SharePoint and Records Management administrator and developer. PowerShell provides a toolbox with which I can better do my job. I will immediately put the knowledge that I gained to work in my day-to-day business.

I'm an old perl guy and find much of PowerShell reminiscent of perl. The object-oriented nature of the language takes a bit of getting used to as does the pipe, but once you get the hang of both, it's pretty easy to get the most out of the tool. I will have to convert some of the perl that I have written for Windows into PowerShell as the other members of the team will be better able to maintain and enhance the scripts if they are written in PowerShell than in perl.

I also plan to make extensive use of PowerShell's remoting capability as we have multiple systems in various farms that we have to administer. We also have the need to make sure that some of the fall-back farms have the same configuration as our primary farms. We need to be ready to fall back to our alternate location in case of any problems with the primary farm. The use of remoting will assure that the same configuration is applied to all servers in both farms. it will also allow us to determine the cause of problems across multiple WFE's as we troubleshoot the farms.