cleavage
asked on
Does W2K3 Standard suffer similar problems as W2k3 Small Business Edition regarding shutting down?
A client has w2k3 small business edition but was not ready to convert to a domain. Not being familier with SBE, I tried to configure it as a stand alone server and ran into a problem where the server will shut down every hour after the 7th day of operation. Is this an issue with w2k3 standard? I'd hate to blow away the current box only to have the same issue appear again.
Thanks,
Greg
Thanks,
Greg
ASKER
Actually, it does seem to be a feature. The event log had an error message that clearly stated the server would not run for more than 7 days if it was not made a domain controller. Here's the skinny from Microsoft themselves. I had never heard of this either.
What I really want to know though is can a w2k3 server be brought up as just a stand alone box without having to be a dc so it can be a member of a workgroup.
MS info...................
Windows 2003 Small Business Server Shuts Down Unexpectedly; Events 1001, 1013 and 1014 are Logged
Author: Chad Gross MVP
COMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
Article ID : 555087
Last Review : October 14, 2004
Revision : 1.0
On this Page
SYMPTOMS
CAUSE
RESOLUTION
MORE INFORMATION
SYMPTOMS
A Windows 2003 Small Business Server may shut down unexpectedly if setup was not completed correctly.
You may receive the following errors in the event viewer:
Event ID: 1013
Source: SBCore
Description: "This computer must be configured as a domain controller. To prevent this computer from shutting down in the future, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller."
Event ID: 1014
Source: SBCore
Description: "This computer must be configured as a domain controller. It will be shut down in 60 minutes. To prevent this computer from shutting down, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller."
Event ID: 1014
Source: SBCore
Description: "This computer must be configured as a domain controller. It will be shut down in 30 minutes. To prevent this computer from shutting down, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller."
Event ID: 1001
Source: SBCore
Description: "The server was shut down because it did not comply with the EULA. For more information, contact Microsoft."
CAUSE
This issue can occur if the Windows 2003 Small Business Server integrated setup was not completed. Windows 2003 Small Business Server must be a domain controller and hold all FSMO roles for the domain. In order to facilitate migration from an existing domain, the Small Business Server can function for 7 days after installing without being promoted to a domain controller. After that time, the Small Business Server must be promoted to a domain controller using the integrated setup. If the integrated setup is not completed, the SBCore service will initiate a shut down of the server.
RESOLUTION
To resolve this issue, complete the Windows 2003 Small Business Server integrated setup. To access integrated setup, select "Windows Small Business Server 2003" in the Add/Remove Programs applet in the Control Panel.
MORE INFORMATION
829623 - Default Services That Are Installed in Windows Small Business Server 2003:
http://support.microsoft.com/?kbid=829623
What I really want to know though is can a w2k3 server be brought up as just a stand alone box without having to be a dc so it can be a member of a workgroup.
MS info...................
Windows 2003 Small Business Server Shuts Down Unexpectedly; Events 1001, 1013 and 1014 are Logged
Author: Chad Gross MVP
COMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
Article ID : 555087
Last Review : October 14, 2004
Revision : 1.0
On this Page
SYMPTOMS
CAUSE
RESOLUTION
MORE INFORMATION
SYMPTOMS
A Windows 2003 Small Business Server may shut down unexpectedly if setup was not completed correctly.
You may receive the following errors in the event viewer:
Event ID: 1013
Source: SBCore
Description: "This computer must be configured as a domain controller. To prevent this computer from shutting down in the future, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller."
Event ID: 1014
Source: SBCore
Description: "This computer must be configured as a domain controller. It will be shut down in 60 minutes. To prevent this computer from shutting down, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller."
Event ID: 1014
Source: SBCore
Description: "This computer must be configured as a domain controller. It will be shut down in 30 minutes. To prevent this computer from shutting down, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller."
Event ID: 1001
Source: SBCore
Description: "The server was shut down because it did not comply with the EULA. For more information, contact Microsoft."
CAUSE
This issue can occur if the Windows 2003 Small Business Server integrated setup was not completed. Windows 2003 Small Business Server must be a domain controller and hold all FSMO roles for the domain. In order to facilitate migration from an existing domain, the Small Business Server can function for 7 days after installing without being promoted to a domain controller. After that time, the Small Business Server must be promoted to a domain controller using the integrated setup. If the integrated setup is not completed, the SBCore service will initiate a shut down of the server.
RESOLUTION
To resolve this issue, complete the Windows 2003 Small Business Server integrated setup. To access integrated setup, select "Windows Small Business Server 2003" in the Add/Remove Programs applet in the Control Panel.
MORE INFORMATION
829623 - Default Services That Are Installed in Windows Small Business Server 2003:
http://support.microsoft.com/?kbid=829623
ASKER
As I side note, I understand MS might not want a server to not be part of a domain to recieve connections since people connecting to a share could be bypassing the whole license per seat thing. My worst case scenario is to make a DC so it's not the end of the world, just trying to delay it.
Wow, never seen that before! Good find on the Ms link
It makes sense though, as you've mention Ms just don't want you to use SBS any of functions without it being the DC. Guess that's one of the many hobbling features they've added.
Looks like you're going to have to make it the DC, I can't see any way around it and I'm sure Ms nailed down any back doors to bypass it.
It makes sense though, as you've mention Ms just don't want you to use SBS any of functions without it being the DC. Guess that's one of the many hobbling features they've added.
Looks like you're going to have to make it the DC, I can't see any way around it and I'm sure Ms nailed down any back doors to bypass it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This question (or the answers to it really) put me in a bit of a pickle because What90 was very helpful but LimeSMJ actually answered the question I was asking. After consulting the powers that be at Expert, it seems that LimeSMJ should really be awareded the points. So, that's what will happen here. I do thank you both for helping with my issue.
That's not a feature, the server shouldn't shut itself down
Sounds like there's a problem with the server, and potentially a script or possibly a thermal shutdown option?
What do the event logs says about the shutdowns?