How To Install Exchange 2013 On Windows Server 2012 R2

KB ID 0001472

Exchange 2022 Migration

If Exchange 2022 was Exchange 2022 in a pretty apparel, and so with Exchange 2022 it's merely added a hat. In the past, every tertiary Exchange release was a major rebuild, merely Exchange 2022 is simply Exchange version xv.1 (Commutation 2022 was 15.0 and Commutation 2022 is version 15.i).

So the Substitution 2022 Migration is pretty much the same as it was from 2022 > 2022, or even 2022 > 2022.

•  There should be NO Exchange 2022 servers in existence before deploying Exchange 2022. You would need to upgrade to 2022/2016 first.
• There's no Unified Comms Role with Substitution any more! If you need to upgrade look at Skype for Concern 2022.
• Edge Server Role is all the same supported.
• Windows Server Core (2016) is now supported with Exchange 2022.
• Windows Server 2022 (Standard or Datacenter) are supported host Operating systems.

Solution

As with all Substitution migrations brand sure your Active Directory Domain/DNS/Existing Substitution system is healthy before y'all start. Then upgrade the existing Substitution to the latest cumulative update.

Commutation 2022 Prerequisites

Yous will demand your Server 2022R2 or Server 2022 server fully updated and added to your domain, then to add the required roles and services use the following Powershell commands for Server 2022, 2022 and 2022;

Server 2022 / 2022 R2

Install-WindowsFeature Equally-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Procedure-Model, Web-Asp-Net45, Spider web-Bones-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Spider web-Http-Errors, Web-Http-Logging, Spider web-Http-Redirect, Web-Http-Tracing, Spider web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Spider web-Mgmt-Panel, Web-Mgmt-Service, Web-Cyberspace-Ext45, Spider web-Asking-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS

Server 2022

Install-WindowsFeature Net-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Spider web-Assimilate-Auth, Web-Dir-Browsing, Web-Dyn-Pinch, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Spider web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Spider web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Spider web-Cyberspace-Ext45, Spider web-Request-Monitor, Spider web-Server, Web-Stat-Compression, Web-Static-Content, Spider web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS

Note: At present Required on Server 2022: You will need to install .Net 4.8 (link), on Server 2022 and 2022.

You lot need to install the MS Unified Communications API 4.0 (link).

You will also need to install Microsoft Visual C++ (link)

Either download the Exchange 2022 install media, or insert the Commutation 2022 DVD, and launch setup.exe > Next > Next > Files volition be copied over.

Don't I demand to extend the schema, woods or domain? The setup does all this for you lot, y'all don't need to do this manually anymore, (yes you can manually practice this before installing, if y'all want to, simply unless your schema primary is in a unlike root domain, or you're not a schema admin, then I don't come across the signal!)

Introduction Page > Next > At the EULA tick "I Accept…" > Next > Tick "Use Recommended settings" > Next.

Select 'Mailbox role', and 'Automatically install Windows Server roles and features…" > Adjacent > Select the install directory, Notation: In production you probably DON'T desire this on the Windows System drive > Adjacent > Unless yous have a reason to disable Malware scanning and so select 'No' > Side by side.

Readiness Checks > Fix and Errors and heed any warnings > Install > The product volition install, this will take a long time!

End > Reboot the server.

An there's our new Exchange 2022 Server.

Exchange 2022 EnterProduct Primal

Servers > Servers > Select the 2022 Substitution Server > Enter Product Key  > Relieve

Notation: On the pre-release version of Exchange 2022, the Exchange 2022 keys worked fine.

At the warning click OK.

Equally directed Restart the 'Microsoft Substitution Information Store' service.

Restart-Service MSExchangeIS

Transfer Exchange Certificate to Exchange 2022

I'1000 using a wildcard certificate then I desire to export the cert form my Exchange 2022 server and import it onto my new Commutation 2022 Server. You volition want to practise the aforementioned if you take a document with your public domain name on it and this will be your 'net facing' Exchange server. Servers > Certificates > Select the Substitution 2022 Server, in the drop down menu > Select The Certificate > Click the ellipses (three dots) > Export Substitution Document > Supply a UNC path and password > OK.

Alter the Dropdown to the Substitution 2022 Server > Click the ellipsis > Import Exchange Document > Supply the UNC path and countersign yous used (above) > Next.

Add together in the Exchange 2022 Server > Cease.

Substitution 2022 Assign Services to Certificate

Select the newly imported certificate> Edit > Services > Select the services > Save > Notation: Here I'm selecting SMTP and IIS. (You cant apply a wildcard cert for IMAP,Pop).

Commutation 2022 Rename Mailbox Database

Servers > Databases > Commutation ever gives databases annoying names > Select the Database on the 2022 Exchange Server > Edit > Rename it  > Save.

Note: The path to the Database retains the original name (we will fix that in the next stride).

Exchange 2022 Migration Move Mailbox Database

I'g pretty old school, I like my Exchange databases on their own drive/partition, and I like the logs on some other drive/partition. To move both the Database and the Logs;

Move-DatabasePath -Identity Database-Name -EdbFilePath Ten:\Folder\Database\Database-Proper noun.edb -LogFolderPath Fifty:\Folder\Log-Binder\

Add Exchange 2022 to the Send Connector

Mail Menstruum > Send Connectors > Select your mail SMTP connector(s) > Edit > Scoping > Source Server section > Add > Add in the new server > OK > Salvage.

Note: The Commutation server will now need to have TCP port 25 (SMTP) open outbound on your corporate firewall.

Migrating Public Binder Mailboxes

Utilise the following command;

Get-Mailbox -PublicFolder -Server            Former-SERVER-Proper name            | New-MoveRequest -TargetDatabase            TARGET-MAILBOX-DATABAASE          

Hybrid (On-Prem) Substitution Migration Note

If your on-premise Exchange is function of an Office 365 Hybrid deployment y'all will demand to add the new server to the 'scope' for that connector also!

Decommission Substitution 2022

From this point forrad nosotros are going to outset getting rid of our Exchange 2022 server, they tin of course coexist, (if you wanted to wait a while).

For that reason I change the 'mail flow' on the firewall to indicate to the new Exchange server at this betoken, and the HTTP access for OWA, Outlook Anywhere,  and Phone/Tablet admission

Commutation 2022 Mailbox Migration

Yeah you tin practice this in the EAC, but I adopt to practise this in PowerShell. But If I don't put this here, I'll get emails! Recipients > Migration  > Add > Movement to a unlike Database > Add together in the mailboxes/users > Next.

Give the 'Batch' a name > Select to motility Archive mailboxes (if you have them) > Select the destination (Exchange 2022) Database > Again if using archive mailboxes, select the target archive mailbox database > Set the bad Item limit to 99 > Next > Select Automatically Start > Select Automatically Finish > New.

From this point, this is where I don't similar the EAC it takes AGES to update with progress! From the Exchange Shell you can go an upwardly to appointment view of that is going on!

Get-MoveRequest | Go-MoveRequestStatistics

For a better listing of commands for moving user mailboxes, and monitoring the migration, and removing the movement requests when you are finished, see the following article;

Exchange: PowerShell Commands

Migrating Exchange System Mailboxes

Before y'all start issue the following command;

Set-AdServerSettings -ViewEntireForest $truthful

In addition to the user mailboxes there are a multitude of different 'System mailboxes' that might be hanging around, before we can go rid of the Exchange 2022 Database we need to migrate those.

Firstly AuditLog Mailboxes

Get-Mailbox -AuditLog -Database "Mailbox-Database-2016"

If there are any!

Become-Mailbox -AuditLog -Database "Mailbox-Database-2016" | New-MoveRequest -TargetDatabase "Mailbox-Database-2019"

And then Arbitration Mailboxes

Get-Mailbox -AuditLog -Database "Mailbox-Database-2016" -Arbitration

If at that place are any!

Get-Mailbox -AuditLog -Database "Mailbox-Database-2016" -Mediation | New-MoveRequest -TargetDatabase "Mailbox-Database-2019"

Then Monitoring Mailboxes

Get-Mailbox -Monitoring -Server "Mail-2016"

If in that location are any!

Get-Mailbox -Monitoring -Server "Post-2016" | New-MoveRequest -TargetDatabase "Mailbox-Database-2019"

Brand sure in that location are no archive mailboxes;

Get-Mailbox -Auditlog -Database "Database-Name" -Archive

If in that location are, move them, (as to a higher place.)

Also motility any  Discovery mailboxes, and move them to 2022;

Go-Mailbox DiscoverySearchMailbox* | New-MoveRequest -TargetDatabase "Mailbox-Database-2019"

Migrating Public Folders

Call up later Exchange 2022 these are just mailboxes! you tin can movement them like any other mailbox 🙂

Delete Substitution 2022 Database(south)

When you are 100% sure theres nothing left on the old database(due south) remove them;

Get-MailboxDatabase -Identity "Mailbox-Database-2016" | Remove-MailboxDatabase

Uninstall Exchange 2022

Your install directory may not be on the C: drive so modify your path appropriately;

cd "C:\Programme Files\Microsoft\Exchange Server\V15\Bin

setup.exe /mode:uninstall

At this point make sure your backup/replication software is pointed to the new Exchange 2022 Server.

Annotation: If yous are running an On-Premise Exchange in Hybrid fashion, and post migration if yous have whatever mail flow problems run across the post-obit article;

No Post Period On-Premise To/From Office 365

Related Articles, References, Credits, or External Links

NA

Source: https://www.petenetlive.com/kb/article/0001472

Posted by: herrmannquism1987.blogspot.com

Share this post