To start: yes it is going to completely kill your inter-site performance. Outlook/Exchange is not smart enough to limit the traffic, you will need to configure QOS if you plan to do this during business hours. As far as re-downloading the mailbox when a user gets a new PC: this is also something that will have to happen with cached Exchange mode. When you configure Outlook's connection to your Exchange server it has to create a new local .OST file (local cached mailbox). A quick search of Google shows there are ways to create the .OST file, stop the download, and replace the new .OST with an old .OST file of the same name. However I have never tried this and cannot condone it. I recently consolidated users in my company onto one domain and had to deal with the re-download of the local .OST file (very Frustrating).
A side note: Although Outlook 2003/2007 allows up to 20GB .PST(http://support.microsoft.com/kb/830336/en-us), I HIGHLY recommend you keep them no higher than 1.5 Gigs anything over that will cause problems. The problems are a mixture too, sometimes outlook will fail to start, sometime it’ll stop sending and receiving, sometimes it will randomly delete mail, other times the entire file can get corrupted. It took me a while to narrow down what was wrong with some of my users Outlook, after talking to another Sysadmin who experienced the same problems I found out it was over-sized PST's. I just want to save you some headaches a year or two down the line.
Well it has to be 1 of 3 things. Something changed in the AD account, something changed in the Exchange account or something changed on the phone itself. Can you enable debugging on the phone to ascertain why exactly the phone is throwing an error.
Follow these steps to enable debugging:
1. On the android phone go to menu -> email. You will need to have an already configured email account in order to enable debugging. If there is not one then you can simply add the User's gmail account. After this gmail account has been added go to the "Accounts" screen in the email app and type the following.
debug
2. This should pop up a new screen with 4 checkboxes to enable enable debugging. Select all four check boxes and press the back button.
3. Now attempt to connect the User's phone to Exchange several more times so we get some good log data.
4. Connect the phone to a PC and Turn on USB storage.
The log should be located at the root of the phone's SD card and will be called emaillog.txt
Search the log for any pertinent error messages and look them up to ascertain the real reason behind the sync failure.
Edit:
Well the log info that you have posted is fairly generic. So I am going to post a couple of things that have helped me in the past:
1. Attempt to disable the the Exchange ActiveSync policy on the User's mailbox and then attempt to re-enable. You could even try making a copy of your current EAS and have him point to that one instead to see if that does anything.
2. Under the User's Active Directory make sure Include Inheritable permissions from this object's parent is check marked. You can view this setting by doing the following:
- In Active Directory Click
View->Advanced Features
- Right Click the User's account and go to the
Security Tab
- Click on
Advanced
- Check the box
Include Inheritable permissions from this object's parent pic below:
Best Answer
Security inheritance is not set by selecting a specific permission. It's a global setting per user object. The step about "select exchange servers" is pointless, you're doing this for all ACL's.
Every AD user should have security inheritance enabled. A ton of software that utilizes these security attributes (especially Exchange and Lync) rely on them.
The only way that option is disabled by default is if it's a domain admin account.
Are you running ActiveSync as an domain admin? Please, don't....