E-Bitz - SBS MVP the Official Blog of the SBS "Diva"

http://www.microsoft.com/downloads/details.aspx?familyid=d9f63c79-6488-4058-bd90-94d46c82cd68

Release Notes for Windows Small Business Server 2003

http://www.microsoft.com/downloads/details.aspx?familyid=022677cc-f5ac-4bfb-9ad0-454e89cb98bb

Troubleshooting Windows Small Business Server 2003

http://www.microsoft.com/downloads/details.aspx?familyid=f74ea7c9-942b-4e33-9708-adcd4c430b9b

Harry Brelsford's SBS 2k3 book is available - AND if you order from his site you can get the pdf within 24 hours

http://www.nethealthmon.com

http://weblogs.asp.net/exchange/archive/2004/03/24/95530.aspx

Take a look at the Exchange team blog for instructions on adding RSS feeds into your Sharepoint!

From a post in the newsgroups....

“Based on my research, this problem could be caused because the SharePoint
Timer Service failed to contact the SharePoint database while the SBS is
rebooting. In SBS 2003, the SharePoint Timer Services is used to send
notifications and performs scheduled tasks of WSS. It needs to access the
SharePoint database when starting. Since the Veritas Backup exec software
is installed on the server box and several backup exec related services
have started during the reboot, these services could cause the SharePoint
database from being mounted in a timely manner, thus, causing the problem
to occur.

I reproduced this problem in my test machine. After the MSSQL$SHAREPOINT
service has stopped, this error message will be logged in the application
log. You may now try to manually start this service to see if the problem
will still occur.

1. Start-->Run-->Type 'services.msc' (without the quotation marks) and
press Enter.

2. In the Services console, stop the 'SharePoint Timer Services'. Check the
status of the 'MSSQL$SHAREPOINT' service, make sure it has been started and
then restart the 'SharePoint Timer Services'. The problem should be
resolved.

If there is no problem with the manually service startup, we can set a
service dependent of the SharePoint Timer Service. Please try the following
steps:

1. Start-->Run-->Type 'Regedit' (without the quotation marks) and press
Enter.

2. In the registry editor, navigate to the following registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

3. Right-click the blank area in the right panel, click
'New'-->'Multi-String Value'.

4. Input the value name 'DependOnService' (without the quotation marks) and
then double-click the newly created value. In the value data area, type
'MSSQL$SHAREPOINT' and click 'OK'.

5. Close the registry editor and reboot the server box.“

Heads up for all SBSers... this KB is something you need to look at and take action.  It talks about a registry key change that needs to be made on all SBS2k3 boxes.  The reg key was entered wrong and you have to delete it out and correct it.  I'll post up some screen shots later on to show you where this reg key is located:

839262 Services may stop abruptly when you shut down or restart a Windows
Small
http://support.microsoft.com/?id=839262

828053 - ISA Server prevents connection to a remote desktop when you connect through Remote Web Workplace on a Windows Small Business Server 2003-based computer:
http://support.microsoft.com/?kbid=828053

838304 - How to publish http://Companyweb to the Internet by using ISA Server 2000 on a server that is running Windows Small Business Server 2003, Premium Edition:
http://support.microsoft.com/?kbid=838304

 Services may stop abruptly when you shut down or restart a Windows Small
Business Server 2003-based computer
http://support.microsoft.com/default.aspx?scid=kb;EN-US;839262

296788 Offline Backup and Restoration Procedures for Exchange
http://support.microsoft.com/?id=296788

I recommend you to make a copy of the old MDBDATA folders. In case 
something goes wrong, you still have an untouch copy.

If the article seems complicated, in a nut shell, here is what you need to 
do.

1. Make a backup of the old MDBDATA folder
2. Stop the Microsoft Exchange Information Store service
3. Delete the files in the mdbdata folder (which contains the new clean 
database)
4. Put back the priv1.edb, priv1.stm, pub1.edb, and pub1.stm
5. Start the Microsoft Exchange Information Store service
6. Open Exchange system Manager, go all the way to the Mailbox Store and 
Public folder store. Right-click each one, database tab. Check the box 
"this database can be overwritten by a restore".
7. Right-click and Mount Store.

If the database is in clean shutdwown state, and you rebuild the server 
with the same server and domain name, the store will mount. Of course, 
there are always other problems that may show up. If you run into the 
problem, post back the errors from the application/system log and see the 
next step.

8. Assuming no problem, then close and reopen the Exchange system manager. 
Expand mailbox store, right click Mailbox, and run Clean up agent. 
Mailboxes on your right should be RedX. Right click each one and Reconnect 
to connect back to a user account. If you don't see the user on the list, 
it means the user already has a clean mailbox. You then need to go to AD 
Users and Computer, right click that user, Exchange Tasks and Delete 
mailbox. Back to Exchange System Manager, run Cleanup agent again, and 
reconnect the mailbox back to the user.

To save time, you should consider calling PSS at 1-800-936-4900 and let us 
to walk you through the steps.