{"id":6371,"date":"2019-01-09T10:00:43","date_gmt":"2019-01-09T15:00:43","guid":{"rendered":"https:\/\/jdhitsolutions.com\/blog\/?p=6371"},"modified":"2019-01-10T12:10:50","modified_gmt":"2019-01-10T17:10:50","slug":"making-the-leap-to-powershell-core","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/","title":{"rendered":"Making the Leap to PowerShell Core"},"content":{"rendered":"

\"\"For years I have spent most of my time in a Windows PowerShell prompt. I have actually taken it as a badge of honor that I've been able to manage my day and all of my work from a PowerShell prompt. I also have created practically all of my content on Windows PowerShell. I will continue to write and present on Windows PowerShell, but I feel I need to jump into the future as well and that means PowerShell Core. So for 2019 I've decided to make a PowerShell Core session, still running on a Windows platform my primary PowerShell interface. I still have Windows PowerShell if I need it but I want to learn more about what I can and can't do from a PowerShell core prompt.<\/p>\n

<\/p>\n

Do You Need PowerShell Core?<\/h1>\n

When I mentioned on Twitter that I was making the move to PowerShell Core as my \"daily driver\" I got some feedback asking why or that it wasn't relevant to them. And it might not be. I don't have Linux based servers that I need to manage. Everything I run is still Windows Server 2016.\u00a0 I also am still running a Windows 10 desktop. Personally, I need to make the jump to truly learn what is new and different in PowerShell Core so that I can teach about it and develop content. But I also know that Windows PowerShell 5.1 is feature complete. Microsoft is no longer developing it. Windows PowerShell isn't going away but the future is clearly PowerShell Core. You can run PowerShell Core side by side with Windows PowerShell so it's not like I have to give one up for the other.<\/p>\n

If you need to manage non-Windows servers and those servers can run PowerShell Core, then it makes sense and is practically a requirement to run PowerShell Core on your desktop. Even though there are limitations today, PowerShell Core, and the underlying .NET Core, continues to be developed and updated. I would also argue that your next job might be in a more heterogeneous environment where your experience with PowerShell Core will be advantageous.<\/p>\n

Installing PowerShell Core<\/h1>\n

Even though I had PowerShell Core installed, I realized I didn't have the most current version. I used commands from my PSReleaseTools<\/a> module.<\/p>\n

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

I then downloaded with msi package for Windows.<\/p>\n

Get-PSReleaseAsset -Family Windows | where {$_.format -eq 'msi' -And $_.filename -match 'x64'} | \nSave-PSReleaseAsset -Path D:\\PS6\\ -Passthru\n<\/pre>\n
Running the file installed PowerShell Core in a few minutes and it didn't require reboot. I pinned the program to my Task Bar and I'm ready to go. I should not that there is no PowerShell ISE equivalent in PowerShell Core. But that doesn't matter since I adopted VS Code<\/a> as my main development tool a few years ago. If I really<\/em> need it, I can still fire up the PowerShell ISE.<\/p>\n
Profile Changes<\/h1>\n
Because I spend so much of my day at a PowerShell prompt, as you might expect I take full advantage of profile scripts to configure it. However, when I fire up PowerShell Core none of my current profile scripts apply. Remember, PowerShell Core and Windows PowerShell can run side by side. This means each has its own set of profile scripts.<\/p>\n
\"Windows<\/a><\/p>\n
\"PowerShell<\/a><\/p>\n
As you can see, the PowerShell Core paths are completely different. Like Windows PowerShell, these files don't exist. You need to create them. Since I wanted to re-create as much of my Windows PowerShell experience into PowerShell Core I started by copying existing profiles. In my Windows PowerShell session, I copied the Current User All Hosts profile script to the corresponding PowerShell Core file.<\/p>\n
copy $profile.CurrentUserAllHosts -Destination ~\\documents\\PowerShell\\profile.ps1\n<\/pre>\n
This profile tends to pre-load modules and define my global settings. However when I launched PowerShell Core, much of the script didn't run or threw errors. That is because I was trying to load modules that PowerShell Core knew nothing about. Module locations are different.<\/p>\n
\"Windows<\/a><\/p>\n
\"PowerShell<\/a><\/p>\n
I could re-install modules in PowerShell Core but that's a lot of work and overhead. The easier solution is to install the WindowsCompatibility module in PowerShell Core. In my profile script I added the command Add-WindowsPSModulePath<\/strong>. Once I do that then PowerShell Core can \"see\" all of the other installed modules.<\/p>\n
\"Adding<\/a><\/p>\n
There's no guarantee that every module will work in PowerShell Core. I already know that some won't due to limitations in the .NET Framework. I expect the major ones, like Active Directory, will eventually get refactored. Plus, that's one of the reasons for jumping into PowerShell Core. I want to learn what works and what doesn't (yet).<\/p>\n
I followed a similar process by copying the Current User Current Host script from its Windows PowerShell location to the corresponding PowerShell Core location. Today, there aren't multiple PowerShell Core hosts on my machine and I'm the only user, so technically I should be able to combine everything into the Current User Current Host script. But for now I think I'll keep the separate scripts for conceptual purposes. If I ever add something that introduces another PowerShell Core host, then I'm ready.<\/p>\n
Configure the Window<\/h1>\n
My last step was to configure the PowerShell Core window. Since I'm spending a lot of time in it I need to make it comfortable. I right-click on the system menu\u00a0 to get the Properties box.<\/p>\n
\"Adjusting<\/a><\/p>\n
I believe the default color scheme for PowerShell Core is black so I'll keep that. It also helps having a different color should I have Windows PowerShell also open. I decided to make my PowerShell Core window even more sexy by setting the opacity level. I could do the same for Windows PowerShell on Windows 10 but never felt motivated.<\/p>\n
On the Layout tab I set my window size and screen buffer size to 120x35. If you keep them the same you'll avoid the horizontal scroll bar. On the Font tab, because I have 4K monitors and have reached a certain maturity level, I set the font size to 24. I prefer using Consolas.<\/p>\n
\"PowerShell<\/a><\/h1>\n
More to Come<\/h1>\n
Next time I'll share with you the prompt function I developed for my PowerShell Core work. Over the course of the year I hope to share with you my experiences of working in and using PowerShell Core. I hope you'll share your experiences as well.<\/p>\n","protected":false},"excerpt":{"rendered":"
For years I have spent most of my time in a Windows PowerShell prompt. I have actually taken it as a badge of honor that I’ve been able to manage my day and all of my work from a PowerShell prompt. I also have created practically all of my content on Windows PowerShell. I will…<\/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: Making the Leap to #PowerShell Core","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,589],"tags":[590],"class_list":["post-6371","post","type-post","status-publish","format-standard","hentry","category-powershell","category-powershell-core","tag-powershell-core"],"yoast_head":"\nMaking the Leap to PowerShell Core • The Lonely Administrator<\/title>\n<meta name=\"description\" content=\"In 2019 I am making the leap and commitment to PowerShell Core, still running it on a Windows platform. A PowerShell Core session will be my daily driver.\" \/>\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\/6371\/making-the-leap-to-powershell-core\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Making the Leap to PowerShell Core • The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"In 2019 I am making the leap and commitment to PowerShell Core, still running it on a Windows platform. A PowerShell Core session will be my daily driver.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2019-01-09T15:00:43+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-01-10T17:10:50+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/07\/powershell-hero-194x300.jpg\" \/>\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\\\/6371\\\/making-the-leap-to-powershell-core\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"Making the Leap to PowerShell Core\",\"datePublished\":\"2019-01-09T15:00:43+00:00\",\"dateModified\":\"2019-01-10T17:10:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/\"},\"wordCount\":1047,\"commentCount\":10,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/powershell-hero-194x300.jpg\",\"keywords\":[\"PowerShell Core\"],\"articleSection\":[\"PowerShell\",\"PowerShell Core\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/\",\"name\":\"Making the Leap to PowerShell Core • The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/powershell-hero-194x300.jpg\",\"datePublished\":\"2019-01-09T15:00:43+00:00\",\"dateModified\":\"2019-01-10T17:10:50+00:00\",\"description\":\"In 2019 I am making the leap and commitment to PowerShell Core, still running it on a Windows platform. A PowerShell Core session will be my daily driver.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/powershell-hero.jpg\",\"contentUrl\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/powershell-hero.jpg\",\"width\":439,\"height\":678},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/6371\\\/making-the-leap-to-powershell-core\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"PowerShell\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/powershell\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Making the Leap to PowerShell Core\"}]},{\"@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":"Making the Leap to PowerShell Core • The Lonely Administrator","description":"In 2019 I am making the leap and commitment to PowerShell Core, still running it on a Windows platform. A PowerShell Core session will be my daily driver.","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\/6371\/making-the-leap-to-powershell-core\/","og_locale":"en_US","og_type":"article","og_title":"Making the Leap to PowerShell Core • The Lonely Administrator","og_description":"In 2019 I am making the leap and commitment to PowerShell Core, still running it on a Windows platform. A PowerShell Core session will be my daily driver.","og_url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/","og_site_name":"The Lonely Administrator","article_published_time":"2019-01-09T15:00:43+00:00","article_modified_time":"2019-01-10T17:10:50+00:00","og_image":[{"url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/07\/powershell-hero-194x300.jpg","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\/6371\/making-the-leap-to-powershell-core\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"Making the Leap to PowerShell Core","datePublished":"2019-01-09T15:00:43+00:00","dateModified":"2019-01-10T17:10:50+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/"},"wordCount":1047,"commentCount":10,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#primaryimage"},"thumbnailUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/07\/powershell-hero-194x300.jpg","keywords":["PowerShell Core"],"articleSection":["PowerShell","PowerShell Core"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/","url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/","name":"Making the Leap to PowerShell Core • The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#primaryimage"},"image":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#primaryimage"},"thumbnailUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/07\/powershell-hero-194x300.jpg","datePublished":"2019-01-09T15:00:43+00:00","dateModified":"2019-01-10T17:10:50+00:00","description":"In 2019 I am making the leap and commitment to PowerShell Core, still running it on a Windows platform. A PowerShell Core session will be my daily driver.","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#primaryimage","url":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/07\/powershell-hero.jpg","contentUrl":"https:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2018\/07\/powershell-hero.jpg","width":439,"height":678},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6371\/making-the-leap-to-powershell-core\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"PowerShell","item":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},{"@type":"ListItem","position":2,"name":"Making the Leap to PowerShell Core"}]},{"@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":6439,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6439\/friday-fun-with-a-cross-platform-powershell-prompt\/","url_meta":{"origin":6371,"position":0},"title":"Friday Fun with a Cross-Platform PowerShell Prompt","author":"Jeffery Hicks","date":"January 18, 2019","format":false,"excerpt":"This year is turning out to be all things cross-platform for me. Continuing this line of discussion I have something fun and simple today. A PowerShell prompt function that will work cross-platform and provide some meaningful information in what I think is a elegant manner. You may not need the\u2026","rel":"","context":"In "PowerShell"","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\/01\/image_thumb-20.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-20.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-20.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-20.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":610,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell-v2-0\/610\/powershell-quick-start-on-server-core-r2\/","url_meta":{"origin":6371,"position":1},"title":"PowerShell Quick Start on Server Core R2","author":"Jeffery Hicks","date":"March 29, 2010","format":false,"excerpt":"The great thing about the Server Core flavor that ships with Windows Server 2008 R2 is that it finally supports Windows PowerShell. I\u2019ve talked about this before. However, I think I neglected some of the finer points in getting started. You can (and should) run PowerShell on your R2 Core\u2026","rel":"","context":"In "PowerShell v2.0"","block_context":{"text":"PowerShell v2.0","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-v2-0\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":6428,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell-core\/6428\/a-powershell-core-out-gridview-solution\/","url_meta":{"origin":6371,"position":2},"title":"A PowerShell Core Out-Gridview Solution","author":"Jeffery Hicks","date":"January 15, 2019","format":false,"excerpt":"As many of you know, this year I've made the jump to PowerShell Core as my \"daily driver\". A major driving factor was to discover the limitations. There are certainly plenty of advantages as we move to a cross-platform world. But the PowerShell Core is based .NET Core which does\u2026","rel":"","context":"In "PowerShell Core"","block_context":{"text":"PowerShell Core","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell-core\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-16.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-16.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-16.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-16.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6449,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6449\/thinking-outside-the-box-with-another-powershell-prompt\/","url_meta":{"origin":6371,"position":3},"title":"Thinking Outside the Box with Another PowerShell Prompt","author":"Jeffery Hicks","date":"January 21, 2019","format":false,"excerpt":"TThe other day I shared my simple PowerShell prompt function that displayed a few pieces of potentially useful information in a color coded box. Today I have a slight variation that also contains a few improvements. One of the things that I was torn with in my previous version was\u2026","rel":"","context":"In "PowerShell"","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\/01\/image_thumb-23.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-23.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-23.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-23.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":6388,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6388\/maximizing-my-prompt-in-powershell-core\/","url_meta":{"origin":6371,"position":4},"title":"Maximizing My Prompt in PowerShell Core","author":"Jeffery Hicks","date":"January 10, 2019","format":false,"excerpt":"Yesterday I wrote about my intention to make PowerShell Core, running on Windows 10, my \"daily driver\". I've also written recently about using the PowerShell prompt function to provide a wide range of information. So I decided to combine the two, plus mix in some functionality from my other PowerShell\u2026","rel":"","context":"In "PowerShell"","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\/01\/image_thumb-13.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-13.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-13.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":573,"url":"https:\/\/jdhitsolutions.com\/blog\/commandline\/573\/power-up-your-r2-server-core-shell\/","url_meta":{"origin":6371,"position":5},"title":"Power Up your R2 Server Core Shell","author":"Jeffery Hicks","date":"January 27, 2010","format":false,"excerpt":"I've recently started using the Server Core option for my test servers, especially for things like domain controllers. I can get by with smaller disk and memory requirements. Once you get the server configured, there's very little you have to do that actually requires logging on to the server. Which\u2026","rel":"","context":"In "CommandLine"","block_context":{"text":"CommandLine","link":"https:\/\/jdhitsolutions.com\/blog\/category\/commandline\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/6371","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=6371"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/6371\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=6371"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=6371"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=6371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}