{"id":9361,"date":"2012-05-21T00:01:00","date_gmt":"2012-05-21T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2012\/05\/21\/understanding-the-six-powershell-profiles\/"},"modified":"2012-05-21T00:01:00","modified_gmt":"2012-05-21T00:01:00","slug":"understanding-the-six-powershell-profiles","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/understanding-the-six-powershell-profiles\/","title":{"rendered":"Understanding the Six PowerShell Profiles"},"content":{"rendered":"

Summary<\/b>: Microsoft Scripting Guy, Ed Wilson, discusses the six different Windows PowerShell profiles, and when to use each.<\/p>\n

\"Hey, Hey, Scripting Guy! Dude, I have been reading some of the posts in your most excellent blog; and first of all, I want to say I think you are great. Now for the question: I do not get the Windows PowerShell profile. I mean I get it, but not really. Here is part of my problem. I put some things in the profile, and then I go back and they are not there. Like, what is up with that? I hope you can help me. By the way, I am, like, totally looking forward to seeing you and the Scripting Wife at TechEd 2012 in Orlando. You will know me, because I sort of look like Urkel<\/a>, and I always wear plaid shirts (but I don’t wear suspenders).<\/p>\n

—BB<\/p>\n

\"Hey, Hello BB,<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Last week was an absolutely great week. The Scripting Wife and I had dinner one night with Rich from the NYC Windows PowerShell Users Group (he is also a moderator for the Scripting Guys forum and writer of a couple of guest blogs). Rich was kind enough to bring me some Gunpower green tea, and I am sipping some right now. It is wonderful with a half teaspoon of organic lavender added to the pot. We also had the PowerScripting Podcast with the two winners of the 2012 Scripting Games and Jeffrey Snover. That conversation was fun and informative. I also enjoy talking to Jeffrey, and I look forward to sitting-in on at least one of his sessions at Microsoft TechEd 2012.<\/p>\n

Six, count ‘em, six different PowerShell profiles<\/h2>\n

BB, there is no doubt that you are a bit confused with Windows PowerShell profiles. There are, in fact, six different profiles. The Windows PowerShell console and the Windows PowerShell ISE have their own profiles. In addition, there are profiles for the current user and profiles for all users. The table that follows lists the six profiles and their associated locations.<\/p>\n\n\n\n\n\n\n\n\n\n
\n

Description <\/b><\/p>\n<\/td>\n

\n

Path<\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Current User, Current Host – console<\/p>\n<\/td>\n

\n

$Home\\[My ]Documents\\WindowsPowerShell\\Profile.ps1<\/p>\n<\/td>\n<\/tr>\n

\n

Current User, All Hosts   <\/p>\n<\/td>\n

\n

$Home\\[My ]Documents\\Profile.ps1<\/p>\n<\/td>\n<\/tr>\n

\n

All Users, Current Host – console   <\/p>\n<\/td>\n

\n

$PsHome\\Microsoft.PowerShell_profile.ps1<\/p>\n<\/td>\n<\/tr>\n

\n

All Users, All Hosts      <\/p>\n<\/td>\n

\n

$PsHome\\Profile.ps1<\/p>\n<\/td>\n<\/tr>\n

\n

Current user, Current Host – ISE<\/p>\n<\/td>\n

\n

$Home\\[My ]Documents\\WindowsPowerShell\\Microsoft.P owerShellISE_profile.ps1<\/p>\n<\/td>\n<\/tr>\n

\n

 All users, Current Host – ISE  <\/p>\n<\/td>\n

\n

$PsHome\\Microsoft.PowerShellISE_profile.ps1<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Understanding the six Windows PowerShell profiles<\/h2>\n

The first thing to do to understand the six Windows PowerShell profiles is to keep in mind that they move. They change (sort of like the staircases at Hogwarts<\/a>). As long as you realize that they are a moving target, you will be fine. In most cases, when talking about the Windows PowerShell profile, people are referring to the current user, current<\/i> host<\/i> profile. In fact, if no one qualifies the Windows PowerShell profile with its associated scope or description, it is safe to assume that they are talking about the C<\/em>urrent User, Current Host<\/i> <\/i>profile.<\/p>\n

Note   <\/b>A Windows PowerShell profile (any one of the six) is simply a Windows PowerShell script. It has a special name, and it resides in a special place, but it is simply a script. In this regard, it is sort of like the old-fashioned autoexec.bat<\/a> batch file. Because the Windows PowerShell profile is a Windows PowerShell script, you must enable the Script Execution policy prior to configuring and using a Windows PowerShell profile. For information about the Script Execution policy refer to this collection of Hey, Scripting Guy! Blogs<\/a>.<\/p>\n

Examining the $profile variable<\/h2>\n

When you query the $profile<\/b> automatic variable, it returns the path to the C<\/em>urrent User, Current Host<\/i> profile. This makes sense, and it is a great way to easily access the path to the profile. The following script illustrates this technique from within the Windows PowerShell console.<\/p>\n

PS C:\\> $profile<\/p>\n

C:\\Users\\ed.IAMMRED\\Documents\\WindowsPowerShell\\Microsoft.PowerShell_profile.ps1<\/p>\n

Inside the Windows PowerShell ISE, when I query the $profile<\/b> automatic variable, I receive the output that is shown here.<\/p>\n

PS C:\\Users\\ed.IAMMRED> $profile<\/p>\n

C:\\Users\\ed.IAMMRED\\Documents\\WindowsPowerShell\\Microsoft.PowerShellISE<\/b>_profile.ps1<\/p>\n

To save you a bit of analyzing…<\/p>\n

The difference between the Windows PowerShell console C<\/em>urrent User, Current Host<\/i> <\/i>profile path and the Windows PowerShell ISE C<\/em>urrent User, Current Host<\/i> profile path is three letters: ISE. <\/i><\/p>\n

BB, these three letters are probably causing you problems. More than likely, you are setting something in your Windows PowerShell console profile, and it is not available inside the Windows PowerShell ISE.<\/p>\n

Unraveling the profiles<\/h3>\n

You can pipe the $profile <\/b>variable to the Get-Member<\/b> cmdlet and see additional properties that exist on the $profile<\/b> variable. This technique is shown here.<\/p>\n

PS C:\\> $PROFILE | Get-Member -MemberType noteproperty | select name<\/p>\n

 <\/p>\n

Name<\/p>\n

—-<\/p>\n

AllUsersAllHosts<\/p>\n

AllUsersCurrentHost<\/p>\n

CurrentUserAllHosts<\/p>\n

CurrentUserCurrentHost<\/p>\n

If you are accessing the $profile<\/b> variable from within the Windows PowerShell console, the AllUsersCurrentHost<\/b> and the CurrentUserCurrentHost<\/b> note properties refer to the Windows PowerShell console. If you access the $profile<\/b> variable from within the Windows PowerShell ISE, the AllUsersCurrentHost<\/b> and the CurrentUserCurrentHost <\/b>note properties refer to the Windows PowerShell ISE profiles.<\/p>\n

Using the $profile variable to refer to more than the current host<\/h3>\n

When you reference the $profile<\/b> variable, by default it refers to the C<\/em>urrent User, Current Host<\/i> <\/i>profile. If you pipe the variable to the Format-List<\/b> cmdlet, it still refers to the C<\/em>urrent User, Current Host<\/i> profile. This technique is shown here.<\/p>\n

PS C:\\> $PROFILE | Format-List *<\/p>\n

C:\\Users\\ed.IAMMRED\\Documents\\WindowsPowerShell\\Microsoft.PowerShell_profile.ps1<\/p>\n

This leads to a bit of confusion, especially because the Get-Member<\/b> cmdlet reveals the existence of multiple profiles and multiple note properties. The way to see all of the profiles for the current host, is to use the force <\/i>parameter. It reveals the hidden properties. The command illustrating this technique is shown here.<\/p>\n

$PROFILE | Format-List * -Force<\/p>\n

The command and the associated output from the command are shown in the image that follows.<\/p>\n

\"Image<\/a><\/p>\n

It is possible to directly access each of these specific properties just like you would access any other property—via dotted notation. This technique is shown here.<\/p>\n

$PROFILE.CurrentUserAllHosts<\/p>\n

The path to each of the four profiles for the Windows PowerShell console are shown in the image that follows.<\/p>\n

\"Image<\/a><\/p>\n

Determine if a specific profile exists<\/h2>\n

To determine if a specific profile exists, use the Test-Path <\/b>cmdlet and the appropriate flavor <\/i>of the $profile<\/b> variable. For example, to determine if a C<\/em>urrent User, Current Host<\/i> <\/i>profile exists you can use the $profile<\/b> variable with no modifier, or you can use the Cu<\/strong>rrentUserCurrentHost<\/b> note property. The following example illustrates both of these.<\/p>\n

PS C:\\> test-path $PROFILE<\/p>\n

True<\/p>\n

PS C:\\> test-path $PROFILE.CurrentUserCurrentHost<\/p>\n

True<\/p>\n

PS C:\\><\/p>\n

In the same manner, the other three profiles that apply to the current host (in this example, I am using the Windows PowerShell console) are determined to not exist. This is shown in the code that follows.<\/p>\n

PS C:\\> test-path $PROFILE.AllUsersAllHosts<\/p>\n

False<\/p>\n

PS C:\\> test-path $PROFILE.AllUsersCurrentHost<\/p>\n

False<\/p>\n

PS C:\\> test-path $PROFILE.CurrentUserAllHosts<\/p>\n

False<\/p>\n

PS C:\\><\/p>\n

Creating a new profile<\/h2>\n

To create a new profile for current user all hosts, <\/i>use the Cu<\/strong>rrentUserAllHosts<\/b> <\/i>property of the $profile<\/b> automatic variable, and the New-Item<\/b> cmdlet. This technique is shown here.<\/p>\n

PS C:\\> new-item $PROFILE.CurrentUserAllHosts -ItemType file -Force<\/p>\n

    Directory: C:\\Users\\ed.IAMMRED\\Documents\\WindowsPowerShell<\/p>\n

 <\/p>\n

Mode                LastWriteTime     Length Name<\/p>\n

—-                ————-     —— —-<\/p>\n

-a—         5\/17\/2012   2:59 PM          0 profile.ps1<\/p>\n

To open the profile for editing, use the ise<\/b> <\/i>alias as shown here.<\/p>\n

ise $PROFILE.CurrentUserAllHosts<\/p>\n

When you are finished editing the profile, save it, close the Windows PowerShell console, reopen the Windows PowerShell console, and test that your changes work properly.<\/p>\n

BB, that is all there is to using the $profile<\/b> variable to discover different Windows PowerShell profiles. Windows PowerShell Profile Week will continue tomorrow when I will talk about editing and testing a Windows PowerShell profile.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, discusses the six different Windows PowerShell profiles, and when to use each.  Hey, Scripting Guy! Dude, I have been reading some of the posts in your most excellent blog; and first of all, I want to say I think you are great. Now for the question: I do not […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[51,3,4,45],"class_list":["post-9361","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, discusses the six different Windows PowerShell profiles, and when to use each.  Hey, Scripting Guy! Dude, I have been reading some of the posts in your most excellent blog; and first of all, I want to say I think you are great. Now for the question: I do not […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/9361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=9361"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/9361\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=9361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=9361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=9361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}