Dagwood
Thu Jun 26 15:49:35 PDT 2008
Excellent answers all...
My main concern was that before when the sbs went down, users couldn't
login.
When performing the steps in the kb article, I never got the
notification that the sbs had successfully gotten "GC"ed...
upon looking further, it looks like I have dns / file replication
problems on the other server, which might have been the problem all
along.
So now I have to fix those issues before I can even finish installing
the sbs.
Thanks everyone.
On Thu, 26 Jun 2008 10:56:12 -0600, "Cliff Galiher"
<cgaliher@gmail.com> wrote:
>Inline...
>
>"Dagwood Bumstead" <dbumstead@jcdithers.com> wrote in message
>news:il876455c3sdvf4e5q3ri6ia8712bo4jqn@4ax.com...
>> Okay, but if the sbs goes down, how does another computer get on the
>> network?
>Authenticating computers is a combination of Active Directory (which your
>second Win2k3 server can keep a copy of if it is a DC) and a global catalog
>server, which again, you can have multiple servers. So, assuming your AD
>structure is intact and set up, the machines will check in with any
>available DC.
>
>> Exactly WHY does SBS have to have DHCP?
>DHCP is more than just a protocol to assign IP addresses. There are various
>parts of the protocol called "options" that are also set. For example, it
>is common for DHCP to assign DNS, as you probably already know. No big
>deal. But DHCP can also assign other options, like PXE, or NTP. NTP is a
>good example because most routers DON'T set this, or, if they do, they use
>themselves as the time server. But since windows uses kerberos for
>authentication and kerberos has built-in protections against replay via
>time-skew, the NTP server *should* be the windows server. This gets
>assigned with windows' DHCP server, but a router won't...and usually SOHO
>routers don't give you access to advanced DHCP options.
>
>Don't get me wrong, if you can replicate *EVERY* setting and option on a
>third-party DHCP server then SBS doesn't care. But most people either can't
>or don't...and those missing options can cause odd, unpredictable, and
>difficult-to-track problems in a network. Since SBS is usually installed in
>smaller environments with limited IT resources, it is best to let SBS do its
>thing and free the IT staff (contract, power user, whatever) to work on more
>urgent matters.
>
>
>> When you say transfer ALL 4 roles, I assume that's covered by the kb
>> article, right?
>Yes.
>
>-Cliff
>
>
>
>
>> On Thu, 26 Jun 2008 07:05:20 -0600, "Cliff Galiher"
>> <cgaliher@gmail.com> wrote:
>>
>>>You have to transfer ALL four FMSO roles to SBS. That is a requirement.
>>>
>>>SBS has to be a GC as well. Active Directory does allow multiple global
>>>catalog servers though, so you do *not* need to disable it on the other
>>>server. Should cover everything.
>>>
>>>Oh, as far as other things you should do? Work on transferring DHCP to
>>>SBS.
>>>;)
>>>
>>>-Cliff
>>>
>>>"Dagwood Bumstead" <dbumstead@jcdithers.com> wrote in message
>>>news:im3764plmokvc63ora7sk4qca6s8t7vfsp@4ax.com...
>>>>I am adding a SBS2003 server to an existing network.
>>>>
>>>> I have and will follow
http://support.microsoft.com/kb/884453
>>>>
>>>> I had an SBS on this network once before (it was at one point, the
>>>> only AD)... but after another server (Server 2003 - NOT an SBS) was
>>>> added a problem occurred where users couldn't connect to the network
>>>> unless the SBS server was up. I had set the Server2003 was AD/GC
>>>>
>>>> I need to make sure that users can login and access the other server,
>>>> even if for some reason the SBS becomes unavailable.
>>>>
>>>> DHCP is on the router (I know, I know...)
>>>>
>>>> I'll continue to run DNS on both servers.
>>>>
>>>> Do I _have_ to disable the GC on the Server2003?
>>>>
>>>> Is there anything else I should do?
>>>>
>>>> FWIW, the reason is that the primary focus of the SBS is the 40
>>>> hour/week back office, whereas the Server2003 supports the 7day/18hour
>>>> retail side.
>>>>
>>>> Thanks,
>>>>
>>>> Dagwood