Assume that an Apple iOS device is configured by using the over-the-air enrollment process. Also assume that an Apple certificate for the IOS device is expired. In this situation, you receive an error message that resembles the following:
Profile Installation Failed the server certificate for federation server name/otaprofile/profile?operation=enroll is invalid.
About this update
This update introduces a new Boolean setting for the Apple certificate expiry check during the over-the-air enrollment. This Boolean setting enables the Device Registration Service (DRS) on a federation server that is running Windows Server 2012 R2 to exempt the validity dates of certificates for Apple iOS devices. By default, after you install the update, the DRS exempts the Apple certificate expiry check. If these certificates are renewed by Apple and should no longer be expired, we recommend as a best practice that you enable the expiry check. To configure the DRS to stop exempting the Apple certificate expiry check, follow these steps:
- On the server that runs the DRS, locate the Microsoft.DeviceRegistration.ServiceHost.exe.config XML file in the %systemroot%\ADFS folder.
- Edit the file to add the CertificateExpiryExemptForiOSProfileService registry entry and the value of false inside the appSettings element as follows:<appSettings><add key="CertificateExpiryExemptForiOSProfileService" value="false"/></appSettings>
- Restart the DRS service.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must first install the update 2919355 on Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update: April 2014
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
To resolve this issue, install update rollup 2967917. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2967917 July 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the over-the-air enrollment, go to the following Apple website: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates