mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
remove assigned access
This commit is contained in:
parent
cf273064fa
commit
0d6f002e6f
@ -158,7 +158,7 @@ Example:
|
|||||||
```
|
```
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
> If you pins elements to the Start menu with Microsoft Edge secondary tiles, ensure to include the following apps in the allowed apps list:
|
> If you pins elements to the Start menu with Microsoft Edge secondary tiles, include the following apps in the allowed apps list:
|
||||||
>
|
>
|
||||||
> - `<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge_proxy.exe" />`
|
> - `<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge_proxy.exe" />`
|
||||||
> - `<App AppUserModelId="Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!App"/>`
|
> - `<App AppUserModelId="Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!App"/>`
|
||||||
|
@ -23,7 +23,7 @@ To learn how to configure the Assigned Access XML file, see [Create an Assigned
|
|||||||
|
|
||||||
You can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
|
You can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
|
||||||
|
|
||||||
- **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
|
- **Setting:** `./Vendor/MSFT/AssignedAccess/Configuration`
|
||||||
- **Value:** content of the XML configuration file
|
- **Value:** content of the XML configuration file
|
||||||
|
|
||||||
Assign the policy to a group that contains as members the devices that you want to configure.
|
Assign the policy to a group that contains as members the devices that you want to configure.
|
||||||
|
Binary file not shown.
Before Width: | Height: | Size: 763 KiB After Width: | Height: | Size: 270 KiB |
@ -35,9 +35,19 @@ The Breakout Sequence of <kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>Del</kbd> is th
|
|||||||
|
|
||||||
Deleting the Assigned Access configuration removes the policy settings associated with the users, but it can't revert all the changes. For example, in a multi-app kiosk scenario the Start menu configuration is maintained.
|
Deleting the Assigned Access configuration removes the policy settings associated with the users, but it can't revert all the changes. For example, in a multi-app kiosk scenario the Start menu configuration is maintained.
|
||||||
|
|
||||||
Here's a PowerShell example to remove the configuration:
|
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||||
|
|
||||||
```powershell
|
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||||
|
|
||||||
|
To remove the Assigned Access configuration, delete the policy that contains the configuration.
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
||||||
|
|
||||||
|
To remove the Assigned Access configuration, uninstall the provisioning package that contains the configuration.
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
|
||||||
|
|
||||||
|
```PowerShell
|
||||||
$namespaceName="root\cimv2\mdm\dmmap"
|
$namespaceName="root\cimv2\mdm\dmmap"
|
||||||
$className="MDM_AssignedAccess"
|
$className="MDM_AssignedAccess"
|
||||||
$obj = Get-CimInstance -Namespace $namespaceName -ClassName $className
|
$obj = Get-CimInstance -Namespace $namespaceName -ClassName $className
|
||||||
@ -45,7 +55,11 @@ $obj.Configuration = $null
|
|||||||
Set-CimInstance -CimInstance $obj
|
Set-CimInstance -CimInstance $obj
|
||||||
```
|
```
|
||||||
|
|
||||||
Reboot the device to apply the changes.
|
#### [:::image type="icon" source="../images/icons/settings-app.svg"::: **Settings**](#tab/settings)
|
||||||
|
|
||||||
|
This option isn't available using Settings.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
## Next steps
|
## Next steps
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user