OOF in hosted environment
-
lunes, 30 de abril de 2012 19:31
Exchange 2010 SP1 hosted environment with separate role servers (CAS server, HUB server and MB server).
I've got a problem enabling OOF in our hosted environment. When I do get-mailboxautoreplyconfiguration and put in the domain\user, I get this -
RunspaceId : 48c4eb40-b40b-405b-bb28-ea53857f61b4
AutoReplyState : Enabled
EndTime : 5/1/2012 2:00:00 PM
ExternalAudience : All
ExternalMessage : <html>
<body>
Testing external OOF
</body>
</html>
InternalMessage : <html>
<body>
Testing internal OOF
</body>
</html>
StartTime : 4/30/2012 2:00:00 PM
MailboxOwnerId : [domain]/[OU]/[OU]/user@domain.com
Identity : [domain]/[OU]/[OU]/user@domain.com
IsValid : TrueLooks good, but I get no OOF message when I send to this user (internal or external). The frustrating part is that another 'tenant' domain works fine when we set the OOF for a user (it's just the test tenant created when the server was built). The get-mailboxautoreplyconfiguration looks EXACTLY the same for both.
We've been making all these adjustments on the CAS server.
All users can access and set their OOF in webmail just fine.
Any ideas would be greatly appreciated!
Edit - Also, I'm trying to use the ignoredefaultscope option (just to try it) but no matter how I type it I can't get the DN to translate...
[PS] C:\Windows\system32>set-mailboxautoreplyconfiguration -ignoredefaultscope -identity CN=user@domain.com,OU=[OU],OU=Microsoft Exchange Hosted Organizations,DC=[DC],DC=COM -autoreplystate enabled -external
audience all -internalmessage "Testing internal OOF" -externalmessage "Testing external OOF"- Editado Alceryes lunes, 30 de abril de 2012 19:44
- Cambiado Mike CrowleyMVP miércoles, 02 de mayo de 2012 2:32 (From:Exchange Server 2010)
Todas las respuestas
-
miércoles, 02 de mayo de 2012 14:14
Figured it out (just gotta get my hands on the hotfix) --
http://worldofexchange.wordpress.com/2011/12/30/a-bug-in-ms-exchange-2010-sp1-hosted/
-
viernes, 04 de mayo de 2012 23:44Do you have journaling enabled?
-
lunes, 14 de mayo de 2012 23:59
Yes we do.
Had to jump through some MS tech support hoops but they finally sent me the hotfix and it worked! Problem solved. -
miércoles, 16 de mayo de 2012 21:35We're going to include this fix in 2010 SP2 RU4.

