In the last couple of months we did a considerable amount of SBS2003 to SBS2008/SBS2011 migrations.
So far the 21 day limit to finish the migration haven’t been an issue – until now. We were waiting for a 3rd party system supplier to migrate their software to the new server. As this work has been delayed, we ran past the 21 day limit. And that’s where the fun started.
Without going in to any further details, here’s the process how to prevent the SBS2003 from shutting down after 21 days of migration have passed. The basic principle is to disable the SBS Core Service (sbscrexe.exe). The problem is when you just kill it, it will restart itself automatically. To achieve this goal follow the steps below:
So far the 21 day limit to finish the migration haven’t been an issue – until now. We were waiting for a 3rd party system supplier to migrate their software to the new server. As this work has been delayed, we ran past the 21 day limit. And that’s where the fun started.
Without going in to any further details, here’s the process how to prevent the SBS2003 from shutting down after 21 days of migration have passed. The basic principle is to disable the SBS Core Service (sbscrexe.exe). The problem is when you just kill it, it will restart itself automatically. To achieve this goal follow the steps below:
- Download process explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653
- Run Process Explorer and SUSPEND the sbscrexe.exe file.
- Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore
- Right click the key and click permissions. Give the Administrators group full control on both the key and the child nodes.
- Refresh the key so you can see all of the registry settings for sbcore and change the Start DWORD value from 2 to 4 to disable the service.
- Using explorer navigate to the sbscrexe.exe file in the C:\WINDOWS\system32 directory and change permissions on the file to everyone deny.
- Go back to process explorer and kill the sbscrexe.exe process. If it doesn’t start again then you have successfully disabled the file.