VERITAS Storage Foundation (tm) 4.1 and 4.2 HA for Windows Private 277390 - Updated Exchange Enterprise Agent for VERITAS Cluster Server 4.1 and 4.2

Article:TECH36787  |  Created: 2005-01-17  |  Updated: 2006-01-08  |  Article URL http://www.symantec.com/docs/TECH36787
Article Type
Technical Solution


Environment

Issue



VERITAS Storage Foundation (tm) 4.1 and 4.2 HA for Windows Private 277390 - Updated Exchange Enterprise Agent for VERITAS Cluster Server 4.1 and 4.2

Solution



Last revised: 01/17/2005


CONTENTS
--------
1. PRIVATE OVERVIEW
 - Symptoms of the Problems
 - Resolution
2. INSTALLING THE PRIVATE
3. UNINSTALLING THE PRIVATE
4. DISCLAIMER



PRIVATE OVERVIEW
----------------
The VERITAS Storage Foundation HA 4.1 and 4.2 PRIVATE 277390 provides fixes to the Exchange Enterprise Agent (versions 4.1 and 4.2). The VERITAS Incident number for the issue is 277390. These cases originate from customers. This Private is supported on VERITAS Storage Foundation HA 4.1 and 4.2.


Symptoms of the Problems
------------------------

Public folders may not be replicated between clustered and standalone Exchange servers.

Clustered Exchange server fails to authenticate another Exchange server if anonymous access is disabled.

Mailboxes on a clustered Exchange server deploying Exchange 2003 SP1 cannot send Internet emails.

Mail from mailboxes on a clustered Exchange server display "From" address as an  SMTP address.


Resolution
----------

When Exchange services are brought online in a VERITAS Cluster Server (tm) environment, Cluster Server changes the ActiveComputerName of the system to the Exchange virtual server name. However, the Exchange protocol services (SMTPSVC, IMAP4SVC,POP3SVC, RESVC) expect the actual computer name, and hence fail to authenticate the node. The updated Cluster Server Enterprise Agent for Microsoft Exchange fixes this issue.



INSTALLING THE PRIVATE
----------------------
Before installing the Private, make sure all Exchange service groups are offline in the cluster

1. Download the Private patch file to a temporary location on your cluster node

2. Extract the files to a temporary location on your cluster node. See the table below to determine the file you must extract:

      ---------------------------------------------------------------------
     |SFW-HA Version | Operating System | Name of Private File to extract  |
      ---------------------------------------------------------------------
     |   4.1         | Windows 2000     | Private_4_1_0_277390_W2K.zip     |
      ---------------------------------------------------------------------
     |   4.1         | Windows 2003     | Private_4_1_0_277390_W2K3.zip    |
      ---------------------------------------------------------------------
     |   4.2         | Windows 2000     | Private_4_2_0_277390_W2K.zip     |
      ---------------------------------------------------------------------
     |   4.2         | Windows 2003     | Private_4_2_0_277390_W2K3.zip    |
      ---------------------------------------------------------------------
     

3. Make sure the Exchange service group is offline on cluster

4. Make sure the cluster configuration is in read-only mode

5. Stop the VERITAS High Availability engine (HAD) on all cluster nodes. Type the following on the command prompt:
 
C:\> hastop -local -force
 
6. From the command prompt, navigate to the location where you extracted the files and run the batch file. Type the following on the command prompt:

  a. If you are using Storage Foundation HA for Windows 4.1:

C:\<unzip location>> Private_4_1_0_277390.bat /install


    The batch file copies the Private files to the relevant location. The batch file also backs up the necessary files under C:\Documents and Settings\All Users\Application Data\VERITAS\VCS\Private_4_1_0_277390.


  b. If you are using Storage Foundation HA for Windows 4.2:
 
  C:\<unzip location>> Private_4_2_0_277390.bat /install

    The batch file copies the Private files to the relevant location. The batch file also backs up the necessary files under C:\Documents and Settings\All Users\Application Data\
    VERITAS\VCS\Private_4_2_0_277390.


7. Start the VERITAS High Availability Engine (HAD) on all cluster nodes. Type the following on the command prompt:
C:\> hastart

8. Repeat these steps on all cluster nodes configured to host the Exchange service groups

After installing the Private on all relevant nodes, bring all the Exchange service groups online in the cluster



UNINSTALLING THE PRIVATE
------------------------
Before uninstalling the Private, make sure the all the Exchange service groups are offline in the cluster

1. Make sure the cluster configuration is in read-only mode

2. Stop VERITAS High Availability Engine (HAD) on all cluster nodes. Type the following on the command prompt:

C:\> hastop -local -force

3. Stop the IISAdmin service

4. From the command prompt:

  a. If you are using Storage Foundation HA for Windows 4.1 navigate to:
 
  C:\Documents and Settings\All Users\Application Data\VERITAS\VCS\Private_4_1_0_277390
 
    and run the batch file. Type the following on the command prompt:

C:\<backup location>> Private_4_1_0_277390.bat /uninstall


  b. If you are using Storage Foundation HA for Windows 4.2 navigate to:

C:\Documents and Settings\All Users\Application Data\VERITAS\VCS\Private_4_2_0_277390

     and run the batch file. Type the following on the command prompt:

C:\<backup location>> Private_4_2_0_277390.bat /uninstall
 
 
 Note: The batch file restores the files from the backed up location.

5. Start the IISAdmin service

6. Start the VERITAS High Availability Engine (HAD) on all cluster nodes. Type the following on the command prompt:

C:\> hastart

7. Perform these steps on all cluster nodes where the Private was installed

After uninstalling the Private from all relevant nodes, bring all the Exchange service groups online in the cluster



DISCLAIMER
----------
This Private is a supported fix that has not been fully regression tested and must be applied only to systems that are severely affected by the problem. For other situations, we recommend that you wait for the next service pack that will contain this fix.

Should you have further questions, please contact VERITAS Technical Support.




Attachments

Patch_277390_274478.EXE (1.1 MBytes)

Supplemental Materials

SourceiTools
Value277390

Legacy ID



274478


Article URL http://www.symantec.com/docs/TECH36787


Terms of use for this information are found in Legal Notices