IBM Support

IJ39804: DOCUMENTATION CHANGES REGARDING EFIX FOR WINDOWS 2016 DISCOVERY AT HTTPS://WWW.IBM.COM/DOCS/EN/TADDM/7.3.0?TOPIC=SENSORS-WINDOWS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • In the Windows computer system sensor documentation at https://
    www.ibm.com/docs/en/taddm/7.3.0?topic=sensors-windows-computer-
    system-sensor, following prerequisite is present for Windows 201
    where customer need to request a efix before running discovery:
    
    
    "Windows Server 2016
    
    Due to a Powershell 5 issue, you must contact your IBM Support
    representative and request that a Powershell 5 eFix be applied,
    before attempting the discovery of a Windows Server 2016 without
    a gateway. Once this has been done, discovery of the Windows
    2016 server via direct SSH will function normally."
    
    
    This efix is only required if customer is at Fixpack-3. For
    subsequent TADDM fixpacks i.e., if customer is at Fixpack 4 or
    later, no such efix is required.
    
    
    Documentation changes are required to give this clarity to
    customer.
    

Local fix

  • N/A
    

Problem summary

  • In the Windows computer system sensor documentation at
    https://www.ibm.com/docs/en/taddm/7.3.0?topic=sensors-windows-co
    mputer-system-sensor , following prerequisite is present for
    Windows 2016 discovery where customer need to request a efix
    before running discovery:
    
    "Windows Server 2016
    Due to a Powershell 5 issue, you must contact your IBM Support
    representative and request that a Powershell 5 eFix be applied,
    before attempting the discovery of a Windows Server 2016 without
    a gateway. Once this has been done, discovery of the Windows
    2016 server via direct SSH will function normally."
    
    This efix is only required if customer is at Fixpack-3. For
    subsequent TADDM fixpacks i.e., if customer is at Fixpack 4 or
    later, no such efix is required.
    
    Documentation changes are required to give this clarity to
    customer.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    packages - documentation update as part of 7.3 fixpack 10
    
    Temporary fix
    
    The document at
    https://www.ibm.com/docs/en/taddm/7.3.0?topic=sensors-windows-co
    mputer-system-sensor is updated as below:
    "Windows Server 2016
    For TADDM 7.3.0.3, due to a Powershell 5 issue, you must contact
    your IBM Support representative and request that a Powershell 5
    eFix be applied, before attempting the discovery of a Windows
    Server 2016 without a gateway. Once this has been done,
    discovery of the Windows 2016 server via direct SSH will
    function normally.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ39804

  • Reported component name

    APP DEPENDENCY

  • Reported component ID

    5724N5500

  • Reported release

    730

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-05

  • Closed date

    2022-06-28

  • Last modified date

    2022-06-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730"}]

Document Information

Modified date:
29 June 2022