Hi Team,

Could you please tell me the way to schedule a task to check new email received in outlook and based on that my batch file has to be triggered or run.

Thanks in advance.

Thanks,

Jey

Hello All,

I have the following situation.

We have a hosted Exchange 2013 environment and the old Exchange was 2010. We are using Outlook 2010 fully updatet and we have a terminal server enivironment on Windows Server 2008R2.

Our Exchange servers are also updatet with the latest updates.

Couple of weeks ago a customer is migrated to our platform.

First we created all the users in our environment. For the migration I did a PST migration and used the Exchange Management Shell. On the server of the customer I did a export of there mail.

After the export was finished we uploaded the mail to our environment and did a Import of the PST files. Also through the Exchange Management Shell. This went all ok and we didn't had any issues.

I noticed the auto-complete list was also migrated and that gave a lot of issues when they tried to mail internal after clearing the Auto-Complete list the issue was solved.

But they have a appliciation called SAP and its there core business application for creating offers or invoices. They have a option which create a email and put it in drafts so the user can check the email and add a signature. Also the To: field is already filled in. When they send the email they get a NDR back immediately. 

Your message did not reach some or all of the intended recipients.

      Subject:    Oferte nav aanvraag IOTD - 29210

      Sent: 5/21/2014 4:22 PM

The following recipient(s) cannot be reached:

      External@external.nl on 5/21/2014 4:22 PM

            Diagnostic code = OrNameUnrecognized; Reason code = TransferFailed; Status code = 510

            < #5.1.0 smtp;550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)>

If we delete the address in the to: field and put in manual it send the email. When they try the same address again already filled in it fails. When I check the Email Properties of the contact the only field that is filled in is Display Name.

After you send the email when the to: field is already filled and you check the sent email you see at E-mail type INVALID. Another user sees a whole different contact when see right click on the address and choose Contact Card. After deleting the contact that shows a different contact is displayed.

I created a test user and also with the test user, newly created, we have the same issue.

I have contacted the supportdesk of the application to ask where the contact information is stored. The contact information is created within the application and the only things filled is the customer name and email address.

I have been looking for a week now and haven't find a solution yet. Also i'm not sure anymore where to look is this Outlook related or Exchange or is it the application?

I hope someone can help me with this.

Kind Regards,

Mathijn

I'm utterly baffled by this, largely because until this morning, everything was working fine. I'm not aware of any changes that would explain this, though obviously something has changed, because none of our users can connect to Exchange (2013, Version 15.0 Build 1156.6, in a 2-server DAG) via Outlook 2016 (don't have any older versions of Outlook to test -- all users are updated automatically via Office 365). All are being told to enter a username and password, which are never accepted. I'm the Exchange admin, so this is my responsibility to fix.

Users have no problem connecting to Exchange and logging in and getting mail via other paths. For example, I can get e-mail on my Windows Phone, in Windows 10 Mail, and via OWA. To test, I have restarted client and server computers, reset user passwords, rebooted the AD servers, deleted and tried creating a whole new mail profile on one of the client computers, and deleted and recreated the connection to the server on Windows 10 Mail. Everything works fine everywhere except Outlook. After deleting the mail profile, I can't recreate it to even launch Outlook, because it gets stuck on the username password window.

I also tried connecting Outlook to Exchange off the LAN, and they suffer the same exact problem, so it's not just the LAN side of the Exchange-Outlook connection that's failing.

Based on the symptoms, and that it affected all copies of Outlook at the same time, I assume this must be an Exchange setting. What could it be? Something to do with Autodiscover?

Unlike previous versions of Outlook, Outlook 2016 doesn't seem to allow me to manually enter the server name, AD domain name, and other information, so if it's not getting it right via autodiscover, I'm not sure how to troubleshoot or work around that.

The closet to changing anything that I can think of is that yesterday (mail was still working until this morning) I had disabled NTLM connectivity on the AD via Group Policy, but as part of debugging, I've since reverted that to the prior setting. I have restarted all servers and the test clients since making that change back, just in case.

I don't think this is related, but one possible unusual aspect to our system is that our OWA domain name is remote.ourcompanydomain.com and mail addresses areuser@marketingname.com. Note that they are different domains (ourcompanydomain vs. marketingname), and where our AD domain would be ourcompanydomain.local (same name as the OWA domain, but ending in .local and note .com). To enter users we are (and always have) entering ourcompanydomain\user.

Colin

When in the office (no matter on WiFi or cable, no matter on VPN or not) Outlook2013 is working fine. When at home (I only have WiFi at home) it will not connect, no matter on VPN or not. So I tried to turn of Wifi and connect to the internet via my iPhone (using it as a modem) and (although I now can't establish VPN connection, which is another issue) Outlook started to work fine (without VPN). What should I do to make it work on WiFi? 

Hello,

We have two separate Exchange 2013 infrastructures one with CU21 and second with CU22 both with the same issue with Out Of Office feature and according to the information in the Internet it is quite common issue. The problem arises when there is more than one mailbox added to the same Outlook profile (using credentials from those mailboxes - not Full Access mailbox permissions). When second (and consequent) mailboxes are linked to the same Outlook profile OOF feature works only on the LAST added mailbox and drops "server is currently unavailable" message when you try to set it up on any of the existing mailboxes. To this moment I can confirm that we checked the following:

1. Autodiscover works fine (as well as all tests from email AutoConfiguration)

2. Proxy settings are being used but if disabled issues persists

3. Certificates/NDS are fully OK - wildcard is used, no issues.

Please advise. Any help is highly appreciated.

Many thanks in advance!

Best regards,

Nikolay

Hi,

I am trying to authenticate a user over IMAP and I have several issues.
Before you asked for it:
- I confirm IMAP/POP services are enabled on the mailbox, services are running on all my servers etc...
- I also configure correctly the X509CertificateName with my fqdn: mail.contoso.com
- I checked ports for SSL and unencrypted bindings and it looks fine.
- The LoginType is configured with "SecureLogin" 
- The EnableGSSAPIAndNTLMAuth is set to "True"
- Components ImapProxy are active

I can see the following logs for imap4:
2018-02-26T17:19:25.388Z,0000000000000052,5,10.12.58.22:143,10.12.58.168:60469,User.Test,51,27,20,login,user.test *****,"R=""6 NO LOGIN failed."";Msg=Proxy:exdb01.contoso.com:1993:SSL;ErrMsg=ProxyNotAuthenticated;LiveIdAR=OK"

I am really stuck at this point as I already spent 2 days to check all troubleshooting methods I found on differents posts and it didn't solve my problem...
Hence, I would really appreciate your help to troubleshoot further and fix this issue.

You will find below all information regarding my exchange architecture/configuration.
On my side, my exchange environment is split over 4 servers with the same updates and CU 19:

Name                : EXDB01 (Primary DB)
Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 1365.1)

Name                : EXCAS01 (Primary CAS)
Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 1365.1)

Name                : EXDB02 (Secondary DB)
Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 1365.1)

Name                : EXDB02 (Secondary CAS)
Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 1365.1)


My 4 servers have the same result when running Get-ImapSettings:

$> Get-ImapSettings

UnencryptedOrTLSBindings  SSLBindings                       LoginType                         X509CertificateName
------------------------  -----------                       ---------                         -------------------
{[::]:143, 0.0.0.0:143}   {[::]:993, 0.0.0.0:993}           SecureLogin                       mail.contoso.com



$> get-ImapSettings -Server exdb01 | fl


RunspaceId                        : 9f705234-b1a9-4dca-9687-f473d02280a1
ProtocolName                      : IMAP4
Name                              : 1
MaxCommandSize                    : 10240
ShowHiddenFoldersEnabled          : False
UnencryptedOrTLSBindings          : {[::]:143, 0.0.0.0:143}
SSLBindings                       : {[::]:993, 0.0.0.0:993}
InternalConnectionSettings        : {exdb01.contoso.com:993:SSL,
                                    exdb01.contoso.com:143:TLS}
ExternalConnectionSettings        : {}
X509CertificateName               : mail.contoso.com
Banner                            : The Microsoft Exchange IMAP4 service is ready.
LoginType                         : SecureLogin
AuthenticatedConnectionTimeout    : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections                    : 2147483647
MaxConnectionFromSingleIP         : 2147483647
MaxConnectionsPerUser             : 16
MessageRetrievalMimeFormat        : BestBodyFormat
ProxyTargetPort                   : 1993
CalendarItemRetrievalOption       : iCalendar
OwaServerUrl                      :
EnableExactRFC822Size             : False
LiveIdBasicAuthReplacement        : False
SuppressReadReceipt               : False
ProtocolLogEnabled                : True
EnforceCertificateErrors          : False
LogFileLocation                   : C:\Program Files\Microsoft\Exchange Server\V15\Logging\Imap4
LogFileRollOverSettings           : Daily
LogPerFileSizeQuota               : 0 B (0 bytes)
ExtendedProtectionPolicy          : None
EnableGSSAPIAndNTLMAuth           : True
Server                            : exdb01
AdminDisplayName                  :
ExchangeVersion                   : 0.10 (14.0.100.0)
DistinguishedName                 : CN=1,CN=IMAP4,CN=Protocols,CN=exdb01,CN=Servers,CN=Exchange Administrative
                                    Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XXXX,CN=Microsoft
                                    Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com
Identity                          : exdb01\1
Guid                              : 4ecfc15c-355a-4493-b3e3-ab19e1eda21c
ObjectCategory                    : contoso.com/Configuration/Schema/ms-Exch-Protocol-Cfg-IMAP-Server
ObjectClass                       : {top, protocolCfg, protocolCfgIMAP, protocolCfgIMAPServer}
WhenChanged                       : 2/26/2018 4:02:59 PM
WhenCreated                       : 6/23/2014 2:04:41 PM
WhenChangedUTC                    : 2/26/2018 4:02:59 PM
WhenCreatedUTC                    : 6/23/2014 1:04:41 PM
OrganizationId                    :
Id                                : exdb01\1
OriginatingServer                 : dc01.contoso.com
IsValid                           : True
ObjectState                       : Unchanged


My SSL certificate is enabled for IMAP, SMTP, IIS
$> Get-ExchangeCertificate -Server excas01 | fl


AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {mail.contoso.com}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=COMODO RSA Organization Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater
                     Manchester, C=GB
NotAfter           : 4/30/2021 12:59:59 AM
NotBefore          : 1/31/2018 12:00:00 AM
PublicKeySize      : 2048
RootCAType         : ThirdParty
SerialNumber       : xxxxxxxxxxxxxxxxxxxxxxxxx
Services           : IMAP, IIS, SMTP
Status             : Valid
Subject            : CN=mail.contoso.com, OU=Unified Communications, OU=IT, O=Contoso,
                     STREET=xxxxx, L=xxxx, S=xxxx, PostalCode=1234, C=XX
Thumbprint         : xxxxxxxxxxxxxxxxxxxxxxxxx

[...]


$> Get-ServerHealth excas01 | ?{$_.HealthSetName -like "IMAP*"}

Server          State           Name                 TargetResource       HealthSetName   AlertValue ServerComp
                                                                                                    onent
------          -----           ----                 --------------       -------------   ---------- ----------
excas01    NotApplicable   MaintenanceFailur...                      IMAP            Healthy    None
excas01    NotApplicable   MaintenanceTimeou...                      IMAP            Healthy    None
excas01    Online          ImapProxyTestMonitor MSExchangeImap4      IMAP.Proxy      Healthy    ImapProxy
excas01    NotApplicable   ImapCTPMonitor       MSExchangeImap4      IMAP            Unhealthy  None


[PS] C:\Windows\system32>Get-ServerComponentState -Identity excas01 | ?{$_.Component -like "IMAP*"}

Server                                  Component                               State
------                                  ---------                               -----
excas01.contoso.com    ImapProxy                               Active


[PS] C:\Windows\system32>Get-ServerComponentState -Identity exdb01 | ?{$_.Component -like "IMAP*"}

Server                                  Component                               State
------                                  ---------                               -----
exdb01.contoso.com     ImapProxy                               Active

Hi Everyone,

Environment

- Exchange 2013 CU15
- Outlook 2010
- Windows Server 2016 RDS / Citrix
- RES Workspace 
- Caching is turned off in Outlook

Problem

Users are experiencing problems with the Outlook calendar. Created appointments sometimes appear after a few minutes in their own calendar. Meetings from collegues cannot be accepted properly. Etc.

Problems do not always occur. 

Question

How can I properly troubleshoot and monitor these issues? What's a good way to do this? 

I know that the Exchange server needs to be updated, as CU22 has been released earlier this month. Office is going to be upgraded to 2016 in Q1 2020.

Hello,

I received a work order today from a client complaining that his OWA calendar was showing no appointments. I tested to see if this was the case for me and I also found the same problem. The calendar does however show up correctly in Internet Explorer. Has their been a recent patch that broke things for OWA in alternative browsers?

i get this message in similar format multiple times a day.

what can i do to fix it

15:52:06 Synchronizer Version 16.0.4810

15:52:06 Synchronizing Mailbox 'Hank Miller'

15:52:06 Synchronizing server changes in folder 'Conference - Calendar'

15:52:07 Error synchronizing folder

15:52:07                               [80070005-508-80070005-560]

15:52:07                               You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator.

15:52:07                               Microsoft Exchange Information Store

15:52:07                               For more information on this failure, click the URL below:

15:52:07 Done

Hello,

I received a work order today from a client complaining that his OWA calendar was showing no appointments. I tested to see if this was the case for me and I also found the same problem. The calendar does however show up correctly in Internet Explorer. Has their been a recent patch that broke things for OWA in alternative browsers?

I have Outlook set up on 3 computers - two of them connect and send/receive with no problem - the third one constantly comes up with 'The server is not available'. I have checked all the settings and everything looks fine and am at my wits end now - been trying to solve this for the past two days unsuccessfully - am hoping someone might be able to help. 

All computers are Windows 10 and are completely up to date as far as updates are concerned

Exchange 2010 SP3 RU25.  Outlook 2016 (and 2007 as test).  Public Folder searches for "attachment contains" returns no matches when there are matches.  All other searchability in Public Folders seems OK.  I can search "attachment yes or no" and it works.  But if I try to search for the attachment file name or the attachment file contents, I get no results.  Cached or non-cached mode makes no difference.

Anyone have any ideas?

We have a Shared Mail Box with several secondary addresses. In Outlook when reading a received email, the TO: field displays the Shared Mailbox primary SMTP address. I do see the original destination SMTP all over in the message header ( externally sent ). Would it be possible to display the original recipient SMTP address in the message display?

Thanks

Tom

Hi All,

Running exchange 2013 in a DAG (2 cas and 2 mailboxes).

So I am trying to get outlook anywhere working.

I have OWA configured to go to webmail.domain.ca, works fine. I would like outlook anywhere to point to anywhere.domain.ca, I make the change in external dns and on the CAS servers for external outlook anywhere. The test PC fails.  When I look at the connection status of outlook it is trying to go to webmail.domain.ca. Where is it getting this info from?

When I edit the host file and point webmail to my desired IP address everything works.

Hi All,

Using Exchange 2013 OnPremise, Can anyone please assist me in how to fix the below issue after creating my email accepted domain to Exchange 2013 OnPremise?

My previous PrimarySMTP for all of the users was: First.LastName@OldDomain.com, but then after creating and changing the primary SMTP to the First.Last@domain.com, all of the users globally got the above annoying pop up daily?

Any steps and suggestion would be greatly appreciated.

/* Server Support Specialist */