Exchange 2010 SP3: UCMA requires the following missing Windows features
When installing Exchange 2010 SP3 on a server with Windows Server 2012 you need to install some prerequisites first. Each server with the Client Access role requires the Unified Communications Managed API 4.0 Runtime.
You may run into this error message when you try to install:
Microsoft Unified Communications Managed API 4.0, Runtime requires the following missing Windows features.
There are a series of requirements for Active Directory preparation to be successful:
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2008 R2 (SP1 or later), in PowerShell run:
For Windows Server 2012, in PowerShell run:
If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:
Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-Clustering-CmdInterface, RSAT-ADDS
The cmdlet action is shown in Figure 03.
Figure 03
You may run into this error message when you try to install:
Microsoft Unified Communications Managed API 4.0, Runtime requires the following missing Windows features.
- Media Foundation
Solution
Add Media Foundation via PowerShell
Run the following command;
Install-WindowsFeature Server-Media-Foundation
Add Media Foundation via Server Manager
1. Launch Server Manager (ServerManager.exe) > Manage > Add Roles and Features > Next > Next > Next > Scroll Down > Select Media Foundation > Next > Install.
Permisos:
Schema admin, enterprice admin:
Preparing Active Directory for Exchange Server 2013
When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.There are a series of requirements for Active Directory preparation to be successful:
- Schema master running Windows Server 2003 with SP2, or a later version of Windows Server
- At least one Global catalog server per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
- At least one Domain controller per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
- Forest functional mode of Windows Server 2003 or higher
- An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setup
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2008 R2 (SP1 or later), in PowerShell run:
Import-Module ServerManager Add-WindowsFeature RSAT-ADDS
For Windows Server 2012, in PowerShell run:
Install-WindowsFeature RSAT-ADDS
If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:
setup /PrepareAD /OrganizationName:"your organization name" /IAcceptExchangeServerLicenseTerms
Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.
setup /PrepareAD /IAcceptExchangeServerLicenseTermsFor other Active Directory preparation scenarios, such as multiple forests or multiple domains, refer to this article on TechNet.
Prerequisitos de componentes sobre servers de correo
Con la propia instalación desde la UI se realiza automáticamente con solo elegir un seteo:
Tambien podemos instalarlo desde el Shell:
The cmdlet action is shown in Figure 03.
Figure 03
No mas exch managment tool:
https://www.youtube.com/watch?v=GpH0jC_2-FQ#t=248
Hi All :
When you installing Exchange Server 2013 Mailbox High-available on Windows Server 2012 environment , you may encounter this error : An Active Manager operation failed with a transient error: Please retry the operation. Error: The fully qualified domain name for node 'XXXX' could not be found.
Now , you need to assign the machine account of the first node added to the DAG with full control of the pre-staged object.
1. Select the appropriate container in Active Directory Users and Computers snap-in console where you wish the account to be created. Right click, select New –> Computer :
2. In the Computer name box, type the name that was assigned to the database availability group :
3. Click OK , the computer account created . Right-click this account and click Properties :
4. Then click Security tab , and click Add... , add the first DAG member server computer account and assign the machine account Full control Allow permission :
6. When presented with the disable dialog, select Yes :
7. After the object has been successfully disabled, press the OK button on the success confirmation :
8. And now , you can start to creating DAG successfully !
When you installing Exchange Server 2013 Mailbox High-available on Windows Server 2012 environment , you may encounter this error : An Active Manager operation failed with a transient error: Please retry the operation. Error: The fully qualified domain name for node 'XXXX' could not be found.
Now , you need to assign the machine account of the first node added to the DAG with full control of the pre-staged object.
1. Select the appropriate container in Active Directory Users and Computers snap-in console where you wish the account to be created. Right click, select New –> Computer :
2. In the Computer name box, type the name that was assigned to the database availability group :
3. Click OK , the computer account created . Right-click this account and click Properties :
4. Then click Security tab , and click Add... , add the first DAG member server computer account and assign the machine account Full control Allow permission :
6. When presented with the disable dialog, select Yes :
7. After the object has been successfully disabled, press the OK button on the success confirmation :
8. And now , you can start to creating DAG successfully !
No hay comentarios:
Publicar un comentario