Friday, June 11, 2010

Microsoft Exchange 2003 migration to Exchange 2010

Waiting to finish up Domain migration...

14 comments:

  1. With Symantec Backup-Exec(ver12.5), restored Microsoft Information Store mailbox to have some data on beta server. We need this to have something to migrate to the new Exchange Server. 1st pass gave me issues due to drive space on c:\temp. Had to redirect exchange server temporary storage logs and patch files.

    ReplyDelete
  2. Installed New Dell with Windows 2008 R2 Operating system. In additional, added to domain member.Ransetup.com /PrepareLegacyExchangePermissions or setup.com /pl command to prep domain. Ran prepairSchema on old WIndows 2003 domain. Install Exchange 2010. No problems so far.

    ReplyDelete
  3. Installed Exchange 2010 x64 with no problems. Still using Exchange 2003 Transport to send out emails. Running post check list on the Exchange Management Console. Getting use to not having 1 centralized location for creating users & mailboxs.

    ReplyDelete
  4. Adding mail enabled servers to "Recieve Connectors" section in Server connection section. We have several software application that send emails. Microsoft Sharepoint, Norton Antivirus, GFI Server Alerts..etc.

    ReplyDelete
  5. Added Custom "Recieve Connector" for internal mailboxs & additonal connector for External clients. Good Way to separate and manage.

    ReplyDelete
  6. Moving mailbox's with "local move request" in Receipt Section of Exchange Managerment Console. Takes about 1 hour per mailbox. Afterwards will need to run Esutil /mh command to check database now that thier data in them.

    ReplyDelete
  7. Having Issues Backing up with Symantec Backup Exec 12.00. Seems thiers an issue with the VSS technology and Symantec Backup Exec. Performing Full Windows Backups locally but need to get Backup Exec working. If I need to restore granular cannot be done write now. Will troubleshoot VSS Windows Backup soon.

    ReplyDelete
  8. Updated Symantec to ver 13. Exchange granduler working fine. Backing up complete storage group and individual ok.

    ReplyDelete
  9. Exchange 2010 producing routing connector error. Coul dbe from previos 2003-2010 migration. Entry was also found on with adsiedit.msc command.

    Process edgetransport.exe () (PID=2688). Configuration object CN=MIA-GEO-EXCH-04-MIA-GEO-EXCH-02,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Geoscape,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=geoscape,DC=com read from mia-geo-gcdc-02.domain.com failed validation and will be excluded from the result set. Set event logging level for Validation category to Expert to get additional events about each failure

    ReplyDelete
  10. Ran Get-RoutingGroupConnector | Remove-RoutingGroupConnector and removed previos connector. Will monitor.

    ReplyDelete
  11. Needed to give 1 person calendar permission to all corporate users. Downloaded Exfolder utility. from http://gallery.technet.microsoft.com/Exchange-2010-RTM-ExFolders-76c3649/file/19079/1/ExFolders-RTM.zip . Need to remember that if you have more than 1 storage you need to select prior connecting.

    ReplyDelete
  12. After migrating mailbox's I ran the Eseutil /mh "path to edb to make sure all databases are in good "Clean Shutdown" state. Rebooted server several times to check status.

    ReplyDelete
  13. Getting: Exchange store Informationxxx is limited to 1024Gb. The current physical size of this database (the .edb) is 3Gb. If the physical size of the database minus its logical free space exceeds the limit of 1024Gb, the database will be dismounted on a regular basis. Only getting this on 1 mailbox store.

    ReplyDelete
    Replies
    1. Ran Get-MailboxDatabase to get name of databases, then ran Get-MailboxDatabase DB1 | fl name, guid to get correct Guid syntax. Afterwards, ran regedit and added DWORD "database Size Limit in GB @ LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeISPrivate

      Delete