Monday, March 28, 2011
I've found this article by Jeremy at http://www.jeremycole.com/blog/2008/06/24/how-to-stop-the-sbcore-service-service-or-how-to-use-sbs2003-as-a-normal-server/
Most of this info was found here: http://forums.speedguide.net/showthread.php?t=173731
Note: Removing this service apparently violates the license agreement for Microsoft Small Business Server. See the details here if you care.
Tools you'll need – Process Explorer from www.sysInternals.com
As you probably know, you have a service called "SBCore Service", 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 regedt32.exe and find:
Right click this, choose Permissions and give the "Administrators" group on the local machine full access (don't forget to replace permissions on child nodes).
Press F5 in regedt32 to refresh, 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 sets the service to the "Disabled" state as far as the MMC services snap-in (and windows for that matter) is concerned.
In the original instructions, the author left the service as Disabled and just denied access to the executable:
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.
I decided that I wanted the service gone completely, so (after exporting it), I just deleted the registry key while in regedt32.
After rebooting, I verified that the service was indeed gone from the list of services in MMC, and there was no sbscrexe.exe process running. Then I moved the file sbscrexe.exe from C:\windows\system32 into a tidy little folder along with my exported registry key to keep for future evaluation. Something like a disgusting little bug under glass.
Tuesday, March 15, 2011
I've found this document that explains how to install Terminal Services in application mode on a Windows Small Business Server (SBS) 2003: http://www.bagsolutions.orconhosting.net.nz/
Before you start you have to had finished the small business server setup!!!!
This will show you how to do what M$ said you could in the pre release versions of SBS 2003 but can't in the final release. This does not crack nor get you to edit any of Microsoft's code. It just does what the install would have done. We have tested this as much as we could we cannot guarantee that it will work or be held liable for any errors, unforeseen or otherwise, that might occur.
Enjoy ;) Bob And Ge 26 Nov 2003
WARNING - People have Reported Problems with MMC after doing this. We found that it worked O.k. with only one console (window) open at a time.
Comments and Queries can be directed to BAG_Solutions@hotmail.com, but we aren't able to spend much time on this issue, so you might not get a reply.
- Run the Following Command: (all on one line)
%systemroot%\system32\rundll32.exe setupapi,InstallHinfSection TerminalServices.AppServer.x86 128 %systemroot%\inf\tsoc.inf
- Reboot Computer after executing above command it will not show any sign that it has been completed
- OPTIONAL: Reinstall Administration Tools from %systemroot%\system32\adminpak.msi - You only need to do this if you have problems with MMC. This won't fix the problem with multiple consoles not working, but can restore completely dead ones.
- Set Permissions For Users In Local Security Policy, to allow logon through Terminal Services.
- Turn On Tick Allow users to connect remotely to your computer in System Properties / Remote
- Add Everyone Group To Permissions:
- Reboot to finish installation
Wednesday, March 9, 2011