There's a new home for Articles. Find Articles on Our Product Support Page.
Hello all, I have mobicontrol on version: 133.0.3454 Our client is Zebra TC75X and the version of client mobcontrol is on version : 13.6 build 1476 I have two profiles: - one contains a lock down and setting for soti surf (url) - other contain all for black list application Together all works fine :) But imagine this scenario , if user find the lockdown password -> lock down is off With this, I've notice that after several seconds, I see that the application that are black list in the second profile appear ... Why ? The second profile is always enable .. Thanks
The latest MobiControl 14.3 is no longer saving changes to existing Profiles. I uploaded a new Package (let's say version 2.0) then modified the Profile's Package assignment to the latest version and hit "Save & Assign". At the Save & Assign window, I basically hit the save button to keep the previously selected groups. The new UI's Profile page then shows me an older version "1.2", and the changes I applied were not actually saved (confirmed by revisiting the old UI's Profile window). Reopening the Profile's list of Packages shows me the previously selected Package version "1.5" when I had in fact chosen "2.0". Simply choosing "Save" instead of "Save & Assign" makes no difference. Deleting the older package "1.2" does not help; the new UI still thinks I have selected "1.2" while the old UI shows "1.5". Now before you tell me "just create a new Profile"... I have some bad news for you. The same problem is replicated when creating a brand new Profile with a single Package. I select the latest version (2.0) and the new UI shows me the older version available (e.g. 1.3, since I deleted "1.2" before). And yes, I cleared my browser cache, cookies, the kitchen sink, etc. MobiControl 14.3 also stopped supporting RSA-PSS certificate signatures (this was fixed in 14.1.x and is broken again!) resulting me to re-generate SHA2 certificates. So yeah, probably a good idea to postpone updating to the latest and greatest until these issues are sorted. Side note: the new Profile and Package UI reduces productivity quite a bit. Takes more clicks and more pop-up windows to delete packages. Was this "improvement" actually necessary?
Does the Time Synchronization policy not apply to Android Enterprise devices? I'm becoming increasingly frustrated by the lack of clear separation of capabilities between AE and Android Plus within the documentation and the SOTI console itself. These Advanced Configurations are listed under the Android Plus device family but Custom Data works on Android Enterprise while Time Synchronization doesn't? Is there anyway to know what scripts and Advanced Configurations do and do not work in AE without manually guessing and checking? I would expect that given that the Help documentation is a centralized web page that it could be updated more frequently.
I have a 14.2.2 MobiControl Cloud instance that was working fine with Remote Control until the trial of SOTI Assist was activated. Now every time an attempt is made to Remote Control a device this error comes up. Has anybody seen this? Since it's a cloud instance I am likely at the mercy of SOTI support to get this resolved if it requires managing anything at the server level but I'd still like to get an idea of what is going wrong.
I am trying to build a kiosk lockdown for a customer.ive not much experience in using this and wondered if there are any templates other than the default ones in could download?
hi everyone, i configured soti surf and everything seems right. but for some reason the app will not launch. it seems to be stuck on the red Soti Surf logo screen. it will never load/launch the browser. could there be something wrong with my android for work profile? soti surf works well on Android plus enrolled devices. Soti Surf version 14.2.0.119 Thanks in advance for your help!
Greetings. We want to enroll some Android Enterprise devices. We have a firewall that does not allow communications to download the required google components. Can you tell us what rules to create in our firewall?
Hi all, there seems to be a problem with RC (plugin downloaded from soti.net) and TC20 latest AE agent (13.6.0.1662). When AE agent is updated to the latest version, then a reboot of device the remote control stop working, in details: RC stay in "waiting screen". It does not matter the version of Android (Nougat or Oreo), the problem it's with the AE agent. In a Zebra TC51, same plugin, same agent version, same enrolment type works fine. Has anyone had the same problem? Thank you, Filippo
hey guys, when i enroll my samsung tablet with enterprise, alot of the apps get uninstalled. we need apps like camera, gallery, calendar and calculator on the kiosk. is there a way to correct this? i am sure i am missing a step.
I'm noticing that a number of devices are starting to enroll as duplicates in a new environment that I'm managing. Has anybody encountered anything like this? Server: 14.2.2.1170 Agent: 13.6.0.1567 Management: Android Enterprise - Device Owner Enrollment Method: StageNow - Agent Install + mcsetup.ini + MX based I take it that it might have something to do with my Enrollment method but I'm not sure how to prevent it or remedy it now.
We have a number of XCover4's and Active2 Tablets which the user accepted an update to the operating system which crashed the device. We've had the devices re-flashed by Samsung Support Centre, however after downloading Mobicontrol and trying to open it to configure it the device crashes. I have a call open to the helpdesk was wondering if anyone else had experienced the same issue and we are wondering if it is an Android/Mobicontrol version conflict of some description.
How can I force all devices to use High Availability for GPS?
Is it possible to pull Integrated Circuit Card Identifier information from reporting. There are no current options to pull this information from any report that I can see. I would like to report on Sim card numbers.
Hello all, I have a mobicontrol server on version : 13.3.0.3454 Our device is zebra tc75x with agent on version : 13.6 build 1476 Some device are in android 6.0 and 7.0 Devices are enrolled by android+ I've find on google this link: https://www.soti.net/mc/help/v10/en/Content/Web/Devices/Android/Device-Configuration-Application-Control.htm In this link , it's possible to disable access to device setting with application control. I would like to do the SAME thing but I can't find it on my server version -> v13 Any idea perhaps or I need to buy some brill ? thanks for your time
I have an enterprise B2B application that I distribute to devices via SOTI Package in a Profile. SOTI is properly installing the APK and is also now automatically granting the required permission (just storage) which is a nice feature recently introduced in this agent version. The issue that I'm now facing is that the app itself will no longer launch and I get a permissions related toast message error as soon as I try to launch it. The same version of the application works under the following circumstances: AEDO Managed Zebra MC33 running Android O (8.1.0) with LifeGuard 12 on SOTI server 14.1.3.1587 and the 13.6.0.1567 Android Enterprise Agent.- App runs correctly AEDO managed Zebra VC80x running Android O (8.1.0) with LifeGuard 12 on SOTI server 14.2.2.1170 and the 13.6.0.1622 Android Enterprise Agent - App crashes on launch with permissions error. I'm trying to isolate my variables as much as possible to identify the root cause of this problem but I'm starting to think that it has to do with the automatic permission granting of the new agent version. Is there any way to disable this feature so that I can manually enable the app permissions? The forced upgrade to a newer agent version seems like a pretty frustrating side effect of leveraging Android Enterprise with a Play Store distributed agent. Is there any way to lock in a specific agent version for AEDO enrollment if it does end up being the Agent causing the problem?
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.
