This is one things I love most about working with Windows PowerShell (and scripting in general) is that most problems have more than one solution. Occasionally, the best solution is the path of least resistance. Finding the “best” solution to a problem is one of the goals that I think drives many people who are successful at what they do. It’s one of the things that makes work interesting. One of the life lessons I have learned over the years working in the IT field as a server administrator is that there are often several different valid responses to a situation. In 2011, I founded the Corpus Christi PowerShell User Group and try to help bring others up to speed on Windows PowerShell. My daily responsibilities keep me involved with Active Directory, supporting Microsoft Exchange, SharePoint, and various ASP.NET applications. In 2008, I made the move to Windows PowerShell and have never looked back. I was introduced to VBScript in 2000, and scripting became a regular obsession sometime in 2005. I started in the IT industry in 1996 with DOS and various flavors of *NIX. I am currently a senior systems administrator with the Department of the Army. Here is what Marc has to say about himself. It was way cool, and both Marc and his wife Pam are terrific hosts. The Scripting Wife and I were lucky enough to attend the first PowerShell User Group meeting in Corpus Christi, Texas. Guest Blogger Weekend concludes with Marc Carter. Summary: Learn how to use Windows PowerShell to quickly find installed software on local and remote computers.
0 kommentar(er)
