�GetWindowsDirectory� API returns on TS in application mode the \windows folder which points to a network share when a TS Home folder is set in users AD properties.
�
Workaround for non-TS aware applications - depending on application behavior - might be to set a Flags value: "Do not substitute user Windows directory": 0x00000400 as per KB186498
�
If an application uses the GetWindowsDirectory API to query the Windows directory path, Terminal Server returns the user's home directory.
For more information see the following Microsoft Knowledge base article:
186498� Terminal Server application integration information
http://support.microsoft.com/default.aspx?scid=kb;EN-US;186498�
�
Search order on process startup is:
� The directory from which the application loaded.
���������������
Note The current working folder is typically the user's home folder.
� The current directory.
� The system directory.
� The 16-bit system directory.
� The Windows directory.
Note GetWindowsDirectory function used to get the path of this directory.
� The directories that are listed in the PATH environment variable.
For more information about the search order process at start up see the following Microsoft Knowledge base article:
306850� Programs start slowly or slow logon if the network connection to your home folder is slow
http://support.microsoft.com/default.aspx?scid=kb;EN-US;306850�