[Issue1]
IssueType: RegisterDLL
DDLName: scrrun.dll
Action:Registerwin32
Title: Win32 scrrun.dll is not registered
Description: Scripting.FileSystemObject is implemented in scrrun.dll which comes with OS. If scrrun.dll is not registered, TTU installation will be aborted with error message "Microsoft VBScript runtime error: ActiveX component can't create object: 'Scripting.FileSystemObject'".
Details: So USER (with Administrator privileges) has to register DLL scrrun.dll.
Fixable:0
FixDescription: Run this command as Administrator: %systemroot%\syswow64\regsvr32 %systemroot%\syswow64\scrrun.dll

[Issue2]
IssueType: RegisterDLL
DDLName: scrrun.dll
Action:Registerwin64
Title: Win64 scrrun.dll is not registered
Description: Scripting.FileSystemObject is implemented in scrrun.dll which comes with OS. If scrrun.dll is not registered, TTU installation will be aborted with error message "Microsoft VBScript runtime error: ActiveX component can't create object: 'Scripting.FileSystemObject'".
Details: So USER (with Administrator privileges) has to register DLL scrrun.dll.
Fixable:0
FixDescription: Run this command as Administrator: %systemroot%\System32\regsvr32 %systemroot%\System32\scrrun.dll

[Issue3]
IssueType: RegisterDLL
DDLName: jscript.dll 
Action:UnRegister
Title: JScript is registered in HKEY_CURRENT_USER
Description: DLL jscript should not be registered in HKEY_CURRENT_USER.
Details: As a security measure, Windows Installer will not load script engines registered in HKEY_CURRENT_USER. As a user-writable store, a normal user could get an elevated install to run their library masking as a script engine if the custom action was not explicitly attributed with msidbCustomActionTypeNoImpersonate (0x0800). This is an elevation of privileges attack; thus, Windows Installer returns error message 2738 or 2739 for custom actions type 6 and type 5, respectively, and returns Windows error 1603, ERROR_INSTALL_FAILURE.
Fixable:1
FixDescription: Remove/Rename the key: HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}

[Issue4]
IssueType: RegisterDLL
DDLName: vbscript.dll
Action:UnRegister
Title: VBScript registered in HKEY_CURRENT_USER
Description: DLL vbscript.dll should not be registered in HKEY_CURRENT_USER.
Details: As a security measure, Windows Installer will not load script engines registered in HKEY_CURRENT_USER. As a user-writable store, a normal user could get an elevated install to run their library masking as a script engine if the custom action was not explicitly attributed with msidbCustomActionTypeNoImpersonate (0x0800). This is an elevation of privileges attack; thus, Windows Installer returns error message 2738 or 2739 for custom actions type 6 and type 5, respectively, and returns Windows error 1603, ERROR_INSTALL_FAILURE.
Fixable:1
FixDescription: Remove/Rename the key: HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

[Issue5]
IssueType: RegisterKey
DDLName: TeraGSS32
Action:UnRegister
Title: Legacy TeraGSS32 - Leftover keys
Description: TTU Suite 15.00 is not present and few legacy TeraGSS keys leftover in registry.
Details: When TTU Suite 15.00 is not present, then the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Teradata\Teradata GSS\nt-i386\15.00.xx.xx should be removed.
Fixable:1
FixDescription: Remove the key: "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Teradata\Teradata GSS\nt-i386\15.00.xx.xx"


[Issue6]
IssueType: RegisterKey
DDLName: TeraGSS64
Action:UnRegister
Title: Legacy TeraGSS64 - Leftover keys
Description: TTU Suite 15.00 is not present and few legacy TeraGSS keys leftover in registry
Details: When TTU Suite 15.00 is not present, then the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Teradata GSS\nt-x8664\15.00.xx.xx should be removed.
Fixable:1
FixDescription: Remove the key: "HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Teradata GSS\nt-x8664\15.00.xx.xx"

