Zebra Nucleus User Guide

Frequently Asked Questions

Frequently Asked Questions

Access a curated list of common questions about the software. This fast-track resource helps you understand key features without searching the entire guide.

Mobile Computer Enrollment
Question	Answer
What do I do if my computer is not scanning barcodes on a monitor?	The ability to scan a barcode displayed on a monitor is subject to a number of factors. If you are unable to scan a barcode from the screen, try these changes to the display parameters: Increase the screen brightness Increase or decrease the display resolution Increase the browser magnification (to enlarge the barcode)
Why did the device fail to enroll after scanning the enrollment barcode?	One potential cause is that the device was not in a factory-fresh state (reset) when you attempted to enroll it. Perform a factory reset and try to enroll the device again. Enrollment failure sometimes occurs if network connectivity is down or the Zebra Nucleus server is temporarily unavailable when you scan the barcode. As a remedy, use a network diagnostics tool (for example, Ping) to verify internet connectivity and availability of the Zebra Nucleus server and scan again. If enrollment still fails, generate a new barcode and try scanning again. If enrollment continues to fail, one of the following might be the cause: The Wi-Fi section of the enrollment Profile contains an invalid setting The device is already in Device Owner mode The Zebra LifeGuard Over-the-Air service is not installed or not running GMS services are disabled or not present
After trying to enroll, why are the devices "greyed out" with an "Enrolling" status label?	Though rare, this issue can occur if the Enrollment Manager or a download or install step fails during enrollment. Device status changes to "Not Enrolled" after an extended period of time, possibly as many as five days. To clear the status immediately and attempt re-enrollment, perform an Enterprise Reset on the effected device(s).

Mobile Computer Inventory
Question	Answer
I just installed Android 13 on my device. Why is it not it manageable anymore?	When first booting (or rebooting from either a cold boot or hard reset), all Zebra devices running Android 13 (or later) must be unlocked (using PIN, password, or pattern) before the Zebra Nucleus client app launches and enables device management. This issue also applies to some 6490-platform devices running Android 11.
Why are some devices shown with a (!) warning symbol?	The (!) icon appears next to devices that contain out-of-date Zebra Nucleus device software, or were enrolled using a barcode created with an older version of the Zebra Nucleus console. The remedy for either scenario is to select "Update Zebra Nucleus Client" for the affected devices.

Using your Printers
Question	Answer
What do I do if my app crashed while communicating with the printer?	If you think the app is crashing because you are communicating to the printer: The device may be unable to communicate because it is out of range or the printer is off, it throws an exception. Make sure all communication to the printer is in try/catch statements. Verify you have the proper permissions to communicate . Communicating to the printer can sometimes take time, sometimes seconds. Handle it as a long-running task. Always communicate to the printer on a thread other than the UI. If you are concerned the print jobs were not printed: Check print status during printing. Keep track of the odometer in the printer to check labels printed.

Using you Scanners
Question	Answer
Why is my scanner not visible in My Scanners and Device Inventory ?	It is possible your host computer is not connecting to Zebra Nucleus . Check to confirm the Client is installed on the host computer. Review the log and confirm you've established a connection between the host computer and Nucleus Client. Ensure your devices meet the network requirements. Re-enroll the host device using a new enrollment file.