deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-27 08:13:39 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Started adding tables by request

Browse Source
This commit is contained in:
Heidi Lohr
2018-09-12 16:51:42 -07:00
parent 04431aa86a
commit f552239a3f
1 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
windows/client-management/mdm/assignedaccess-csp.md
View File

@ -102,9 +102,27 @@ Note that status codes available in the Status payload correspond to a specific
| 2 | KioskModeAppNotFound | | 2 | KioskModeAppNotFound |
| 3 | KioskModeAppActivationFailure | | 3 | KioskModeAppActivationFailure |
Additionally, the status payload includes a profileId, which can be used by the MDM server to correlate which kiosk app caused the error. Additionally, the status payload includes a profileId, which can be used by the MDM server to correlate which kiosk app caused the error.
In Windows 10, version 1810, Assigned Access runtime status supports monitoring single-app kiosk and multi-app modes. Here are the possible status codes.
|Status|Description|
|---|---|
|Running|The AssignedAccess account (kiosk or multi-app) is running normally.|
|AppNotFound|The kiosk app isn't deployed to the machine.|
|ActivationFailed|The AssignedAccess account (kiosk or multi-app) failed to sign in.|
|AppNoResponse|The kiosk app launched successfully but is now unresponsive.|
Note that status codes available in the Status payload correspond to a specific AssignedAccessRuntimeStatus.
|Status code|AssignedAccessRuntimeStatus|
|---|---|
|1|Running|
|2|AppNotFound|
|3|ActivationFailed|
|4|AppNoResponse|
Supported operation is Get. Supported operation is Get.
<a href="" id="assignedaccess-shelllauncher"></a>**./Device/Vendor/MSFT/AssignedAccess/ShellLauncher** <a href="" id="assignedaccess-shelllauncher"></a>**./Device/Vendor/MSFT/AssignedAccess/ShellLauncher**