ad1) Please be more specific with sync issues. Do messages disappear? Do messages get duplicated?...
ad2) The basic issue is that Outlook 2003 support UDP and polling notifications. Exchange 2007 supports UDP, polling and Async notifications. Exchange 2010 only supports polling and Async notifications. This means when Outlook 2003 move from Exchange 2007 to Exchange 2010, Outlook clients will fall back to polling which by default only gets notifications every 30secs-1min. This means any change won’t show up immediately.
UDP notification support was removed from Exchange 2010. As a result, Outlook 2003 can only use polling notifications in online mode, which are still supported by RPC Client Access. This will result in a slight delay in updates to item status (30 seconds on average up to a 1 minute delay) when changes are made to items in a mailbox accessed by Outlook 2003.
source: http://social.technet.microsoft.com/Forums/en/exchange2010/thread/d5a610d5-b3cd-40a5-8653-634f3b174f4e
Okay, sorry to dismiss the earlier Server Fault message--it led me on the right track, at least. I called Dell support and had them walk me through disabling the performance features on the NIC, which resolved the issue. I think the key was disabling global chimney and receive side scaling, as I had tried most of the other steps as per the other Server Fault question posted. Of course none of these settings should cause problems, so maybe it's going to vary from server to server.
I also upgraded the driver version for the NIC, applied a BIOS patch and the latest Windows optional update rollup for Hyper-V issues, including a blue screen issue that we had experienced twice in the last week: KB2264080.
Here's the Dell support script I followed:
In a command prompt:
a. netsh int tcp set global chimney=disabled
b. netsh interface tcp set global rss=disabled
b. On each NIC inside the Broadcom Advanced Control Suite (BACS)
i. Disable IPv4 Checksum Offload
ii. Disable IPv4 Large Send Offload (LSO)
iii. Disable Receive Side Scaling (RSS)
. Uncheck the TCP Offload Engine (TOE) checkbox
v. Click Apply
Intel Configuration
a. Open Device Manager
b. On each Intel NIC in Device Manager, disable the following:
c. NOTE: Not every option is available or exist on the Advanced Tab.
i. Offload Receive IP Checksum
ii. Offload Receive TCP Checksum
iii. Offload TCP Segmentation
iv. Offload Transmit IP Checksum
v. Offload Transmit TCP Checksum
vi. IPV4 Checksum Offload
vii. Large Send Offload v2 (IPV4)
viii. Large Send Offload v2 (IPV6)
ix. Receive-Side Scaling
x. TCP Checksum Offload (IPV4)
xi. TCP Checksum Offload (IPV6)
In Windows Server 2008
1. Start à Run à CMD
2. netsh interface tcp set global rss=disabled
a. netsh int tcp set global autotuninglevel=disable
Best Answer
Obviously the company SHOULD be running proper Exchange backups to begin with. Not doing so is simply unprofessional and shows that email isn't that important to them to begin with. They may say it's important...but their actions show differently. OR just as bad...they assume their sysadmin is backing it up properly and they aren't and haven't divulged that to management.
That aside:
I think you have 3 schools of thought here.
OPTION #1 - the "kamikaze approach"
You simply run the sp3 upgrade on the server. I can tell you from dozens of experiences with Exchange service packs that I've yet to have one result in a catastrophic failure.
OPTION #2 - the "fix what's broken first approach"
You postpone your upgrade and get proper backups working on Exchange and the DC first so that you can rollback properly if something goes wrong. Otherwise, you're simply inviting a disaster. And snapshots aren't proper backups. The built in Windows 2008 R2 windows backup utility can properly backup the entire server with Exchange to an external USB drive in a pinch if you want to get lazy about it. (http://www.techrepublic.com/blog/the-enterprise-cloud/back-up-exchange-2010-with-this-windows-server-2008-r2-feature/)
OPTION #3 - your question's approach
Putting aside the fact that it's technically against licensing unless you already own an additional Exchange license...you could bring up another Exchange server. But man what a PITA. You aren't just "syncing" email as a backup, and when you do "move it all back" you'll have to properly decommission the new server, not to mention the frustrations client's Outlook and mobile devices will have if you don't properly setup this new server as a part of your Exchange "organization". You also don't take into account the possibility that adding this server COULD cause a failure to happen on the existing Exchange server, and without proper backups you could be just as bad off.
My advice...you go with Option #2...then run the SP3 installer on the existing server.