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 Team, Facing issue when deploying a package on Honeywell 7800 devices with Windows CE. Below is the error from the device. There is no issue with the package as the same is getting installed for some devices. 2020/09/23 02:18:52.397(0x6ef4ca22): EVENT: Creating partial snapshot (ID=150)2020/09/23 02:18:52.513(0x6ef4ca22): EVENT: Cfg: Export to \IPSM\pdb.ini2020/09/23 02:18:52.043(0xaf5bfa32): ERROR: Schedule: Reload2020/09/23 02:18:52.094(0xaf5bfa32): EVENT: Schedule(Install Controller): No more schedule availablenstall Controller): No more schedule available There is also this error where in the device has ample amout of space and the package is just in kilobytes ERROR: CDOSMgr::GetDeviceFreeSpace(\PdbInfo): 0-238133248 Regards, Dheeraj
Hi! We have started seeing some problems with scheduling a package installation with the functionality of Package Install Date. If we for example assign a profile to install the package at a given time nothing will install on the majority of devices, we can remote control the devices, do checkins, but no installation. Until we do a restart of the agent. Then the installation goes through. Are there anyone else that have experienced the same?
Is there a way to select more than one group when setting up a location report? reason i ask is because we have multiple groups for all our different warehouses. i am needing to run a location report on several devices located in different groups. is there anyway to select multiple devices for one report? or will i have to schedule an individual report for each device?
Hello Is it possible via MobiControl create a Schedule Task which start the distribution of the IOS update to the IOS devices Powershell ? Script ? Task ?
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!
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
