I need some help with this one. I have migrated Exchange 2007 to Exchange 2013 and decommissioned the old server. Everything was working fine at that time. A few days later I looked in the AD and saw duplicated Groups under ‘Microsoft Exchange Security Groups’ like ‘Organization Management’, ‘Organization Management1', ‘Compliance Management’, ‘Compliance Management1’. I decided to delete duplicated entries with the 1. Something I shouldn’t have done because after that moment I couldn’t manage my exchange environment anymore. Commands like ‘Get-ManagementRoleAssignment’ were not working and I couldn’t manage users with ECP. When I executed the command ‘get-mailbox’ I saw only my own mailbox.

Next I deleted all ‘Microsoft Exchange Security Groups’ and recreated them with  PrepareAD. furthermore I correct RBAC with the following commands, which I found on Social TechNet:

1. Run a powershell session as admin
2. Get-ManagementRoleAssignment
3. Add-PSSnapin *setup
4. Install-CannedRbacRoleAssignments -InvocationMode Install –Verbose
5. Remove-PSSnapin *setup
6. Get-ManagementRoleAssignment

Correcting RBAC solve my problem half. Commands such as get-mailbox andGet-ManagementRoleAssignment are working again and I can access ECP with the Organization Management role. But when I try to change something which involves an AD operation, it failed.I am getting the following message on Exchange 2013 ECP and Exchange Powershell.

Active Directory operation failed on DC1.Local.example.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

I tried several things like the technet forum posts below:

Exchange 2010 and the Exchange Trusted Subsystem

• Looks like the same issue, possible solution: Exchange Trusted Subsystem permissions should have an inherited Full Control from the CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com container.
• Checked with ADSIEdit:
• Services   
• Microsoft Exchange    
• First Organization – (check here)    
• Administrative Groups – (check here)    
• Exchange Administrative Group (FYDIBOHF23SPDLT) – (check here)
• Experience: Exchange Trusted Subsystem has everywhere inherited permission.

Active Directory operation failed in ECP

• Looks like the same issue, possible solution:
• 'full control' on the employee (user) entry in AD to the following groups:
• Exchange Enterprise Servers, Exchange Servers, Exchange Trusted Subsystems, Exchange Windows Permissions
• Experience: Doesn't work.

This error is not retriable. Additional information: Access is denied.

• Looks like the same issue, possible solution:
• Add-ADPermission "User Name" -User "domain\user1" -Extendedrights Receive-As
• Add-ADPermission "User Name" -User "domain\user1" -ExtendedRights Send-As
• Experience: Doesn't work, get the same error message: 'This error is not retriable. Additional information: Access is denied.

Cant Modify or Delete mailboxes DC error

• Looks like the same issue,possible solution:
• Check Inherit permissions
• Experience: Inherit permissions is ticked.

***I can't post the urls because my account isn't verified yet. I will post them later.

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

Re-installing CAS server. This is something I have done before without issue. In order to properly upgrade from Server 2012 to 2012 R2, I have actually deleted the VDisk, created a blank. Installed server 2012 R2, ran prerequisites and hit the Exchange 2013 SP1 setup as follows:

.\setup.exe /IAcceptExchangeServerLicenseTerms /m:RecoverServer

This time, it hit an error trying to install the Frontend Transport Server:

Error:

The following error was generated when "$error.Clear();

set-ExchangeServerRole -Identity $RoleFqdnOrName -IsFrontendTransportServer:$true -DomainController $RoleDomainController

" was run: "Property IsFrontendTransportServer can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

Any assistance would be greatly appreciated.

Hi, 

I am new to this forum, but thought to try it out. I have set up a lab environment with a 2012 dc in domain a together with a dag exchange system of 2 servers with all roles installed on each exchange server. The exchange servers are 2013. 

I have a domain b with a 2012 domain controller - and a 2008r2 server with 2007 exchange installed (sp3). 

I have trusts setup between the two, and I am trying to do a cross migration of some test accounts. I've successfully moved all items - however when I look at the output from the command.

get-moverequeststatistics -identity test1 | fl

it states : 

Message : Warning: The following failure occurred after the active directory modification completed: couldn't find database "LABEX07\First Storage Group\Mailbox Database". Make sure you have it typed correctly.

The database it says it can't find is from the source 2007 exchange server - and I know it exists. I can't see anything else wrong with the content of whats moved to the 2012 domain except for that message. Does anyone have an idea of what it means? My movement code was

.\prepare-moverequest.ps1 -identity test1@domainb.local -remoteforestdomaincontroller dc01.domainb.local -remoteforestcredential $remoteuser -localforestdomaincontroller dc01.domaina.local -localforestcredential $localuser

followed by the new-moverequest 

new-moverequest -identity test1 -remoteLegacy -remotecredential $remoteuser -remoteglobalcatalog dc.domainb.local -targetdatabase 'mailbox db 1' -targetdeliverydomain domaina.local

Hi all,

Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.

 When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:

The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'

Why would I get this error? The install itself was problematic so I am concerned something is broke.

Thank you in advance.

Hello.

I am implementing co-existence with Exchange 2007/2013. I have a Kemp Loadmaster 2600 that I am getting ready to configure with ESP.

I have two 2013 Edge Transport boxes that will sit in my DMZ in a cloned configuration.

I have created an SMTP VIP in my DMZ that will load balance smtp traffic to these two ips on the dmz.

Once cutover all SMTP traffic will be pointed to this VIP on the dmz. An edge subscriptions will be setup for my hub transport.

Internally I have three 2013 MBX+CAS Servers that I need to balance for the CAS.

Currently we have an external OWA address that is NAt'd back internally to our Exchange 2007 box for OWA access.

My question is, once everything is cutover (namespaces, etc) would it be better to NAT my OWA address to a separate VIP on the DMZ for reverse proxy functionality, or do I need to setup the VIP internally for my CAS servers and Nat this back to this address?

Right now I have a new vip internally set to load balance traffic to the three internal CAS servers at layer 7, but not sure if this is correct.

I just installed Exchange 2013 on a single server and installed SP1 and the lastest CU.  When a message is sent from OWA, it sits in the drafts folder.  There are no errors on the Exchange server and if I run test-mailflow, the following error is returned:

RunspaceId         : 504b7d14-a785-418c-8402-b20b78feb787
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest       : False
Identity           :
IsValid            : True
ObjectState        : New

RunspaceId          : 504b7d14-a785-418c-8402-b20b78feb787
Events              : {Source: MSExchange Monitoring Mailflow Local
                      Id: 1002
                      Type: Error
                      Message: The delivery receipt for the test message from
                      Exchangeserver\SystemMailbox{4b4fb4e8-db56-4d72-adbd-74b3c4673d8e}@domain to
                      Exchangeserver\SystemMailbox{4b4fb4e8-db56-4d72-adbd-74b3c4673d8e}@domain wasn't received
                      within the error latency timeout of 180 seconds. The command will wait until the execution
                      timeout or the arrival of the delivery receipt., Source: MSExchange Monitoring Mailflow Local
                      Id: 1001
                      Type: Error
                      Message: The delivery receipt for the test message from
                      Exchangeserver\SystemMailbox{4b4fb4e8-db56-4d72-adbd-74b3c4673d8e}@domain to
                      Exchangeserver\SystemMailbox{4b4fb4e8-db56-4d72-adbd-74b3c4673d8e}@domain wasn't received
                      within the execution timeout of 240 seconds. The cmdlet will not wait any longer for the
                      delivery receipt.}
PerformanceCounters : {Object: MSExchange Monitoring Mailflow Local
                      Counter: Mailflow Latency
                      Instance: servername\organization1
                      Value: -1}

VERBOSE: [21:39:21.672 GMT] Test-Mailflow : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [21:39:21.678 GMT] Test-Mailflow : Ending processing Test-Mailflow

Also OUtlook clients receive the following error:

Cannot start OUtlook.  Cannot open the outlook window.  The set of folders cannot be opened.  You must connect to Microsoft Exchange with the current profile before you can syncronize yur folders with your outlook data file (.ost).

the attempt to log on to Microsoft Exchange has failed.

Thanks in advance for any assistance on these issues.

Hi,

I am migrating users from Exchange 2010 to 2013 and facing a lot of migration issues. few of them are as follow.

1. It hung up at "syncing" and end up with a failure.

2. After a long migration i got the following errors

Error: MigrationPermanentExeception: Failed to reset the target mailbox after the move. Error Details:MaipExceptionADUnavailable: Unable to prepopulate the cache for user :: on domain controller xyz.domain.com (hr=0x80004005,ec=2414) Diagnosti Context: Lid: 65256 Lid:1494 ---- Remote Context Beg ---- Lid: 52664 StoreEc: 0x96E Lid: 35973 StoreEc: 0x96E Target Mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: Target mailbox connection was lost.

3. users migration is taking a lot of time although mailbox size is not big and both servers are in same datacenter.

Need urgent help pls....

hi,

I'm getting the following error during install . please help me.

Hi. We are about to bring on-prem Exchange back to our organization which is currently hosted. All servers are Windows 2012 R2 and Exchange 2013 will be built on them. We are a little concerned about the Adprep process and need some opinion.

Would Adprep process affect the current state of AD? current users and accounts?

Would it affect the current hosted email? (we don't want email to be cut off)

Is there anything else that we need to be careful about?

Thanks in advance!

In the process og migrating from Ex2007 to Ex2013 we faced an odd problem:

The Ex2013 CAS seems to Proxy/redirect to the Ex2007s old servername, not the New "Legacy.domain.com" name now defined in all the Ex2007ths Virtual directories. This seems to result in a loopback when the old Ex2007 servername "mail.domain.com" DNS is switched to point to the New Ex2013 servers IPaddress. The Connection status at the Outlook Clients do not show any sign of the "Legacy"name and pops up neverending credentials windows.

Did the followin for testing: On the New Ex2013 server I edited the hosts file so that "mail.domain.com Points to the ip of the Ex2007 server and all is "well", Outlook Works like a charm for all mailboxes on both old an New server.

So what have I stumbled upon here, doesn't the Ex2013 server pick up the Legacy name or have I badly misunderstood something With DNS settings during coexistence? Please kick me in the right direction,

Thanks.

* First, I install Exchange 2013 SP1 on my server, so step 14 of 18 to 100% then alert error:

=======================

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: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256  
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x667F9F
    Lid: 57728   dwParam: 0x668155
    Lid: 46144   dwParam: 0x66851E
    Lid: 34880   dwParam: 0x66851E
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
    Lid: 35200   dwParam: 0x548
    Lid: 46144   dwParam: 0x66885A
    Lid: 34880   dwParam: 0x66885A
    Lid: 56264   StoreEc: 0x1388    
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".

========================

* After I run install Exchange 2013 SP1 again, so go to step 5 of 9 then alert error.

* Now, my Exchange 2013 not run. So bad. Please help me fix it! Thank you so much!

Hello Everyone!

We have an issue with pop/imap clients trying to authenticate.

Users log on with credentials from Account Forest, security audit shows a succesful log on and impersonation from process Microsoft.Exchange.Pop3.exe, but fails to login to mailbox.

The following warning appears in the event log:

Log Name:      Application
Source:        MSExchangePOP3
Date:          22/01/2014 11:41:29
Event ID:      2005
Task Category: (1)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      exchangeCAS
Description:
User user1@account.forest wasn't found in Active Directory.

Protocol logs show the same warning.

Seems that Microsoft.Exchange.Pop3.exe process is unable to determine the linked mailbox of the provided credentials.

Hi All,

Getting extremely frustrated now with a new Exchange 2013 installation on a Windows Server 2012 VM...

After having a lot of problems with the installation (didn't uninstall visual c++ which caused failure, then needed to delete the AD Microsoft Exchange System Objects group due to permission failures, etc) I've now got a fully installed Exchange server. Still, now I cannot figure out how to fix my next problem - Accessing the EAC/ECP.

I've searched every possible web guide/forum thread and the only one which is the same issue I'm having is this one: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/89c42771-78c9-4d94-88e5-557320eccc71 

Unfortunately, as you can see in that thread, it is still unresolved. 

Current Issue: trying to access https://localhost/ecp (or any other variation) returns a 404 Not Found.

The error page points the physical path to c:\inetpub\wwwroot\ecp however that folder does not exist. I have tried manually changing the IIS site (Exchange Back End) to point its physical path to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp which seems to be valid, however it doesn't work...

Not sure what else to do... HELP!

Oli

I am importing PSTs that I got out of Exchange 2003 server in to Exchange 2013 SP1

Some of the import jobs are failing with the following error

FailureCode   : -2146233088
FailureType   : TooManyMissingItemsPermanentException
Message       : Error: This mailbox exceeded the maximum number of corrupt or missing items that were specified for this request.

How can I increase the limit for corrupt or missing items ?

Hopping I would be able to restart the request with

Resume-MailboxImportRequest -Identity XXXXXXXXXXXXXXXXXXXX

and provide the user with a list of not imported items from the report below

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics -IncludeReport | fl > x:\Report.txt

MsExchangeMailboxReplication.exe.config has ContentVerificationMissingItemThreshold = 0, 0, MaxInt