Skip to content

Conversation

@noahtalerman
Copy link
Member

  • Main goal is to clarify "Verifying" v. "Verified" for user-scoped Windows profiles
  • Also reorganize/update the heading to improve the guides flow
  • "user-scoped" and "device-scoped" get a hyphen

- Main goal is to clarify "Verifying" v. "Verified" for user-scoped Windows profiles
- Also reorganize/update the heading to improve the guides flow
- "user-scoped" and "device-scoped" get a hyphen
```

> Currently only device scoped SCEP profiles are supported for Windows devices.
> Currently only device-scoped SCEP profiles are supported for Windows devices.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We actually support user-scoped as well so this can be removed

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great catch! Thanks

#### Upgrading to 4.71.0
### Windows

To make a Windows configuration profiles user-scoped, replace `./Device` with `./User` in all `<LocURI>` elements.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may want to refer user to the Windows CSP documentation: https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-configuration-service-provider

Few CSPs actually indicate user support. Most are device only

#### Upgrading to 4.71.0
### Windows

1. Head to the [Windows configuration profiles (CSPs) documentation](https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-configuration-service-provider) to verify that all the settings in your Windows profile support the user scope. For example, the [SCEP setting](https://learn.microsoft.com/en-us/windows/client-management/mdm/clientcertificateinstall-csp#devicescep) supports both the device and user scope.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JordanMontgomery what do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great

Clarified the verification process for macOS and Windows profiles, including timing for status updates.

Hosts that applied all OS settings.

For macOS configuration profiles and device-scoped Windows profiles, Fleet verified by running an osquery query. It can take up to 1 hour ([configurable](https://fleetdm.com/docs/configuration/fleet-server-configuration#osquery-detail-update-interval)) for these profiles to move from "Verifying" to "Verified".
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JordanMontgomery is this "1 hour" part accurate?

cc @ddribeiro

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@noahtalerman that is correct. If the host is online it should happen within 1 hour

@noahtalerman noahtalerman removed the request for review from JordanMontgomery January 7, 2026 22:20
#### Windows

1. Head to the [Windows configuration profiles (CSPs) documentation](https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-configuration-service-provider) to verify that all the settings in your Windows profile support the user scope. For example, the [SCEP setting](https://learn.microsoft.com/en-us/windows/client-management/mdm/clientcertificateinstall-csp#devicescep) supports both the device and user scope.
2. To make a Windows configuration profiles user-scoped, replace `./Device` with `./User` in all `<LocURI>` elements.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@noahtalerman, should this be a Windows configuration profile or Windows configuration profiles? Also, user scoped is the correct grammar for this sentence. It only needs to be hyphenated when modifying a noun, e.g., "user-scoped certificates."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mike-j-thomas I went with your Windows configuration profile to be consistent with step 1.

Also, user scoped is the correct grammar for this sentence. It only needs to be hyphenated when modifying a noun, e.g., "user-scoped certificates."

Got it! Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants