This article describes an issue that occurs after Active Directory Federation Services (AD FS) certificate rollover is complete, and the original certificate expires in Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Cause

This issue occurs because the AD FS server can have more than one token-signing certificates configured. The Work Folders server reads the set of signing certificates from the AD FS server, but only uses the first certificate on the list to validate token signatures. If the first certificate is not the primary, Work Folders server treats tokens as not signed and rejects them.

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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, submit a request to 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, visit 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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

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 and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" 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.16 xxx

    Windows Server 2012 R2

    RTM

    GDR

    6.3.960 0.17xxx

    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" 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

Ecsserver.mof

Not applicable

3,158

14-Sep-2013

04:45

Not applicable

Ecsserver_uninstall.mof

Not applicable

873

01-Jul-2013

16:50

Not applicable

Syncserversetting.cdxml

Not applicable

2,354

01-Jul-2013

16:50

Not applicable

Syncshare.cdxml

Not applicable

11,597

14-Sep-2013

04:45

Not applicable

Syncshare.psd1

Not applicable

732

30-Jul-2013

18:47

Not applicable

Syncshareres.dll

6.2.9200.16384

2,048

22-Aug-2013

11:44

x64

Syncsharesrv.dll

6.3.9600.17714

1,270,272

26-Feb-2015

02:52

x64

Syncsharesvc.config

Not applicable

6,891

01-Jul-2013

16:50

Not applicable

Syncsharesvc.dll

6.3.9600.17714

418,816

26-Feb-2015

02:52

x64

Syncsharettlib.dll

6.3.9600.17714

96,256

26-Feb-2015

21:34

x86

Syncsharettsvc.exe

6.3.9600.17714

147,456

26-Feb-2015

04:38

x64

Syncuserstatus.cdxml

Not applicable

1,047

01-Jul-2013

16:50

Not applicable

Syncserversetting.cdxml

Not applicable

2,354

01-Jul-2013

16:50

Not applicable

Syncshare.cdxml

Not applicable

11,597

14-Sep-2013

04:45

Not applicable

Syncshare.psd1

Not applicable

732

30-Jul-2013

18:47

Not applicable

Syncuserstatus.cdxml

Not applicable

1,047

01-Jul-2013

16:50

Not applicable

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File property

Value

File name

Amd64_e818fe748732d80d503d6c4ca30547e0_31bf3856ad364e35_6.3.9600.17714_none_b1c077df4e7ad138.manifest

File version

Not applicable

File size

1,080

Date (UTC)

26-Feb-2015

Time (UTC)

21:37

Platform

Not applicable

File name

Amd64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_6.3.9600.17714_none_688ed1524fa89e53.manifest

File version

Not applicable

File size

68,693

Date (UTC)

26-Feb-2015

Time (UTC)

21:37

Platform

Not applicable

File name

Wow64_microsoft-windows-e..seclientsync-server_31bf3856ad364e35_6.3.9600.17714_none_72e37ba48409604e.manifest

File version

Not applicable

File size

46,621

Date (UTC)

26-Feb-2015

Time (UTC)

05:29

Platform

Not applicable

Status

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

References

See the terminology that Microsoft uses to describe software updates.

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!

×