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

LVL 1
hongeditAsked:
Who is Participating?
 
Philip ElderConnect With a Mentor Technical Architect - HA/Compute/StorageCommented:
The following:

 + Task Offloading is enabled

 + Free disk space is low
 +  Driver file is more than 1 year old
 +++ Exchange-oma local path does not match /Exchange
 +++ Change the functional level of Exchange Server 2003

 + EDNS is enabled (?)

 +++ OWA Update for Exchange Server is not installed
 +++ The installed version of samsrv.dll is not current (Win2K3 SPx)
http://support.microsoft.com/kb/889100

 + Windows SBS 2003 is not compatible with Vista/Outlook 2007 (Huh? Is it installed here?)

For obvious reasons if you are migrating Exchange 2003 mailboxes to the new setup then Exchange releated issues need to be dealt with.

Make sure that your Forest and Domain AD levels are set to 2003 native too.

Philip
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
It looks as though this particular SBS 2003 was not set up like an SBS should have been. That is using the SBS Wizards.

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:

http://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
0
 
hongeditAuthor Commented:
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.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
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
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.