starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Question]Is support for GUI-less systems (server core) planned? #13214

New Issue
Closed
opened 2026-01-31 03:36:49 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 03:36:49 +00:00
Owner
Copy Link

Originally created by @AndrewSav on GitHub (Mar 27, 2021).

Description of the new feature/enhancement

Let me start with saying that I saw all these prior issue, and then mine is different: https://github.com/microsoft/terminal/issues/7560 https://github.com/microsoft/terminal/issues/2177 https://github.com/microsoft/terminal/issues/6717 https://github.com/microsoft/terminal/issues/6956 https://github.com/microsoft/terminal/issues/1643

The difference is that most of those issues ask about Windows 2019 server which is not on or past 1903, where Windows Core Server is, which is the key.

Windows Server Core, by the nature of not having GUI needs a comfortable terminal the most. Arguably on a GUI system, there may be other than command line ways to achieve one's goals, on a server core there are not. It has to be done in a terminal. And the terminal does not seem to be able to run on those systems.

So the question is: can it be supported on the windows server core systems that have at least 1903?

Originally created by @AndrewSav on GitHub (Mar 27, 2021). # Description of the new feature/enhancement Let me start with saying that I saw all these prior issue, and then mine is different: https://github.com/microsoft/terminal/issues/7560 https://github.com/microsoft/terminal/issues/2177 https://github.com/microsoft/terminal/issues/6717 https://github.com/microsoft/terminal/issues/6956 https://github.com/microsoft/terminal/issues/1643 The difference is that most of those issues ask about Windows 2019 server which is not on or past 1903, where Windows _Core_ Server is, which is the key. Windows Server Core, by the nature of not having GUI needs a comfortable terminal the most. Arguably on a GUI system, there may be other than command line ways to achieve one's goals, on a server core there are not. It has to be done in a terminal. And the terminal does not seem to be able to run on those systems. So the question is: can it be supported on the windows server _core_ systems that have at least 1903?
claunia commented 2026-01-31 03:36:51 +00:00
Author
Owner
Copy Link

@floh96 commented on GitHub (Mar 28, 2021):

Instead of trying to run the terminal on the Server directly I think it would be the better approach if you run the terminal on your local machine and connect to the server via SSH/winrm.

@floh96 commented on GitHub (Mar 28, 2021): Instead of trying to run the terminal on the Server directly I think it would be the better approach if you run the terminal on your local machine and connect to the server via SSH/winrm.
claunia commented 2026-01-31 03:36:51 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Mar 28, 2021):

No. This is not planned. The Windows Terminal is a graphical application that requires much of the desktop experience unavailable on core. Server Core will continue to have the classic console host window (that DOES receive updates from this repository).

For the most part though, you're not supposed to administrate from the local machine for server core. The point of Server Core isn't a comfortable local CUI experience; the point is minimal attackable surface. It is supposed to be administrated remotely with the local session as a last-chance recovery environment.

As such, the previous poster is correct. It is expected you use another machine as your terminal and remote to your server core machine.

@miniksa commented on GitHub (Mar 28, 2021): No. This is not planned. The Windows Terminal is a graphical application that requires much of the desktop experience unavailable on core. Server Core will continue to have the classic console host window (that DOES receive updates from this repository). For the most part though, you're not supposed to administrate from the local machine for server core. The point of Server Core isn't a comfortable local CUI experience; the point is minimal attackable surface. It is supposed to be administrated remotely with the local session as a last-chance recovery environment. As such, the previous poster is correct. It is expected you use another machine as your terminal and remote to your server core machine.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Issue-Question Product-Terminal Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13214
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?