REF: Exchange 2010 migration from Exchange 2003

-

 

 

Upgrade Exchange 2003 to Exchange 2010 - Part II

Comments

Post a Comment

Popular posts from this blog

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Secti...
Read more

REF: Planning Exchange 2010 DAG - Part 1 - Network Requirements

-
Image
  Planning for High Availability and Site Resilience  - Network Requirements (a single MAPI network / one or more Replication networks ) In Exchange 2010, each DAG will have multiple networks: a single MAPI network , which is used by other Exchange 2010 servers to communicate with the Mailbox server in the DAG, and one or more Replication networks , which are used for log shipping and seeding within the DAG. It's important that the DAG networks are configured correctly. (two adapters/ MAPI network failover/ Replication network revert to MAPI Network/ ) Each member of the DAG must have at least two network adapters installed . This configuration provides you with one MAPI network and one Replication network, and the following recovery behaviors: In the event of a failure affecting the MAPI network, a server failover will occur (assuming there are healthy mailbox database copies that can be activated). In the event of a failure affectin...
Read more

Backup issues and limitations with Exchange 2010 and DAG

-
  Backup issues and limitations with Exchange 2010 and DAG http://blogs.technet.com/b/ehlro/archive/2010/02/13/backup-issues-and-limitations-with-exchange-2010-and-dag.aspx   13 Feb 2010 12:14 AM   · I have come up with the following conclusions after testing some backup functionalities with Windows Server Backup and Exchange 2010 with DAG. There are some limitations that we'll have to be aware of: 1. Windows Server Backup (WSB) When using Windows Server Backup to backup an Exchange 2010 database the backup fails under the following conditions: - Each database and associated logs are stored on a dedicated LUN (these are presented by the SAN software to the OS as separate volumes as expected in Disk Management) - The database LUN is presented via a mount point - Some database copies on the server are not active For example, two mailbox servers that are DAG members (SERVER1 & SERVER2), and two mailbox databases (MBX1 & MBX2). If both mailbox...
Read more