I receive the below message when attempting a MoveRequest from my 2010 server to my new 2013 server.  I have successfully moved other mailboxes after seeing a similar message and restarting the MRS.  I have tried the same with this mailbox move and it doesn't resolve.  There isn't anything in the event viewer that points me in any direction.  I have rebooted the target and source servers.  I have run the MoveRequest from the PSShell and the console both return the same results.  Any ideas or help would be great as I'm stuck and don't know why this mailbox is not moving or what I can do to resolve "unfavorable server health".

Informational: The request has been temporarily postponed due to unfavorable
server health or budget limitations. MRS will attempt to continue processing
the request again after 9/18/2015 6:53:36 AM.
Job is waiting for resource reservation. MRS will continue trying to pick up
this request. Details: Resource reservation failed for 'Mailbox Database
0869134059/MdbWrite' (CiAgeOfLastNotification(Mailbox Database 0869134059)):
load ratio 1.79769313486232E+308, load state 'Critical', metric 2147483647.
This resource is currently unhealthy.

Hopefully a simple question someone can answer for me.

Within our environment alias does not match SAMAccountName. When using OWA or Online mode, typing in the SAMAccountName into the To field will happily find the user from what I understand by using Ambiguous Name Resolution (ANR).

Unfortunately when using Cached mode, and thus the Offline Address Book, this doesn't work. Is there a way of enabling SAMAccountName searching within the OAB? I am aware we can force cached mode to use the online address book for searching, but that kind of kills the point of Cached Mode and the OAB.

Environment is Exchange 2013 Enterprise currently at CU9

Thanks

Tony Harper

Dear Team,

We found that abnormal growth of transaction logs on database, which has Migration.8f3e7716-2011-43e4-96b1-aba62d229136 arbitration mailbox.

Just to know you that currently no migration batch is in progress but still the transaction logs are increasing.

Please help or suggest to check the issue.

Regards

Satish D.

I am sure there is some uninstall step that I have missed.  This is a new Exchange installation with no prior install.  The server is 2012 R2 and there are two DCs with 2008 R2.  I was having the error: 

Write-ExchangeSetupLog -Error "Unable to set shared config DC."

I found a thread that said to activate IPv6, which I did.  That did not work, so it then said to uninstall using the command line. Now I get the following error when trying to reinstall Exchange 2013:

Failed [Rule:GlobalUpdateRequired] [Message:Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.]
[12/16/2015 22:18:51.0490] [1] Failed [Rule:LocalDomainPrep] [Message:The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.]
[12/16/2015 22:18:51.0490] [1] Failed [Rule:AdInitErrorRule] [Message:Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.  See the Exchange setup log for more information on this error.]
[12/16/2015 22:18:51.0490] [1] Failed [Rule:ForestLevelNotWin2003Native] [Message:The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.]
[12/16/2015 22:18:51.0490] [1] Failed [Rule:CannotAccessAD] [Message:Either Active Directory doesn't exist, or it can't be contacted.]
[12/16/2015 22:18:51.0506] [1] [REQUIRED] Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
[12/16/2015 22:18:51.0506] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
[12/16/2015 22:18:51.0522] [1] [REQUIRED] The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
[12/16/2015 22:18:51.0522] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx
[12/16/2015 22:18:51.0522] [1] [RECOMENDED] 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.
[12/16/2015 22:18:51.0537] [1] [RECOMENDED] 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.
[12/16/2015 22:18:51.0537] [1] [REQUIRED] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.  See the Exchange setup log for more information on this error.
[12/16/2015 22:18:51.0537] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
[12/16/2015 22:18:51.0537] [1] [REQUIRED] The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
[12/16/2015 22:18:51.0537] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
[12/16/2015 22:18:51.0537] [1] [REQUIRED] Either Active Directory doesn't exist, or it can't be contacted.
[12/16/2015 22:18:51.0537] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
[12/16/2015 22:18:52.0819] [1] Ending processing test-SetupPrerequisites
[12/16/2015 22:18:53.0006] [0] CurrentResult console.ProcessRunInternal:136: 1
[12/16/2015 22:18:53.0022] [0] CurrentResult launcherbase.maincore:90: 1
[12/16/2015 22:18:53.0022] [0] CurrentResult console.startmain:52: 1
[12/16/2015 22:18:53.0022] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[12/16/2015 22:18:53.0022] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/16/2015 22:18:53.0022] [0] CurrentResult main.run:235: 1
[12/16/2015 22:18:53.0022] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/16/2015 22:18:53.0022] [0] CurrentResult setupbase.maincore:396: 1
[12/16/2015 22:18:53.0022] [0] End of Setup

I have tried to run /PrepareAD on both the Exchange Server and a Domain Controller, with the same results.  I am using the administrator account, which is a member of all of these groups, however, the Organization Management group does not exist.  The forest level is 2008 and the domain level is 2008 R2.

I would be very greatful for any assistance.

Thank you.

Team,

we have migrated from exchange 2003 to exchange 2010 server while accessing via Outlook. Instead of TCP/IP it shows HTTPS, we need TCP/IP for internal communication. Also please help share me the ports details for exchange 2010 clients. Which ports are used for clients to server connectivity.

 the ports 

to try to enable the hybrid environment the following error is displayed:

[12/15/2015 19:17:01]   ERROR : System.Management.Automation.RemoteException: Can't read all of the recipient objects that you want to update update using LDAP recipient filter "(mailNickname=*)" of object "EmailAddress". The following exception occurred: Active Directory operation failed on ROKU.ds.iteso.mx. Additional information: Active Directory rejected paged search cookie because a cookie handle was discarded by a Domain Controller or a different LDAP connection was used on subsequent page retrieval. Paged search needs to be restarted and will succeed.
                                Additional information: The parameter is incorrect.
                                Active directory response: 00000057: LdapErr: DSID-0C090753, comment: Error processing control, data 0, v1db1.
[12/15/2015 19:17:01]    INFO : Session=OnPrem Cmdlet=Update-EmailAddressPolicy FINISH Time=48061.8472ms
[12/15/2015 19:17:01]   ERROR : Subtask Configure execution failed: Configure Recipient Settings
                                Execution of the Update-EmailAddressPolicy cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.
                                Can't read all of the recipient objects that you want to update update using LDAP recipient filter "(mailNickname=*)" of object "EmailAddress". The following exception occurred: Active Directory operation failed on ROKU.ds.iteso.mx. Additional information: Active Directory rejected paged search cookie because a cookie handle was discarded by a Domain Controller or a different LDAP connection was used on subsequent page retrieval. Paged search needs to be restarted and will succeed.
                                Additional information: The parameter is incorrect.
                                Active directory response: 00000057: LdapErr: DSID-0C090753, comment: Error processing control, data 0, v1db1.
                                   at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors)
[12/15/2015 19:17:01]    INFO : Task='Configure Recipient Settings' Step='Configure' FINISH Result=False Time=51680.2972ms

Hello All ,

Is it possible to upgrade Exchange 2013 CU6 to CU 11 Directly .

Thank you .

I am planning an upgrade from Exchange 2007 to Exchange 2013 and I have some OWA and Activesync questions.  First, I've done quite a bit of research reading thru the Technet guides, Exchange Deployment Assistant and also going thru the book Mastering Exchange Server 2013. 

Once I install the first Exchange 2013 CAS server, I'm not really sure what happens next or what I should expect. 

1) Exchange Deployment assistant says "As part of the upgrade process, this FQDN will be moved from your Exchange 2007
server to the new Exchange 2013 server. Your Exchange 2007 server will be assigned a new FQDN, such as legacy.contoso.com."

It looks like this is a manual step, not something that happens automatically.  Is this correct?

2) Just because the first 2013 CAS server is installed, this does not affect any clients (OWA and Activesync) that are still on the 2007 server until I change DNS or firewall settings to go to the new Exchange 2013 CAS.

Is this a correct understanding?

3)  If I'm understanding how this works correctly (question 1 and 2), then at what point do I change the virtual directories in Exchange 2007 to "legacy.domain.com"?  My concern is that as soon as I change the VDirs, then all the clients may not be able to access the servers or they'll get an SSL cert error.  I'm assuming I would want to do this at the same time that I'm changing DNS and firewall settings to point to the new Exchange 2013 CAS server. 

Current Setting     webmail.domain.com --> Public IP 1.1.1.1 (NAT) --> internal IP 172.30.8.12  (Exchange 2007 CAS)

Changes to be made (at the same time):

a) Change firewall NAT to point to new internal IP 172.30.8.13  (Exchange 2013 CAS)

b) Change Vdirs in Exchange 2007 CAS server

Is this correct?

4) Once I make the necessary DNS and firewall changes to point OWA and Activesync clients to the new Exchange 2013 CAS servers, (assuming the client mailboxes are still on 2007 servers) will these clients get an SSL cert error when they get redirected to the legacy servers (i.e. "legacy.domain.com") ?

Per Exchange Deployment Assistant:Your end users will not see or use the legacy host name. It will be used by Autodiscover and Client Access servers when redirecting legacy users to a legacy server.

5) Do I need to create an external DNS record and a public IP address for "legacy.domain.com" ? 

Exchange Server Deployment assistant says: You might need to make changes to your firewall to support this new legacy host name. You might need to add new firewall rules, add an external IP address for your Exchange 2007 server, or make other configuration changes.

I am thinking, if the client never sees that name "legacy.domain.com", why do I need to create a DNS record and external IP?

Hello,

I encounter an error in Exchange 2013 installation to migrate from Exchange 2007 to 2013.

It's a fresh installation on server 2012R2. 

the error is step 1 of 8 : Mailbox role : transport service :

Can you help me ?

thanks

During the configuring prerequisites I receive the below error and can not proceed:

Error:

THe Following error was generated when "$error.clear();

   $keyPath = "hklm:\software\Microsoft\webmanagement\server";

There is more but I can not paste in this forum for some reason.

How can I proceed as the only option on the screen is retry. I had to red x to close out.



Kelly Sietmann

Is there any solid documentation around this?  The below URL is the closest I got and did implement the suggestions but free/busy is still an issue.  This is 2 different domains/forests but using the same email domain in Exchange 2010 and 2013.

http://port25guy.com/2014/11/05/configuring-cross-organization-free-busy-information-in-exchange-2013/

Hello everyone,

I need a help on below scenario where I want to migrate exchange and Lync from Resource forest to user account forest.

Scenario.

I have a forest named xyz.abc.com where I have one domain controller as DC1.xyz.abc.com and all my user account are created here.

I have another forest named gws.abc.com where I have one domain controller as DC1.gws.abc.com and which has two way active directory forest trust with xyz.abc.com

Now in gws.abc.com I have below configured servers.

10 exchange 2013 servers installed (CAS+MBX role) in one AD site.

4 exchange 2010 servers installed (CAS+HUB+MBX role) in another AD site.

All user have linked mailboxes with master account configured in xyz.abc.com

i also have 1 Lync site named Site1 with one pool named pool1.gws.abc.com installed with 3 frontend server, 2 SQL Server in Mirrored configuration and 2 access edge server in HLB.

i have Another Lync site named site2 configured with another pool named pool2.gws.abc.com installed with 3 frontend server and 2 SQL server in mirrored configuration. The frontend server pool in this site is associated with the access edge pool of site1 for external access.

My external domain is abc.com with below configuration.

All records configured in abc.com is pointing to exchange server and Lync server installed in gws.abc.com forest.

My user’s email address & sip domain is configured to follow firstname.lastname@abc.com.

What is the best possible way to migrate complete exchange and Lync environment from GWS.abc.com forest to xyz.abc.com forest?

Any help is greatly appreciated.

Hi All, I would appreciate your advice regarding my new Exchange 2013 server.

Our company IT department decided it was time for a new domain.
Our existing domain is 12 years old, has an incorrect suffix, and had many administrators that did who knows what to it.
We have an existing 2013 Std Exchange server with about 100 mailboxes, I will refer to as ExchangeA.

So last summer we built a new 2012 domain in a new forest and I built a new 2013 Std Exchange server.. I will refer to as ExchangeB.
The two exchange servers were then configured to relay and the test mailboxes on ExchangeB work just fine.
No regular user mailboxes have been migrated to ExchangeB yet.

Our domain migration got delayed and now ExchangeB tells me I have 17 days left in the trial.

So my questions are:

1) can I use the license from ExchangeA to activate ExchangeB, without breaking anything? (I suspect this is a no)

2) can I acquire a temporary license to extend my trial period another say 30 days?

3) what may be my other options outside of spending Christmas and New Years migrating mailboxes to ExchangeB and pulling the license over to this new server?

4) Boss is checking out how much an Exchange Std license would cost...if it is just a couple grand we may simply purchase another one

5) I can let the Exchange trial pass and rebuild the server from scratch.... I really dislike duplicating such efforts...especially when due to my own poor planning.

Many many thanks

Andy

Hi,

I'm trying to apply CU10 to my Exchange 2013 SP1 but i'm getting these errors:

Error:
The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagingRoleNotInstalled.aspx

Error:
The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.BridgeheadRoleNotInstalled.aspx

I have tried this also for CU9 and even for the latest CU11.

i already prepared Schema and AD and using admin user with all access required.

The errors in my setup logs file are:

[12/18/2015 10:22:41.0297] [1] Failed [Rule:UnifiedMessagingRoleNotInstalled] [Message:The Mailbox server role isn't installed on this computer.]
[12/18/2015 10:22:41.0297] [1] Failed [Rule:BridgeheadRoleNotInstalled] [Message:The Mailbox server role isn't installed on this computer.]
[12/18/2015 10:22:41.0312] [1] [REQUIRED] The Mailbox server role isn't installed on this computer.
[12/18/2015 10:22:41.0312] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagingRoleNotInstalled.aspx
[12/18/2015 10:22:41.0312] [1] [REQUIRED] The Mailbox server role isn't installed on this computer.
[12/18/2015 10:22:41.0312] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.BridgeheadRoleNotInstalled.aspx
[12/18/2015 10:22:41.0375] [1] Ending processing test-SetupPrerequisites
[12/18/2015 10:22:41.0375] [0] Exchange Server installation failed during prereq check. Trying to restore the server state back to active.
[12/18/2015 10:22:41.0375] [0] RestoreServer Script Path: C:\Windows\Temp\ExchangeSetup\RestoreServerOnPrereqFailure.ps1

could you please help me on this.

Thanks

Alaa

alaaabdou

Hi,

Currently I'm running Exchange 2007 SP3 and I'm getting things ready to move to Exchange 2013.  I've been reading all the steps and things seem somewhat straight forward for setting up the Co-existence with Exchange 2007 and Exchange 2013.

I know one of the steps involves creating an external DNS entry "legacy.mydomain.com" and pointing it to the same IP address as my current owa.mydomain.com address. 

I currently don't have an external autodiscover.mydomain.com DNS entry setup so I was going to have my ISP set that up for me and was wondering if there is any issue with having my ISP also create the legacy.mydomain.com at the same time?

Or do I need to wait until after I've gotten further along with the setup of Exchange 2013 before creating this external DNS entry? 

The main issue is that it takes some time once our ISP creates a DNS entry for it to get published and I'm worried that I might be in a broken or non-functioning state, while I'm waiting for the external legacy.mydomain.com name to get published.

Thanks in advance

Nick

I have a question about the VIPs required to load balance Exchange 2013 client access. How would you typically configure a load balancer to handle both internal and external clients?

It seems to me that you would want want a one-arm configuration for internal clients but two-arm for external. Is that true and, if so, how would that work. Would the internal and external clients connect to different VIPS and rely on split-brain DNS to route them to the correct one?

I'm new to load balancing and would appreciate any guidance on this topic.

Thank you.

Kenny

Salam..

Hy..

Respected Sir/mam/Team..

                                          im trying to install Exchange server 2013 On my Microsoft server 2012, but can't install successfully.it gives me An error at the End. please give me brief Answer and Explain it in Detail i need to teach ECP and OWA to my Students in exchange class.. i will be very thankfull to you for your this act of kindness.

                                                                     hazrat Usman Barki 

                                                                      hazratusmanbarki10@gmail.com

Error:
The following error was generated when "$error.Clear(); 
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "Unable to set shared config DC.".

Hello,

When Installing Exchange 2013 on server 2012 I get the following error during Step 1 of 8 of Transport Service. I have installed and unistalled Exchange a few times, restarted the machine manually and removed exchange from AD, etc. to no avail.

Any suggestions will be very much appreciated.

Thank You.

VK