"Is Charging = TRUE"

M
MetroMRA
METROSELSKABET I/S

Hi

We have been using "Is Charging = TRUE" filter for a month now to make OS updates on our Zebra TC56 and TC57.

But now, for som reason that Filter does not work anymore. I have several devices I know are in charger, but when making a manual filter search, non comes up.

We are running Version: 15.1.2.1035

4 years ago
SOTI MobiControl
ANSWERS
J
JCMOD@SOTI
4 years ago

Hi MetroMRA,

Thank you for posting in SOTI Central.

This could be a problem with your Search Service, a common way to redeem integrity issues is through the following:

1. Navigate to Global Settings

2. Click "MobiControl Search Sync Interval"

3. Press "Sync Now" then occasionally press "Refresh" until the synchronization is complete

4. If the Integrity is still below an acceptable level, then repeat step 3.

Also to note, for big environments, it's advisable to stop the Deployment Servers before performing this step. You will then repeat step 3 twice and the Search Integrity should be 100%. Then start the DS Servers back up, however there sometimes can be other issues that affect the server and in cases like that, you should contact our Technical Support Team.

Once it's 100%, you should then see the most up to date information on your search filter.

If this resolves the issue, please mark this post as the solution. Also, feel free to reach out if you need clarification or have any questions.

Regards,

M
MetroMRA
4 years ago

I have tried your suggestions and even if I hot 100% the filter does not work

J
JCMOD@SOTI
4 years ago

Hi MetroMRA,

Do you think the problem is specific to that filter, could you try other filters and validate if they work? Also earlier on I tested this on a 15.2.3.1033 internal server and it worked fine. Has anything changed in your environment if you compare it now vs when it was known to work?

Regards,

J
JCMOD@SOTI
4 years ago

On top of the above, to validate if the Search Filter / Search Service is the problem. Run this query on your database:

SELECT * FROM dbo.DevInfo WHERE IsCharging = 1;

If it outputs results then we know where the problem resides.

Regards,

M
MetroMRA
4 years ago

If I run the query I get the same error result.

The only change that has been done, is windows update has been performed on the windows server 2012 it runs on

J
JCMOD@SOTI
4 years ago

Hi MetroMRA,

To clarify, you ran the SQL Query and no results returned? That means no agents are reporting that they're charging. Perhaps it's device related in that case. Are you using the same device model across your environment or are there any devices you can quickly test and charge to see if results are returned in SQL query?

Regards,

MD
Matt Dermody Diamond Contributor
4 years ago

Most of the properties you see reported in SOTI are not collected in real time, they are collected at the Check In interval which is by default every 2 hours. If your search sync is indeed at 100% there is still the possibility of the data being up to two hours stale based on the check in window. If you select the device and opt for a manual check in you should see that the properties get refreshed.

M
MetroMRA
4 years ago

To specify. Some devices shows up both in SOTI and in the Query.

But I have several devices that I Know are in charger, that do not show up.

There are no difference between the ones showing up and the ones not showing up.

M
MetroMRA
4 years ago

I have tried that as well without luck.

Most of the properties you see reported in SOTI are not collected in real time, they are collected at the Check In interval which is by default every 2 hours. If your search sync is indeed at 100% there is still the possibility of the data being up to two hours stale based on the check in window. If you select the device and opt for a manual check in you should see that the properties get refreshed.

J
JCMOD@SOTI
4 years ago

No difference in terms of Model, Agent Version, OEM Version, Plugin Version (If applicable), and Profiles?

Regards,

M
MetroMRA
4 years ago

No, no difference

RC
Raymond Chan Diamond Contributor
4 years ago

There must be some difference(s) somewhere. Are profile/action deployment equally responsive for both groups of devices? Perhaps you can also check connection parameters (mode, interval, etc),  data-collection parameters (buffer size, etc.),  network connection type, cellular-operator/Wifi set-up, different feature-control/firewall policies deployed, etc