{"id":253,"date":"2017-09-26T20:01:29","date_gmt":"2017-09-27T02:01:29","guid":{"rendered":"http:\/\/draith.com\/?p=253"},"modified":"2017-09-26T20:01:29","modified_gmt":"2017-09-27T02:01:29","slug":"customize-your-powershell-profile-for-useful-startup-actions","status":"publish","type":"post","link":"https:\/\/draith.com\/?p=253","title":{"rendered":"Customize your PowerShell profile for useful startup actions"},"content":{"rendered":"

Did you know you can make PowerShell run any commands you want when you start a shell? This is amazingly useful for gathering information, making settings changes, or kicking off processes – all at shell startup. There are plenty of places that talk about the profiles, so I won’t go into each type, but long story short there are almost 10 different profiles when you account for 32 and 64 bit PowerShell. Some of them are explained in detail here.<\/a><\/p>\n

For my example here, I am going to deal with the %UserProfile%\\My Documents\\WindowsPowerShell\\profile.ps1 <\/em> profile, which affects the current user, but all shells. This is useful for when you are switching back and forth between the ISE and console – say when you are testing new scripts. By default this file won’t exist – you will have to create it if it doesn’t. <\/p>\n

#See if your profile file exists.  Checks the 'My Documents\\WindowsPowerShell' directory\nTest-Path $profile<\/pre>\n
The profile file is really just a .ps1 file.  You can put any PowerShell you want in this file.  Say you want to get a random Cat Fact<\/a> every time you start a shell? (who am I to judge?)<\/p>\n
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12\n((((invoke-webrequest -uri https:\/\/catfact.ninja\/fact -Method get).content).split(':')[1])).trim('\",\"length\"')\n<\/pre>\n
\"\"<\/p>\n
There are some really useful things you can do now that you know you can run anything.  For example – this will show the number of running PowerShell processes, along with WinRM service status:<\/p>\n
write-host -ForegroundColor Green \"PowerShell Processes: \" (Get-process 'PowerShell').count\nwrite-host -ForegroundColor Green \"WinRM Status: \" (Get-service 'winrm').status<\/pre>\n
And this will show the PowerShell module paths:<\/p>\n
write-host -ForegroundColor Green \"Module Paths:\"\nforeach ($module in ($env:PSModulePath).Split(\";\")){write-host -ForegroundColor Green \"    \"$module}<\/pre>\n
\"\"<\/p>\n
Notice here – I also added a simple “cd c:\\blog” to my profile – really useful for starting straight in your scripts directory (no more “cd c:\\workspaces\\app\\development\\scripts….” every time you start a console)<\/p>\n
But you can do even more!  Full functions can be loaded into your profile and are available immediately.  One of my favorites is one that will add a Start-RDP function, so I can initiate a remote desktop session without ever touching the start menu!  How cool is this?<\/p>\n
write-host -ForegroundColor Green \"PowerShell Processes: \" (Get-process 'PowerShell').count\nwrite-host -ForegroundColor Green \"WinRM Status: \" (Get-service 'winrm').status\nwrite-host -ForegroundColor Green \"Module Paths:\"\nforeach ($module in ($env:PSModulePath).Split(\";\")){write-host -ForegroundColor Green \"    \"$module}\ncd C:\\Blog\nfunction Start-RDP\n{\n    param  \n    (  \n        [Parameter(\n            Position = 0,\n            ValueFromPipeline=$true,\n            Mandatory=$true\n        )]\n        [ValidateNotNullOrEmpty()]\n        [string]\n        $ServerName\n    )\n    mstsc \/v:$ServerName \n}<\/pre>\n
\"\"<\/p>\n
There is also a special function you can put in your profile – it’s the ‘prompt’ function.  This will change the PowerShell command line prompt to whatever you want!  Just create a new function called ‘prompt’, write-host anything you want into the function, and make sure you put a ‘return ” “‘ at the end – it’s that’s simple!  You can put some great data right on the prompt – for example, you can make the current time show up each time the prompt is shown!  This is really useful for measuring how long something takes to run if you don’t want to pull out measure-object!  Here is my prompt, along with the full profile:<\/p>\n
function prompt\n{\n    $time = \"(\"+(get-date).ToLongTimeString()+\")\"\n    write-host -NoNewline -ForegroundColor Green \"PS \" (Get-Location).Path $time \">\"\n    return \" \"\n}\nwrite-host -ForegroundColor Green \"PowerShell Processes: \" (Get-process 'PowerShell').count\nwrite-host -ForegroundColor Green \"WinRM Status: \" (Get-service 'winrm').status\nwrite-host -ForegroundColor Green \"Module Paths:\"\nforeach ($module in ($env:PSModulePath).Split(\";\")){write-host -ForegroundColor Green \"    \"$module}\ncd C:\\Blog\nfunction Start-RDP\n{\n    param  \n    (  \n        [Parameter(\n            Position = 0,\n            ValueFromPipeline=$true,\n            Mandatory=$true\n        )]\n        [ValidateNotNullOrEmpty()]\n        [string]\n        $ServerName\n    )\n    mstsc \/v:$ServerName \n}<\/pre>\n
And the outcome:
\n\"\"<\/p>\n
It’s that simple!  Customize your profile, and start being productive quicker!  Leave a comment below to tell me what your favorite profile modifications are!!<\/p>\n","protected":false},"excerpt":{"rendered":"
Did you know you can make PowerShell run any commands you want when you start a shell? This is amazingly useful for gathering information, making settings changes, or kicking off processes – all at shell startup. There are plenty of places that talk about the profiles, so I won’t go into each type, but long … Continue reading “Customize your PowerShell profile for useful startup actions”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[16],"class_list":["post-253","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-powershell"],"_links":{"self":[{"href":"https:\/\/draith.com\/index.php?rest_route=\/wp\/v2\/posts\/253","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/draith.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/draith.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/draith.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/draith.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=253"}],"version-history":[{"count":0,"href":"https:\/\/draith.com\/index.php?rest_route=\/wp\/v2\/posts\/253\/revisions"}],"wp:attachment":[{"href":"https:\/\/draith.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=253"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/draith.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=253"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/draith.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=253"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}