So I am trying to do a clean initial install on premise of exchange 2013 on a 2012 r2 server a dedicated email server, AND I NEED HELP. I have got through most of the red tape, but I have this last final hang up error:

Error:
The following error was generated when "$error.Clear();
 initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:14ee3863-b810-409e-b38a-dede591b1c1e,CN=Deleted Objects,DC=hq,DC=reefpt,DC=com on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=reefpt,DC=com points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.".

PLEASE ADVISE THE FULL STEPS I NEED TO TAKE TO GET THIS DAMN INSTALL COMPLETE I've been at this for 5 days now on google, TechNet, and otherwise this is my first time posting online for help ever not sure what to expect. All the sites I go to about expanding AD or running commands never work when I go to try them like setup.exe /prepare        or

1. Extend the Active Directory schema

The first step in getting your organization ready for Exchange 2016 is to extend the Active Directory schema. Exchange stores a lot of information in Active Directory but before it can do that, it needs to add and update classes, attributes, and other items. If you're curious about what's changed when your schema is extended, check out  Exchange 2016 Active Directory schema changes.

Before you extend your schema, there are a few things to keep in mind:

•The account you're logged in as needs to be a member of the Schema Admins and Enterprise Admins security groups.

•The computer where you'll run the command to extend the schema needs to be in the same Active Directory domain and site as the schema master.

•If you use the DomainController parameter, make sure to use the name of the domain controller that's the schema master.

•The only way to extend the schema for Exchange is to use the steps in this topic or use Exchange 2016 Setup. Other ways of extending the schema aren't supported.

tipTip:

If you don't have a separate team that manages your Active Directory schema, you can skip this step and go directly to Step 2. Prepare Active Directory . If the schema isn't extended in step 1, the commands in step 2 will extend the schema for you. If you decide to skip step 1, the information you need to keep in mind above still applies. 

When you're ready, do the following to extend your Active Directory schema. If you have multiple Active Directory forests, make sure you're logged into the right one.

1.Make sure the computer is ready to run Exchange 2016 Setup. To see what you need to run Setup, check out the  Active Directory preparationsection in .

2.Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.

3.Run the following command to extend the schema

CopySetup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms  <--------doesn't work 

After Setup finishes extending the schema, you'll need to wait while Active Directory replicates the changes to all of your domain controllers. If you want to check on how replication is going, you can use the repadmin tool. Repadmin is included as part of the Active Directory Domain Services Tools feature in Windows Server 2012 R2 and Windows Server 2012. For more information about how to use it, see Repadmin.

2. Prepare Active Directory

Now that the Active Directory schema  has been extended, you can prepare other parts of Active Directory for Exchange 2016. During this step, Exchange will create containers, objects, and other items in Active Directory that it'll use to store information. The collection of all of the Exchange containers, objects, attributes, and so on, is called the Exchange organization.

Before you prepare Active Directory for Exchange, there are a few things to keep in mind:

•The account you're logged in as needs to be a member of the Enterprise Admins security group. If you skipped step 1 because you want the PrepareAD command to extend the schema, the account you use also needs to be a member of the Schema Admins security group.

•The computer where you'll run the command needs to be in the same Active Directory domain and site as the schema master. It'll also need to contact all of the domains in the forest on TCP port 389.

•Wait until Active Directory has replicated the changes made in step 1 to all of your domain controllers before you do this step.

When you run the command below to prepare Active Directory for Exchange, you'll need to name the Exchange organization. This name is used internally by Exchange and isn't normally seen by users. The name of the company where Exchange is being installed is often used for the organization name. The name you use won't affect the functionality of Exchange or determine what you can use for email addresses. You can name it anything you want, as long as you keep the following in mind:

•You can use any uppercase or lowercase letters from A to Z.

•You can use numbers 0 to 9.

•The name can contain spaces as long as they're not at the beginning or end of the name.

•You can use a hyphen or dash in the name.

•The name can be up to 64 characters but can't be blank.

•The name can't be changed after it's set.

When you're ready, do the following to prepare Active Directory for Exchange. If the organization name you want to use has spaces, enclose the name in quotation marks (").

1.Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.

2.Run the following command:

Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms    <----- doesn't work     

After Setup finishes preparing Active Directory for Exchange, you'll need to wait while Active Directory replicates the changes to all of your domain controllers. If you want to check on how replication is going, you can use the repadmin tool. repadmin is included as part of the Active Directory Domain Services Tools feature in Windows Server 2012 R2 and Windows Server 2012. For more information about how to use the tool, see Repadmin.

3. Prepare Active Directory domains

The final step to get Active Directory ready for Exchange is to prepare each of the Active Directory domains where Exchange will be installed or where mail-enabled users will be located. This step creates additional containers and security groups, and sets permissions so that Exchange can access them.

If you have multiple domains in your Active Directory forest, you have a couple of choices in how you prepare them. Select the option that matches what you want to do. If you only have one domain, you can skip this step because the PrepareAD command in step 2 already prepared the domain for you.

PLEASE HELP ANYBODY!!!

So I am trying to do a clean initial install on premise of exchange 2013 on a 2012 r2 server a dedicated email server, AND I NEED HELP. I have got through most of the red tape, but I have this last final hang up error:

Error:
The following error was generated when "$error.Clear();
 initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:14ee3863-b810-409e-b38a-dede591b1c1e,CN=Deleted Objects,DC=hq,DC=reefpt,DC=com on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=reefpt,DC=com points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.".

PLEASE ADVISE THE FULL STEPS I NEED TO TAKE TO GET THIS DAMN INSTALL COMPLETE I've been at this for 5 days now on google, TechNet, and otherwise this is my first time posting online for help ever not sure what to expect. All the sites I go to about expanding AD or running commands never work when I go to try them like setup.exe /prepare        or

1. Extend the Active Directory schema

The first step in getting your organization ready for Exchange 2016 is to extend the Active Directory schema. Exchange stores a lot of information in Active Directory but before it can do that, it needs to add and update classes, attributes, and other items. If you're curious about what's changed when your schema is extended, check out  Exchange 2016 Active Directory schema changes.

Before you extend your schema, there are a few things to keep in mind:

•The account you're logged in as needs to be a member of the Schema Admins and Enterprise Admins security groups.

•The computer where you'll run the command to extend the schema needs to be in the same Active Directory domain and site as the schema master.

•If you use the DomainController parameter, make sure to use the name of the domain controller that's the schema master.

•The only way to extend the schema for Exchange is to use the steps in this topic or use Exchange 2016 Setup. Other ways of extending the schema aren't supported.

tipTip:

If you don't have a separate team that manages your Active Directory schema, you can skip this step and go directly to Step 2. Prepare Active Directory . If the schema isn't extended in step 1, the commands in step 2 will extend the schema for you. If you decide to skip step 1, the information you need to keep in mind above still applies. 

When you're ready, do the following to extend your Active Directory schema. If you have multiple Active Directory forests, make sure you're logged into the right one.

1.Make sure the computer is ready to run Exchange 2016 Setup. To see what you need to run Setup, check out the  Active Directory preparationsection in .

2.Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.

3.Run the following command to extend the schema

CopySetup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms  <--------doesn't work 

After Setup finishes extending the schema, you'll need to wait while Active Directory replicates the changes to all of your domain controllers. If you want to check on how replication is going, you can use the repadmin tool. Repadmin is included as part of the Active Directory Domain Services Tools feature in Windows Server 2012 R2 and Windows Server 2012. For more information about how to use it, see Repadmin.

2. Prepare Active Directory

Now that the Active Directory schema  has been extended, you can prepare other parts of Active Directory for Exchange 2016. During this step, Exchange will create containers, objects, and other items in Active Directory that it'll use to store information. The collection of all of the Exchange containers, objects, attributes, and so on, is called the Exchange organization.

Before you prepare Active Directory for Exchange, there are a few things to keep in mind:

•The account you're logged in as needs to be a member of the Enterprise Admins security group. If you skipped step 1 because you want the PrepareAD command to extend the schema, the account you use also needs to be a member of the Schema Admins security group.

•The computer where you'll run the command needs to be in the same Active Directory domain and site as the schema master. It'll also need to contact all of the domains in the forest on TCP port 389.

•Wait until Active Directory has replicated the changes made in step 1 to all of your domain controllers before you do this step.

When you run the command below to prepare Active Directory for Exchange, you'll need to name the Exchange organization. This name is used internally by Exchange and isn't normally seen by users. The name of the company where Exchange is being installed is often used for the organization name. The name you use won't affect the functionality of Exchange or determine what you can use for email addresses. You can name it anything you want, as long as you keep the following in mind:

•You can use any uppercase or lowercase letters from A to Z.

•You can use numbers 0 to 9.

•The name can contain spaces as long as they're not at the beginning or end of the name.

•You can use a hyphen or dash in the name.

•The name can be up to 64 characters but can't be blank.

•The name can't be changed after it's set.

When you're ready, do the following to prepare Active Directory for Exchange. If the organization name you want to use has spaces, enclose the name in quotation marks (").

1.Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.

2.Run the following command:

Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms    <----- doesn't work     

After Setup finishes preparing Active Directory for Exchange, you'll need to wait while Active Directory replicates the changes to all of your domain controllers. If you want to check on how replication is going, you can use the repadmin tool. repadmin is included as part of the Active Directory Domain Services Tools feature in Windows Server 2012 R2 and Windows Server 2012. For more information about how to use the tool, see Repadmin.

3. Prepare Active Directory domains

The final step to get Active Directory ready for Exchange is to prepare each of the Active Directory domains where Exchange will be installed or where mail-enabled users will be located. This step creates additional containers and security groups, and sets permissions so that Exchange can access them.

If you have multiple domains in your Active Directory forest, you have a couple of choices in how you prepare them. Select the option that matches what you want to do. If you only have one domain, you can skip this step because the PrepareAD command in step 2 already prepared the domain for you.

PLEASE HELP ANYBODY!!!

So I am trying to do a clean initial install on premise of exchange 2013 on a 2012 r2 server a dedicated email server, AND I NEED HELP. I have got through most of the red tape, but I have this last final hang up error:

Error:
The following error was generated when "$error.Clear();
 initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:14ee3863-b810-409e-b38a-dede591b1c1e,CN=Deleted Objects,DC=hq,DC=reefpt,DC=com on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=reefpt,DC=com points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.".

PLEASE ADVISE THE FULL STEPS I NEED TO TAKE TO GET THIS DAMN INSTALL COMPLETE I've been at this for 5 days now on google, TechNet, and otherwise this is my first time posting online for help ever not sure what to expect. All the sites I go to about expanding AD or running commands never work when I go to try them like setup.exe /prepare        or

1. Extend the Active Directory schema

The first step in getting your organization ready for Exchange 2016 is to extend the Active Directory schema. Exchange stores a lot of information in Active Directory but before it can do that, it needs to add and update classes, attributes, and other items. If you're curious about what's changed when your schema is extended, check out  Exchange 2016 Active Directory schema changes.

Before you extend your schema, there are a few things to keep in mind:

•The account you're logged in as needs to be a member of the Schema Admins and Enterprise Admins security groups.

•The computer where you'll run the command to extend the schema needs to be in the same Active Directory domain and site as the schema master.

•If you use the DomainController parameter, make sure to use the name of the domain controller that's the schema master.

•The only way to extend the schema for Exchange is to use the steps in this topic or use Exchange 2016 Setup. Other ways of extending the schema aren't supported.

tipTip:

If you don't have a separate team that manages your Active Directory schema, you can skip this step and go directly to Step 2. Prepare Active Directory . If the schema isn't extended in step 1, the commands in step 2 will extend the schema for you. If you decide to skip step 1, the information you need to keep in mind above still applies. 

When you're ready, do the following to extend your Active Directory schema. If you have multiple Active Directory forests, make sure you're logged into the right one.

1.Make sure the computer is ready to run Exchange 2016 Setup. To see what you need to run Setup, check out the  Active Directory preparationsection in .

2.Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.

3.Run the following command to extend the schema

CopySetup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms  <--------doesn't work 

After Setup finishes extending the schema, you'll need to wait while Active Directory replicates the changes to all of your domain controllers. If you want to check on how replication is going, you can use the repadmin tool. Repadmin is included as part of the Active Directory Domain Services Tools feature in Windows Server 2012 R2 and Windows Server 2012. For more information about how to use it, see Repadmin.

2. Prepare Active Directory

Now that the Active Directory schema  has been extended, you can prepare other parts of Active Directory for Exchange 2016. During this step, Exchange will create containers, objects, and other items in Active Directory that it'll use to store information. The collection of all of the Exchange containers, objects, attributes, and so on, is called the Exchange organization.

Before you prepare Active Directory for Exchange, there are a few things to keep in mind:

•The account you're logged in as needs to be a member of the Enterprise Admins security group. If you skipped step 1 because you want the PrepareAD command to extend the schema, the account you use also needs to be a member of the Schema Admins security group.

•The computer where you'll run the command needs to be in the same Active Directory domain and site as the schema master. It'll also need to contact all of the domains in the forest on TCP port 389.

•Wait until Active Directory has replicated the changes made in step 1 to all of your domain controllers before you do this step.

When you run the command below to prepare Active Directory for Exchange, you'll need to name the Exchange organization. This name is used internally by Exchange and isn't normally seen by users. The name of the company where Exchange is being installed is often used for the organization name. The name you use won't affect the functionality of Exchange or determine what you can use for email addresses. You can name it anything you want, as long as you keep the following in mind:

•You can use any uppercase or lowercase letters from A to Z.

•You can use numbers 0 to 9.

•The name can contain spaces as long as they're not at the beginning or end of the name.

•You can use a hyphen or dash in the name.

•The name can be up to 64 characters but can't be blank.

•The name can't be changed after it's set.

When you're ready, do the following to prepare Active Directory for Exchange. If the organization name you want to use has spaces, enclose the name in quotation marks (").

1.Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.

2.Run the following command:

Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms    <----- doesn't work     

After Setup finishes preparing Active Directory for Exchange, you'll need to wait while Active Directory replicates the changes to all of your domain controllers. If you want to check on how replication is going, you can use the repadmin tool. repadmin is included as part of the Active Directory Domain Services Tools feature in Windows Server 2012 R2 and Windows Server 2012. For more information about how to use the tool, see Repadmin.

3. Prepare Active Directory domains

The final step to get Active Directory ready for Exchange is to prepare each of the Active Directory domains where Exchange will be installed or where mail-enabled users will be located. This step creates additional containers and security groups, and sets permissions so that Exchange can access them.

If you have multiple domains in your Active Directory forest, you have a couple of choices in how you prepare them. Select the option that matches what you want to do. If you only have one domain, you can skip this step because the PrepareAD command in step 2 already prepared the domain for you.

PLEASE HELP ANYBODY!!!

Error:

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

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

          {

            Set-Service MpsSvc -StartupType Automatic

            Start-SetupService -ServiceName MpsSvc

          }

        " was run: "Microsoft.Exchange.Configuration.Tasks.ServiceDisabledException: Service 'bfe' is disabled on this server. ---> System.InvalidOperationException: Cannot start service bfe on computer '.'. ---> System.ComponentModel.Win32Exception: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it

   --- End of inner exception stack trace ---

   at System.ServiceProcess.ServiceController.Start(String[] args)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartServiceWorker(ServiceController serviceController, String[] serviceParameters)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

   at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Thanks

Manojkumar Bhoyar

From: Manoj Bhoyar Sent: Wednesday, October 07, 2015 3:06 PMTo: Rajesh Velagapudi Subject: error while installing exchange 2013 CU6

Error:

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

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

          {

            Set-Service MpsSvc -StartupType Automatic

            Start-SetupService -ServiceName MpsSvc

          }

        " was run: "Microsoft.Exchange.Configuration.Tasks.ServiceDisabledException: Service 'bfe' is disabled on this server. ---> System.InvalidOperationException: Cannot start service bfe on computer '.'. ---> System.ComponentModel.Win32Exception: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it

   --- End of inner exception stack trace ---

   at System.ServiceProcess.ServiceController.Start(String[] args)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartServiceWorker(ServiceController serviceController, String[] serviceParameters)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

   at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

I am presently migrating from Exchange 2007 on a Small Business Server 2007 to Exchange 2013 on a VM.  I have already moved the mailboxes and for the most part I'm done.  I never used Exchange Public folders at this location.  Do I still need to migrate the SYSTEM public folders (offline address book, schedule+Free Busy. etc.).  Because I never used public folders can I effectively "ignore" this migration step?  Or do I have to migrate the public folders because of the system folders? 

If I have to migrate, is there an "easy" way to do it.  The methods I've found have relied on the Exchange management shell.  Thanks!

Hi all,

           in order to move to exchange 2016, im upgrading exchange 2013 to CU10.

When trying to move to CU10 on exchange 2013, I get the following error during the first phase of setup.

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

               install-AdministrativeGroup -DomainController $RoleDomainController

" was run: "Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on AD03.company.com. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.

  at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)

  at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)

  at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)

  at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)  --- End of inner exception stack trace ---

  at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)

  at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)

  at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)

  at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)

  at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InstallConfigurationObject[TObject](ADObjectId id, Boolean force, TObject instance)

  at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InternalProcessRecord()

  at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

  at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Using ADSIedit, I can see that the "Folder Hierarchies" does indeed already exist, as it should, and have verified the permissions on the key, allowing the exchange servers full control.

The same error occurs if run from the gui or command "setup.exe /p /IAcceptExchangeServerLicenseTerms" from any of the exchange 2013 servers or DC's.

Whenever I try to set the internalURL I keep getting an active directory error seen below.

Active Directory operation failed on Server1.MURRAY.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150BC1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 

I have made sure that Permission Inheritance is enabled. Any idea why I am getting this error still?

Thank you.

Hi everyone,

(I'm sorry if I posted this question in the wrong forum).

We are in the process of enabling Hybrid mode for our Exchange 2013 (CU9) installation. But we seem to have run into some problem with the Hybrid Configuration Wizard (HCW)... I posted my original problem in the community forum at Office 365 but after some troubleshooting with the Microsoft support, they concluded that the fault was with the on-premises installation and that the HCW never ran therefore on-premises Exchange has not communicated with Exchange Online. They've simply redirected me and my question to this forum for further assistance.

So... basically what I've done so far is:

1. Create an Office 365 E4 account and a global administrator.
2. Verified my custom domain.
3. Created an Azure Active Directory user sync.
4. Setup a working ADFS for SSO (verified with the Remote Connectivity analyzer).
5. I've logged in to the ECP panel (with my administration account).
6. Then clicked the Hybrid -> Enable - in order to start the HCW.
7. Logged on with my Office 365 Global administration account when prompted.
8. After some loading "Please wait" I'm given the error message below:

"The wizard did not complete successfully. Please see the list below for error details. Unable to access the Federation Metadata document from the federation partner. Detailed information: The remote server returned an error: ‎(400)‎ Bad Request.."

I'm unable to find any log files under: "%SystemDrive%\Program Files\Microsoft\Exchange Server\V15\Logging\Update-HybridConfiguration"or any error messages in the Event Viewer.

I would appreciate any help on what to try or do next.

Regards,

Anders

Hi guys.

We had EXCHANGE 2010 in SITE1 and EXCHANGE2010 in SITE2.

In SITE1 we have migrated EXCHANGE2010 to EXCHANGE2013 and decomission the old server.

Current scenario.
SITE1 - with EXCHANGE2013

SITE2 - with EXCHANGE2010

We have problems with Outlook clients on SITE2 who's mailboxes are on EXCHANGE2010.
Their Outlook clients redirects Outlook Anywhere to settings which are on Exchange2013.

If we take a look on Autodiscover test for user on site2 on exchange2010 it resolves scp sucessfully from exchange2010 on site2.

But we also see the he recieves:

EXCHANGE RCP - from exchange 2010

EXCHANGE HTTP - from exchange 2013

Is it possible that exchange2013 from SITE1, somehow takes "precedence" and push OutlookAnywhere settings to users which are in SITE2 and hosted on EXCHANGE2010?

with best regards 

bostjanc

The Help link for this simply implies I didn't prepare the Domain Controller before installing which I've already done.

I followed steps at https://technet.microsoft.com/en-us/library/bb125224(v=exchg.160).aspx

I also did all the prep on the exchange server itself before attempting the install.

I've also tried removing the Action and Watermark registry under mailbox which did fix one issue that i got before this.

Any help would be appreciated, thanks.

Error:
The following error was generated when "$error.Clear(); 
        set-ExchangeServerRole -Identity $RoleFqdnOrName -IsUnifiedMessagingServer:$true -DomainController $RoleDomainController

" was run: "The operation couldn't be performed because object 'mail.domain.local' couldn't be found on 'dc.domain.local'.".

I have upgrade to Exchange 2013, moved all the mailboxes and everything seems to be working fine.  The final step is to remove the legacy Exchange 2010 server and UM server. 

The TechNet guides explain that I just need to uninstall Exchange 2010 on the old server.  So, I thought that I would first try shutting down the old Exchange 2010 server and let the new Exchange 2013 ride solo.  All seemed OK, I was getting emails in Outlook 2010 and on our smartphones. But, the next morning after re-launching Outlook 2010, even though it said it was connected, I was not receiving any new email.

I turned back on the old Exchange 2010 server, and then all of the emails starting coming into Outlook 2010. 

Looking at the event logs on Exchange 2013, I see that I was getting 3005 warnings regarding [Autodiscover] Marking ClientAccess 2010 server srv2010.domain.com (https://srv2010.domain.com/Autodiscover) as unhealthy due to exception: System.Net.WebException: The operation has timed out....

Before I uninstall Exchange 2010, is there another way to remove this apparent dependency on the old server?

Thanks.. Chris

Hi All,

Our company was purchased 2 years ago by another company. I have been running 2 independent forests with a trust relationship while i worked out how to migrate to the single forest.

We have 2008R2 Forest with Exchange 2013 on each.

I am unable to download the ADMT and PES due to a website issue (1st couldn't get the site up, now the files are not available)

So, i am wondering the best course. I have seen on Petri regarding this. But that was mainly aimed at 2010. https://www.petri.com/exchange-2010-cross-forest-migration

Does anyone have any good pointers on this? I have seen lots of 2007 to 2013 or 2007 to 2010 and 2010 to 2013.. but nothing that met our requirements.

Hi,

We are about to install Exchange 2013 CU10 when we notice that there are existing Exchange objects already in the Active Directory.

We have verified that the Exchange servers have been decommissioned but incorrectly. Via the attribute value, we determine that 2013 CU3 was the version installed previously.

We wish to do a clean installation for the Exchange 2013 CU10 not polluted by the previous installation. May I know what is the cleaning required to achieve this.

Thanks.

I get the error below when installing exchange 2013 in my Exchange 2010 Environment.

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
          {
              $mailboxId = [Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter]::MigrationMailboxName;
              $dispName = "Microsoft Exchange Migration";
              $mbxs = @(Get-Mailbox -Arbitration -DomainController $RoleDomainController -Filter {Name -eq $mailboxId});
              $migrationMailbox = $null;

              if ($mbxs.Length -eq 0)
              {
                  Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
                  $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                  if ($dbs.Length -ne 0)
                  {
                      Write-ExchangeSetupLog -Info ("Retrieving users with Name=$mailboxId.");
                      $arbUsers = @(Get-User -Filter {Name -eq $mailboxId} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                      {
                          Write-ExchangeSetupLog -Info ("Enabling mailbox $mailboxId.");
                          $migrationMailbox = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
                      }
                  }
              }
              else
              {
                  $migrationMailbox = $mbxs[0];
              }

              # Set the Organization Capabilities and quotas needed for this mailbox
              if ($migrationMailbox -ne $null)
              {
                  Set-Mailbox -Arbitration -Identity $migrationMailbox -ProhibitSendReceiveQuota 300MB -ProhibitSendQuota 300MB -IssueWarningQuota 150MB -RecoverableItemsQuota 30GB -RecoverableItemsWarningQuota 20GB -UseDatabaseQuotaDefaults $false -SCLDeleteEnabled $false -SCLJunkEnabled $false -SCLQuarantineEnabled $false -SCLRejectEnabled $false -HiddenFromAddressListsEnabled $true -DisplayName $dispName -Management:$true -Force;
              }
              else
              {
                  Write-ExchangeSetupLog -Info ("Cannot find migration mailbox with name=$mailboxId.");
              }
          }
        " was run: "Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
          {
              $mailboxId = [Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter]::MigrationMailboxName;
              $dispName = "Microsoft Exchange Migration";
              $mbxs = @(Get-Mailbox -Arbitration -DomainController $RoleDomainController -Filter {Name -eq $mailboxId});
              $migrationMailbox = $null;

              if ($mbxs.Length -eq 0)
              {
                  Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
                  $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                  if ($dbs.Length -ne 0)
                  {
                      Write-ExchangeSetupLog -Info ("Retrieving users with Name=$mailboxId.");
                      $arbUsers = @(Get-User -Filter {Name -eq $mailboxId} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                      {
                          Write-ExchangeSetupLog -Info ("Enabling mailbox $mailboxId.");
                          $migrationMailbox = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
                      }
                  }
              }
              else
              {
                  $migrationMailbox = $mbxs[0];
              }

              # Set the Organization Capabilities and quotas needed for this mailbox
              if ($migrationMailbox -ne $null)
              {
                  Set-Mailbox -Arbitration -Identity $migrationMailbox -ProhibitSendReceiveQuota 300MB -ProhibitSendQuota 300MB -IssueWarningQuota 150MB -RecoverableItemsQuota 30GB -RecoverableItemsWarningQuota 20GB -UseDatabaseQuotaDefaults $false -SCLDeleteEnabled $false -SCLJunkEnabled $false -SCLQuarantineEnabled $false -SCLRejectEnabled $false -HiddenFromAddressListsEnabled $true -DisplayName $dispName -Management:$true -Force;
              }
              else
              {
                  Write-ExchangeSetupLog -Info ("Cannot find migration mailbox with name=$mailboxId.");
              }
          }
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".

Dear All

I am currently starting the installation Exchange server 2013 in exchange 2007 SP3 Environment. but when I kick the installation I get the following 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: "Couldn't resolve the user or group "mydomain.local/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.".

*****************************************************

SOME FORUMS ARE ADVISING TO DELETE THE (DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}) WHICH IS DISABLED IN ACTIVE DIRECTORY. 

KINDLY ADVISE THE BEST WAY TO RESOLVE THIS 

YOUR USUAL SUPPORT IS GREATLY APPRECIATED IN ADVANCE

REGARDS

MICHAEL

having some issue after we have decomission exchange2010 in site one and migrated everything to exchange 2013.

SITE 1

EXCHANGE 2013

SITE 2

EXCHANGE 2010

Site 2, Outlook clients which are hosted on exchange2010 on site2 gets popup redirections internally.

If we try with test E-mail Autoconfiguration internally on OUTLOOK 2013 (SITE2 - exchange2010) we get.

POP UP: https://owa.domain2.com/autodiscover/autodiscover.xml
And errors: httpStatus=500; FAILED (0x800C820F)

On exchange2010 on SITE2 results:

Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Identity    : EXCHANGE2010\EWS (Default Web Site)
InternalUrl : https://owa.domain2.com/EWS/Exchange.asmx
ExternalUrl : https://autodiscover.domain2.com/EWS/Exchange.asmx

Get-ClientAccessServer -Identity exchange2010.subdomain.domain.local | fl

AutoDiscoverServiceInternalUri       : https://autodiscover.domain2.com/autodiscover/autodiscover.xml
AutoDiscoverSiteScope                : {SITE2}

Please help?

bostjanc

After moving mailboxes to Exchange 2013, I get this loop of where when I log in through the OWA in 2013, it redirects me tohttps://legacy.myorg.com/owa which then presents a message that the mailbox needs to be accessed in a different version of OWA, and it gives the link to it. So I click the link and I go right back to the OWA 2013 login page.

Now here is where it gets unusual... if I'm outside my network accessing OWA externally, it continues this cycle over and over.  If my users are internal and they try it, it puts them on OWA correctly.  It never attempts to redirect them to the legacy site (or it may try once, but then after that they are fine).  Exchange knows that the mailbox has moved and sticks the user to the correct OWA server.  But all that's internal.  Externally, it just goes back and forth which is aggravating because I do have a few users that use OWA externally majority of the time.

Any ideas?

JB

Hi Everyone,

i am trying to export some mailbox in my exchange2010 Sp3 to Pst , but when excute the below command i got the Error:

New-mailboxExportRequest -Mailbox "admin" -filepath \\ server\Pst\admin.pst

i got the following Error:

The call to 'net.tcp://server name/Microsoft.Exchange.MailboxReplicationService server name' timed out. Error details: This request operation sent to net.tcp:// server name//Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00).

i tried to increase TimeOut on Client Access folder in Web.config file  i make (DataImportTimeout=00:20:00)but not successfully.

Note: (Pst) folder has been shared and give Group (exchange trust subsytem) full permission.

thank in advance 

I think I have a weird scenario.

We have 2 AD domains that don't talk to each other at all. I'll try to explain in detail...

We have contoso.com and alumni.contoso.com...but remember they were named like that but they are not related, not even in the same network subnet.

In contoso.com we have exchange 2010 working with outlook web app and certificates without problems. We installed a new exchange 2013 Mailbox and CAS server, no certificates.

Alumni.contoso.com is setup in Office365, so our DNS is configured to forward mail for alumni.contoso.com to microsoft.

Contoso.com receives our email in our exchange 2010.

I'm working on getting the certificates for exchange 2013 and moving the users from 2010 to 2013...I did this with exchange 2007...

What I'm trying to figure out is how to move the on premises contoso.com exchange if I already have alumni.contoso.com in Office365. Since alumni.contoso.com "acts" as a child domain from contoso.com I think I might run into trouble?

Thanks for your time and suggestions.

I have Exchange 2007 currently coexisting with Exchange 2013. I have one server 2008 r2 server with Exchange installed all roles on one server. I also have 2x 2012 r2 servers one with CAS role and one with Mailbox role. So far the install has gone without issue but before i can move on i need to be able to see the 2007 database in the 2013 ECP but currently only the 2013 database is listed and I do not feel good about moving further until i can get 2013 to recognize the 2007 Database. 

Can someone help??

Hi ,

I am currently testing a cross forest migration from exchange 2007 to exchange 2013. i do not have trust between my forest but i did set up conditional forwarding in both the source and target environment.

The Mailbox replication service does not behave as expected when i submit a new move request.

the move request : New-MoveRequest -Identity "f2867850-5e88-4f97-9efb-0b867a1fdb4b" -BadItemLimit "10" -TargetDeliveryDomain "TargetDomain" -TargetDatabase "{cbc90e5e-6124-458c-8105-464bc27d26c1}" -RemoteCredential (Get-Credential "sourcecredential") -RemoteGlobalCatalog "FQDN of source GC" -RemoteLegacy:$true

the error : "The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (15.0.775.35 caps:3F)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client."

I can ping both global catalog in the source environment and in the target from both side. nslookup and autodiscover is working as well.

MRS Proxy is enable on the exchange 2013 side and i have enable remote Powershell on both side.

i do not have any load balancer configure.

If anyone can point me in the right direction where to look it would be greatly appreciated.

thanks you

Fr&#233;d&#233;ric B&#233;dard

Hi every one, i need some help. Setup process of Exchange 2016 finishing with Error on step 14:

Ошибка:
При выполнении "$error.Clear(); 
start-SetupService -ServiceName MSExchangeFrontendTransport

" произошла следующая ошибка: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Службе 'MSExchangeFrontendTransport' не удалось достичь состояния 'Running' на этом сервере.
   в Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   в Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   в Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   в Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   в Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Service MSExchangeFrontedTransport can not start. It begin starting and stoped, so many times. In System monitor there is id mistake 7031. I could not stop it manually - it starts and then stops automatically. If u have any ideas i will really appreciate it! Thanks!