Re: New SBS 2003 and domain

Tech-Archive recommends: Fix windows errors by optimizing your registry

picky, picky, picky :-)

You do not seize the roles, you transfer them. Role seizure (to me) is only
necessary where the original holder of the roles is either unavailable
(crashed and burnt) or uncommunicative (probably due to a problem in AD), in
which case you would have had to have had an additional DC in the domain at
some point and now wish to make it 'root of the forest' in the absence of
the original root.

Role transfer in a functioning AD is a minor process, role seizure is
somewhat more complex.

"Frank McCallister SBS MVP" <anonymous> wrote in message
news:ORPYHLDpFHA.3244@xxxxxxxxxxxxxxxxxxxxxxx
> Actually you can do this IF you seize the FSMO roles and make the SBS the
> root of the forest. See SBSMigration.com for some concepts on this. Your
> existing Domain can remain as member servers, and Domain Controllers. If
> this is a Temporary situation for development purpose then this is a bad
> idea!
>
> --
> Frank McCallister SBS MVP
> COMPUMAC
> "Leythos" <void@xxxxxxxxxxx> wrote in message
> news:MPG.1d6eb61be1dbae53989c53@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> In article <uCc5sADpFHA.1412@xxxxxxxxxxxxxxxxxxxx>,
>> dlchase@xxxxxxxxxxxxxxx says...
>>> We are a software development shop and we would like to install a new
>>> server
>>> with SBS 2003 Premium. Can we make it part of our existing Win2k/2003
>>> servers domain when we install it? If so, can someone point me to any
>>> whitepapers or ?? for this. Thank you.
>>
>> SBS is it's own domain and will not install in an existing domain. SBS
>> is a stand alone type setup.
>>
>> --
>>
>> spam999free@xxxxxxxxxx
>> remove 999 in order to email me
>
>


.