Procedure to use a custom profiles.json for all Active Directory profiles #7850

Open
opened 2026-01-31 01:14:14 +00:00 by claunia · 0 comments
Owner

Originally created by @lauxjpn on GitHub (May 1, 2020).

As far as I can see, the profiles.json file is currently located in the AppData\Local folder.

Wouldn't that mean, that I would need to make the same custom changes to the file on every machine I log into with the same user account, only to get the same terminal experience?

Also, there should be a simple (or at least documented) was to use the same custom profiles.json file for all active directory accounts (either forced or as the default but modifiable).

These both are much needed features for every administrator out there, so they don't have to tinker with the settings on every machine again, before they can do their actual tasks (like in the old cmd.exe days).

Originally created by @lauxjpn on GitHub (May 1, 2020). As far as I can see, the `profiles.json` file is currently located in the `AppData\Local` folder. Wouldn't that mean, that I would need to make the same custom changes to the file on every machine I log into with the same user account, only to get the same terminal experience? Also, there should be a simple (or at least documented) was to use the same custom `profiles.json` file for all active directory accounts (either forced or as the default but modifiable). These both are much needed features for every administrator out there, so they don't have to tinker with the settings on every machine again, before they can do their actual tasks (like in the old `cmd.exe` days).
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:14:14 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7850