Date:   June 27, 2002

Patch:  3.7-DAD-0001

Component: Distributed Monitoring for Active Directory

Description:
 This patch fixes the problems described hereafter.


Database Changes: 
 The following modified resource models are installed:

 TMW_DCs_Avail
 TMW_DCs_Perf
 TMW_IntraSite_Repl
 TMW_IntraSite_ReplTraff
 TMW_InterSite_Repl
 TMW_InterSite_ReplTraff
 TMW_ReplPerf
 TMW_FRSPerformance
 TMW_DNSPerformance
 TMW_DNS_ADIntegrated


Files replaced or added by this patch (for one or more of the 
 supported platforms):

 lcf_bundle/Tmw2k/Rm/TMW_DCs_Avail.tar
 lcf_bundle/Tmw2k/Rm/TMW_DCs_Perf.tar
 lcf_bundle/Tmw2k/Rm/TMW_IntraSite_Repl.tar
 lcf_bundle/Tmw2k/Rm/TMW_IntraSite_ReplTraff.tar
 lcf_bundle/Tmw2k/Rm/TMW_InterSite_Repl.tar
 lcf_bundle/Tmw2k/Rm/TMW_InterSite_ReplTraff.tar
 lcf_bundle/Tmw2k/Rm/TMW_ReplPerf.tar
 lcf_bundle/Tmw2k/Rm/TMW_FRSPerformance.tar
 lcf_bundle/Tmw2k/Rm/TMW_DNSPerformance.tar
 lcf_bundle/Tmw2k/Rm/TMW_DNS_ADIntegrated.tar
 
Problems Fixed:

      APAR: IY32073
      Symptom: Some resource models do not run when Windows 2000 french 
               version is installed

      Note: The "InterSite Replication Traffic" resource model should 
            be distributed on Bridgehead servers. If they are unknown, 
            the customer can distribute it to all
            the domain controllers

      APAR: IY25803
      Symptom: The "File Replication Service performance" resource model 
                    fails if the sysvol is placed on a drive different 
                    from c:

      APAR: IY29338
      Symptom: Error on a Sendevent call on the "DNS Performance" 
               resource model.

      APAR: IY29952
      Symptom: Bad LDAP query on "Active Directory Integrated DNS" 
               resource model causes error 

      APAR: IY29984
      Symptom: The "Active Directory Integrated DNS" resource model 
               does not support DNS zone delegation

      Note: The resource model now supports delegation.
            The subdomain delegation of the subdomain gc._msdcs is not 
            yet supported.  If you decide to delegate that subdomain 
            to another DNS, the resource model will not be able to 
            distinguish if a GC dnsNode is missing because it has been 
            delegated or because of a real problem

      APAR: IY29986
      Symptom: Some resource models of the "Active Directory Replication" 
               category do not work if there are references to 
               "Deleted Servers"	  

      APAR: IY30459
      Symptom: If the GetGCList call fails, the "Domain controller 
               availability" resource model will fail. However, no 
               events are sent.

      APAR: IY30685
      Symptom: If there are failures in some of the APIs of the 
               iadstools.dll the application event log will be filled 
               up with events generated by the IadsTools source.

      APAR: IY30997
      Symptom: The "File Replication Service Performance" resource model 
               fails if the performance counters dynamic library got 
               disabled for some reasons 

      APAR: IY31000
      Symptom: The "Active Directory Integrated DNS" resource model could 
               show return code 19 improperly in some conditions.

      APAR: IY31007
      Symptom: The "Inter-site replication traffic" resource model 
               failed to re-start when running together with 
               "Domain controller performance" resource model

      APAR: IY31384
      Symptom: The "Domain controller availability" resource model may 
               have problems in resolving names

      APAR: IY32440
      Symptom: The "Domain controller availability" resource model 
               sends the "All GC unavailable" twice if there are no 
               global catalog in the forest 

Operating Systems: Solaris, AIX 4, HP-UX 10/11, Windows NT 4.0, Windows 2000

Patches superseded by this patch: None

Dependencies: 3.7-DMW-0003


Patch Contents:

    - This README file
    - Verification Status Report
    - A CDROM image for this patch 



 Before You Begin the Patch Installation: 

 Before you install the patch, you MUST stop the Tmw2k engine on all 
 endpoints by using the wtmntcmd -stop command.


 **********************************************************************

 Installing the patch is a two-stage process:
 1) Extract the patch.
 2) Apply the patch in ONE of the following two ways:
   2A) With Software Installation Service (SIS)
   2B) From the Tivoli desktop

 **********************************************************************

 1) To extract the patch, perform the following steps:
 
   On a UNIX system:
      
      Get the patch tar file from machine (i.e. tivoli) and put it in 
      the $PATCH directory. Then use the tar command to extract the 
      contents into a temporary directory:
        
      # cd $PATCH
      # tar xvf 3.7-DAD-0001.tar
    
      where:
      the symbol $PATCH points to the temporary directory  

   On a Windows NT system:

      Get the patch tar file from machine (i.e. tivoli) and put it in
      the $PATCH directory. Extract the contents into a temporary 
      directory: 

      > %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
      > X:              
      > cd %PATCH%
      > tar xvf 3.7-DAD-0001.tar

      where:
      - the symbol %PATCH% points to the temporary directory
      - 'X' is the drive letter where the %PATCH% directory 
        is located
     
      NOTE:  On Windows NT systems, the executable for tar is 
             in the TME installation under bin/w32-ix86/tools/tar.exe.


 2)   You MUST have both the install_product and super 
     authorization roles to successfully install this patch.


 2A)  Before you apply the patch using Software Installation Service
     (SIS), note the following:

     SIS can install Tivoli products on any hardware
     platform supported by Tivoli, but there are some
     hardware platforms on which SIS cannot be run. 
     Check your Tivoli Software Installation Service User's Guide 
     and Tivoli Software Installation Service Release Notes, 
     Version 3.6.1 for the list of platforms on which SIS can be
     run and for more information about using SIS.

 2B) To apply the patch from the Tivoli desktop, perform the following
    steps:
    
     a)  Select "Install -> Install Patch" from the
         "Desktop" menu to display the "Install Patch" dialog.
    
     b)  Click "Select Media" to display the 
         "File Browser" dialog.
    
     c)  Type the path to the directory that contains the patch, $PATCH,
         in the "Path Name" field.               
    
     d)  Click "Set Media & Close" to return to the "Install
         Patch" dialog.
         The patch install list now contains the names of the patch 
         component to be installed:

	 o Distributed Monitoring for Active Directory 3.7 patch 3.7-DAD-0001

     e)  Select the following patch component from the list by clicking
         it:
    
     	 Distributed Monitoring for Active Directory 3.7 patch 3.7-DAD-0001

     f)  Select the managed nodes on which to install the patch.
                 
     g)  Click "Install" to install the patch.

	 
	      
