My company is utilizing Kix scripts in our login scripts to map drives and it has been working fine. We have started to implement DFS namespace and had a strange issue that started when we began to test.

The script that we are using:

 Code:
;Special logic for DFS-n implementation added by Minnie Mouse - April 2022
If exist("\\$NTDataServer\Data01")
   MapDrive("N:", $NTDataServer, "Data01")
   ;MapDrive("N:", $NTDataServer, "Data02")
   MapDrive("R:", domain.net\Global\stuff, "Stuff")
   ;MapDrive("V:", server.ab.domain.com, "Read")
   ;Future usage to delete the H: mapped drive that it's useful for $NTDataServer - But it's NOT a Home Folder
   ;Use H: /Delete /Persistent
   Return
Endif


the DFS namespace that works: \\Domain.net\AMER\site\Data01

The DFS namespace that does not work:\\Domain.net\AMER\US\site\Data01

all that we did was to move the site from under US and placed it under AMER and things started to work.

The $NTDataServer variable is picked up from the users profile home folder information.

I am no programmer and at the end of my knowledge.

Edited by Mart (2022-04-19 10:55 AM)
Edit Reason: Please use code tags when posting code.