Device log error when using mxconfig

Device log error when using mxconfig

I'm using a Zebra TC75x device. I created an mxconfig file using the Stage Now app (sets the screen timeout setting) and exported the xml file for MDM. I took the xml file and created a package with MCStudio. The file is placed in /sdcard/Download/ and the package has a post-install script that runs the command "mxconfig /sdcard/Download/<filename>.xml. I put the package in a profile and assigned the profile to the device. After doing so, I check the logs for the device and see that the package and profile both log as installed. However, I also see an error log that says "Custom log (Mxconfig -/storage/emulated/0/\Download\<filename>.xml was not found.)".

Now, the settings that were part of the xml file were applied successfully (screen timeout and lock screen). So my question is why does it show the error log even though the settings were applied successfully?

4 Answers

Order By:   Standard | Newest | Votes
Matt Dermody | posted this 13 April 2018

It sounds like you're doing everything correctly in terms of generating a StageNow generated MX XML profile and then deploying it with a SOTI package. I use the same exact method for all of the Zebra device types that I manage and I don't recall ever seeing that error in the log. The only difference that I can think of is that I'm storing the XML files in another directory (/sdcard/manhmx/) but I don't think that would make any difference in outcome. 

 

 

 

  • 0
  • 0
Matt Dermody | posted this 13 April 2018

Actually I just double checked and I am actually seeing the same error messages in the logs as well, despite the configuration being successfully applied. Maybe it's a bug?

  • 0
  • 0
David P. | posted this 13 April 2018

Could be then. I also get an error message when I try to turn on watchsettings. I send the command "watchsettings on" and the log says script command not supported by the device (Zebra TC75x). Have you had that happen with any of your Zebra devices?

  • 0
  • 0
Matt Dermody | posted this 13 April 2018

I actually was going to suggest you try the watchsettings method given the specific use case of setting the screen timeout value. I assumed that you were likely using MX for setting additional configurations that are not even exposed through that method which is why I held off. Either way, for screen timeouts specifically I have used this script for setting screen timeouts and don't recall running into any issues. 

 

writesecuresetting -sys screen_off_timeout 600000

 

Then again, I traditionally enroll using Android+ and DA mode and if you're on a Nougat TC75x you might be using Android Enterprise and DO mode, which will support a different set of management features. 

 

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback