Server: Windows 2003 with sp1 or later

Windows 2000 native mode or later

Windows 2000 native or later --Forest functional level

Active Directory Site

In Active Directory, a site is a set of computers well-connected by a high-speed network, such as a local area network (LAN). All computers within the same site typically reside in the same building, or on the same campus network. A single site consists of one or more Internet Protocol (IP) subnets.

• Replication
• Client authentication

GC--Finding object

When you search for people or printers from the Start menu or choose the Entire Directory option within a query, you are searching a global catalog. Once you enter your search request, it is routed to the default global catalog port 3268 and sent to a global catalog for resolution.

Test
Uncheck “Global Catalog” for your forest.
The following error occurs when you create an account.

In a single-domain forest, configure all domain controllers as global catalog servers. Because every domain controller stores the only domain directory partition in the forest, configuring each domain controller as a global catalog server does not require any additional disk space usage, CPU usage, or replication traffic. In a single-domain forest, all domain controllers act as virtual global catalog servers; that is, they can all respond to any authentication or service request. This special condition for single-domain forests is by design. Authentication requests do not require contacting a global catalog server as they do when there are multiple domains, and a user can be a member of a universal group that exists in a different domain. However, only domain controllers that are designated as global catalog servers can respond to global catalog queries on the global catalog port 3268. To simplify administration in this scenario and to ensure consistent responses, designating all domain controllers as global catalog servers eliminates the concern about which domain controllers can respond to global catalog queries. Specifically, any time a user uses Start\Search\For People or Find Printers or expands Universal Groups, these requests go only to the global catalog.

setup /?

Welcome to Microsoft Exchange Server 2007 Setup Help
Please type one of the below options for detailed help on each subject:

Setup.com /help:Install         - Installing Exchange Server roles.
Setup.com /help:Uninstall       - Uninstalling Exchange Server roles.
Setup.com /help:Upgrade         - Upgrading Exchange Server roles.
Setup.com /help:RecoverServer   - Recovering an existing Exchange Server.
Setup.com /help:PrepareTopology - Preparing your topology for Exchange.
Setup.com /help:Cluster         - Installing Exchange on Clusters.
Setup.com /help:Delegation      - Delegated server installations.
Setup.com /help:UmLanguagePacks - Adding/removing UM language packs.

setup /help:PrepareTopology

Setup.com /PrepareAD [/DomainController:<FQDN of DC>]
Setup.com /PrepareSchema [/DomainController:<FQDN of DC>]
Setup.com /PrepareDomain [/DomainController:<FQDN of DC>]
Setup.com /PrepareDomain:<domainA,domainB> [/DomainController:<FQDN of DC>]
Setup.com /PrepareAllDomains [/DomainController:<FQDN of DC>]
Setup.com /PrepareLegacyExchangePermissions [/DomainController:<FQDN of DC>]

/PrepareLegacyExchangePermissions, /pl
Prepares the permissions in a legacy forest.
Use this parameter only if you have Exchange 2000 or 2003 servers in your organization.

/PrepareLegacyExchangePermissions:<domain FQDN>, /pl:<domain FQDN>
Prepares the permissions for the specified domain.

/PrepareAD, /p
      Prepares the Active Directory forest for the Exchange installation.
       This will perform all the operations listed below in the local domain.

/PrepareSchema, /ps
Prepares the Active Directory Schema for the Exchange installation.

/PrepareDomain, /pd
Prepares the local domain for the Exchange installation.

/PrepareDomain:<domain FQDN>, /pd:<domain FQDN>
Prepares the specified domain for the Exchange installation.

/PrepareAllDomains, /pad
Prepares all domains in the forest for the Exchange installation.

--Prepare Topology Optional Parameters--

[/DomainController, /dc]
Specifies the domain controller that setup will use to read and write to Active Directory. Netbios or FQDN format can be used.

Domain controller: Paula.work.com
Member server: Ex20071.work.com

Run EXCHANGE Setup from Exchange 2003 machine

setup /p

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

No server roles will be installed

Performing Microsoft Exchange Server Prerequisite Check

    Organization Checks              ......................... FAILED
The Active Directory schema will be upgraded if you continue. Verify that the organization is ready for Exchange 2007 by running the Exchange 2007 Readiness Check, which is part of the Exchange Best Practices Analyzer.
A previous version of Exchange Server is already installed on this computer. Run Exchange 2007 Setup from a different computer or remove the previous version of Exchange Server.

     Active Directory domain 'DC=work,DC=com' is in mixed mode. To install Exchange Server 2007, the domain functional level must be raised to Windows 2000 native mode or above.

     Active Directory root domain 'DC=work,DC=com' is in mixed mode. To install Exchange Server 2007, this domain must be Windows 2000 native mode or above.

From member server, run Exchange 2007 Readiness Check

Download ExBPA.msi and install it.

Link state suppression in not enabled.

Before introducing Exchange Server 2007 into this topology, the “SuppressStateChanges’ configuration parameter should be set to 1 on server PAULA.work.com. This parameter is essential if you plan to create multiple connectors to the dedicated Exchange 2007 routing group.

In the simple environment, it does not matter of SuppressStateChanges.

Regedit

Navigate to HKLM\System\CurrentControlSet\Services\RESvc\Parameters.
Right-click Parameters and select New | DWORD value. Name the new DWORD value SuppressStateChanges and set it to 1.

From the member server:
You could successfully run the SETUP /P.

Install the first Exchange 2007

Enable support for legacy Outlook clients (Outlook 2003 and previous). Essentially, this means that Exchange 2007 will install public folders database, as legacy clients are heavily dependent on public folders.

.NET Framework 2.0 (Net Frame 3.5 installed)
MMC 3.0
Powershell 1.0

If you install a server that supports multiple roles, the installation program will determine the order that it installs the roles. However, if you install a single-role server and then decide to install other roles on that server, the suggested order to do this is Client Access Server, Hub Transport, and Mailbox followed by Unified Messaging if required.

Exchange 2007 Intelligence

Warning:
Setup cannot detect an SMTP or Send connector with an address space of “*”. Mail flow to the Internet may not work properly.

What does the warning (if Outlook Web Access is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step should be performed once Setup completes) mean? see below!!!

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

SystemPages:0

Warning:
If Outlook Web Access is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step should be performed once Setup completes.

You can create the legacy mailbox in Exchange 2007 store.

Create two user accounts in AD: Paul2007 and Tom2007 without mailboxes created.

Exchange Management Console

You cannot create Exchange 2007 mailboxes in Exchange 2003 store.

'work.com/Paul2007' | Enable-Mailbox –Database 'Ex20071\First Storage Group\Mailbox Database'

Create outlook profiles;

Open Administrator’s profile;

From outlook, paul user can view the Company Calendar.

Same for Paul2007 user;

Please give 5 minutes or more time to replicate the new Calendar Item.

Paul can access the Company calendar from OWA.
HTTP://Paula.work.com/exchange

However, Paul2007 will get the following:

How to configure the replication of the Free/Busy folder?

Wait for 15 minutes or more.

Warning:
Setup cannot detect an SMTP or Send connector with an address space of “*”. Mail flow to the Internet may not work properly.

If your network is as follows:

Mailbox users of Exchange 2003 can send mail to INTERNET. But mailbox users of Exchange 2007 server cannot send mail to INTERNT.

Only Exchange SMTP virtual server connects directly to Internet.

Don't set the Internet Connector as the following:

Exchange 2003 SMTP virtual server relay configuration:

This configuration will have a problem: if the SMTP virtual server fails, all undelivered mail will send to Exchange 2007—looping will be detected.

It’s better to “Use domain name system (DNS) MX records to route mail automatically”. Ex2007 server should have a direct connection to Internet.

New Organization installation

With the simple domain environment, you directly run the SETUP program. It will automatically run /PrepareSchema /PrepareAD, etc.

Test of installation failure:

During Transport role installation, I shut down the computer and restart the system and re-run the setup.

The Transport role is installed successfully.

Understanding Setup /M:RecoverServer

Setup /m:RecoverServer The Exchange files and services are then installed on the server, and the roles and settings that were stored in Active Directory are then applied to the server. It is only for recovering a server that was once fully functional, or to move a server to new hardware and maintain the same name.

Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can be recovered only on Windows Server 2008.

Exchange 2007 organization has two servers: Ex64 and EXA. EXA hosts 3 storage groups.

$password=read-host "Enter password please!" –asSecureString

$firstName="Chris"
$lastName="Dion"
$company="No Name"
New-Mailbox -Name "$firstName $lastName" -Alias "$firstName.$lastName" -OrganizationalUnit 'east.com/users' -UserPrincipalName "$firstName.$lastName@east.com" -SamAccountName "$firstName.$lastName" -FirstName $firstName -Initials '' -LastName $lastName -Password $password -Database 'EXA\First Storage Group\Mailbox Database'

$firstName="Samad"
$lastName="Torres"
$company="Telus"
New-Mailbox -Name "$firstName $lastName" -Alias "$firstName.$lastName" -OrganizationalUnit 'east.com/users' -UserPrincipalName "$firstName.$lastName@east.com" -SamAccountName "$firstName.$lastName" -FirstName $firstName -Initials '' -LastName $lastName -Password $password -Database 'EXA\Telus Group\TelusData'

$firstName="Rafael"
$lastName="Ramas"
$company="Shaw"
New-Mailbox -Name "$firstName $lastName" -Alias "$firstName.$lastName" -OrganizationalUnit 'east.com/users' -UserPrincipalName "$firstName.$lastName@east.com" -SamAccountName "$firstName.$lastName" -FirstName $firstName -Initials '' -LastName $lastName -Password $password -Database 'EXA\Shaw Group\ShawData'

Backup the databases:

Assuming the EXA server is crashed. You must build a new system to replace it.

After the new machine joins the domain with the same name: EXA, run Exchange 2007 setup with /m:RecoverServer option.

Restore data from backup.

Check the databases and their mailboxes for messages. All there.

Uninstall Exchange 2007 server

SETUP  /mode:uninstall

To uninstall Exchange 2007 from Server EXA;

Remove all mailboxes hosted on Server EXA:

[PS] C:\>get-mailbox | where {$_.Servername -eq 'Exa'} | fl Name,servername

Name       : FirstTam
ServerName : exa

Name       : TelusTam
ServerName : exa

Name       : ShawTam
ServerName : exa

Name       : Chris Dion
ServerName : exa

Name       : Samad Torres
ServerName : exa

Name       : Rafael Ramas
ServerName : exa

Move them to EX64 server

get-mailbox | where {$_.Servername -eq 'Exa'} | move-mailbox -TargetDatabase 'EX64\First Storage Group\Mailbox Database'

Remove the last Exchange 2007 server:

setup /help:Delegation

Server Setup Delegation Usage:
Setup.com /NewProvisionedServer:<ServerName> [/ServerAdmin:<Server Admin Group Name>]
Setup.com /RemoveProvisionedServer:<ServerName>

The Enterprise Administrator has installed the Exchange 2007 SP1 on both Ex20071 and Ex20072 member servers. He will delegate the user: Saigon to install the Exchange 2007 SP1 onto Ex20073 member, which is located in Burnaby Site.

Saigon is a member of local administrators group of EX20073 server.

Delegation:

setup.com /NewProvisionedServer:EX20073.WORK.COM /ServerAdmin:work\Saigon

Remove the delegation:

setup.com /RemoveProvisionedServer:EX20073.WORK.COM

Home