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 is good because all you have is a C:\\ prompt, which I know makes some people a little uncomfortable. But with Windows Server 2008 R2, there is another option: PowerShell.
\n<\/p>\n
I've started experimenting with Windows PowerShell as my default shell on an R2 Server Core installation. Now when I logon I get a PowerShell window, not a CMD window. I can setup a PowerShell profile and be fully ready to manage my server. Of course there's so much I can do remotely now but for the sake of discussion let's say I have a need to logon to the console. Normally I would get a CMD window. And while I could start PowerShell from the C:\\ prompt, if I know I always want PowerShell, why not make it the default?<\/p>\n
The change is very easy to do. But because it involves the registry: backup and test thoroughly in a non-production environment<\/strong>. The registry key to change is HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\winlogon. Look for the Shell entry. Here's how you can do it with PowerShell: PSPath : Microsoft.PowerShell.Core\\Registry::HKEY_LOCAL_MACHINE\\software\\microsoft\\windows nt\\currentversion\\winlogon [cc lang=\"PowerShell\"] But now my shell is set to PowerShell. I logoff and back on and I now have a PowerShell prompt. I can still run commands like the sconfig script and other CMD tools. So far I haven't found any downside to changing the default shell but if you know of any, please let me know.<\/p>\n","protected":false},"excerpt":{"rendered":" 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 is good because all you…<\/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":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[72,75,110,135],"tags":[156,534,157,158,159],"class_list":["post-573","post","type-post","status-publish","format-standard","hentry","category-commandline","category-powershell-v2-0","category-registry","category-windows-server","tag-156","tag-powershell","tag-r2","tag-server-core","tag-shell"],"yoast_head":"\n
\n[cc lang=\"PowerShell\"]
\nPS C:\\> get-itemproperty \"hklm:\\software\\microsoft\\windows nt\\currentversion\\winlogon\" shell<\/p>\n
\nPSParentPath : Microsoft.PowerShell.Core\\Registry::HKEY_LOCAL_MACHINE\\software\\microsoft\\windows nt\\currentversion
\nPSChildName : winlogon
\nPSDrive : HKLM
\nPSProvider : Microsoft.PowerShell.Core\\Registry
\nshell : cmd.exe \/c \"cd \/d \"%USERPROFILE%\" & start cmd.exe \/k runonce.exe \/AlternateShellStartup\"
\n[\/cc]
\nNotice the shell value is essentially a CMD.EXE shell. We can change that value to anything we want. But first, let's save the value in case we ever want to revert back. You could simply export the entire Winlogon key, but I'm going to simply grab the shell value and save it to a file.
\n[cc lang=\"PowerShell\"]
\nPS C:\\> get-itemproperty \"hklm:\\software\\Microsoft\\windows NT\\currentversion\\winlogon\" Shell | select -ExpandProperty Shell | out-file savedshell.txt
\n[\/cc]
\nIf I ever need to restore this value, I would do something like this:<\/p>\n
\nPS C:\\> $shell=get-content .\\savedshell.txt
\nPS C:\\> $shell
\ncmd.exe \/c \"cd \/d \"%USERPROFILE%\" & start cmd.exe \/k runonce.exe \/AlternateShellStartup\"
\nPS C:\\> set-itemproperty \"hklm:\\software\\microsoft\\windows nt\\currentversion\\winlogon\" shell $shell
\n[\/cc]<\/p>\n