{"id":1302,"date":"2014-05-24T00:01:00","date_gmt":"2014-05-24T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2014\/05\/24\/whats-in-your-powershell-profile-powershell-team-favorites\/"},"modified":"2014-05-24T00:01:00","modified_gmt":"2014-05-24T00:01:00","slug":"whats-in-your-powershell-profile-powershell-team-favorites","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/whats-in-your-powershell-profile-powershell-team-favorites\/","title":{"rendered":"What’s in Your PowerShell Profile? Powershell Team Favorites"},"content":{"rendered":"

Summary<\/b>: Microsoft Scripting Guy Ed Wilson talks to members of the Windows PowerShell team about what is in their Windows PowerShell profile.\nMicrosoft Scripting Guy, Ed Wilson, is here. I’m wrapping up the week with profile excerpts from the Windows PowerShell team. There is some really cool stuff here.\nHemant Mahawar<\/b><\/span> indicated that he does not use a profile.\nThis is quite common for people who work in Windows PowerShell core. This is also a common theme I have run across from people who teach or otherwise work with customers on a regular basis. The danger, of course, is inadvertently picking up something that is in your profile, and expecting it to be in a default Windows PowerShell installation.\nLee Holmes<\/strong><\/span> shared a couple of really cool techniques.\n“Here are two killer techniques I use in my profile.”<\/p>\n

Use PSDefaultParameterValues on Out-Default<\/b><\/h4>\n

“This is only supported on Windows PowerShell 4.0 and later in Windows 8.1), but it lets you capture the output of the last command into a variable (I use $0<\/b>).”<\/p>\n

123 [C:windowssystem32]<\/p>\n

>> $PSDefaultParameterValues[“Out-Default:OutVariable”] = “0”\n <\/p>\n

124 [C:windowssystem32]<\/p>\n

>> Get-Command Watch-Clipboard\n <\/p>\n

CommandType     Name                                               Version    Source<\/p>\n

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

ExternalScript  Watch-Clipboard.ps1                                           d:documentstoolsWatch-Clipboard.ps1\n <\/p>\n

125 [C:windowssystem32]<\/p>\n

>> ise $0.Source<\/p>\n

Auto-register scheduled jobs<\/b><\/h4>\n

“My Windows PowerShell jobs are constantly being blasted from my machines. So I put their registration in my profile. When Windows PowerShell launches, it lets me know if the job is missing. If it is, it re-registers it.”<\/p>\n

if(-not (Get-ScheduledJob -Name PowerFix -EA Ignore))<\/p>\n

{<\/p>\n

    $trigger = New-ScheduledTaskTrigger -Once -At (Get-Date) -RepetitionInterval (New-TimeSpan -Minutes 15) -RepetitionDuration ([TimeSpan]::MaxValue)<\/p>\n

    $null = Register-ScheduledJob -Name PowerFix -Trigger $trigger -ScriptBlock { powercfg -x -standby-timeout-ac 0 } -MaxResultCount 1<\/p>\n

}\nSteve Lee<\/strong><\/span> is a principal test lead in Windows PowerShell and WMI, and he provided links to several resources.<\/p>\n