Exchange 2013 / Outlook 2007

Hi,
Just finish to configure Exchange 2013 CU3; I have no problem with OWA. But trying to connect to outlook 2007 SP3 (PC is joined to local domain: mysociety.lan) i'm facing with this error: "The connection to Microsoft Exchange is unavailable. Outlook
must be online or connected to complete this action". When i try to continue it gives to me : [email protected]; when i replace it to:[email protected] it connect; but restarting the computer give me the same error.
Please Help

Hi,
In addition, please use the ExRCA to test Outlook Anywhere connectivity and see if there is any error. For your convenience:
https://www.testexchangeconnectivity.com
Regards,
Rebecca Tu
TechNet Community Support

Similar Messages

Exchange 2013 - Outlook 2007 - Server name GUID

Hi Guys.
I am hoping someone can shine some light on something for me.
Right now I have the following with roles.
1 x Exchange 2010 - MBX & CAS
1x Exchange 2013 - MBX
1 x Exchange 2013 - CAS
Mix of Outlook 2007 & 2010
I migrated a user from Exchange 2010 over to Exchange 2013 and the process went fine. Email flow is working, OWA and Active Sync again working ok.
However when we opened Outlook 2007 it displayed a message to say an Administrator had made changes and we needed to restart Outlook. No issues there.
Outlook connected up fine and everything works. However when you look in the mail profile for the Exchange server name i see something like
[email protected]
Also Outlook Anywhere is ticked and when you untick it from the client and then open it again it comes back.
Are the above items of migration?

Hi,
RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as Outlook Anywhere).
Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP
address.
To expand on this a little bit, I worked an issue with a new Exchange 2013 environment for 3 days before figuring out that you do NOT specify a server name where it asks for it in Outlook, you use the format mentioned above.
For reference, I received a very particular error from testconnectivity.microsoft.com that made no sense until I discovered the server name format. If a test fails with a 404 HTTP Not Found error and an X-CasErrorCode of MailboxGuidWithDomainNotFound,
this is most likely your problem. Its very frustrating that Microsoft does not have it documented anywhere exactly what this error means, would have saved me a lot of time and energy.

Exchange 2013, Outlook 2007 clients Problems with Outlook Anywhere connection

Hi everyone,
I have a mail system Exchange 2013 SP1, on Windows Server 2012 R2.
I have only one mail server with the Client Access and Mailbox roles Server.
I have a Wildcard certificate type *. Mydomain.com.
All connections to the Outlook Anywhere Outlook 2010, Outook 2013 work correctly.
The ActiveSync connections are working properly, too.
But Outlook 2007 clients connecting with Outlook Anywhere asking for credentials continuously fail continuously.
How can I solve this?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
Based on my experience, we need to set Outlook provider with the domain name if it's wildcard certificate:
Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
Thus, I recommend you try the above configuration and test the Outlook connection again.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 - Outlook 2010 - 550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address

Hello,
I have issue when sending email to some addresses. Server respond with:
Remote Server returned '550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)'
My enviroment: Exchange 2013, Outlook 2010 - no cached mode. Issue happend with two email addresses but not always.
Any suggestion, how to resolve issue?
Thx.

Hi Tomas,
Does this issue occur in OWA? How is the impact, only one user or all users?
Please try to run Outlook under safe mode to avoid add-ins and AVs.
If there is any 3rd party add-ins, please try to disable them for testing.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 and 2007 coexistence and redirects

Hi all,
I'm settings up the coexistence but i've got a problem.
I've got 3 sites:
Site A: Exchange 2013 cas and mailbox
Site B: Exchange 2007 hub/cas and mailbox
Site C: Exchange 2007 hub/cas and mailbox
The problem is the owa and active sync redirect. I can open a mailbox located in site B where the legacy.domain.com dns record points, but i cannot open a mailbox from the exchange 2013 nor 2007 owa from site B to C.
I configured only the internal url leaving the external one blank.
How do i redirect all the requests to a mailbox located in site C from site A and B?
Thanks,
D.

You need to have External URL too, so that redirection can take place.
http://blogs.technet.com/b/mbaher/archive/2009/12/17/exchange-2010-proxy-or-redirect.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Configuring Message Clasifications Exchange 2010 - Outlook 2007/2010/2013

Hi
I created Message Classification as described in:
http://technet.microsoft.com/en-us/library/bb123498(v=exchg.141).aspx
New-MessageClassification ....
New MessageClassification is visible in OWA.
I stared deploy Message Classifications for Outlook 2007 using this
http://technet.microsoft.com/en-us/library/aa998271(v=exchg.141).aspx
Of course there is small bug: "AdminClassificationPath"="c:\\Classifications.xml" but is should be
"AdminClassificationPath"="c:\Classifications.xml"
After set up it doesn't work. The same for Outlook 2010 and 2013?
Does anybody deploy Message Classifications for Outlook 2007 or 2010 or 2013 with success?
I use Exchange 2010 SP3 with all RU and Outlook 2007, 2010, 2013 with all updates.
Kind Regards Tomasz

Hi,
How do you know this is an old reoccurring message? Based on the content or time?
Since the MailboxAutoReplyConfiguration is correct, I suspect the issue can occur by certain client machine. At this stage, I suggest you disable OOF and re-enable
OOF on the problematic machine. If the issue persists, please refer to the following article to clean the problematic client’s Outlook rules. (run Outlook.exe /cleanrules in Run console.)
http://www.tech-recipes.com/rx/2161/outlook_2007_clean_up_command_line_switches/
Thanks.
Novak Wu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

Hello,
we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
using Outlook Anywhere.
The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content## from the external provider's servers.
When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
We have no problems using the company's Exchange 2013 servers.
Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
Thank you
Sascha

Hi,
The problem should be related to the External Exchange 2007.
Please refer to this kb below:
http://support.microsoft.com/kb/2203381/en-us
This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body. If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
To resolve this problem, you should let the External Provider install the following update rollup:
2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Hope this helps.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Windows XP Machines Always Prompt for Credentials (Exchange 2013, Outlook 2010)

I am running Exchange 2013 on Server 2012 Datacenter (VM). Windows 7 clients with Outlook 2010 work fine. Windows XP clients with Outlook 2010 prompt for credentials (user name and password) each time Outlook is started, and checking the "Remember
my password" box does not prevent this from happening the next time. The "Always prompt for logon credentials" checkbox on the "Security" tab of the "More Settings" section of the Exchange account is not checked. I have found a myriad of posts
with similar issues, but they all seem to have to do with SBS/Exchange 2007, and I haven't come across something that works as a solution for me. One suggested certificate issues, and I was having certificate security warnings, but I got that resolved.
I am hopefuly that the fact that this only happens on Windows XP will be telling.

Proxy settings:
auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 50
auth_param ntlm keep_alive on
auth_param basic program /usr/lib/squid3/squid_ldap_auth -R \
-b "DC=domain,DC=local" \
-D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" \
-W passldap \
-f "sAMAccountName=%s" \
-h domain.local
auth_param basic children 20
auth_param basic realm Domain Internet Proxy
auth_param basic credentialsttl 8 hours
external_acl_type ADS children=50 ipv4 ttl=60 %LOGIN /usr/lib/squid3/squid_ldap_group -S -K -b "DC=domain,DC=local" -f "(&(objectclass=person)(sAMAccountName=%v)(memberof =CN=%a,OU=Domain,DC=domain,DC=local))" -D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" -s sub -W ldappass domain.local
tks.

Exchange 2010 - Exchange 2013 Outlook 2010 resolves wrong server

Hello,
We are upgrading from exchange 2010 to 2013.
Now I have migrated a testmailbox, but when I try to configure it in outlook it tries to connect to the Exchange 2010 server instead of the Exchange 2013 server.
I have configured outlook manually like described on the following url:
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
At the "Check Name" step, it will not resolve the Exchange 2013 server guid but the Exchange 2010 server... but the mailbox is migrated to Exchange 2013...
When I try to launch outlook an error occurs: Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data
file (.ost)."
Can someone help me out please?
Thx!

Are you sure the mailbox move completed? What happens when you log into OWA? Are you having AD replication issues in your environment?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange 2013- Outlook will stop working intermittently but OWA works that time

Hello everyone. Hope someone can help me with this issue. We are experiencing a strange issue with our exchange 2013 server. We only have one exchange 2013 server and it is up to the CU2 level. The issue is sometimes the outlook clients
will stop working and the only way to fix this issue is by restarting the server . I tried restarting the exchange services but it didn't fix the issue. The outlook web access will work without any issue during this time. My research indicates
that the exchange server is getting some kind of disconnection/timeout from the Active directory. I can see the following event logs on the exchange server:
Log Name:      Microsoft-Exchange-MailboxDatabaseFailureItems/Operational
Source:        Microsoft-Exchange-MailboxDatabaseFailureItems
Date:          13/03/2014 1:12:20 PM
Event ID:      1
Task Category: Store
Level:         Information
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
Failure Item (Namespace=Store, Tag=HungStoreWorker, Database=CN=Mailbox Database 0572517180,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xx,DC=local,
Instance=Mailbox Database 0572517180)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-MailboxDatabaseFailureItems" Guid="{08E893EA-4C11-4FFF-A737-99B9EEDEE4F4}" />
    <EventID>1</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-13T02:42:20.026303800Z" />
    <EventRecordID>8180</EventRecordID>
    <Correlation />
    <Execution ProcessID="5980" ThreadID="14380" />
    <Channel>Microsoft-Exchange-MailboxDatabaseFailureItems/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <Version>1</Version>
      <Namespace>1</Namespace>
      <Tag>38</Tag>
      <DatabaseGuid>{D789BB55-9D2A-445C-B29E-E7EA510E89D6}</DatabaseGuid>
      <DatabaseInstanceName>Mailbox Database 0572517180</DatabaseInstanceName>
      <Component>StoreService</Component>
      <IOErrorIsSpecified>false</IOErrorIsSpecified>
      <NotificationEventIsSpecified>false</NotificationEventIsSpecified>
      <IOError>
        <Category>0</Category>
        <FileName>
        </FileName>
        <Offset>0</Offset>
        <Size>0</Size>
      </IOError>
      <NotificationEvent>
        <EventID>0</EventID>
        <ParameterBufferSize>0</ParameterBufferSize>
        <ParameterBuffer>
        </ParameterBuffer>
      </NotificationEvent>
    </EventXML>
</UserData>
</Event>
Log Name:      Microsoft-Exchange-HighAvailability/Operational
Source:        Microsoft-Exchange-HighAvailability
Date:          3/03/2014 1:43:53 PM
Event ID:      841
Task Category: Database Action
Level:         Error
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
ListMdbStatus failed to server 'xxexchsvr': Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of 00:00:05.
(hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-HighAvailability" Guid="{455E3D31-77EF-4853-94A1-032A399567EC}" />
    <EventID>841</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T03:13:53.421449100Z" />
    <EventRecordID>15370</EventRecordID>
    <Correlation />
    <Execution ProcessID="7264" ThreadID="5188" />
    <Channel>Microsoft-Exchange-HighAvailability/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <NodeName>xxexchsvr</NodeName>
      <Message>Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of
00:00:05. (hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)</Message>
    </EventXML>
</UserData>
</Event>
Can anyone please tell me what causing this issue?
Thanks in advance.

Hi,
According to your description, your Outlook client intermittently cannot work. I recommend you try to use RPC trace log to find the root cause.
Additionally, I recommend you update to Exchange 2013 sp1 and then check if the issue still can be reproduced.
http://blogs.technet.com/b/rmilne/archive/2014/02/25/exchange-2013-sp1-released.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

How to disable Exchange 2013 Outlook Anywhere for internal Outlook client

Hello;
By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013. What is the best method to disable the Outlook anywhere
on mailbox but let the Outlook 2013 still able access to Exchg server.
The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only. Looks like Microsoft did not think about the security.
thanks!

Hello;
By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013. What is the best method to disable the Outlook anywhere
on mailbox but let the Outlook 2013 still able access to Exchg server.
The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only. Looks like Microsoft did not think about the security.
thanks!
I don't understand your request. If you disabled Outlook Anywhere, Outlook will only be able to connect via IMAP or POP3.
If you want to disable this ability and allow some then perhaps use cas-mailbox to disable in bulk and then enable only those allowed:
http://technet.microsoft.com/en-us/library/bb125264(v=exchg.150).aspx
The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox by using Outlook Anywhere (RPC over HTTP) in Microsoft Outlook.
Valid values for this parameter are:
$true Only Outlook clients that aren't configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox. By default, Outlook 2013 is configured to use Outlook Anywhere.
$false Outlook clients that are configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox.
The default value is $false.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 / Outlook 2010+ Attachment size limit

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl
1. If you send a message larger than 10MB from an external client to your org, does it bounce back because its over the limit?
2. Do you see the same problem sending internally with OWA?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2003, Outlook 2007 and Free/Busy options

We are using Exchange 2003 and Outlook 2007 our Free/Busy options are not showing up, is the a copatibility issue between the two?

Hi,
It is by design that there is no Free/busy option for Exchange 2003 mailbox. Here is a similar thread for your issue:
http://social.technet.microsoft.com/Forums/en-US/00859a5b-ada8-4824-9406-dff8d763b5b8/freebusy-options-in-outlook-2007-exchange-2003?forum=exchangesvrclientslegacy
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 - outlook in LAN environment very slow upload but fast download - not using 'use cached exchange mode'

Hi,
I have Exchange 2013 setup in a new environment (no migration) and it is working great except I just realized there is a big problem.
I notice the following
Problem 1:
Outlook 2010 with sp2 with cached exchange mode on: when I import the pst into outlook, it imports fine but the sync is extremely slow. It uploads to the Exchange 2013 mail server at 20-70KB/sec (bytes) via LAN.
Problem 2:
Outlook 2010 with sp2 with cached exchange mode off: when I import the pst into outlook, it imports extremely slow. It uploads to the Exchange 2013 mail server at 20-70KB/sec (bytes) via LAN.
More info:
-user1 has 1GB of mail and when setting up the user on a new pc with outlook with cached exchange mode on, it downloads the mail very fast. It downloads at 40-80 Mbps/sec (bits).
-I have Exchange 2013 with CU3 with win2k12 non r2.
Why is the download so fast from Exchange 2013 but the upload to Exchange 2013 is extremely slow? How do I fix this?
Thanks

I did some more testing.
I setup a test environment with:
-Exchange 2013 SP1 on win2k12 r2
-Outlook 2010 SP2 on windows 7 sp1
-Outlook 2010 SP2 on windows 8.1
-Outlook 2013 SP1 on windows 8.1
Both windows 7 and windows 8.1 have the very slow upload issue to Exchange 2013. Windows 7 upload to Exchange 2013 is around 20-70KB/sec (bytes) via LAN. Windows 8.1 upload is a bit more responsive at around 500-600KB/sec (bytes) via LAN.
I changed the TcpAckFrequency to 1 for windows 7 and 8.1 and the problem went away. The upload on both Windows 7 and 8.1 was going at megabytes after the change.
I hope Microsoft fixes this soon.
PowerShell script to have this automated via GPO:
http://community.spiceworks.com/topic/571571-outlook-slow-after-migrating-to-exchange-2013
PowerShell Script:
$strGUIDS=[array](Get-WmiObject win32_networkadapter -filter "netconnectionstatus = 2" | select -expand GUID)
foreach ($strGUID in $strGUIDS) {New-ItemProperty -path HKLM:\System\CurrentControlSet\services\Tcpip\Parameters\Interfaces\$strGUID -propertytype DWORD -name TcpAckFrequency -value 1}

Out of office sending out old messages - Exchange 2010 - Outlook 2007

Tracking down an issue of a user (I think it's only one) having their Out of Office Message always being a previous message from a year or two back. Doesn't matter if it's changed in Outlook 2007 or in OWA.
I've read some older post on this, but didn't find a clear answer.
This current Exchange 2010 setup is a migration from 2003. Could this be a leftover migration issue?
Anybody have this happen recently?

Hi,
How do you know this is an old reoccurring message? Based on the content or time?
Since the MailboxAutoReplyConfiguration is correct, I suspect the issue can occur by certain client machine. At this stage, I suggest you disable OOF and re-enable
OOF on the problematic machine. If the issue persists, please refer to the following article to clean the problematic client’s Outlook rules. (run Outlook.exe /cleanrules in Run console.)
http://www.tech-recipes.com/rx/2161/outlook_2007_clean_up_command_line_switches/
Thanks.
Novak Wu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2013 / Outlook 2007

Similar Messages

Maybe you are looking for