Hello.  I have been working on this issue for the last three days and am at my wits end.  

On Sunday I installed Cumulative Update 1 on our Exchange 2013 Server.  It's the only Exchange server in the environment and is integrated with Server 2012 Essentials.  After rebooting from the update, autodiscover was no longer functional.  No outlook clients could log in to the server, internal or external.  Activesync is still working, so mobile clients are functioning normally, and OWA and ECP are functional both internal and external.

I have been pouring through numerous technet articles, forums, and anything else that my have a solution to my problem.  I managed to solve several issues, but every time I fix an issue a new one will crop up and send me two steps back.  Here is where I stand now:

Remote Connectivity Analyzer outputs this at the moment after the latest iisreset:

There was an issue with the EXCH Provider previously, but after trying a solution and rebooting, I now have an issue with EXPR.  Originally, I couldn't even get autodiscover to connect.  I fixed that, but keep on hitting roadblocks every step I take.

Here are some powershell outputs for reference.  Note that before I copied these, I have recreated the autodiscover virtual directory and performed an iisreset.  I also had changed the outlookprovider certprincipalname and server, but have since changed them back to $null

get-outlookprovider

Name                          Server                       CertPrincipalName             TTL
----                          ------                       -----------------             ---
EXCH                                                                                     1
EXPR                                                                                     1
WEB                                                                                      1

get-outlookanywhere | fl

ServerName                         : exchangeserver
SSLOffloading                      : False
ExternalHostname                   : mail.domain.com
InternalHostname                   : mail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://exchange.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 620.29)
Server                             : exchangeserver
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web
                                     Site),CN=HTTP,CN=Protocols,CN=exchangeserver,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First
                                     Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity                           : exchangeserver\Rpc (Default Web Site)
Guid                               : 9db72642-860f-4354-9a8e-57df4b4b6d1c
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 6/19/2013 2:07:15 PM
WhenCreated                        : 3/20/2013 2:43:54 AM
WhenChangedUTC                     : 6/19/2013 6:07:15 PM
WhenCreatedUTC                     : 3/20/2013 6:43:54 AM
OrganizationId                     :
OriginatingServer                  : domaincontroller.domain.local
IsValid                            : True
ObjectState                        : Changed

get-autodiscovervirtualdirectory | fl

RunspaceId                      : 7df1e323-86fc-46bd-9ec6-b96f483a10ef
Name                            : Autodiscover (Default Web Site)
InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
LiveIdNegotiateAuthentication   : False
WSSecurityAuthentication        : False
LiveIdBasicAuthentication       : False
BasicAuthentication             : True
DigestAuthentication            : False
WindowsAuthentication           : True
OAuthAuthentication             : False
AdfsAuthentication              : False
MetabasePath                    : IIS://exchangeserver.domain.local/W3SVC/1/ROOT/Autodiscover
Path                            : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
AdminDisplayVersion             : Version 15.0 (Build 620.29)
Server                          : exchangeserver
InternalUrl                     : https://autodiscover.domain.com/autodiscover/autodiscover.xml
ExternalUrl                     : https://autodiscover.domain.com/autodiscover/autodiscover.xml
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
DistinguishedName               : CN=Autodiscover (Default Web
                                  Site),CN=HTTP,CN=Protocols,CN=exchangeserver,CN=Servers,CN=Exchange Administrative
                                  Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft
                                  Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity                        : exchangeserver\Autodiscover (Default Web Site)
Guid                            : 02d22cf2-1ded-46d6-b647-3d1923732875
ObjectCategory                  : domain.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass                     : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged                     : 6/19/2013 2:04:43 PM
WhenCreated                     : 6/19/2013 2:03:17 PM
WhenChangedUTC                  : 6/19/2013 6:04:43 PM
WhenCreatedUTC                  : 6/19/2013 6:03:17 PM
OrganizationId                  :
OriginatingServer               : domaincontroller.domain.local
IsValid                         : True
ObjectState                     : Changed

Everything is configured and turned on.  I'm just stumped about the issue with the outlook provider.  I'm fairly certain that it has surfaced due to changes I made from fixes I found for other issues.  If I can't get this fixed by this evening, I'm probably just going to reinstall Exchange entirely and start from scratch.  Anybody have a bright idea?  Thanks in advance.

There is a user running Office 2010. She is a member of our distributed list. She receives emails when they're sent to the DL, but when she attempts to send emails to that DL, outlook states she doesn't have permission to send to that DL. Can some please assist?

Thanks.

Hi,

I am trying to publish Exchange 2010 OWA/EAS/Outlook Anywhere using TMG 2010.

Configuration detsils:

TMG 2010 has 2 NICs--Internal and External. External NIC has multiple IP asociated with it (used for multiple listener)

OWA/EAS will use basic auth and OA will use NTLM auth.

I have created 2 listerners--listener1  for OWA and EAS both  and listener2 for OA. The relevant publishing rules have also been created.

The publishing rule for OA/EAS has autodiscover.contoso.com listed in the public website along with mail.contoso.com.

I have 2 public DNS records- mail.contoso.com and autodiscover.contoso.com.

mail.contoso.com will be used for OWA/EAS/OA and is pointing to the external IP of listerner1.

autodiscover.contoso.com is pointing to external IP of listerner2 which will make the OA work. Do I also need to point the autodiscover.contoso.com to the external IP address of  listerner1 for EAS to work? Any help will be appreciated.

Regards,

Imrul Emon

This is an issue we are having with some but not all of our users..

It appears to be impacting about 60% of the accounts we have tested..

For some users the move is Successfull.. Outlook asks to restart, it does and they are good to go.

For others Outlook fails. They get the promot to restart outlook after the mailbox move is complete..

They restart and outlook stops with a Outlook cannot log on error.

THe profile looks correct with the Exchangeguid and email address.

They can log on VIA OWA without issue but not Outlook 2010.

I have run the Connectivity Analzser with on of the failed users credentials and it shows Autoconfigure passses

but it fails on Outlookanywhere.

If I gave a successfull 2013 user full control over a failed users mailbox and they can open the mailbox without any issues.

The issue also follows the user from PC to PC or thin clients. Successfull users work logged into a failed users PC. Failed users don't work logged into a successfull user's PC.

We thought it may be a Kerberos ticket size issue so we increased the HTTP parameters MaxFieldLength and MaxRequestBytes  to 65534 on all the CAS servers.

THis did not help.

I ran Netmon while I had a user try to open outlook and noted for following

Network capture on CAS during attempts show

Http: Response, HTTP/1.1, Status: Unauthorized, URL: Using Multiple Authetication Methods, see frame details

                StatusCode: 401, Unauthorized

And

Http: Response, HTTP/1.1, Status: Bad request, URL:

                StatusCode: 400, Bad request

Outlook and the sever are current on all patching.

Certs on CAS are issued from our Enterprise CA.

I cannotdelete accepts frommeeting requests in my inbox.As aworkaroundthey holddown the shift keyand delete the item permanently

ErrorMessage: "The item could not be moved., It iseither alreadymoved or deleted,or accesswas denied"

Tried thefollowing:

newoutlookprofile
Outlook/cleanviews
movedmailboxfrom one Exchange maildatabaseto another

Please help. I cannot share my default calendar. The "Share Calendar" option when I right clicked the calendar was not available. Also, there is no permission tab under properties. However, other calendar I created has the "Share Calendar" option and the permission tab in properties is available.

Hi,

starting with Exchange 2013 we have following odd thing. 

(That happens with Outlook 2010 aswell as Outlook 2013). 

My mailbox has several other mailboxes mounted aswell. (using Full Access at ECP Settings), aswell as one separate Exchange Mailbox with own User/Password. 

Now, when I have an Email with an attachment (like Word, .jpg, whatever), I used to move it to another mailbox by using "drag & drop". 

The mail was moved to the mailbox without noticable changes. 

Starting with Exchange 2013, the Mail is changed into Rich Text. That means, the attachment now appears somewhere within the message, instead as real attachment. Some attachments are also lost, and as the message was moved, the only way to recover it is using our external Email Archive. 

Is this a bug, or didn't I see any option that results in this odd behaviour?

Moving to a different folder does work as expected, but not to another mailbox.

Thanks

Patrick 

Hi there!

All of you know the reg key to set to enable the feature that will allow users with expired passwords to change their password (orchange password at next logon).
http://blogs.technet.com/b/exchange/archive/2010/10/06/so-you-want-to-change-your-expired-passwords-in-owa.aspx

On Exchange 2013 this key is set oob.

On Exchange 2010 SP1 RU3 this works fine with UPNs.

But on Exchange 2013 some of the old Problems are back! I am not able to change the Password while using UPN Logonname. Its not a Problem when using the pre-win2k logon domain\username.

UPNs still work fine for normal OWA logon.

Is there any way to resolve this issue?
On OWA virtual folder i set form based authentication to UPN.

Thanks alot and sorry for my english skills ;)

Garfield

Our company is currently running Outlook 2013 clients and an Exchange 2013 DAG environment.

Today I noticed some weird inconsistencies in the representation of phone numbers stored in my own personal Address Book.

We are testing IM UC functionality from a few different platforms and click to call is one of those features from the different programs.  In order to make this function work with all numbers - such as mobile numbers that I have configured in my address book - I need them to be in the proper format for our CUCM PBX to accept and forward.

So today I went to edit a particular contact for testing.  This contact had a full ten-digit number with area code entered into his Mobile Number field and I needed to add a 1 in front of it to have it forward properly.

To do this I clicked in the People tab at the bottom of outlook, selected the contact, and clicked the Edit button in the top right to open up fields for editing.  After pressing this most of the fields become selectable and can be edited.  The"Work Phone" field, however is not editable, and has a faint writing underneath that says "Address Book" which I assume means it is being pulled from the GAL and that is fine since we can control that on the server side in AD.

The "Mobile Phone" number is also uneditable, however, with writing underneath that says "Outlook" and this is the part that is really confusing to me.  I think it is telling me that the number is coming from Outlook - but it won't let me edit it from within outlook?  Just to be sure there was no conflict I closed Outlook on all but one computer and shut down my phone.  But this still did not allow me to edit this field.

Even more weird, if I switch within the People tab and change my Current View to any of the other view (Business Card, Card, Phone, List) the Mobile Number I am unable to edit is not even shown.  Here I can double click on the user which brings up his Contact Card and the mobile phone field is blank.  I can proceed to enter the mobile phone number with the 1 I would like for it to have and save it.  Then If I switch BACK to people view I see this new number I just created, along with the previous uneditable number, both listed as mobile numbers.

And when I click Edit again - I am able to edit the new number I created, but I am still unable to edit the previous one and it still has the Outlook tag right underneath it.

It seems like Microsoft is somehow saving these contact details in different locations and representing them different based upon the view and it is really frustrating.  I have verified this same behavior for several of our users so it basically seems like a bug in 2013 or some really weird decision making in the part of Microsoft.

Can anyone tell me how to edit or delete this persistent mobile number that it showing up in my Outlook 2013 clients?

Hi.

In Exchange 2013 when importing PST file, the EAC allow us to “Send email to the mailbox below when the .pst file has been exported”. (Note, there is typo here because it’s supposed to say “imported”).

Well, I’m trying to archived the same thing via PowerShell but the “New-MailboxImportRequest” doesn’t allow me send an email when the request it’s done.

Does anyone know how to send a notification email when the mailbox import request start and it’s finished?

Thank you.

This may seem a bit unusual, but i'd like to hear from some of the experts regarding this...

I recently discovered i can click and drag a text file into an outlook folder and it be stored within my mailbox.  Outlook recognizes them as text files.  OWA recognizes them as attachments.

I'm wondering if this is an OK thing to do with Exchange?  To click and drag to store text files straight into an Exchange Mailbox?  Is this any different than Exchange storing emails with attachments?

The reason i'm asking is that we have an old email system we've decommissioned and all emails were converted to .txt files.  We have had some requests to have access to these files which for most, we have my document redirection that we copy these files too. 

Well, we're having to deal with some "special cases."  We have users that only use workstations with generic accounts, so to grant the generic accounts access to these text files obviously means everyone using that can access.  Which all that is irrelevant to my question...

Does anyone forsee any issues with Exchange being used to store straight data text files?  Or any file for that matter that's not an email?

Thanks,

JB

[Edit: I did figure out a little more of the issue. I have figured out that what is causing this is the IIS Application Poll that The Exchange 2013 installer creates by default when installing called "MSExchangeRpcProxyAppPool". The server is recycling the RPC Application Pool every 20 - 30 minutes or so. I have recycling completely turned off  on this pool yet it still restarts which leads me to believe it may be a code problem since it only should recycle if the poll crashes. Short of a bug in the code somewhere, I for the life of me can not find why the Application Pool keeps restarting. This is the only pool out of all the ones Exchange created during installation that is recycling constantly. It is frustrating because our Outlook Anywhere clients keep getting disconnection messages several times an hour because of this. The event logs I listed below are the only event logs I can find that trigger when the pool recycles, so as you can see, they give me no useful information in debugging the problem.]

This problem only applies to outlook clients using RPC over HTTP. ActiveSync, OWA and EWS are working fine.

There is a problem with the RPC over HTTP tunnel on our server. Every 20-30 minutes, sometimes more sometimes less, but usually with in that 20-30 minute timeframe, the RPC over HTTP tunnel drops and all Outlook Anywhere clients get immediately disconnected. IT comes back up very fast and all clients reconnect with in a matter of seconds. Not a huge deal for people using cached mode outlook but all the non-cached mode people (Thin clients are an example are not using cached mode to save diskspace). People using non-cached mode would get a couple errors pop up and outlook stopped working.

The only relevant entries I have found in the exchange server event log are here. These same grouping of events show up everytime the RPC over HTTP tunnel shuts down and restarts. I just can't figure out why its doing it:

1-23-2013 9:21:18 AM RPC Proxy 4 (1)
-- RPC Proxy successfully loaded in Internet Information Services (IIS).

1/23/2013 9:22:41 AM WAS 5138 None
--- A worker process '75832' serving application pool 'MSExchangeRpcProxyAppPool' failed to stop a listener channel for protocol 'http' in the allotted time.  The data field contains the error number.

1/23/2013 9:22:41 AM WAS 5013 None
--- A process serving application pool 'MSExchangeRpcProxyAppPool' exceeded time limits during shut down. The process id was '75832'.

Hello,

After migrated mailbox from exchange 2007 to exchange 2013, Microsoft Outlook client keep freeze and rejected the password sometime it take up to 30 minutes just to login to Outlook. It was working perfectly when it was in exchange 2007.

I have uninstalled and reinstalled outlook 2010 and restarted computer many times but nothing seem to fix the problem.

Anyone have any idea why this happen? I need help.

Thank you.

Jimmy

Vincent Sprague

Hi Guys,

I have been troubleshooting the infamous “authentication/login” issue on Outlook 2010 Windows XP clients for the last three days. Today I think I finally succeeded in getting it to work, although I need to perform an odd step in order for this to work, which I need to avoid/correct and figure out what is going on, so my users do not need to perform this step during migration or initial profile logon.

I am literally stumped on this one. This has to be the most puzzling and odd issue I have come across in my I.T. career in the last 15 years. *minor rant* Damn you Microsoft! *end rant* Disclaimer: This has to be the first time I have ever said that. Wow…

Anyhow to the point, explanation and question.

On a clean XP profile (admin user or not), autodiscover successfully retrieves the clients connection details and proceeds to query me for a username and password, no combination will work at this stage (Username, UPN, Email or Domain/Username).

*here is where things begin to get interesting*

I launch Internet Explorer proceeding with the URL of OWA - the browser loads OWA, I then proceed to close the browser. No login is required at this point, just a logon screen.

I go back to Outlook launch it, autodiscover begins to do its discovery and voila, success. No login screen prompts and Outlook 2010 successfully connects to Exchange 2013.

My initial suspicion was that the purchased certificate is not being added or trusted rather by the users profile at this stage, hence loading Internet Explorer loads the certificate either into memory or some sub-system process which then allows me to authenticate via NTLM. I am not sure if this is the root cause or not, but it seems to be the only logical explanation at this stage.

I am fortunate (so to speak), it was just those out of luck attempts. “Hey, let’s try to see if OWA works – Great! OK Let’s go back to Outlook – hey what do you know, it worked”.

I have re-tested this practice over and over for the last 5 hours trying to capture system changes, nothing appears obvious in the system track changes (registry or file). I’ve made sure the profile was always fresh and can confirm that all users on Windows XP connecting to exchange 2013 have this issue. The same users on Windows 7 do not have this issue at all with Outlook 2010. Just Windows XP with Outlook 2010 connecting to Exchange 2013. Again, weirdest thing I have come across. Hopefully somebody has further knowledge about the internal working on this process that allows my XP clients to connect. I am literally baffled, perhaps been working on this issue far too long and it has fried my brain.–

P.S. The Windows clients are all fully up to date with Windows and Office updates.

Let’s hope somebody can help me make sense of this and figure out what the hell is going on.

Cheers…