Hi, I setup an co-existence setup with Exchange 2010 and Exchange 2013, moved test mailbox it was working (using ECP) but OWA was not working after upgrade of Exchange 2013 CU7 upgrade. I tried reset virtual directories but no luck. now none of the Exchange virtual directories in working.

Can you please provide me troubleshooting steps to solve this issue? also during troubleshooting i was trying to open " web.config file from using notepad "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa" unfortunately all config files turns with notepad icon (not sure related to above issue but still thought of giving here).

any help would be much appreciated.

Thanks, Karthikeyan R

Hi, expert

I'm trying to configure a non-domain joint client host to use MAPI to connect to the exchange server (both are in the same subnet) with a domain user account.

For my understanding, as long as there are no firewall sitting in between which is blocking the RPC ports, it should work. But for somehow, I can only use this setup to initialize the Outlook profile, and after Outlook is launched, it will try to connect to the exchange server but fails at the end.

Thanks.

Dave

We have recently upgraded to Exchange 2013 from Exchange 2010.. We have certain users that have their calendar appointments disappearing randomly.. They do not go into deleted items, they just disappear...

Things we have tried / things to note:

• Recreate Outlook Profile
• Remove account from iPhone and recreate
• Copied their AD account and then created a mailbox on their same database to see if appointments would disappear with the test account (they do not).
• Removed all delegates for this user
• User's iPhone is on latest iOS (8.3)
• Removed devices that haven't synced in a while (old iPhone, iPad)
• It's not just one user, it's multiple users. The one thing in common is they are on the same database and they are in the same OU.. We are in the process of migrating one user to a different DB to test.
• These particular users have been migrated to the 2013 servers for months, however, the issue seemed to have start when we decommissioned the 2010 servers.

Anyone have any suggestions on what to check?

Thanks

I have two Exchange 2013 SP1 CAS servers (no CUs). I try to restore a deleted message in OWA (right-click on the Deleted folder, click Recover Deleted Items) and receive Error 404 in the popup window (Chrome) or "Something went wrong" in IE. In addition, the IE window contains the following explanation of the error:

X-OWA-Error: ClientError;exMsg=Sys.ArgumentException: Value does not fall within the expected range.Parameter name: Unknown type _d.$Vq was requested;file=Sys.ArgumentException: Sys.ArgumentException: Value does not fall within the expected range.Parameter name: Unknown type _d.$Vq was requested   at $7CD (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1170602)   at Anonymous function (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1171016)   at Anonymous function (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:294125)   at $5e5 (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482)   at $iS (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669)   at $9lW (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369266)   at $1mX (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27230)   at $4pt (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27759)   at $6Kk (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:32733)   at Anonymous function (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/preboot.js:34:39102)   at $5e5 (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482)   at $iS (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669)   at $9lW (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369266)   at $1mX (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27230)   at s (https://CAS-SERVER-NAME.domail.local/owa/prem/15.0.847.34/scripts/boot.0.mouse.js:91:28216):91
X-OWA-Version: 15.0.847.34
X-FEServer: CAS-SERVER-NAME
X-BEServer: null
Date: 02.01.1601 15:31:19

Our CAS servers are joined to a NLB cluster, but the error is the same whether I connect to the NLB name or to a specific CAS Server.

All other links in OWA and ECP work fine, no errors.

Looks like a bug in the Exchange code. Does someone besides me encounter the same error?

Evgeniy Lotosh
MCSE: Server infractructire, MCSE: Messaging

We have a Exchange 2013 standard install with versión 15.0 Build 847.32 and we are having several errors: 

Watson report about to be sent for process id: 2864, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Parser, M.E.R.F.P.FastTransferContext`1.Process, System.IndexOutOfRangeException, 9700, 15.00.0847.030.

Watson report about to be sent for process id: 2864, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Parser, M.E.R.F.P.FastTransferContext`1.Process, System.IndexOutOfRangeException, 9700, 15.00.0847.030.ErrorReportingEnabled: False 

Watson report about to be sent for process id: 2864, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, M.E.RpcClientAccess.Service, unknown, M.E.D.T.I.F.F.TextStore.AddText, System.IndexOutOfRangeException, a89e, unknown.ErrorReportingEnabled: False 

Dear all,

I knew there are some discussions about solving this problem I tried. But those don't work for me.

I have 2 Exchange 2013 Std with all CAS & MBX in-a-box, creating a DAG over these 2 Exchange servers. On top, I have 2 x Windows 2012 R2 WAP as reverse proxy. Users connect Outlook Anywhere with WAP pass-thu mode. And I have WNLB on these 2 WAP servers.

All the things work fine except all users cannot download the offline GAB no matter I can access the XML URL by web, re-create the XML...

Please suggest more way to trouble shoot it and fix it.

Thank all guys!

KK

Hello...I am Rahul.We are not able to send emails to Hotmail ,but able to receive th emails from them.Getting below error message.

BAY004-MC3F18.hotmail.com gave this error:
SC-001 (BAY004-MC3F18) Unfortunately, messages from 103.23.150.85 weren't sent. Please contact your Internet service provider since part of their network is on our block list. 

Please help to unblock the ip.

Hello!

I'm trying to get Exchange 2010 and Exchange 2013 coexistence to work. I've struggle some time with this i finally manage to get EX2010 to work with EX2013 but not the other way around.

When I login through the OWA on EX2013 (https://webmail.domain.com) with a mailbox residing on EX2010 i'm able to "open a another mailbox..." residing in EX2013. I've had to follow this blog to make this work:http://www.techtalklive.org/ttlblog/Pages/Exchange-2010-2013-Coexistence.aspx

Even in Outlook 2010/2013 this works, the EX2013 mailbox is auto mapped and we are able to manage every single object.
The strange thing is it won't work the other way around. A EX2013 mailbox is unable to open a EX2010 mailbox, problem occurs in both OWA and in Outlook 2010/2013 so i'm guessing its a more central issue.

The error message in OWA when trying to open a EX2010 mailbox from EX2013 mailbox:
"The custom error module does not recognize this error."
The URL becomes: https://webmail.domain.com/owa/Test.Mailbox1@domain.com/?offline=disabled

The error message in Outlook when trying to open a EX2010 mailbox from EX2013 mailbox:
"Cannot display the folder. Microsoft Outlook cannot access the specified folder location. The operation failed. An object cannot be found."

Since we can open a EX2013 mailbox from EX2010 you can remove all thoughts that we are not proxying using EX2013's namespace. We are publishing EX2013 through a Kemp loadbalancer and EX2010 through TMG.
A EX2010 mailbox can't open a EX2010 mailbox when we are proxying through EX2013, if we go straight to the EX2010 CAS via TMG it's fully functionally.

Settings:
EX2010: 1CAS, 2MBOX (TMG for publishing webaccess)
EX2013: 2servers using both CAS and MBOX roles (Kemp for publishing)

Get-OWAVirtualDirectory

LogonFormat                  : FullDomain
ClientAuthCleanupLevel       : High
OwaVersion                   : Exchange2010
ServerName                   : EX-CAS1
LegacyRedirectType           : Silent
CrossSiteRedirectType        : Manual
Name                         : owa (Default Web Site)
InternalAuthenticationMethods: {Basic, Ntlm, WindowsIntegrated}
MetabasePath                 : IIS://EX-CAS1.domain.net/W3S
BasicAuthentication          : True
WindowsAuthentication        : True
DigestAuthentication         : False
FormsAuthentication          : False
LiveIdAuthentication         : False
DefaultDomain                : domain.net
WebSite                      : Default Web Site
DisplayName                  : owa
Server                       : EX-CAS1
InternalUrl                  : https://webmail.domain.com/owa
ExternalUrl                  : https://webmail.domain.com/owa
ExternalAuthenticationMethods: {Fba}

LogonFormat                  : UserName
OwaVersion                   : Exchange2013
ServerName                   : SER-EXCHANGE01
Name                         : owa (Default Web Site)
InternalAuthenticationMethods: {Basic, Fba}
MetabasePath                 : IIS://SER-EXCHANGE01.domain.net/W3SVC/1/ROOT/owa
BasicAuthentication          : True
WindowsAuthentication        : False
DigestAuthentication         : False
FormsAuthentication          : True
LiveIdAuthentication         : False
AdfsAuthentication           : False
OAuthAuthentication          : False
DefaultDomain                : domain.net
WebSite                      : Default Web Site
DisplayName                  : owa
Server                       : SER-EXCHANGE01
InternalUrl                  : https://webmail.domain.com/owa
ExternalUrl                  : https://webmail.domain.com/owa
ExternalAuthenticationMethods: {Fba}

LogonFormat                  : UserName
OwaVersion                   : Exchange2013
ServerName                   : SER-EXCHANGE02
Name                         : owa (Default Web Site)
InternalAuthenticationMethods: {Basic, Fba}
MetabasePath                 : IIS://SER-EXCHANGE02.domain.net/W3SVC/1/ROOT/owa
BasicAuthentication          : True
WindowsAuthentication        : False
DigestAuthentication         : False
FormsAuthentication          : True
LiveIdAuthentication         : False
AdfsAuthentication           : False
OAuthAuthentication          : False
DefaultDomain                : domain.net
WebSite                      : Default Web Site
DisplayName                  : owa
Server                       : SER-EXCHANGE02
InternalUrl                  : https://webmail.domain.com/owa
ExternalUrl                  : https://webmail.domain.com/owa
ExternalAuthenticationMethods: {Fba}

Name                                 : EX-CAS1
Fqdn                                 : EX-CAS1.domain.net
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : EX-CAS1
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {SITE-A}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
Identity                             : EX-CAS1
IsValid                              : True
ObjectCategory                       : domain.net/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
Id                                   : EX-CAS1
OriginatingServer                    : AD4.domain.net
ObjectState                          : Unchanged

Name                                 : SER-EXCHANGE01
Fqdn                                 : SER-EXCHANGE01.domain.net
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : SER-EXCHANGE01
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {SITE-A}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
Identity                             : SER-EXCHANGE01
IsValid                              : True
ObjectCategory                       : domain.net/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
Id                                   : SER-EXCHANGE01
OriginatingServer                    : AD4.domain.net

Name                                 : SER-EXCHANGE02
Fqdn                                 : SER-EXCHANGE02.domain.net
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : SER-EXCHANGE02
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {SITE-A}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
Identity                             : SER-EXCHANGE02
IsValid                              : True
ObjectCategory                       : domain.net/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
Id                                   : SER-EXCHANGE02
OriginatingServer                    : AD4.domain.net

ServerName                         : EX-CAS1
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EX-CAS1.domain.net/W3SVC/1/ROOT/Rpc
Path                               : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 14.3 (Build 123.4)
Server                             : EX-CAS1
AdminDisplayName                   :
ExchangeVersion                    : 0.10 (14.0.100.0)
Name                               : Rpc (Default Web Site)
Identity                           : EX-CAS1\Rpc (Default Web Site)
Guid                               : 133923b3-b116-4faa-923f-ef63c202fa05
ObjectCategory                     : domain.net/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
Id                                 : EX-CAS1\Rpc (Default Web Site)
OriginatingServer                  : AD4.domain.net
IsValid                            : True
ObjectState                        : Changed

RunspaceId                         : 606c1631-b2c2-45b8-93d8-1a3dd596ee82
ServerName                         : SER-EXCHANGE01
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://SER-EXCHANGE01.domain.net/W3SVC/1/ROOT/Rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 1076.9)
Server                             : SER-EXCHANGE01
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
Identity                           : SER-EXCHANGE01\Rpc (Default Web Site)
Guid                               : 82a17d36-0201-4607-8a0e-6c4c04b37535
ObjectCategory                     : domain.net/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
Id                                 : SER-EXCHANGE01\Rpc (Default Web Site)
OriginatingServer                  : AD4.domain.net
IsValid                            : True
ObjectState                        : Changed

RunspaceId                         : 606c1631-b2c2-45b8-93d8-1a3dd596ee82
ServerName                         : SER-EXCHANGE02
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://SER-EXCHANGE02.domain.net/W3SVC/1/ROOT/Rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 1076.9)
Server                             : SER-EXCHANGE02
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
Identity                           : SER-EXCHANGE02\Rpc (Default Web Site)
Guid                               : 133c7875-1947-4ccc-b9e2-a928a96da65c
ObjectCategory                     : domain.net/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
Id                                 : SER-EXCHANGE02\Rpc (Default Web Site)
OriginatingServer                  : AD4.domain.net
IsValid                            : True
ObjectState                        : Changed

Hi there:

I'd like to poll the group to see if anyone has deployed OWA 2013 using UAG 2010.  Any challenges or issues?

In particular I'm looking to see if you were able to configure the IIS settings on the 2013 Exchange CAS for Forms Based Auth (FBA). 

There seems to be some confusion concerning the modes of authentication required by UAG. What I've found is that when FBA is enabled for the Exchange CAS IIS, an end-user logging on through the UAG portal gets a double-logon prompt - once for UAG and once for OWA.

Any help greatly appreciated.

hi,

We are experiencing issues with Outlook 2013 on an onpremise Exchange 2013 system.

the issue only affects users with Outlook 2013 and messages queue up in the outbox until we restart Outlook. 2010 users are fine.

The article http://support.microsoft.com/kb/2862523 describes the issue exactly but i wanted to know if anyone has fixed this issue without disabling SPI on the firewall. The article says it is a temporary workaround as it puts the clients at risk and the last update was July 2014.

Microsoft have already verified the on premise Exchange setup as we opened a call with the Exchange team before we discovered the article.

sg

ms

I am wondering if anyone can add any assistance to an issue that I have been having with a users default Contacts folder being duplicated.

This has been escalated to Microsoft Support Engineers and we have not been able to find a resolution yet.

We use Office 365 Education plan and Office 2013 for desktop clients.

The situation:

• The user has connected to the account with an iPad and a Windows Phone.
• There are now two default contact folders.
  I am told that this occurred when the staff member was given a new laptop
• When a contact is put in on the phone or iPad, it goes into one of the contact folders (I will call this OtherContacts).
• However the contact does not appear on the device unless it is copied to the Contacts folder on the desktop client.

What we have tried

We have removed the connection for the iPad and WP, and deleted the identities associated with the users mailbox.
In OWA, there is the option to delete the OtherContacts - however - "There was a problem deleting the folder" is the response.

It was suggested that the Contacts folder cold be deleted in the Outlook client.
There is an option to delete the Contacts folder (not OtherContacts).
However the message is:

"Cannot delete this folder. Right-click the folder, and then click Properties to check you permissions for your folder....."
(The folder has no special permissions and is not shared)

Any ideas greatly appreciated.

Hi All ,

In my environment frequently i am getting account lockouts for the pop based email accounts (both internal and external user from internet).

So i just tried to find the caller computer name for the account lockouts.Finally i found that exchange CAS server is making those account lockouts.

I have enabled the protocol logging on the CAS server and i found the below mentioned error message.

"R=""-ERR Logon failure: unknown user name or bad password."";Msg=LogonFailed:LogonDenied"

Environment Details :

Exchange 2013 SP1

Client Windows Live mail.

Please all you tell me how to overcome this issue for my pop Email clients ?

Thanks & Regards S.Nithyanandham

ENVIRONMENT

-1 Exchange 2013 SP1 CU7 server with all roles that is also a hybrid server with Office 365 tenant, mailboxes are all on premise only LYNC online is being utilized right now.

-Exchange 2013 public folders

-Mix of Outlook 2013 SP1 and Outlook 2010 SP3 clients all fully update to day as of Feb 2015

Outlook anywhere is working perfectly across all clients both internally and externally using autodiscover.  Both Outlook 2013 and 2010 clients can open the program and create a profile automatically via autodiscover and no additional logon prompts are seen.

We set the internal and external mapi virtual directory URLs to a valid URL that also matches the Exchange 2013 SSL certificate.  We set the security to ntlm, negotiate on the mapi virtual directory.  We reset IIS and enabled mapi over http in the org config.  We run in to problems here.

Outlook 2010 clients appear to be working fine.  We can create a new profile and open and close Outlook without any logon prompts and verify that MAPIHTTP and Negotiate are used to connect to Exchange.

Outlook 2013 clients are having problems.  As soon as we try to create a profile it says your administrator has made a change that requires you to restart outlook and then a windows logon prompt appears. If we authenticate Outlook will open and connect.  This logon prompt should not occur.    We can confirm that it is connecting via MAPI HTTP and Negotiate.

If we set the mapi virtual directory to NTLM only then a logon prompt also appears during every open of Outlook 2013.  We can confirm that it is trying to connect with MAPIHTTP via NTLM in the outlook connection test screen.

I do not understand this behavior by Outlook 2013 which was supposed to be designed with MAPI HTTP in mind.  I would think the same issues would occur with Outlook 2010 but they do not.  I am not sure how to resolve this and I am looking for help.

Dear all,

I've a couple of users who receive the by now infamous "Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later." error as soon as the try to enable their OOF reply within Outlook 2013. Thing is that only a couple of users receive this error whereas the rest does not, never ever. So it must have something do to with that particular user account.

I tried out all suggestions spread over the internet, e.g.

• IE proxy settings
• IE trusted site settings
• IE intranet site settings
• EWS virtual directory, availability, authentication
• IIS settings
• DNS settings
• Autodiscover settings
• new Outlook profile
• bla bla bla

All to no prevail. I still receive this error. The user opens his or her Outlook 2013 (which runs on Online mode, Cache Mode has been disabled company wide via GPO) and then clicks on OOF in order to enable it - and receives stated error. Thing is you could click to enable a couple of times and maybe after 5 or 7 or 8 clicks it suddenly workes. It's just random.

These are the different articles I already checked:

• http://www.petenetlive.com/KB/Article/0000897.htm
• http://www.techieshelp.com/out-of-office-doesnt-work-after-installing-exchange-2007-or-2010/
• http://www.msoutlook.info/question/879
• http://serverfault.com/questions/677657/exchange-2013-oof-not-working-for-migrated-accounts
• http://blog.shipshapeit.com/microsoft-exchange-out-of-office-replies-not-working-try-this/
• and so on

Any help would be greatly appreciated.
Alex

Alexander Ollischer Diplom-Wirtschaftsinformatiker (FH) Citrix & Microsoft Certified Engineer (CCEA, CCEE, MCSA, MCSE, MCDBA, MCTS) Afontis IT+Services GmbH Baierbrunner Straße 15 81379 München Deutschland Telefon (089) 74 34 55-0 Fax (089) 74 34 55-55 mailto:a.ollischer@afontis.de http://www.afontis.de http://www.itganzeinfach.de Amtsgericht München, HRB 109 005 Geschäftsführer: Thomas Klimmer

Hi,

I have Exchange 2013 one CAS and one Mailbox server and configured multiple users on POP and IMAP. The problem is on Client Frontend security settings the anonymous is selected and port 587 is allowed on Firewall. If someone from outside telnet on our domain on port 587 they can send email to any outside domain and 587 port is acting as relay.

The problem is when I uncheck the anonymous on Client Frontend on port 587 in security option the telnet from outside stop but my local users who were configured on POP were unable to send email. In client computer, change the POP port from 587 to 25 the user send and receive email but the problem is to uncheck on the "server required authentication".  I want to enable the "server required authentication" on port 25.

I am having permission conflict on the configuration what I think so. Can some one help me to find the solution.

Hi All,

Running Exchange 2013 SP1.

So we have a bunch of users who share out their calendars and this allows others to make appointments in those calendars. The only problem is that we are encountering lots of double bookings. Does anyone have a solution for this or a better of making appointments in peoples calendars?

Thanks.

We have recently upgraded to Exchange 2013 from Exchange 2010.. We have certain users that have their calendar appointments disappearing randomly.. They do not go into deleted items, they just disappear...

Things we have tried / things to note:

• Recreate Outlook Profile
• Remove account from iPhone and recreate
• Copied their AD account and then created a mailbox on their same database to see if appointments would disappear with the test account (they do not).
• Removed all delegates for this user
• User's iPhone is on latest iOS (8.3)
• Removed devices that haven't synced in a while (old iPhone, iPad)
• It's not just one user, it's multiple users. The one thing in common is they are on the same database and they are in the same OU.. We are in the process of migrating one user to a different DB to test.
• These particular users have been migrated to the 2013 servers for months, however, the issue seemed to have start when we decommissioned the 2010 servers.

Anyone have any suggestions on what to check?

Thanks

Hello,

I have a strange problem.

When external user (outside of my lan) try to access to OWA, they can sign in, then they receive this message:

This is the same with Firefox, IE, Chrome, name it....

On my lan everything works fine.

Strange thing, with "OWA Light", eveything works fine from outside.

The problem is with the "Premium" version.

Idea?

It deactivate the IPS, Antivirus, everything...