Email stuck in outbox when sent to address outside of Exchange domain while using roaming profile on 2008 Terminal Server.

I have four users out of about 130 with the following problem.  When they send an email to someone outside of our Exchange 2010 domain, the message gets stuck in outbox.  This happens when they are using Outlook 2007 on 2008 R2 RDS, roaming profile, and redirected services.  OWA works fine. Using a standard workstation works fine with same roaming profile and redirected folders.  Safe mode works for two of the users.  Also works if a user does a right-click to send a file as an attachment instead of opening new message and adding file.  Deleting roaming profile works for a short time.  One user has rare occurrence when email get sent correctly.  All users have same configuration.  

Any ideas?
joseph6478Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
joseph6478Connect With a Mentor Author Commented:
I ended up contacting MS about this.  It appears they found something in logs that they have created a hotfix for that will be released in next few weeks.  So I will wait until then to see if the fix works.

Thanks for input.
0
 
CoralonCommented:
It sounds like they are getting multiple outlook profiles created.  I have run into this before, and the profiles simply refuse to send out email.  The solution was to delete all of the profiles, and recreate a new one.  If that fixes it, then your next step is to determine where the multiple profiles are coming from.

Coralon
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Could be a corrupt machine profile causing the issue if all others with the same configuration are working fine

- Rancy
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Brian BIndependant Technology ProfessionalCommented:
Sounds like a profile issue to me as well, but that's been covered. Also if you are using caching, find the OST associated with that user and delete it.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So you made MS create a Hot-fix :) 'jokin'

- Rancy
0
 
Brian BIndependant Technology ProfessionalCommented:
Glad you found a fix. Thanks for posting the solution.
0
 
joseph6478Author Commented:
I used the following MS Hotfix to solve the problem.

http://support.microsoft.com/kb/2760822
0
All Courses

From novice to tech pro — start learning today.