Hi,

I am working on our Exchange 2010-2013 migration and have come upon an issue after migrating test mailboxes. After migrating a mailbox to the 2013 database I am able to open it in OWA but when I try to open it via Outlook I get the error message "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)". I also get the same message when I create a new mailbox in the 2013 database and try to open it.

I have deleted and recreated the profile on the client. When I create the profile and let autodiscovery configure the information I get a message that the Ex2013 server is not available and the window comes up allowing me to enter the server and mailbox name. If I enter the Ex2013 server name I get the same error whether I enter the hostname of the server or the full DNS name. When I enter the Ex2010 server name it accepts it and converts it to the DNS name of the Ex2013 server but Outlook will still not open.

Both servers are single servers hosting all the roles. The Ex2010 server is using an internal certificate using the internal DNS. When I originally set up the Ex2013 server I did the same thing but have since purchased a SAN certificate based on our public DNS and installed that. The 2 names on the certificate are webmail.(xxxx).com and autodiscover.(xxxx).com. I was getting certificate errors on machines and now I have the SAN certificate that seems to have solved that problem.

I have a feeling I might have 2 problems, 1 with the autodiscover settings and another with the mailbox looking at the 2010 CAS rather than 2013. After doing some research I'm still a little lost in how I move forward on this one. Any help would be appreciated.

Peter Haase

I'm in the process of migrating a company from a single-label domain & forest, "domainname," to a new "newdomainname.local" domain & forest. EX2013 single-server installed and working on both domains, including autodiscover. Trust is set up and works, cross-domain DNS works from both sides. However...

I can create a Migration Endpoint on ex2013.domainname that points to ex2013.newdomainname.local, but when I try to add a mailbox created in newdomainname.local, none are displayed.

I can't create a Migration Endpoint at all on ex2013.newdomainname.local. I get a message that starts, "We couldn't detect your server settings. Please enter them. AutoDiscover failed with a configuration error: The migration service failed to detect the migration endpoint using the Autodiscover service."

I'm prompted for the FQDN of the other Exchange server. When I enter ex2013.domainname, I get, "Error: The connection to the server 'ex2013.domainname' could not be completed."

Is this expected when one server is on a single-label domain? Is there a way to enable me to use mailbox migration?

TIA

Hello, our organizations have just merged. We have 2 Active directory forests. In forest A we have Exchange 2010. In forest B we have Exchange 2013.

We would like to be able to start sharing Global address books, availability information, and also share mailboxes if possible. We have some users that work in both organizations. We are only creating mailboxes in one or the other exchange environment for now until we get this figured out.

I have read numerous articles and a few books explaining how this can be done with forests trusts, Federated services, Microsoft Identify Life-cycle management for GAL sync. Each one seems to be geared towards Exchange 2010 or below, or two exchange 2013 environments.

We ultimately will be moving to one forest and one brand new exchange environment, however, because of the complexities with our current forests we need to be able to setup some coexistence in the mean time until we can plan out the new environment.

What tools should we be using to accomplish the following?:

1. Sharing of global address books.

2. Availability information.

3. Sharing or delegation of mailboxes across both exchange orgs.

Thank you.

Hello

We are in the middle of an Exchange Server 2007 > 2013 Migration.

We have a single DAG with 4 Mailbox Servers, 2 active, 2 passive between sites (fast link)

We tend to manage Mailbox Moves remotely using ISE & "new-migrationbatch" etc etc.  

There is no information on the batch as to which Mailbox Server is actually doing the work of moving the mailbox and I can only presume that the Server hosting the active TargetDatabase of the mailboxes that are being moved will be.

We wondered if anyone had any recommendations or experience of running migration batches from the Servers themselves, adn if we did if we could expect to see performance improvements?

Thanks

Hi,

I have a multi-site Exchange 2013 environment. The configurations are as below.

Active Directory Sites and Exchange Servers.

SiteA - EXMB1 & EXCAS1

SiteB - EXMB2 & EXCAS2

SiteC - EXMB3 & EXCAS3

All sites are connected via VPN. (Good speed. No latency issues)

All the three Mailbox Servers are in DAG. Only one mailbox database. All servers running Exchange 2013.

I am planning to deploy Edge Servers in the infrastructure (I am doing it for the first time). Normally, it will be in DMZ.

Now, I can deploy 2 Edge Servers for reliability.

Question.

1. Can I deploy 2 Edge Servers and create subscription to all the mailbox server in 3 different site? Or, is it like one edge server can make subscription to only mailbox servers in one Active Directory Site? I am not sure about this and could not find much information from TechNet.

One Edge Server can make subscription to all 3 mailbox server in 3 sites. Similarly, I can make the subscriptions in the second edge server as well. Configure 2 external MX records with the same priority so that there will be some load balancing.
Also, in such a case if the mailbox database become active from a different site, I need not make any new changes to the Edge Servers right?

2. If the first way is not correct, I will have to deploy 1 Edge Server each for each of the Active Directory Site. (In DMZ only, not in domain)

Make Edge Subscription to the mailbox server in corresponding site.

Make 1 MX record and point it to the Edge Server which is subscribed to the Mailbox Server from which the Database is Active. The problem is, every time will have to change the DNS record when ever the database copy is activated from a different mailbox server. And the issues with propagation.. delay..

I am not sure which of the above 2 ways will work. Appreciate suggestions from anyone who have previous experience with similar infrastructure.

Thanks in advance. :)

I am trying to use this utility to move the emails/contacts/etc. in some of my local PST files into an email account on Exchange Online (the cloud) through Office 365.

I have set up the "Online Connection Settings" and have connected successfully using the "check" button to my Office 365 global administrative account.

Next I added my PST file using the  "Add from Folder..." button.

The problem is that when I click on "Set mailbox..."( to direct the emails/contacts/etc. to be added to the correct email address in my company) the list never loads, it simply says "The Central Service is retrieving the mailbox data, try again in a moment".

It has been like this for several hours and shows no signs of change.

I need to be able to load .pst files from my old domain into the exchange cloud and NEVER USE THEM AGAIN. This means actually importing the emails, not just adding the .pst file to Outlook.

Please advise why the tool cannot find my company's email addresses and how to fix.

-Joe

P.S: I have already posted this in the Office 365 forums, they gave me the "not officially supported" nonsense and sent me here.

I am having an issue after deploying Lync 2013 into the same Forest/Domain where Exchange 2013 is deployed. Lync 2013 and Exchange 2013 both work fine, however, when I am in the Exchange 2013 Admin Center and I edit either a Group or a Resource, I receive the following warning:

Environment:  (2) Servers in a DAG with (9) databases, all db's residing on Server1.  I have already patched Server2.  What is the proper procedure for installing the rollup on Server1?  Not all the databases have copies on Server2, i.e. public folders and a couple others. 

Sorry, I didn't see a forum for Exchange 2010.

Thanks,

Hi, I understand this has been discussed before but I don't think previous posts quite cover my scenario.

So here goes... My current setup is a single Exchange 2010 box with CAS, HT, MB, UM. I also a LYNC 2010 box running. I have installed an Exchange 2013 box on a new site (Datacenter), same domain. This has all the pre reqs etc and is configured completely with certs and so on, i have test users running on there fine, i will start to migrate mailboxes shortly. The question is what do i do with LYNC? I want to build a LYNC 2013 box on the new site. Will this impact existing service or is there a migration process for users similar to the Mailbox moves? I dont mind users having to start a fresh on the new system as far as LYNC is concerned if need be - i need this as simple as possible.

Any ideas much appreciated. Carl.

Hi Folks,

I have a Windows 2012 R2 Server with Essentials role and I'm running a Hyper-V instance of Windows 2012 R2 with Exchange 2013 installed joined to domain.  I have been through the wizards and the Exchange Server deployment wizard but I'm stuck with configuring DNS records correctly.

Currently I can browse to https://remote.contoso.com externally and internally which works as expected but not https://remote.contoso.com/owa or any other Exchange pages.  All I get is 404 - File or directory not found.  However if I browse internally to https://exchangeserver.domain.local/owa it works. So I'm guessing 404 is coming from the DC server not the exchange server.  Hence I think its DNS.

Although I have noticed that IIS is on the DC and the Exchange server, showing different Sites.  Does this have anything to do with the issue at hand.  Also the guides are not perfectly clear on how to add the DNS CNAME records.

Would someone be so kind as to point me in the right direction.

Thank you 

Good afternoon

I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.

According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.

'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'

http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx

Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary site and I would like to keep that traffic to the replication network I have configured.

Any insight would be helpful.

Hi,

I've followed several technical articles but still don't have a resolution, the product is Exchange 2010. I have an existing Exchange 2003 which I need to upgrade. I have built three windows 2008 R2 servers, Patched and installed the prerequisites and have installed both the Hub/CAS roles without any issues. When I came to install the Mailbox role I'm getting:

Preparing Exchange Setup

    Copying Setup Files              ......................... COMPLETED

The following server roles will be installed
    Languages
    Management Tools
    Mailbox Role

Performing Microsoft Exchange Server Prerequisite Check

    Language Pack Checks             ......................... COMPLETED
    Mailbox Role Checks              ......................... COMPLETED

Configuring Microsoft Exchange Server

    Preparing Setup                  ......................... COMPLETED
    Stopping Services                ......................... COMPLETED
    Copying Exchange Files           ......................... COMPLETED
    Language Files                   ......................... COMPLETED
    Restoring Services               ......................... COMPLETED
    Languages                        ......................... COMPLETED
    Exchange Management Tools        ......................... COMPLETED
    Mailbox Server Role              ......................... FAILED
     The following error was generated when "$error.Clear(); $arbUsers = @(get-u
ser -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"}
 -IgnoreDefaultScope -ResultSize 1); if ($arbUsers.Length -ne 0) { $mbxname = $a
rbUsers[0].name; $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname}
 -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-Ma
ilboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0) { enable-mailbox -Arbitration -identity $arbUsers[0] -dat
abase $dbs[0].Identity; } } }" was run: "No provisioning handler is installed.".

The Exchange Server setup operation did not complete. Visit
soft.com and enter the Error ID to find more information.

Exchange Server setup encountered an error.

I then attempted to run the prepare AD:

D:\>setup.com /preparead

Welcome to Microsoft Exchange Server 2010 Unattended Setup

Preparing Exchange Setup

    Copying Setup Files              ......................... COMPLETED

No server roles will be installed
    Mailbox Role

Performing Microsoft Exchange Server Prerequisite Check

    Organization Checks              ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
 The Active Directory organization configuration version (13214) is higher than
Setup's version(12640). Therefore, PrepareAD can't be executed.

     A Setup failure previously occurred while installing the Mailbox role. Eith
er run Setup again for just this role, or remove the role using Control Panel.

The Exchange Server setup operation did not complete. Visit
soft.com and enter the Error ID to find more information.

Exchange Server setup encountered an error

Any pointers?

Regards, Julian

Hi

I removed my 2003 exhcange server physically and installed a 2012 server with exchange 2013 on it.

How do I get it to work? Where do I manage the exh 2013 server, through web interface only?

It installed, and worked for a few days (after i first had to remove the 2003 exchange server).
Now i only get "done" in the web interface after loggin in, outlook does'nt find the server when trying to connect to accounts and i can't access it through powershell (exchange management shell) and the Exchange Toolbox does not work neither... The services are running though, but that's about it.

It won't uninstall cause there is mailboxes etc on the mailbox database..

My servers are on a standalone network, cut of from the internett..

How do I get a clean slate to install echange from scratch?? We only have a few users, so they won't mind..

Any help would be appreciated.. As of now, the server does nothing...

Since we have a failing VM Exchange 2013, we need to move the installation to a new server. We have created a new Hyper-V Server 2012 and installed a new Exchange 2013 on it. After connecting the new server to the domain we can see all settings and users of the existing Exchange Installation.

Since the old server has a corrupt RAID, we need to move all data and settings to the new server. We have moved some user mailboxes with the ecp to the new server. They are still working, but mailtraffic takes exactly 1 hour now?! Also these users who logon with Outlook now get the error message 'problem with the safetycertificate of the proxyserver (translated)'. The mail still works, but 1 hour delay.

Can we now move the other mailboxes too? And if we have moved them, how can we move the settings of this server? If we shutdown the old server, will Exchange (the moved one) still be up and running? Because we are afraid that when we shutdown the old server it will not boot again.

Thanx for any tips of leads in the right direction.

Hi all ,

on my side i would like to clarify few queries.

Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .

Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed the autodiscover service to exchange 2013 during coexistence.

When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.

Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?

I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.

http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>

Internal Outlook Connectivity

For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.

For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.

Please share me your suggestions and that would help me a lot .

Regards
S.Nithyanandham

We've migrated users mailboxes from Exchange 2010 to Exchange 2013, and trying to resolve resting nuisances. One of them: now users can't change its membership in distribution groups (universal distribution groups) with Open MemberJoinRestriction / MemberDepartRestriction using Outlook.

Exploring RBAC role entries I discover that they keep reference to Exchange 2010, like this:

(Microsoft.Exchange.Management.PowerShell.E2010) Get-CalendarNotification -Credential -Debug -DomainController -ErrorAction -ErrorV
ariable -Identity -OutBuffer -OutVariable -ReadFromDomainController -ResultSize -Verbose -WarningAction -WarningVariable

Is it Ok Or I have to upgrade RBAC entries?

Dmitry

Dears,

I'm facing a issue with Exchange 2013 SP1 CU5 "15.00.0913.022" suddenly after 2 month of the migration from Exchange 2010 i get the "Unknown" status for Content Index status on any database hosted on two servers only

my new Exchange 2013 topology is : 3 CAS servers & DAG contains 6 Mailboxes servers and 4 lagged Mailboxes servers

The following is the errors and warnings logs on my effected mailboxes servers:

The indexing of mailbox database DB53 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped for '3a5ec474-ea70-42b5-a123-d7ff7e5aadc3 (DB53)' due to the state 'Unknown', error code: 'Unknown'."

   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()

   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)

   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)

The FastFeeder component received a connection exception from FAST. Error details: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.GetItems(Guid flowIdentifier, String outputName)

   at SyncInvokeGetItems(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Event 169 (Search) of severity 'Error' occurred 14 more time(s) and was suppressed in the event log

-------------------------------------------------------------------------------------------------------------------------------------

An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

Server stack trace:

   at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Microsoft.Ceres.CoreServices.Admin.IAdminServiceManagementAgent.SystemInfo()

   at Microsoft.Exchange.Search.Fast.NodeManagementClient.CheckForAllNodesHealthy(Boolean retry)

   at Microsoft.Exchange.Search.Fast.IndexManager.<UpdateConfiguration>b__8()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.<>c__DisplayClass1.<PerformFastOperation>b__0()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[T](Func`1 function, String eventLogKey)

   --- End of inner exception stack trace ---

------------------------------------------------------------------------------------------------------------------------------------

Exchange Server Information Store has encountered an error while executing a full-text index query ("string("ItemWarmUpSearch31febf7b418e44878df6e5623e37c828*", mode="and")"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)

   at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

What i have tried to solve the issue with no luck is: 

1- Reseed the effected Databases

2- Reset the index manually by stop the Search and Search Host Controller services and delete the index folder and start the services again in order to force it to rebuild the index

3- Restart the mailbox server that has the index issue

4- Create the AD group "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group as the following technet article http://support.microsoft.com/kb/2807668

Any Idea will be much appreciated.

Thanks,

Ayman Saleh

Ayman Saleh

Hi!

Our Exchange 2013 Backup is failing due to a vss writer failure. The message in vss writer status is:

Writer name: 'MSMQ Writer (MSMQ)'
   Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Instance Id: {3dbfb560-3e45-4dbe-8284-021982a8126f}
   State: [7] Failed
   Last error: Timed out

Exchange Version is Version 15.0 (Build 516.32)

If it needs to be updated to fix this problem then can we install the newest update which is CU6 directly without installing the previous updated which were released before CU6?

What safety measures we should take before installing CU6 as the backup is not working?

Thanks.

Hello,

We are using Exchange server 2003 on Windows Server 2003 SBS. We have decided to migrate to cloud and use codetwo office 365 tool for migration due to its public folders support.

The migration tool requires SP2 on the server 2003 and due to some reasons which can not be fixed without a repair installation (we do not want to mess with it or stop it), we can not update the windows.

We decided to try a scenario that includes setting up a windows server 2003 on a virtualbox and installing exchange 2003 with the same server name.

We use ntbackup to backup the data and I used this backup to restore the mailbox store and public folder store (with and without Log Files). I followed the instructions in http://www.ciaops.com/storage/tech-docs/NTbackup%20exchange%20recovery.pdf. The problem occurred when I tried to mount the either mailboxes or the public folders at the last step (error id:c1041724). I have tried solving it with the Microsoft support information but I have neither the issues of free space on harddisk nor runningeseutil /p command on the system.

I would like to get some help about how I can do this migration successfully.