Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Group Policy to control default Terminal setting #18302

Closed
htcfreek opened this issue Dec 10, 2024 · 1 comment · May be fixed by #18363
Closed

Group Policy to control default Terminal setting #18302

htcfreek opened this issue Dec 10, 2024 · 1 comment · May be fixed by #18363
Labels
In-PR This issue has a related PR Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@htcfreek
Copy link

Since a year or longer I can choose if WT is the default conhost.

Is it possible to implement a policy that allows company admins to control this centralized?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 10, 2024
@DHowett
Copy link
Member

DHowett commented Dec 10, 2024

Right now, enterprise administrators can use Group Policy to roll out registry changes as documented in this knowledgebase article.

@microsoft microsoft locked and limited conversation to collaborators Dec 10, 2024
@DHowett DHowett converted this issue into discussion #18303 Dec 10, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Dec 25, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
In-PR This issue has a related PR Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants