Nota: Este artigo foi publicado originalmente em 2006 and has been comprehensively expanded. Windows Small Business Server 2003 reached end of life in 2015 and is no longer supported. This guide serves as a reference for environments still running SBS 2003 and provides migration guidance to modern platforms.
Windows Small Business Server 2003 (SBS 2003) was Microsoft’s all-in-one server solution designed for businesses with 75 or fewer users. It bundled multiple server products into a single, integrated package at a significant discount compared to purchasing each product separately. Despite being long out of support, SBS 2003 remains in use in some legacy environments. This guide covers its architecture, common configuration tasks, essential tools, troubleshooting techniques, and the critical topic of migrating to modern solutions.
SBS 2003 Architecture Visão Geral
SBS 2003 is built on Windows Server 2003 and integrates several Microsoft server products into a unified management experience.
Bundled Components
| Component | Standard Edition | Premium Edition |
|---|---|---|
| Windows Server 2003 | Yes | Yes |
| Exchange Server 2003 | Yes | Yes |
| Windows SharePoint Services 2.0 | Yes | Yes |
| Shared Fax Service | Yes | Yes |
| Remote Web Workplace (RWW) | Yes | Yes |
| VPN (RRAS) | Yes | Yes |
| SQL Server 2000 / 2005 | No | Yes |
| ISA Server 2004 | No | Yes |
Key Architecture Constraints
SBS 2003 has several important limitations that differentiate it from standard Windows Server:
- Single domain controller: SBS must be the root of a new Active Directory forest and must hold all FSMO roles
- Single server: Only one SBS server is permitted per domain (you can add standard member servers)
- User limit: Licensed for a maximum of 75 Client Access Licenses (CALs)
- Cannot be a child domain: SBS must be the forest root
- No Datacenter or Enterprise features: Limited to Standard-level functionality
- Combined roles: All services run on a single server (domain controller, Exchange, SharePoint, etc.)
Default Folder Structure
C:\
+-- WINDOWS\ # Windows Server 2003 OS files
+-- Program Files\
| +-- Microsoft SQL Server\ # SQL Server (Premium)
| +-- Exchsrvr\ # Exchange Server 2003
| +-- Microsoft ISA Server\ # ISA Server (Premium)
| +-- Microsoft Windows Small Business Server\
| +-- Networking\
| +-- ClientSetup\ # Client deployment files
| +-- Monitoring\
+-- INETPUB\ # IIS web root
+-- ClientApps\ # Client application deployment share
+-- Users\ # Redirected user folders
+-- Companyweb\ # SharePoint content
Common Configuração Tasks
Initial Server Setup
After installing SBS 2003, the To Do List wizard guides you through essential configuration:
- Network configuration: Set static IP, configure DNS
- Internet connection: Configure the Internet connection and firewall settings
- Remote access: Set up VPN and Remote Web Workplace
- Add users: Create user accounts with the Add User Wizard
- Add computers: Join client machines to the domain
- Configure backup: Set up the built-in NTBackup schedule
- Configure monitoring: Set up server performance and health reports
- Activate server: Complete Windows and SBS activation
Configuring Exchange Server 2003
Exchange is pre-installed but requires configuration:
# Exchange Management tasks:
1. Server Management Console > Advanced Management > Exchange
2. Configure SMTP virtual server for internet mail delivery
3. Set up POP3/IMAP if needed for client access
4. Configure message size limits
5. Set up mailbox size quotas
6. Configure Outlook Web Access (OWA)
Key Exchange settings to configure:
| Setting | Location | Recommendation |
|---|---|---|
| SMTP Connector | Exchange System Manager > Connectors | Configure for internet mail delivery |
| Message Size Limit | Global Settings > Message Delivery | Set to organizational policy (default 10 MB) |
| Mailbox Quotas | Mailbox Store Properties > Limits | Issue warning at 200 MB, prohibit send at 250 MB |
| OWA | HTTP Virtual Server properties | Enable Forms-Based Authentication |
| Anti-spam | Global Settings > Message Delivery > Connection Filtering | Configure RBL lists |
Configuring Remote Web Workplace (RWW)
Remote Web Workplace provides browser-based remote access:
- Open Server Management > Internet and E-mail
- Click Configure Remote Web Workplace
- Set the external URL (typically
https://remote.yourdomain.com) - Configure the SSL certificate (self-signed or from a CA)
- Set up port forwarding on your router (port 443 or 4125 to the SBS server)
Configuring Internet Information Services (IIS)
SBS 2003 runs IIS 6.0 with multiple web sites:
| Site | Port | Purpose |
|---|---|---|
| Default Web Site | 80 | Redirects to RWW |
| SharePoint (companyweb) | 80 (host header) | Internal SharePoint |
| Exchange OWA | 443 | Outlook Web Access |
| Remote Web Workplace | 4125 | Remote access portal |
Configuring the SBS Firewall
If using SBS Premium with ISA Server 2004:
- Open ISA Server Management
- Review the default SBS firewall policy
- Configure publishing rules for Exchange (OWA, ActiveSync, RPC/HTTP)
- Set up VPN client access
- Configure web proxy settings for client internet access
Without ISA Server (Standard Edition), use the built-in Windows Firewall:
# Open required ports in Windows Firewall
netsh firewall add portopening TCP 25 "SMTP"
netsh firewall add portopening TCP 443 "HTTPS"
netsh firewall add portopening TCP 4125 "RWW"
Essential Tools and Utilities
Built-In SBS Tools
| Tool | Access | Purpose |
|---|---|---|
| Server Management Console | Start > Administrative Tools | Central management for all SBS components |
| SBS To Do List | Auto-launches on first login | Guided initial configuration |
| Add User Wizard | Server Management > Users | Creates AD account, mailbox, SharePoint access in one step |
| Internet Connection Wizard | Server Management > Internet and E-mail | Configures internet and firewall |
| Monitoring and Reporting | Server Management > Monitoring | Server health reports and alerts |
| Backup Configuração | Server Management > Backup | NTBackup scheduling |
Third-Party Tools for SBS 2003
| Tool | Purpose |
|---|---|
| SBS Melhores Práticas Analyzer (BPA) | Scans SBS for configuration issues |
| Exchange Melhores Práticas Analyzer | Scans Exchange for problems |
| dcdiag | Active Directory domain controller diagnostics |
| netdiag | Network connectivity diagnostics |
| ExMerge | Export/import Exchange mailboxes |
| ADMT | Active Directory Migration Tool for domain migrations |
Key Command-Line Utilities
# Active Directory diagnostics
dcdiag /v /c /d /e
# DNS diagnostics
dcdiag /test:DNS /v
# Replication diagnostics
repadmin /showrepl
# Exchange mailbox statistics
# (Run in Exchange Management Shell or install Exchange tools)
# In Exchange System Manager: right-click Mailbox Store > Properties > Logons
# Group Policy update
gpupdate /force
# Check SBS license status
# Server Management > Server Computers > right-click server > SBS Properties
# Network diagnostics
netdiag /v
# Verify FSMO role holders
netdom query fsmo
# Check DNS configuration
nslookup
> set type=any
> _ldap._tcp.dc._msdcs.yourdomain.local
Problemas Comuns and Solução de Problemas
Exchange Not Sending External Email
- Verify SMTP Connector exists in Exchange System Manager > Connectors
- Check DNS: the server must resolve external MX records
- Verify port 25 is open outbound on the firewall/router
- Check if your ISP blocks port 25 (common for residential and some business connections)
- Verify the server is not on email blacklists (check with MXToolbox)
- Review the SMTP queue: Exchange System Manager > Queues
SharePoint (Companyweb) Not Accessible
- Verify the SharePoint site is running:
http://companywebfrom the server - Check IIS: ensure the SharePoint site has the correct host header binding
- Verify DNS: the server’s DNS should resolve
companywebto the server IP - Check application pool: IIS Manager > Application Pools > ensure DefaultAppPool is running
- Reset SharePoint:
stsadm -o extendvs -url http://companyweb -ownerlogin DOMAIN\administrator -owneremail admin@domain.com -databasename STS_Config
Remote Web Workplace Not Working
- Verify the SSL certificate is valid and not expired
- Check port forwarding on the router (port 443 or 4125)
- Test with
https://your-external-ip:4125/remote - Verify the Remote Desktop Web Connection component is installed
- Check IIS: ensure the RWW site is running
- Review the ISA Server publishing rules (if ISA is installed)
Active Directory and Group Policy Issues
# Run the SBS Best Practices Analyzer
# Download from Microsoft and run on the SBS server
# Common AD checks:
dcdiag /v
netdiag /v
gpresult /r
# Reset Group Policy
gpupdate /force /boot
Backup and Disaster Recuperação
Built-In Backup (NTBackup)
SBS 2003 uses NTBackup with a preconfigured backup job:
- Server Management > Backup
- Configure the backup destination (tape, external USB drive, network share)
- Set the schedule (recommended: daily full backup)
- The SBS backup includes:
- System State (AD, registry, boot files)
- Exchange Information Store
- SharePoint databases
- File shares
- IIS metabase
Critical Backup Locations
| Data | Location | Notes |
|---|---|---|
| Active Directory | System State backup | Includes AD database, SYSVOL, registry |
| Exchange mailboxes | Exchange Information Store | C:\Program Files\Exchsrvr\MDBDATA |
| SharePoint content | SQL/WMSDE databases | C:\WINDOWS\SYSMSI\SSEE\MSSQL$SBSMONITORING |
| User files | File shares (varies) | Redirected folders typically under C:\Users\ |
| Group Policy | SYSVOL | C:\WINDOWS\SYSVOL\sysvol\domain\Policies |
| IIS Configuração | IIS Metabase | C:\WINDOWS\system32\inetsrv\MetaBase.xml |
Migration Paths to Modern Soluçãos
Running SBS 2003 in production is a significant security risk. There are several migration paths depending on your organization’s needs.
Option 1: Migrate to Windows Server + Microsoft 365
This is the most common and recommended path for small businesses:
- Email: Migrate Exchange 2003 mailboxes to Microsoft 365 (Exchange Online)
- Use the Microsoft 365 migration tools or a third-party tool like BitTitan MigrationWiz
- Export mailboxes with ExMerge to PST as a fallback
- Active Directory: Set up a new Windows Server 2022/2025 domain controller
- Join the new DC to the existing domain
- Transfer FSMO roles to the new server
- Decommission the SBS server
- File Shares: Move to the new file server or SharePoint Online / OneDrive
- SharePoint: Migrate to SharePoint Online (Microsoft 365)
Option 2: Migrate to Windows Server Essentials
Windows Server Essentials (successor to SBS) provides:
- Simplified dashboard for small business management
- Integration with Microsoft 365
- Client computer backup
- Remote Web Access
- No Exchange Server (use Microsoft 365 for email)
Option 3: Full Cloud Migration
For very small businesses, moving entirely to the cloud eliminates on-premises servers:
- Migrate email to Microsoft 365
- Migrate files to SharePoint Online / OneDrive for Business
- Use Microsoft Entra ID (Azure AD) for identity (no on-premises AD)
- Use Intune for device management
- Decommission all on-premises servers
Migration Checklist
| Passo | Description | Status |
|---|---|---|
| 1 | Inventory all SBS services in use | |
| 2 | Document current configuration (IP, DNS, DHCP, etc.) | |
| 3 | Perform full backup of SBS server | |
| 4 | Set up new server or Microsoft 365 tenant | |
| 5 | Migrate Active Directory (if keeping on-premises AD) | |
| 6 | Migrate Exchange mailboxes | |
| 7 | Migrate file shares | |
| 8 | Migrate SharePoint content | |
| 9 | Update DNS records (MX, autodiscover, etc.) | |
| 10 | Reconfigure client machines | |
| 11 | Test all services | |
| 12 | Decommission SBS server | |
| 13 | Update firewall rules | |
| 14 | Update documentation |
Historical Resources
While many original SBS 2003 resources are no longer available online, the following were historically valuable:
- Microsoft SBS Documentation Team Blog (blogs.msdn.com/sbsdocsteam) — archived content may be available via the Wayback Machine
- SBS MVP blogs by Susan Bradley, Jeff Middleton, and others
- TechNet SBS 2003 documentation — some content preserved in Microsoft’s archive
- SBS 2003 Resource Kit — available as a download from Microsoft’s archive
- “Microsoft Windows Small Business Server 2003 Administrator’s Companion” — published by Microsoft Press
Resumo
Windows Small Business Server 2003 was a powerful all-in-one server solution that bundled Active Directory, Exchange Server, SharePoint, and additional services for small businesses. While it reached end of life in 2015 and should no longer be used in production, many organizations still run it. Understanding its architecture is valuable for planning migrations to modern platforms. The most common migration path is moving email to Microsoft 365, setting up a new Windows Server for Active Directory and file services, and decommissioning the SBS server. Any organization still running SBS 2003 should treat migration as an urgent priority due to the lack of security updates.