Many thanks for the advice. 
I needed this info because we made a mistake by assuming that two Windows 
servers could share an iSCSI target. This seems to be the road to hell, because 
NTFS filesystems don't like multiple clients having access to them. Therefore 
we needed a new solution. 

It seems that windows services can't see the shared drive that is created with 
option 1 nor from option 2. Now we use the direct link inside ( 
\\ComputerName\DriveName ) our windows service and then it works well. 



-----Original Message-----
From: Robert Soubie [mailto:[email protected]] 
Sent: vrijdag 7 september 2012 16:31
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Multiple Windows servers and a OI NAS, how 
to get there

Le 04/09/2012 23:13, Natxo Asenjo a écrit :
> You have, I think, two solutions. The first one is only available for 
> newer windows servers, I think. The second is a nice hack that will 
> probably never be supported if you run into trouble but I have used it 
> and it works :-) 1. use mklink 
> (http://en.wikipedia.org/wiki/NTFS_symbolic_link) to create a 
> symbolink link anywhere on the local drives to the share.
> mklink /d d:\mylink \\server\share You have to create the link on 
> every windows server, obviously. I used the d: drive, use whatever you 
> like/can :-) 2. run net use letter: \\server\share during computer 
> startup (using group policy). This way it will run as windows user 
> SYSTEM and the drive letter will be available to everybody.

Excellent ! So far, in my context (a ZFS home server with multiple non-server 
Win 7 clients), I used solution #2. I now find that solution
#1 brings two advantages, and one disadvantage :

a) When using the Windows Explorer function "copy or move a file or directory 
to some target place", Explorer does not forget any more the last target place 
used.

b) I can now delete from any Windows box the server thumbs.db files that 
Windows Explorer creates. I do not know why those files cannot be deleted, 
Windows users having full control of the SMB share.

c) With solution #1, I lose access to snapshots. However, both solutions seem 
to be compatible, so...

--
Éditions de l'Âge d'Or — Stanley G. Weinbaum http://www.lulu.com/robert_soubie 
http://www.smashwords.com/profile/view/StanleyGWeinbaum

_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss


_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to