Using and mapping to \\domain.local to sustain connection to data even if DC goes down
Posted on 2008-06-26
We have two DC's (DC1 & DC2) running Windows 2003.
Upon login to a workstation (running either XP or Vista) the login script uses several tools which are stored in a shared folder on DC1. If DC1, however, is off-line the login script cannot use these tools and various functions fail. I am going to improve the code within the login script to handle the situation better but wondered if I could use the following method.
Rather than access files from DC1 by using "\\DC1\System" is there any problem using "\\domain.local\System"?
I thinking that by using the domain path which ever DC is 'online' will handle the request?
When browsing to \\domain.local I see two folders 'Netlogon' and 'Sysvol'. I'd assume I could add an additional folder but where would I store it and then share it? And how would I set the replication to the other DC?
I'm effectively trying to keep data in sync between the DC's and avaliable to workstations should either DC go offline.
And lastly....I used to map the R: drive to \\DC1\System but I've changed this to map R: to \\domain.local\netlogon. Has anyone done this?
Sorry for all the questions :) Thanks!