{"id":72022,"date":"2015-07-21T00:01:00","date_gmt":"2015-07-21T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2015\/07\/21\/i-have-a-powershell-profilenow-what\/"},"modified":"2019-02-18T09:46:55","modified_gmt":"2019-02-18T16:46:55","slug":"i-have-a-powershell-profilenow-what","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/i-have-a-powershell-profilenow-what\/","title":{"rendered":"I Have a PowerShell Profile—Now What?"},"content":{"rendered":"

Summary<\/b>: Ed Wilson, Microsoft Scripting Guy, talks about the what to add into a Windows PowerShell profile.<\/span>\nMicrosoft Scripting Guy, Ed Wilson, is here. It was a beautiful sunny weekend in central Florida. The Scripting Wife and I headed to Tampa, where we met up with various Windows PowerShell peeps. It is good to get together and talk about cool stuff with cool people. The Microsoft office in Tampa is a really cool place to hang out, and it has awesome views of the harbor. There are also lots of really good restaurants in town.\nAnyway, when I am around Windows PowerShell people, one of the things I tend to ask them is what they have in their profiles. The answers are usually pretty interesting. In addition to providing good ideas, their answers also lend insight into how people use Windows PowerShell and the kinds of things they do with it.\nI like to organize my Windows PowerShell profile into sections because it helps me keep track of stuff.\nAs you may know, a Windows PowerShell profile is sort of like the old-fashioned autoexec.bat file. It is simply a file that has a special name and resides in a special place. Unlike the autoexec.bat file, however, there are different files that can be in different places, and that will have different scope.\nThis can become really confusing if one does not do a little bit of planning at the outset. There are really six profiles that are available by default:<\/p>\n