Boyderama
asked on
Using and mapping to \\domain.local to sustain connection to data even if DC goes down
Hello!
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!
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!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Haha typo-tastic afternoon!
That should have said:
Active Directory already relpicates this location and will keep the folder in sync for you.
That should have said:
Active Directory already relpicates this location and will keep the folder in sync for you.
ASKER
Thank you for such a rapid response. I understood you but thanks for correcting yourself...twice lol.
I've done as you've said and mapping works a treat. I'll start altering my login script code to use this path as it will ensure to keep on working even if one DC fails.
Being inquisitive I took a look at where that folder is stored on the DC's and also saw the following folders:
domain
staging
staging areas
sysvol <---- Shared as SYSVOL and contained within is a folder called 'Scripts' which is shared as 'NETLOGON'.
Where could I find more info as to what the additional folders are for?
Also, is there any way to create an additional folder within the \\domain.local share or is it hard coded to only show two shared system folders?
I've done as you've said and mapping works a treat. I'll start altering my login script code to use this path as it will ensure to keep on working even if one DC fails.
Being inquisitive I took a look at where that folder is stored on the DC's and also saw the following folders:
domain
staging
staging areas
sysvol <---- Shared as SYSVOL and contained within is a folder called 'Scripts' which is shared as 'NETLOGON'.
Where could I find more info as to what the additional folders are for?
Also, is there any way to create an additional folder within the \\domain.local share or is it hard coded to only show two shared system folders?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry DrDave242, i didn't read all of your last post, and didn't mean to duplicate.
ASKER
Thank you all very much. Have split the points as you all helped me out.
Active Directory already relpicates this location and will keep your the folder in sync for you.