dostadawg Posted June 26, 2017 Report post Posted June 26, 2017 Like to pick the brains of the experts with an enrollment issue I am having. I am trying to reuse a corp iPhone and re-enroll it for another user. When i try to re-enroll the device and User affinity is turned on I get stuck a the Configuration Screen where it keeps prompting for username/password. If I turn off User Affinity once i try and enroll the user through Company Portal I get the an error of UserLicenseTypeInvalid. Most solutions i have found seem to point at the license is not assinged correctly but i am sure that is not the problem. I can actually enroll the user on another device with no problem, an iPad. Which lead me to believe the problem must be with the device and it is "hung" somewhere in AzureAD but not sure where to begin to look. I am not the person that deprovisioned this device so I am 100% what the tech did but they claimed they did the Retire/Wipe Option and not just delete it from the console. The user that the phone was assigned to previously has also been been deleted from our AD/O365 tenant. Is there anything i am missing or somewhere I can look to see what the issue is with this device? Thanks in advance for any input. Quote Share this post Link to post Share on other sites More sharing options...
dostadawg Posted June 29, 2017 Report post Posted June 29, 2017 Just an update as I finally got this working. First off this was a lesson of verifying the info giving to you. Come to find out the user had not been enrolled previously. So with that tidbit after much troubleshooting determined it was definitely something up with the user on the Azure side. Working with Microsoft we determined everything was setup for the user in AD, SCCM, O365, AzureAD from what we could see. So what I had to do is actually disable the user and make sure they were removed from O365, AzureAD, SCCM Intune Collection and not showing up in the SCCM db. Then I reenabled the user and verified licenses were correct in O365/AzureAD and showing back up in the SCCM collection and db. It worked. Hope I don't run into this problem too many times but at least I know the work around. Quote Share this post Link to post Share on other sites More sharing options...
