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, 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.
Hi, is there a way to generate data collection rule of foreground apps, but instead of Android, for Windows Modern? Version: 15.3.0.6713
Hi, I'm hoping someone can help. I have set up a test device with custom data and I can see the fields under the device details screen but no values. The values do however show up under the collected data tab. I'd like to be able to see these values reflected on the device details screen also
We're currently running our SOTI instance on Version: 15.2.3.1033, and attempted to setup an iOS Data Collection rule to pull geolocation data on a set of iPads enabled with cellular data. Data collection is only appearing under device information once the agent is launching. What needs to be configured so that the rule queries these devices ever so often for the geolocation data to be recorded instead of having to open the iOS SOTI app?
Hello Guys, i have created a datacollection rule that collects the hostname of specific devices, the rule works fine ( i can view collected data under device tab) but when i select the rule name to show in the device dashboard i only get "unknown". Version is 14.44 Any advice what i need to check or should try out? Thanks in advance.
We have been having issues with our Samsung tablets running Oreo 8.1, Mobicontrol Cloud v14.3.2.1171. We recently injected the ELM agent version 13.7.3.1045 and most of our devices are using this and today I see that there is a newer version available, 13.7.5.1013, but I can see neither agent listed in the Release Notes located at https://docs.soti.net/soti-mobicontrol/android-agent/release-notes/v137/android-oem-agent-maintenance-releases/ I would like to see what is fixed in these versions to know if we should upgrade but right now I can't tell. In general we are struggling to find any patterns or trends regarding the following issues and hope that a newer agent might provide some relief: Boot loop: the device at the lockscreen will accept the password but will return right back to the password prompt without indicating an incorrect password, Only way forward is soft reset from Mobicontrol console or hard reset on the device (long hold on power button) Collected Data: sometimes stops collecting, will resume after a restart Odin Mode (or Download Mode): numerous reports of devices going into Odin Mode, which is typically done by holding Power, Vol Up and Vol Down simultaneously. Too many users reporting for this to be user error only. We never had the problem until after upgrading Mobicontrol from 13.3 andgoing with the 13.5.x version of the agent. Devices not checking in: Some devices will go offline from Mobicontrol even though they are connecting to the network via WiFi or 4G (they can browse the web, sync data with our survey app, etc, just won't connect to Mobicontrol). Resolved with restart. Thought this might be related to Doze, sent "no doze" script to all devices and agent sleep issue shows fixed in MCMR-16238 False Low RAM Alerts: We have an alert set up to warn us when available memory drops below 768 MB, we get multiple alerts daily on multiple devices that this threshold is exceeded but whenever we investigate we have yet to find a single device actually running that low on RAM, even if we remote tot he tablet within a minute of the alert having been received. None of these is absolutely related to the agent but I can't rule it out either, would really like more comprehensive notes for each release Thanks, Matt
We are on Mobicontrol Cloud 14.3.2.1171 using Samsung Tab S2 and Tab S4 Android tablets. I have a data collection rule set to gather data for available memory, battery percentage, location, signal strength, and a few other of the configurable items. We sometimes encounter situation where we are troubleshooting user complaints and when we go to see where the tablet has been, what the connectivity was like, etc we frequently see that we are missing collected data for the previous week or longer even though the device has been checking in during that time. Our data collection rule is set to run every 20 minutes, and due to server activity we have put the devices into different groups, exh with their own schedule, to stagger the collections so we aren't running the rule on every device at the same time. Looking at device logs it will often reveal that the device is connecting and disconnecting frequently so my theory is that the devices are seldom online when the rule actually runs, or that it disconnects before the rule is completed. We have tried to leverage the out of contact rule but that only tells us if the device connected at all, not that it was persistently connected and able to do it's routine housework. Ideally we could make use of an alert that tells us if there has been no collected data for n-days and run it only against devices that were also "active" (connected at all) during that same interval. Such a tool would allow us to not only proactively ensure we aren't missing any data but to know soon after the device goes dark that we need to take corrective action. We just ran into a situation where a device was lost or stolen and after the fact we find that we haven't had any location data for 10 days. This is just one example, of course. I don't see where the current array of alerts or reports allow us to get this information, can anyone suggest a way for us to do this? Many thanks, Matt
Hello, we have mobicontrol on version 13.3.3454 the client is on version : 13.3.0.1059. our devices is zebra tc75x under android 6.0. I trying to collect some data with the fonction available -> data collection. I've create a data collection with type => IP Address on it . (just for to realize some tests) I've selected somme devices and apply on them. Now on device, i go to collected data on the right panel but every time there is nothing ... I think the steps i follow is not good ..but which one ? why my data collection is always empty .. thanks for your time
Is it possible to create a report based on data collection? For example all devices having an app in the foreground at a certain date/time.
I have been having an issue that I hope the minds here can help with. We are using Mobicontrol Cloud and have been having issues since version 11 (we are now on 14.1) in which we find that we don't reliably get all the specified data from each device, even when they are online continuously, and I think I know why but would like ot hear your thoughts and opinions. We are probably trying to hard to get as much data as possible instead of just what is needed (of all the data we can specify in the collection rule we ope to NOT select only 4 parameters, and I think we are trying to grab it too frequently (20 minute interval). It seems like the 20 minute interval may not be enough to upload each manifest before the the schedule starts collecting again, this assumes that the collection is set up as a round-robin: connect to Device A, upload all that is there to take, connect to Device B, gather that data...and so on. I think we may benefit from taking the following steps: -Reduce the individual items that we collect to only what is needed -Set up different collection rules and stagger them. Our single most important data to get is Location, so we could have a collection rule just for that and make sure it takes place on a schedule to avoid conflict with any other collection rules. Does anyone know if each rule gets its own thread when it executes? I'd like to understand if we can collect the same data if we simply break it up into smaller chunks per rule/schedule, or if it is too much data to collect in the current time interval (20 minutes) and we need to consider going to 30 or 45 minute schedules. Thanks!
Hi, I have set up basic data collection rule just for logging what is going on on our Android devices. Couple of units have noted that they are out of memory, so I got a look for the logging data. 'Available memory' does not seem to give any logical value, starting with minus (-) and amount is high. On some logic it seems to be used bits, but is that a correct assumption since that does not match the idea of title 'available memory'? Data Collection rules that I have set up: Data of the logs for available memory: -1140219904 -1142300672 -1154449408 -1156825088 -1142095872 -1130221568 -1128972288 Units have 4GB memory, so device details give something like 2,94GB / 3,74GB while usage ranging 2,7GB to 3,1GB currently Could someone give a hint how to interpret this data? Thank you for your support! //PMa
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
