I have a on-premise EXCH2010 / EXCH2013 deployment and I would like to allow our users to be able to access their email using their domain joined and non-domain joined (workgroup) laptop/outlook.

The clients are running Outlook 2010 and/or Outlook 2013.

The current issue is that I cannot connect, my test case is using Outlook 2013 trying to connect externally (using autodiscover). When I go and add a new profile and I select Exchange and enter my server URL (the autodiscover urL) and my user-id and click"check name" I get nothing, just an error saying lookup failed.

I would expect for a WORKGROUP computer to get prompted for user/pass so they can get authenticated and the profile added.

Here is my OutlookAnywhere settings in my AD.

RunspaceId                         : cd27e542-1c8b-4569-b62d-cb8a19a745a4
ServerName                         : exch-server
SSLOffloading                      : False
ExternalHostname                   : webmail.mydomain.com
InternalHostname                   : 
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Ntlm}
XropUrl                            : 
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://exch-server.xand1.mydomain.com/W3SVC/1/ROOT/Rpc
Path                               : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 14.3 (Build 123.4)
Server                             : exch-server
AdminDisplayName                   : 
ExchangeVersion                    : 0.10 (14.0.100.0)
Name                               : Rpc (Default Web Site)
Identity                           : exch-server\Rpc (Default Web Site)
Guid                               : e2325c87-eb52-49cb-ab18-f02a76e07340
ObjectCategory                     : xand1.mydomain.com/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
OrganizationId                     : 
OriginatingServer                  : xan-dc02.xand1.mydomain.com
IsValid                            : True
ObjectState                        : Changed



RunspaceId                         : cd27e542-1c8b-4569-b62d-cb8a19a745a4
ServerName                         : exch-server01
SSLOffloading                      : True
ExternalHostname                   : webmail.mydomain.com
InternalHostname                   : webmail.mydomain.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Ntlm}
XropUrl                            : 
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://exch-server01.xand1.mydomain.com/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 847.32)
Server                             : exch-server01
AdminDisplayName                   : 
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
Identity                           : exch-server01\Rpc (Default Web Site)
Guid                               : 4f20a6e4-ed74-4d75-8e6b-43fb0687848a
ObjectCategory                     : xand1.mydomain.com/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
OrganizationId                     : 
OriginatingServer                  : xan-dc02.xand1.mydomain.com
IsValid                            : True
ObjectState                        : Changed

Any idea how to make it work? We use Split DNS and one DNS entry for both internal/external clients (webmail.mydomain.com).

Hello All...

Trying to uninstall Exchange 2013 CUv2 v2. I've moved all the Mailboxes, Arbitration, Discovery, Public Folder, etc to another working server. Everything was moved over fine. Uninstall via the control panel proceeded as normal, then just failed. No choice but to exit. Now when trying to recover, and uninstall again....I cannot. I get the vague error of "An incomplete installation was detected.  Run setup to complete Exchange installation." 

Not that I want to, but tried to reinstall, but can't do that either.

I know it's a last resort and not supported, but can I just use ASDIEdit ,and manually remove the server references? If so, what is a good guide on the procedure....? I don't want spend hours pouring over setup logs and the registry if I don't have to- just want this removed from AD.

I've searched the net quite a bit on manual removal, but can't find a concise how-to...

Any help is appreciated ...Thanks

This is still a problem with installing CU5.

Do you have just a few less than an infinite number of monkeys writing your code these days?

-=Chris

I was having insurmountable problems trying to install Exchange 2013 SP1 on a production 2008 R2 SP1 server for a customer. So eventually I gave up and tried to install it on an existing virtual W2K8 R2 server running on a VMWare box in my lab. When that failed, I created a brand new VM, installed W2K8 R2 SP1 and then installed Exchange 2013 SP1 on there and FINALLY a working system. SO now exchange is working, at least in as much as I can run the EAC.

I then discovered some further problems. I had installed an Exchange Server many years ago, as a trial, and while that server is long gone and using ADSI Edit I had removed the Exchange values from my AD, lo and behold there are some "mailboxes" left over. However, these mailboxes can't be deleted because "the object does not exist". This seems like a bizarre situation. How can a system enumerate items that don't exist? That just reeks of dreadful software design. A solution to that problem would be appreciated.

But the main problem I have is probably far simpler, but I can't figure it out. The company I am doing this for is called, for the sake of argument, ACME. When I originally set up their AD they didn't have a registered domain name so I called it "acme.local". And now I have all the users in that domain. When they got email, and hence a domain name, let's call it acme.com, they used Outlook to access POP accounts on an external server. Now I want to set up exchange. But the AD only knows about acme.local but exchange seems to demand that the AD has a domain acme.com.

One possible solution would be to rename the acme.local domain to acme.com but there doesn't appear to be a way of doing that using any of the RSATs. I can see where I can set up a "receive connector" and specify acme.com, but can I convince Exchange to deliver email addressed to user@acme.com to the AD user user@acme.local

If someone can point me in the right direction, I'd be very grateful. I'm also open to suggestions on what is a good book to understand Exchange 2013. I find Microsoft documentation in general to be very confusing. They use English words but arranged in such a way that the meaning is totally obscured.

Thanks for reading.

When I log on as Administrator to either .../ecp or .../owa, authenticaion, I believe, succeeds but then I get HTTP 500.

When I do this on another server hosting the Exchange server for the same Organisation, I succeed - can get into both the mailbox and the Exchange server ECP interface. Unlike the first server, this Exchange server does not host any mailboxes but otherwise has identical Exchange roles installed.

When I log on as another non-administrator user to the first server that hosts mailboxes, I again succeed.

The problem seems to relate the administrative interface that the first server somehow fails to display but what could be the reason for that?

Thank you.

Hi,

we are currently in the progress of migrating more and more customers to Exchange 2013. Now there is a limit for large Items within public folders. We do know that we have large items and it is OK to wait for the replication to be done but how can we also migrate those large items?

For instance within the public folder Migration-Request log we find:

15.06.2014 22:28:37 [EXCHANGE] A large item was encountered: Item (IPM.Note) Subject:"MESSAGESUBJECT",
 Size: 22.69 MB (23,795,978 bytes), Folder:"PF Folder Name"

Now I'm aware of the switch -LargeItemLimit but with that we will loose those large items. I haven't found any switch to enable the move of those large items - anyone an idea to also get those items moved to modern public folders?

Thanks!

Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

Hi everyone,

Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.

On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.

The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's

The main problems are as follows:

1. There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport Service.
   The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long...  It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
   
2. I receive an error in the Event Log regarding RPC over HTTP Proxy to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down this post

The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs for over chatty warnings about disk space (the warning is that we have loads of space...)

This is a brief outline of the environment:

Exchange 2007 SP3 RU13

UK - Two physical locations in a stretch LAN (100Mb WAN)

4 x CCR Cluster Mailbox Servers in two separate CCR Clusters

Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.

Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.

Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.

2 x Virtual Windows 2003 R2 - Hub Transport Servers

2 x Virtual Windows 2003 R2 - Client Access Servers

1 x Virtual Windows 2003 R2 - Unified Messaging Server

1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)

US - One physical location

1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server

Exchange 2013 CU5

UK - Installed into same site along side Exchange 2007 servers

1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server

Problem 2 Error Message - Please note, server names and domain name changed:

Log Name:      Application
Source:        MSExchange Front End HTTP Proxy
Date:          18/07/2014 10:00:37
Event ID:      3005
Task Category: Core
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EXC2013.domain.local
Description:
[RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
Event Xml:
<Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
  <System>
    <Provider Name="MSExchange Front End HTTP Proxy" />
    <EventID Qualifiers="32768">3005</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
    <EventRecordID>64832</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EXC2013.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>RpcHttp</Data>
    <Data>EXC2007CAS1.domain.local</Data>
    <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
    <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
  </EventData>
</Event>

Hi, I get following error on my new Exchange 2013 server:

 It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

Mailbox database is mounted and contains mailboxes (also system mailbox), ipv6 is enabled on the exchange server.

Is there any logging I can find to see what's going on actually? The transport service won't start either.

Hello everyone,

I'd like to know if it is ok/safe to install Exchange Server 2013 on Windows Server 2012 Standard?

As I started doing some research and noticed a page where Microsoft states they don't recommend running Exchange on Server 2012 Standard, and recommend making 2 different servers one for Active Directory and another for Exchange.
On that page they also listed some features that wouldn't work in case of Exchange is running on Server 2012. And that it may put a larger data load if setup this way.
I am hoping someone knowledgeable can explain and tell me if it is safe to use such setup or if it is better to use something like SBS 2011 Standard instead, which has Exchange included?

Has anyone installed Exchange 2013 on Server 2012 Standard successfully and used it for more then several months without problems?

Also just to give an idea on my background, I've been in IT field fairly long but haven't really updated to newer versions much and mainly used SBS 2003 and 2008 only with a few clients so haven't used 2008 too much.

Thanks in advance.

Hello,

I am in the process of deploying Exchange 2013 in our environment, it will co-exist with Exchange 2010 until we move everyone over to the new server.

My question is regards to the disk storage design, we have a SAN that Exchange will share with the rest of our Virtual Machines. I plan to have 20 live databases and 20 archive databases so I can balance out mailboxes per database so that each db is roughly 100GB in size.

The goal is is to keep the size down so that any database specific maintenance can finish quicker and if I ever had to deal with db corruption it is faster to restore, backup, etc.

My question is, is there a lot of overhead I will be adding onto the Exchange server by having 40 databases mounted?

Currently 300 users, 3.5TB in exchange databases between live and archive mailboxes (no mailbox caps), with 40 databases (20/20) it spreads out nicely with roughly 15 users per db, and db size is roughly 100GB. 

My concern is having 40 databases mounted on a single EXCH2013 multi-role server? We have no DAG, etc.

The machine is a 4vCPU/32GB and the disks are on a Compellent tiered SAN shared among other VMs.

Thanks.

mail client use ms.outlook 2007, everything ok when it's use first time after setup, next business day it's show error and status disconnect

"Task 'Microsoft Exchange Server' reported error (0x8004011d): 'The server is not available. Contact your administrator is this condition persists."

i've follow this instruction,but not works.

*support.microsoft.com/kb/923575

*forums.msexchange.org/Error_%280x8004011D%29_The_server_is_not_available/m_30795900/tm.htm

note.first time after setup mail client,there's no certificate required pop-up, now each time open it, it's show certificate alert

in security alert,show cross : the name on the security certificate is invalid or does not match the name of the site

After succesfull moving mailboxes from Exchange 2010 to Exchange 2013 (single all role servers in same Forest/AD) error messages are displayed in the eventviewer:

source: MSExchange Management Application
id: 5000

I do have installed a valid 3rd party certificate, all works well on both servers (2010 and 2013). How to fix this before I migrate all other mailboxes from 2010 to 2013?

Thnx Remco

I have installed a Exchange 2013 in one server Hardware. When i wanted to connect Outlook 2007/2010/2013 with the exchange server then i got a error message.

Then i put a registry value in exchange provider that is "DS Server" domain controller name and can configured outlook in mail server not other server but i can not connect with the exchange and got the following error.

Please help me on this...

Hello,

Exchange 2010 SP3 and Exchange 2013 Version 15.0 (Build 913.22) Living in Co-Existence mode.

When I move a test mail box from 2010 to 2013 the outlook client continues to look for the old CAS server. IT appear recycling Exchange Application pools and/or a forced AD replication solves the issue. repadmin /syncall. I would like to have this resolved. I have thousands of mailboxes and recycling or replicating after each mailbox is moved is not acceptable. I see multiple posts on these forums that talk about the issue but none with a solid solution. Can any one point me in the right direction?

Hello,

I have recently tried to migrate a user to another database and I am having some issues. I originally was trying to migrate the user to another database but I stopped it midway and tried to create another migration batch to move the users mailbox. Now I am getting an error saying that MigrationPermanentException: Mailbox 'X' is already being moved to "Y"

Mailbox"X" is already being moved to "Y"

I have since deleted the old Migration Batch and have not been able to figure out how to fix this problem. Any help would be appreciated I am running a VM with Server 2012 and Exchange 2013

thanks in advance

Hi All, 

I was hoping to get some information around which of these values are applied by the client for outlook anywhere connections: 

ExternalClientAuthenticationMethod or InternalClientAuthenticationMethod

We have tested externally and found that NTLM works for mail but fails when trying to auth the directory connection in outlook. So we would like to have external set to basic (Works without issues) and internal to NTLM (Fine within the network) 

Our HLB is F5 and with the source addresses coming from the SNAT local IP I was wondering if the external Auth value will do anything? 

Do we know how client works out whether they are internal or external and which auth setting is used? 

Thanks

Joshua Bines

Hi Team,

Can anyone walk through me for any artical/knowledge for the migration of exchange 2010 sp3 multitenant environment to exchange 2013?

Thanks

Shawn

Shawn

Dear All

    I implement exchange 2013, but our client is not join to domain, we have a problem about certificate warning when try to access owa, both internal network  and external network so my manager decision to buy external certificate, my question is

1. I have 2 cas server with NLB, so it need to install external CA on these CAS only or install to all Exchange server

2. What type of certificate that I should buy ( I used webmail.domain.com/owa   ) 

3. I have other web server used on same these domain, it will have effect or not 

Thank you

I got past the earlier error. Now setup detects an incomplete installation and promises to continue only to fail immediately in "Mailbox Role: Transport service" with the following error:

The following error was generated when "$error.Clear(); 
set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController

" was run: "Property IsHubTransportServer can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

I found similar errors relating to Exchange 2010 (in fact one of the sad bits of all this is all the problems people have with 2013 also happened on 2010) and people muttered about IP V6 but I didn't see any comment that appeared to be relevant. This error appears to be a version error, of some sort. 

Why is Exchange so difficult? Any program that is this much trouble should be free, not several hundred dollars!