{"id":750,"date":"2020-06-18T14:26:27","date_gmt":"2020-06-18T19:26:27","guid":{"rendered":"https:\/\/itblog.ldlnet.net\/?p=750"},"modified":"2020-06-18T14:33:56","modified_gmt":"2020-06-18T19:33:56","slug":"windows-server-core-how-to-have-powershell-automatically-start-when-logging-onto-the-session","status":"publish","type":"post","link":"https:\/\/itblog.ldlnet.net\/index.php\/2020\/06\/18\/windows-server-core-how-to-have-powershell-automatically-start-when-logging-onto-the-session\/","title":{"rendered":"Windows Server Core – How to have PowerShell automatically start when logging onto the session."},"content":{"rendered":"\n

In my environment, I have a Windows Server (2019) Core edition server installed with Exchange 2019. Most of the time, I have to get on the server to run PowerShell commands for maintenance purposes, etc…<\/p>\n\n\n\n

Well, by default, Windows Server Core opens the command prompt when you logon and then I have to manually open PowerShell from there to run cmdlets, etc…<\/p>\n\n\n\n

However, if you would like to change the default cmd to PowerShell, you can change it by changing the Registry value.<\/p>\n\n\n\n

The Registry that I\u2019m talking is located under the following location:<\/p>\n\n\n

HKLM:\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WinLogon <\/pre>\n\n\n\n
\"\"
Change the Shell Value in the Registry<\/figcaption><\/figure>\n\n\n\n
The easiest way I see to change the value is to use the Set-ItemProperty<\/em><\/strong> cmdlet within PowerShell.<\/p>\n\n\n\n
Open Windows PowerShell within Server Core command prompt. You can type \u201cPowerShell\u201d on your command prompt.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Then, enter the following command on PowerShell console and hit enter:<\/p>\n\n\n
Set-ItemProperty -Path 'HKLM:\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WinLogon' -Name Shell -Value 'PowerShell.exe'<\/pre>\n\n\n\n
Once completed, you will need to reboot the computer from PowerShell:<\/p>\n\n\n
Restart-Computer -force<\/pre>\n\n\n\n
When the computer has rebooted and you have logged on, PowerShell should load by default instead of Command Prompt.<\/p>\n\n\n\n
EVEN MORE INFORMATION<\/h3>\n\n\n\n
Now, since I have an Exchange Server installed on this server, there is a Command in the $bin directory called LaunchEMS.cmd<\/em><\/strong> that will load the Exchange Management Shell for you. So instead of loading just PowerShell, I tell WinLogon to load Exchange Management Shell so that I do not have to do any additional typing or searching for EMS on the box. Remember, Server Core has no GUI!<\/p>\n\n\n\n
I run the same commands as above, but just change the value to LaunchEMS.cmd<\/em><\/strong><\/p>\n\n\n
Set-ItemProperty -Path 'HKLM:\\Software\\Microsoft\\Windows NT\\CurrentVersion\\WinLogon' -Name Shell -Value 'LaunchEMS.cmd'<\/pre>\n\n\n\n
Then Restart the Computer:<\/p>\n\n\n
Restart-Computer -force<\/pre>\n\n\n\n
Once Rebooted, you can logon and EMS will be the only window prompt that loads in the shell!<\/p>\n\n\n\n
\"\"
Exchange Management Shell loads when you logon<\/figcaption><\/figure>\n\n\n\n
NOTE: You can always run cmd <\/strong>from the prompt to open Command Prompt and also run PowerShell.exe <\/strong>to open regular PowerShell<\/em> from the EMS Session Window. <\/p>\n\n\n\n
REMAIN POSITIVE!
THANKS FOR READING!<\/h2>\n\n\n\n
REFERENCES:<\/strong>
Windows Server Core: How to start PowerShell by Default<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
In my environment, I have a Windows Server (2019) Core edition server installed with Exchange 2019. Most of the time, I have<\/p>\n
Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":147,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,2,3,16],"tags":[164,245,244,246,8,163,242,20,247,226,243],"class_list":["post-750","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-exchange","category-general","category-powershell","category-windows","tag-hklm","tag-launchems","tag-launchems-cmd","tag-logon","tag-powershell","tag-registry","tag-server-core","tag-windows","tag-windows-logon","tag-windows-server-core","tag-winlogon","odd"],"_links":{"self":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/750","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/comments?post=750"}],"version-history":[{"count":3,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/750\/revisions"}],"predecessor-version":[{"id":755,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/750\/revisions\/755"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media\/147"}],"wp:attachment":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media?parent=750"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/categories?post=750"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/tags?post=750"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}