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.
Hi, since the last MobiControl update, v14.3.4 Build 1087 , i cant edit or assign current/new profiles to devices. When i click in a current profile edit, the popup shows "add profile" with empty data. When i want to assign a existing profile the following error occurs: And in the Header is something missing
We are currenty testing deploying iOS Applications to our managed iOS devices within MobiControl. We are not enrolled in the Apple DEP program and our iOS devices are enrolled into MobiControl unsupervised. We therefore assign a profile to our iOS devices with a default web clip to access the Application Catalog. Any applications can then be downloaded and installed from there via the relevant Application Catalog Rule. We have enrolled two test devices for this scenario, an iPhone and an iPad. On the iPhone, we successfully deployed a Profile containing the App Catalog web clip and was able to install applications from there. However, on the iPad, even though the same Profile is assigned to this device, the profile remains at "Pending Installation" status and will not install the default App Catalog web clip from this Profile. Has anyone had this issue before where iOS profiles are stuck at "Pending Installation" status? Are there any agent or server side logs I can view to see why this profile is not installing?
In the Windows CE world, I always manually controlled when my applications updated in MobiControl by moving devices to new release folders. Yeah, I know that is not how most installations do it. I did this for several reasons. The first devices I managed (Psion 7530/7535s) were highly unreliable on their installations. Under Windows CE the executable sizes were small and finally I found the scheduling in the early versions of MobiControl to be unreliable with Windows CE. Now I am diving into the Android world with both feet due to the shutdown of 3G Cell. While it seems Android is more reliable about installations, the install size of the applications is huge compared to Windows CE and let's not talk about patch sizes. My issue is that my devices are very often stored in areas that contain a lot of concrete and steel which by nature makes cell connections hit and miss. All devices are supposed to be put in networked cradles every night, but we all know how that goes :-/. So I have come to the conclusion that I NEED to evaluate methods of utilizing the options within MobiControl that allow for a scheduled delivery. What I would like to accomplish is to have a profile with the new versions of my applications get pre-staged on the device and then when the time comes that I what them installed, the installation gets triggered and the installation happens quickly. I thought I had figured it out and attempted to set up an install using scheduled profiles for tonight. What a mess! Fortunately I am still in the the 100+ devices, but over the next month I will be sitting with over 1000 devices. Since the Agile development is going on, everyone things that we can have deployments every two weeks...... in my opinion not a pretty site. My problem tonight what that I had Profile A with version 1 of the app and I attempted to assign Profile B with version 2 of the app. I set an install date far into the future as I only wanted the apps to download but not install. My plan was to replace Profile B with a Clone of Profile B without the schedule associated with it. I didn't get to first base as Profile B failed because it said the a version of the application already existed on the device. I thought I had this whole thing worked out in my Dev environment. So, I am looking for advise, how are others accomplishing this. My applications are line of business applications and the versions that are supported are tightly controlled by the development teams (they rarely support more than 1 version). Environment: MobiControl 14.1.2 Agent: 13.6.0.1662 Android Management: AEDO Device: Zebra TC77 Locked down in Kiosk Mode Shared by multiple users Any advise appreciated. Thanks in Advance.
After an upgrade of MobiControl from v13.4.0 to 14.3.2 we have an issue where devices do not download profiles, and the search integrity is usually around 30-40%. All the needed ports are open and the system was working before the upgrade. Ports 9200/9300 were opened during the upgrade process. Are these two issues linked to the same root cause or completely independent issues? Setup: 3 servers, 1 mgmt/DS on LAN, 1 DS in DMZ, 1 SQL. The agent has been updated on the devices. Any ideas how to resolve this?
Greetings. I want to know, if it is possible to avoid being screenshot about a managed profile? I disabled it in the function control, but it did not work for me. Is this function only valid for Managed Devices?
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?
I've cloned our companies existing profile for iPhones, as a test group. I've added 9 users to this group. All devices have received and installed the test profile, but 1 user is not able to do one of the functions specified in authentication. User has an iPhone 7 (12.1.4) and is unable to specify and easy password. On my phone i created a simple password, was advised that it could easily be guessed but selected "user anyways". My colleague who is on the same profile, confirmed it has been installed, cannot specify a simple password. When he does he gets the message that the password can easily be guessed but only gets the option to "change password", use anyways is not an option. We have force restarted the phone. Still will not apply that one setting Everything else appears to be correct. Any ideas?
Hello all, I have a tablet Panasonic FZ B2 under android 6.0 On this tablet , i have a mobicontrol client on version 1330 1110 since several month. All works fine but we need to update the tablet with some news feature and restriction. we 'd like to update this tablet with soti surf and new version of client mobicontrol. For this, i have create a profile and on this profile i have put inside two packages (package studio) - first position : client mobicontrol on last version - second position : soti surf => download from the site (https://docs.soti.net/soti-mobicontrol/downloads) result is client is well installed and connected but ...soti surf isn't installed ...and no information about what's happen's ... no error, profile is on status installed. If i change on profile the order of installed package : - soti surf - mobicontrol client Result is the same ...soti surf not installed Of course, if i installd all apk manually all works Any idea ? thanks
Hi, Please help me to configure VPN IPsec Xauth PSK with Login and password at SOTI Mobicontrol platform to apply them on tablets with system Android + . very urgent. Thanks you for your return, Best Regards,
Recently we had changed our root DMZ certificate for our Zebra/Symbol MC3190 and MC3200 devices however we are having a lot of trouble with wireless connectivity on multiple devices after it went live. After the change, we are noticing that some of our Fusion profiles are not connecting anymore even after verifying our wireless settings are correct and that the correct certificate is bound to the correct profile we want to use, not all of our production devices have experienced issues. We deleted the old root certificate as well. We can use bar-code provisioning for our MC3200 devices to install a “support” profile as well as delivering the new bar-code embedded certificate which works pretty well but doesn’t stick. What we are seeing is that the certificate delivered from the bar-codes for the 3200 handhelds is disappearing each day when the device is rebooted or has a battery swapped out. Here is the tricky part, each store has its own folder for district>region>store and each store folder has individual wireless settings. Due to this structure I was not able to use the cold boot persisting bar-codes due to the fact that it leaves copies of the said profile on the handheld (if stores use the codes more than once) and we only want the device to use the store profile we created and not the "support" profile assigned by the bar-codes. It seems that the store profile is our point of failure but I am unable to determine if this is a device issue, or a profile issue. Is it possible that the individual store profile is carrying a conflicting certificate and is somehow and overriding the new root cert that we pushed out via a blanket profile over all of production? If this is the case would it require manual removal of the root certificate from each store profile? When we rolled out the new certificate we used a profile with the new root cert attached and assigned it to our production environment in phases. We then used the reporting feature to check to ensure all of our production devices received the new profile and reported "installed". We remoted in and verified the new certificate installed on a number of device's root cert store, but we are still seeing issues after the original cert expired. Is there any way the Fusion profile could get corrupted due to the certificate update? We are looking for a way that we can potentially re-provision our devices offline as they are now disconnected and we do not use networked charging cradles that can reach the deployment server in the stores. We are fervently trying to avoid needing to physically replace these units if possible. We appreciate any help or insight you can provide. Thanks
I have a question and a suggestion for the Soti "feature request" folks. Is anyone trying to manage apk updates that will not conflict with a running app? If so, how are you doing it? We have a couple of applications that it is paramount that we not update if the app is running. The normal android app store knows how to do this, ie, not update an apk if it is being used. Our devices are all COSU and are kiosk locked so there is no "self serve" option. The profile model is maddening. It has TONS of options to cover the "IF" a profile should apply but precious few to cover the "WHEN" it should be applied. It has Network Connectivity, specific time, and battery level. I need to be able to check if a specific app is running and if so, defer the assignment until the next check-in. I could even work with "charging/not charging" as a proxy for app use but that isn't an option either. Coupled with the fact that the Android script engine has no conditional processing I am unable to figure out a way to meet this very reasonable customer demand. At this point it appears we will have to erect a secondary server infrastructure and a device side agent to call the MC API to assign profiles on demand, which is exasperating since that is basically what we purchases MobiControl to do. Anyone see something obvious I'm missing?
I have a Samsung device that was setup as a work managed device. I have read that "encryption is enabled by default" on work managed devices but have seen the opposite on my devices. When I check the device statuses the encryption status is always "no" unless I manually enable secure boot on that device. I have searched high and low for an option to enable this but can not locate one. On standard android+ device profiles when the encryption option is enabled it turns on secure start up which requires entering the pin before the phone boots. Is there a way to force enable secure startup via MobiControl or am I stuck manually setting it.
I've just noticed that application stays on device after being removed from profile. Is it expected behavior or I've messed up with profile configuration (didn't increment version) ?
Do I have to uninstall my existing Android App, everything I want to deploy a package with an updated APK in MobiControl? Here's my workflow: 1. Factory Reset Nokia 8 Android 8.0.1 phone and set up with Android for Work (afw#mobicontrol) and enroll in MobiControl. 2. Build my Android APK, create a Package, and assign Package to Phone 3. Confirm app is up and running 4. Make a change to my Android APK, create new Package 5. Remove old package from Profile and add new Package 6. Save and Assign to phone 7. Install fails with File IO Error Current workaround: 1. Remove old app on phone by looking at Applications in MobiControl, finding the app and clicking remove 2. Redeploy new Package. The problem is that by uninstalling the existing app I am loosing a database that I need to maintain and this is alsoa long and painful process for 60+ phones. Am I missing something here? Thanks, Ciaran
Hello all, i'm beginner with soti mobicontrol, we have mobicontrol in version 13.3.0.3454 and we have +- 700 devices under android 6.0. we have a package who contains an apk who is installed on all devices. Now, we have a new version of the apk and of course we'd like to update all devices with this new apk (package). For to do that (testing), on 1 device i've created a new package with the new apk. on this package, i have created a script who run (pre script) a command for to uninstall the apk i have put this package into a new profile, and assign this new profile to my device. that's work fine but..i've notice and it's normal i have two profil on this device !!! profile 1 with the old package profile 2 with the new package i think my procedure isn't a good way ? My question is, how i can update all my device with a proper method ? Is it possible to find a good procedure or tell me how i can delete a profile with a command perhaps ? thanks for all Christophe
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.
