Hey Matt, big thanks for the quick fix!
Now on the duplication issue, this turn up to be really weird. So I'll go into more details bellow and maybe we make some sense out of what I see.
The way this happens is that I added the source just once (the symlink) and the files appeared twice. This didn't make any sense.
So I set up a test library and imported just the symlink folder, say D:\Media\!Audio\. D:\Media is a real folder. '!Audio' is a simlink to \\Source\e\!Audio
And to my surprise I could not replicate the issue. The files imported just once, with the resolved path (on my .144 build). What the heck? So then I went and mirrored more of my Main library import paths. So here's how this looks:
D:\Media\!Audio (!Audio symlink to \\Source\e\!Audio; network location on my server)
D:\Media\Movies\ (many other symlink subfolders in here)
D:\Media\Series\ (many other symlink subfolders in here)
D:\Media\Music Videos (Music Videos symlink to \\Source\p\!MusicVideos; network location on my server)
So the green folders are symlinks, the rest are real. With a scheme like that the music files in D:\Media\!Audio are imported twice, even on the test library.
So I guess my question is: when the 'root' point (here D:\Media\) containes both real folders and symlinks, is there something that confuses the import mechanism to import the symlinks twice, as-is and resolved?
Many thanks for all the help.