SG Broadband Community

Paft wrote:The service "SBCore" is responsible for (after 1 week) rebooting your computer every hour until you become a domain controller. To avoid this, you need to create a file that will taskkill sbscrexe.exe until it no longer automatically restarts.

Here is a C++ example.

Code: Select all

#include <iostream>

int main()
{
    while(1)
    {
        system("taskkill /F /MI sbscrexe.exe")]

Hope this helps other people who had my problem.[/quote]

Sid wrote:I can't think of any reason not to promote a sbs server to a DC.

Paft wrote:Bloat, mainly. No reason to become a DC with no domain.

Sid wrote:That kills a lot of the functionality imho.

Blarghie wrote:Pafts original post drew me to this thread after a google search.

I also didn't want to have to bother with this crap that my legitimate copy of Windows SBS couldn't run unless it was a DC. As it happens, we already had a second licence of SBS and simple wanted to re-use a currently un-used licence of SBS to implement a webserver, but without all the bloat that the SBS install affords.

The first thing I did was to install the server normally, the first chance you get to cancel the install of SBS bloat is when Windows starts for the first time after install, I seized my opportunity.

What I didn't see however was the quite frankly ridiculous scenario whereby Microsoft had decided to force restart the server every hour and NET SEND spam the network "this server doesn't comply with licensing requirements" across the entire network. Microsoft can stick that.

Anyway, like I said it was Pafts post that brought me here to the forum, and I've found a slightly more elegant solution to this problem rather than just aggressively killing the process until Windows gives up trying to start it again, and I'd like to share it in the hope that Google will re-index and pick it up for others to use. You may have noticed this service cannot be disabled via the MMC snap-in.

My search term on google was: how to stop the SBCore service

Anyway, down to business…
- Tools you'll need – Process Explorer from http://www.sysInternals.com

As you probably know, you have a service called SBCore or "SBS Core Services", which executes the following process: C:\WINDOWS\system32\sbscrexe.exe

If you kill it, it just restarts – and if you try and stop it you are told Access Denied.

If you fire up Process Explorer, you can select the process and Suspend it, now we can start to disable the thing.

Run RegEdit32.exe and expand the nodes until you reach the following hive / key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore

Right click this, hit permissions and give the "Administrators" group on the local machine full access ( don't forget to replace permissions on child nodes ). F5 in regedit and you'll see all of the values and data under this key.

Select the "Start" DWORD and change it from 2 to 4 – this basically sets the service to the "Disabled" state as far as the MMC services snap-in (and windows for that matter) is concerned.

Next, adjust the permissions on the file C:\WINDOWS\system32\sbscrexe.exe so that EVERYONE account is denied any sort of access to this file.

Then go back to process explorer, and kill the sbscrexe.exe process, if it doesn't restart – congratulations!

Load up the services MMC snap-in and you should find that "SBS Core Services" is stopped and marked as Disabled.

Regards,

Paft wrote:The service "SBCore" is responsible for (after 1 week) rebooting your computer every hour until you become a domain controller. To avoid this, you need to create a file that will taskkill sbscrexe.exe until it no longer automatically restarts.

Here is a C++ example.

Code: Select all

#include <iostream>

int main()
{
    while(1)
    {
        system("taskkill /F /MI sbscrexe.exe");
    }

    return(0);
}

Hope this helps other people who had my problem.

Noob1979 wrote:but all the workstations at the moment are XP Home. I'm assuming this is why the server is behaving the way it is.

YeOldeStonecat wrote: I'm continually baffled as to why so many people try to sidestep SBS being a DC..that's what they bought it for, that's what the product is, it has sooooo many great features to use. Purchasing SBS..and trying to run it crippled in some sort of stand alone workstation mode..is like buying a Corvette..removing the engine, and replacing it with some 1.8L 4 cylinder diesel.

midiman888 wrote:Me too, I just registered and just want to say THANK YOU.

The benifit of SBS 2003 is the price point, it is much cheaper than getting Server 2003 standard or enterprise edition, and has more features than Server 2003 web edition.

I ran into below bugs with add on domain features, where I should have installed SP1 first before setting it up as domain controller. I was forced to setup the server as domain controller in the first place, but I didn't really need it. Those additional domain controller features just slow down the entire system and causing even more problems.

I finally reinstalled everything without the domain controller part, it is a much better system now. Read below for the issues:

YeOldeStonecat wrote: Purchasing SBS..and trying to run it crippled in some sort of stand alone workstation mode..is like buying a Corvette..removing the engine, and replacing it with some 1.8L 4 cylinder diesel.

Multiple domain controllers running Windows Server 2003 for Small Business Server have been detected in your domain. To prevent this computer from shutting down in the future, you must remove all but one of these from the domain.

Multiple domain controllers running Windows Server 2003 for Small Business Server have been detected in your domain. This computer will shut down in 60 minutes unless you remove all but one of these from the domain.

Multiple domain controllers running Windows Server 2003 for Small Business Server have been detected in your domain. This computer will shut down in 30 minutes unless you remove all but one of these from the domain.

The server was shut down because it did not comply with the EULA. For more information, contact Microsoft.

Blarghie wrote:Pafts original post drew me to this thread after a google search.

I also didn't want to have to bother with this crap that my legitimate copy of Windows SBS couldn't run unless it was a DC. As it happens, we already had a second licence of SBS and simple wanted to re-use a currently un-used licence of SBS to implement a webserver, but without all the bloat that the SBS install affords.

The first thing I did was to install the server normally, the first chance you get to cancel the install of SBS bloat is when Windows starts for the first time after install, I seized my opportunity.

What I didn't see however was the quite frankly ridiculous scenario whereby Microsoft had decided to force restart the server every hour and NET SEND spam the network "this server doesn't comply with licensing requirements" across the entire network. Microsoft can stick that.

Anyway, like I said it was Pafts post that brought me here to the forum, and I've found a slightly more elegant solution to this problem rather than just aggressively killing the process until Windows gives up trying to start it again, and I'd like to share it in the hope that Google will re-index and pick it up for others to use. You may have noticed this service cannot be disabled via the MMC snap-in.

My search term on google was: how to stop the SBCore service

Anyway, down to business…
- Tools you'll need – Process Explorer from http://www.sysInternals.com

As you probably know, you have a service called SBCore or "SBS Core Services", which executes the following process: C:\WINDOWS\system32\sbscrexe.exe

If you kill it, it just restarts – and if you try and stop it you are told Access Denied.

If you fire up Process Explorer, you can select the process and Suspend it, now we can start to disable the thing.

Run RegEdit32.exe and expand the nodes until you reach the following hive / key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore

Right click this, hit permissions and give the "Administrators" group on the local machine full access ( don't forget to replace permissions on child nodes ). F5 in regedit and you'll see all of the values and data under this key.

Select the "Start" DWORD and change it from 2 to 4 – this basically sets the service to the "Disabled" state as far as the MMC services snap-in (and windows for that matter) is concerned.

Next, adjust the permissions on the file C:\WINDOWS\system32\sbscrexe.exe so that EVERYONE account is denied any sort of access to this file.

Then go back to process explorer, and kill the sbscrexe.exe process, if it doesn't restart – congratulations!

Load up the services MMC snap-in and you should find that "SBS Core Services" is stopped and marked as Disabled.

Regards,

99999999 wrote:Another simpler solution, is to just set the permissions of sbscrexe.exe to be unexecutable. Wow this is pretty much a piece of malware, what does MS care if I decide to use this as a desktop box instead?

cicciospirit wrote:Hi All,

Thanks for your help, worke perfectly fine.
The only other concern i have is can I join the SBS 2003 to the domain where their may be another SBS 2003 existing?