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