Phil_Helmling's Posts

Hi @Suzuki23 , I think it samples the UBR of the device, but could you please do me a favour and run both of these sensors (locally or manually is fine) on an affected device and that should show which value is being sampled. https://github.com/vmware-samples/euc-samples/blob/master/UEM-Samples/Sensors/Windows/os_build_number.ps1 https://github.com/vmware-samples/euc-samples/blob/master/UEM-Samples/Sensors/Windows/os_build_ubr.ps1  

Hey Daniel, if you are using a trial, then the best course of action is to speak with your partner or your VMware SE to get them to log a support call on your behalf. VMware have EUC Specialist SEs that can also assist. 

Its configured at the tenant level. Goto Groups & Settings > All Settings > Devices & Users > Android > Android EMM Registration (see screenshot). default is Work Managed meaning it should be showing. If not, please log a support call and they should be able to troubleshoot.

There looks to be two APIs you can use: https://host/api/system/users/enrolleddevices/search which returns { "EnrolledDeviceInfoList": [ { "DeviceID": 1, "SerialNumber": "RZ1G124JZ6W", "AssetNumber": "ea856771ba6277bfca16528a79c5ce1f", "FriendlyName": "TestUser's iPhone", "UserName": "TestUser", "EnrolledDate": "04/24/2017", "RegistrationDate": "04/24/2017", "LastSeen": "04/24/2017", "Platform": "Apple", "OrganizationGroup": "TestOg", "CustomAttributes": [ { "Name": "identity.deviceModel", "Value": "TC25", "Source": "Device", "Application": "com.airwatch.androidagent.identity.xml" } ] } ] }  https://host/api/system/users/registereddevices/search { "RegisteredDeviceInfoList": [ { "OrganizationGroup": "TestOg", "Username": "TestUser", "FriendlyName": "Testuser's iPhone", "AssetNumber": "ea856771ba6277bfca16528a79c5ce1f", "UDID": "9bf5ae7cf74efe385bbe3b18261fd21c", "RegistrationDate": "04/24/2017", "SerialNumber": "RZ1G124JZ6W", "Platform": "Apple", "CustomAttributes": [ { "Name": "identity.deviceModel", "Value": "TC25", "Source": "Device", "Application": "com.airwatch.androidagent.identity.xml" } ] } ] } if neither of these return the correct details, please confirm that the device was registered by DEP into UEM. I think you can see the devices listed in the Devices > Lifecycle > Enrollment Status page. If they are showing then please log a support ticket so that we can get this escalated and assigned to the correct engineer.

which ownership mode did you enrol the device into? See this page for the commands available for each mode - https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/Android_Platform/GUID-AndroidManagementManageAndroid.html  

only Active Directory users are silent enrolled (no HUB popup). Like Emad said, we match the local logged on user account to a user in the directory that is configured in UEM, if no match then we popup and ask for creds.

Ok so if they are domain joined and have line of sight to a DC when logging in, then Hub should not popup as Hub matches the user in AD to the logged on user. There are potential complications on the staging user and how auth is setup, such as whether you have WS1 Access in the auth flow.  On staging user, find the user in Accounts > Users > Advanced and look at the staging config (screen capture of one of mine attached).

try this example and duplicate line 41 to create the second shortcut. But you must have the shortcuts created already https://github.com/helmlingp/WS1UEM_CustomKiosk/blob/main/ExampleKioskProfile_Chrome_AutoLaunch.xml  

@mnanev you have pinged or RDP from ACC to DC to confirm network connectivity? Have you nslookup the DC by name to confirm resolution back to IP? You can also enable debug logging as per info found in https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/WS1_Logging.pdf in the VMware AirWatch Cloud Connector (ACC) section.

@eg2428 the answer depends on if the machines are joined or not joined to a domain and how the staging is configured and also how the devices are configured for public use (assuming shared use where users are not logging in). If you just want to present some apps, then I would enrol the devices to a user not staging user, that is dedicated for the task. We sometimes refer to this user as a service account. The service account user would have the apps and profiles required to support its use and I would also use the kiosk profile to force control over the desktop/shell. Have a look here for examples of kiosk profiles - https://github.com/helmlingp/WS1UEM_CustomKiosk Phil

@keijd_04 this happens sometimes after an upgrade or where your environment is not enabled for Baselines. I would suggest you log a support call if this is a production environment or ask your SE for help if this is a POC. They will need to check the feature flags are enabled for Baselines. Regards, Phil

Hey @rodderix , Enterprise Reset doesn't re-enrol the device - https://kb.vmware.com/s/article/50103263 if you want to reset the device and have it come back as if freshly built (including auto-enrol), then look at https://github.com/helmlingp/apps_DeviceWipewProvisioning Regards, Phil

Yup, I have customers doing this very successfully. You can either sideload (add internal app) or add apps to your private Google Playstore - https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/2302/Application_Management_for_Android/GUID-AWT-INTERNAL-APPS.html

Shaunchan you should contact your local VMware partner or rep and ask to be put on the "do not block" support list. You will likely need to prove you are renewing and therefore entitled to the upgade, then upgrade.