KB – Working commands if no user is logged on
The scenario is not quite “modern” but from time to time we have devices where no user is logged on and you still want to manage it.
The list is based on HUB 21.02 and also tested on 21.05 – later versions might change the behaviour.
First of all: only commands that are assigned to the device and not to the user are covered. User commands are only process when the enrollment user is logged on.
|Name||Installed when no user is logged on||Comment|
|Password||Yes||Only if “Use Protection Agent” is disabled|
|Credentials||Yes||Also Certificate reporting works|
|Defender Exploit Guard||Yes|
|SCEP||Yes||Also Certificate reporting works|
|Unified Write Filter||Yes|
Custom Profiles are working as long as the target is set to OMA DM Client and not to Workspace ONE Intelligent HUB.
All profiles that are targeted to the HUB, are not working if no user is logged on.
Baselines are only applied if a user is logged on.
Also Baseline compliance will only be reported if a user is logged on.
Application installation and also the installation status reporting works if no user is logged on.
|Query type||Works when no user is logged on|
|Available OS Updates||Yes|
|Hub Check In||No|
|Certificate List Sample||No|
|App List Sample – HUB||No|
|App List Sample – OMA-DM||No|
|Action name||Works when no user is logged on|
|Request Device Log||Yes|
Product Provisioning only works when a user is logged on.
Scripts only work when a user is logged on.
Since certificate deployment works, also the revocation and renewal works if no user is logged on.
Currently Remote Assist does not work if no user is logged on.
Right now everything that is targeted to the Intelligent HUB is not working when no user is logged on – while everything that is targeted to the native OMA-DM client is working regardless of the user status.