Exchange 2013 Migration issues

Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2

I have migrated 1 user so far to Exchange 2013.

ISSUE

Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook 2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

I recently migrated our 2007 Exchange Server to 2013.  This is a single server setup.  Everything seemed to go fairly well.  I've been through many Exchange migrations in the past, but this is the first one that has been 2007 to 2013.  This environment has also been migrated from 2003 to 2007 in the past (not me) and the Exchange 2003 server was never decommissioned properly.  So...  I've removed the 'first administrative group' from ADSI Edit which enabled me to install Exchange 2013 without it thinking there was a legacy 2003 server installed.

Once I got everything setup I moved all mailboxes have been moved to the new 2013 server, set all URLs to the respective domain names, installed the new cert.  Pretty much followed a guide i found online for an Exchange 2007 to 2013 migration.  Everything with 2013 seems to be functioning correctly.  I have mailflow between 2007 and 2013, i have mailflow to external addresses, mailflow in from external.  OWA functions properly, ActiveSync for all of my mobile devices seems to be working just fine.

Here's my one (major) issue:

My Outlook Clients are now asking for credentials upon launch and then about every 10 mins or so thereafter.  At first i was testing with my account and Outlook Client (2013).  Then decided to test with Outlook 2010.  Same issue on both clients. After a lot of searching on this particular issue, I found a possible cause of the issue, but cannot for the life of me seem to fix it...

I've found multiple posts stating that this issue is related to the OAB connection.  This was confirmed by noticing Outlook was trying to download the OAB everytime the authentication box would pop up under the Local Mailbox tab on the Connection Status option using the ctrl+rightclicking the outlook icon in the notification area.

Also, i've noticed if i hit 'cancel' to the authentication request, Outlook functions just fine.  All folders are updated, however the request does come back.  It also shows 'need password' in the bottom right of Outlook.  It also doesn't matter how many times i enter the correct user and password it doesn't take it.  (yes, password is correct and yes, i've entered user name as domain\username, just username and username@domain).

So, I started investigating the OAB issue.

The first thing i did was verify i have an OAB.. I did... There was the default one with 2007 and there was a new one for 2013.  I did try and do a move-offlineaddressbook request during the migration process and it failed stating I couldn't move an old OAB to Exchange 2013 i had to create a new one.  So i removed the (already new) exchange 2013 OAB, and created my own and made it default.  Still no change in behavior.  I verified the internal and external URLs for the virtual directory they are correct (https://mail.domain.com/oab) and the virtual directory is linked to the OAB. 

One thing i did notice that was odd was when i do a get-offlineaddressbook | fl, on my new OAB i notice that there is a property called OriginatingServer and it was pointed to my old 2007 server FQDN, not the new 2013 one.  I found that odd that it wouldn't originate from 2013 especially when I created the OAB from the 2013 server....

My next step was to just kill all services to the 2007 box...  Essentially shutting down the old 2007 exchange server.  Everything was moved so i should be able to use it solely off 2013.  Once i did this, my Outlook 2010 clients seemed to function just fine, no long requiring username and password.  Score!  I then i tried Outlook 2013 thinking the issue would be remedied once i uninstall and decommission 2007....  WRONG.  Outlook 2013 is now broken.. I get the following error when starting Outlook 2013:

Cannot Start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened.  The attempt to login to Microsoft Exchange has failed.

I started all 2007 services up again and Outlook 2013 is still jacked up.  Outlook 2010 is back to asking for credentials.  My worry is this:  SOMETHING is still tied to Exchange 2007.  I'm guessing it's with OAB, but no clue if that's it.

Oh  I also looked for the arbitration mailboxes for OAB, they are on the new server and i have none on the old 2007 server.  I'm at such a loss at this point.  Can anyone help me??

Thanks!

-Jeff

If I am correct non of the Exchange Servers are compatible with Windows Server 2012 R2. I know there will be Update 4 for the Exchange 2013 to support this system. But I was not able to find any information regarding Exchange 2010.

What's about Exchange 2010 and 2012 R2? Again, I only want to know the facts about Exchange 2010 and 2012 R2.

Hello,

Im trying to create a DAG between 2 servers (both mailbox and ca) i managed to create this without any errors displayed at that time however when i use "test-replicationhealth" in my shell it says the following:  There were database availability check failures for database '...  i tried looking in the log file however that didnt help me much.

[2014-01-13T07:44:46] new-dag started
[2014-01-13T07:44:46] commandline:         $scriptCmd = {& $wrappedCmd @PSBoundParameters }

[2014-01-13T07:44:46] Option 'Name' = ''.
[2014-01-13T07:44:46] Option 'WitnessServer' = '233SVR03'.
[2014-01-13T07:44:46] Option 'WitnessDirectory' = ''.
[2014-01-13T07:44:46] Option 'WhatIf' = ''.
[2014-01-13T07:44:53] New-DatabaseAvailabilityGroup passed the initial checks.
[2014-01-13T07:44:53] New-DatabaseAvailabilityGroup completed successfully.
new-databaseavailabiltygroup explicitly called CloseTempLogFile().

could someone tell me how i can find out why the DAG isn't working, or give me a push in the right direction?

Thanks,

Folks,

On a Standalone Server with CU3 Deployed i Receive the Message:

An inconsistency in the Active Directory was detected: Database 'MailboxDatabase01' is expected to be in a database

availability group but the value for its MasterServerOrAvailabilityGroup property ('E2013N1') is not valid. This may

be a defect in the product and this should be reported to Microsoft Product Support.

    + CategoryInfo          : InvalidOperation: (MailboxDatabase01:MailboxDatabase) [New-MailboxDatabase], Inconsisten

   tADException

    + FullyQualifiedErrorId : [Server=E2013N1,RequestId=ac98a62f-10f5-4709-8b73-d13eb1669f04,TimeStamp=10.01.2014 12:5

   6:26] ABC21501,Microsoft.Exchange.Management.SystemConfigurationTasks.NewMailboxDatabase

    + PSComputerName        : e2013n1.brslab.local

When trying toi Create a Database. This Worked with CU2. If Server is Part of a DAG, everything is fine.

I Did a New-Install for 4 Scenarios, the error is Reproducible:
CU3 Error

Hi,

We have just upgraded out test lab to Exchange 2010 SP3 RU3. 

We have 2 CAS-servers and 2 Mailbox-servers. All servers er fully patched.

Question - reason for upgrading is that our Production environment is running Exchange 2010 SP2 RU7, and we have issues with IE 11(light mode only) which is resolved in SP3 RU3. But we have discovered a another issue after upgrading. 

After upgrading Exchange,  IE 11 is fixed at the login screen, and we can now choose which login methode we want to use, so this is good. 

But if you login with IE 11 chosse Options > See all Options > Organize E-mails > Automatic Replies - then the page is blank.

If you choose to use Firefox or Chrome everything is working correctly.. 

Does any else have the same problem?

We are migrating from Exchange 2007 to Exchange 2013. We have a new Exchange 2013 server will all of the roles installed, but none of the mailboxes have even been moved yet. We are seeing some of our users getting prompted to accept the self signed certificate on the exchange 2013 server. Exchange 2007 server is still handling all of the mail flow and connectors. Any reason why some of our users would be prompted with the certificate for the exchange 2013 server even though their mailbox is still on exchange 2007. Our users are on outlook 2010.

Ed

Ed

Since the installation of Exchange CU3 none of our XP users can access Public Folders.  I can't seem to find a fix nor have a heard ifMicrosoft plans to address this with a patch/fix. I understand that there isn't an option to rollback the update.  I have seen people suggest uninstalling exchange completely and then re-installing with Cu2.  Is this possible or does the exchange version have to match what the AD schema version is?  If so, can someone offer some references on how this can be done without losing configuration, data, etc?

Hello,

Currently I'm configurating a 2013 Microsoft Exchange server (multi-tenancy.)

The problem I'm encountering is that my tenant-administrators can view other tenant users.

Is there any way to disable the ability for tenant administrators to view the other tenants?

User1@tenant1.local

Admin1@tenant1.local

User1@tenant2.local

Admin1@tenant2.local

Both admins can view the other E-mail addresses in the ECP. How to disable this ability?

Error:

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

         $feVdirName = "PowerShell (Default Web Site)";

         $beVdirName = "PowerShell (Exchange Back End)";

         $vdirName = "PowerShell";

         $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

         get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

         new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

         new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

       " was run: "The virtual directory 'PowerShell' already exists under 'server01.XXXXX.local/Exchange Back End'.

Parameter name: VirtualDirectoryName".

Thanks

Hi,

I'm a bit confused about where autodiscover is getting it's information from in this environment and from time to time a users Outlook account ends up pointing to the wrong Organisation.

• Domain A and Domain B both have an Exchange organisation.
• User A is a member of Domain A but logging into a computer in Domain B.
• User A has an Exchange Mailbox in both organisations but needs to use the mailbox in Domain B.

I thought that since the computer was a member of Domain B, autodiscover would find the information using SCP... from Domain B? I'm not sure if it's possible to trace where/which method Outlook gets the update from?

Thanks for any help.

I'm running into problems preparing the schema in my AD.   We currently have Exchange 2010 SP3 installed onsite with our Office365 tenant space.   We have been upgraded to V15 in Office365.   I followed the instructions and connected via powershell to our tenant space and generated the MyTenantOrganizationConfig.XML file.   Running the exhange setup with /TenantOrganizationConfig switch comes back with not supported with /PrepareSchema.   Runing setup with just the /TenantOrganizationConfig doesn't work either.   Both URL links below don't work, the first one just takes you to a general Exchange page.

Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.

Performing Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis                                     FAILED
     A hybrid deployment with Office 365 has been detected.  Please ensure that you are running setup with the /TenantOrganizationConfig switch.  To use the TenantOrganizationConfig switch you must first connect to your Exchange Online tenant via PowerShell and execute the following command: "Get-OrganizationConfig | E
xport-Clixml -Path MyTenantOrganizationConfig.XML".  Once the XML file has been generated, run setup with the TenantOrganizationConfig switch as follows "/TenantOrganizationConfig myTenantOrganizationConfig.XML".
If you continue to see this this message then it indicates that either the XML file specified is corrupt, or you are attempting to upgrade your on-premises Exchange installation to a build that isn't compatible with the Exchange version of your Office 365 tenant. Your Office 365 tenant must be upgraded to a compatible
version of Exchange before upgrading your on-premises Exchange installation. For more information, see:http://go.microsoft.com/fwlink/?LinkId=262888
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.DidTenantSettingCreatedAnException.aspx

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

if you have any idea what happens, Please give me some advices.

This is a pst from test email. it has only 4 emails. 

thanks,

Long

All,

Our company is running Exchange 2003 Server and planing to Exchange 2013. We understand that Exchange 2003 cannot migrate to Exchange 2013 directly. Can we install Exchange 2013 in same forest and then migrate mailbox item using third party tool (such as Quest tool). After all mailboxes items migrated, uninstall Exchange 2003 in forest. Is it work solution ?

thanks

Keith

I want to setup, deployment exchange 2010 server with windows 2012 server. So I need step by step guide line with screenshot and video link. Like as mx record, dns entry, real ip domain name etc.

Thanks,

Qamrul

I am running windows server 2003 R2, with exchange 2007 SP2.

I would like to upgrade to Exchange 2013 on Windows server 2012 R2.

I am running a VM, Hyper V environment, so my win 2012 R2 is a VM.

Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.

I currently only have 1 exchange server, with all the roles on the one server.  I would like to keep that same as well with exchange 2013.

My domain controllers are 2 servers running 2012 R2, and one running 2012.  In about 3 weeks, I'm upgrading the 2012 to 2012 R2, so all three will be at the same level.

Is there a technet aricle explaining how to perform this?

Dan

I did a test as command "new-moverequest" for migrate mailbox cross forest and it worked. After the move completed, the source mailbox was removed. Anyway to keep the mailbox on source server until server decommission ?

thanks

Keith

Hi

I get this error when trying to install Exchange 2013 on a Server 2012 build on Hyper-V (running on Windows 8.1).  All prerequisites are installed and I have tried re-downloading the .iso from TechNet.

It's also impossible to scroll down the error message to see the rest of it.

dear friends,

its been few days completed migration and few doubts which are in my mind wanted to share with you if some one can please guide on the same.

1. During the migration i added 2013 and started moving mailboxes. The observation was that till the time the mail box was on 2010 all is good and once mailbox gets transferred it stops. as i havent had any connector configured on 2013. The article i followed guided to configure the connector once all mailbox moves.. not sure if this is correct as this will be a good time and dont knw when all will finish so we can have downtime.  - What is the recommended way.

2. Can this be fully transparent to user.

3. It took almost 2days 2 night to transfer - 100Gb data... is it normal ... Is there any other fast and reliable way

4. i didnt migrated the SSL from source instead i applied a new SSL reason being my source SSL was about to expire. But then all the users started getting the SSL proxy error... - Not sure why, i was expecting this to work without issues

5. Password prompt : Not sure why my half of the users started getting password prompt continuous from outlook,.

6. Any suggestions for anti-Spam as forefront is no more there and i am getting loads spam, i knw about third party .. - SUGGESTIONS

These were my observations .. and i hope i am able to put all... please share your views on above.

Upgraded to CU3 last night.  5 out of 6 were successful.

Error:

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

                  $RoleDomainController = $RoleDomainController                 

                  $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "The virtual directory 'PowerShell' already exists under '$RoleFqdnOrName/Exchange Back End'.

Parameter name: VirtualDirectoryName".

I successfully manually ran the cmdlet to remove the Powershell Virtual Directory and got a bit further:

get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController

Then came this error:

Error:

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

        Get-PushNotificationsVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | Remove-PushNotificationsVirtualDirectory -DomainController $RoleDomainController;

        New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;

      " was run: "The virtual directory 'PushNotifications' already exists under $RoleFqdnOrName/Exchange Back End'.

Parameter name: VirtualDirectoryName".

I manually deleted the PushNotifications virtual directory and got a little further.  Next came this error and I'm stuck:

Error:

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

          Update-OwaVirtualDirectory -DomainController $RoleDomainController;

          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";

          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;

          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeOWAAppPool" -Version:"v4.0";

          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeOWACalendarAppPool" -Version:"v4.0";

        " was run: "An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.

. HResult = -2147024893".

I've verified the path and file exist for $RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" and the MSExchangeOWAAppPool, MSExchangeOWACalendarAppPool pools exist.

At this point I can't get the CU3 to complete and I don't know how to uninstall Exchange and start over.  I've tried .\setup.exe /m:uninstall /IAcceptExchangeServerLicenseTerms and it just resumes the failed install.

I'm tempted to blow the server away and manually remove the server with ADSIEdit, but I'd like to find the fix if possible.

Ambers