![]() ![]() You'll notice that the Business SKU is missing from that list.that's because it's NOT identified in the DDF. Here's a snip of one of the applicability tables: For example, see which is already updated to the new format. This process also involves automating the CSP applicability based on the details in the DDF. We'll migrate some of the relevant information from the existing content, but generally rely on the DDF/ADMX info as the source of truth. We are completely refactoring the CSP documentation, automating the creation of the reference content based on information directly from the DDF and ADMX files. GitHub Login: Microsoft Alias: dansimp.Content Source: windows/client-management/mdm/configuration-service-provider-reference.md.Content: Configuration service provider reference - Windows Client Management.It is required for ➟ GitHub issue linking. It would be good to get some clarity on this in the documentation. My (possibly flawed) thinking would be that because Windows 10 Business is just the edition that Windows 10 Pro changes to when enrolled into Microsoft 365, you would expect the same AppLocker functionality that is available on Pro edition to be available if the install is converted to Business edition. Nowhere within the article is there any mention of any editions being excluded. In the same table it also makes clear that all AppLocker rule types can be configured and enforced on "Windows 10". "You can use the AppLocker CSP to configure AppLocker policies on any edition of Windows 10 supported by Mobile Device Management (MDM)." However, the AppLocker documentation says the following: In the matrix showing which CSPs are supported on which Windows 10 editions, the AppLocker CSP is listed as being supported on all editions of Windows 10 other than Windows 10 Business. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |