Erro ao Adicionar MailboxServer na DAG (Exchange 2013)

Quando tentamos adicionar um servidor  em um "Database Availability Group" o erro abaixo aparece:

A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. 

Clique na imagem para ver em tamanho original

Para resolver este erro, Edite as Propriedades o Objeto DAG01 (objeto do tipo Computador) e adicione as permissões conforme imagem abaixo:

Execute novamente o comando para adicionar o server na DAG e depois liste os servidores pertencentes a DAG01 conforme imagem:

Referências:

https://technet.microsoft.com/en-us/library/ff367878.aspx

Setup cannot continue with the upgrade because the 'cscript' () process (ID : ) has open files. Close the process and restart Setup.

Este erro ocorre geralmente ao atualizar o Exchange Server 2010/2013 com agente do System Center instalado.

Exemplo:

Preparing Exchange Setup

    Copying Setup Files                           COMPLETED

The following server roles will be upgraded
Languages
Client Access Role
Management Tools

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Organization Checks                                        COMPLETED
    Language Pack Checks                                    COMPLETED
    Client Access Role Checks                              FAILED
     Setup cannot continue with the upgrade because the 'cscript' () process (ID
: 4128) has open files. Close the process and restart Setup.

     Setup cannot continue with the upgrade because the 'cscript' () process (ID
: 4368) has open files. Close the process and restart Setup.

     Setup cannot continue with the upgrade because the 'cscript' () process (ID
: 6604) has open files. Close the process and restart Setup.

     Setup cannot continue with the upgrade because the 'cscript' () process (ID
: 6684) has open files. Close the process and restart Setup.

     Setup cannot continue with the upgrade because the 'cscript' () process (ID
: 6688) has open files. Close the process and restart Setup.


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

Exchange Server setup encountered an error.

Porém, basta parar o agente System Center Management (servicename: HealthService)
E o resultado é este:

Preparing Exchange Setup

    Copying Setup Files                           COMPLETED

The following server roles will be upgraded
Languages
Client Access Role
Management Tools

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Organization Checks                                       COMPLETED
    Language Pack Checks                                    COMPLETED
    Client Access Role Checks                              COMPLETED

Configuring Microsoft Exchange Server

    Organization Preparation                                  COMPLETED
    Preparing Setup                                                COMPLETED
    Stopping Services                                            COMPLETED
    Language Files                                                COMPLETED
    Removing Exchange Files                              COMPLETED
    Preparing Files                                                COMPLETED
    Copying Exchange Files                                 COMPLETED
    Language Files                                               COMPLETED
    Restoring Services                                         COMPLETED
    Languages                                                      COMPLETED
    Client Access Server Role                             COMPLETED
    Exchange Management Tools                       COMPLETED
    Finalizing Setup                                            COMPLETED

The Microsoft Exchange Server setup operation completed successfully.

Alterar a porta RDP(3389) de forma rápida

Configurando "TlsCertificateName" em ReceiveConnector do Exchange Server 2013

Erro ao executar o cmdlet "Set-ReceiveConnector -identity "conector" -TlsCertificateName ?

...
value of type "Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeCertificate" to type
"Microsoft.Exchange.Data.SmtpX509Identifier".
    + CategoryInfo          : InvalidData: (:) [Set-ReceiveConnector], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-ReceiveConnector
...

Ao executar o comando tentando adicionar um certificado válido "Client Receive Connector" o erro acima é exibido,
Resolvi escrever este post porque a explição do get-help set-receiveconnector não é clara, informando que os parametros válidos são do Type [I]Issuer[S]Subject. Então resolvi colocar o comando completo abaixo para um certificado com nome ficticio de dhois.com


Set-ReceiveConnector -Identity "SERVIDOR1\Client Frontend SERVIDOR1" -TlsCertificateName "<I>CN=RapidSSL SHA256 CA - G3, O=GeoTrust Inc., C=US<S>CN=*.dhois.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)14, OU=GT123456789"

Exchange: MapiExceptionNotFound error while moving the mailb...

MapiExceptionNotFound error while moving the mailbox
Error: MapiExceptionNotFound: Unable to synchronize manifest. (hr=0x8004010f, ec=-2147221233)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=239]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=503][latency=15]

This error will appear due to mailbox corruption to eliminate the above error need repair the mailbox

execute the following shell command then clear the move request and initiate again move request

New-MailboxRepairRequest -Mailbox userID -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

Use EventViewer to follow the progress

Application >> Level=Information  Source=MSExchangeIS Mailbox Store
--------------------------
Mailbox level online integrity check for request 68abeafe-003c-5b3b-9e49-94a68c48e6f4 started:
Database=teste.01
Mailbox=D84234C4-321D-41DE-A486-D8444E864326
Flags=Detect, Fix
Tasks=SearchFolder
--------------------------
Online integrity check for request 68abeafe-003c-5b3b-9e49-94a68c48e6f4 completed successfully.
--------------------------

Reference: http://exchangelearn.blogspot.com.br/2013/10/mapiexceptionnotfound-error-while.html

Desabilitando IPv6 em todas as interfaces windows 2008 R2, 2008 e Seven

Para desabilitar o IPv6 em todas as interfaces do Windows 7, 2008 e 2008 R2. basta executar o comando:

reg add HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents /t REG_DWORD /d 0xffffffff /f

Este comando cria o registro "DisabledComponents" com o tipo "DWORD" e adiciona o valor "ffffffff" a este registro. 

Para testar você pode executar um ping em localhost, antes de executar o comando "reg add" o retorno deve ser algo como:

C:\>ping localhost

Disparando servertest.edg.local [::1] com 32 bytes de dados:

Resposta de ::1: tempo<1ms

Resposta de ::1: tempo<1ms

Depois do executar o comando para desabilitar o IPv6 e REINICIAR o server, o retorno deve ser algo como:

C:\>ping localhost

Disparando servertest.edg.local [127.0.0.1] com 32 bytes de dados:

Resposta de 127.0.0.1: bytes=32 tempo<1ms TTL=128

Resposta de 127.0.0.1: bytes=32 tempo<1ms TTL=128

The sender does not meet basic 550-5.7.1 ipv6 sending guidelines of authentication and rdns resolution of 550-5.7.1 sending ip. Please review 550 5.7.1

mx.google.com #550-5.7.1 [2002:xxxx:xxxx::xxxx:612e 16] The sender does not meet basic 550-5.7.1 ipv6 sending guidelines of authentication and rdns resolution of 550-5.7.1 sending ip. Please review 550 5.7.1 https://support.google.com/mail/answer/81126for more information. 21si6252847yhf.314 - gsmtp ##

Este erro acontece devido ao servidor de origem ter conectado ao MX do Google usando IPv6. Se não há configuração de reverso para o IPv6 que estiver usando, a mensagem acima será mostrada.

Este erro é mais comum em servidores Exchange e pode ser resolvido primeiramente desabilitando o IPv6 da placa de rede do HUB.

Feito isto, execute o comando abaixo, caso retorne status "default" significa que o "6to4" está habilitado.

C:\>netsh interface ipv6 6to4 show state

6to4 Service State        : default

Undo on Service Stop     : default

Para desabilitar execute o comando:

c:\>netsh interface ipv6 6to4 set state disabled

C:\>netsh interface ipv6 6to4 show state

6to4 Service State      : disabled

Undo on Service Stop   : default