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.
I have a weird issue. I cannot uninstall mobiecontrol. It seems to be stuck in a weird loop. Mobicontrol is installed through the afw#mobicontrol option. But on this handheld it didn't remove all the excess apps like it should have. Mobicontrol works as it should otherwise on this handheld. But I cannot remove it at all. If I factory reset the handheld it tells me mobicontrol is still installed and then rebuilds the profile up to the home screen with all of the apps it shouldn't have still there. I've tried going through as much SOTI documentation I can find on how to uninstall mobicontrol and it all seems to stem from turning off the device admin under settings/security/device admin. I do not have the option to turn that off. It's grayed out for me. I've tried this in admin mode and user mode. I've tried various forms of wiping the handheld reset /w and /e. At first I thought /e was going to work because it acted like it was completely wiped and actually brought up the google login screen to where I could type afw#mobicontrol. But when I did this it appeared that the app was already installed and continued to do the same thing. **Edit** This is a Zebra TC20 my mistake I thought I added this.
several of our employees have figured out a loophole in our Kiosk. We are trying to have them use Soti Surf as their browser. The loophole is when they go into adobe and select print - they can click on all services and it will open up a google chrome browser window. we have blacklisted com.android.chrome and have also tried the disable script. So far we have not found a solution. i found this solution https://discussions.soti.net/thread/how-to-fully-blacklist-a-browser/ i have tried the manualblacklist and no avail. our devices are ATT and Verizon Tab A's Model: SMT387 android 9 enrolled with android + can anyone provide further advice? if needed i will open a ticket.
Hi, We are encountering enrollment issues as of today. Environment is AEDO, with managed play store, Zebra TC56. Worked fine for almost 2 years. The NFC part of the process is working fine, we get an error when the MC Agent tries to enroll to the server, it fails. Server version : 13.4.0.5203 The DSE Log says something like that : Corresponding AfW device was not found while processing the device xxxxxxx with afw id yyyy. Anybody already experienced that kind of issue ? I'm mainly trying to find out where I should focus my investigations. Seems like an issue matching a device on the google part, with a deviceid on mobicontrol Thanks
Hello! I'm struggling with the installation of APKs into the work container of Android Enterprise (work managed profile on Samsung S9, Android 9). Installation via package in a profile doesn't work as well as the installation via Application Catalog (Enterprise Application). How can we install APKs into the work container? The log shows following errors: 8:47:32ErrorProfile "Test_AE - Pre-installed Apps" version 4 failed to install, because all of its payloads cannot be installed.8:47:32ErrorPackage "XXXXXXXXX" version 1.0 failed to install. File IO error on device. Check Storage/Permissions.8:47:32ErrorError message received from device (Installierung der Anwendung XXXXXXXX von Paket XXXXXXX.pcg Fehlgeschlagen)
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
Hello Everyone, I am attempting to utilize scripts to alter screentimeout and change the screenlock to none. I have tried the below: writeprivateprofstring –sys screen_off_timeout 600000 writesecuresetting -sys Screen_lock_type_Nonewrite_setting -sys Screen_lock_type_Nonewrite_setting -Screen_lock_type_None I am working on Tab A, OS 9, enrolled via Enterprise. Any help would be greatly appreciated! Thank you! Monique
I'm running 14.4 and using a AE device in DO mode, can a script turn on NFC?
any one know any licensed screen recording solution for andriod devices . which we can use in our enterprise
Is there a better way to manage folders and files other than the File Manager interface? As it stands now, you have to manually (re)create folders one-by-one as well as uploading files one-by-one. Maybe a better way such as ftp ??... Any thoughts or ideas or options here?
when choosing device id... What does it really mean when set to Server Generated? Who's server...my deployment server? is it incremental ? Can anyone elaborate with an example or two? Thanks.
Hello all, it's always me :) I hope you're well. We work with zebra tc75x under android 6 The server is on version v 13.3.0.3454 Actually, i'm testing and writing a procedure for to upgrade our parc of device to android 7. the step is -> place zip file and send a mxconfig script (stagenow) If I start an upgrade to android 7 has no production profile all is ok (hour / date / language / enroll MDM / APN / Wifi / ….) Now, I have installed on a device under android 6 all our production profile and also the zebra keyboard. I start the upgrade but after reboot I have two problems and I'm still block .. a) after upgrade, the hour it's not correct -> there is 20 minutes left ! Why and How i can make hours correct ? I've try sync file / disconnect ,connect again client / reboot device .. but nothing work we don't have a server time; the time is managed by soti when I enrolled a new device a see in the log -> time sync configured b) after upgrade, the zebra keyboard disapears ! I can't understand because our program is still there (apk) / lock down / soti surf and a lots of thing.. Ok i can install again zebra keyboard but I would like perhpas to find a better solution. Someone has perhpas an idea. thanks for all
Hi, We've been using MobiControl since November 1st, 2017, under a perpetual license. Since then, we've increased our device count and paid the yearly maintenance & support fees so we can receive the latest MobiControl updates. Less than two (2) weeks ago, my boss made the decision to postpone our yearly MobiControl maintenance renewal to December 2019, to coincide with our upcoming purchase and delivery of new trucks & appropriate tablets. Since we're on a perpetual licence, MobiControl will still work as-is, right? Wrong. As of November 1st, 2019, I am unable to enroll devices even though my available device count says otherwise. I am pretty sure it's because we haven't renewed the yearly maintenance plan. I say this because the MobiControl Deployment Server logs are now filled with the following messages whenever I try to enroll a new device: Destination path:LicenseObject.LicenseType.LicenseTypeSource value:Soti.MobiControl.Core.Licensing.Com.LicenseObjectAdapter ---> System.NullReferenceException: Object reference not set to an instance of an object. at Soti.MobiControl.Core.Licensing.Com.LicenseObjectAdapter.get_LicenseType() at lambda_method(Closure , Object ) at AutoMapper.Impl.MemberGetter.Resolve(ResolutionResult source) at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func) at AutoMapper.Mappers.TypeMapObjectMapperRegistry.PropertyMapMappingStrategy.MapPropertyValue(ResolutionContext context, IMappingEngineRunner mapper, Object mappedObject, PropertyMap propertyMap) --- End of inner exception stack trace --- at AutoMapper.Mappers.TypeMapObjectMapperRegistry.PropertyMapMappingStrategy.MapPropertyValue(ResolutionContext context, IMappingEngineRunner mapper, Object mappedObject, PropertyMap propertyMap) at AutoMapper.Mappers.TypeMapObjectMapperRegistry.PropertyMapMappingStrategy.Map(ResolutionContext context, IMappingEngineRunner mapper) at AutoMapper.Mappers.TypeMapMapper.Map(ResolutionContext context, IMappingEngineRunner mapper) at AutoMapper.MappingEngine.AutoMapper.IMappingEngineRunner.Map(ResolutionContext context) at AutoMapper.MappingEngine.Map[TDestination](Object source, Action`1 opts) at Soti.MobiControl.DeploymentServerExtensions.Facade.Implementation.AdapterFacadeService`1.Convert[TDestination](Object source) at Soti.MobiControl.DeploymentServerExtensions.Facade.Implementation.Licensing.LicenseService.GetLicense(LicenseObjectRequest licenseObjectRequest) at MobiControlLicensing.LicensingLogic.GetLicense(LicensingLogic* , shared_ptr<MobiControlLicensing::LicenseObject const >* , LicenseRequest* licenseRequest)2019-11-06 16:53:54,794 (0x00001afc) [ERROR] [Elm::CElmLicenseMgr::GetElmLicenseKey] Error getting the license object from DSE.2019-11-06 16:53:54,810 (0x00001afc) [ERROR] Failed to verify MandatoryApplication version: Device(3585100_DEVICE_IMEI), Expected(com.google.android.tts), Got(android7.1.1)2019-11-06 16:53:54,810 (0x00001afc) [ERROR] Failed to verify MandatoryApplication version: Device(3585100_DEVICE_IMEI), Expected(net.soti.mobicontrol.androidwork), Got(android7.1.1)2019-11-06 16:53:55,372 (0x00001afc) [INFO ] [ 75] Comm.Client.34586 [3585100_DEVICE_IMEI]: ProcessJobs: Device 3585100_DEVICE_IMEI check-in finished in 703 ms.2019-11-06 16:53:56,325 (0x00002448) [INFO ] <190> Queue stats: Length: 0, Locks: 2 in 0 ms, Enqueue: 1 in 0 ms, TryAdd: 1 in 0 ms, TryTake: 1 in 0 ms, Processed 1 in 1568 ms (average 1568 ms)2019-11-06 16:53:56,325 (0x00002448) [INFO ] <190> Queue stats: Threads: 5, Working: 0, Waiting: 0, FileBlockMsg: 0, Jobs: 02019-11-06 16:53:58,997 (0x00000d4c) [INFO ] [ 19] PulseChecker enter: Send: False, Check: True, Memory: 133715904, Threads: 32767/999/82, Queue: 0, Workers: 52019-11-06 16:53:58,997 (0x00000d4c) [INFO ] [ 19] PulseChecker exit: Total: 823, Connected: 131, Busy: 0, Dropped: 0, Retried: 0, Threads: 32767/999/82, finished in 0.000 ms2019-11-06 16:54:12,375 (0x000021a4) [INFO ] < 89> Comm.Client.34587: Accepted a new connection from [::ffff:192.168.30.59]:57959.2019-11-06 16:54:12,734 (0x000021dc) [INFO ] <103> Comm.Client.34587: Client [::ffff:192.168.30.59]:57959 authenticated. Cipher: Aes256/2562019-11-06 16:54:12,766 (0x000021a4) [INFO ] < 89> Comm.Client.34588: Accepted a new connection from [::ffff:67.69.x.x]:60477.2019-11-06 16:54:13,750 (0x000024a4) [INFO ] <208> Comm.Client.34588: Client [::ffff:67.69.x.x]:60477 authenticated. Cipher: Aes256/2562019-11-06 16:54:15,312 (0x00000930) [INFO ] [187] Comm.Client.34587: AutoConfigureDevice: Device 48f0******f2509 connected. Total 31 ms, query 15 ms, DSE 16 ms, update 0 ms2019-11-06 16:54:15,891 (0x00000930) [WARN ] Check for ELM License2019-11-06 16:54:15,891 (0x00000930) [ERROR] [MobiControlLicensing::LicensingLogic::GetLicense] AutoMapper.AutoMapperMappingException: For those wanting the details: we're enrolling Samsung T377Ws as Android Enterprise devices using afw#mobicontrol and scanning a Stage barcode to complete the deployment. Server version is 14.4.4. The device successfully joins our on-premises deployment server, but enrollment comes to a grinding halt when the agent attempts to install the required Profiles: Furthermore, the following functions/screens in MobiControl no longer work: Locations (through a device's property pages) regularly time out. Android Agent & Plugins management no longer works (screenshot below). And other stuff I can't recall right now. I thought that enrolling through the 8-character "Enrollment ID" might be the issue (I realize it's a provided service by SOTI) so I attempted to enroll another device via the server's FQDN without success. I suspect the Samsung device plugin isn't getting installed and/or activated as I am also unable to Remote Control the newly enrolled tablets. Honestly, I'm pretty damn annoyed right now as our MobiControl instance is crippled and does not function as intended. We have fully paid for a solution under the guise that we can fallback to our current version and continue to use the product without a maintenance plan, yet I am unable to utilize the remaining device licenses that are available to us. Until our maintenance renewal in December 2019, we still plan to remove & enroll replacement devices as failures do occur but can't given the current limitations at play. I'm really hoping I'm wrong and this is another bug, but it's a pretty crappy one to say the least.
Since upgrading to MobiControl version 14.1 (agent v13.7.3.1045) every line break or enter key leaves a | in the message. Does anyone know a way around this?
Is there any way to force a check-in on the device side?
Hello, just wanted to ask if anyone has yet tested Version 15.0 and if there are known bugs. I am going to start testing myself next week, maybe we can collect bugs etc. in this thread? Have a nice evening.
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.
