Going to upload the new device token and getting an error message "The File received is not valid". Anyone got any ideas? Sync is now failing due to downloading a new Token.
Solved
Unable to upload renewed Device token
+24Best answer by DBrowning
I uploaded a new PublicKey and then downloaded another new Device Token and that seems to have work!!
+23I had the same issue last year. When I called Jamf Support, they suggested that I do the upload using a private browser. That worked.
+24I had the same issue last year. When I called Jamf Support, they suggested that I do the upload using a private browser. That worked.
Just tried that and still no luck. Thanks for the suggestion!!
+24I uploaded a new PublicKey and then downloaded another new Device Token and that seems to have work!!
+23My post from last year has a response that may help.
@hodgesji suggested something that may solve your issue.
+23I uploaded a new PublicKey and then downloaded another new Device Token and that seems to have work!!
Great! I had just replied letting you know about something that someone suggested to me when I had this problem. He suggested the same thing.
I uploaded a new PublicKey and then downloaded another new Device Token and that seems to have work!!
Worked! Thanks
+11I uploaded a new PublicKey and then downloaded another new Device Token and that seems to have work!!
I appreciate that many people are posting back that uploading a new JSS Public Key to ASM is the accepted solution, but I've not found additional information about whether there are OTHER CONSEQUENCES to uploading the new public key. If I do this will I need to update/renew any other tokens or anything besides the Apple Device Enrollment tokens (which is what brought me here in the first place.... "file not valid" error.)
Can someone confirm that replacing the Jamf public key in ASM had no other consequences and resolved ONLY this problem?
+23I appreciate that many people are posting back that uploading a new JSS Public Key to ASM is the accepted solution, but I've not found additional information about whether there are OTHER CONSEQUENCES to uploading the new public key. If I do this will I need to update/renew any other tokens or anything besides the Apple Device Enrollment tokens (which is what brought me here in the first place.... "file not valid" error.)
Can someone confirm that replacing the Jamf public key in ASM had no other consequences and resolved ONLY this problem?
I have had to do this several times while working as a contractor recently for a company that has over 700 Jamf Pro servers. We didn't see any issues with doing this.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.