Outlook Users connection issues after Mailbox Migration from 2007 to 2013

Hi,
We have a coexistance between Exchange 2007 SP3 and Exchange 2013 CU7. There is an issue when after migrating the user from exchange 2007 mailbox to exchange 2013, the outlook keeps on prompting for password when it is being launched. Checking the Connection
Status we found that there is a connection to the old 2007 Server and the type is Exchange Public Folder. I have migrated the public folder and checked the Mailbox of the user and found that the DefaultPublicFolderMailbox is set to the 2013 Public Folder Mailbox.
If I check my 2013 MailboxDatabase Properties, It sill shows that PublicFolderDatabase Properties is still pointing to the 2007 Public Folder Database. Any resolution on this?
Another issue is, We set outlook anywhere on the 2013 to use basic authentication, however, when users are migrated to 2013 the Outlook client changes to NTLM. even if we set the outlook to basic to make it work, it still comes back to NTLM after a while.
I did most of the resolutions online to use powershell to make changes to outlook anywhere but no luck. any suggestions is highly appreciated.
Thanks & Regards,
Arthur

Hi,
For the first problem, please check the msExchHomePublicMDB attribute for mailbox database in Exchange 2013, you can check this attribute in ADSIEdit.
If this attribute is pointing to Exchange 2007 public folder database, please set to blank. After that, please restart the information service.
And for the second question, I suggest we open a new case for this issue. In order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one
issue per thread in order to find a resolution efficiently.
Thanks for your understanding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

Mac Outlook 2011 Not Syncing After User Is Migrated from 2007 to 2013

I have a couple users using Outlook for Mac 2011 (14.4.1) that have trouble automatically syncing their mailboxes after being migrated from our Exchange 2007 environment to our Exchange 2013 environment. When they kick off a manual sync, it works
fine. Automatic syncing is very hit and miss and can go for hours before syncing. Identities, accounts, and profiles have been rebuilt without success. Is there something to look for client side or perhaps server side in EWS settings? Thanks.

Hi Peter,
Does this syncing issue occur in OWA?
If it works well in OWA, it seems an issue on the Outlook for Mac 2011 side.
I suggest asking Outlook for Mac 2011 Forum for help so that we can get more professional suggestions.
For your convenience:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
Sorry for the lack of knowledge on Mac. If there is safe mode in Mac, I suggest run Mac under the safe mode to avoid some AVs and add-ins for testing.
If the syncing issue exists in OWA, I suggest collecting app logs for the further troubleshooting.
Thanks
Mavis
Mavis Huang
TechNet Community Support

DL Migration from 2007 to 2013

Guys,
We need to migrate 150 DL's from 2007 to 2013.
2007 DL's are in .companyname<department> format and in 2013 special characters are not supported
We would like to change the format to DL-companyname....
Is there is script to copy the existing list of DL's including permissions in 2007, recreate new one's in the new format and add the permissions in 2013?
Thanks
D

Hi
Hi Here you go
You can use this one
foreach ($DL in (Get-DistributionGroup -ResultSize Unlimited)) { $owners = Get-ADPermission $DL.identity | ?{$_.User -notlike “*Exchange*” -and $_.User -notlike “S-*” -and $_.User -notlike “*Organization*” -and $_.User -notlike “NT*” -and $_.User -notlike
“*Domain Admins*” -and $_.User -notlike “*Enterprise Admins” -and $_.User -notlike “BUILTIN*” -and $_.User –notlike “*Delegated Setup*”} | %{$_.user.tostring()};Set-DistributionGroup $DL -BypassSecurityGroupManagerCheck -ManagedBy $owners }
Refer below link for more information which has clear cut information
http://exchangeserverinfo.net/2013/12/upgrading-distribution-groups-from-exchange-2007-to-exchange-2013/
http://gallery.technet.microsoft.com/scriptcenter/8c22734a-b237-4bba-ada5-74a49321f159
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Resources and public folder database - migration from 2007 to 2013

We migrated our resource mailboxes thru the move mailboxes in 2013 EAC but now we're at the point of decommissioning our 2007 servers. Before the actual decommission we stopped all 2007 services and dismounted all 2007 databases. Once we did
this the resources would no longer work - errors pertaining to cannot directly book the resource.
I had to bring up the public folder database for the moved resources to work again. We do not use public folders any longer so we did not do any type of public folder migration. Do I need to do this for the resources to work?

Hi,
Could you please tell me your Outlook version?
I saw someone got the following error when he tried to book resource after migrating from Exchange 2007 to Exchange 2010, if Outlook version is Outlook 2007. But Outlook 2010 worked well.
"Cannot directly book a resource for this meeting."
Please switch between online and cached mode to check the result. And please check if this issue occurs in OWA.
If possible, please use Outlook 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Workflow migration from 2007 to 2013?

We are planning on moving from SP 2007 to 2013. After looking at the new workflow platform in 2013, I'm wondering if our custom Designer-made workflows are going to migrate over. It looks, after only one day of trying out Designer 2013, that
the workflow functionality is greatly reduced. For example, in the actions, I don't even see the AND and OR operators, or "begins with" or "includes" etc. Can anyone point me to any good workaround tutorials/articles?
There are no mistakes; every result tells you something of value about what you are trying to accomplish.

Hi run4it,
How did you designe your SharePoint 2013 workflow?
SharePoint Designer 2013 workflow also has the operators AND/OR when I insert multiple conditions, and when I insert the list text type column like "Title", it will show "begins with" and "includes" operators like the following image, please try again.
Thanks,
Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Daniel Yang
TechNet Community Support

Migration from 2007 to 2013

hi ,
I have to migrate from sharepoint 2007 to 2013 so please provide me the all details .. from starting...
Thanks

@Sol4u, Check the similar threads below
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/a91880e6-da10-4d37-b951-167cc5deaa6a/migration-from-moss-2007-to-sharepoint-2013?forum=sharepointadmin
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/e9542ff4-7812-4e41-9a31-1fe8966c2988/moss-2007-to-sharepoint-2013-migration?forum=sharepointgeneral
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

TS1963 Issues after file migration from PC

Hi, I'm new to Mac and I've just done a file migration of my photo's from my old PC (using migration assistant after I've been using the mac i.e. not at initial start-up) and I now can't find the files. Looking at previous similar issues on forums people seem to suggest that a new account will be set up and the photo's will be in there, however there is no new account when I look for it.
Can anyone help to steer me in the right direction?

Welcome to the Apple Support Communities
Migration Assistant creates a new user. Open Apple menu > Log Out to go to the login screen, and you must see the user

Migrated from 2007 to 2013 - Sharing Calendars broken?

Issue: User Test1 cannot create calendar items for user Test2 and vice versa, regardless of permisions.
No amount of security permissions allow a user to create items on another user's calendar.
We've done it the powershell way ((Get-Mailbox) | Foreach-Object {Set-MailboxFolderPermission $_":\Calendar" -User Default -AccessRights PublishingEditor}), or a more targeted
"add-mailboxfolderpermission Test1:\Calendar -User Test2 AccessRights Owner"
We've done it the Outlook way (share calendar, calendar permissions, mailbox permissions...)
We've done it the Exchange Admin Console way (Full Access Delegation)
We tried elevating some test accounts to domain administrator, but still calendar items can't' be created.
No clues in event logs. Outlook Anywhere on\off doesn't matter. Caching on\off doesn't matter. Outlook 2010 fully updated is their client, Exch2013 fully updated is everyone's server. Supposedly their calendar sharing worked fine on the old Exch2007 Server.
Other people who have my problem:
Spiceworks Thread here
-Dane

Brand new users and security, like you asked! None of these 3 users can make calendar items in eachothers calendars. I haven't tried anything using OWA, I'll give that a shot and update you. Thanks for the replies too
by the way
>>>>>>>>>>>>>>Get-MailboxFolderPermission –Identity Test1:\Calendar | FL
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/test1:\Calendar
FolderName   : Calendar
User         : Default
AccessRights : {Editor}
IsValid      : True
ObjectState : New
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/test1:\Calendar
FolderName   : Calendar
User         : test2
AccessRights : {Owner}
IsValid      : True
ObjectState : New
>>>>>>>>>>>Get-MailboxFolderPermission –Identity Test2:\Calendar | FL
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/test2:\Calendar
FolderName   : Calendar
User         : Default
AccessRights : {AvailabilityOnly}
IsValid      : True
ObjectState : New
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/test2:\Calendar
FolderName   : Calendar
User         : mstest
AccessRights : {Owner}
IsValid      : True
ObjectState : New
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/test2:\Calendar
FolderName   : Calendar
User         : test1
AccessRights : {Owner}
IsValid      : True
ObjectState : New
>>>>>>>>>Get-MailboxFolderPermission –Identity mstest:\Calendar | FL
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/mstest:\Calendar
FolderName   : Calendar
User         : Default
AccessRights : {AvailabilityOnly}
IsValid      : True
ObjectState : New
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/mstest:\Calendar
FolderName   : Calendar
User         : Anonymous
AccessRights : {Owner}
IsValid      : True
ObjectState : New
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/mstest:\Calendar
FolderName   : Calendar
User         : test2
AccessRights : {Author}
IsValid      : True
ObjectState : New
RunspaceId   : de62dc26-c253-4d70-a008-714ada48a716
Identity     : hasb.local/Users/mstest:\Calendar
FolderName   : Calendar
User         : mstest
AccessRights : {Owner}
IsValid      : True
ObjectState : New
-Dane

Outlook Authentication prompt after migrating from 2007/2013

I have a very simple environment. 3 new Exchange 2013 servers in a DAG behind a load balancer. Most users are still on Exchange 2007 environment. Autodiscover has been configured for load balanced name. There is no External Outlook
Anywhere connectivity. I have NOT enabled Outlook Anywhere in the 2007 environment. I have a simple Lync 2013 environment. 1 Server in a standard pool with no external connectivity. I have integration with OWA 2013 and Lync working.
All versions of Outlook are at least on the patch level required for Exchange 2013.
My issue is random password prompts in Outlook for some (not all) users with mailboxes on Exchange 2013. This password prompt appears to be coming from the load balanced Outlook anywhere name. I have had a few reports of users on Exchange 2007
getting an error stating they cannot open default set of folders. If I have them exit Lync 2013 client and open Outlook again it works fine. They can then open Lync without issue. Closing and opening Outlook will no longer reproduce the issue.
It seems like Lync is causing an issue here somewhere, but I have no idea where.
Lync BPA completes without any warning or errors. All test cmdlets complete without any errors.
2013 Outlook Anywhere settings:
Name                               : Rpc (Default Web Site)
ExternalHostname                   :
InternalHostname                   : mail.company.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
Get-AutodiscoverVirtualDirectory|select *auth*
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication : False
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : True
DigestAuthentication          : False
WindowsAuthentication         : True
OAuthAuthentication           : True
AdfsAuthentication            : False
brian smith

I just could not let this go last night. The issue was occurring when I moved a mailbox to 2013.
2 scenarios
#1. Users mailbox moved from 2007 to 2013. Profile has a secondary mailbox that is still on 2007. When entering Outlook they are prompted for
a password into the internally resolvable load balanced name (mail.company.com). If I remove this secondary 2007 mailbox they work fine, UNTIL they try to access anything on 2007 (calendar, Public Folder, another mailbox, etc). When they do attempt they
are prompted for a password.
I have seemingly fixed this error by adding the external URL back to AutoDiscover on 2013 based on
http://support.microsoft.com/kb/2839517<u5:p></u5:p>. Even though we have no intentions of using Outlook Anywhere externally.
During this troubleshooting I also changed InternalClientsRequireSsl from false to true. Now I have clients reporting errors in their event log “A fatal error occurred while
creating an SSL client credential. The internal error state is 10013." I do not think changing this to require SSL, but I’m almost scared to change it because this issue
is seemingly resolved.
#2 mailbox that is only accessed as a shared mailbox Mailbox is moved from 2007 to 2013. Users attaching to the mailbox are still on 2007. This works perfectly fine for some. However others receive a password prompt each time they open Outlook.
If the 2013 mailbox is removed from their outlook profile they receive no prompt. If I manually remove the mailbox from their profile and add it back the prompts go away. I have not been tracking client versions, but these last 4 are running 12.0.6691.5000.
I also noticed in checking the connection status all 2007 references are using [Nego] for authentication and mail.company.com is using NTLM. Is this normal? This is the same in my test environment, but I can’t replicate this issue in my test environment
either.
I’m very stumped.
2013 Outlook anywhere config:
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
SSLOffloading                      : True
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
2007 Outlook anywhere config:
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
SSLOffloading                      : True
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
brian smith

Migrated mailbox from 2007 to 2013 now unable to connect to Samsung S4

I'm in the process of migrating from 2007 to 2013.
I have moved successfully a several mailbox's from Ex2007 to Ex2013. Currently, all the EAS policies reside on the 2007 server and I have been successful reconnecting all the smartphones so far.
However, I have a Samsung S4 that is refusing to connect. Any ideas what I need to do?
Penny Miller
PennyM

I checked the phone settings in his OWA account and it is blank. How can I add it in?
Penny
PennyM

Migration from 2007 and Archive Mailbox PST import question

Our enterprise will be migrating from Exchange 2007 SP3 to Exchange 2013 CU3 very shortly. Exchange 2013 is set up and I am in coexistance mode currently. Everything is working fine with the legacy redirection, I have tested some mailbox migrations and they
work fine. We currently use Mimosa Nearpoint as a third party email archive product.
As part of this migration from 2007 to 2013, we plan on moving away from Mimosa Nearpoint and utilizing the Exchange 2013 Archive Mailbox feature. We will give each user an Archive Mailbox. We have the ability to export the users existing archive out of
NearPoint to .PST files and then migrating them directly into the users Archive Mailbox using the "New-MailboxImportRequest -IsArchive" powershell commandlet. This has been tested and works fine with one very important exception.
When I export from Nearpoint, I have to export the entire contents of the archive, I cannot set date ranges. So when I do an export, it also contains the contents of the user's mailbox. I have managed folder policies in place in the Exchange 2007 environment
which delete all contents of the mailbox older than 60 days, but when I import the .PST to the archive, it imports ALL items into the Archive Mailbox. So I have 60 days worth duplication of items.
It is my understanding that if I imported the Archive .PST directly into the users production mailbox in the 2013 side, that it would not import duplicate items. I am trying to find out if there is any process which will do the same thing with me importing
directly into the users Archive Mailbox.
Thanks you,

Hi,
We used a third patry email archive product to export to .pst files, so it is too hard to say that whether it cause this issue.
However, I found a method to delete the duplicate items from our mailbox via MFCMAPI Tool.
Please make sure that the Exchange Server mailbox has been backed up first.
Details in the following KB:
How to remove duplicate folders in Outlook when connected to an Exchange Server mailbox
http://support.microsoft.com/kb/2509983
I also found a script to remove duplicate items.
This script will scan each folder of a given mailbox and removes duplicate items from those folders. You can specify how the items should be deleted and what items to process, e.g. mail items or appointments. Sample usage is after a misbehaving synchronization
tool creates duplicate items or (accidental) import of PST file with duplicate items.
*****Please also make a full back up first*****
Removing Duplicate Items from a Mailbox
http://gallery.technet.microsoft.com/office/Removing-Duplicate-Items-f706e1cc#content
Disclaimer
The sample scripts are not supported under any Microsoft standard support program or service.
The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose.
The entire risk arising out of the use or performance of the sample scripts and documentation remains with you.
In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss
of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Some clients migrated from 2007 is presented with the self signed certificate in 2013

I have migrated from 2007 to 2013. I did a couple of test migrations and on the ones with domain member computers Outlook is giving a certificate warning. The certificate they are presented with is the default self signed certificate on the 2013 server.
Even though I have added a trusted public certificate to Exchange and checked of to use With IIS.
I see that the default certificate is also checked of to use With IIS and it cant be removed in ECS. Shouldnt this be removed from IIS all together when adding a New certificate? And why does some Clients gets presented With the self signed and some With
the Public? For instance owa is presented With the Public cert. Also and Outlook I tested from outside the domain.
Regards

Only the UCC certificate should be bound to IIS.
Are any clients using POP or IMAP, which also use SMTP? In this case clients can be presented with the "wrong" certificate as well.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Mailflow Problem After Migrating Mailbox From 2007 to 2013

I thought I was at the point of migrating our mailboxes from 2007 to 2013. I had created a new test mailbox on the 2013 server and changed all the DNS and virtual directories for the legacy on the 2007 server and was able to successfully send mail
to the test mailbox out and in both internally and externally. Then I migrated my first mailbox from 2007 to 2013 and things went south.
I CAN NOT:
Send e-mail from a mailbox on the 2007 server to the migrated mailbox on the 2013 server.
Send e-mail from migrated mailbox to external e-mail address.
I CAN:
Send e-mail from the migrated mailbox to a 2007 mailbox and the test mailbox on the 2013 server.
Send e-mail from the internet to the migrated mailbox and the 2013 test mailbox.
I unfortunately am running Exchange 2013 with CU6 (I am already aware of the activesync issue and delegation crash issue but saw the info too late).
Suggestions please!!

Hi,
Before going further, I'd like to ask the following questions to troubleshoot the issue:
1. Could you send email from 2007 mailbox to the test mailbox on 2013 server?
2. Did you get any NDR message when sending email to the migrated mailbox failed?
In addition, I recommend you try the following methods to find out the root cause:
1. Try to use message tracking tool in exchange 2007 server ,it will help us to find the email which was sent to the migrated mailbox .
2. Run the following command to check the permission groups of the receive connector:
Get-Receiveconnector |fl Name,PermissionGroups,Exchangeversion
Best regards,
Niko Cheng
TechNet Community Support

Troubleshooting for RPC over https (Outlook Anywhere) connection issue

RPC over https (ROH), well known as Outlook Anywhere, is more frequently used. Even in Exchange 2013, Outlook no longer connects CAS server via MAPI.
In this thread, we will discuss about the troubleshoot checklist about the RPC over https (Outlook Anywhere) connection issue. In order to make it more logical, I’d like to divide the whole troubleshooting to the following processes:
1. Client side to CAS side
2. CAS side to MBX side
[Issues between Client side to CAS side]
In Exchange 2013, Outlook Anywhere is enabled by default. Different from this, Outlook Anywhere in Exchange 2007 and 2010 need to be manually enabled. Thus, please firstly check if the RPC over HTTP component has been installed:
Click Start, and then click Control Panel.
Double-click Programs and Features.
In the left pane of Server Manager, click Features.
In the right pane, click Add Features.
Check if the RPC over HTTP component has been selected.
If the ROH connectivity issue only happens on certain users, the property MAPIBlockOutlookRpcHTTP can be checked:
Get-CASMailbox name | fl MAPIBlockOutlookRpcHttp
2. Confirm if Exchange server is blocked. Ping the Exchange server FQDN on client machine and confirm if it can return the proper IP address.
3. Check if the RPC Proxy server is responding correctly:
rpcping -t ncacn_http -s ExchServer -o RpcProxy=RPCProxyServer -P "user,domain,*" -I "user,domain,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
If 200 code returns, the test is successful.
4. Check if Outlook Anywhere host names are added in the certificate:
To get host names, the following command can be used: get-outlookanywhere |fl *hostname
5. To use the Shell to test Outlook Anywhere connectivity, use the
Test-OutlookConnectivity cmdlet.
[Issues between CAS side to Mailbox side][RZ1]
A. Check if it can connect to store’s port:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
B. Check if it can Connect to DsProxy Service:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
C. Check the following registries:
[Disable the auto update]
1).Open Regedit and navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeServiceHost\RpcHttpConfigurator\RpcHttpConfigurator
2).Set the PeriodicPollingMinutes value to 0.
[Check the RpcProxy ValidPorts]
1).On the RPC proxy server, start Registry Editor (Regedit).
2). In the console tree, locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
3). In the details pane, right-click the ValidPorts subkey, and then click Modify.
4). In Edit String, in the Value data box, type the following information:
ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004
Note:
ExchangeServer is the NetBIOS name of your Exchange server. ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server. If the FQDN that is used to access the server from the Internet differs from the internal FQDN, you must use
the internal FQDN.
[Check the 6004 port settings in registry]
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)
D. Check if the RPC ports are used by other applications instead of Exchange by using : netstat –o
Then it will return all active TCP connections and the process ID (PID) for each connection.
After that, please check the application based on the PID on the Processes tab in Windows Task Manager and confirm if it’s Exchange server.
Additionally, ExRCA is a perfect tool to test the whole connection between client side and Mailbox side:
https://testconnectivity.microsoft.com/
1. On the ExRCA website, under Microsoft Office Outlook Connectivity Tests, select Outlook connectivity, and then select Next at the bottom of the page.
2. Enter the required information on the next screen, including email address, domain and user name, and password.
3. Choose whether to use Autodiscover to detect server settings or to manually specify server settings.
4. Accept the disclaimer, enter the verification code, and then select Verify.
5. Select Perform Test.
<Resource for reference>
How does Outlook Anywhere work (and not work):
http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspx
How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003:
http://support.microsoft.com/kb/831051
Test Outlook Anywhere Connectivity:
http://technet.microsoft.com/en-us/library/ee633453(v=exchg.150).aspx
[RZ1]It’s part, please re-layout
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I've just restored the M11 to Windows XP with the disks provided and Outlook Anywhere connected without issue. As strange as it sounds, this looks to be isolated to this particular model of laptop and Windows 7.
I've used the same Enterprise copy of Windows 7 and Office on a variety of laptops and pc's and none have come across this problem. The only commonality I can see is the hardware and OS.
Aftery trying to troubleshoot this unsuccessfully with Microsoft tech support for a few hours, they eluded to the fact that this +could+ be a hardware related problem. (driver, adapter properties, etc)

Outlook Users connection issues after Mailbox Migration from 2007 to 2013

Similar Messages

Maybe you are looking for