I want to reinforce what Leonid has been telling you. The issues you are
having seem, on the basis of the limited information you have provided, to
be the direct result of the FSMO roles being spread across multiple DCs.
You may very well have reasons for such, but if so, then indeed, SBS is the
wrong product for your environment. It is a wonderful solution for organizations
that meet its design criteira, but it is what it is and you cannot make it
So, along with Leonid, and with a lack of information that would indicate
otherwise (such as exceeding the limit of 75 licenses), I suggest you at
least try returning the FSMO roles to the SBS, leaving the other DC's in
your network if you feel the need. (That is a nother discussion, most here
would say there is no need for additional DC's in an SBS network, member
servers, sure, but not DCs).
Once that is done, please let us know any issues you have and we will do
our best to help you with them. But for now, you are in between the badlands
and no mans land, totally unsupported, and hanging by a thread.
How is that for mixing the metaphors? <g>
Please post the resolution to your
issue so others may benefit
Get Your SBS Health Check at www.sbsbpa.com
> On 2/24/2010 4:40 AM, Dave wrote:
> If it's shutting down on its own... let's say... every 100 minutes?
>> The server keeps shutting down and crashing on its own and leaving it
>> in the pool of servers isnt an option, it has to go.
>> Is it possible to run a dcpromo on it and actually demote it?
>> What about using a trasition pack and trying to make it a normal
>> server and demoting it?
>> Something I dont understand is how everybody keeps saying it has to
>> have all the FSMO roles but in my network it only has two, the scema
>> master and domain naming master, the other three are handled by a
>> different dc that is not an SBS Server.
>> I want to get rid of it as a dc but cleanly and I want it to stay as
>> a member server until I can transfer the Sharepoint Services role
>> from it to another server.
>> There must be a way around this, surely not all companies that have
>> used an SBS Server are restricted and can never upgrade systems or
>> demote it.
> Then you are experiencing the effect of this server telling you that
> it must own all FSMO roles. Please transfer the roles back to the SBS
> and see if the "random" shutdowns stop. It is designed to reboot
> itself every 100 minutes if it detects that it's not holding all the
> If you run dcpromo on it and then later promote it back to a DC, you
> will create problems with IIS. I have done that and basically the
> impact is that you need to adjust permissions on C:\Windows\Temp to
> bring certain features back online.
> There is no harm in letting this server keep all these roles if you
> have additional domain controllers. There is also no harm for you to
> keep it alive while you have other global catalog servers available.
> For license compliance, among other things, in order for your SBS CALs
> to be valid, this server must exist on your network.
> The transition pack removes these restrictions, but it will be like
> throwing out the baby with the bathwater. It will also be very
> expensive. My recommendation is to fix the malfunctioning SBS server.