IJ14919: THERE IS NO EXPLICIT REQUIREMENT FOR THE WINDOWS SCRIPT HOST TO BE ENABLED ON THE WINDOWS ENDPOINT, BUT WE REQUIRE IT IN ILMT

APAR status

• Closed as program error.

Error description

• there is no explicit requirement for the Windows Script Host to
  be enabled on the Windows endpoint, while we require it in
  ILMT, i. e. following registry setting:
  
  ----------------------------------------------------------------
  --------------------------------------------
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows
  Script Host\Settings]
  
  "DisplayLogo"="1"
  
  "ActiveDebugging"="1"
  
  "SilentTerminate"="0"
  
  "UseWINSAFER"="1"
  
  "Enabled"=dword:00000000
  

Local fix

• changing the registry entry:
  
  ----------------------------------------------------------------
  --------------------------------------------
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script
  Host\Settings]
  
  "DisplayLogo"="1"
  
  "ActiveDebugging"="1"
  
  "SilentTerminate"="0"
  
  "UseWINSAFER"="1"
  
  "Enabled"=dword:00000000
  
  ----------------------------------------------------------------
  --------------------------------------------
  
  
  
  to:
  
  ----------------------------------------------------------------
  --------------------------------------------
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script
  Host\Settings]
  
  "DisplayLogo"="1"
  
  "ActiveDebugging"="1"
  
  "SilentTerminate"="0"
  
  "UseWINSAFER"="1"
  
  "Enabled"=dword:00000001
  
  ----------------------------------------------------------------
  --------------------------------------------
  
  
  
  allows customer to execute the the VBS script manually using
  the user account he was then logged in to the endpoint.
  
  ----------------------------------------------------------------
  --------------------------------------------
  
  is preventing the capacity scan fixlet to be successfully run.
  

Problem summary

• [Description (what is the problem)]:
  there is no explicit requirement for the Windows Script Host to
  *
  * be enabled on the Windows endpoint, while we require it in
  *
  * ILMT, i. e. following registry setting:
  *
  *
  *
  * --------------------------------------------------------------
  *
  * --------------------------------------------
  *
  *
  *
  * [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows
  *
  * Script Host\Settings]
  *
  *
  *
  * "DisplayLogo"="1"
  *
  *
  *
  * "ActiveDebugging"="1"
  *
  *
  *
  * "SilentTerminate"="0"
  *
  *
  *
  * "UseWINSAFER"="1"
  *
  *
  *
  * "Enabled"=dword:00000000
  *
  *
  *
  *
  *
  * LOCAL FIX:
  *
  * changing the registry entry:
  *
  *
  *
  * --------------------------------------------------------------
  *
  * --------------------------------------------
  *
  *
  *
  * [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script
  *
  * Host\Settings]
  *
  *
  *
  * "DisplayLogo"="1"
  *
  *
  *
  * "ActiveDebugging"="1"
  *
  *
  *
  * "SilentTerminate"="0"
  *
  *
  *
  * "UseWINSAFER"="1"
  *
  *
  *
  * "Enabled"=dword:00000000
  *
  *
  *
  * --------------------------------------------------------------
  *
  * --------------------------------------------
  *
  *
  *
  *
  *
  *
  *
  * to:
  *
  *
  *
  * --------------------------------------------------------------
  *
  * --------------------------------------------
  *
  *
  *
  * [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script
  *
  * Host\Settings]
  *
  *
  *
  * "DisplayLogo"="1"
  *
  *
  *
  * "ActiveDebugging"="1"
  *
  *
  *
  * "SilentTerminate"="0"
  *
  *
  *
  * "UseWINSAFER"="1"
  *
  *
  *
  * "Enabled"=dword:00000001
  *
  *
  *
  * --------------------------------------------------------------
  *
  * --------------------------------------------
  *
  *
  *
  *
  *
  *
  *
  * allows customer to execute the the VBS script manually using
  *
  * the user account he was then logged in to the endpoint.
  *
  *
  *
  * --------------------------------------------------------------
  *
  * --------------------------------------------
  *
  *
  *
  * is preventing the capacity scan fixlet to be successfully run.
  *
  *
  *
  *
  *
  *
  *
  * [Steps to reproduce]:
  *
  *
  * [Environment]:
  *   BFI or ILMT?
  *   Windows, Linux, Other?
  *   Build number?
  * EXPECTED RESULTS:
  * The issue does not occure.
  ****************************************************************
  * RECOMMENDATION: Apply appropriate update when available.
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  packages:
   | Update | ILMT 9.2.16
  ****************************************************************
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  LIC METRIC TOOL

• Fixed component ID

  5724LMTEM

Applicable component levels