hope its ok to post this.
watch out for your use of the Win32_Product class from vbscript. under some circumstances it can cause any MSI application it comes across (say you are auditing installed apps) to check its integrity and can result in repairs etc being kicked off. (this can be painful when the account running the Win32_Product enum doesnt have rights etc)
advise is to use the win32reg_addremoveprograms class instead
watch out for your use of the Win32_Product class from vbscript. under some circumstances it can cause any MSI application it comes across (say you are auditing installed apps) to check its integrity and can result in repairs etc being kicked off. (this can be painful when the account running the Win32_Product enum doesnt have rights etc)
advise is to use the win32reg_addremoveprograms class instead
