No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hello, is there an possibility to force the download and installation of OTA via Soti 2024.1.2.1046. With force i mean The OTA process on the device start immediately with download and installation and not "12h" later.. only Zebra Enterprise devices. Kind regards Günter
Hi all, I have a problem with an existing Android enterprise Wi-Fi profile which I created a year or so ago, it pushes the hidden SSID network with the RADIUS certificate (which expires 2027) to all "manager" devices across our entire company. An authentication profile is deployed with some other bits and pieces in another profile as that is a requirement for the certificate. The new SSID has only been available at our head office over the last year, and our 8 other offices were going to get the enterprise SSID at a later date. For the past year this profile has been working fine at our head office and hasn't been changed in that time either. The enterprise SSID configuration has been copied across our other 8 sites over the last month via Aruba Central and I have seen most enrolled devices connect to it automatically as they already had the profile in place from when it was implemented a year ago to all manager devices. This should allow all manager devices to join even if they are at a different location to normal. And that should be the end of it! I started noticing a few devices not joining the hidden SSID automatically when other devices in the same location were joining fine... and I thought perhaps the managers had their Wi-Fi switched off on their device, so I pushed a SOTI script to enable the Wi-Fi radio... no luck. I also found that some devices had automatically made the users aware of an open "Guest" SSID in the same location we have available, and they tried to join that instead but it's a captive portal which requires a logon so does nothing, it in fact breaks their internet connection. "Forgetting" the Guest SSID forced some devices onto the correct SSID. But some were still not joining the required SSID. In an attempt to force all devices off of the Guest SSID in case that was the problem, I created a new Wi-Fi profile for the Guest SSID and applied it to my device (which was already happily on the correct hidden enterprise Wi-Fi) and I then revoked the profile in an attempt to make it "forget" the Guest Wi-Fi. This worked as expected but for some reason forgot the enterprise SSID that I want manager devices to be on at the same time. Strange I thought, so I revoked that enterprise Wi-Fi profile and reinstalled again. SOTI thinks it's applied, the device thinks it's applied (within the SOTI MobiControl profile list), the device gets the certificate, but the SSID network does not join. I would expect to see it in the "known Wi-Fi" list, but nothing appears. I've removed it from the group, applied it again, restarted, forgotten all network settings and applied it, recreated a brand-new profile to apply the same SSID again, nothing. I cannot deploy this hidden enterprise SSID that hasn't changed or this Wi-Fi profile which also hasn't changed to this device that has happily been using it for the past year. I have the same issue with my colleague in the same office, we re-created the exact same steps, and he cannot join this Wi-Fi now either. I have checked 2/3 other users that I was struggling to see on the correct SSID and can confirm via SOTI remote control that they also do not know of this SSID. I enrolled a brand-new device and that picked up all of the configurations as expected, so it does work... but is just being selective! I spoke to SOTI support and asked them to restart our cloud instance or services as it seems like a niggle rather than a configuration error/issue. No luck. We were running MobiControl 15.6.0 and I requested they upgrade to the latest version 15.6.4 because our devices are running the latest MobiControl agent from the Google Play Store and I thought they may be some incompatibility mismatch where the agent has upgraded faster than the MobiControl instance. After the MobiControl upgrade, still no luck. I still have the case open with SOTI but I’m at a loss, I have literally no idea why it won't work for certain devices. No config changes have been made with MobiControl at all! It has been happily working at one site for a year and additional sites were seemingly working as I was adding them and now my device at head office is playing silly buggers, it just seems to be certain devices. Not a specific Android version or type of device, random! Any ideas welcome! If someone had the same issue and a fix, even better!
Hi all, So I am currently working on updating our Honeywell CK65's OS versions with zero touch for end users. My issue is that when the device updates you are required to put an Android Pin when the device turns back on. Is there a script to bypass the need of putting the pin in? Thank you
Good Morning, I have 5 devices stuck on the account activation pending and will not complete the enterprise enroll. We have enrolled over 150 devices using the same enrollment method and ID, however my most recent batch have not completed. Any advice or ideas here?
Hello, Since on devices enrolled as Android Enterprise, it has hardware encryption information and a value next to it. What does that value mean and what level of encryption does the device have?
Soti device licenses are expensive as we all know, and to limit the needed amount in our environment, we're tracking the "Agent Check-In time" and pulling devices from production that are not being used. However, an online device hooked on usb power that no one is using, will not be caught by monitoring the agent check-in time. Is there a way to track/monitor some custom data like, touch screen used X times, power button clicked X times, specific app openend X times the last X days? Or does anyone have a better idea? My environment:Android devices running Android Enterprise profiles.½ of my devices are used in warehouses meaning tracking the gps for activity wont give the data I need.Thanks in advance.
Hi all, I'm currently using Android Enterprise - Work Managed devices, with Managed Google Play Account... Mobicontrol version 15.3.2 I have a selection of Add device rules set up and all have the Permissions set on the Rule like below: However at enrolment of the device, I'm experiencing a mix of results and not sure why. For example, once the device is staged as AFW - its on the enrolment screen waiting for a code. We use Mobicontrol Stage and scan barcodes created from the Enrolment ID. This then prompts for username and password (we use ldap authentication) and then it prompts for the Password Policy we set and moves onto the kiosk/lockdown. On some devices, this proceeds and there are no further pending actions. All policies, apps, etc download and the device is enrolled and compliant. However on another device, same model, same staging but perhaps a different Rule - with the same Permissions set - we get prompted in Pending actions and have to manually accept each one and toggle Mobicontrol. I have gone over the Rules and aside from the target and ldap groups these are almost carbon copies. All have the tickboxes set but I'm confused if they mean it should prompt, or should auto grant these? Little baffled on why some do it but not all... Is there something at the profile level that has an effect, or maybe something in feature control that conflicts with this that I'm potentially missing? If anyone can help and offer the intended action it would be much appreciated as we may need to update documentation for user enrolment asap. Many thanks Leigh
Hi, A customer requires lockscreen authentication on Zebra TC56 by scanning a RFID-card. The Zebras are running Android 8.1 with StageNow and Soti Mobicontrol. How can I best solve this? I found the NfcMgr in Stagenow that allows me to enable "NFC on Lock Screen", but on the device itself after scanning the Stagenow barcode I get the following staging error: "NFC Enterprise Settings not supported". I'm using MX 9.0. Any ideas?
We have a number of Samsung A40 devcies all enrolled on soti as android enterprise - Work managed devcies all using outlook mail client for email. Hoever we are unable to sync phone mumbers from the users emal accounts. On a non enrolled device the user has a sync contacts option from within the contacts applicationa and this will pull over the required numbers. But on the soti enrolled devcies this option is missing? and I cant seem to find the option for allowing/disabling the functionality.
There have been many requests for AE device, to get this feature (watchsetting on) back. Will it come back or will there be something other to get the setting names?
I have an issue where we have implemented Enterprise on the XCOVER4s and via QR code enabled all the on board apps via enterprise. All good, However i wanted to use the content library as there are certain things that our remote workers need extra information on when they are in the field. It all deployed fine and the documents have been downloaded to the device but none of them will open even though we have the google PDF reader installed and set to default. You click the button and nothing happens. Unlock the device......go to the Mobicontrol app --->Content Library.......Open..........work fine Lock it back up..............docs wont open Any Ideas?
Which Mobicontrol Agent do I have to install on this device? ZEBRA VC8300 Those that I have installed have given me various errors, indicating that they were not compatible. (Zebra, Zebra Concierge, Zebra ET1 GB, Zebra MC36) Any suggestion ?. Thank you. --//--Que Agente Mobicontrol es el que tengo que instalar en este dispositivo? ZEBRA VC8300 Los que he instalado me han dado diversos errores, indicándome que no eran compatibles. (Zebra, Zebra Concierge, Zebra ET1 GB, Zebra MC36) Alguna sugeréncia?. Gracias.
I am having difficulty sending some scripts to my Android Enterprise device - Samsung A50, Android 9. Our platform is version 15.0.1.1181 and the agent version is 14.1.6.1018. The scenario is: Firstly I noticed that after sending the script unlock, the logs need to update to state “Custom log (New authentication password applied)” before sending the kill_application and/or start script. After I did this I noticed that my test device successfully completed the scripts correctly each time – however, I then started sending them to other devices and was finding they hadn’t worked. This then has led me to find another issue: I believe what is happening is – if the device is pressed or touched by the user once the script is sent – then the following scripts: kill_application com.commontime.infinity.jobmenuprod start com.commontime.infinity.jobmenuprod will work correctly. However, if the user does not touch the device at all once the script is sent (I have found 30-60 seconds or more) then the final script is not correctly ran. The device appears to run the start script once the user opens or touches the device, but if this does not happen then the script is not ran at all – almost as though the device forgets that that start script needs to be ran. I have also tried sending it at three separate scripts – firstly sending the script unlock, and waiting for the logs to update to state “Custom log (New authentication password applied)”, next sending the kill_application script and waiting for this to appear in the logs, and then finally sending the third script – start. Again, if I press or enter the device manually as soon as the final script is sent, then the application does load once the screen is opened – yet, if I wait and enter or select the device after 30-60 seconds or more the application does not start – again as though the device has forgotten it needs to complete the third and final script. To confirm in all instance – the unlock and kill_application scripts are correctly working each time – it is just the start application that is causing an issue. Please could you provide any advice on how I can ensure the scripts each run - without user interference? Thank you
Using an Android OnePlus6 in SOTI i have somehow lost the work container on the device after enrolling it. It was working and available last week but after a period of testing un-enrolling and re-enrolling the work container is now longer on the device. Can anyone point me in the right direction with this i have spent time running through all the options for the device in SOTI i can't see where this might have happened. Android OS9 Android Status Provisioned / Enabled with Managed Google Play Accounts Management Type Work Managed Device
I am wondering if anyone has found a way to not only "ungray" the setting under Settings > Google > Security > Google Play Protect so that it can be toggled, but also actually toggle it OFF. SOTI provided two methods for doing the first item, to re-enable the setting so that it can be manually toggled. The methods are actually the same thing (a feature control) done two different ways: (1) Send script command: writesecureprofstring DeviceFeature DisableVerifyApps 1 apply featurecontrol (2) Create / assign a Feature Control that has "Disable Verify Apps Enforcement" checked. In my experience, these have the effect of re-enabling the toggle on the GPP setting, but leaving the setting toggled ON. It then has to manually be toggled OFF. I have certain apps that are mission-critical and mass-deployed, so touching each device to turn off GPP scanning for first deployment and subsequent app updates is absolutely not a feasible option. So far, SOTI Support has been unable to provide a means to programmatically toggle that option OFF. My other rather large challenge with this is, under AEDO, I've found that a Lockdown Screen profile has the side effect of toggling GPP back on, and graying it back out again so that it once again cannot be toggled off. SOTI says that this is the "expected behavior," to which I respond, WHY? Perhaps I am missing a pertinent concept here, but to my mind it is ridiculous to have a lockdown screen profile that also has the effect of locking GPP scanning on. These corporate users need app installations and app updates -- and those need to happen while the lockdown screen is in place. I've found that if the lockdown profile is already applied, the above two methods will have the effect of "ungraying" the GPP option so that it can manually be turned off. BUT if the lockdown profile ever is re-applied, or refreshes itself due to an editing change (such as perhaps adding an entry for whatever new app(s) are intended to be applied), then GPP is again turned on and the toggle is grayed out. This is very frustrating. I need a way to turn GPP scanning off, and KEEP it off, until I (and only I) tell it that it can turn back on again, Any advice would be appreciated. Thank you, Mark
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
