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.
Hello, Getting errors trying to import a CSV with our dozens of locations. The error simply says "Please provide custom data or IP range for (). Invalid Destination Path ()." I have a CSV with 3 columns, the paths of our OU's, the starting IP and the ending IP. Example: \\Company Name - Enterprise\Zebra TC-56 Active and Deployed\Location1 192.168.1.1 192.168.1.254 Is this correct? Do I need customdata columns, or headers? SOTI documentation is lacking with this. Thanks!
Hello there We have the following situation: There are several Android 8.1 Devices which we want to update to Android 9. These devices are working in Kioskmode and are using the Phone App. As the Bundle ID of the phone App is not the same in Android 8.1 as in Android 9, the updated devices can't access the phone app anymore and we have to move the device manually in the desired group. Is there any possibility to automate this process throug device relocation rules? My hope is somehow autofill a custom attribute when the device is updatet to Android 9. Is there any chance to do this? Thank you and best Regards Beni
Hello there We have the following situation: There are several Android 8.1 Devices which we want to update to Android 9. These devices are working in Kioskmode and are using the Phone App. As the Bundle ID of the phone App is not the same in Android 8.1 as in Android 9, the updated devices can't access the phone app anymore and we have to move the device manually in the desired group. Is there any possibility to automate this process throug device relocation rules? My hope is somehow autofill a custom attribute when the device is updatet to Android 9. Is there any chance to do this? Thank you and best Regards Beni
Hey folks, I'm trying to create a CSV file for bulk import into a Device Relocation rule that SOTI will accept. I'm not sure where it's falling down because I'm providing it what it wants per their documentation. The file I'm testing is just a standard UTF-8/CRLF formatted CSV file with one entry but the only quirk is that I don't need custom data. I would just think the import processor would just drop it. Nevertheless I've tried extra commas, fake data, etc. and it still complains. The error I get is a variation on the following: Please provide custom data or IP range for (). Invalid Destination Path (). Example: \\Company Prod\Retail\001-100\001,10.1.100.1,10.1.100.250[Blank Line]
First off my ultimate intentions is to have one barcode that loads all Zebra devices. Doesn't matter if it is a ET50, TC70X, or a TC50. With that in mind I have setup the add rule to drop all devices into a Stage folder. My goal is to setup a device relocation based on the device model. Unfortunately IP and Custom Data are the only option to trigger relocation rules (Soti PLEASE make this more flexible in future!). I could use the Custom Data, but the only way to fill a custom data feild is through an INI or XML file off of the device (again FLEXIBILITY please...). So at this point i'm thinking a file sync rule with a custom script post file sync that will take the %MODEL% and write it to an ini file on the android device. Then I can tie the custom attribute to that file and pull back what was written into that ini. FYI - I have this working on WinMobile devices since there are ini files built in that include the device model. I am very weak at writing soti scripts and am wondering if i'm on the right track before I spend a bunch of time writing the script. Is there an easier way? Will this work at all?
Dear all, is there any way to move devices based on device name from one group to another group ?? as our policies are differing based on group . so there inter group movement is very frequent
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
