Swap the primay SMTP address from old domain to new one in Office365 with ADD Connect

Hello everyone,
I worked with this method several times and it is very useful and efficient when your customer in Office365 and you have AAD Connect in place and they want to change their primary domain with a new one say, the old one is cats.com to dogs.com and you need to deal with a lot of number of mailboxes, the steps are:

1. In the Office365 and from the Active Users screen export the users to .csv
2. Clean the sheet and leave the UPN and the Primary SMTP Address columns.
3. Clean the UPN column by removing everything after the @. 
4. Add the new email addresses in another column to the sheet.
5. Change the heading in the sheet for the UPN to username for old smtp to OldEmail and for the new smtp NewEmail.
6. Save the file as users.csv and copy it to the DC.
7. Stop the AAD Connect from services till you finish all the process.
8. Remove the old primary SMTP email address run the following:
   import-csv C:\temp\users.csv | foreach ({Set-ADUser -identity $_.Username -Remove @{proxyAddresses = "SMTP:"+($_.OldEmail)}})
9. To add the new primary SMTP
   import-csv C:\temp\users.csv | foreach ({Set-ADUser -identity $_.Username -Add @{proxyAddresses = "SMTP:"+($_.NewEmail)}})
10. To add the old primary as a secondary SMTP
    import-csv C:\temp\usesr.csv | foreach ({Set-ADUser -identity $_.Username -Add @{proxyAddresses = "smtp:"+($_.OldEmail)}})
11. To check the changes:
    import-csv C:\temp\users.csv | foreach ({Get-ADUser -identity $_.Username -Properties *})| fl DisplayName,proxyaddresses
12. After everything changed as you wish, start the AAD Connect services and watch the magic!

Exchange 2013 - Use the Recovery Database to Restore Mailbox or Inbox Rules

 

Pre requisites

Access to a healthy backup.

Name of the mailbox(es) you want to recover example: ITSupport

Create a temp user with mailbox (IT2)

Access to the exchange server.

 

Procedures and steps

 

1-    Check you have enough space to accommodate the exchange database file that you will copy from the backup

2-    Copy the edb file from the backup and the log files to a folder called Recovery and the logs to a sub-folder Logs

3-    Start the EMS and run

eseutil /mh <the .edb file>

the status will show Dirty Shutdown.

4-    Run the following command to bring the database to clean shutdown state,

eseutil /R Exx /l G:\Recovery\Logs /d G:\Recovery

5-    Create the recovery database

New-MailboxDatabase –Recovery –Name RDB1 –Server <ExchangeServerName> -Edbfilepath G:\Recovery\<the.edb file> -LogFolderPath G:\Recovery\Logs

Restart-Service MSExchangeIS

6-    Mount the database

Mount-Database RDB1

7-    Verify that the mounted database contains the mailbox(es) you want to restore

Get-MailboxStatistics –Database RDB1 | Ft –auto

8-    Start the recovery process

New-MailboxRestoreRequest –SourceDatabase RDB1 –SourceStoreMailbox “ITSupport” –TargetMailbox IT2 –BadItemsLimit 10

9-    You can use the following to monitor the restore process

Get-MailboxRestoreRequest

Get-MailboxRestoreRequest | Get-MailboxRestoreRequestStatistics -IncludeReport |Format-List > C:\AllRestoreReports.txt

 

 

10- Once the restore has a status Completed run

Get-MailboxRestoreRequest –Status Completed | Remove-MailboxRestoreRequest

11- Now you can access the mailbox from your Outlook and you can restore or export any item you want include Inbox Rules just make sure there are no errors in the rules (red text) before you can export it to a file and select the server side when you access the rules.

12- When you finish clean what you did unless you deal with a lot of recovery issues like this. You can remove the Recovery database

Remove-MailboxDatabase –Id RDB1

13- Delete recovery folder and all of its contents.

Exchange Server Updates: build numbers and release dates

Product name	Release date	Build number
Exchange Server 2013 CU5	May 27, 2014	15.00.0913.022
Exchange Server 2013 SP1	February 25, 2014	15.00.0847.032
Exchange Server 2013 CU3	November 25, 2013	15.00.0775.038
Exchange Server 2013 CU2	July 9, 2013	15.00.0712.024
Exchange Server 2013 CU1	April 2, 2013	15.00.0620.029
Release to Manufacturing (RTM) version of Exchange Server 2013	December 3, 2012	15.00.0516.032
Update Rollup 6 for Exchange Server 2010 SP3	May 27, 2014	14.03.0195.001
Update Rollup 5 for Exchange Server 2010 SP3	February 24, 2014	14.03.0181.006
Update Rollup 4 for Exchange Server 2010 SP3	December 9, 2013	14.03.0174.001
Update Rollup 3 for Exchange Server 2010 SP3	November 25, 2013	14.03.0169.001
Update Rollup 2 for Exchange Server 2010 SP3	August 8, 2013	14.03.0158.001
Update Rollup 1 for Exchange Server 2010 SP3	May 29, 2013	14.03.0146.000
Exchange Server 2010 SP3	February 12, 2013	14.03.0123.004
Update Rollup 13 for Exchange Server 2007 SP3	February 24, 2014	08.03.0348.002
Update Rollup 12 for Exchange Server 2007 SP3	December 9, 2013	08.03.0342.004
Update Rollup 11 for Exchange Server 2007 SP3	August 13, 2013	08.03.0327.001
Update Rollup 10 for Exchange Server 2007 SP3	February 11, 2013	08.03.0298.003
Update Rollup 9 for Exchange Server 2007 SP3	December 10, 2012	08.03.0297.002
Update Rollup 8-v3 for Exchange Server 2007 SP3	November 13, 2012	08.03.0279.006
Update Rollup 8–v2 for Exchange Server 2007 SP3	October 9, 2012	08.03.0279.005
Update Rollup 8 for Exchange Server 2007 SP3	August 13, 2012	08.03.0279.003
Update Rollup 7 for Exchange Server 2007 SP3	April 16, 2012	08.03.0264.000
Update Rollup 6 for Exchange Server 2007 SP3	January 26, 2012	8.03.0245.002
Update Rollup 5 for Exchange Server 2007 SP3	September 21, 2011	8.03.0213.001
Update Rollup 4 for Exchange Server 2007 SP3	May 28, 2011	8.03.0192.001
Update Rollup 3-v2 for Exchange Server 2007 SP3	March 30, 2011	8.03.0159.002
Update Rollup 2 for Exchange Server 2007 SP3	December 10, 2010	8.03.0137.003
Update Rollup 1 for Exchange Server 2007 SP3	September 9, 2010	8.03.0106.002
Exchange Server 2007 SP3	June 7, 2010	8.03.0083.006

Points to remember when you want to remove SBS 2008

After you installed a new DC and they are replicating perfect with SBS then you need to do the following:

1. Move the Data, printers and shares
2. Change the port forwarding in the FW.
3. Change the DNS and DHCP to point to the new domain
4. Remove Exchange 2007
5. Remove the CA role.
6. Move the FSMO roles manually. the Schema is most tricky one of them. usually wait for 15 mins before you attempt to move it and do it from the SBS server.
7. Dcpromo the server and if there is an error to remove the delegation record from the DNS, don't worry this will not stop the dcpromo.
8. After the server restarted, clean the DNS and Site from the SBS.
9. The remove the SBS server from the domain and then shut it down.
10. Restart the other DC.

Preparation before you install Exchange 2013 in existing organisation

1. There are only two roles now for Exchange 2013, CAS and MBX. You can only install Exchange 2013 with CU1 or later.
2. If you will use the legacy method, configure second internet ip to point to an A record called legacy. In the FW point both ip addresses to the old exchange server. 
3. Upgrade all the existence exchange servers to the latest sp3 and rollup. You can’t upgrade from exchange 2003.
4. Supported Clients:

• Outlook 2013 (15.0.4420.1017)
• Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 update (14.0.6126.5000). For more information, see Description of the Outlook 2010 update: November 13, 2012. 
• Outlook 2007 Service Pack 3 with the Outlook 2007 November 2012 update (12.0.6665.5000). For more information, see Description of the Outlook 2007 update: November 13, 2012. 
• Entourage 2008 for Mac, Web Services Edition
• Outlook for Mac 2011

5- Hardware needs to be 64bit processors, Xeon is the preferred with 8GB memory will be a good start.
6- The supported OS is either 2008 R2 sp1 or 2012
7- In a multi-server scenario these are the requirements:
• Schemma is windows 2003 sp2
• Domain Function level can be 2003
• Forest level is 2003
• DNS is a Multi-label DNS online.local
8- Additional Components:
• .NET Framework 4.5
• Internet Information Services (IIS)
• Windows PowerShell V3.0 you can use Get-Host to determine the version
• Windows Management Framework V3.0
9- Two versions of CAL for Exchange, Standard and Enterprise.. The Enterprise CAL allows for the use of unified messaging, advanced compliance capabilities and antivirus / anti-spam facilities.
10- To use the advance features in Exchange 2013 like UM voice message to email and auto-archiving you need the Client Standard license plus the Enterprise one.
11- Sales bought SSL certificate with a multi-domains capability.
12- Ensure the RPC-Over-HTTP service installed as well.
13- Change WinRM services to automatic and type the following command in PowerShell:
Enable-PSRemoting -Force
14- To do the prerequisites
For the Windows 2012

• Install-WindowsFeature AS-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-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
• Install-WindowsFeature RSAT-ADDS

For 2008 R2 use the following:
a- Import-module ServerManager
b- Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

15- On servers that will host the CAS or Mailbox server role, install the Microsoft Filter Pack. Download and install the following:
• Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
• Microsoft Office 2010 Filter Pack 64 bit
• Microsoft Office 2010 Filter Pack SP1 64 bit

16- Make sure the server is up to date in securities
17- Setup will do these commands but in multi-server installation it will be preferred to run them manually so you can assess the reaction of each one. Run these commands to upgrade the Schema setup.com /PrepareSchema, Domain setup.com /PrepareAD,

How to Setup and configure the Legacy option with EXCH07

1-      Pre-requisties: 

§  Second internet IP address and point it to an A record called legacy.

§  Access to the internal and external DNS service.

2-       In the FW point both ip addresses mail and legacy to the old exchange server.

3-      Create the SSL certificate and include the legacy.internetdomainname as one of the Subject Alternative Name. Install the certificate in the new exchange2010

4-      Make sure the RPCoverHTTP server component is installed in the 2010

5-      Configure OWA and Outlook Anywhere as well.

6-      Move the OAB and enable web distribution

7-      After the certificate is ready, install it in the Exchange 2010

8-      Export the certificate to a file

9-      There may be a small outage of service till you make the 2007 work with the 2010 so, inform the admin or your contact.

10-   Import the certificate to the Exchange 2007

11-   This is needs to be done in the 2007 HUB server

Disable-OutlookAnywhere –Server EXCH2007

12-   All the below needs to be done in the 2007 CAS

Set-OWAVirtualDirectory –Id EXCH07\OWA*
-ExternalURL https://legacy.company.co.uk/owa

Set-OABVirtualDirectory –Id EXCH2007\OAB*
-ExternalURL https://legacy.company.co.uk /OAB

Set-UMVirtualDirectory –Id EXCH2007\Unified*
-ExternalURL https://legacy.company.co.uk /UnifiedMessaging/Service.asmx

Set-WebServicesVirtualDirectory –Id EXCH2007\EWS* -ExternalURL https://legacy.company.co.uk /ews/exchange.asmx

Set-ActiveSyncVirtualDirectory –Id EXCH2007\Microsoft* -ExternalURL https://legacy.company.co.uk /Microsoft-Server-ActiveSync

13-   Configure the legacy in the internal DNS to point to the Exchange 2007 and mail and autodiscover to point to the Exchange 2010 if exist in the internal DNS.

14-   Configure the FW to point the old IP address to the new Exchange 2010

15-   Move one of the test mailbox and test OL Anywhere, webmail and mobile.

16-   Test it as well with a mailbox in the 2007 server.