VBscripts installed by virtual package Altiris are not working after upgrading/installing to VSE 8.7 .
Scripts started via explorer are giving a popup "Can't find script engine "VBscript" ....
The same script can be started without problems with cscript or wscript.
Also after adding a file or subfolder in the patch of the virtual package, the VB scripts starts working again.
It certainly has something to do with scriptscan. Disabling scriptscan solves the problem but isn't an option for a production environment.
We also tested the scriptscan with the procedure deliverd by McAfee (see below).
The result is that the problem scripts do not generate any output. The working scripts do generate output.
Procedure to test scriptscan :
Step 1 - Disable Access Protection.Click Start, Programs, McAfee, VirusScan Console. Right-click Access Protection and select Disable. Step 2 - Configure debugging for the VSE ScriptScan componentClick Start, Run, type regedit and click OK. Navigate to the following registry key:[HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\VSCore\Script Scanner]Right-click the key and select New, String Value. Rename New Value #1 to DebugDumpDirectory and press ENTER. Double-click the new key and in Value Data, type the name of a directory.Example: C:\TestClose the registry editor. Step 3 - Collecting outputLaunch Windows Explorer and create the folder configured in the registry. For example, C:\TestEnsure that you exclude this directory from scanning by the On-Access Scanner. For information, see KB61000 - Managing VirusScan Enterprise exclusions with hardware paths.Reproduce the issue and new files will be created in the directory. After collecting the information, delete the DebugDumpDirectory key you just created. Step 4 - Enable Access Protection.Click Start, Programs, McAfee, VirusScan Console. Right-click Access Protection and select Enable.