Question : Windows 2003 SBS Shuts down automatically because of Microsoft EULA

 I have identified the problem that Windows 2003 SBS Shuts down automatically because of Microsofts's EULA. The service SBCore shuts down the server every 90 minutes because it says its not the primary domain controller (read in the event log).

 Here is the server set up.

 "Server 1" - Microsoft 2003 Server SE Installed in March 2004, Has Exchange 2003 and acts primarily as the Mail Server for the company, until the new server was introduced this acted as the File Server, the Active Directory, and Domain controller. All User Accounts are created on this server to set up the e-mail account. Runs DynSite to attach the domain to the ip address (DynDns.org), With MailHop (E-mail forwarding service).
 4 Work Stations - 2x Windows Xp Pro - 2x Windows Xp Home
 "Server 2" - Microsoft 2003 Server SBS Installed in November 2004 primarily acts as the File Server, Shuts down because it does not comply with Microsofts EULA. Holds all roles.

 Both servers have Active Directory running on one domain, they are both Domain Controllers.

 This is what I did so far.

 First I tried reinstalling the server but then canceled haflway through realizing that I probabally didn't need to do it. I then set all the roles to Server 2 and about 20 hours later it shut down.

Any help is appreciated.

Answer : Windows 2003 SBS Shuts down automatically because of Microsoft EULA

You are going to have to migrate all the data somewhere.
Both machines ideally need to be wiped. While you can do workarounds - these aren't to be recommended.

The SBS machine will have to be wiped and started again.
Exchange will run quite happily on SBS. That is what SBS is designed to do. It is one of the main reasons that people purchase it - it allows them to get Exchange and Windows 2003 for a good price.

The number of times that I have seen someone using a server as a workstation just makes my mind boggle. When you can get a workstation from Dell for silly money (check their Outlet store for even cheaper machines) that probably have more horsepower than the server.
Server will put most of its resources towards being a server - whereas a workstation can do what it is designed to do.

So..

A number of recommendations:

1. Buy a cheap workstation so that the boss can have his own machine. Even cheap ones can be a P4 2.8 with 512mb RAM.
2. Which ever of the two machines has the most processing power and memory needs to be the SBS machine. All data on it needs to be migrated out. Anywhere will do.
You may also want to investigate memory upgrades for this machine. If it only has 512mb or 1gb and you are going to get everything on this machine, then put it up to 2gb and it will not wheeze as much.
3. That machine then needs to be wiped and reinstalled with SBS - using the new media kit. Updates and upgrades to the OS and apps (Exchange 2003 SP1 for example). New domain etc etc.
You may even want to consider Software Update Services, a purchased SSL certificate for OWA etc - all the things that can be done very easily for no or little cost that make management of the new server and domain much easier.
4. The other server needs to be wiped and put in to the new SBS domain.
All data moved back.
5. All workstations put in to the new domain, profiles and data migrated.

There are lots of holes in that list - heck I am not doing all of your job for you - which include migrating Exchange mailbox data, the exact order that it is done and which server does what. However it should give you a clear idea of what needs doing. Basically the entire environment needs to be redone.

You might also suggest having the two Windows XP Home machines upgraded to pro so that they can take a full part in the domain.

Simon.