Writing program to do this using NetDfsSetClientInfo should be quite easy
thing to do.
Do you also want clients to failover to other targets if your "default"
target is down? In case you don't want any failover, then you can make all
other targets offline using DFSGUI.msc. Then clients will connect only to
"default" target and it WILL NOT failover to any other target. This won't
affect replication.
--
Thanks
Mukul [MSFT]
PS: Please post DFS related queries in newsgroup
microsoft.public.win2000.file_system. Please use "DFS" in subject to make it
immediately noticeable.
PS: Please find latest dfsutil.exe (updated) at
http://www.microsoft.com/downloads/d...displaylang=en
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights
"Erik Verheul" <(E-Mail Removed)> wrote in message
news:2AEAD66E-9866-4470-BD9F-(E-Mail Removed)...
> In my case we are trying to use DFS/FRS as a means for automatic failover.
Users must connect to the 'default' target to prevent the 'last writer wins'
problem. A second reason that users must connect to the same target is that
some files are shared by all users. Setting the Time To Live value very high
helps until a client reboots. Then the client is connected to a randomly
selected target.
>
> If only DFSUTIL.exe supported the feature to set a default target at
startup would be a great help.
>
> As a last resort I consider to program the Windows API using
NetDFSSetClientInfo(). This however is a costly endeavour.
>
> Is there an alternative? We use Windows 2003 Enterprise.
>
> Erik
>
> PS: We tried setting up two sites in the domain. This did not work as the
replication performance dropped dramatically.
Similar Threads
