Symptoms
Consider the following scenario:
-
You have a computer that is running Windows Server 2012.
-
The Active Directory Domain Services (AD DS) Best Practices Analyzer contains a rule to identify accounts in which Data Encryption Standard is enabled.
-
You configure a Windows Server 2012-based domain controller.
-
You add an Organizational Unit (OU) to the domain controller.
-
The name of the OU contains some XML escape characters. For example, the name of the OU is "Users & Computers".
-
You create some user accounts or computer objects in the OU.
-
You enable the Use Kerberos DES types for this account setting for the users or computers.
-
You try to run the AD DS Best Practices Analyzer.
In this scenario, the AD DS Best Practices Analyzer fails. Additionally, you receive the following error message:
The Best Practices Analyzer scan has failed.
An error occurred while parsing EntityName. Line <number>, position <number>.
Cause
This issue occurs because characters that should be escaped are interpreted incorrectly as XML markup.
Resolution
This hotfix is also available at Microsoft Update Catalog.
Hotfix information
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 be running Windows Server 2012.
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You do not 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 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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" 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.2.920 0.16 xxx
Windows Server 2012
RTM
GDR
6.2.920 0.20 xxx
Windows Server 2012
RTM
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
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" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Directoryservices.ps1 |
Not applicable |
450,636 |
01-Apr-2013 |
22:07 |
Not applicable |
|
Directoryservices.sch |
Not applicable |
212,346 |
02-Jun-2012 |
14:31 |
Not applicable |
|
Directoryservices.xsd |
Not applicable |
38,940 |
02-Jun-2012 |
14:31 |
Not applicable |
|
Manifest.psd1 |
Not applicable |
298 |
02-Jun-2012 |
14:31 |
Not applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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.
More Information
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
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
|
File name |
Amd64_09af4a19cfdc8639301287543e9ea37a_31bf3856ad364e35_6.2.9200.20678_none_765ba4873d6a6744.manifest |
|
File version |
Not applicable |
|
File size |
713 |
|
Date (UTC) |
02-Apr-2013 |
|
Time (UTC) |
08:29 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-directoryservices-bpa_31bf3856ad364e35_6.2.9200.20678_none_c95866ef03d772d5.manifest |
|
File version |
Not applicable |
|
File size |
5,798 |
|
Date (UTC) |
02-Apr-2013 |
|
Time (UTC) |
01:14 |
|
Platform |
Not applicable |
