Cannot Adding Mailbox Server for Database Copy for Exchange 2013 SP1

Before I upgraded to 2013 SP1 everything works find but after I upgrade to SP1 I cannot add database copy. the details are...
I have 2 sites
Site 1 : 4 Mailboxes (Mailbox01,Mailbox02,Mailbox03,Mailbox04)   + 2 CAS
Site 2 : 2 Mailboxes (Mailbox05,Mailbox06)   + 2 CAS  (just for standby site)
So I have 2 DAG group  (6 Mailboxes separate to 3 Mailboxes for 1 DAG group Mailbox01,Mailbox02,Mailbox05 for DAG1  and Mailbox03,Mailbox04,Mailbox06 for DAG2)
After I upgrade Exchange 2013 to SP1 , I try to create new database on Mailbox01 and after that I try to add mailbox02 and mailbox05 to database copy of new database that I created.
"Mailbox05 can added to be database copy but Mailbox02 cannot add database copy for it , Error "Network path not found" occur" but Im very sure that path is the same for each mailbox database server.
so I try to create new database on Mailbox 03 and add database copy on mailbox04 and mailbox06.... the result is the same only Mailbox06 can add mailbox copy of database.
It look like I cannot have 2 mailbox in site 1 for database copy of each new database (I already try to create new database on Mailbox 02 and add database copy on mailbox01 and mailbox05 , the result is only mailbox05 can be database copy of database).
Please help me to fix this out.

Hi,
I recommend you check if the Remote Registry service is running on Mailbox01, Mailbox02, Mailbox03 and Mailbox04. If not, please start it and then add mailbox database copy to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

  • Failed to Manually Seed the Mailbox Database Copy on Exchange 2013

    Hi,
    I tried to manually seed the mailbox database copy via exchange shell by run this command
    Update-MailboxDatabaseCopy –Identity “DB_name\Server” -sourceserver "Name Server" –DeleteExistingFiles.
    However, i got the error message whereas shown below.
    A parameter cannot be found that matches parameter name 'identity'.
        + CategoryInfo          : InvalidArgument: (:) [Update-MailboxDatabaseCopy], ParameterBindingException
        + FullyQualifiedErrorId : NamedParameterNotFound,Update-MailboxDatabaseCopy
        + PSComputerName        : XXXX.abc.XXX
    Any ideas?

    I hope database is in suspended state and not in failed state.
    Make sure EMS is running As Administrator.
    http://technet.microsoft.com/en-us/library/dd335201(v=exchg.150).aspx
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Error while adding member to the dag in exchange 2013 sp1

    I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
    Senior Technical Consultant, MDS Computers

    When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
    [PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
    WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
        + CategoryInfo          : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
        + FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
       mConfigurationTasks.SetDatabaseAvailabilityGroup
        + PSComputerName        : <server>
    Also, this is logged in the eventlog:
    Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
    ErrorReportingEnabled: True 
    Definitely looks like a problem creating the filewitness share.
    Frank.

  • Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

    Hi Everybody,
    For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
    When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
    This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
    So i did the traditional cmdlet
    Get-SendConnector
    Set-SendConnector -Indentity "connector name" -Port 551
    Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
    When i type Get-ExCommand
    Any reference to SendConnector and ReceiveConnector are not on the list.
    Am I missing somethings?  This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
    I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
    The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials.  However, i very much doubt the on-premise installation add-on to SBS would cause any issues
    to missing cmdlets.
    I searched all over the internet and found nothing.
    Now my biggest fear is to re-install Exchange and import the mailboxes manually.
    Any help is greatly appreciated.
    MattLok

    Hello
    check role asigment for your user:
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
    sorry my english

  • Exchange 2013 SP1 server working for several months now messages are getting stuck in drafts folder

    This a small, simple environment. There is a MS Server 2012 R2 server hypervisor with a MS Server 2012 R2 VM running Exchange 2013 patched to SP1.  This server has been deployed into production and passing mail without issues for several months.
    Upon initial deployment, we experienced the issue that many have reported and that has been widely documented where Mail Flow works fine inbound, but outbound will stick in the drafts folder. We resolved the issue by manually configuring the IP Address of
    our internal DNS server (which is an installed role on our hypervisior / base layer server).  The issue was immediately resolved and mail was flowing in both directions without issue.  We later installed SP1 and there was no issue.  Mail has
    been flowing normally all the while.
    Now fast-forward through several weeks of reliable mail delivery... We experienced a power loss and a system shutdown and upon reboot, inbound is working and outbound goes to drafts.  I've confirmed DNS Lookup settings in ECP still points to our internal
    server as previously configured.  Both servers have internet access, NSLOOKUP returns expected values, and DNS appears to be working normally.  
    I'm not sure if we had an MS Update that installed with the reboot that caused the breakage, if there was a lingering settings change that took effect on reboot, or what is causing the interruption.  I'm looking for some fresh ideas on where to look
    for answers, and all the information available on the drafts folder issue points to DNS settings that have already been put in place.  
    Any constructive ideas are welcome!   Thanks in advance. 
    David

    Amit,
    Long story short, I'm not sure how or why, but there were a few automatic services that were not starting "automatically."  I'm used to seeing some services that are triggered by the application to start and stop on their own, so I didn't necessarily
    panic when there were a few automatic services that were stopped..
    However, The MS Exchange Health Manager, and the Mailbox Submission services weren't running.  After manually starting the services my drafts folder emptied and we are back in business.. Maybe not "innovative" as you said, but it certainly put us on
    the right track.  We were looking so hard at DNS because of all the reported cases of "stuck in drafts" being related to DNS, we totally overlooked the obvious, so THANKS!
    Now the only question is, what stopped the services and why did they not restart automatically??  

  • Upgrade of Exchange 2013 SP1 Reboots Server During Step 3 "Copy Exchange Files"

    While upgrading Exchange 2013 to the new SP1, the installer reaches step 3, "Copying Exchange Files", sits at 0% for 10-15 minutes and then when without warning the machine will reboot.
    The last couple logs from ExchangeSetup.log are:
    [02/28/2014 00:16:58.0878] [1] Installing MSI package 'C:\Exchange2013SP1\exchangeserver.msi'.
    [02/28/2014 00:16:58.0878] [1] No updates directory was specified for the msi installation.
    [02/28/2014 00:16:58.0878] [1] Installing a new product. Package: C:\Exchange2013SP1\exchangeserver.msi. Property values: DISABLEERRORREPORTING=1 PRODUCTLANGUAGELCID=1033 DEFAULTLANGUAGENAME=ENU DEFAULTLANGUAGELCID=1033 INSTALLCOMMENT="Installed language
    for this product: English (United States)" REBOOT=ReallySuppress TARGETDIR="C:\Program Files\Microsoft\Exchange Server\V15" ADDLOCAL=Bridgehead,FrontendTransport,ClientAccess,UnifiedMessaging,Mailbox,AdminTools,Cafe,AdminToolsNonGateway

    Hi,
    Where did you download the install package?
    Please download the Exchange 2013 SP1 from the following link and install again:
    Microsoft Exchange Server 2013 Service Pack 1 (SP1)
    Thanks.
    Niko Cheng
    TechNet Community Support

  • What is the best practice on mailbox database size in exchange 2013

    Hi, 
    does anybody have any links to good sites that gives some pros/cons when it comes to the mailbox database sizes in exchange 2013? I've tried to google it - but hasn't found any good answers. I would like to know if I really need more than 5 mailbox databases
    or not on my exchange environment. 

    Hi
       As far as I know, 2TB is recommended maximum database size for Exchange 2013 databases.
       If you have any feedback on our support, please click
    here
    Terence Yu
    TechNet Community Support

  • Exchange 2013 sp1 smtp NTLM auth for child domain users

    i have exchange organization with exchange 2007 sp 3 & exchange 2013 sp1.
    there are  all users in Exchange 2013 server (mail flow is through Exchange 2013 server)
    i have single forest, 2 site (site1, site2), root domain root.local and 1 child domain ch.root.local
    DC  for child domain is located in site2 (dc.ch.root.local)
    multirole exchange 2013 server is installed in root domain.
    i am traing to configure smtp receive connector with NTLM auth and have one problem.
    when user in child domain try send email through this receive connector i see in log
    <,AUTH NTLM,
    >,334 <authentication response>,
    *,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
    *,CH\user1,authenticated
    *,,Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user
    *,,"Setting up client proxy session failed with error: 451 4.4.0 Primary target IP address responded with: ""535 5.7.3 Unable to proxy authenticated session because either
    the backend does not support it or failed to resolve the user."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 192.168.1.15:465"
    but authentication is succesfull for users from root domain.
    why do it can be?
    Thanks.

    thanks for link
    at smtp receive logs (Hub transport role) i've found the  next:
    Client Proxy EXMAIL2013,08D134DAF6CE1C51,49,192.168.1.15:465,
    *,NT AUTHORITY\SYSTEM,authenticated
    >,235 <authentication response>,
    <,XPROXY SID=08D130D354F520D1 IP=192.168.1.21 PORT=57085 DOMAIN=[192.168.1.21] CAPABILITIES=0 SECID=Uy0xxx...
    *,,Error while looking up SamAccountName chuser: The user name or password is incorrect.\r\n
    *,None,Set Session Permissions
    >,250 XProxy accepted but user identity could not be obtained,

  • Exchange 2013 SP1: Fix for failing MSExchangeTransport service

    We had a newly updated Exchange 2013 SP1 that would not start the Transport service
    "Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
    After many tears, I found this solution: 
    Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive.  Disable it.
    Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
    If both services restart normally, troubleshooting is complete.
    We use several custom connectors carried forward from the previous installation, which was SBS 2008.  If this applies to you, take notice.

    Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
    1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
    2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
    Step by Step Screencasts and Video Tutorials

  • Exchange 2013 sp1 move databases

    Hello all
    I am running Exchange 2013 sp1 in a two node DAG. Originally the DAG  had two under powered servers, i built two new more powerful servers added the servers to the DAG, then i moved database copies to the new servers, removed the copies from the original
    servers and then removed the original servers from the DAG. The two original servers are multi role (CAS Mailbox) and currently they are still in the org. My confusion is around this. When i run get-mailbox -identity <name>. The output from the command
    shows the mailbox is on oldserver.  Again oldserver was removed from the DAG and no databases exist on the server. I want to remove the two old servers from the org, but i am hesitant on doing this because all mailboxes seem to think they exist on oldserver 
    Thanks for any help
    Bulls on Parade

    You can ignore that:
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-homemta-and-msexchhomeservername-are-not-updated-on-mailboxes.aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 SP1 Install fails on step 5 of 9: Mailbox Role: Mailbox Service

    We have exchange installed on a windows 2008 R2 box.
    We keep getting the following error when we try to install the update:
    Error:
    The following error was generated when "$error.Clear(); 
              if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
              if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
              Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
              $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox.".
    Error:
    The following error was generated when "$error.Clear(); 
              if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
              if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
              Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
              $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox.".
    Any help would be greatly appreciated!
    Thanks, 
    Wes

    Hello,
    Please make sure you do exchange server upgrading or a clean exchange 2013 installation. If you do a upgrading, please refer to the similar thread to assign a database to the arbitration mailbox "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}".
    http://social.technet.microsoft.com/Forums/en-US/239cb4a6-4a07-4b9a-800c-974573bbff32/error-installing-step-12-mailbox-role-service-on-exchange-2013-cu2?forum=exchangesvrdeploy
    Please make sure you have these permission "Schema Admins, Domain Admins and Enterprise Admins" to install exchange 2013 server.
    If this is a clean exchange 2013 installation, please try to recreate the system mailbox to check the result.
    Cara Chen
    TechNet Community Support

  • Exchange 2013 SP1 Installation Errors I Cannot Resolve

    Good Afternoon All -
    Note:  I updated this post an hour after posting.  Still no solution, but please see updated info at end of this post)
    I'm trying to introduce Exchange into an existing, small environment.  The server I'm trying to install it onto is an SBS 2011 server (single server.)  Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
    had attempted to uninstall it before.  Yes, it's being installed onto a server with a DC.  I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
    Before I started, I made sure all Exchange data had been removed.  I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
    When I try to install Exchange 2013 SP1, I get the below errors.  I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one.  I've restarted the server many times when making
    changes or applying various updates and still get flagged to restart during installation.  I've tried the SBS 2011 repair disc as well, but had many issues with it.  In all honesty, the whole server needs to be wiped and re-installed, but
    cannot do at this point.
    Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below.  Also below are system specs.  The only edit I made in them is a find/replace for server and domain name.
    ExchangeSetupLogs Folder
    System Specs
    Xeon E31270 3.4Ghz
    16gb RAM
    Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
    C:\ - RAID 1 = 500gb
    D:\ - SATA HDD = 320gb
    E:\ - SATA HDD = 320GB
    Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
    Any help would be appreciated - Thanks!
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
    Without this update, the Outlook Anywhere feature may not work reliably.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
    Error:
    There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
    run Setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
    Error:
    The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
    http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ben K.
    UPDATE
    I just tried fixing a few things and tried again.  Still no luck.  Below is what I changed as well as the errors received.  Only option was Retry.  Can I just not install it onto this environment?
    What I Changed
    Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
    Installed KB2619234 for Outlook Anywhere
    Installed 12 updates - Server fully patched
    Exchange Setup Errors
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Thanks Guys -

    Hi,
    Agree. Windows Server 2011 SBS x64 can be the problem.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

    Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
    users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
    I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
    As you can see from the error above  ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
    virtual folders?!
    What I’m missing here?! Please help.

    Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
    To check whether inheritance is disabled on the user:
    1.Open Active Directory Users and Computers.
    2.On the menu at the top of the console, click View > Advanced Features.
    3.Locate and right-click the mailbox account in the console, and then click Properties.
    4.Click the Security tab.
    5.Click Advanced.
    6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
    Ref:
    http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
    Also check the Virtual directory authentication
    Microsoft-Server-ActiveSync
     •Basic authentication
     •SSL required
     •Requires 128-bit encryption
    Ref:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    Check the IIS log if you are able to find any error message on it
    Exchange Queries

  • Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

    Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
    Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
    I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
    Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
    move them to the new server and mount them and relocate the mailboxes?
    Frank.

    Hi,
    According to your description, I recommend you consider using DAG to achieve your requirement.
    The following steps for your reference:
    1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
    2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
    3.After replication, you can mount all the databases on the new server.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support
    This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
    Please Unmark it!
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

Maybe you are looking for