Article ID: 294312 - View products that this article applies to.
This article was previously published under Q294312
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
This article describes the installable file system (IFS), which provides access to the Microsoft Web Storage System that SharePoint Portal Server uses. By default, IFS is not mounted during the installation of SharePoint Portal Server.
You can use IFS access for the following tasks:
NOTE: Do not use IFS (network drive M) to create SharePoint Portal Server folders or documents, assign security to folders or documents, or edit properties for folders or documents. SharePoint Portal Server roles and configuration options are available when you use the supported Web folders interface. If you manipulate the IFS security attributes, you may interfere with the roles information associated with SharePoint Portal Server, which results in data loss. Workspace management functions, such as creating document profiles, are also available when you use only the Web folders interface. In addition, do not use Microsoft ActiveX Data Objects (ADO) or OLE DB to configure security on SharePoint Portal Server folders or documents.
SharePoint Portal Server Setup uses drive M during Setup and repair operations. The following issues may occur:
How to Mount Drive M Temporarily
How to Mount Drive M PermanentlyWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Contact us for more help