Re: Demoting DC or create new file share server?

I always thought you want your DC's doing what they are intended to do...GC,
FSMO roles, DNS, etc. They should not have a ton of shares for users to
access via mapped drives. If I ever need to reboot the server, I will need
to do this during a slow time period. Which in a hospital setting is very
rare. This is one of 2 DC's for a 2 hospital system. Both have file shares
existing for over 600 users. It really isn't a "remote" office but more like
2 hospitals about 25 mi. from each other with DC/file share servers in each
hospital.

"Danny Sanders" wrote:

I have a DC which has home directories and other dept. file shares. This
is
a bad idea in my opinion.

There is nothing "wrong" with this setup. In fact it makes sense if your
trying to cut down on hardware costs of remote offices.



This is the only DC for this location so I would
like to demote the DC and keep the old hardware for the file share server
&
create a new DC on new hardware. Or should I keep the DC (which has all
the
FSMO roles, DNS & WINS) on the existing hardware and create the file share
server on the newer hardware. I do have one other DC in a different
location
over a 100Mb GigE WAN connection. "Old hardware" is about 3-4 years old
and
is a Dell blade server. Not sure if moving the FSMO roles, DNS & WINS
would
be the best/easiest/least risky way to go or not.


I would suggest leaving it alone.

hth
DDS


"Fetzer" <Fetzer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EF968682-8954-4AEF-B056-2609BEC2FB90@xxxxxxxxxxxxxxxx
I have a DC which has home directories and other dept. file shares. This
is
a bad idea in my opinion. This is the only DC for this location so I
would
like to demote the DC and keep the old hardware for the file share server
&
create a new DC on new hardware. Or should I keep the DC (which has all
the
FSMO roles, DNS & WINS) on the existing hardware and create the file share
server on the newer hardware. I do have one other DC in a different
location
over a 100Mb GigE WAN connection. "Old hardware" is about 3-4 years old
and
is a Dell blade server. Not sure if moving the FSMO roles, DNS & WINS
would
be the best/easiest/least risky way to go or not.

Thanks!



.

Relevant Pages

  • Re: Migrate to new server
    ... You have 5 FSMO roles, so you can see that 002 is schema owner and Domain owner and the other roles are at 001. ... I will be migrating the server tomorrow, ... For this tools you have to install the support\tools\suptools.msi ... For DNS make your live easy and use AD integrated zones on the ...
    (microsoft.public.windows.server.dns)
  • Proper rules/procedures for setting up DNS/Default Gateways
    ... I run a small test network behind a hardware firewall ... I recently replaced my 'server' ... Toshiba DOCSIS cable router connected to the WAN side of a Sonicwall SOHO3 ... DG 192.168.1.2 DNS same as above ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant add computers to domain
    ... posts the big picture with some of the little points on how to do this. ... the existing hardware as the 'source' while needing new hardware to create ... > So I use dcpromo to remove ad from the server. ... and follow the instructions again hoping that all the DNS stuff is set up ...
    (microsoft.public.win2000.active_directory)
  • Re: upgrading domain controllers from Server 2000 to Server 2008
    ... just move the FSMO roles. ... Terminal server service licence server) in builtin ... On the old server open DNS management console and check that you ... Install the new machine as a member server in your existing ...
    (microsoft.public.win2000.active_directory)
  • Re: Justification for creating a new Domain
    ... We also have a SQL Server, Application Server, SAN. ... hardware was purchased as a life cycle purchase to replace Dell 2650 servers. ... DNS and AD in the same server? ... That is on top of the the migration of shares that must be done when a server is replaced anyway. ...
    (microsoft.public.windows.server.active_directory)
Loading