{"id":7242,"date":"2020-02-10T13:08:57","date_gmt":"2020-02-10T18:08:57","guid":{"rendered":"https:\/\/jdhitsolutions.com\/blog\/?p=7242"},"modified":"2020-02-13T09:33:55","modified_gmt":"2020-02-13T14:33:55","slug":"powershell-remoting-profiles-with-windows-terminal","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/","title":{"rendered":"PowerShell Remoting Profiles with Windows Terminal"},"content":{"rendered":"<p>I have jumped in the deep end and fully committed to Windows Terminal as my default PowerShell environment. I love having one interface with tabs for different terminal profiles. Windows Terminal makes it easy for me to have tabs open to PowerShell 7, Windows PowerShell, an Ubuntu instance or even a PowerShell session with no profile. The last piece I needed was an easy way to launch a Windows Terminal profile and connect to a remote computer. Want to see how I did it?<\/p>\n<p><!--more--><\/p>\n<p>First I created a new profile in my Windows Terminal settings. I'm going to assume you know how to do that or can figure it out. If you copy and paste an existing profile, don't forget to set a new GUID.\u00a0 For my first remote profile, I wanted to create a PowerShell remoting session to my test domain controller DOM1. Here's my Windows Terminal profile for that part.<\/p>\n<pre class=\"lang:ps mark:0 decode:true\">{\n        \"acrylicOpacity\": 0.5,\n        \"background\": \"#0a52e2\",\n        \"closeOnExit\": true,\n        \"colorScheme\": \"Jeff\",\n        \"commandline\": \"powershell.exe -nologo -noprofile -noexit -file c:\\\\scripts\\\\wtpsremote.ps1 dom1\",\n        \"cursorColor\": \"#FFFFFF\",\n        \"cursorShape\": \"underscore\",\n        \"fontFace\": \"Cascadia Code\",\n        \"fontSize\": 14,\n        \"guid\": \"{b89c512a-cd2b-4fb4-a6d2-3366cee85970}\",\n        \"historySize\": 9001,\n        \"icon\": \"ms-appx:\/\/\/ProfileIcons\/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png\",\n        \"name\": \"DOM1\",\n        \"padding\": \"0, 0, 0, 0\",\n        \"snapOnInput\": true,\n        \"startingDirectory\": \"%USERPROFILE%\",\n        \"tabTitle\": \"PSRemote: DOM1.Company.Pri\",\n        \"useAcrylic\": false\n   },\n<\/pre>\n<p>The magic bits are centered on the commandline setting. In my profile I'm telling Windows Terminal to start Windows PowerShell with no logo, no profile and not to exit. I'm then providing a file and an argument for that script. I initially fussed with -Command but eventually found it easier to simply call a script file. The wtpsremote.ps1 file, creates the remoting session.<\/p>\n<pre class=\"lang:ps mark:0 decode:true\">#requires -version 5.1\n\n#wtpsremote.ps1\n\n[cmdletbinding()]\nParam(\n    [Parameter(Position = 0, Mandatory, HelpMessage = \"Specify remote computer name\")]\n    [ValidateNotNullOrEmpty()]\n    [string]$Computername,\n    [pscredential]$Credential,\n    [Parameter( HelpMessage = \"A profile script to run in the remote session\")]\n    [ValidateScript( {Test-Path $_})]\n    [string]$RemoteProfile = \"C:\\scripts\\RemoteProfile.ps1\",\n    [Parameter(HelpMessage = \"Specify a remote endpoint other than the default Microsoft.powershell\")]\n    [string]$ConfigurationName,\n    [int32]$Port,\n    [switch]$UseSSL\n)\n\n#remove this this parameter if specified since it can't be used to create a new PSSession\n[void]($PSBoundParameters.Remove(\"RemoteProfile\"))\n\n#Create a new remoting session splatting the parameters passed to this script\n$remote = New-PSSession @PSBoundParameters\n\n#run the remote profile script\nif ($RemoteProfile) {\n    Invoke-Command -Session $remote -FilePath $RemoteProfile -HideComputerName |\n        Select-Object -property * -ExcludeProperty runspaceID |\n        Format-Table -AutoSize\n}\n\n#open the pssession\nEnter-PSSession -session $remote\n\n$msg = @\"\n Reminder:                                                                        \n Remove the `$remote pssession after you exit and before you close the profile tab.\n                                                                                  \n PS C:\\&gt; `$remote | Remove-PSSession                                               \n PS C:\\&gt; exit                                                                     \n\"@\n\n#you may need to adjust colors based on your profile settings\nWrite-host $msg -ForegroundColor Magenta -BackgroundColor Gray\n<\/pre>\n<p>The script takes a number of parameters related to creating a new PSSession, which it does and then connects to it. And the script goes a bit further.<\/p>\n<p>Normally, when you launch a PowerShell remoting session, no profile scripts are run. But this script lets you specify local file that can be run remotely, in essence as a profile script. This is the default I use.<\/p>\n<pre class=\"lang:ps mark:0 decode:true\">#requires -version 5.1\n\n#this is a remote profile script\n\n#create a new prompt function for the remote session\n#how long has this session been running?\n$initiated = Get-Date\n\n$remotePrompt = {\n    #display the session runtime without the milliseconds\n    $ts = ((Get-Date) - $initiated).ToString().split(\".\")[0]\n    Write-Host \"&gt;$ts&lt; \" -ForegroundColor yellow -nonewline\n    \"PS $($executionContext.SessionState.Path.CurrentLocation)$('&gt;' * ($nestedPromptLevel + 1)) \";\n}\n\nSet-Item -Path function:\\prompt -Value $remotePrompt -Force\n\nSet-Location C:\\\nClear-Host\n\n#display some information about the remote computer\nGet-CimInstance -ClassName Win32_OperatingSystem |\nSelect-Object @{Name=\"Computer\";Expression={$_.CSName}},\n@{Name=\"OS\";Expression = {$_.Caption}},\n@{Name=\"PSVersion\";Expression = {$PSVersionTable.PSVersion}},\n@{Name=\"User\";Expression = {Whoami.exe}}\n<\/pre>\n<p>The profile script defines a prompt for the remote session that will show you how long you have been connected. It also displays a summary about the remote computer. You can add whatever else you might need such as defining variables, aliases or importing modules.<\/p>\n<p>Going back to wtpsremote.ps`, the last step is to display a reminder.\u00a0 If you simply close the profile tab, the remoting session will remain in a disconnected state until the remote computer cleans it up or is rebooted. To be a good network citizen, when you are finished type 'exit' to leave the remote session. This will dump you back in the terminal profile running Windows PowerShell. You should remove the pssession and then you can exit or close the profile tab.<\/p>\n<p>Here's what I get when I open this Windows Terminal profile.<\/p>\n<p><a href=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image-6.png\"><img loading=\"lazy\" decoding=\"async\" style=\"display: inline; background-image: none;\" title=\"A Windows Terminal PowerShell Remote Tab\" src=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png\" alt=\"A Windows Terminal PowerShell Remote Tab\" width=\"1028\" height=\"429\" border=\"0\" \/><\/a><\/p>\n<p>As I use the terminal, the prompt updates to show me how long I have been connected. When finished, I can exit.<\/p>\n<p><a href=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image-7.png\"><img loading=\"lazy\" decoding=\"async\" style=\"display: inline; background-image: none;\" title=\"A remote session prompt\" src=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-7.png\" alt=\"A remote session prompt\" width=\"1028\" height=\"520\" border=\"0\" \/><\/a><\/p>\n<p>It is at this point that I would remove the pssession and exit the tab.<\/p>\n<p>My connection script also lets you specify alternate credentials and even an alternate endpoint. Here's a profile for SRV1 that connects with specific credentials and connects to the PowerShell 7 endpoint.<\/p>\n<pre class=\"lang:ps mark:0 decode:true\">{\n    \"acrylicOpacity\": 0.5,\n    \"background\": \"#808285\",\n    \"closeOnExit\": true,\n    \"colorScheme\": \"Jeff\",\n    \"commandline\": \"powershell.exe -nologo -noprofile -noexit -file c:\\\\scripts\\\\wtpsremote.ps1 -computername srv1 -credential company\\\\administrator -configurationname PowerShell.7.0.0-rc.2\",\n    \"cursorColor\": \"#FFFFFF\",\n    \"cursorShape\": \"underscore\",\n    \"fontFace\": \"Cascadia Code\",\n    \"fontSize\": 14,\n    \"guid\": \"{173fd06c-883a-404b-97bd-9f955a0e85f0}\",\n    \"historySize\": 9001,\n    \"icon\": \"ms-appx:\/\/\/ProfileIcons\/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png\",\n    \"name\": \"SRV1\",\n    \"padding\": \"0, 0, 0, 0\",\n    \"snapOnInput\": true,\n    \"startingDirectory\": \"%USERPROFILE%\",\n    \"tabTitle\": \"PSRemote: SRV1.Company.Pri\",\n    \"useAcrylic\": false\n},\n<\/pre>\n<p><a href=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image-8.png\"><img loading=\"lazy\" decoding=\"async\" style=\"display: inline; background-image: none;\" title=\"A Windows Terminal PowerShell Remote Session to an alternate endpoint\" src=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-8.png\" alt=\"A Windows Terminal PowerShell Remote Session to an alternate endpoint\" width=\"1028\" height=\"462\" border=\"0\" \/><\/a><\/p>\n<p>I am finding these remote tabs very useful and hope you will too. Enjoy!<\/p>\n<h3>Update<\/h3>\n<p><span data-offset-key=\"2ihlr-0-0\">I updated my techniques and code for creating remote profiles in Windows Terminal to now support cross-platform. Read about it <a href=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/7257\/cross-platform-powershell-profiles-with-windows-terminal\/\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>.<br \/>\n<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have jumped in the deep end and fully committed to Windows Terminal as my default PowerShell environment. I love having one interface with tabs for different terminal profiles. Windows Terminal makes it easy for me to have tabs open to PowerShell 7, Windows PowerShell, an Ubuntu instance or even a PowerShell session with no&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"New on the blog: #PowerShell Remoting Profiles with Windows Terminal","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[4,615],"tags":[534,84,87,616],"class_list":["post-7242","post","type-post","status-publish","format-standard","hentry","category-powershell","category-windows-terminal","tag-powershell","tag-profile","tag-remoting","tag-windows-terminal"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>PowerShell Remoting Profiles with Windows Terminal &#8226; The Lonely Administrator<\/title>\n<meta name=\"description\" content=\"Windows Terminal is my default PowerShell host for everything. Now I can also use it to create tabs to PowerShell remoting sessions. Here&#039;s how I did it.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PowerShell Remoting Profiles with Windows Terminal &#8226; The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Windows Terminal is my default PowerShell host for everything. Now I can also use it to create tabs to PowerShell remoting sessions. Here&#039;s how I did it.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-10T18:08:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-02-13T14:33:55+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"PowerShell Remoting Profiles with Windows Terminal\",\"datePublished\":\"2020-02-10T18:08:57+00:00\",\"dateModified\":\"2020-02-13T14:33:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/\"},\"wordCount\":536,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/image_thumb-6.png\",\"keywords\":[\"PowerShell\",\"Profile\",\"remoting\",\"Windows Terminal\"],\"articleSection\":[\"PowerShell\",\"Windows Terminal\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/\",\"name\":\"PowerShell Remoting Profiles with Windows Terminal &#8226; The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/image_thumb-6.png\",\"datePublished\":\"2020-02-10T18:08:57+00:00\",\"dateModified\":\"2020-02-13T14:33:55+00:00\",\"description\":\"Windows Terminal is my default PowerShell host for everything. Now I can also use it to create tabs to PowerShell remoting sessions. Here's how I did it.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/image_thumb-6.png\",\"contentUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/image_thumb-6.png\",\"width\":1028,\"height\":429},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/7242\\\/powershell-remoting-profiles-with-windows-terminal\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"PowerShell\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/powershell\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PowerShell Remoting Profiles with Windows Terminal\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"PowerShell Remoting Profiles with Windows Terminal &#8226; The Lonely Administrator","description":"Windows Terminal is my default PowerShell host for everything. Now I can also use it to create tabs to PowerShell remoting sessions. Here's how I did it.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/","og_locale":"en_US","og_type":"article","og_title":"PowerShell Remoting Profiles with Windows Terminal &#8226; The Lonely Administrator","og_description":"Windows Terminal is my default PowerShell host for everything. Now I can also use it to create tabs to PowerShell remoting sessions. Here's how I did it.","og_url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/","og_site_name":"The Lonely Administrator","article_published_time":"2020-02-10T18:08:57+00:00","article_modified_time":"2020-02-13T14:33:55+00:00","og_image":[{"url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png","type":"","width":"","height":""}],"author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"PowerShell Remoting Profiles with Windows Terminal","datePublished":"2020-02-10T18:08:57+00:00","dateModified":"2020-02-13T14:33:55+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/"},"wordCount":536,"commentCount":2,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#primaryimage"},"thumbnailUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png","keywords":["PowerShell","Profile","remoting","Windows Terminal"],"articleSection":["PowerShell","Windows Terminal"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/","url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/","name":"PowerShell Remoting Profiles with Windows Terminal &#8226; The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#primaryimage"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#primaryimage"},"thumbnailUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png","datePublished":"2020-02-10T18:08:57+00:00","dateModified":"2020-02-13T14:33:55+00:00","description":"Windows Terminal is my default PowerShell host for everything. Now I can also use it to create tabs to PowerShell remoting sessions. Here's how I did it.","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#primaryimage","url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png","contentUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/02\/image_thumb-6.png","width":1028,"height":429},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7242\/powershell-remoting-profiles-with-windows-terminal\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"PowerShell","item":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},{"@type":"ListItem","position":2,"name":"PowerShell Remoting Profiles with Windows Terminal"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":7257,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7257\/cross-platform-powershell-profiles-with-windows-terminal\/","url_meta":{"origin":7242,"position":0},"title":"Cross Platform PowerShell Profiles with Windows Terminal","author":"Jeffery Hicks","date":"February 13, 2020","format":false,"excerpt":"Earlier this week I shared my techniques for creating a Windows Terminal profile that would open a remote PowerShell session. But with PowerShell 7, I can also connect to non-Windows machines using SSH. So why not extend my code to allow connecting to a Linux box? Before you try anything\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":8499,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/8499\/using-the-powershell-ise-as-a-remote-management-console\/","url_meta":{"origin":7242,"position":1},"title":"Using the PowerShell ISE as a Remote Management Console","author":"Jeffery Hicks","date":"July 20, 2021","format":false,"excerpt":"Way back before the days of PowerShell Core, or even VS Code for that matter, the PowerShell ISE was the center of my PowerShell world. I spent a lot of time finding ways to make it easier for me to use and to push it to its limits. Naturally, the\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/07\/ise-remotetab-form2.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":7476,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7476\/open-windows-terminal-powershell-split-paned\/","url_meta":{"origin":7242,"position":2},"title":"Open Windows Terminal PowerShell Split Paned","author":"Jeffery Hicks","date":"May 14, 2020","format":false,"excerpt":"The other night I presented for the Mississippi PowerShell User Group on how to get started using Windows Terminal. This has been my go-to PowerShell console for quite a while. I use Windows Terminal for everything. During the talk a question came up about starting a session with split panes.\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/wt-split.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/wt-split.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/wt-split.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/wt-split.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/05\/wt-split.png?resize=1050%2C600&ssl=1 3x"},"classes":[]},{"id":5073,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/5073\/powershell-sessions-and-vs-code\/","url_meta":{"origin":7242,"position":3},"title":"PowerShell Sessions and VS Code","author":"Jeffery Hicks","date":"June 8, 2016","format":false,"excerpt":"If you do any amount of PowerShell scripting you have most likely heard about Visual Studio Code. This is a free cross-platform light-weight editor from Microsoft. VS Code supports multiple languages and is extensible. I've tried different versions since it was first released but never found a reason to jump\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"image","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2016\/06\/image_thumb-5.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2016\/06\/image_thumb-5.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2016\/06\/image_thumb-5.png?resize=525%2C300 1.5x"},"classes":[]},{"id":7112,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7112\/testing-for-powershell-in-windows-terminal\/","url_meta":{"origin":7242,"position":4},"title":"Testing for PowerShell in Windows Terminal","author":"Jeffery Hicks","date":"December 20, 2019","format":false,"excerpt":"I have pretty much migrated to Windows Terminal as my primary PowerShell interface. Even though my daily session is PowerShell 7 I love that I can open up other sessions in the same application. yes, I know there are still limitations and that many of you prefer ConEmu. And that's\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-30.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-30.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-30.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/12\/image_thumb-30.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6800,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6800\/a-powershell-proof-of-concept-with-windows-terminal\/","url_meta":{"origin":7242,"position":5},"title":"A PowerShell Proof of Concept with Windows Terminal","author":"Jeffery Hicks","date":"July 8, 2019","format":false,"excerpt":"I recently updated my Windows 10 systems to the 1903 release. One of the reasons is that I wanted to try out the new Windows Terminal preview. You can find it in the Windows Store. This is bleeding edge stuff and far from complete but promises to be a great\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/07\/image_thumb.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/07\/image_thumb.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/07\/image_thumb.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/7242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=7242"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/7242\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=7242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=7242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=7242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}