I have Exchange 2010 SP3 (two CAS, two mailbox servers) coexisting with Exchange 2013 CU2 (two CAS, two mailbox servers). I have not yet committed DNS changes to point clients to the new Exchange 2013 CAS servers.  I want to verify my clients will be able to connect to their mailboxes before finalizing the cut over.  I have migrated ONE user account.  Mail flow works fine between Exchange 2010 users and the Exchange 2013 user. OWA works fine for the migrated user. However, I can't seem to connect Outlook 2010 (fully patched) or Outlook 2013 (with patches) directly to the migrated mailbox by BYPASSING the CAS.  Since DNS has not been adjusted, autodiscover is still pointing to Exchange 2010.  

The workstation is a domain member, the migrated user is not hidden in the address book.  Internal Outlook authentication is set for NTLM, but I'm not sure that even matters if I'm bypassing the CAS.  

I am configuring the connection manually.  I enter the server name of the mailbox server hosting the migrated mailbox and the full name of the user.   Errors reported by Outlook include:

"Outlook cannot log on.  Verify you are connected tot he network and are using the proper server and mailbox name.  The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

and

"The name cannot be resolved.  The action cannot be completed."

I have seen countless posts related to these messages, but most are related to Outlook Anywhere configuration problems; problems I believe are fixed by modifying CAS server configurations.  

I don't know what logs I should be looking at on the mailbox server I'm attempting to attach to.

I am in the process of a cross-forest exchange migration and need some advice about internal and external URLs.

My source server is Exchange 2007 sp1 rollup 10 in a Windows Server 2008 SP2 server which is the primary domain controller with FSMO roles for the source domain; sourcedomain.org. The external and internal URLs are set to mail.sourcedomain.org and the email addresses are user@sourcedomain.org.

My target server is Exchange 2013 in a Windows Server 2012 joined to targetdomain.net

I would like to keep the internal and external URLs as mail.sourcedomain.org because a lot of our users use the Outlook Web App and also to be consistent with the email addresses which will still be the same; user@sourcedomain.org

I tested that configuration and it worked fine but I had to edit the hosts file on the test computer to point mail.sourcedomain.org to the ip address of mail.targetdomain.net.

I would like to create a dns record to do this for me. I tried creating a cname under the targetdomain.net dns zone but the end result is mail.sourcedomain.org.targetdomain.net

Any advice on how to do this?

I have been trying to install Exchange 2013 for a while now and have continued to run into the same error during the readiness check.  The readiness check stalls at 40% completed and I receive the following error:

Error:

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

if (Get-Service MSDTC*|?{$_.Name -eq 'MSDTC'})

{

Set-Service MSDTC -StartupType Automatic

Start-SetupService -ServiceName MSDTC

}

"was run:"The task failed because a Win32 error occurred: "Access is denied". Could not open the service "MSDTC".".

I have tried to install this both onto Windows Server 2008 R2 as well as Windows Server 2012.  I have installed all of the prerequisites as noted in the Microsoft documentation.  I have tried to install this as the first Exchange server in a brand new AD environment as well as trying to install it into an AD environment where I had already installed Exchange Server 2010 with SP3.  I always receive the same error message during the readiness check when it stalls at 40%.

Any help here would be very much appreciated.

Thank you.

Hi!

We need to migrate from Exchange 2003 Installed on Win 2003 to Exchange 2010 which will be installed on windows 2012 Data Center Edition. The Domain Controllers are windows 2008 R2. There is no windows 2003 DC.

Will it be fine to install Exchange 2010 on Windows 2012 Data Center? Secondly, after checking our current Exchange 2003 and Active Directory with DCDIAG andRepadmin, we did not find any problem. What else we can check in our environment for smooth Exchange Migration and what problems we can face during or after migration?

Thanks.

Hi all. 

I'm a bit lost, it's my first exchange 2013 install and my first coexistence scenario. So I need help. 

I've got an existing Exchange 2007 SP3 CU 12 organization, with 3 servers : 

- Server38 and Server39 as Mailbox Server, CCR Cluster, virtual node isServer40

- Server41 as CAS Server. 

I want to migrate everything to Exchagne 2013 SP1 on Windows 2012 R2. I have 2 servers : 

- Server12 and Server13 are Multirole servers, CAS ans MBX. I have configured a DAG. It's working. 

To provide HA on CAS service, I put this in order : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/

Clearly, I want my CAS Server to be accessed with mail.domain.com instead of Server12.domain.com or Server13.domain.com

So I configure Outlook Anywhere like this : "Set-OutlookAnywhere -InternalHostname mail.domain.com -InternalClientsRequireSsl $false"

Now, I don't really imagine how I can use this platform during coexistence. 

I want to set users on my new servers, but autodiscover is configured in DNS to point Server41. 

Users can access to their mails via OWA and Outlook. 

How can I configure autodiscover? Must I change autodiscover record in DNS to point to new servers or should I let it on Server41? 
How will Outlook work when I migrate one user to the new servers? Will I have to change config? 

Thanks

Greetings All,

Assume I have 1000 User with mailboxes stored on SAN Storage, say concurrency is 100%, which means 1000 users are accessing their mailboxes through MBX Server concurrently. Does this imply there will be 1000 connections to SAN Storage?

Thanks 

Hello,

I would like your advice in my migration scenario.

Source:

• Exchange Server 2007 SP1 installed on Windows Server 2008 SP2 primary domain controller with FSMO roles.
• Domain name is abc.org
• We have about 150 mailboxes.

Target:

• Exchange Server 2013 on Windows Server 2012
• Domain name is abc123.net on a new forest
• We will keep receiving emails on abc.org but the domain where the server, computers and everything else is on abc123.net

The way I am thinking about doing this migration is by exporting all the mailboxes with powershell to a folder and then using powershell again to import them to the new server. I did a test with one mailbox and it worked fine. I had to create an empty mailbox first.

Do you have any thoughts on this? Do you see anything I should pay attention to?

Thanks a lot!

I a bit of at newbie at this so please forgive what is a wordy and possibly a dumb question...

We are planning a cross-forest migration of Exchange from SBS 2003 to Server 2012 R2 Standard with Exchange 2013 using the CodeTwo migration tool.  Our SBS2003 domain is ourcompany.local and the new Server2012 domain will be called ourco.local.  We have a website at www. ourcomapny .co.uk.  Our external email comes to mail.ourcompany.co.uk and we wish to continue with this.  We wish to end up with a single server in our organisation - I know this is not recommended but the anticipated stress on the server will be minimal.

My plan is to set up a new fresh install Server 2012 as a domain controller in the new ourco.local domain, then install Exchange 2013, then set up a trust between ourcompany.local and ourco.local ready for the migration.

I have been following the Exchange Server Deployment Assistant and have got the to the "Collect required information" page.  The examples on this page seem to assume the internal domain name will be the same as the external web site name so I cannot be sure what values will be correct in our organisation.  My guess is the following but I would be pleased if someone would take a look and confirm if I am on the right track:

AD forest root:  ourco.local
External Exchange 2013 FQDN:  mail.ourcompany.co.uk
Internal Exchange 2013 FQDN:  mail.ourcompany.co.uk
External Exchange 2013 FDQN for Outlook Web App: owa.ourcompany.co.uk
Internal Exchange 2013 FDQN for Outlook Web App: owa.ourcompany.co.uk
Autodiscover FDQN:  autodiscover.ourcompany.co.uk
Primary SMTP namespace:  ourcompany.co.uk
User principle name domain:  ourco.local

Any corrections and/or friendly advice would be most welcome.

Cheers
Nico

So I've decided to start testing SSL offloading with Exchange 2013 SP1 now that it is supported. I have followed this guide: http://technet.microsoft.com/library/dn635115(EXCHG.150).aspx. It is fairly straightforward, remove the "Require SSL" option on the VDIRS and IISRESET.

To test, I load up http://CAS/OWA and it immediately redirects to HTTPS://CAS/OWA. I do not see why it is doing this or how to configure it otherwise. So while my server is accepting connections on port 80, it's just bouncing them over to 443. How do we disable this?

I checked the HTTP Redirect option on the VDIRs, which is not present. Also, I am going straight to the server, so there is not a device in front that is redirecting my requests. Any thoughts?

Thanks,

Brandon

Hi, I am getting the following error during the Exchange 2010 SP2 readiness checks. The server is a member of the domain, is pointing to the correct DNS servers, and is a member of a valid site in AD.

Error: Setup encountered a problem while validating the state of Active Directory: Could not find Active Directory site to which the server belongs.

Error: This computer does not belong to a valid Active Directory site. Check the site and subnet definitions.

Hi,

We are currently setting up a new domain for a company. The new server is running Server 2012 and Exchange 2013.

The old server on the original domain is running SBS 2008 and Exchange 2007 - how do we go about migrating mailboxes across from one to the other? The domains are differently named, as are the two servers.

Many Thanks,

We just brought online a new Exchange 2013 server in coexistence with Exchange 2007. We have been trying to send emails within OWA all day without any luck. All the messages keep going into Drafts. The email address being used was created on Exchange 2013 and is being sent to an email address in Exchange 2013. I have done all of the DNS changes within Exchange Admin Center as well as in the hosts file. I have also done what was suggested in this forum:

http://social.technet.microsoft.com/Forums/en-US/1813eec7-dc2b-40af-a3b0-1fd552f745e2/all-sent-emails-stuck-in-either-outbox-for-outlook-or-drafts-for-owa-on-new-exchange-2013?forum=exchangesvrclients 

We have had not luck with this. Any other possibilities I could be missing?

Thank you,

Ryan

So we have

2010 Exchange  User@abc.com

2013 Exchange User@abc.com

We are migrating mailboxes from 2010 to 2013 and its all working. However there is one problem we are encountering: Exchange 2013 is not or can not forward emails to 2010 Exchange because it does not see it..

(Also to note these users are on different forests AD abc.com and AD abc1.com)

So what would be best way to forward emails to 2010 exchange users that have not been migrated yet?

Greetings.

I've been working on moving mailboxes from an old exchange 2007 server to Exchange 2013. Both Exchange servers are in the same AD. During the move, the target Exchange server ran out of disk space (Don't ask...), and ended up apparently losing track of its message store. Mail databases are still fine, but I can no longer access the migration tool or use migration cmdlets, as the information store is missing.

The following error is logged when I try to run Get-MigrationBatch:

I'm trying to configuring my Exchange Server 2010 sp1 on Windows Server 2008 R2 to receive emails from the internet. i configured exchange and its working fine on this link https://fmggv.com/owa(fmggv.com is my local domain). I have a hosted domain name and website fmg.edu.in. My quetion is how to point local domain to external domain so that i can use mail.fmg.edu.in from outside the world to access Outlook web app. I have a public ip and using port forwarding to my local ip.

Please advise me asap.

We would like to be able to offer our clients access to their on premises only mailbox via Office 365 through a Hybrid deployment on client devices such as apple and android and we were wondering if this was possible please?

Version of Exchange is 2013

Thanks

Alan.

Alan Hughes

Hi!

We are going for Exchange 2003 to 2010 transition. What can we do to revert to Exchange 2003 if the transition process fails?

Thanks.

We have deployed Exchange 2013 RTM with no issues, upgraded from Exchange 2007 SP3 and Exchange 2010 SP3.

I am currently attempting to install Exchange 2013 SP1 but getting a very vague error - Object reference not set to an instance of an object. From researching, most users are getting this error from /PREPAREAD, but I had no problem there.

Here is a copy of ExchangeSetup:

[04/03/2014 08:37:54.0767] [0] **********************************************
[04/03/2014 08:37:54.0798] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[04/03/2014 08:37:54.0798] [0] **********************************************
[04/03/2014 08:37:54.0798] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[04/03/2014 08:37:54.0798] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[04/03/2014 08:37:54.0814] [0] Setup version: 15.0.847.32.
[04/03/2014 08:37:54.0814] [0] Logged on user: ****.
[04/03/2014 08:37:55.0002] [0] Command Line Parameter Name='sourcedir', Value='C:\Users\**\Downloads\E2013SP1'.
[04/03/2014 08:37:55.0002] [0] Command Line Parameter Name='mode', Value='Upgrade'.
[04/03/2014 08:37:55.0017] [0] RuntimeAssembly was started with the following command: '/sourcedir:C:\Users\**\Downloads\E2013SP1 /mode:Upgrade'.
[04/03/2014 08:37:55.0752] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[04/03/2014 08:37:56.0220] [0] Finished loading screen CheckForUpdatesPage.
[04/03/2014 08:38:00.0486] [0] Finished loading screen UpdatesDownloadsPage.
[04/03/2014 08:38:02.0642] [0] Starting file's copying...
[04/03/2014 08:38:02.0658] [0] Setup copy files from 'C:\Users\**\Downloads\E2013SP1\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
[04/03/2014 08:38:02.0736] [0] Disk space required: 1826493368 bytes.
[04/03/2014 08:38:02.0736] [0] Disk space available: 19240181760 bytes.
[04/03/2014 08:38:02.0845] [0] Finished loading screen CopyFilesPage.
[04/03/2014 08:38:22.0892] [0] File's copying finished.
[04/03/2014 08:38:23.0095] [0] Finished loading screen InitializingSetupPage.
[04/03/2014 08:38:32.0752] [0] Setup is choosing the domain controller to use
[04/03/2014 08:38:33.0627] [0] The MSExchangeADTopology has a persisted domain controller: **DC4.AIT.LOCAL
[04/03/2014 08:38:38.0877] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use *DC4.AIT.LOCAL
[04/03/2014 08:38:38.0877] [0] Setup is choosing a global catalog...
[04/03/2014 08:38:39.0002] [0] Setup has chosen the global catalog server **DC4.AIT.LOCAL.
[04/03/2014 08:38:39.0049] [0] Setup will use the domain controller '**DC4.AIT.LOCAL'.
[04/03/2014 08:38:39.0049] [0] Setup will use the global catalog '**DC4.AIT.LOCAL'.
[04/03/2014 08:38:39.0049] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=AIT,DC=LOCAL'.
[04/03/2014 08:38:39.0064] [0] Exchange organization container for the organization is 'CN=**,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=AIT,DC=LOCAL'.
[04/03/2014 08:38:39.0142] [0] Setup will search for an Exchange Server object for the local machine with name 'AITTWMAIL'.
[04/03/2014 08:38:39.0580] [0] Exchange Server object found : 'CN=AITTWMAIL,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=**,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=AIT,DC=LOCAL'.
[04/03/2014 08:38:39.0611] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[04/03/2014 08:38:39.0627] [0] The following datacenter roles are unpacked:
[04/03/2014 08:38:39.0627] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[04/03/2014 08:38:39.0627] [0] The local server has some Exchange files installed.
[04/03/2014 08:38:39.0674] [0] Server Name=AITTWMAIL
[04/03/2014 08:38:39.0799] [0] Setup will use the path 'C:\Users\**\Downloads\E2013SP1' for installing Exchange.
[04/03/2014 08:38:39.0814] [0] Setup will discover the installed roles from server object 'CN=AITTWMAIL,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=**,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=AIT,DC=LOCAL'.
[04/03/2014 08:38:39.0814] [0] 'BridgeheadRole' is installed on the server object.
[04/03/2014 08:38:39.0814] [0] 'ClientAccessRole' is installed on the server object.
[04/03/2014 08:38:39.0814] [0] 'MailboxRole' is installed on the server object.
[04/03/2014 08:38:39.0814] [0] 'UnifiedMessagingRole' is installed on the server object.
[04/03/2014 08:38:39.0814] [0] 'CafeRole' is installed on the server object.
[04/03/2014 08:38:39.0814] [0] 'FrontendTransportRole' is installed on the server object.
[04/03/2014 08:38:39.0924] [0] The installation mode is set to: 'BuildToBuildUpgrade'.
[04/03/2014 08:38:41.0767] [0] An Exchange organization with name '**' was found in this forest.
[04/03/2014 08:38:41.0767] [0] Active Directory Initialization status : 'True'.
[04/03/2014 08:38:41.0767] [0] Schema Update Required Status : 'False'.
[04/03/2014 08:38:41.0767] [0] Organization Configuration Update Required Status : 'False'.
[04/03/2014 08:38:41.0767] [0] Domain Configuration Update Required Status : 'False'.
[04/03/2014 08:38:41.0767] [0] The locally installed version is 15.0.516.32.
[04/03/2014 08:38:41.0767] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[04/03/2014 08:38:41.0892] [0] Setup is determining what organization-level operations to perform.
[04/03/2014 08:38:41.0892] [0] Because the value was specified, setup is setting the argument OrganizationName to the value AcumenIT.
[04/03/2014 08:38:41.0970] [0] RootDataHandler has 1 DataHandlers
[04/03/2014 08:38:42.0002] [0] Validating options for the 7 requested roles
[04/03/2014 08:38:42.0002] [0] UpgradeModeDataHandler has 17 handlers and 17 work units
[04/03/2014 08:38:42.0345] [0] CurrentResult launcherbase.maincore:90: 0
[04/03/2014 08:38:42.0564] [0] Finished loading screen WelcomePage.
[04/03/2014 08:38:50.0002] [0] Finished loading screen EULAPage.
[04/03/2014 08:38:52.0314] [0] **************
[04/03/2014 08:38:52.0314] [0] Setup will run the task 'Start-PreConfiguration'
[04/03/2014 08:38:52.0345] [1] Setup launched task 'Start-PreConfiguration -Mode 'BuildToBuildUpgrade' -Roles 'LanguagePacks','BridgeheadRole','FrontendTransportRole','ClientAccessRole','UnifiedMessagingRole','MailboxRole','AdminToolsRole','CafeRole'' 
[04/03/2014 08:38:52.0392] [1] Finished loading screen PreCheckPage.
[04/03/2014 08:38:54.0908] [1] [ERROR] Object reference not set to an instance of an object.
[04/03/2014 08:38:54.0908] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.

Can anyone point me in the right direction? I have also noticed other articles about deleting Exchange groups, but the articles do not appear to apply and I really don't want to go around removing groups that explicitly state "Do Not Remove".

Thanks in advance!

Working to live ...

Hi People,

The ladies at the reception are having issues with Outlook 2010 meeting room calendars, they are out of syncing. Sometimes appointment are visible for the other, some times they are not showing up or they do when adding a new appointment. For example: If we look at one day with 5 room calendars near each other all looks the same except 1 meeting is not shown.

Can someone advice where to check sync settings or something like that? 

I created the room mailboxes the regular way with default room settings, just granted them access so they can read/write.

Running a Windows Server 2008 R2 SP1 x64 with exchange 2010 v. 14.2.247.5

Thanks in advance.

MAPI and Mailflow tests fail after applying SP1 for Exchange 2013 Standard

Originally installed Exchange 2013 Standard RTM, applied SU3 immediately.  After a few months, upgraded to SP1.  Found App log issues with Health mailboxes. 

 Found that there was no “Monitoring Mailboxes” OU.  From my understanding, this OU was not part of the original RTM release; however, it does exist in the SP1 version.  I re-ransetup /prepareAD from the SP1 installation which created the container and allowed the health mailboxes to be created. 

All Database copies appeared Healthy in the EAC, showing 0 bad copy count for all, mounted for all

Databases

But MAPI connectivity now fails from C1 to all databases.  Health check prior to SP1 had no MAPI Test failures or MailFlow test failures.  Now  I have failures of both for all servers.

server errors and warnings were detected.

• KC-P-EX1 - MAPI tests failed.
• KC-P-EX1 - Mail flow test failed.
• KC-P-EX2 - MAPI tests failed.
• KC-P-EX2 - Mail flow test failed.
• KP-P-EX1 - MAPI tests failed.
• KP-P-EX1 - Mail flow test failed.
• KP-P-EX2 - MAPI tests failed.
• KP-P-EX2 - Mail flow test failed.

Mail flow test: WARNING: Couldn’t perform the operation because a system mailbox isn’t available .  Same MAPI failure on all four servers

Application Log Errors:

1.

Log Name:      Application

Source:        MSExchange Mailbox Replication

Date:          3/28/2014 10:17:04 AM

Event ID:      1006

Task Category: Service

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      KP-P-EX1.kadmon.llc

Description:

The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.

Database: KPExecs

Error: Couldn't find system mailbox 'eaec6631-0d6f-47fa-a296-fecb28a23cf8' in Active Directory.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Mailbox Replication" />

    <EventID Qualifiers="32772">1006</EventID>

    <Level>3</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-28T14:17:04.000000000Z" />

    <EventRecordID>680598</EventRecordID>

    <Channel>Application</Channel>

    <Computer>KP-P-EX1.kadmon.llc</Computer>

    <Security />

  </System>

  <EventData>

    <Data>KPExecs</Data>

    <Data>Couldn't find system mailbox 'eaec6631-0d6f-47fa-a296-fecb28a23cf8' in Active Directory.</Data>

  </EventData>

</Event>

2.

Log Name:      Application

Source:        MSExchange Management Application

Date:          3/28/2014 10:16:07 AM

Event ID:      9001

Task Category: Migration

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      KP-P-EX1.kadmon.llc

Description:

Couldn't connect to the migration service at KP-P-EX1.kadmon.llc.  Error: "The RPC call failed with result 'MigrationPermanentError'."

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Management Application" />

    <EventID Qualifiers="49152">9001</EventID>

    <Level>2</Level>

    <Task>9</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-28T14:16:07.000000000Z" />

    <EventRecordID>680593</EventRecordID>

    <Channel>Application</Channel>

    <Computer>KP-P-EX1.kadmon.llc</Computer>

    <Security />

  </System>

  <EventData>

    <Data>KP-P-EX1.kadmon.llc</Data>

    <Data>The RPC call failed with result 'MigrationPermanentError'.</Data>

  </EventData>

</Event>

I didn’t have these issues prior to SP1 so I have to assume that running setup /prepareAD from the SP1 install after application of SP1 caused a change to the migration mailbox

Found this solution:

To resolve this issue, follow these steps:

Start the Active Directory Users and Computers snap-in.

Click Users, and then verify that the following account does not exist:

Migration.8f3e7716-2011-43e4-96b1-aba62d229136

Note If this account exists in the Users container, go to step 4.

Run the following cmdlet:

setup /preparead/IAcceptExchangeServerLicenseTerms

Run the following cmdlets:

Enable-Mailbox -Arbitration -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136"

Set-Mailbox "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration –Management:$true

However, when I try to apply the fix, I get an error:

This task does not support recipients of this type. The specified recipient

kadmon.llc/Users/Migration.8f3e7716-2011-43e4-96b1-aba62d229136 is of type UserMailbox. Please make sure that this

recipient matches the required recipient type for this task.

    + CategoryInfo          : InvalidArgument: (kadmon.llc/User...b1-aba62d229136:RecipientIdParameter) [Enable-Mailbo

   x], RecipientTaskException

    + FullyQualifiedErrorId : [Server=KC-P-EX1,RequestId=48e4936f-27c4-43e5-91bd-d091587208d2,TimeStamp=3/28/2014 3:18

   :06 AM] [FailureCategory=Cmdlet-RecipientTaskException] A0A49849,Microsoft.Exchange.Management.RecipientTasks.Enab

  leMailbox