Outlook 2010 / EWS

I've got a process that needs to pick up mail messages from a certain account, and we have messages from one vendor that seem to have trouble--something in their message formatting. Our workaround has been to open Outlook 2010, and move the message(s) from
the inbox to Sent Items, and back again. The external process then seems to be able to pick up the message(s). I've got a filter in place that moves the messages to the Sent items folder, and have a Powershell script leveraging EWS to move them back to the
inbox. Even though the messages are getting moved correctly, our external process can't seem to get at the messages. Would there be any significant differences between how the outlook client and EWS are acting on these messages? Really confused by this one,
the logs don't shed any light...
TIA

Hello,
Accroding to your description, I understand that you manually do it, the external process seems to be able to pick up the message, but if you use Powershell script leveraging EWS to do it automatically, the external process not work.
If so, I consider the issue may related to EWS. Please follow the Ed's suggestion.
Cara Chen
TechNet Community Support

Similar Messages

Using Outlook (2010 & 2013) to connect to Exchange using EWS

First things first.
I know that Outlook on the PC platform uses MAPI to connect to Excahnge while the Mac flavor of Outlook uses EWS, however, i was cycling through some available EX and ExO PowerShell cmdlets and found a parameter for set-casmailbox named EWSAllowOutlook Which
leads me to believe that configuring this setting should allow Outlook to use EWS to connect to Exchange. (This is a separate parameter from EWSAllowMacOutlook).
I tried a manual configuration (entering in the EWS url and setting the correct Outlook Anywhere settings) with no success.
I also tried manual configuration of an outlook.com and activesync account and entering the EWS URL as well with no success.
Has anyone successfully configured Outlook for PC to connect to Exchange using EWS and how did you configure the client?
Thanks

Hi,
Sorry for the late reply.
About the EWSAllowOutlook parameter, I have something to clarify.
This parameter allow or disallow Outlook 2007 to access EWS for the user.
Outlook uses EWS for free/buzy, OOF settings, and calendar sharing.
Outlook connect to Exchange server by using MAPI is a by design behavior.
We cannot change this.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2010 "Your automatic reply settings cannot be displayed because the server is unavailable" error

Hi,
We recently introduced a Exchange 2010 server into our Exchange 2003 enviroment but had to stop migrating users over to it after it became appartent that users using Outlook 2010 could not switch on their Out Of Office, getting an "Your automatic reply settings
cannot be displayed because the server is currently unavailable" error. However users on the new 2010 can set OOF if they use OWA or Outlook 2003!
Running the Test E-mail AutoConfiguration shows no errors with the Log tab showing Autodiscover succeeded and the Results tab showing all the correct values, including a OOF URL of
/Autodiscover/Autodiscover.xml">https://<servername>/Autodiscover/Autodiscover.xml into IE gives a XML file with a 600 error code.
I have looked at loads of 'solutions' on the Internet but cannot get this working, anyone have any suggestions?
Thank you,
Craig

Please verify IIS
settings:
======================
On Exchange CAS
server, open IIS console,
Go to default web site, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Click Autodiscover, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Click EWS, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Click OAB, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Please run IISRESET command to load the changes.
Thanks.
Tony Chen
TechNet Community Support

No Free/Busy Information for Exchange 2010 users in Outlook 2010 client, 2010 OWA shows this information fine

I have looked for hours and hours on Google and this web site for this type of issue and nothing seems to help.
Problem:
On my new Windows 2008 R2 /Exchange 2010 server with IIS7 installed, I can use Outlook 2010 client to login and send and receive e-mail but when I try to busy search internal Exchange users I get no information (cross-hatch), but the sender of the Meeting Request
can see their own free/busy information fine. And OWA users can see free/busy information fine, as can Outlook 2003 client users against this Exchange 2010 server when logged in.
I don't know if I have a certificate problem with regard to IIS7 or Exchange 2010, I did not create my own certificate , it is just what was installed by default when I installed and configured Win2K8 server, IIS7 and Exchange.
On the Windows 7 workstations with Outlook 2010 client, I am not logging into the Exchange 2010 server DNS domain, if that makes any difference. On these workstations I can ping "autodiscover.my.exchange.server.com" and my.exchange.server.com
with no problem. I even used this Microsoft KB to install a new _autodiscover dns entry, but it did not help :
When I turn on logging on my Outlook 2010 client, I see this in my C:\Users\Administrator\AppData\Local\Temp\1\outlook logging\20131208-135658864-fb.log :
2013/12/08 13:56:58.864: Getting ASURL
2013/12/08 13:56:58.864: URL returned from cached autodiscover: blah blah
2013/12/08 13:56:58.864: Request to URL:
2013/12/08 13:56:58.864: Request action:
2013/12/08 13:56:58.864: Request XML: <?xml version="1.0"?>
2013/12/08 13:56:59.051: Request sent
2013/12/08 13:56:59.051: Response error code: 00000000
2013/12/08 13:56:59.051: HTTP status code: 0
2013/12/08 13:56:59.051: -------------------------------
2013/12/08 13:56:59.051: There is an error in request/response.
2013/12/08 13:56:59.051: XML response:
2013/12/08 13:56:59.051: -------------------------------
2013/12/08 13:56:59.051: Getting ASURL
2013/12/08 13:56:59.644: Failed to get ASURL. Error 8004010F
At an Exchange shell console I enter this command and get these results :
Exchnage Management Shell :
VERBOSE: Connecting to BPExchange2010.my.exchange.server.com
VERBOSE: Connected to BPExchange2010.my.exchange.server.com.
[PS] C:\Windows\system32>Test-OutlookWebServices -id:[email protected] -TargetAddress:[email protected]
ll.com
RunspaceId : c929eacd-d53c-49d7-8532-c4b74e61b8be
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is
Type : Success
Message : [Server] Successfully contacted the UM service at https://bpexchange2010.my.exchange.server.com/ews/exchan
ge.asmx. The elapsed time was 234 milliseconds.
[PS] C:\Windows\system32>
** Also frequently when I log into Outlook 2010 client and start to send a meeting request , I get the Security Alert dialog :
autodiscover.my.exchange.server.com
Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
Green Check Mark : The security cerficate is from a trusted certifying authority
Green Check Mark: The security certificate date is valid
Red X : The name on the security certificate is invalid or does not match the name of the site.
Do you want to proceed ? . I either import the certificate or click YES, but does not help this issue.
NOTE: Each user that shows as NO INFORMATION cross-hatch, these users have appointments and have logged into outlook before.
When I do this autodiscover url from a Windows 7 pc with outlook 2010 I get :
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="14:47:01.5656198" Id="401440650">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Can anyone assist ? What am I missing ?
Thank You
NOTE: When will this go away. I had to strip out a lot of helpful information to post this. "Body text cannot contain images or links until we are able to verify your account."

Hi,
How many users encounter this issue, all users with Outlook 2010 or some specific users?
According to your post, the Error code 600 indicates that your Autodiscover service is working well. as for the certificate mismatch issue, we can also following the KB below to resolve it:
http://support.microsoft.com/kb/940726/en-us
The Free/Busy information in Exchange 2010 is using the Availability service to
retrieve it. Please directly access
https://mail.mydomain.ae/EWS/Exchange.asmx in IE and see whether a proper XML file is returned.
Or we can go to
https://testexchangeconnectivity.com and check MS Exchange Web Services Connectivity Tests.
Thanks,
Winnie Liang
TechNet Community Support

Outlook 2010 Certificate does not match

I have a problem with a new installation of Exchange 2013 on a Windows 2012 Server. Most of the clients are Outlook 2010.
All the internal users are getting the error message:
"There is a problem with the proxy server's certificate. The name on the security certificate is invalid or does not match the name of the target site exchange2013.myinternaldomain.local
This is shortly followed by another box "the name on the security certificate is invalid or does not match the name of the site"
Of course the issue is my purchased SSL certificate is MAIL.REALDOMAIN.ORG while the server's name is exchange2013.myinternaldomain.local
With Exchange 2010 servers I have deployed I have had success following KB article 940726 but this time it didn't fix it with Exchange 2013.
There must be a solution!
I found this article:
http://support.microsoft.com/kb/2783881 the first suggestion from MS were impractical and the registry edit didn't work either (plus the thought of going to all my clients to do a registry
fix doesn't make me happy!)
I tried creating a local DNS zone for my external domain name and pointing to the internal IP but that didn't fix it.
In the ECP under the Outlook Anywhere section -- "*Specify the internal host name such as contoso.com that users will use to connect
to your organization:" I changed the internal host name to the external .org address but this caused Outlook clients internally not to work.
I used the -AutodiscoverServiceInternalUrl command to point it to the .org address on the certificate but didn't work either.
I have a service record in both external and internal DNS pointing to the mail.realdomain.org address.
Any other suggestions?
Thanks in advance!
Mike

Thanks for the information. I actually finally got this resolved a few weeks ago by speaking directly with a Microsoft technician. I am going to post what finally fixed my problem with the hopes that it will help others in my position.
Again, the problem which I am sure is common is a .local domain internally and a "real" domain on the outside. The solution that the MS tech had me do was to simply point EVERYTHING both internally and externally to the external host name - the one that
matched the certificate I had.
I'm surprised this solution isn't found elsewhere - it seems so obvious.
He had me run an number of commandlets which I will post here - with the caveat that they were for my environment! (I've masked my real domain name and substituted - mydomainame.org)
Set-Webservicesvirtualdirectory -Identity "EXCHANGE2013\ews (Default Web Site)" -InternalURl
https://mail.mydomainname.org/ews/exchange.asmx
Set-OutlookProvider EXCH -CertPrincipalName msstd:mail.mydomainname.org
Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.mydomainname.org
Set-OutlookAnywhere -Identity "EXCHANGE2013\Rpc (Default Web Site)" -InternalHostName "mail.mydomainname.org" -InternalClientsRequireSsl $True -InternalClientAuthenticationMethod NTLM
Set-Webservicesvirtualdirectory -Identity "EXCHANGE2013\ews (Default Web Site)" -InternalURl
https://mail.mydomainname.org/ews/exchange.asmx
Set-OutlookAnywhere -Identity "EXCHANGE2013\Rpc (Default Web Site)" -ExternalHostName "mail.mydomainname.org" -ExternalClientsRequireSsl $True -InternalClientAuthenticationMethod NTLM --ExternalClientAuthenticationMethod NTLM -IISAuthenticationMethods
Basic, NTLM, Negotiate
Set-OutlookProvider EXCH -CertPrincipalName msstd:mail.mydomainname.org
Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.mydomainname.org
Set-OutlookAnywhere -Identity "EXCHANGE2013\Rpc (Default Web Site)" -InternalHostName "mail.mydomainname.org" -InternalClientsRequireSsl $True -InternalClientAuthenticationMethod NTLM
The last thing we did was ADD in DNS on the internal DNS server the mail.mydomainname.org and point it my Exchange Server private IP (192.168.1.2) If you do the whole host name and not just mydomainame.org it wont mess up access to say an external
website.
hope this helps!

Outlook 2010 Mail Tips Could Not Be Retrieved / Out Of Office Doesn't work too.

Hi,
We have a small set up with 5 pc's and 1 server. All of the workstations are exactly the same.. specs,OS,software etc...
One of the users is currently experiencing "Mail Tips Could Not Be Retrieved" issue.
It shows up right above the SEND button when replying or sending a new e-mail.
Also Out Of Office / Automatic Replies function does not want to work as well. It asks me to try again later cause the server is not responding.
The funny thing is that this is happening only to a single user.
Here is what I've tried:
- Tested E-Mail AutoConfiguration - Autodiscovery works fine and points to the right directory.
- Deleted the profile and recreated it ... didn't work
- Added the same mailbox to another computer - IT WORKED
- Checked all the SSL settings for each virtual folder in IIS and they are all set to IGNORE the certificate.
The other strange thing is that when I try to download the OAB from the affected PC a credential window pops up and asks for the username/password
of the particular mailbox.. Once I enter them the "Mail Tips could not be retrieved" message disappears and Out Of Office is accessible and ready to be used.
Maybe Outlook 2010 setting or registry value ?

This sounds like an authentication issue for the Autodiscover/EWS URLs and your last paragraph basically confirmed it.
Is this PC domain joined and is this user logging on with his domain credentials and not locally to the computer?
Is the user able to access:
https://autodiscover.domain.com/autodiscover/autodiscover.xml
or
https://domain.com/autodicover/autodiscover.xml
An xml-page should be returned with ErrorCode 600 Invalid Request.
Is there a TMG or UAG server involved here?
Also check the proxy settings in Internet Options (if configured/required).
Robert Sparnaaij
[MVP-Outlook]
Outlook guides and more: HowTo-Outlook.com
Outlook Quick Tips: MSOutlook.info

Outlook 2010 authentication pop up box won't go away

After we applied the latest round of Windows Updates to our guinea pig workstations, we discovered that one of them caused something to break in Outlook 2010. We are set to use AD auto detect authentication on a local Exchange 2007 server. The pop
up window has varied, and nothing we have done has fixed it, not even uninstalling all the patches. (After the first workstation had the bug, I installed the patches one at a time and determined its KB2553248 that breaks it.)
Mail flows normally and we can send and receive without any problems. The pop up box can be sent to the back but cannot be minimized.
Mine says:
Windows Security
Microsoft Outlook
Connecting to (my AD email address)
The OK button is grayed out. Hitting the Cancel button breaks the connection to Exchange, and causes "Connected to Microsoft Exchange" to change over to "Need Password" on the bottom toolbar. Clicking "Need Password" logs me in within a few seconds
without any further prompting.... but within five minutes the pop up box is back.
On the other user's computer, the pop up box says:
Windows Security
Please Insert a Smart Card
and prompts for credentials if she hits OK. Like my pop up, the window can be ignored and mail flows normally. If she hits cancel, her connection to Exchange breaks until she hits "Need Password" at which point she's logged right back in again.
Interestingly, her Outlook was never configured to authenticate with a smart card. Like mine, it's set to Auto Detect connection type and to configure with the Windows AD login information.
We're holding off deployment of KB2553248 until we have a fix for this. Although it does not impede mail flow it's annoying as heck, and our clients that use Outlook (all 500ish of them...) are sure to click Cancel and break their connection to Exchange
without knowing to click the Need Password again.
How can we hide this pop up box?

OK...update on my issue (which is now RESOLVED!!!) since other people may did what I did.
I looked at the following link:
http://demazter.wordpress.com/2010/02/09/outlook-continually-prompting-for-username-and-password-2/
None of the above worked...even the kerberos method.
OL 2010 pop up box didn't say anything about connecting to where. So I looked closely at the popup box for OL 2007...keeps on saying connecting to mail.company.com. I was wondering why OL was trying to go outside instead of exch2010.domain.local
even though my account settings/profile is set to exch2010.domain.local.
As I was reading an article on SCP and how to locate it using adsiedit (which I couldn't figure out how),
http://blogs.msdn.com/b/douggowans/archive/2007/06/28/serviceconnectionpoints.aspx
This line in the blog got me thinking:
This url can be changed using the set-clientaccessserver cmdlet with the parameter -AutodiscoverServiceInternalURI.
That InternalURI got me thinking. When I looked at a txtfile that I jolted down and saved of what I did during the install of Exch 2010,
Set-ClientAccessServer -Identity "exch2010" –AutodiscoverServiceInternalURI
https://mail.company.com/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity "exch2010\EWS (Default Web Site)" –InternalUrl
https://mail.company.com/EWS/Exchange.asmx
Set-OABVirtualDirectory -Identity “exch2010\OAB (Default Web Site)” -InternalURL
https://mail.company.com/OAB
I figured, let's try changing them to:
Set-ClientAccessServer -Identity "exch2010" –AutodiscoverServiceInternalURI
https://exch2010/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity "exch2010\EWS (Default Web Site)" –InternalUrl
https://exch2010/EWS/Exchange.asmx
Set-OABVirtualDirectory -Identity “exch2010\OAB (Default Web Site)” -InternalURL
https://exch2010/OAB
I entered those commands in EMS and executed them...then I loaded up OL 2010 and OL 2007. It's been 30 min and nothing has popped up!!!
Silly me..I think why I did mail.company.com was that I was following a couple of guides that were posted out there on the internet on exchange 2010 and they just entered mail.company.com into there. But I think their guides are for networks where
the internal domain and external domain are the same. ie company.com for both insdie and outside.
I am going to install KB2553248 back onto my Win 7/OL 2010 workstation and see if that breaks it.

Free Busy takes over 30 seconds to retrieve on Outlook 2010 using Exchange Server 2010

We have a small 100 user domain running Exchange server 2010 and outlook 2010 clients. The issue is that Retrieving Free/Busy takes over 30 seconds.
So someone is trying to schedule a meeting has to wait Minutes see the Free/busy time for many users.. I have checked and all the users in question have published at least one month free busy time.
It seems it would be much faster. Anyone have this same experience and know of a way to speed it up?
thanks in Advance
David

Hi David,
Does the issue happen in OWA? In Exchange 2010, the free/busy information is retreved by using Availability service (EWS url). Generally, if a user wants to view free/busy information when create a meeting, the http Availability service request
would send to CAS server.
Please check whether the usage in Exchange server is high when the slow free/busy information occurs. This reflect time would also be related to the network in your environment.
Regards,
Winnie Liang
TechNet Community Support

Users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply

Hi All,
Please help me.
I have an issue where users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply. But they are can set Out Of Office automatic reply from OWA. My exchange server is Ms Exchange 2010.
The test E-mail AutoConfiguration failed with this error:
Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml starting
GetLastError=12175; httpStatus=0.
Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
GetLastError=12007; httpStatus=0.
Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
Local autodiscover for mydomain.com starting
Local autodiscover for mydomain.com Failed (0x8004010F)
Redirect check to http://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
Srv Record lookup for http://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x80072EE7)
Srv Record lookup for mydomain.com starting
Srv Record lookup for mydomain.com Failed (0x8004010F)
Any idea?
Thanks,
Pieter

OK.
Please follow this step.
1. As you said you are in coexistence step , so for now all endpoint already point to Exchange 2010 right?
2. Check legacy owa redirect that you already configure
3. In Exchange 2010 , Make sure that you already configure "Autodiscoverinternaluri" by this command set-clientaccessserver -identity "servername" -autodiscoverinternaluri
https://autodiscover.domain.com/autodiscover/autodiscover.xml. and don't forget to create autodiscover record in DNS
4. in Exchange 2010 , Make sure that you already configure "EWS" path by this command set-webservicesvertualdirectory -identity "XXX\Default web site name" -internalurl
https://yourinternalurl/EWS/Exchange.asmx -externalurl https://yourexternalurl/EWS/Exchange.asmx
5. don't forget to replicate freebusy from Exchange 2003 to Excahnge 2010 via public folder.
You error look like client cannot get autodiscover process please check it again.

Outlook 2010 Scheduling Assistent - No free busy information can be received.

Folks:
I have recently upgraded to Outlook 2010 running on Windows 7 x64. My email is exchange based. My machine is not a member of the domain my exchange server is in.
I access it my a stored credential.
Everything is fine except for Scheduling assistant. All the folks invited to a meeting (except for myself) show up as "No Information Available".
I have found plenty of posts that suggest this is also a Outlook 2007 issue, and that creating a key HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Calendar\UseLegacyFB
(value 1) solves the issue. (Example:http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/c765605d-27a7-4784-993c-925394e2e09f) I did create the key on my Outlook 2010 machine - but in HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options\Calendar
key. It is not resolving my issue.
Does anyone know the Outlook 2010 solution to this issue? Note: I have Administrative privilege on my Client - but no privilege on the server. I need to get
Outlook 2010 to interface with Exchange 2007.
John

Hi John,
Thank you for using Outlook IT Pro Discussions forum.
From your description, I understand that you are using Outlook 2010 and Exchange account.
There is no free busy information when using scheduling assistant. If there is any misunderstanding, please feel free to let me know.
First, you must be using an Exchange server and everyone must publish their free/busy information.
Check from File > Options > Calendar Options > Free/Busy Options.
Make sure the month value for publishing is not zero.
Also, I found a similar thread here:
http://social.technet.microsoft.com/Forums/en-GB/exchangesvradmin/thread/5991f3b6-f0cc-432f-82c6-f24da0a42862
You can also try the suggestions in that thread to recreate the web services virtual directory
===============
1. Remove-WebServicesVirtualDirectory -identity "Servername\EWS (Default Web Site)" -identity "Servername\EWS (Default Web Site)"
2. IISReset –noforce
3. New-WebServicesVirtualDirectory
4. IISReset –noforce
If this problem persists, it might be related to some settings on the Exchange server side. You can also post this thread in Exchange server forum:
http://social.technet.microsoft.com/Forums/en-GB/exchangesvradmin/threads
Please take your time to try the suggestions and let me know the results at your earliest convenience. If anything is unclear or if there is anything I can do for
you, please feel free to let me know.
Best Regards,
Sally Tang

Fixing Internal SSL Certficate Warnings in Outlook 2010

Installed 2013 SP1.
We have a Split Domain Foobar.local and Foobar.com
We got a Certficate for Foobar.com
All is good on the public side.
All is good on the internal side except for Certificate Warning User has to keep saying yes to.
We understand the problem but none of our fixes work.
1) We know if inhouse domain was foobar.com it would work. We prefer not do that. We know it could be renamed as well.
2) We could live with installing certificate on each client (only 20 or so). But it does not work. Prefer not have to do anything special on each client.
3) We changed virtual Directories in ECP to use http on Internal instead of https (basically how old server was). No go.
4) We unchecked requires SSL in IIS on OWA, Autodiscover, EWS. No go.
5) We could get an internal Certificate but that won't be allowed in Nov 2015 and cost extra money.
6) Outlook 2013 works. Outlook 2010 and 2007 pop warnings. Somehow Outlook 2013 knows !!
7) We could run our own CA but that seems really overkill.
I get a little worried disabling SSL stuff as it might allow something external to not use SSL.
How do admins typically deal with this?
Even with SSL not required and set to http on virtual directories you can see clients are still connecting with SSL.

Thanks Martina It Worked !!
What threw us off is in ECP (easier) you could not set the Internal URI on Autodiscover.
You have to do AutoDiscover in powershell.
Also some virtual directories have been renamed or replaced.
So we did what made sense (owa, ews, etc.) [I forget which, need to recheck things]
I think the real culprit was AutoDiscover, the only one we missed because ECP has no access.
So in total:
You must do the DNS thing (forward zone mail.contoso.com -> NETBIOSNAME IP Addr)
In ECP Virtual Directories Set most Internal URL's
from netbiosname.mydomain.local to mail.contoso.com (leave it https).
You must do the same to AutoDiscovery using Exchange PowerShell (not accessible in ECP)
Set-ClientAccessServer -Identity <NETBIOSNAME> -AutodiscoverServiceInternalUri
https://mail.contoso.com/autodiscover/autodiscover.xml
Change Internal URL on Outlook Anywhere in ECP -> Servers -> YourServer -> Outlook Anywhere from netbiosname.mydomain.local to mail.contoso.com

IP Virtualization - Outlook 2010 unable autoconfigure

Hello!
I have a problem with Outlook 2010 and Exchange 2010 on the MS Windows Server 2008 R2 RDS (RD Session Host) with users sessions IP-Virtualization. Outlook does not detect username (and email address) when user launch Outlook first time. If user
manually enter all user parameters then Outlook works fine, but Outlook must do it automatically (Outlook_unable_detect_username.jpg). Without IP-Virtualization on the RD Session Host Outlook 2010 successfully detect username when first launched (Outlook_success_detect_username.jpg).
DHCP-server - Cisco Catalist Switch 3750.
Help me, please, with this problem.
Thanks,
Andrew.
P.S. I unable attach the images to request

Hi!
I do not agree that this topic should be moved to Exchange 2010 because without RDS IP-Virtualization Outlook Autoconfiguration test processed successfully. And with RDS IP-Virtualization after Outlook manually
configuration autoconfiguration test successfull too.
The results of "Test-OutlookWebServices" command:
[PS] C:\Windows\system32>Test-OutlookWebServices -Identity: testuser01 @ rusdel.ru
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1019
Type       : Information
Message    : Обнаружена допустимая точка подключения к службе автообнаружения. URL-адрес автообнаружения для данного об
             ъекта: https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1006
Type       : Information
Message    : Служба автообнаружения подключится по URL-адресу https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1016
Type       : Information
Message    : [EXCH] Для данного пользователя настроена служба AS в ответе автообнаружения, полученного от https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1015
Type       : Information
Message    : [EXCH] Для данного пользователя настроена служба OAB в ответе автообнаружения, полученного от https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1014
Type       : Information
Message    : [EXCH] Для данного пользователя настроена служба UM в ответе автообнаружения, полученного от https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1016
Type       : Information
Message    : [EXPR] Для данного пользователя настроена служба AS в ответе автообнаружения, полученного от https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1015
Type       : Information
Message    : [EXPR] Для данного пользователя настроена служба OAB в ответе автообнаружения, полученного от https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1014
Type       : Information
Message    : [EXPR] Для данного пользователя настроена служба UM в ответе автообнаружения, полученного от https : // <dns_name_CAS>/Autodiscover/Autodiscover.xml.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1022
Type       : Success
Message    : Проверка службы автообнаружения успешно завершена.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1024
Type       : Success
Message    : [EXCH] Связь со службой AS успешно установлена в https : // <dns_name_CAS>/EWS/Exchange.asmx. Истекло99 миллисек.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1026
Type       : Success
Message    : [EXCH] Связь со службой UM успешно установлена в https : // <dns_name_CAS>/EWS/Exchange.asmx. Истекло560 миллисек.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1024
Type       : Success
Message    : [EXPR] Связь со службой AS успешно установлена в https : // mail.<dns_domain_name>/ews/exchange.asmx. Истекло 109 миллисек.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1026
Type       : Success
Message    : [EXPR] Связь со службой UM успешно установлена в https : // mail.<dns_domain_name>/ews/exchange.asmx. Истекло 15 миллисек.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1124
Type       : Success
Message    : [Server] Связь со службой AS успешно установлена в https : // <dns_name_CAS>/ews/exchange.asmx. Истекло 62 миллисек.
RunspaceId : 67e7c22d-c653-43f9-bf3b-7c92d269540e
Id         : 1126
Type       : Success
Message    : [Server] Связь со службой UM успешно установлена в https : // <dns_name_CAS>/ews/exchange.asmx. Истекло 15 миллисек.
Thanks!

Errors Sharing Calendar in Outlook 2010

Hello,
I have an issue with sharing calendars to someone that is in the same Exchange org on Exchange 2013 CU3 when using Outlook 2010. When trying to share I get this error message:
"Error while preparing to send sharing message"
The exchange org that I'm trying to connect to is published from behind a TMG deployment, and effectively everyone is an external user. I've tried doing a wireshark packet capture at the time when I get the error, and from the information I see, it looks
like its trying to connect to the right target. At the same time, if I watch the TMG logs as I'm generating this error with a filter to see all IP from the address of my connecting location) I see no attempt to connect to TMG at all.
I've checked in the event log of the work stations I'm using (tried more than one) and I get an event ID 300, which basically just states the same message as above, with P1 value of 301931, P2 value of 14.0.7015.1000, P3 value of 634y and P4 value of
0x80004005.
I've found an article for this exact same issue that applies to Outlook 2007, so I'm wondering if it's basically the same issue, but Microsoft haven't spotted or updated the article:
http://support.microsoft.com/kb/2836889
I've found this article (and more) but none do the trick for me:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26529686.html
I've also seen one that asks to check whether the DB is corrupt and to check autodiscover, but an exchange connectivity test against my domain comes back all green. I've also tried to make the same check with the same client against an Office 365 mailbox
and Outlook 2010, and I do not get the error there (guess it might be because they're using different authentication mechanism). I've tried a few things (patching Office 2010 up to the latest SPs and updates, updating the client with .Net updates, installing
.Net 4.5.1( but none work for me.
I've also found that this is not an issue if using Outlook 2013.
Does anyone have ideas on what might be the cause of this?
Thanks

One thing that I'm sometimes seeing when I hit the send request from Outlook 2010 is a line in the TMG log that indicates it's going to
http://domainname/autodiscover/autodiscover.xml (where 'domainname'
is the real domain name in use). We have a rule for this with a /* path that directs traffic off to another set of servers not related to email at all. I think I'm going to try adding a rule above this one with /autodiscover/* as the only path,
and do a deny/redirect to the full autodiscover address.
Incidentally, if I run a wireshark capture when doing this from an Outlook 2010 client, I see that its trying to hit the HTTP address of my TMG server, but I see no traffic at the TMG server (not from the log view anyway). If I do the same from an Outlook
2013 client, I see wireshark trying to hit the same HTTP listener address, but at TMG I see an EWS lookup.
I'll update when I've tried the new TMG rule.

Lync 2010 and Outlook 2010 cannot save conversation history

I have a user that is having issues saving their conversations to Outlook 2010. It is isolated to 1 user and follows that user no matter what machine they log into. They have the feature turned on to save their conversations to outlook and i even see the
conversation history start to queue up, but it will not get sent to outlook. The issue 2 weeks ago for them and as far as i can tell nothing was done to their account.

Hi,
Lync client save the conversation history to outlook through EWS, If the EWS is not possible it will go through MAPI. So please check the user's lync client Configuration Information, make sure the EWS deploy is OK and you can find the EWS URI.
You also can try to change the EWSFindCountLimit for this user.
New-ThrottlingPolicy –Name LyncClientPolicy –EWSFindCountLimit $null
Set-Mailbox -Identity usermailAddress –ThrottlingPolicy LyncClientPolicy
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.

Search Folders in Outlook 2010

Hi,
Is it possible to create custom search folders for Outlook 2010 from Exchange 2010?
Thanks
Anil Chauhan

Hi Anil Chauhan,
Based on my knowledge, it is possible to create search folder using EWS.
About how to create search folder using EWS, I recommend you ask in Exchange Development forum which is staffed by more experts specializing in this kind of problems. You can get better help there. Thanks for understanding.
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrdevelopment
Besides, here is a related article for your reference.
http://gsexdev.blogspot.com/2011/09/create-search-folder-using-ews-managed.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software
or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Belinda Ma
TechNet Community Support

Outlook 2010 / EWS

Similar Messages

Maybe you are looking for