Forum Discussion
VPP Apps on DEP iPadOS Devices Do Not Automatically Update Error code: 0x87D13B9F
Hi,
I came across that same issue last week. Somebody already mentioned it here, but it really was the case that the token (under Home > Tenant admin > Connectors and tokens) would show as active, but when you would click on it (Home > Tenant admin > Connectors and tokens > "TokenName") the state of the token would say invalid even though the expiration date was not due yet. The only thing that helped was logging in to ABM downloading the VPP token and uploading it again. After a few minutes it would show the state as valid again and the apps would update on the devices affected by this.
Hope this helps.
MattisJanos Thanks for following up on this and I appeciate the super hot tip. I did a quick check and everything seems to check out:
Although this it is a pretty standard operation, I'm going to submit a request for change (RFC) to re-import the token & see how that goes.
Question: We're transitioning from one MDM solution to Intune and I'm wondering if, since some apps were delivered using the other MDM solution, do need to set 'Take control of token from another MDM' to yes?
JuliusPIV, your token looks fine, so that shouldn't be the issue here, you're right.
Regarding your question; This is what MS Documentation says;
"Take control of token from another MDM - Setting this option to yes allows the token to be reassigned to Intune from another MDM solution."Not sure if I'd set this to yes, since you'll have to create a new MDM Server for Intune as a new solution in ABM anyways, so you'd also get a new token different from the one being used so far. I probably would leave it to no, since that what I also did when we had a migration project. It was from Intune to Intune, but the ABM tenant were two different ones and the users unenrolled their devices from the old Intune tenant before. Not sure if this information helps.
