Re: What are FSMO roles?
- From: Dagwood Bumstead <dagwood@xxxxxxxxxxxxx>
- Date: Thu, 07 Jul 2005 20:24:46 GMT
This is an old message I was going back over... I don't know if javier
is still around, so anyone, please feel free to answer.
I have now added the new 2K3 server into the SBS2000 domain and
everything is swimmingly fine, but this question is regarding Javier
saying he wouldn't make the new server a DC without a good reason.
There are 11 workstations in the domain that use the SQL Server on the
2003 server and do all their work there. They have no reason (save 1
workstation) to ever hit the SBS2000 server except to authenticate and
get their GPO settings.
The SBS Server is business hours, whereas the 2K3 is on 7-day, 16-hour
production schedule. Requiring the SBS to authenticate in reality puts
in on the same 7x16 schedule.
Isn't this a good enough reason to make the 2K3 a DC? That way if the
SBS server goes down (or the fiber link to it does) the 11
workstations can still authenticate? (DHCP and DNS are non-issues)
Is there some terrible reason I shouldn't dcpromo the 2K3?
On Tue, 8 Mar 2005 16:56:19 -0500, "Javier Gomez [SBS MVP]"
<javier_gomez@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Yeah... thanks NickZ for pointing that out. I totally missed that the OP
>mentioned that it was an SBS2k box. There is no connectcomputer wizard on
>SBS2k, as SG mentioned you can just join the domain manually at any point.
>
>Again, I want to stress out that DCPromo and/or extending the AD schema are
>only necessary if you want to make the 2nd server a DC. Which I wouldn't do
>unless I had a good reason for it.
.
- Follow-Ups:
- Re: What are FSMO roles?
- From: Bill Swan
- Re: What are FSMO roles?
- Prev by Date: Re: POP3 Connector Question?
- Next by Date: Re: WSUS SelfUpdate Issue
- Previous by thread: Creating Port and redirect it in ISA
- Next by thread: Re: What are FSMO roles?
- Index(es):
Relevant Pages
|
Loading