I use this on a regular basis, and as long as the MDM commands are going through, it works well. The only consideration is that this will kick off the binary re-enrollment process, so if you have any policies with the trigger set to Enrollment and frequency Ongoing, they will run again. And, if you have clear policy logs on re-enrollment enabled, any Once Per Computer policies will run again as well.
I use this on a regular basis, and as long as the MDM commands are going through, it works well. The only consideration is that this will kick off the binary re-enrollment process, so if you have any policies with the trigger set to Enrollment and frequency Ongoing, they will run again. And, if you have clear policy logs on re-enrollment enabled, any Once Per Computer policies will run again as well.
This may not be what you are seeing, but be sure you are looking at the correct device record in Jamf Pro. If this unit has had a service event, it may have the same serial, but a new UDID. This will cause Jamf Pro to create a NEW device record when the device re-enrolls. You may search for serial and find two device records, one is checking in normally, but the other is not.