Article ID: 236813 - View products that this article applies to.
This article was previously published under Q236813
You can use Microsoft Distributed File System (DFS) to map drives directly to folders and subfolders in a DFS share. If your home folder is on a DFS share, the %HOMEDRIVE% variable is mapped only to the DFS root and not to the complete path. This behavior is evident when you view the folder in Windows NT Explorer. In addition, the %HOMEPATH% and %HOMESHARE% variables are not resolved correctly.
For example, if DFS_root is the DFS root on the \\Pkdfs share and your home folder is \\Pkdfs\Dfs_root\Home\User1:
%HOMEDRIVE% (for example, drive Z) is mapped to \\Pkdfs\Dfs_rootInstead, %HOMEDRIVE%%HOMESHARE% should resolve to \\Pkdfs\Dfs_root\Home\User1, %HOMEPATH% should resolve to \, and %HOMEDRIVE% (Z:) should map to \\Pkdfs\Dfs_root\Home\User1.
%HOMESHARE% resolves to \\Pkdfs\Dfs_root
%HOMEPATH% resolves to \Home\User1.
Windows NTTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
Windows 2000By default, Windows 2000 maps the %HOMEDRIVE% variable to your home folder, even if it is on a non-DFS share. In this case, the %HOMEDRIVE% variable is mapped to the \\Pkdfs\Dfs_root\Home\User1 share and the %HOMEPATH% variable resolves to \.
Windows 2000 supports deep share implementation. You can use this feature to directly map to folders in a share if you have appropriate permissions. If your home folder is \\server\share\dir\dir2\%username% (where share is a non-DFS share), your %HOMEDRIVE% variable is mapped to \\server\share\dir1\dir2\%USERNAME% and the %HOMEPATH% variable resolves to \ by default.
You can use the Group Policy Object (GPO) of Active Directory to turn off the deep share feature for the home folder (and keep the behavior the same as Windows NT 4.0). To do this, follow these steps:
For a Windows 2000 Server in an NT 4.0 Domain, to open this policy, do the following:
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Article ID: 236813 - Last Review: May 29, 2012 - Revision: 4.0