Using and mapping to \\domain.local to sustain connection to data even if DC goes down

Posted on 2008-06-26
Last Modified: 2010-04-21

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!
Question by:Boyderama
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
LVL 13

Accepted Solution

TheCapedPlodder earned 350 total points
ID: 21875813
Create a sub-folder under the Netlogon share (which is actually \sysvol\domain.local\scripts) to contain your tools.  Active Directory already this location and will keep your the folder in sync for you.

Then you can map to \\domain.local\netlogon\subfolder with no issues, and we do this all the time so it does work.


LVL 13

Expert Comment

ID: 21875818
Sorry that should say:

Active Directory already relpicates this location and will keep your the folder in sync for you.
LVL 13

Expert Comment

ID: 21875824
Haha typo-tastic afternoon!

That should have said:

Active Directory already relpicates this location and will keep the folder in sync for you.
Revamp Your Training Process

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action.


Author Comment

ID: 21875979
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:

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?
LVL 26

Assisted Solution

DrDave242 earned 100 total points
ID: 21876596
This should give you some more info on what those folders are for:

It sounds like you've got it working, but FYI, if your servers are running the R2 version of 2003, and especially if you've got a lot of them scattered across different sites, you may want to look into DFS Namespaces (DFS-N) and DFS Replication (DFS-R) for this sort of thing.  DFS-R is much more efficient than the old FRS, which is what is still used for SYSVOL replication (and has to be - don't try to use DFS-R to replicate SYSVOL).

An overview of the R2 DFS is here:
LVL 77

Assisted Solution

by:Rob Williams
Rob Williams earned 50 total points
ID: 21877486
The NETLOGON and Sysvol folders are special folders which do automatically replicate between DC's, assuming hey are properly replicating but mapping is done to a physical machine. Perhaps what you should be looking at is DFS (Distributed File System) which allows you to create a virtual file structure which is replicated between multiple locations. One one is not available the other/s are.
For the record Server 2003 R2 version has improved the replication efficiency.
LVL 77

Expert Comment

by:Rob Williams
ID: 21877506
Sorry DrDave242, i didn't read all of your last post, and didn't mean to duplicate.

Author Closing Comment

ID: 31471019
Thank you all very much. Have split the points as you all helped me out.

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here's a look at newsworthy articles and community happenings during the last month.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

690 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question