I am not an expert in Exchange. I did set up and administer an Exchange server for a customer years ago, and I just persuaded another customer to purchase and install Exchange Server 2013 SP1.

I downloaded the ISO file and extracted it and then did the install. It told me some Hotfixes needed to be installed, so I installed all that were required. It's worth noting at this point that the link to the KB974405 was wrong and I had to search for the hotfix. But eventually all prerequisites were installed and installation began. Apart from taking a long time, it appeared to work.

After installation completed I clicked to allow administration to open and I was unable to administer anything. The link to Exchange Administrative Center failed with a 404. I opened IIS and noticed that Exchange Back End was installed on port 444. Subsequently I observed that the Exchange website appeared to be installed twice, once as Exchange Back End and once under Default Web Site. The first problem was a complaint that a module, which name now escapes me, but which was installed locally had been compiled with a later version of .Net than the website is using. The website is using .Net 4.5.1. In case it matters I had installed Exchange with both the mailbox and client access roles.

After messing around with it for a long time and finding no relevant help on Google, I decided to uninstall and start over. The uninstalled failed because there are mailboxes. Heaven knows where the mailboxes came from since I had never managed to administer Exchange. I attempted to use Get-Mailbox cmdlet but got a response the Get-Mailbox was an unknown cmdlet.

I am considering reverting the server back to a backup prior to the install and starting over, but I am not sure it would be any different the second time around. Does Microsoft have any suggestions. I suppose I could ask for a refund, but then I am left with a dissatisfied customer. 

Please help, I am desperate!

having problems on new server so I followed instructions to remove Exchange Server 2013 Sp1 using ADSI edit p;er these instructions:

http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/

now when I re-run setup for exchange 2013 SP1 I get the error :    

"Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

David Sheetz MCP

I am in the process of migrating resources from an existing AD forest to a new AD forest. There is a 2 way trust configured between the 2 forests. In the old forest we have an Exchange 2007 estate, which we are moving to an Exchange 2013 estate. The new Exchange 2013 environment has been configured and is working correctly. Both forests consist of multiple sites and the Exchange 2007 estate has 2 CAS servers (these are not behind a load balancer) that carry out CAS-CAS proxying to connect to the mailbox servers (that are also CASs) in 4 sites local to users from our single Internet ingress point. On the Exchange 2013 side there are 3 CASs using DNS round robin to connect to 2 DAGs.

I have used the prepare-moveresquest.ps1 script and ADMT to move a user object from old forest to new forest and then attempted to carry out a new-moverequest (from Exchange 2013 servers). However, this is failing with the following error:

[PS] C:\Windows\system32>New-MoveRequest -Identity admt2@es.ec.local -RemoteLegacy -TargetDatabase BedeA-M -Remot
Catalog esbndcesf01b.es.ec.local -RemoteCredential $remote -TargetDeliveryDomain esf-schools.org.uk
The call to 'net.tcp://dcexmb1.esf-schools.org.uk/Microsoft.Exchange.MailboxReplicationService
DCEXMB1.esf-schools.org.uk (15.0.847.31 caps:03FF)' timed out. Error details: This request operation sent to
net.tcp://dcexmb1.esf-schools.org.uk/Microsoft.Exchange.MailboxReplicationService did not receive a reply within
configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.
may be because the service is still processing the operation or because the service was unable to send a reply
message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and
setting the OperationTimeout property) and ensure that the service is able to connect to the client.+ CategoryInfo          : NotSpecified: (:) [New-MoveRequest], TimeoutErrorTransientException+ FullyQualifiedErrorId : [Server=DCEXMB1,RequestId=cf7e69ab-b6fa-41f9-b4db-bcade3619166,TimeStamp=18/07/2014
   8:31] [FailureCategory=Cmdlet-TimeoutErrorTransientException] 705CD530,Microsoft.Exchange.Management.Recipient
  s.NewMoveRequest+ PSComputerName        : dcexmb1.esf-schools.org.uk

Any ideas how I can solve this?

Thanks

I have a standalone active directory server and another server that I want to dedicate to exchange. 

I have everything setup properly. I think..

I can send email's fine. But if I reply or send a new email to an account on the exchange server about a day later I get a failure message: 

The error that the other server returned was:451 4.7.0 Temporary server error. Please try again later. PRX2

I know my domain DNS is setup properly because if I install Small Business Server 2011 everything works fine. 

The only thing I can think of that is different is SBS comes with a DNS and DHCP server already installed. I am letting my router handle that currently. Is there an issue with that?

Thank you for your help.

Hello,

We have 2 Exchange 2013 (build 712) servers in a DAG with distinct subnets. Cisco ASA in between was set to have no filtering between servers in subnet.

We cannot add database copies nor move mailboxes.

Tes-Mapiconnectivty fails with

unspaceId  : e8a087f1-6197-48df-b094-d5c93a7b6070
Server      : CLI-SRV01
Database    : CLI-MDB01
Mailbox     : SystemMailbox{376e8d54-7154-484a-a0a3-58f22d73236f}
MailboxGuid :
IsArchive   :
Result      : *FAILURE*
Latency     : 00:00:00
Error       : [Microsoft.Exchange.Data.Storage.MailboxOfflineException]: Cannot open mailbox /o=First
              Organization/ou=Exchange Administrative Group
              (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CLI-SRV01/cn=Microsoft System Attendant. Inner error
              [Microsoft.Mapi.MapiExceptionMdbOffline]: MapiExceptionMdbOffline: Unable to make connection to the
              server. (hr=0x80004005, ec=1142)

In event log:

Adding database copy fails with

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'CLI-SRV02.CLI.ch'. Hresult: 0xc7ff07d7. Error: Failed to open a log truncation context because the Microsoft Exchange Information Store service is not running. [Database: CLI-PFDB02, Server: CLI-SRV01.CLI.ch]

How can I further verify communication from CLI-SRV02 to CLI-SRV01 ?

Any help welcome

/Patrice

In Exchange 2013, the RPC client access service now runs exclusively on mailbox role and no longer on CAS servers.  THis has caused a rather unique issue wit ha client I'm at.

Said client uses a firewall to separate client machines from server VLAN.  While thye normally only expose RPC/HTTP to the CAS servers in 2010, in 2013 this causes problems.  WHat happens currently is if a client queries for an RPC CAS server he will get the current CAS 2010 servers and the 2013 MBX servers... which have no client ports open to them (nor do they want them).  Eventually the problem will be solved on it's own when clients are upgraded to 2013, things are defaulted to MAPI over HTTPS etc ... but for now what it means is if anyone tries to setup a new profile there is a chance the service will attempt to bind to a mailbox server to which the client has no port access to.

with the remove-rpcclientaccessserver cmdlet gone in 2013, is there any way to disable the the publishing of the mailbox clienta ccess service in 2013?  If I used the blockedclientversions option on just the 2013 servers ... would clients auto-attempt to connect to the 2010 CAS?  

The goal here is to get the clients to ignore the 2013 RPC service until all upgrades and migrations are ready rather than exposing the mailbox servers before they've been tested/cleared.

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...