The following steps describe how to configure an Exchange service group using the Exchange Configuration Wizard.
To configure an Exchange service group
The wizard starts validating your configuration. Various messages indicate the validation status.
An informational message appears if you chose to configure a SnapMirror resource without configuring replication between NetApp filers at primary and secondary sites. Review the message and click Yes to continue. You must always click Yes if you encounter this message while configuring a service group at the secondary site.
Do the following:
Verify the Exchange Virtual Server name.
Click Advanced if you wish to configure the Lanman agent to perform Windows Active Directory updates. These settings are applicable to the Lanman resource in the service group.
On the Lanman Advanced Configuration dialog box, complete the following:
In the Organizational Unit field, type the distinguished name of the Organizational Unit for the virtual server in the format CN=containername,DC=domainname,DC=com. To browse for an OU, click the ellipsis (...) button and search for the OU using the Windows Find Organization Units dialog box. By default, the Lanman resource adds the virtual server to the default container "Computers."
Click OK. The user account for VCS Helper service must have adequate privileges on the specified container to create and update computer accounts.
Check the Configure NetApp SnapMirror Resource(s) check box if you want to configure a NetApp SnapMirror resource. SnapMirror resource is required only in case of a disaster recovery configuration.
If you are running the wizard to modify a service group, unchecking this check box will remove the NetApp SnapMirror resource from the service group configuration
Verify the Exchange Database Path.
Verify the Transaction Log Path.
To configure Detail Monitoring for Exchange databases, click Configure.
On the Detail Monitoring Configuration dialog box, complete the following:
In the Available Databases box, select the databases for detail monitoring and double-click, or click the right-arrow button to move them to the Selected Databases box. To remove a database, select the database in the Selected Databases box, and double-click or click the left-arrow button.
Check Enable detail monitoring check box, and specify the monitoring interval in the Detail monitoring interval field.
If you want the VCS agent to fault the service group if a database selected for detail monitoring is dismounted, check the Fault service group if any of the selected database is dismounted check box.
See the VCS agent attribute descriptions in the Appendix, for more information on detail monitoring and VCS agent behavior.
Click OK.
To configure additional storage, click Configure.
On the Additional Storage Configuration dialog box, complete the following:
In the Available Volumes box, select a volume that you wish to add and click the right-arrow button to move the volume to the Selected Volumes box.
To remove a volume, select the volume in the Selected Volumes box, and click the left-arrow button.
Click OK. The wizard will configure resources required for the additional storage as child resources of the Microsoft Exchange System Attendant (MSExchangeSA) service resource.
Click Next.
Each optional service that is selected will be configured as a VCS resource of type ExchService2007.
If you are configuring MPIO over FC, you must select at least two FC initiators for each cluster node. Note that the node from which you run this wizard already has an initiator selected by default. This is the initiator that was specified when you connected the LUNs to this cluster node.
Do the following:
For IPv4 networks, the IP Address details displayed are the values entered while installing Exchange. You can keep the displayed values or enter new values.
Select IPv4 and then enter a unique IP address and its associated subnet mask. Ensure that the IP address is currently not being used on your network, but is in the same subnet as the current node.
If you change the virtual IP address, create a static entry in the DNS server mapping the new virtual IP address to the virtual server name. Ensure that the IP address is currently not being used on your network, but is in the same subnet as the current node.
For IPv6 networks, select IPv6 and then select the IPv6 network from the drop-down list. The wizard uses the network prefix and automatically generates a unique IPv6 address that is valid on the network.
The IPv6 option is disabled if the network does not support IPv6.
If you select another network, create a static entry in the DNS server mapping the new IPv6 address created by the wizard to the virtual server name.
For each system in the cluster, select the public network adapter name. Select the Adapter Display Name field to view the adapters associated with a node.
The wizard displays all TCP/IP enabled adapters on a system, including the private network adapters, if they are TCP/IP enabled. Make sure that you select the adapters to be assigned to the public network.
Note: |
If you have a tagged VLAN network configuration having multiple logical network interfaces or a teamed network interface that have the same MAC address, then you must edit the "MACAddress" attribute of the NIC agent and the IP agent, after you configure the application service group. See About the modifications required for tagged VLAN or teamed network. |
The Resources box lists the configured resources. Click a resource to view its attributes and their configured values in the Attributes box.
The wizard assigns unique names to resources. To edit a resource name, select the resource, click the resource or press the F2 key. Edit the resource, and press the Enter key to confirm the changes. To cancel editing a resource name, press the Esc key.
After bringing the service group online, run the Exchange Management Console to modify the database settings such that all the stores are automatically mounted on start-up.
If you need to configure additional storage groups or mailbox stores, you should do that now.
Perform the following tasks in the order given:
Create the new storage groups and mailbox stores.
Mount or connect the volumes or LUNs that have been created for the additional storage groups or mailbox stores.
You cannot move the Exchange database to the shared storage, using the Exchange Management Console. Move the new storage groups and mailbox stores on the shared storage using either of the following ways:
Run the Exchange Configuration Wizard to bring the new storage groups and mailbox stores under VCS control.
You do not need to run the wizard if you already designated the additional volumes or LUNs when you ran the configuration wizard the first time while installing and configuring Exchange.
Using the Java Console, bring the Exchange service group offline.
Open the registry key "HKLM\System\CurrentControlSet\Services\MSExchangeSA\Parameters" and create a registry string value "OAB Folder Location".
Set the value of "OAB Folder Location" to some path on the shared volume. The Offline Address Book gets created at this location.
Configure the storage resources for the Offline Address Book.
Create the resouce dependency such that the System Attendant resource depends on the storage resources created in the above step.
Navigate to "%ProgramFiles%\Microsoft\Exchange Server" and remove the "ExchangeOAB" share, if it already exists. Perform this task on each of the cluster node.
Bring the Exchange service group online.