Select the product you need help with
The "Create symbolic links" Group Policy setting is not displayed in GPMC on a Windows Server 2008-based computer or a Windows Vista Service Pack 1-based computerArticle ID: 955857 - View products that this article applies to. On This PageSYMPTOMSIn an Active Directory domain environment, you define the following Group Policy setting on a Group Policy object (GPO): Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Create symbolic links Then, on a Windows Server 2008-based computer or on a Windows Vista Service Pack 1 (SP1)-based computer that has Remote Server Administration Tools (RSAT) installed, you use the Group Policy Management tool (GPMC.MSC) to generate a report of the GPO settings. Note To generate a report of the GPO settings, click the GPO under the "Forest\Domains\Domain\Group Policy Objects" node, and then click the Settings tab in the right pane. In this case, the "Create symbolic links" Group Policy setting does not appear in the report. Also, on the computer where GPMC is running, you run the Group Policy Results wizard for the computers or users to which this Group Policy setting should be applied. Then, when you click the Settings tab, in the "Computer Configuration\Policies\Windows Settings\Security Settings" area, you receive the following error message: An error has occurred while collecting data for Security Configuration Engine (SCE) Extension. RESOLUTIONHotfix informationA 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. 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, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. PrerequisitesTo apply this hotfix, you must have Windows Server 2008 or Windows Vista SP1 installed on the computer.Restart requirementYou may have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationTo use this hotfix, you do not have to make any changes to the registry.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2008 and Windows Vista noteThe MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.For all supported x86-based versions of Windows Server 2008 and Windows VistaCollapse this table
For all supported x64-based versions of Windows Server 2008 and Windows VistaCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor additional information, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesAdditional file information for Windows Server 2008Additional files for all supported x86-based versions of Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008Collapse this table
PropertiesArticle ID: 955857 - Last Review: October 8, 2011 - Revision: 2.0 APPLIES TO
|
Back to the top
