Quote:
Originally Posted by slbailey1
If you have an Exchange Server, that is all you need to keep Outlook and your phone synced, even with Windows Mobile - direct syncing between phone and laptop via bluetooth or USB is not required or need.
In Window Mobile, just setup your Exchange account. Any email sent to you Exchange account email address will appear in Outlook on your laptop AND on your phone. If you add, edit, or delete any contacts or tasks in Outlook, those changes will be reflected on your phone. If you add, edit, or delete any contacts or tasks on your phone, those changes will be reflected in Outlook.
Now with Hero, you can do the same things - setup your Exchange account on your phone and have the correct sync settings and your phone will stay synced with Outlook on your laptop via your Exchange server. There are a few things to keep in mind about Exchange and the Hero.
1. Using the built-in Exchange support on the Hero will not sync Tasks.
2. Not all security settings are supported.
To be able to sync tasks via Exchange, and to have all security settings supported, you must use a 3rd party Exchange application. A the best one to use is Touchdown and it only cost $10.
The Hero does not have any bluetooth sync support with Outlook. If you want to directly sync with Outlook, you must do USB sync, using the HTC Sync application. There are a few things to keep in mind about HTC Sync.
1. Tasks and Emails ARE NOT synced.
2. The only thing that are synced are Contacts and Calendar.
|
Slbailey1 - Thanks SOOO much for your post. I had no idea that my home version of Outlook had the capability of connecting to my work exchange server. I set up that relationship today and it works PERFECT! Now I don't have to worry at all about sync'ing my calendar and contact data back to outlook on my home PC.
Hopefully my Hero will arrive on Monday and I can try out the Exchange sync'ing relationship on the phone.
Thanks again! =D>
(Slapmedia - please accept my apologies. I know this post was specifically for Outlook, which was part of my problem, but the solution ended up being Exchange related.)