microsoft / microsoft/scout-resources
Microsoft Scout ADMX policy registry properties not in "Microsoft" key
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 30
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Microsoft Scout's ADMX file - https://github.com/microsoft/scout-resources/blob/main/admins/microsoft-scout.admx - shows that the Scout policies defined by the ADMX files define their corresponding registry keys in location HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Scout.
Modifications to the AllowScoutFrontierAccess value on a test machine show that the Scout application is indeed looking for policies in SOFTWARE\Policies\Scout.
I would expect these values to instead be located in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Scout, where the "Scout" key (name of product) exists under a "Microsoft" key (name of vendor) like numerous other Microsoft (and other software vendor) products, examples:
Microsoft Edge Policies - "These policy settings are located at this registry path: HKLM\SOFTWARE\Policies\Microsoft\Edge."
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with admins/microsoft-scout.admx, linked in the issue, and inspect the registry paths for the Scout policies, including AllowScoutFrontierAccess. Done means the policy registry properties use HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Scout consistently with the requested vendor and product keys.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100