hongedit
asked on
SBS 2003 BPA results - sanity check please
Hi all
I am about to migrate my client from a very much overloaded SBS2003 server to multiple Server 2008 R2 + Exchange 2010 solution.
After running BPA, can someone please verify what is really crucial to fix, and/or what can be safely ignored?
Please note that there are no current known issues.
Critical
Task Offloading is enabled
Warnings
Free disk space is low
NIC Driver file is more than 1 year old
/Exchange-oma local path does not match /Exchange
CEICW has not been run
Change the functional level of Exchange Server 2003
Companyweb Filter Names is not at default value
EDNS is enabled
Microsoft Outlook 2003 is missing
OWA Update for Exchange Server is not installed
SBSMonitoring Agent Service not set at defaukt value
The installed version of samsrv.dll is not current
Windows SBS 2003 is not compatible with Vista/Outlook 2007
Windows SBS Backup wizard has not run
Windows SBS Monitoring wizard has not run
I am about to migrate my client from a very much overloaded SBS2003 server to multiple Server 2008 R2 + Exchange 2010 solution.
After running BPA, can someone please verify what is really crucial to fix, and/or what can be safely ignored?
Please note that there are no current known issues.
Critical
Task Offloading is enabled
Warnings
Free disk space is low
NIC Driver file is more than 1 year old
/Exchange-oma local path does not match /Exchange
CEICW has not been run
Change the functional level of Exchange Server 2003
Companyweb Filter Names is not at default value
EDNS is enabled
Microsoft Outlook 2003 is missing
OWA Update for Exchange Server is not installed
SBSMonitoring Agent Service not set at defaukt value
The installed version of samsrv.dll is not current
Windows SBS 2003 is not compatible with Vista/Outlook 2007
Windows SBS Backup wizard has not run
Windows SBS Monitoring wizard has not run
ASKER
Correct, it was not set up using Wizards...
I am already following that guide, just wondered if anything there jumped out at you as an immediate migration failure.
I am already following that guide, just wondered if anything there jumped out at you as an immediate migration failure.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I think I just remembered what the Vista/Outlook 2007 means:
SBS 2003 RipCurl:
http://blog.mpecsinc.ca/2007/05/sbs-2k3-r2-windows-vista-ripcurl.html
Addresses the compatibility issues.
Philip
SBS 2003 RipCurl:
http://blog.mpecsinc.ca/2007/05/sbs-2k3-r2-windows-vista-ripcurl.html
Addresses the compatibility issues.
Philip
Your best bet is to have a good System State and full backup of the server. To us "Good" means _test restored successfully_.
Since SBS is not set up like SBS anything goes.
Your methodology to migrate can be found in Glen's guide here:
https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html
Philip