EXchange 2007 Install and Configure Notes

September 29, 2008

Migration from NT to Windows 2003 and Exchange from 5.5 to 2003

Filed under: EXchange, Migration, Windows — Preetam @ 5:59 pm

Event Review: Migrating from Windows NT Server 4.0 to Windows Server 2003 (Session ITPROADD-02)

 

Event Review: Upgrading from Exchange Server 5.5 to Exchange Server 2003 (Session ITPROEXC-02)

Advertisements

October 8, 2007

NEW THINGS AND JUST DISCOVERED THINGS

Filed under: EXchange, Installation, Migration — Preetam @ 6:22 pm

One database per storage group is design requirement of CCR.

/PrepareLegacyExchangepermission

Use this parameter only if you have servers that are running Exchange 2000 Server or Exchange

server 2003 in your organization

If you move mailbox using either EMC or EMS log file is created under C:\Program Files\Microsoft\Exchange Server\Logging\MigrationLogs

Exchange 2007 Mailbox cannot be modified using ADUC, there are not extended in ADUC

Active-Active cluster is no longer supported

Single copy cluster is available in enterprise edition

Also CCR is not available in Standard edition

At registry level you can check what roles are installed on the exchange server by parsing to hklm/software/Microsoft/exchange/v8.0

October 5, 2007

Exchange 2007 Notes 4th Oct 2007

Filed under: EXchange, Migration — Preetam @ 10:20 am

Memory Requirement:512 megabytes is the recommended minimum for any exchange role.

Software requirement: All server running exchange 2007 must also be running on windows 2003 SP1 or above 64-bit editions.

Upgradations:If you are planning to upgrade your DC and GC servers it would make sense to implement them on 64bit hardware, as any organization whose AD database is in excess of 3GB will see significant improvement in performance from exchange perspective.

For example one 64 Bit dual core Global Catalog server with 14 GB RAM can handled work load of 11 32-bit equivalent GC servers and so support 20000 mailboxes.

Client requirement: Outlook anywhere (RPC over HTTPS) will require outlook 2003.

If you do have legacy clients in use, specifying this in the installation process on the server enables things like public folders – which are not required for Outlook 2007 because in Outlook 2007 this is handled by web services for outlook 2007clients . Specifically, calendaring for Outlook 2003 requires some system folders, which are special public folders, to support the publishing of free/busy schedule information – which in turn allows users to create appointments with one another

Mixed Environment: CAS provides links to the back end servers when accessing mailbox using OWA. However OWA experience will differ based on what is the backend server version is. To experience OWA 2007 both front end and backend servers should be Exchange 2007.

Installation from cmd Prompt:Select H for Hub Transport, C for Client Access, E for Edge Transport, M for Mailbox or U for Unified Messaging. You can also install only the management tools by using the option T for your server role

Prepare Ad & Prepare Schema:Note that the difference is that prepare schema only modifies the schema in preparation for installation. It does not create the necessary security groups in the forest root required to deploy Exchange Server. If you run prepare AD without having previously prepared the schema, the installation routine will prepare the schema at the same time as it prepares Active Directory. In both cases, you must be in the same site and same domain at the schema operations master to run setup with these switches.To prepare active directory for exchange installation, requires Schema and domain admin permissions.

Mailbox Migrations:Note that you cannot use the Exchange Server 2003 Move Mailbox Wizard to move mailboxes from Exchange Server 2007 to Exchange Server 200x servers, nor can you use the 200x wizard to move mailboxes from Exchange Server 200x to Exchange 2007 servers

September 15, 2007

Notes on Exchange 2007 15-09-2007

Filed under: EXchange, Migration — Preetam @ 2:12 pm

What type of AD topology allows you to separate the administration of Exchange server from that of Active directory ?

== > It is Resource Forest topology, while in case of Cross forest topology you have EXchange in both the forest, so if two organizations have to communicate with each other they should have Edge servers in both the forest.

New administrative roles introduced in EXchange 2007

  1. EXchange Organization Administration
  2. EXchange Server Administration
  3. EXchange recipient Administration
  4. EXchange Read-Only Administration

 

  • You cannot use Exchange system manager to manage EXchange 2007 and vice-versa.
  • EMC: EXchange Management console
  • EMS: EXchange Management Shell

 

Transition Path

In Transition you need to introduce Exchange 2007 server into existing organization and move mailbox from 2000/2003 to 2007.

You can transition from Exchange 2000 and Exchange 2003 to Exchange 2007, provided Exchange organization is in 2000/2003 Native mode. If the organization is in mixed-mode transition path is not possible. When you transition to 2007, make a point to bring in Client Access Server role first, then other roles on the same lines are front-end must be upgraded first, then back-end.

Migration

You can migrate from Exchange 5.5 to Exchange 2007 however in this case you have to create new organization and put Exchange 2007 into that organization. This path has lots of challenges compare to Transition path, So simple alternative will be to upgrade to Exchange 2003 and then transition to Exchange 2007.

In-place upgrade is not supported and technically many not be possible, since previous of Exchange never came with 64 bits.

Create a free website or blog at WordPress.com.