I’ve successfully installed Exchange 2013 CU1 (in a cloned environment so I’m no harm done J) and most thinks seems to work but OWA and Active Sync on EX2007 mailboxes give me some headache.

I’ve created a legacy.company.com DNS record, reconfigured the virtual directories on EX2007 and set OWA to FBA/basic.

OWA IS redirected to EX2007 legacy URL but authentication is not being passed through and you have to enter username password again at the EX2007 OWA site. Active Sync (tested on Iphone) works but you have to enter password at every sync.

What could I be missing?

/Søren Emig

I recently upgraded two Exchange 2010 servers that are both in the same DAG from SP1 to SP3.  The upgrade seemed to go fine, but we are now finding that Out-of-Office messages are not being sent and Moderated Mailbox messages are not being sent.  These facts are only true when the mailbox databases are mounted on EX01.  If I move them all to EX02 I do not see those problems.

After a bunch of digging I’ve found that the “Microsoft Exchange Mailbox Assistants” service on EX01 is failing to start.  It is set to Automatic, and does not start on bootup.  When I attempt to start it manually I get an “Error 193: 0xc1”  This service is configured exactly the same way as on EX02, though on EX02 the service is starting properly and when the mailboxes are mounted on EX02 we do not see these problems.

This was not a problem for either server prior to the upgrade to EX2010 SP3

Has anyone seen this before?  Can anyone suggest where I might look for a solution for this?

I’ve searched the usual sources and I’m only finding a couple of articles that refer to vaguely similar issues with Exchange 2000 or 2007.

Thanks for your input,

Hi All,

I want to upgrade our exchange 2007 SP3 RU10 to Exchange 2013 CU1. please let me know what would be the process / steps

1 should i first install CAS or mailbox

2 do i have to install both or should i go first with CAS and move CAS roles and then deploy Mailbox role

3 should i install both together configure every thing and then move CAS Role

4 do i have to install Exchange 2013 RTM first and then CU1 or should i start the installation directly from CU1

5 if point number 5 is true then Exchange 2013 CU1 is general download will i be able to activate the server with our Exchange product key.

Thanks

If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

Hi,

we are in process of upgrading existing Exchange 2007 to exchange 2013.  follwing the below MS article:

http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx

In the below sction

I've searched for the error I have nothing turned up so I'm hoping to find some help here. Otherwise I'll need to do a full restore. Getting an error in my lab after attempting to install the cu1 update: Couldn't resolve the user or group "DSGTARGET.CORP/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.".

Here's the tail end of the log.

  at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[05/13/2013 14:08:10.0414] [1] [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: "Couldn't resolve the user or group "DSGTARGET.CORP/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.".
[05/13/2013 14:08:10.0414] [1] [ERROR] Couldn't resolve the user or group "DSGTARGET.CORP/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.
[05/13/2013 14:08:10.0414] [1] [ERROR] The trust relationship between the primary domain and the trusted domain failed.

Question: Will an Exchange 2013 server work with an Exchange 2010 Hub Transport and Client Access server?

My environment consists of a single Exchange 2010 server acting as the Mailbox, Hub Transport and Client Access server.  I would like to build out a separate Exchange 2013 Mailbox server (Mailbox only) and migrate the Exchange 2010 DBs (or the user mailboxes) to the Exchange 2013 Mailbox server. Then remove the Exchange 2010 Mailbox role leaving only the Exchange 2010 Hub Transport and Client Access server roles on the original server. After a week, if everything is running smooth, then I will upgrade the Exchange 2010 Hub Transport and Client Access server to Exchange 2013 - keeping the Exchange 2010 Hub Transport and Client Access server separate from the Exchange 2013 Mailbox server.

Any comments and advice would be greatly appreciated.

We are migrating to Exchange 2013 from a 2010+2007 environment.  The 2010 and 2007 may be left in place due to some legacy applications.

The question I have is in regards to certificates on the exchange 2013.

We use a single Godaddy certificate for both the internal and external connections.  Internal and external url's for all services are https://mail.<company>.com/<service>.  The server name is EX2013SRV.<company>.com.  The certificate is used for mobile, owa, etc.

Does the certificate need to have the FQDN of the server on it as well for internal and external access?  I would much rather not have that server fqdn name on a certificate that is external.

One thing I notice is that when I go to the https://mail.<company>.com/EWS/Exchange.asmx, and that hits the EX2013Srv correctly, I get a Service page showing an address of https://ex2013.<company>.com:444/EWS/Services.wsdl.  If I click that I get the xml response page.

In the Exchange 2013 server IIS I see default website and an Exchange Back End site.  The Default site has the GoDaddy cert and the Back End ahs the self signed original cert.

This may be causing issues with our Lync 2013 and some other weirdness with outlook clients we are experiencing.

Any advice or ideas would be appreciated.

When attempting to migrate a mailbox from Exchange 2007 to 2013 DB

I am receiving the error:

The migration mailbox for the organization is either missing or invalid ?

How do I correct this error ??

Event Logged in Applicaiton Log:

Common Sense attempts to resolve:
1. dismount and re-mount default maill DB
2. Create new MB DB - attempt to migrate to new MB DB
3. Create new user with MB in 2013 and attempt to move from default MB DB to Newly created MB DB
**** Needless to say -- nothing works

*** Looked for a Command to recreate Migration Mailbox -- NO such luck

?? how does the auto created "Migration Mailbox" disappear or become corrupt and why is there not a command to fix / create a new "Migration Mailbox"

Addition Attemps that failed:

1. Re-Create the Discovery System Mailbox - as per instructions:
           http://technet.microsoft.com/en-us/library/gg588318.aspx

2. Found this user under "Users" in ADCU
   Migration.8f3e7716-2011-43e4-96b1-aba62d229136

Group membership: Domain Users

this user is disabled as are most of all the special exchange user that are installed by defaut.

Not sure how to proceed from here. ??

Error Message Logged:

I am trying prepare the schema for the exchange server, unfortunately I keep receiving

" Setup encountered a problem while validating the state of Active Directory: Could not find information about the local
 site. This can be caused by incorrect configuration of subnets or sites or by replication latency"  can someone assist with this?

dose anyone know how you can Manually Copy the mailbox database from a failed exchange 2010 server to a new 2010 exchange server 

if anyone can help that would be great my exchange server is down need help I'm almost done building a new exchange 2010 server

gene campbell

Bill Coulter

Hello every one,

I have a problem to migrate mailbox from exchange 2013 to exchange 2007 back.

Recently We have installed a pilot exchange 2013 and already migrate about 100 mailboxes.

But we still have some problems, and need transfer/migrate some mailboxes back to exchange 2007

i'm facing with this problem couple of days from now, can't move some mailboxes i'm geting this message:

Relinquishing job because the mailbox is locked. The job will attempt to continue again after 5/27/2013 10:27:43 AM.

Dear all,

My Exchange is currently Exchange 2003 and Exchange 2007 mixed. I'm going to introduce Exchange 2010 server. Am I require to run /PerpareLegacyExchangePermissions? I have already run it during setup Exchange 2007 beforehand.

Thank you for your kind attention.

Ivan Ho

We have Exchange 2010 running and want to have 2013 in co-existence.

Installation of Exchange 2013 went smooth. Mailbox role server name- MBX and client access server name CAS. After the installation I couldn't access ECP- it was giving"The service is temporarily unavailable. Please try again in a few minutes" error. Event log had event id 2112:

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2276). The Exchange computer DC1.sub.organization.net does not have Audit Security Privilege on the domain controllerDC1.sub.organization.net. This domain controller will not be used by Exchange Active Directory Provider.

Message was repeated for every domain controller.

The first question. DC1 (and others) is not the exchange computer. It is domain controller.Why event log is saying that it is the Exchange Computer?

Digging further... Exchange Active Directory Topology service (2080) discovered the following characteristics:

 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)       
In-site:
DC1.organization.net    CDG 1 7 7 1 0 1 1 7 1
DC2.organization.net    CDG 1 7 7 1 0 1 1 7 1
DC1.sub.organization.net    CDG 1 7 7 1 0 0 1 7 1       
Out-of-site:
DC2.sub.organization.net    CDG 1 7 7 1 0 0 1 7 1
DC3.sub.organization.net    CDG 1 7 7 1 0 0 1 7 1
DC4.sub.organization.net    CDG 1 7 7 1 0 0 1 7 1
DC5.sub.organization.net    CDG 1 7 7 1 0 0 1 7 1

Well, previous event log, probably, makes sense, as it doesn't have SACL right. So I run setup with /PrepareDomain switch. That fixes SACL forDC1.sub.organization.net controller and I can login to ECP or start Exchange Management Powershell without issues. But after a few hours (random number) SACL value is restored to 0 and I'm having problems logging to ECP or starting Exchange Management Powershell. Running /PrepareDomain temporarily fixes the problem again... What is going on? Why SACL is being restored?

Also, seems like policytest utility is removed from 2013 installation. Tried using from the 2010- it ends up withlookupaccountname returned error 1332.

Tahnks, guys, for any ideas!

At first I would like to describe what I have done:

We had a 2008 R2 Server Enterprise as single server so it was PDC and an Exchange 2010 Installation.

The Exchange database crashed and even with esutil and isinteg etc it was not possible to resolve this problem. So we installed a Server 2012 Standard and migrated all roles from the old 2008 R2 to the new 2012 Server. We did not uninstall Exchange. We downgraded the old 2008 R2 from a DC to a memberserver and removed it from the domain. Then we installed on this hardware also Server 2012 Standard and unfortunately named it exactly as the old 2008 R2 before. And added it to the domain as a memberserver. We installed Exchange 2013 according the instructions on Microsoft Exchange Homepage. This was only possible after deleting the existing entries in ADSI Editor in CN=configuration,DC=…./CN=services/CN=Microsoft Exchange.

Then we installed the cumulative update. After that it was possible to connect to the exchange installation with the powershell but not with the webinterface https://servername/ECP

It always granted no access due to authentication error. So we decided to uninstall exchange again. After several restarts we tried to reinstall it again. The installation process stops at the point where it is trying to configure the IIS while installing the virtual directory for PowerShell.

can anyone help me solving the issue?

below you find parts of the ExcangeSetup.log

Ralph from Nuernberg Germany

---------

[05.31.2013 09:29:54.0385] [1] Setup failed previously while performing the action Install.  Looking for the failed task with ID PowerShellComponent___0933481a46d24e77abfdf174e8240b80.
[05.31.2013 09:29:54.0386] [1] 248 tasks were found to run.
[05.31.2013 09:29:54.0386] [1] Processing component 'PowerShell Configuration' (Die virtuellen Windows PowerShell-Verzeichnisse werden installiert und konfiguriert).
[05.31.2013 09:29:54.0386] [1] Executing:
          $vdirName = "PowerShell";
          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

[05.31.2013 09:29:54.0415] [2] Die Active Directory-Sitzungseinstellungen für 'New-PowerShellVirtualDirectory' lauten: Vollständige Gesamtstruktur anzeigen: 'True', Konfigurationsdomänencontroller: 'vc-server-red.vision-computer.local', Bevorzugter globaler Katalog: 'vc-server-red.vision-computer.local', Bevorzugte Domänencontroller: '{ vc-server-red.vision-computer.local }'
[05.31.2013 09:29:54.0416] [2] Beginning processing new-PowerShellVirtualDirectory -Role:'Mailbox' -InternalUrl:'http://vc-server-blue.vision-computer.local/powershell' -DomainController:'vc-server-red.vision-computer.local' -BasicAuthentication:'False' -WindowsAuthentication:'False' -RequireSSL:'False' -WebSiteName:'Default Web Site' -AppPoolId:'MSExchangePowerShellFrontEndAppPool' -Name:'PowerShell'
[05.31.2013 09:29:54.0452] [2] Searching objects "vc-server-blue.vision-computer.local" of type "Server" under the root "$null".
[05.31.2013 09:29:54.0472] [2] Previous operation run on domain controller 'vc-server-red.vision-computer.local'.
[05.31.2013 09:29:54.0473] [2] Processing object "VC-SERVER-BLUE\PowerShell".
[05.31.2013 09:29:58.0486] [2] [ERROR] Couldn't find the parent object for  on domain controller vc-server-red.vision-computer.local. Check that HTTP exists and that the domain controller belongs to domain vision-computer.local.
[05.31.2013 09:29:58.0487] [2] [ERROR] Das Active Directory-Objekt für das virtuelle Verzeichnis 'IIS://vc-server-blue.vision-computer.local/W3SVC/1/ROOT/PowerShell' auf 'VC-SERVER-BLUE' konnte nicht erstellt werden. Möglicherweise ist es bereits in Active Directory vorhanden. Entfernen Sie das Objekt aus Active Directory, und erstellen Sie es anschließend neu.
[05.31.2013 09:29:58.0488] [2] [ERROR] Couldn't find the parent object for  on domain controller vc-server-red.vision-computer.local. Check that HTTP exists and that the domain controller belongs to domain vision-computer.local.
[05.31.2013 09:30:01.0087] [2] [ERROR] Das Active Directory-Objekt für das virtuelle Verzeichnis 'IIS://vc-server-blue.vision-computer.local/W3SVC/1/ROOT/PowerShell' auf 'VC-SERVER-BLUE' konnte nicht erstellt werden. Möglicherweise ist es bereits in Active Directory vorhanden. Entfernen Sie das Objekt aus Active Directory, und erstellen Sie es anschließend neu.
[05.31.2013 09:30:01.0087] [2] [ERROR] Couldn't find the parent object for  on domain controller vc-server-red.vision-computer.local. Check that HTTP exists and that the domain controller belongs to domain vision-computer.local.
[05.31.2013 09:30:01.0093] [2] Ending processing new-PowerShellVirtualDirectory

As the title suggests,

I have just setup public folders in Exchange 2010. The hierarchy has copied over but no content.

I'm going to use the method of exporting to pst and re-importing to migrate my 2003 public folders so now im in the state where i want to remove / clear down my 2010 hierarchy.

When i delete a public folder from within 2010 public folder management it delete the PF in 2003... I dont want this to happen as i need them on the old server to export.

Hi,

I installed Exchange 2013 CU1 and I began to migrate my Exchange 2010 SP3 mailboxes. After a few successful migration batches using the EAC, I am currently not able to migrate any single mailbox!

I am afraid that the Exchange system is damaged. Is there any suitable cmdlet to test or repair the system? Unfortunately the BPA is yet not available...

Thank you in advance for any good idea!

Greetings, George

The batch report says

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​5/31/2013 12:40:42 PM [EXCH2013ghue] '' created move request.
5/31/2013 1:53:48 PM [EXCH2013ghue] '' suspended move request.
5/31/2013 1:53:51 PM [EXCH2013ghue] Suspending job.
5/31/2013 1:53:51 PM [EXCH2013ghue] Relinquishing job.
5/31/2013 2:15:52 PM [EXCH2013ghue] '' modified move request.
5/31/2013 2:15:52 PM [EXCH2013ghue] '' resumed move request.
5/31/2013 2:15:55 PM [EXCH2013ghue] Job resumed with status 'Queued'.
5/31/2013 2:15:55 PM [EXCH2013ghue] Relinquishing job.
5/31/2013 2:19:04 PM [EXCH2013ghue] '' suspended move request.
5/31/2013 2:19:13 PM [EXCH2013ghue] Suspending job.
5/31/2013 2:19:13 PM [EXCH2013ghue] Relinquishing job.

The Event-Viewer says

Cmdlet fehlgeschlagen. Cmdlet New-MoveRequest, Parameter {WhatIf=False, Identity=dextest.de/OU SmartOutlook/Erika Mustermann, CompletedRequestAgeLimit=7.00:00:00, BatchName=MigrationService:Donald Duck, Erika Muster und dexchange nach Exchange 2013, BadItemLimit=0, TargetDatabase=Mailbox Database 1852746295, ArchiveTargetDatabase=Online Archive 2013}.