Configuring VPN Remote Access for the first time on your Sophos XG Firewall? Check out this useful Community post!
We'd love to hear about it! Click here to go to the product suggestion community
in former times we registered iOS-Devices with Apple Configurator 2 via USB and successfully deployed these devices. Starting iOS 13 we have problems finish the Apple Configurator "preparation" process.
We get Invalid Profile [MCProfileErrorDomain - 0x3E8 (1000)] Error - due to this error we can see the device within the Sophos Console (after we moved the device within Apple business Manager to the correct virtual MDM-Server (SMC 9.5.2 in our case).
On device side we get a remote configuration popup - but we can not procees: invalif configuration profile.
So guys: who is able to add iOS 13 devices with Apple Configurator 2 these days?
Thank you for your feedback.
Would you please confirm how many devices you are seeing this error? Could you please try to remove the device from the MDM solution, factory reset, and try enrolling the device again.
In reply to Shweta:
we want to start a new batch of DEP-Devices - so I tried 2 devices and both failed. I already removed the devices from MDM, from DEP and made factory reset and started this process again.
Due to the reason that this process fails, I just want to know wo also has no success - we deployed last year several devices and change nothing - except iOS 13 is the new giant within this game.
In reply to TillLober:
Thank you for your reply.
We have seen the same issue with one or two customers and currently, our Support team is working with them to resolve their issue. The issue seems to be because of the new apple business manager and the few changes in the new iOS 13 which is even detecting blank device as a profile which is linked to another MDM solution.
I'd request you to open a support case here and PM me the case number once it is opened.
In reply to Jasmin:
do you have an updated status for us? We want to rollout our fleet and have to plan these activities.
The case number which you provided me is closed on 22nd January as there was no reply from the person who opened it. Same is happening on the other two cases where customers are not replying, so currently, there is no actual solution available.
I'd request you to send an email on your case to re-open it, so it can be processed further.
we will reopen this issue - but we have no further information to provide - we only want to use this feature which was working up to iOS 12.
I'm a litte bit disapointed regarding the software quality - this is the 2nd major bug which has been investigated by me (took me days to find this out!) and I get a "case closed" feedback from your side. I only contact sohos if there is no possibility for me to solve problems - but the I want to get support from your side.
I understand your concern regarding the issue.
When we see a similar type of issues which could be highlighted to product specialist team, we ask to open a case, so all the needed logs can be documented well in the case and specialist can work with the development team if needed and once it is escalated to them.
The assigned engineer on the case will let you know about the log which is needed in order to escalate the case ahead and will also provide you with the steps to collect those logs.
Configurator 2 Restore Issues with iPad OS 13.1 iOS 13.1 or iPadOS 13.1 device to the Mac to start the update to the newer version. connection through a hub.
In reply to Audrey Nathan:
Hi Audrey Nathan
Are you able to add iOS 13 devices with Apple Configurator 2 successfully?
I can not understand this procedure: every developer with DEP Account and SMC and a device can set up this environment to trace the logs and find out whats going wrong - I have 2 environements and both do not work any more (iOS 12 worked until the day of the iOS 12 Release)
Invest your time and trace the logs with IPCU and Wireshark (if required) - on serverside you can also use a reverse-proxy to get all data.
I certainly understand this but our global escalation team will require certain logs to investigate this for you and hence Jasmin has requested to re-open the case by replying to the last email sent, hence they can troubleshoot this further.
Hi to everybody,
right now it works - we got the error message within the IPCU and ignored this.
You have to reassign the DEP Profile in the Device/DEP-area and then reset the device.
Thank you support-Team!
Glad to know that it works fine for you now.
Thank you for sharing the solution here.