Changes for page Konfigurationsprofile
Last modified by Sabrina V. on 2025/03/11 06:50
From version 2.1
edited by Sabrina V.
on 2024/10/23 06:27
on 2024/10/23 06:27
Change comment:
There is no comment for this version
To version 5.1
edited by Sabrina V.
on 2025/03/11 06:43
on 2025/03/11 06:43
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -24,11 +24,9 @@ 24 24 25 25 == Assigning Configuration Profiles to Clients == 26 26 27 -Sie können über zwei Wege Ihren Clients ein Konfigurationsprofil zuweisen: 28 - 29 29 There are two ways of assigning Configuration Profiles to your Clients: 30 30 31 -**1.By explicit assignment** 29 +**~1. By explicit assignment** 32 32 This assignement is done via a query. To do this, select a required Client, navigate to BitLocker Management in the Query action bar, and click //Assign Configuration Profile//. This will open a dialogue box where you can select the required configuration profile. Within the default configuration, you can overwrite the configuration assignment with a container. If this is not desired you can uncheck this option. Continue the association by clicking on //Execute//. You can view the status of the mapping in the Job Monitor. 33 33 34 34 **2. Via an automatic container association** ... ... @@ -41,7 +41,7 @@ 41 41 If you want to remove the assignment or make changes to the Configuration Profile, you can also do this from the ribbon bar. 42 42 43 43 {{aagon.infobox}} 44 -If a Managed Client is skipped when manually assigning the profile, the minimum requirement will not be met. Please note the 42 +If a Managed Client is skipped when manually assigning the profile, the minimum requirement will not be met. Please note the[[ requirements>>doc:ACMP.67.ACMP-Solutions.Security.BitLocker Management.WebHome||anchor="HSystemrequirementsforBitLocker"]] for BitLocker management on the clients. 45 45 {{/aagon.infobox}} 46 46 47 47 == **Container behaviour** ==