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 am testing mobicontrol as a potential support tool for a clients roll out of M3 SM15X devices and I have an SM15N device for my testing. I have manged to enrol my SM15N (Android V7.1.1) device and I can remote control it using the M3 SM10 profile and this works fine. When trying to use the same solution for the SM15X (Android 8.1.0) devices there is no option for Remote Control, only remote view. How can I get remote control working for the SM15X devices?
I have a couple of devices, android plus, OEM Agents currently on 14.5.5, I have updated the agent compatibility on the server so the devices are showing that they need an agent upgrade.However, it doesn't matter how many times I click Upgrade Agent, they just will not upgrade. The devices have plenty of space, and battery charge. Any ideas of how to resolve this please
Hello all,I would like to update Apple devices via the API I use:POST /devices/{deviceId}/actions { "Action": "AppleSoftwareUpdateSchedule"} do I have to add a parameter? as error I always get: { "$type": "ErrorDetails", "ErrorCode": 0, "Message": "Vertragsprüfung fehlgeschlagen", "Data": [ "actionInfo: Error parsing value" ], "HelpLink": null } I hope you can help meThanks
Hi, I migrated our on-prim MobiControl server to an on-prim cloud service server. I added the new server address as the secondary deployment server in the MobiControl admin application so the devices would connect once the old server was shut down. Some of our sites didn't power on there unused devices as instructed and the secondary/new server address didn't get pushed the those devices. Is there any particular file (PBI.INI) I can edit to reflect the secondary address (new server address) or do I have to wipe MobiControl and re-enroll those devices? These are all old Windows CE devices. Thanks,
Hello, Does anybody know why after assigning a new IP address to the MS the displayed IP in the console is "still" the old one? In the MCAU we use only a FQDN and no IP adress. MC vers. 15.4.1.4828 update: dbo.MSInfo->IP
Motorola MC55A0 & MC5590 disconnected from SOTI server after migrate SOTI server to AWS. These devices are offline and not connecting to SOTI server even after connected network\WIFI. What could be the reason and how to fix it to make it these devices get connected again to our SOTI server. These are on OS Windows Mobile /CE and version 5.2 Also wanted to know is there any process , config to switch the WIFI network from one SSID to another SSID without any impacts.
Hi All, I have a locked down google app. The only way for me to break out of the device is to revoke the profile. Is there anyway for me to access the device without revoking the lockdown?
Dear community, I was wondering if someone knows how you could change the logo in the Dynamic Android Template. I have tried to change it using the logo and logoImage keywords in the #header section, but that didn't work. My current configuration is: /* HEADER BACKGROUND COLOR */ #header { background-color: #0099d3 !important; logoImage:url("<MCImg_Momo text logo (XL).jpeg>"); }
Hi, I have a problem with the collected data location feature where the data in the logs is not the same as the one in the collected data location.as shown in the logs, there is a data location recorded at 2:32:07 AM but when you check the collected data location, the data is empty as shown in the collected data image.
Hello, Recently we started using Panasonic FZ-S1 Android 10 tablets. We've installed the v14.5.3.1017 OEM specific MobiControl device agent and the corresponding plugin and everything seems to be responding fine. We're using a profile with a lockdown and an authentication password. And now when you reboot the device it's got problems with deciding which default launcher it should use. The screen is on and active but stays black. After a while, it warns that MobiControl is unresponsive and gives the options to either wait or close MobiControl. Waiting for MobiControl to work just keeps resulting in the same error, but if you close it down it offers the option to select another launcher: Quickstep, Panasonic Enterprise Launcher, or MobiControl. Only if you select Quickstep (which is the 'normal' default launcher), the tablet responds and shows its normal screen. If you select MobiControl, you end up in the same errors as mentioned before. That's not what we want though, we'd like to have MobiControl show it's lockdown screen. Only if you select Quickstep and choose to "always" use it as its default launcher and then re-open MobiControl, it'll show its lockdown screen and will work properly untill you reboot the device. Does anybody have an idea what we could do about this? Kind regards, Theun SchellekensMobiCoach B.V.
Hello, We have mobicontrol in version 14.49 all works fine with lot of devices inside Zebra But since today and i don't know why when some users click on the link -> view all devices NO devices are visible and of course the search bar is EMPTY .. Any idea ? thanks
Hello, I have the below issue in Soti Services (in announcements) " a problem has been identified with your Mobicontrol environment. SOTI services are not available at present, this will impact your license validation and device enrollment processes" what is the cause of this issue although everything working normally. Regards
Hello, i need to configure a auto power on when the devices start charging. The devices are Android 10 & Android 11. Do you know any script than can allow this behaviour? It depends on the manufacturer?
Can anyone verify if Mobicontrol v13.4 supports Android 11 devices? We're currently running a mix of 7.1 and 8.1 Android devices. One of our sites is pressed for devices and are looking at Zebra TC72s running Android 11. We're unsure if there are any upper limits on what Mobi v13.4 supports. I don't foresee any issues with Android 11 devices using the same AFW profiles that our 8.1 devices use, but it's always nice to get a confirmation.
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.
