BobHot's Posts

Sorry for the poor initial formatting.
Hi, I'm playing around with a global ruleset of restrictions, but I need the option to make simple granular exceptions from that. So for example just an exception for one restriction, not for the co... See more...
Hi, I'm playing around with a global ruleset of restrictions, but I need the option to make simple granular exceptions from that. So for example just an exception for one restriction, not for the complete ruleset. The problem here, it's not possible to do it like in group policies in Windows, where the policy that is the closest to the object wins. In WS1 the most restrictive rule wins. That means, that a global rule cannot be overwritten by a more specific one. Let's assume you have the following organization groups and a few settings X,Y,Z. All settings are from the restriction payload (e.g. X:disable bluetooth, Y:disable camera, Z:disable wlan).     Root ├─ AAA ├─ BBB ├─ CCC ├─ DDD ├─ ... ├─ ZZZ     I want the settings X,Y,Z everywhere active, except X not in BBB and Y not in CCC (please keep in mind, that this is only a minimized example). Like this:     OG <- Restrictions ---------------------------------------------------------------- Root <- default: disable bluetooth, disable camera, disable wlan ├─ AAA <- default ├─ BBB <- default, but allow bluetooth ├─ CCC <- default, but allow camera ├─ DDD <- default ├─ ... ├─ ZZZ <- default     Here my idea to realize that: Create a smartgroup 'SG Enable Bluetooth' and assign it to OG 'BBB' Create a smartgroup 'SG Enable Camera' and assign it to OG 'CCC' Create 3 policies with the same restriction payload and link it all to the Root OG 'Policy Restriction default'       <- set all global default restrictions, e.g. 'disable wlan' and others, but bluetooth and camera are allowed 'Policy Restriction Bluetooth'  <- set only the setting 'disable bluetooth' 'Policy Restriction Camera'     <- set only the setting 'disable camera' Set 'SG Enable Bluetooth' as exception in 'Policy Restriction Bluetooth' Set 'SG Enable Camera' as exception in 'Policy Restriction Camera' The smartgroup to enable something (e.g. 'SG Enable Camera') could also make use of a TAG instead of an organisation group, so that only the devices with a specific TAG would be affected (e.g. TAG: Camera). Just add the TAG an the device can use the camera. So, what do you think about that idea? Did I miss something? How would you do that? I can't imagine that nobody before had such a situation. Greetings Bob
Hi, I pushed a profile to automatically install system updates on Android 10 devices. WS1 says that everything is fine and the profile is successful installed. But in the 'Intelligent Hub > Pr... See more...
Hi, I pushed a profile to automatically install system updates on Android 10 devices. WS1 says that everything is fine and the profile is successful installed. But in the 'Intelligent Hub > Profiles' on the device itself the profile says 'Installation error' (I do not use English language on the device, so the message may differ a little bit). Does anyone ever seen this behavior? BH :smileycool:
Hi bspencer505​, I have experienced with Android 10 that the passcode reset works not 100% stable (as many other things too in WS1). Sometime it works, sometimes not. I tried the reset on ... See more...
Hi bspencer505​, I have experienced with Android 10 that the passcode reset works not 100% stable (as many other things too in WS1). Sometime it works, sometimes not. I tried the reset on two equal test devices at almost the same moment. On one device the passcode was reset in seconds. On the other device i needs a few hours. So maybe you just repeat and wait? I'm not sure if synchronizing the device has an effect. Maybe instead of use 'Clear Passcode > Device', you could try 'Management > Change Device Passcode'. Good luck BH :smileycool:
Hi bakerb​, thank you for your answer. The problem exists much longer than 12h and Sync Attributes had no effect. But while I was checking your idea, I found rather incidentally a solution tha... See more...
Hi bakerb​, thank you for your answer. The problem exists much longer than 12h and Sync Attributes had no effect. But while I was checking your idea, I found rather incidentally a solution that solves it all. The group I want to add from AD into WS1 has to be an universal group. A global group doesn't work. Is that a bug or a feature? I've never read about it, but I tested a universal group and it works fine. All users are automatically added into WS1, just by adding the AD group. Exactly what I was looking for. BH :smileycool:
Hi dragan, I'm new in WS1 too, but as far as I know, the decision for "Work Managed Device" or "COPE" is not reversible. If a device is COPE once, it is always COPE until an enterprise wipe. ... See more...
Hi dragan, I'm new in WS1 too, but as far as I know, the decision for "Work Managed Device" or "COPE" is not reversible. If a device is COPE once, it is always COPE until an enterprise wipe. So I decided to create an extra organization group just for enrollment with two sub og's they differ only in this one setting. One for WMD and one for COPE. I enroll a new device into one of these og's and after that I put the device in the final group with profiles, apps..etc. Cheers BobHot
Hi, I have a problem with user groups and active directory. There is a working connection between WS1 UEM and the active directory (AD). I can add AD users and AD groups to WS1. Fine. The p... See more...
Hi, I have a problem with user groups and active directory. There is a working connection between WS1 UEM and the active directory (AD). I can add AD users and AD groups to WS1. Fine. The problem is, my test AD group has 5 AD users, but in WS1 it says 0 users. For my understanding when adding a user group from AD, the users in this group should be added to WS1 automatically. In WS1 the user group settings are: Auto Sync:  Enabled Auto Merge: Enabled Add Group Members Automatically:    Enabled I tried to sync or to add the missing users. But nothing happens. WS1 says 0 user in this group. What's wrong here? BH