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.
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.
Hi! We'd like to set up a migration scenario where our Samsung devices will migrate from Android+ to Android Enterprise (Work Profile). Has anybody done this so far? What is the best practise scenario with less user interaction? Thank you!
When we restart our Devices they connect to our apn flawlessly, but arent opening a data channel. The button "connect" in the soti agent triggers an event where a data stream to our apn is opened. The 3G/HSDPA-Icon is doing a little "connect" animation, thats how i know. As a workaround i created a profile with Out-Of-Contact policy to force the agent to connect to the ds via "connect -f" but this is unfortunately not triggering the same connect event as via the button in the agent, so the data channel to the apn / provider isnt opened. Has anyone of you experienced the same issue in the weh world or maybe has a script that does exactly what the button press "connect" in the agent does? Agent is 14.43 and Device is a CN51
In the Windows Classic Kiosk you have the option to disable the kiosk mode. Where is the option to reenable it again? For my understanding its kind off senseless to disable kioskmode while the profile with the payload "kiosk" is still showing as installed. Current solution for us is to disable kiosk when needed and then you need to reinstall the whole kiosk-profile whilst the terminal is restarting 2 times. Any Ideas / Solution?
Hello all, We have mobicontrol on version v13.3.0.3454 we have a lot of device under Zebra TC75X (android 6) who are enrolled by android +. Last week, I've try to update OS android 6 to 7 with stage now and mobicontrol script. The result is ok, my OS is well updated to android 7 and the device STILL enrolled AGAIN (profile, rules, …). All seems to work fine. Nice nice nice :). Well,for to be quiet :) for a certain period of time, we think to migrate to android 8 oreo. But sorry, for me it's not clear I have some question about this. a) Is it possible to jump to android 6 to android 8 directly ? Or it's better to migrate to 7 and after migrate to 8 ? b) Is it possible to enroll an android 8 with android + ? Because, I've read that now for android 8 we must to used android entreprise !!!! c) Why it's not possible to enroll android 8 with android + ? Also, could you tell me if there are some big difference between android entreprise and android + ? All our rules will be work again with android entreprise or we need to review all ? All information is welcome. thanks for your time
Greetings, i'm struggling to get the following devices: -Honeywell CT40, 50, 60 -Zebra TC57, 77 to pair with: -Honeywell 86801 -Zebra RS6000 If the Computer devices are not enrolled they pair perfectly with a NFC bump but as soon as enrolled with SOTI they do not pair. It appears that the device does not show the prompt for pairing after they are tapped with NFC but i cannot find a way to allow this prompt message to show?
Hi, Anyone know if it's possible to add/deploy the widget for the Anyconnect app to the Soti Loackdown screen on a Android device (EDA51)? It could be nice on a Kiosk device to easily see the VPN status and have the possibility to switch it on or off :-) Br, Thomas
How do I prevent the installation of a cab file (bundled from package studio) from prompting the user to choose where to install the application to? It gives the user 3 choices to install to \Device, \Cache Disk and \Application. I would like to have it always install to \Application. How would I accomplish this? We are using motorola Model MC67NA windowsCE/mobile 6.5) mc55x mobile devices tia.
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.
