Getting REAL frustrated installing Exchange 2013. Tried to install MSDN Exchange 2013 and then update it with CU3 and that failed all over the place with exceptions.

So I am trying to install a "fresh" CU2 installation from command line and it goes quite a long way in the setup and then fails at  Mailbox Role: Mailbox service. Fails trying to mount the database with "The Exchange server for the database object "Mailbox Database 0637172224" wasn't found in Active Directory Domain Services. The object may be corrupted."

As previously mentioned I did a complete error free install with MSDN 2013, no problems. Previous to CU2 install I installed all prerequisites, setup/ps, setup/PreapreAD, setup /pd.

Done searching for answers as this is gotten to be more than a headache. The goal here is to migrate Exchange 2007 to 2013 and I need at least CU2.

Any idea's???

Hello Team,

We are planning to go for Exchange 2013 for 300 mail boxes and looking for the best way of deployment.

Questions:

1.How many servers required for fault tolerance for 300 user mailboxes?<o:p></o:p>

2.What are the Hardware and software specifications?<o:p></o:p>

3.Is there any documentation for DAG concept in Exchange 2013?<o:p></o:p>

4. Which License (Standard/Enterprise) do we require for 300 users mail boxes?

Please advise. MANY THANKS.

I'm currently in the process of merging users from 1 domain to another.  I want to make this as simple as possible, since it's a limited amount of people(20 users) I'm just going to backup email to a .pst file.  Then add there domain name as an accepted domain in our Exchange 2013 Server.  Aside from the internal/external routing is there anything else I need to do?  Would I have to add there domain name to our certificate?

Thanks

We migrated from 2010 to 2013 with that being said , we also consolidated few forests into 1 main forest so

forestA.forestB,forestC are now all on MainForest - users / email / AD - basically everything.. 

We dont have any mail flow issues however I am getting lots of errors since we shut down the forestA/B/C DC's (active directory).. 

Errors:

•  Failed to connect to the Active Directory in the remote forest forestA.coM

Please check for misconfigurations on the ServiceBinding attribute on the Service Connection Point object CN=ForestA.com,CN=Microsoft Exchange Autodiscover,CN=Services,CN=Configuration,DC=MainForest,DC=com 

Note: Looking at the SCP above in config of AD, it states true that I have two objects: MainForest and ForestA.com ... so my assumption is that I could just delete that object and should be fine? ... Please let me know if thats the case.. 

Error 2:

Process w3wp.exe (OWA) (PID=10016). WCF request (GetServerFromDomainDN DC=forestA.com,DC=com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running

Hi Experts, I had been primarily a RHEL guy in the past. Currently, I have 3 Node (All-in-one) Exchange 2013 DAG (all 3 nodes are virtualized in Hyper-V 2012 and are a part of HyperV2012 Cluster). In DNS, I have created 3 A records for mail.domain.com which resolve to to the Public IP addresses (MAPI IP address) of all 3 CAS servers. And I have also enabled Outlook anywhere. OWA internally is working fine.

I would like to know: what else do I need to do in DNS (& elsewhere in EAC) to get Outlook 2013 (MAPI/CDO client) & OWA work from both within & outside the corporate network (via the internet). I mean, in terms of additional Resource records in DNS, SRV records, MX records, new zones, URL settings of each server for each service, virtual directory changes etc. I am not sure which all RR's in DNS would be needed, how they should be set & what purpose each of them would server.

A simplified (but detailed) explanation would be better because I have never dealt with Outlook anywhere before.  Would be great if experts could point me to relevant blogs & online resources that contain valid examples of accomplishing the same.  Thanks in advance.

Regs,

Rahul

I have read that legacy public folders and 2013 public folders canot co-exist.
If I have legacy public folders A, B and C, does this mean...

 that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
..or..
 If I migrate folder A to 2013, I must migrate folders B and C also.

If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality 2013 PF has that the users will lose if the folders are down graded to legacy?

Thanks!
Tom

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks

Hello

I found annoying issue with CU6 setup. When you try to use GUI setup using setup.exe everything goes fine until it reaches prerequisites analysis. It goes to 100% and display "back" and "install" buton but they are not working. You cant't also finish Setup using close button. I try few times reboot and resetup again without success.

Then I try to make Schema and AD prepare using setup.exe from command line.

Then I got this error:

Performing Microsoft Exchange Server Prerequisite Check

Prerequisite Analysis                                     FAILED
The fully qualified domain name (FQDN) of the local computer matches the SMTP address of recipient policy 'Default Policy'. Setup can't continue. For more information, visit (...)

It's strange because this error should be reported in GUI setup windows instead of freezing it.

When I removed SMTP Recipient address from 'Default policy', evrything goes just fine. Maybe this will help some of you.

Cheers Pacek. 

When I open EMS I got this error:

VERBOSE: Connecting to SERVER01.Elfring.local.
New-PSSession : [server01.elfring.local] Connecting to remote server server01.elfring.local failed with the following e
rror message : De WinRM-client kan de aanvraag niet verwerken. Het authenticatiemechanisme Kerberos is gebruikt, maar d
e toegang tot de doelcomputer (SERVER01.Elfring.local:80) is geweigerd. Wijzig de configuratie zodat het authenticatiem
echanisme Kerberos is toegestaan of geef een van de authenticatiemechanismen op die door de server worden ondersteund.
 Als u Kerberos wilt gebruiken, geeft u de naam van de lokale computer op als externe bestemming. Controleer ook of de
clientcomputer en de doelcomputer lid zijn van een domein. Als u basisauthenticatie wilt gebruiken, geeft u de naam van
 de lokale computer op als externe bestemming, geeft u basisauthenticatie op en geeft u gebruikersnaam en wachtwoord op
. Door de server kunnen de volgende mogelijke authenticatiemechanismen worden gerapporteerd:   Digest Negotiate For mor
e information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
VERBOSE: Connecting to SERVER01.Elfring.local.
New-PSSession : [server01.elfring.local] Connecting to remote server server01.elfring.local failed with the following e
rror message : De WinRM-client kan de aanvraag niet verwerken. Het authenticatiemechanisme Kerberos is gebruikt, maar d
e toegang tot de doelcomputer (SERVER01.Elfring.local:80) is geweigerd. Wijzig de configuratie zodat het authenticatiem
echanisme Kerberos is toegestaan of geef een van de authenticatiemechanismen op die door de server worden ondersteund.
 Als u Kerberos wilt gebruiken, geeft u de naam van de lokale computer op als externe bestemming. Controleer ook of de
clientcomputer en de doelcomputer lid zijn van een domein. Als u basisauthenticatie wilt gebruiken, geeft u de naam van
 de lokale computer op als externe bestemming, geeft u basisauthenticatie op en geeft u gebruikersnaam en wachtwoord op
. Door de server kunnen de volgende mogelijke authenticatiemechanismen worden gerapporteerd:   Digest Negotiate For mor
e information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
VERBOSE: Connecting to SERVER01.Elfring.local.
New-PSSession : [server01.elfring.local] Connecting to remote server server01.elfring.local failed with the following e
rror message : De WinRM-client kan de aanvraag niet verwerken. Het authenticatiemechanisme Kerberos is gebruikt, maar d
e toegang tot de doelcomputer (SERVER01.Elfring.local:80) is geweigerd. Wijzig de configuratie zodat het authenticatiem
echanisme Kerberos is toegestaan of geef een van de authenticatiemechanismen op die door de server worden ondersteund.
 Als u Kerberos wilt gebruiken, geeft u de naam van de lokale computer op als externe bestemming. Controleer ook of de
clientcomputer en de doelcomputer lid zijn van een domein. Als u basisauthenticatie wilt gebruiken, geeft u de naam van
 de lokale computer op als externe bestemming, geeft u basisauthenticatie op en geeft u gebruikersnaam en wachtwoord op
. Door de server kunnen de volgende mogelijke authenticatiemechanismen worden gerapporteerd:   Digest Negotiate For mor
e information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
VERBOSE: Connecting to SERVER01.Elfring.local.
New-PSSession : [server01.elfring.local] Connecting to remote server server01.elfring.local failed with the following e
rror message : De WinRM-client kan de aanvraag niet verwerken. Het authenticatiemechanisme Kerberos is gebruikt, maar d
e toegang tot de doelcomputer (SERVER01.Elfring.local:80) is geweigerd. Wijzig de configuratie zodat het authenticatiem
echanisme Kerberos is toegestaan of geef een van de authenticatiemechanismen op die door de server worden ondersteund.
 Als u Kerberos wilt gebruiken, geeft u de naam van de lokale computer op als externe bestemming. Controleer ook of de
clientcomputer en de doelcomputer lid zijn van een domein. Als u basisauthenticatie wilt gebruiken, geeft u de naam van
 de lokale computer op als externe bestemming, geeft u basisauthenticatie op en geeft u gebruikersnaam en wachtwoord op
. Door de server kunnen de volgende mogelijke authenticatiemechanismen worden gerapporteerd:   Digest Negotiate For mor
e information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
VERBOSE: Connecting to SERVER01.Elfring.local.
New-PSSession : [server01.elfring.local] Connecting to remote server server01.elfring.local failed with the following e
rror message : De WinRM-client kan de aanvraag niet verwerken. Het authenticatiemechanisme Kerberos is gebruikt, maar d
e toegang tot de doelcomputer (SERVER01.Elfring.local:80) is geweigerd. Wijzig de configuratie zodat het authenticatiem
echanisme Kerberos is toegestaan of geef een van de authenticatiemechanismen op die door de server worden ondersteund.
 Als u Kerberos wilt gebruiken, geeft u de naam van de lokale computer op als externe bestemming. Controleer ook of de
clientcomputer en de doelcomputer lid zijn van een domein. Als u basisauthenticatie wilt gebruiken, geeft u de naam van
 de lokale computer op als externe bestemming, geeft u basisauthenticatie op en geeft u gebruikersnaam en wachtwoord op
. Door de server kunnen de volgende mogelijke authenticatiemechanismen worden gerapporteerd:   Digest Negotiate For mor
e information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

What is going wrong?

We have installed EX13 CU5 in a EX07 SP3CU12 environment.
I changed OWA Virtual Directory on EX13 to FBA with UserName option and selected the domain "fat.local"

Now when i run get-owavirtualdirectory on the EX13 machine no errors are reported and LogonFormat shows userName and DefaultDomain shows fat.local

But when i run get-owavirtualdirectory on the EX07 machine i get error referring to the EX13 OWA default web site saying;

"WARNING: Object DC-PEXCVS1\Exadmin (Default Web Site) has been corrupted and it
 is in an inconsistent state. The following validation errors have occurred:
WARNING: You must set a DefaultDomain if LogonFormat is set to UserName.

Rather strange error cause it does not show this error when running on the 2013 machine.

Hello,

Upgrading from CU5 to CU6 I ran into this error during the installation. Has anyone seen this before or knows a way round it:

Error:
The following error was generated when "$error.Clear(); 
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          {
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          {
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          {
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          }

          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          {
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
          {
            trap [Exception]
            {
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            }
            
            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
          }
          }
          }
          }
        " was run: "Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndLocatorException: Server Locator Service call had a communication error. ---> Microsoft.Exchange.Data.Storage.ServerLocator.ServerLocatorClientTransientException: Server Locator Service call had a communication error. ---> System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://styx2.corp.alpha-data.com:64337/Exchange.HighAvailability/ServerLocator. The connection attempt lasted for a time span of 00:00:04.0683258. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.2.224:64337.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.2.224:64337
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.SocketConnectionInitiator.ConnectAsyncResult.OnConnect(IAsyncResult result)
   --- End of inner exception stack trace ---

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(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 ServerLocator.EndGetActiveCopiesForDatabaseAvailabilityGroup(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.ServerLocator.ServerLocatorServiceClient.EndGetActiveCopiesForDatabaseAvailabilityGroup(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.ApplicationLogic.Cafe.MailboxServerLocator.EndGetServer(IAsyncResult result)
   at Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndLocator.GetBackEndServerByDatabase(ADObjectId database, OrganizationId organizationId, SmtpAddress primarySmtpAddress)
   at Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndLocator.<>c__DisplayClass3.<getbackendserver>b__2()
   at Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndLocator.CallWithExceptionHandling[T](Func`1 actualCall)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndLocator.CallWithExceptionHandling[T](Func`1 actualCall)
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.PrepareDataObject()
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<processrecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".</processrecord></getbackendserver>

Best regards,

David

I'm trying to introduce Exchange 2013 into my existing Exchange 2010 organization. Schema preparation ran fine, but AD Preparation is failing with "The administrative limit for this request was exceeded". I figured out that it is related to "otherWellKnownObjects" attribute under "Services/Microsoft Exchange". Apparently this attribute can hold on 11 records about security groups instead of 17. Looks like it might be related to attribute size.

Is there a way to extend this attribute size?

Thanks.



Regards, Mindaugas Laucius

posting as nothing else can be found relating to ECP redirects to OWA native ex2013 environments.

In Ex2013 CU5 a non-mailbox enabled admin accounts accessing EAC gets redirected to OWA (external URL) and fails.

the unexpected redirect for non-mailbox enabled accounts is actually a bug that had been introduced with Exchange 2013 CU3. (it was fixed in Ex2010 SP1) 

The problem actually is that non-mailbox accounts are redirected to the OWA logon page in the AD site where the arbitration mailbox (SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}) lives in.

This issue will be fixed in a future build15.00.1016.000 which will probably be CU7.

immediate fix - mailbox enable the admin account (breaking the majority of your security policies)

Hello All

I'm in the middle of an Exchange 2007 and Exchange 2013 migration.

I thought I had finished setting up my coexistence between the two; however, it has come to my attention that clients are no longer able to download the offline address book.

Clients are using Outlook 2010 and when they try to manually download the address book they are receiving:
"Task <user> reported error (0x8004010F): 'The operation failed. An object cannot be found"

Distribution on the Ex2013 list is set for web, while Ex2007 is set for Public Folder

The Ex2007 Management tool shows the new one as the default.  Is there a way to get the Outlook clients to automatically download the Global Address List (2013) into their Outlook prior to their mailboxes being moved over?

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.

I am mid way through migrating from Exchange 2007 to 2013. I have been following the instructions on Step-by-Step Exchange 2007 to 2013 Migration (it would not let me link it unverified). I have had to undo some of it in order to keep email flowing for the organization.

From the 2013 ECP, I cannot see the Mailbox Databases residing on the 2007 server. I successfully migrated a single mailbox to the 2013 server. If I have the 2013 server as the internet facing server as per the instructions, I can access the migrated mailbox without any issue via OWA and Outlook. I cannot access any mailboxes on the 2007 server in any way though.

With the 2007 server as internet facing, I can access every mailbox except for the migrated one. There appears to be a disconnect between the servers that is blocking communication.

From my understanding, I should be able to have the 2013 server set up to take over and all mailboxes should be accessible through that server. I have already tried checking some of the answers regarding the public folders (I have not even started to tackle that yet), but none of it seems to apply. I can see the databases from both servers through the management shell with no errors. Other than being unable to access mailboxes on the secondary server regardless of which is primary, I have not seen any errors.

Any help or suggestions would be appreciated.

Hello Everyone,

I've been installing Exchange servers since Exchange 5.5. I'm now installing Exchange 2013 with SP1 that will coexist with one Exchange 2010 SP3 server. I'm installing it on 2012 R2 Enterprise Edition. There is a root domain and one child domain. The Exchange Server is in the child domain.  Even though I've run the .\setup PrepareSchema, AD and domain and all were successful I still get the message below when running Exchange setup. If I look at what /preparedomain does it seems like it has done what is needed. I've run the /prepareschema, /preparead and /preparealldomains in the root domain & have even run /preparedomain over and over in the child domain. Like I said everytime I run these they are successful. Oh and my account belongs to all the right groups needed to run these. Any ideas would be appreciated!