Date: 2010-07-15

OS: Windows Server 2003, Windows Server 2008

Etrack Incident: 2070582

Errors/Problems Fixed:[
  Exchange explorer crash while trying to discover Exchange 2007 server (e2070582)
]

Install/Uninstall instructions:
============================================================================

Installing the hotfix
============================================================================

Apply this hotfix on hosts where the CommandCentral 5.1.2 Management Server 
and managed hosts are installed.

Deploying the hotfix from a Windows Management Server
-----------------------------------------------------

The examples in the following procedure assume that you installed 
CommandCentral on a 32-bit host in the default installation directory.

1. Download the hotfix ("ccs-win-5.1.2HF512002070582w.zip") to a temporary location. 
   For example, to C:\\Temp\\

2. Extract the hotfix in the temporary directory.

   When you extract the hotfix, the following contents appear:

   README
   patches\VRTSccs-F512002070582.tar.gz

3. Apply the HotFix
 
   - Open an operating system console.

   - Type the following command to change to the HAL bin directory:
          
     cd C:\\Program Files\\VERITAS\\CommandCentral Storage\\HAL\\bin

   - Type the following command:

     halsecurity login 
        
     You may have to provide the password for the 'admin' account which you 
     use to log in to the Console. The default password for this account is 
     'password' (without single quotes).
   
   - To apply the HotFix on Windows Management Server , type the following command:

     perl LocalUpgrade.pl C:\Temp\patches\VRTSccs-F512002070582.tar.gz

   - To push the HotFix to Windows managed hosts from the Management Server, 
     first get the list of all managed hosts in a text file, by running the
     following command:	
       	
     perl CHMGetManagedHosts.pl -f C:\\Temp\\mhs.txt

     C:\\Temp\\mhs.txt includes the list of all managed hosts.
           
   - Edit mhs.txt to keep the name of only those managed hosts where you want
     to deploy the hotfix.

   - To deploy the hotfix on all hosts listed in C:\\temp\\mhs.txt, run the
     following command:
	
     perl PushUpgrade.pl -u C:\\Temp\\patches\\VRTSccs-F512002070582.tar.gz 
-H C:\Temp\mhs.txt

4. After you deploy the hotfix, you can check the installation logs on relevant 
   managed hosts as follows:

   - To see the detailed logs, go to the CommandCentral Storage Data directory.
     
     The default location is:
        
     C:\\Program Files\\VERITAS\\CommandCentral Storage Data\\Data\\HAL\\maint

     cd <HAL data directory>\\Data\\HAL\\maint\\VRTSccs-F512002070582\\
<time stamp>\\output
     
     For example:

     C:\\Program Files\\VERITAS\\CommandCentral Storage
	 Data\\Data\\HAL\\maint\\VRTSccs-F512002070582\\<time stamp>\\output

   - Check if there are any errors in the stderr.txt file.
     
   - Check the detailed logs of hotfix application in the stdout.txt file.

5. Verify the hotfix version on relevant managed hosts as follows:
     
   - Open the CommandCentral Storage version file.
     
     The default location is:

     C:\\Program Files\\VERITAS\\CommandCentral Storage\\Version\\cc_version.txt

   - Check the FIXID which shows the hotfix number.
      
     For example:

     FIXID=F512002070582
     DATE=Thu Jul 15 08:37:03 2010
     DESCRIPTION=Exchange Explorer hotfix to fix explorer crash while discovering Exchange 2007 server



Deploying the hotfix from a Solaris Management Server
-----------------------------------------------------

The examples in the following procedure assume that you installed 
CommandCentral on a 32-bit host in the default installation directory.

1. Download the hotfix ("ccs-sol_sparc-5.1.2HF512002070582u.tar.gz") to a temporary location.
   For example, to /tmp

2. Extract the hotfix in the temporary directory.

   When you extract the hotfix, the following contents appear:
     
   README
   patches\VRTSccs-F512002070582.tar.gz

3. Apply the HotFix

   - Open an operating system console.

   - Type the following command to change to the HAL bin directory:
          
     cd /opt/VRTSccs/VRTShal/bin

   - Type the following command:

     ./halsecurity login 
        
     You may have to provide the password for the 'admin' account which you 
     use to log in to the Console. The default password for this account is 
     'password' (without single quotes).
  
   - To push the HotFix to Windows managed hosts from the Management Server, 
     first get the list of all managed hosts in a text file, by running the
     following command:	
        	
      ./perl CHMGetManagedHosts.pl -f /tmp/mhs.txt

      /tmp/mhs.txt includes the list of all managed hosts.
	  
   - Edit this file to keep the names of only those managed hosts where you 
     want to deploy the hotfix.

   - To deploy the hotfix on all hosts listed in /tmp/mhs.txt, run the 
     following command:
	
      ./perl PushUpgrade.pl -u /tmp/patches/VRTSccs-F512002070582.tar.gz 
-H /tmp/mhs.txt

4. After you deploy the hotfix, you can check the installation logs on relevant 
   managed hosts as follows:

   - To see the detailed logs, go to the CommandCentral Storage Data directory:
     
     The default location is

     /var/VRTSccs/data/VRTShal/maint/VRTSccs-F512002070582/<time stamp>/output
     
     cd <HAL data directory>/data/VRTShal/maint/VRTSccs-F512002070582/
<time stamp>/output
     
     For example:

   cd /var/VRTSccs/data/VRTShal/maint/VRTSccs-F512002070582/<time stamp>/output

   - Check if there are any errors in the "stderr.txt" file.
     
   - Check the detailed logs of the hotfix application in the "stdout.txt" file.

5. Verify the hotfix version on relevant managed hosts as follows:

   - Open the CommandCentral Storage version file.
       
     The default location is: /opt/VRTS/version/cc_version.txt
       
   - Check the FIXID which shows the hotfix number.
     
     For example:

        FIXID=F512002070582
        DATE=Thu Jul 15 08:37:03 2010
        DESCRIPTION=Exchange Explorer hotfix to fix explorer crash while discovering Exchange 2007 server


Additional Notes: None