Outlook advanced search & Exchange 2013 - "Sent to...." field doesn't work correctly in online mode?

Hello,<o:p></o:p>
We've come across what seems to be a problem with advanced find in Outlook in online mode, when used with Exchange 2013. 
Using the "Messages" tab of "Advanced Find", anything typed into the "Sent to...." field produces no search results.  If the field is populated by clicking
"Sent to..." and selecting a name from a contact list or GAL, results are returned. 
eg. 
Sent items contains messages to "Charlie" who has the email address
[email protected] and sender is
"Dave" who has the email address
[email protected] 
Entering "charlie" or
[email protected], (or any previously acceptable partial term such as "charl" or "@contoso.com") into the "Sent to"" field produces no results.  If the user exists in a contact
list and is selected from it, the search works fine.  The same is true searching the inbox, using the local user's id of "Dave" or
[email protected]
We've confirmed this issue occurs at four client's sites, plus our own internal Exchange 2013 CU3 system.  Four of the sites have been transitioned from Exchange 2010, the fifth was a completely new installation.  The problem occurs with Outlook
2007, 2010 and 2013. 
This works fine in cached mode (not a solution as our clients are predominantly Citrix/RDS).  Exchange search doesn't report any issues and the index states are all "healthy",
we've also tried rebuilding the indexes with no improvement.
Any ideas would be appreciated, or even if someone else can confirm they see the same thing.
Thanks.

Hi Winnie,
Thanks for your reply, and I'm sorry I've not responded earlier.  While this problem is one that's annoying several of our clients, and while I have been doing further testing and investigation, it's had to take a back seat to other more pressing issues
until now.
OWA search works fine, as does using "From:" in instant search, and the "From" query on the Advanced tab in Advanced Find.  The search services have been restarted, indexing state and copy status etc are all healthy, the indexes
have been rebuilt/reseeded, and I've gone through the diagnostics again.  Nothing is logged in event viewer, and the only error that comes up when checking failed index docs for a user are for unsupported format handlers (.png etc).
The issue seems purely to be with the "Sent to..." field on the Messages tab, it's as if it gets completely ignored.  The search returns instantly with "There are no items to show in this view".  Just to make sure I wasn't losing
my marbles, I've compared searches on Exchange 2007 and 2010, and on those I can enter as little as a single letter or email domain and receive the expected results.  On 2013 I get nothing whatsoever whatever I enter, unless I pick an address from a contact
list.
At this point, I thought that since Office 365 is Exchange 2013 based it'd be worth testing that, and sure enough I got exactly the same issue.  I setup an Office 365/Outlook 2010 profile on a machine that is currently in an existing Exchange 2010
environment where search works correctly, searching Office 365 doesn't work on that either.
EDIT - Ignore this bit, a fresh install of Windows 7 and Office 2010 doesn't work with Office 365 either.  I am exploring another avenue.  I setup a fresh Windows 7 VM, installed Office 2010 and connected that to Office 365, search worked fine,
so I'm now looking into what the difference with that VM and the servers and workstations out "in the wild" could be.  For example, the test VM isn't on a domain, it's not fully patched, it has no additional software installed etc.  Outside
of Microsoft applications and operating systems and having similar configurations, I haven't isolated a common link across all of our client sites that are affected, there's no single 3rd party application or anti-virus solution in place at all of them for
example. 
I'll update with any findings, but if you or anyone else has any idea in the meantime I'd be grateful for your input.
Regards.

Similar Messages

  • Office 2013 Sent To Mail Recipient Not Working Correctly.

    I have Office 2013 running in a 2008 RDS farm. Im having a strange issue where if I right-click a file and use the Send To Option:
    It prompts me with this:
    The strange thing it works just fine when Outlook is closed. Any ideas on this strange issue? 

    Hi,
    I wasn’t able to see the issue with the prompted window. Are you able to send email message after input correct email account credentials?
    If you are wondering what the FIXMAPI 1.0 MAPI Repair tool is for, it is used to detect and aid in resolving conflicts with Messaging Application Programming Interface (MAPI) files that may affect your ability to send and receive mail and faxes from other
    programs.
    More information for you:
    Description of the Fixmapi.exe Tool Included with Internet Explorer 5
    https://support.microsoft.com/en-us/kb/kbview/228457
    You receive an error message if a file conflicts with the MAPI file on your computer when you start Outlook 2007 or Outlook 2003
    https://support.microsoft.com/en-us/kb/813602/id-id
    In addition, since we are not familiar with Outlook, if there is any Outlook/mail specific query, please refer to Outlook IT Pro Discussions forum below to get more efficient support:
    https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • In CRM IC the search pop up for 'To' field  doesn't work

    Hi,
    I have a case management scenario in IC CRM 4.0 , where i go and search for a consumer in Identify account screen. On clicking 'Confirm' for the consumer i go to navigation link 'Email/ Letter' and try to create a new Email. On the 'To' field i click and a F4 search opens for Partner addresses. On clicking 'Find' on it nothing happens.
    I saw the code of Mailheader.htm  but nowhere is mention of the F4 link popping up. I have to make this search help work but debugger doesn't take me in. I put breakpoints at PartnerSearch.htm also but nothing work.
    Does anybody has idea.
    Regards
    apoorva

    Hi,
    Just in case, have you tried using external breakpoints for the debugging purposes.
    Rgds,
    Rajiv

  • I have got Acrobat 10.1.13 for Mac running Yosemite - and the 'advanced search' feature has stopped functioning - it doesn't install the search window, nothing happens - so I uninstalled acrobat, reinstalled it - but it still not working?

    I have got Acrobat 10.1.13 for Mac running Yosemite - and the 'advanced search' feature has stopped functioning - it doesn't install the search window, nothing happens - so I uninstalled acrobat, reinstalled it - but it still not working?

    It's a 3rd party app.  You really should contact Adobe Support and/or post in the Adobe Forums
    Mac OS X (10.6.6)
    Use Software Update or the OS 10.6.8 combo update to update your OS.  Also, update everything SU has to offer for your computer.  When done, repair permissions and restart your computer.

  • Outlook 2010 - 64 bit, Windows 7 64 bit, doesn't work ?

    I am using Photoshop Element 8 with Windows 7 English Versuin 64 bit, I installed in the past Office 2007 32 bit and Office 2010 32 bit, with office 2007 32 bit every thing works well, I am talking about sending email through Outlook, I don't remembre if I tried to send emails with Outlook 2010 32 bit, but at the moment I am workin with Office 2010 64 bit and I choose in the E-Mail Settings - the E-Mail Client the Microsoft Outlook, The Microsoft OUtlook is my default email client, but !!!  when I try to send pictures from the Photoshop Elements I get an error that I have to choose the Outlook as the DEFAULT EMAIL CLIENT. so I am using now the Adobe E-Mail Service.
    Is this a BUG ? Can I fix this problem ?
    Please your HELP.
    Have a Good day and congratulationsto Uruguay !
    Eli

    Hello
    Thank you for your help
    This is exactly what I did but it doesn't work.
    Best regards
    Eli
    [email protected]
    Date: Tue, 6 Jul 2010 22:15:07 -0600
    From: [email protected]
    To: [email protected]
    Subject: Outlook 2010 - 64 bit, Windows 7 64 bit, doesn't work ?
    Hi Eli,
    Can you try setting the outlook as Default email client. Here are the steps to achieve this -
    Start Internet Explorer.
    Select Tools | Internet Options from the menu.
    Go to the Programs tab.
    Make sure Microsoft Office Outlook or Microsoft Outlook is selected under E-mail.
    Click OK.
    Now please see if you face any issue using Outlook in PSE.
    Thanks,
    Sourabh
    >

  • My "sent mail " tone doesn't work. All other tones do work.   I've changed tones and rebooted. Still silent

    "sent mail" tone doesn't work. All other tones do. What to do?
    ILive changed tones and rebooted

    Hi Gwing17,
    Welcome to the Apple Support Communities!
    I understand that all of your iPhone sounds are working as expected except for the Sent Mail sound. I understand that you have already changed the Sent Mail sound as well as reset your iPhone and the issue persists. In this situation, to isolate the issue, I would first recommend backing up your iPhone to either iTunes or iCloud.
    Back up and restore your iPhone, iPad, or iPod touch using iCloud or iTunes - Apple Support
    After you have backed up, I would recommend restoring your iPhone and setting it up as new to test the Sent Mail sound. If the sound works as expected, try restoring from your backup and test the sound again. Please let me know if the issue returns or if the sound still does not work when you set up your iPhone as a new device.
    Use iTunes to restore your iOS device to factory settings - Apple Support
    Cheers,
    Joe

  • Index (search button) in finder and mail doesn't work after installing mountain lion, index doesn't work after installing mountain lion

    after I up grade to mountain lion search button in finder and mail doesn't work: when I search from something the result is "zero"
    How can I solve this problem? thank you

    Try:
    sudo mdutil -E /
    which rebuilds spotlight and search indexes on the volume.

  • Outlook disconnects from Exchange 2013 several times an hour.

    [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'.
    I have been searching for weeks on the problem and all I really have found is that the problem can sometimes be caused by RPC timeouts so I set the RPC timeout on the server to 120 seconds via the registry. That actually helped for about 5 days and then the
    problem mysteriously came back and I can not get it to go away even though the registry value is still set to 120 seconds on that RPC time out.
    Does anyone else know of any thing else that causes this? Its Exchange 2013 on Server 2012 and is a pretty fresh install. Was setup in mid-December.
    --Trent W.

    Hello,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Thanks,
    Simon Wu
    TechNet Community Support
    Have you had any luck diagnosing the problem?

  • Can't add multi exchange account on outlook 2010 with exchange 2013 Sp1

    I did install exchange 2013 with DAG group successful, the exchange work fine now
    Outlook can connect to exchange automatically and working fine
    The problem appear when i need create the second exchange account by go to control panel/Mail add new profile and add new exchange profile
    How can i solve the problem ?

    This Problem in exchange generally appear when users mistakenly create the wrong account type or Outlook upgrades an older account profile.In these situations you need to remove that wrong account and  create a New account .
    When you have the wrong type of account configured in Outlook you can easily remove the account and create the correct type of account. 
    1 Go to Control Panel, search for the Mail. If you are using 64-bit Windows and 32-bit Outlook, it will be named as “Mail (32-bit)”
    2 Double click on Mail (or Mail (32-bit)).
    3 Click Email account button
    4. Select the wrong account and click Remove. (If you only have one account listed in your profile,But you may need to create a New account first, set it as default then remove the wrong account.)
    5. Click New, select Email Account for POP3 or IMAP accounts, or select other then the correct account type.
    6. Fill in your preferred display name, email address and password on the Add New Account dialog.
    Outlook will look for published account configuration for the domain and setup the account automatically.
    In this event if your email provider does not publish autodiscover information, you’ll need to set up the account yourself. Check your mail providers support site for the proper configuration and then check the box to Manually configure the account at the bottom
    of the Add New Account dialog. 

  • Outlook 2003 and Exchange 2013

    We have just installed Exchange 2013 servers in our organization alongside existing Exchange 2007 servers. No mailboxes have been migrated yet and we are about ready to point our client access namespace to the Exchange 2013 servers and go into the co-existence
    stage.
    We still have some Outlook 2003 clients and I know these need to be updated to 2007 SP3 or 2010 Sp1 or 2013 before those mailboxes are migrated to Exchange 2013.
    However, I am curious as to whether we would hit any problems at all if we pointed our namespace to E2K13 before upgrading the Outlook 2003 clients, as long as none of the Outlook 2003 clients use Outlook Anywhere and the mailboxes those clients
    connect to remained on Exchange 2007 for the time being ?
    Clearly, Outlook 2003 is not 'supported' but the wording in the following link...
    http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
    says " Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013"
    Would the situation I'm thinking of be one of those 'compatible but unsupported' scenarios. i.e I can't think of any reason why the Outlook 2003 clients would have a need to connect to an E2K13 CAS server ...
    I'd be interested to hear other people experiences/opinions on this. Thanks!

    Hi,
    Based on my knowledge, for internal users whose mailboxes exist on Exchange 2007, it is ok to still use Outlook 2003 as clients. Because
    they will still connect to the Exchange 2007 Mailbox server instance hosting the mailbox. If the user is moved to Exchange 2013, please upgrade the Outlook client to higher version. Because Exchange 2013 doesn’t support Outlook 2003 client.
    For Outlook 2003 clients connected to Exchange 2007, they doesn’t support autodiscover service to get some Exchange services such as free/busy information, OAB. Outlook 2003 would connect to Public Folder in Exchange 2007 to retrieve these
    services. For OWA and ActiveSync service, it is not related to Outlook 2003 client, the CAS2013 would redirect the service request or send to CAS2007 for necessary data.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook Clients for Exchange 2013 Prompt for Password

    I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem: 
    - Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows: 
    RunspaceId                         : b43cd829-a81f-4b00-bb4d-73389c9df50d
    ServerName                         : EXCH-HTCA13
    SSLOffloading                      : False
    ExternalHostname                   : webmail.first.pt
    InternalHostname                   : exch-htca13.first.pt
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    Can anyone help me identify the problem?

    Hi,
    Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
    In addition, I recommend you refer to the following article:
    Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
    Thanks.
    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.
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working

    Goal:
    I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
    http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
    At the very bottom of the page are three different methods.  I have tried the first (per-user) and the third (untrusted) methods, with identical results.  For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
    information (although that is configured in the production domain and I would use it if it were possible). 
    Situation:
    When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible.  If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
    will be visible, and sometimes it will not.  When it is not, the area is filled with diagonal lines and hovering over it says “No Information”.  The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
    Adatum or Fabrikam.
    I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person.  They are quickly eroding what little confidence I had in them already.  I’m posting here because
    I’m desperate, and web searches for my errors turn up zero results.  I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
    to heave about anyone getting this to work, or not.
    Setup:
    There are three separate domains I am working with (names changed to protect the innocent).  Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers.  Adatum.local is a test domain set up fresh with Exchange
    2013 SP1.  Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
    The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels.  The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012. 
    Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites.  Adatum has a single site, and has two CAS and two mailbox servers.  Fabrikam has one internet facing server to connect
    to.  A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
    Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets.  Routing between them is completely unimpeded.  The Fabrikam server sits on another network across the internet, but firewalls have
    been configured and I can browse the availability website from the Contoso CAS servers.
    The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum.  The number of actual users on Exchange 2013 in Contoso is
    ~10.  In Adatum, there are only a handful of mailboxes configured.  The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability. 
    None of our testing/configurations have involved the Exchange 2007 servers.  There are no SPNs configured for the other domains in AD.
    Errors:
    There are three basic errors that are returned in Outlook diagnostics.  The first is the timeout error.  For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
    idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error.  If it doesn’t timeout, then it will respond with the Correct Response.
    Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls.  Less frequently, it will return Availability Error 2.  If a mailbox server returns the first Availability
    Error, then it will continue to return that error until it times out again or starts working.  Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
    If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work.  There is never an issue accessing availability information for users in the same domain as the request.
    If the remote Exchange is in an errored state, then the response includes the error.  For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
    for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
    There are no Event Log errors that correspond to failed requests of any type.  IIS logs don’t show anything beyond what is shown in the Outlook diagnostics.  There are no DNS or Active Directory Replication errors in the Event Logs.
    Timeout error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorTimeoutExpired
    ErrorMessage         : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
    AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error 2:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
    Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
                              at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
    organizationId, String domainName)
                              at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
    emailAddress)
                           . Name of the server where exception originated: Mailbox02
    ErrorDetails         : {}
    ErrorProperties      : {}
    Working:
    CalendarEvents       : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
    ViewType             : FreeBusyMerged
    MergedFreeBusyStatus : {Free, Free, Free, Free...}
    WorkingHours         : Microsoft.Exchange.WebServices.Data.WorkingHours
    Result               : Success
    ErrorCode            : NoError
    ErrorMessage         :
    ErrorDetails         : {}
    ErrorProperties      : {}
    Start : 04/09/2014 00:00:00
    End : 04/12/2014 00:00:00
    Subject :
    Location :
    Testing Methodologies:
    While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time.  Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
    post them here to help anyone in the future.
    Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers.  At least by default, it seems to pick a mailbox server in the same
    site, but which mailbox server in the site appears to be random.  It will typically pick the same one repeatedly for a while.
    The first script uses the Microsoft Exchange Web Services Managed API 2.1.
    http://www.microsoft.com/en-us/download/details.aspx?id=42022
    You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address.  The CAS proxies the request to the mailbox server which either responds with a failure
    or the free/busy data.
    The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly.  That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
    server the CAS happens to select.  I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
    I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times.  I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
    ADs to verify it wasn’t failing authentication.  (A failed authentication also generates a 401 error that is returned to the client.)  I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
    errors ever.
    First Script:
    # Import the Exchange Web Services module
    Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
    # Create the services object used to connect to Exchange
    # You can specify a specific Exchange version, which I had to do to connect to 2007
    # Exchange2007_SP1
    # Exchange2010
    # Exchange2010_SP1
    # Exchange2010_SP2
    # Exchange2013
    # $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
    # $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
    $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
    $Service.UseDefaultCredentials = $true
    # Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
    # This is used to distinguish resolving from the 2007 server versus 2013
    #$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
    $Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
    # Increase the amount output at the end to include the SOAP commands
    $Service.TraceEnabled = $true
    # Specify time frame to get free/busy for
    $StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
    $EndTime = $StartTime.AddDays(7)
    # Create the various objects needed to perform the EWS request
    $drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
    $AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
    $AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
    $Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
    $attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
    # Specify SMTP addresses of accounts to request availability for
    #$Attendeesbatch.Add("[email protected]")
    $Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    # Clear out old results so that a failed request doesn't show information still
    $availresponse = ""
    # Request the availability information from Exchange
    $availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
    # Show summary information that would include errors
    $availresponse.AttendeesAvailability
    # Show all of the appointments in the requested time period
    foreach($avail in $availresponse.AttendeesAvailability){
    foreach($cvtEnt in $avail.CalendarEvents){
    "Start : " + $cvtEnt.StartTime
    "End : " + $cvtEnt.EndTime
    "Subject : " + $cvtEnt.Details.Subject
    "Location : " + $cvtEnt.Details.Location
    Second Script:
    # Change the server in this URL to specify which mailbox server to access
    $url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
    # Uncomment the below lines if you want to query EWS using credentials other than
    # the ones used to run the script.
    #If(!(Test-Path variable:global:cred))
    # $cred = Get-Credential
    function Execute-SOAPRequest
    [Xml] $SOAPRequest,
    [String] $URL
    write-host "Sending SOAP Request To Server: $URL"
    $soapWebRequest = [System.Net.WebRequest]::Create($URL)
    # These appear to be the only things needed in the headers when making the request
    $soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
    $soapWebRequest.Accept = "text/xml"
    $soapWebRequest.Method = "POST"
    If(Test-Path variable:global:cred)
    $soapWebRequest.Credentials = $cred
    Else
    $soapWebRequest.UseDefaultCredentials = $true
    write-host "Initiating Send."
    $requestStream = $soapWebRequest.GetRequestStream()
    $SOAPRequest.Save($requestStream)
    $requestStream.Close()
    write-host "Send Complete, Waiting For Response."
    $resp = $soapWebRequest.GetResponse()
    $responseStream = $resp.GetResponseStream()
    $soapReader = [System.IO.StreamReader]($responseStream)
    $ReturnXml = [Xml] $soapReader.ReadToEnd()
    $responseStream.Close()
    write-host "Response Received."
    return $ReturnXml
    # The specing and line returns in the below variable are important for some reason
    # For example, there must be a line return after the @' on the first line, or it's invalid...
    # Change the line with this:
    # <t:Address>[email protected]</t:Address>
    # to the email address in the domain you want to query
    $soap = [xml]@'
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
    <t:RequestServerVersion Version="Exchange2013_SP1" />
    <t:TimeZoneContext>
    <t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US &amp; Canada)" Id="Central Standard Time">
    <t:Periods>
    <t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
    </t:Periods>
    <t:TransitionsGroups>
    <t:TransitionsGroup Id="0">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/1</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>4</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>10</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>-1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    <t:TransitionsGroup Id="1">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/2007</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>3</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>2</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>11</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    </t:TransitionsGroups>
    <t:Transitions>
    <t:Transition>
    <t:To Kind="Group">0</t:To>
    </t:Transition>
    <t:AbsoluteDateTransition>
    <t:To Kind="Group">1</t:To>
    <t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
    </t:AbsoluteDateTransition>
    </t:Transitions>
    </t:TimeZoneDefinition>
    </t:TimeZoneContext>
    </soap:Header>
    <soap:Body>
    <m:GetUserAvailabilityRequest>
    <m:MailboxDataArray>
    <t:MailboxData>
    <t:Email>
    <t:Address>[email protected]</t:Address>
    </t:Email>
    <t:AttendeeType>Required</t:AttendeeType>
    <t:ExcludeConflicts>false</t:ExcludeConflicts>
    </t:MailboxData>
    </m:MailboxDataArray>
    <t:FreeBusyViewOptions>
    <t:TimeWindow>
    <t:StartTime>2014-04-03T00:00:00</t:StartTime>
    <t:EndTime>2014-04-10T00:00:00</t:EndTime>
    </t:TimeWindow>
    <t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
    <t:RequestedView>DetailedMerged</t:RequestedView>
    </t:FreeBusyViewOptions>
    </m:GetUserAvailabilityRequest>
    </soap:Body>
    </soap:Envelope>
    $ret = Execute-SOAPRequest $soap $url
    # Uncomment out one of the below two lines to get output in different alternative formats
    #$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
    #$ret.InnerXml
    # If the request is successful, show the appointments, otherwise show the failure message
    If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
    Else
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage

    In this case, the SMTP domain is the same as the AD domain.  If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
    RunspaceId            : abb30c12-c578-4770-987f-41fe6206a463
    ForestName            : adatum.local
    UserName              : adatum\availtest
    UseServiceAccount     : False
    AccessMethod          : OrgWideFB
    ProxyUrl              :
    TargetAutodiscoverEpr :
    ParentPathId          : CN=Availability Configuration
    AdminDisplayName      :
    ExchangeVersion       : 0.1 (8.0.535.0)
    Name                  : adatum.local
    DistinguishedName     : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
                            Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
    Identity              : adatum.local
    Guid                  : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
    ObjectCategory        : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
    ObjectClass           : {top, msExchAvailabilityAddressSpace}
    WhenChanged           : 4/15/2014 12:33:53 PM
    WhenCreated           : 4/15/2014 12:33:35 PM
    WhenChangedUTC        : 4/15/2014 5:33:53 PM
    WhenCreatedUTC        : 4/15/2014 5:33:35 PM
    OrganizationId        :
    OriginatingServer     : dc01.contoso.local
    IsValid               : True
    ObjectState           : Unchanged

  • Exchange 2013 Non Deliverable Messages do not show correct information

    I tried looking around for a solution for this but have been unable to. 
    We have a new (1 month old) single-server installation of Exchange 2013 CU5, running on server 2012. It's in coexistence with an Exchange 2007 box. All users, groups, and everything have been migrated, we actually just shut down 2007 today. However, Exchange
    2013 never seems to give accurate or helpful NDRs.
    When someone sends an email to, let's say, a user who has left the company, so their mailbox is gone, the user who sent the email will receive an NDR. However, the NDR will not tell you the user who the email failed to. It shows the sender's account and
    says "command not allowed". This happens only to internal recipients. When sending to an external domain, we receive the NDR from the other domain with the explanation that the user does not exist or whatever. But within our domain, we never get
    a "helpful" NDR. It's just "command not allowed" and the email doesn't get to ANY of the recipients that it was sent to. Any ideas or help would be greatly appreciated!
    Delivery has failed to these recipients or groups:
    [email protected] Your message wasn't delivered due to a permission or security issue.
    It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    Diagnostic information for administrators:
    Generating server: mailserver.ourdomain
    [email protected] Remote Server returned
    '550 5.7.1 Command not allowed'
    Original message headers:
    Received: from mailserver.ourdomain ([removed]) by  mailserver.ourdomain ([removed]) with mapi id  15.00.0913.011; Thu, 17 Jul 2014 10:18:03 -0500 MIME-Version: 1.0 Content-Type:
    text/plain Date: Thu, 17 Jul 2014 10:18:03 -0500 Message-ID: <removed > Subject: RE: ASAP

    I just tested, and yes, it happens when sending to any invalid SMTP address within our domain. I also tried sending an email to a non-existant user in our domain from my gmail account and received the same message with "command not allowed". We
    are running GFI MailEssentials for spam filtering (on the same server), and I also have content filtering and recipient filtering enabled on exchange. For GFI, we exported the config we had for GFI on our 2007 server and imported it into the GFI installation
    on our Exchange 2013 server. Should I try disabling content and/or recipient filtering on Exchange? Should I try shutting off GFI and send a test email?
    I appreciate your time and effort on this!!
    I did a message trace on the test email I sent to a non-existent SMTP address on our domain and this is what I got... Not sure how helpful this is :(
    Sorry, my account isn't "verified" yet so I can't post pictures. I put the output up here for now. http://andyslights.com/trace.jpg

  • Exchange 2013 CAS - Round Robin DNS not working properly

    I have exchange 2013 server (2MB, 2CAS) server. I created two dns records for mail.test.com, autodiscover.test.com pointing to my two CAS servers.
    But the problem is if i switched of one cas server, client outlook not connecting automatically to other CAS server. By restarting the outlook also its not working. By restarting the system or running the command ipconfig /flushdns in command prompt, it
    working.
    is there any configuration iam missing, please advice how to achieve decent load balancing in Exchange 2013 CAS without going for third party Loadbalancer...

    I have exchange 2013 server (2MB, 2CAS) server. I created two dns records for mail.test.com, autodiscover.test.com pointing to my two CAS servers.
    But the problem is if i switched of one cas server, client outlook not connecting automatically to other CAS server. By restarting the outlook also its not working. By restarting the system or running the command ipconfig /flushdns in command prompt, it
    working.
    is there any configuration iam missing, please advice how to achieve decent load balancing in Exchange 2013 CAS without going for third party Loadbalancer...
    If a CAS role server is down or unable to service clients, you have to remove it from  DNS round-robin consideration manually. There is no health check with DNS round-robin unlike a true load balancer.
    Also, I would set the TTL to a low value for the CAS servers in the round-robin.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Adobe: Search Field Doesn't Work!!!

    the search field at the top of the forums just throws an
    exception with any word. Noticed it for the past 3 months! Adobe
    come on, for a great product, this forum could certainly use face
    lift! Fix the code!
    Arrrrrrgggghhhh!

    "Xilian" <[email protected]> wrote in
    message
    news:gkfucs$1br$[email protected]..
    > the search field at the top of the forums just throws an
    exception with
    > any
    > word. Noticed it for the past 3 months! Adobe come on,
    for a great
    > product,
    > this forum could certainly use face lift! Fix the code!
    Use the advanced search instead.

Maybe you are looking for