Win2k3 SBS as secondary domain controller?

Question

Active Directory

There is an organization with an existing domain on a full-fledged server. I needed a secondary server, and for some reason unknown to me, Win2k3 SBS was purchased for it. And here a problem arises - SBS wants to be a domain controller. A technical and licensing question arises: can it be used as a replica of a domain?
Poke your nose please, is it possible to upgrade 2k3 SBS to 2k8 SBS? Need to buy a license?

Answer 1

Probably this link will help you with a question about a domain controller,
but this link with a question about migration
From myself I will add:
- I would not put SBS as a second domain controller next to a regular server. I won't tell you why. I prophesy bad consequences and a rake.
- To upgrade to 2008, you need to buy a new license. As far as I know, there are no versions “cheaper for upgrading server OSes”.

Answer 2

I had a similar situation. Turning off 100% is due precisely to the fact that SBS must be (under license) a domain controller. The main and only. Moreover, he will constantly check the DNS for the fact that the weight of his address was less than that set by hand.
I couldn’t immediately google the solution, but last time it was solved by disabling some system process and capturing the owner of a certain registry branch, blocking access to the system key. After that, he began to work as a secondary one and we migrated normally from him to 2k8.
You can again convert from 2k3 sbs to non-sbs, provided that it is not R2. R2 was no longer possible, it was necessary to rearrange it.