Hello,

We have had a terrible time with certificate errors on our new Exchange 2013 server (exchange.company.com).  We have certificates for exchange.company.com and autodiscover.company.com.  We are now getting certificate warnings in Outlook 2013 that state the name on the security certificate is invalid or does not match the name of the site.  At the top of the warning it says exchange.company.com.  Makes no sense!

When I click on VIEW CERTIFICATE it says issued to/by hubrouter.westell.com.  This is my DSL modem outside my firewall.  Why is this occurring?  There is an option to "install certificate" on the error in Outlook so I did this and pushed the hubrouter.westell.com certificate to all clients, no change.

Any suggestions on how I can resolve this?  Is there a way to ignore hubrouter.westell.com?  I really don't understand what is occurring and am running out of options.  Do I need to turn off autodiscover by HTTPS and just rely on SVC records?

Thanks!

Mike

Hi Team,

I have 2 exchange 2013 MBX+CAS. I plan to use wildcard public certificate as IIS services for all my Exchange.

I deploy wildcard, assign service and test it at browser and outlook in windows 7. no issue.

but when I test to windows XP machine SP2. outlook become issue, disconnect and prompt password.

heres the erro

I already change outlook provider but no good result. still disconnected. I am really sure outlook anywhere configuration for all my server is OK. no ssl offload and use NTLM.

please help :)  what is the root cause of this issue?

Thanks

Hey All,

I wanted to start this thread because for the first time since working on this, I have official confirmation from Microsoft that this is a known issue.

This has been discussed in various posts such as here and here, This post is actually a semi cross-post of another post of mine in this thread. This same behavior has been linked to this KB. Although the same behavior is observed, I am able to confirm that the two issues are unrelated. I was able to observe this problem with a newer version of Outlook 2013 than mentioned in the KB as well as in Outlook 2010.

Symptoms:

Consider this scenario:

- Existing Exchange 2010 environment with new Exchange 2013 Mailbox and CAS servers introduced. All Exchange 2010 servers on SP3 CU 5. Exchange 2013 Servers on SP1 CU 5

- Clients include Outlook 2010 SP1 and Outlook 2013 SP1

This procedure is followed to replicate the issue:

- Create new mailbox using Exchange 2010 console and add it in an Exchange 2010 Mailbox Database

- Create Outlook profiles in both Outlook 2010 and Outlook 2013. Outlook should work as expected at this point.

- From Exchange 2013, initiate a new migration for the mailbox in question. 

- When the migration finishes Outlook displays a pop-up and asks to be restarted

- After restart, Outlook stays disconnected. Looking at the Outlook "Connection Status" screen the client tries to connect to the Exchange 2013 server but the connection is redirected back to the 2010 server.

Cause:

According to Microsoft this is a known issue. It occurs because when a mailbox is moved to Exchange 2013 from Exchange 2010, the mailbox itself still has a cache entry that points the client back to the 2010 server. According to Microsoft, this cache expires after an "undetermined" time interval for Exchange 2013 SP1 up to CU4 and every "2 to 2.5 hours" in Exchange 2013 CU5. They could not reference a KB article with this info.

Workaround:

After a migration batch completes, perform aniisreset on the Exchange 2013 CAS server. The following strategy can be followed to streamline the process of migrating multiple mailboxes:

• Create a migration batch for a number of mailboxes. 
• Select to "Manually Complete the batch" in the "New Local Mailbox Move" window. This process will migrate 95% of the mailbox and then stop. 
• After 95% of the contents of each mailbox have been moved, the batch will stop syncing and show as "synced" on the migration window. Up to this point in the process users are able to use Outlook without any interruption and the move is invisible to them.
• When you are ready to finish the migration, select to "Complete This Migration Batch" on the ECP Migration screen. At this time, users that have Outlook open will receive a prompt to restart it. When Outlook re-opens, it will show as "Disconnected" until the next step is performed.
• Once the batch shows as "completed", perform an iisreset on the 2013 CAS server. At this time, Outlook will show as "Connected to Microsoft Exchange" and users will receive a second prompt to restart Outlook. After the second restart Outlook will be permanently connected to Exchange 2013.

If you do not wish to perform an iisreset, there is an alternative way of forcing Outlook to reconnect:

Microsoft has confirmed that recycling the following Application Pools forces Outlook to connect to Exchange 2013:

Exchange 2013 CAS Server

• MSExchangeAutodiscoverAppPool
• MSExchangeRpcProxyFrontEndAppPool

Exchange 2013 Mailbox Server:

• MSExchangeAutodiscoverAppPool
• MSExchangeRpcProxyAppPool

If you decide to not perform an iisreset and opt for recycling the App Pools instead, be advised that after the AppPools are recycled, Outlook connects to Exchange and asks to be restarted. If you close Outlook and immediately open it again, you will be prompted with a username and password pop-up (At least I was in all my tests of this method.) This issue is resolved if, after you close Outlook, wait 5 to 10 minutes before re-opening it. You will not be prompted for a user/pass at this point.

For those who choose to have the migration complete automatically: The cache entry that causes all this issue is cleared after about 2 to 2.5 hours if you are on Exchange 2013 CU5. In any case, it may be better if you have control over when the migration finishes by opting to complete it manually.

There is currently no KB article referencing this issue and Microsoft cannot provide a time when a patch fixing this will be released.

Thanks,
Fable

Hi All,

This is my case :

My environment need transport rule requirement like this post solution,

https://social.technet.microsoft.com/forums/exchange/en-US/dcf74b3c-063f-42ed-bed2-37b6e882445b/transport-rule-for-automatic-reply-to-sender

But in my environment using Exchange 2010 SP3, there is no "send bounce message to sender with enhanced status code" option.



Can you tell me why this happen?

Is it another option to replace "send bounce message to sender with enhanced status code" in Exchange 2010 SP3?

Hope that you can help me.

Thanks for your attention.

Best Regards,

Henry Stefanus

Hello

I have just migrated a few users from Exchange 2010 to Exchange 2013.

If I try and access their mailboxes via OWA 2013 using "open another users mailbox" I receive the following error:

X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
X-OWA-Version: 15.0.995.28
X-FEServer: EX2013
X-BEServer: EX2013.company.local
Date: 07/11/2014 11:23:46
I can still access any mailbox on a 2010 server via the same method.

Can anyone assist in resolving this issue please?

Matt

Hi Guys,

I keep having issues for some users who use Outlook 2010 SP2 with the latest patches and updates. from some reason they cannot see any Public folders (Ctrl+6) but, when they log in via OWA, they can view public folders and also add them to their favorites. In addition, on the Exchange 2013 SP1, I also assigned the right Public Folders permissions to the users, and they still cannot see any Public Folders. at first glance I thought it's a machine issue but after re-creating Outlook profile on a different machine for these users, still couldn't see Public Folders.

Please advise.

I'm currently migrating into my new Office 365 tenant and am experiencing the ios 8 corruption issues.

Outlook clients show recurring meeting updates as 'Out Of Date' and will not apply them to the meeting.

What does outlook do to calculate the age of a meeting update

Users with Outlook 2010/2013 in Exchange 2013 complaining about missed "Manage Voice Mail" icon in Outlook. Previously they used to click phone button in Outlook -> File Tab to manage their voice mail, however suddenly they missed this button in outlook.

Not sure what happened, please help us to resolve this issue.

Thanks

Tek-Nerd

We have added an exchange 2013 server to our existing exchange 2007 environment. We are having issues accessing OWA externally on the new server. When going to the OWA site of the new sever we are being directed to the OWA login page of the 2007 exchange not the 2013. Ports 443, 110 and 25 are forwarded to the 2013 server, but still only get the 2007 OWA. Both servers have different external OWA addresses. Any help would be appreciated, thank you in advance.

Adam

A company is using O365, with Outlook 2013 on their clients. Two people added a general account to their accountlist in Outlook 2013, which is used for "sales". For example, customers can send questions to this "sales" mail account and both employees can read the mail and answer the customer from that acoount.

My question is the following.

Both employees would like to have a different reading pane/lay-out. At this moment, if the first user change his view (in his Outlook client) to the view he likes, the second user see a change of his view too. The first person like to see the preview pane, the second don't... If the second change the view again to the one he likes, the first person will lose his prefered view.

I can't see any options to personalize the views at this account in Outlook or elsewhere in O365 for both people seperately. Is it possible anyway? If yes, how?

Currently running server 2012 r2 and exchange 2013 sp1...

Internally everything works fine, clients can also connect externally to owa/ecp. However when using an outlook client they are unable to connect. This is my first experience with exchange 2013 so I am at a loss. What steps should I be following to get this working properly? Or if anyone has some suggestions to get more information I can do that as well.

Thanks! 

Connecting from a mobile-phone using mail.mail.com works fine.

We are using a self-signed certificate for testing purposes..

Dear Users.......

we have a company website (www.tora.ir) and email addresses as well, all was going fine suddenly our hosting company asked us to get backup of all the emails because they said we are transferring to new web server. we were using outlook so we had all the emails on computers. .....after the transferring.......now when i go to directly account of mail there i found all the emails but my outlook does not receive some of the emails specially those emails which are in junk email of mail server account. my setting of outlook (2010) is as under...

mail server is .....      smartermail professional 11.7

setting of outlook is as under

account type ....................pop3

incomming mail server..... pop3.tora.ir

outgoing mail server........mail.tora.ir

incomming port................110

outgoing port...................587

any help .......thankssss

Tahir Mehmood

Hi,
I installed Exchange 2013 RTM in existing environment with Exchange 2010 Sp3 in our test environment.  After installing Exchange 2013 RTM I checked when I access OWA using Internal URl it redirected to Exchange 2010 CAS server's Internal URL and I was able to access Exchange 2010 mailbox.

I upgraded to CU2 and now Exchange 2013 internal URl not re-directing it to Exchange 2010 mailbox anymore. I checked all the settings on virtual directories and made sure that FBA authentication is selected.  It is a test environment and I just wanted to test the re-direction in co-existence environment using Internal URL. It should work out of the box but not sure what happened.  There was no issue in CU2 instllation.
Exchange 2013 CAS and mailbox roles are on separate servers.  Same with Exchange 2010.  There is no certificate 3rd party certificate install on CAS servers since it is a test environment.
Not sure what else can I check.
I appreciate if any help I can get.
Thanks,
Regards
Raman

Raman

Dear 

Is there any possibility to make all my exchange users reset there password using there alternative email like (yahoo ,hotmail or gmail).

Best regards

Rawa Zangana

Hi,

i am trying to send a mail with about 500 recipients from Outlook connected with Outlook Anywhere to the Exchange 2013 Server. For each user i get an error saying mail could not be send - Error: [0x80004005-00000000-00000000].

If i send mails only to a few recipients it works with no problem.

I found the following limitations:

get-ReceiveConnector | fl identity, MaxRecipientsPerMessage

MaxRecipientsPerMessage : Default : 5000, other connectors : 1000

get-transportservice | fl PickupDirectoryMaxRecipientsPerMessage

PickupDirectoryMaxRecipientsPerMessage : 100

get-transportconfig | fl maxrecipientenvelopelimit

maxrecipientenvelopelimit : 1000

get-mailbox user| fl RecipientLimits

RecipientLimits : Unlimited

Did i missed something?

Thanks Martin

All,

As a part of our path to POODLE remediation, I've been tasked with trying to determine browser types\versions that connect to our OWA. For instance, I need connection information that notes date\time browser and version. Is that possible, if so where can I get the instructions to review and pass along?

Thanks.

I am having a major headache trying to troubleshoot this issue.

My environment has an exchange 2010 server installed and running fine. We just installed Exchange 2013 in a coexistence situation (after upgrading 2010 to the SP3 RU5 etc) and migrated a few test mailboxes (mine included) before we do the full migration.
Setting up Outlook happens correctly. Autodiscover works and it resolves the name of the mailbox automatically and I get the correct guid@domain.fqdn (cant post images until im verified)

If I have to manually set up a mailbox (manual exchange connection) if I type in exch2010.fqdn it resolves to the mailbox correctly no matter which server or database it resides on.
|If I type in exch2013.fqdn I get the following error (action cannot be completed, the connection to Microsoft exchange is unavailable)

The only way to resolve this is to edit the registry HKCU\Microsoft\Exchange\Exchange Provider and add a string DS Server and point it to either of our 2 DCs (both are GCs). Doing so allows me to enter the exchange2013 fqdn and it resolves but not to the GUID but to the fqdn of the server.

Troubleshooting

I have spent days (if not weeks) trying to figure out why this is happening. DCDIAG gives me perfect results, DNS has been cleared of all the old name servers (there were still pointers of very old DCs showing as name servers in a few places but that has been thoroughly cleaned. replication is working fine, I have scoured event viewer of both DCs and both exchange servers and nothing stands out as relating to any errors.

Reason I need this resolved

The main reason for needing this resolved is that our ArchiveManager (mail archiver) is unable to log into any of the mailboxes on the new Exchange 2013 server (needs to do so in order to sort through the mail within each mailbox). There is no problem when accessing any mailbox on the 2010 server.

I'm using an Exchange 2013 SP1 environment with almost no customization. Only 2 servers exists - one holding CAS+MBX, and a second one being an MBX. No DAGs, balancers, etc. Mapi over HTTP is not enabled. The default self-signed certificates are used (no new certificate was installed, nor any self-signed certificate manually installed on any server/client). A mailbox is provisioned on a database located on the first server. Outlook is configured for the corresponding user on a client machine and started. Everything works just fine, with the 'Outlook Connection status' window showing 2 Exchange Directory + 2 Exchange Mail connections. Authentication is NTLM. Ports for all 4 connections are 6001 - which hint that Outlook Anywhere is indeed used.

From time to time, the familiar "Security Alert" comes up warning about the self-signed certificate, but this is usually traced in my experience to the various services Outlook is using, that are running on HTTPS (OAB, EWS, Availability...). 

Here we find that in Exchange 2013 "Outlook Anywhere is enabled by default, because all Outlook connectivity takes place via Outlook Anywhere". Thenhere it's stated that "Outlook Anywhere won't work with a self-signed certificate on the Client Access server". I remember the latter being true against Exchange 2010 instances, but seems not to be the case in Exchange 2013 anymore. Unless I'm missing something, from the standpoint of a default installation, the 2 articles contradict each other. 

Second issue - even though Outlook is set for "Negotiate" in its Security setting, it looks like the Kerberos preferred option is never chosen. Would it have to do with the self-signed certificate and Outlook Anywhere ?

I posted the following in Answers and was directed here.

http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/outlook-2013-to-do-bar-turns-off-after-outlook/ca912fac-6f98-4de0-a8ba-3699ee0abcba

I also ran the Outlook PSD and submitted my results. It did not find any obvious error or issue.

----

I have encountered what seems to be a bug with Outlook 2013.

First off, configuration:

Windows 7 64-bit and Windows 8 64-bit

Outlook 2013 installed as part of Office Professional Plus 2013

Lync 2013 installed and connected to Exchange server

Outlook 2013 profile connected to Exchange server

Background:

I have the To-Do Bar enabled with Calendar and Tasks. This bar stays visible and persistent through opening and closing Outlook.

Scenario:

When Outlook hangs - and this can happen randomly when creating a new message - and then I choose the option to restart Outlook, when Outlook does restart, the To-Do Bar is not enabled and then I have to re-enable the Bar. The Bar is again sticky until another hang/crash occurs.

I'd like to resolve two things:

1. Allow the To-Do Bar to be enabled as per user preference after a hang/crash.

2. Address the Outlook hang.

I would love indicate what is causing the hang/crash and indicate the steps required to reproduce it, but I'm not entirely sure. I received a notice once that the Lync add-in caused the crash and was disabled after Outlook restarted. However I re-enabled the add-in and haven't seen that add-in warning since - it's been at least a few weeks. The hang/crash occurs at least once a week and doesn't log anything in the application event log. My computer has all the latest updates as well.

These are my enabled add-ons: