Symptoms

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:

  1. On the server that runs the DRS, locate the Microsoft.DeviceRegistration.ServiceHost.exe.config XML file in the %systemroot%\ADFS folder.

  2. 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>

  3. Restart the DRS service.

Resolution

Hotfix information

A 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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Prerequisites

To 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 information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information notesImportant Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17 xxx

    Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Microsoft.deviceregistration.iosdeviceenrollmentservice.dll

6.3.9600.17133

98,816

22-May-2014

15:43

x86


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

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about the over-the-air enrollment, go to the following Apple website:

General information about the over-the-air enrollment 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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×