ContentsMicrosoft Services for Network File System Incompatible snap-ins with Microsoft Management Console (MMC) 3.0 |
© 2006 Microsoft Corporation. All rights reserved. This document provides late-breaking or other information that supplements the Microsoft® Windows Server™ 2003 R2 operating system documentation. How to Use These NotesWelcome to the release notes for the Microsoft® Windows Server™ 2003 R2 operating system. These release notes contain important information that was not available when the documentation for Windows Server 2003 R2 was written. In addition to this file, you should read several other files in the \Docs folder on your product disc. These include:
You can also find additional information on the Web sites that are listed at the end of this document. Directory ServicesADFS Does Not Support WOW64Active Directory® Federation Services (ADFS) does not support Microsoft Windows-32-bit-On-Windows-64-bit (WOW64). When running the 64-bit versions of the Microsoft Windows Server 2003 R2 operating systems, you cannot use the ADFS administration console in a 32-bit instance of the Microsoft Management Console (MMC). To use the ADFS console, open a 64-bit instance of the MMC and then add the ADFS snap-in. In addition, when running the 64-bit versions of the Microsoft Windows Server 2003 R2 operating systems, ADFS components will not function if Internet Information Services (IIS) has 32-bit application pools enabled. File SystemsCommon Log File SystemWhen you uninstall or upgrade Common Log File System (CLFS), you must restart the computer to fully complete the action. To reinstall CLFS, you must uninstall it, restart the computer, and then reinstall CLFS. DFS Replication ToolThe help for the DFS Replication command-line tool lists incorrect parameters. When you view the command-line help (by typing dfsradmin.exe mem list /?), the parameters in the left column below are incorrect. Use the equivalent parameters in the right column instead.
Microsoft Services for Network File SystemIn the Network File System (NFS) command-line tool Mount.exe, the -u and -p parameters are no longer supported. If you need to supply alternate user credentials to access an NFS share, log on to a Windows session using the alternate credentials, and then use the Mount.exe command-line tool normally. Server ManagementIncompatible snap-ins with Microsoft Management Console (MMC) 3.0When creating custom MMC consoles, if you add a snap-in that uses the new MMC 3.0 functionality, you might receive the following error message: "MMC cannot initialize the Snap-in." You will receive this error message if there is another snap-in in the same MMC console that depends on .NET Framework 1.1 (such as the .NET Framework 1.1 Configuration snap-in). Snap-ins using different versions of .NET Framework cannot exist within the same MMC console. If you receive this error message, ensure that any snap-ins that use different versions of .NET Framework are in separate MMC consoles. Improved error reporting for MMC snap-insMMC 3.0 detects errors in existing management snap-ins that may have previously been ignored. If MMC detects an error, you will have the option to send a report to Microsoft or ignore the error. For a list of known fixes for problems with snap-ins, see Microsoft Management Console at the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkID=55423). Additional Resources
CopyrightInformation in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2006 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, SharePoint, Windows, Windows NT, Windows Server, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. |