Hello
(E-Mail Removed),
If you have a server with hardware problems that are known, i strongly recommend
to replace it.
If you have an environment with a domain the best practise is to have 2 domain
controllers for redundancy and let them only manage the domain, means DHCP
and DNS and Global catalog, thats all. For data files, home folders and user
profiles use a separate member server with large diskspace and a good backup
planning.
The DNS workload depends on the amount of servers/workstations in your network.
If you have only a single domain without a lot of subdomains or trusts to
other domains, DNS workload will not be so much. So you can also use it as
file store, but think about the basic work of DC's. It will not slow down
the DNS load if user folders/files located there, if your domain is quiet
simple. What will slow down the server is maybe the NIC, the harddisk etc.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Hello Folks,
>
> Let's see how many administrators or techies are using deja\google
> groups....
>
> The company I work for is in need of file\folder reorganization. Home
> folders have yet to be implemented but I'm fighting for this to
> happen.
>
> We have 2 servers acting, along with other roles, as File Servers.:
>
> One of these servers, we'll say is Server1, has bad sectors on it, is
> the new Symantec End Point Manager, participates in AD, and acts as
> the print spooler for all printers in the organization (5).
>
> The other, Server 2, is a DC, contains drive shares for file\folder
> access, DNS role.
>
> Server1 has displayed problems related to SEPM, bad sectors, and
> limited drive space (c:\) for spooling. I'm requesting from our
> Director that I'm allowed to change the Spool path. The problems
> we've been experiencing is shared directories become slow to respond
> and printing stops where a reboot resolves the problem. In my 2
> months of working here I've seen this be the root of most user's
> frustration. Reason: this is where most of their "network" folders
> reside.
>
> I proposed to my Director that we implement home folders and do so on
> Server2. Server 2 has over 150GB available on it. I explained the
> benefits of setting up home folders through AD: users' data will be
> backed up. I also explained the benefits of setting up home folders
> on Server2: no more down time in relation to accessing files.
>
> His response was: 1. He didn't want to take away from the primary
> responsibility of Server2...DNS.
>
> My Question: would home folders or increased read\write slow down DNS
> resolution? Does anyone foresee issues in having home folders setup
> on a DC that is responsible for DNS?
>
> Thanks folks,
>
> Tony
>
Similar Threads
