Please clarify

1.  If you or your company is in software development business?  Only normal apps or also enterprise apps?

2.  If the Soti MobiControl instance belong to your company or your customer?

3.  If the Soti MobiControl instance (associated with the APNS certificate currently managed with the Enterprise developer Apple ID)  is only used to test/deploy your company software developed for use by other customer(s) on their own MDM solution(s)?  Or if the instance is also used for day-to-day management of production devices not related to any software development/test tasks?

4.  If there are only a few or a large number of devices currently managed with the Soti MobiControl instance , and if you/your company can afford the cost/time to re-enroll (and possibly factory reset for devices in supervised mode)  ALL such device(s)? 

Irrespective of your answers to the above, the simple fact is that if you have no access to the APNS portal to renew the existing APNS certificate BEFORE it expires, ALL devices currently enrolled and managed by the associated Soti MobiControl instance will become permanently out of control upon such certificate expiration.

In fact, any person/company owning an active MDM server instance can create APNS certificate using any AppleID account of his/her choice.  You should have used a normal personal AppleID  (that may or may not be dedicated solely for APNS certificate management purpose)  to create account for the APNS certificate in the past.

After clarifying your situation based on your answers to my questions, you can decide whether to approach Apple support team to see if there is any way to fix your APNS portal access, or to simply create a new APNS certificate with a new normal AppleID account and then re-enrol ALL devices after reconfiguring the MDM server with the new certficate.

If you eventually take the path to follow up with Apple, please share with us some details on what Apple says and how the issue is resolved.  

Hi Sara Gonzalez,

Thank you for posting on SOTI Pulse, thanks Raymond for responding to the post.

Have you had an opportunity to test the suggestion provided by Raymond? He asked you some questions, and we are currently awaiting your reply.

Based on your situation, it seems that your old Apple Developer Enterprise license has expired, preventing you from pushing an IPA from your previous enterprise account. Consequently, you created a new normal developer account.

It's important to note that both the Apple Developer account types (normal and enterprise) are primarily used for generating in-house IPA files. Now, let's consider two scenarios:

1. If you have an active APNS (Apple Push Notification Service) certificate that was created using your old Apple ID in your SOTI instance, you don't need to take any immediate action. You can continue using your old Apple ID to renew the APNS certificate for your SOTI instance. It's worth mentioning that APNS generation is unrelated to your expired Apple Developer Enterprise license. If you have the information for your old Apple ID, that's great.

2. However, if you are unable to use your current old Apple ID or have forgotten it, there will not be any immediate issues as long as your current APNS certificate remains active. The problem will arise when it expires, at which point you will need to create a NEW APNS certificate using your new Apple ID.

However, please keep in mind that generating a new APNS certificate will result in all previous devices that were configured with the old APNS becoming offline. In order to regain connectivity, these devices will require re-enrollment (and potentially a factory reset for devices in supervised mode).

To proceed with configuring SOTI on the new Apple Developer ID, you will need to follow these steps:

1. Generate a new APNS certificate on the new Apple Developer account. This involves creating a Certificate Signing Request (CSR) from SOTI Mobicontrol and using it to obtain the APNS certificate from Apple.

2. Once you have the new APNS certificate, you will need to import it into the SOTI Mobicontrol console. This ensures that SOTI can communicate with your iOS devices for application management and other functionalities.

3. Update any necessary configurations within SOTI Mobicontrol to reflect the new Apple Developer ID. This may involve updating the account information and any associated settings that reference the old Apple Enterprise ID.

By completing these steps, you should be able to configure SOTI Mobicontrol with the new Apple Developer ID and continue submitting applications using the normal Apple Developer program.

It's important to note that the specific steps may vary slightly depending on the version of SOTI Mobicontrol you are using, and any updates or changes made by Apple. Therefore, I recommend referring to the official documentation and contacting SOTI support for detailed guidance and assistance with the configuration process.

Kind regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |