I found a good site to find missing DLL's. In case you don't find the original media, this site can be helpful to download the right DLL in few minutes...

How to perform the DLL recovery:

• Identify the DLL file through the Search funciton or the file directory list
• Download the ZIP file
• Uncompress and install the DLL following the step-by-step istructions

Link: dll-files.com

OpenedFilesView displays the list of all opened files on your system. For each opened file, additional information is displayed: handle value, read/write/delete access, file position, the process that opened the file, and more...
Optionally, you can also close one or more opened files, or close the process that opened these files.

This utility is especially useful if you try to delete/move/open a file and you get one of the following error messages:

1. Cannot delete [filename]: There has been a sharing violation. The source or destination file may be in use.
2. Cannot delete [filename]: It is being used by another person or program. Close any programs that might be using the file and try again.

When you get one of these error messages, OpenedFilesView will show you which...

In testing the Symantec Endpoint Protection Integration Component, I noticed that the default uninstall.js provided for the new client does not uninstall live update. This causes issues if you install the client and later need to uninstall/reinstall it. A silent reinstall of the client will fail unless live update is manually removed.

Resolution:

Add the following section to the uninstall.js after the //uninstall the SEP client section

+++++++++++++++++++++++++++++++++++++++
//uninstall Live Update else reinstall will not work
var lupLocation = "c:/Progra~1/Symantec/LiveUpdate/Lsetup.exe";
shell.Run( lupLocation + " /u /q", 0, true );
++++++++++++++++++++++++++++++++++++++++

Hope this helps!

In addition to ErikW's article: Wise Package Studio, Part 11: Testing Our Packages I am attaching two examples that I created which can be used as 'sign off' documents of tested Application(s).

The UAT (User Acceptance Testing) form is to be filled out by the user who test the application. This is to make sure the user doesn't forget to test anything. He/She can sign off of the steps.

The QA/Peer review form is to be filled out by a fellow packager. We are all human, therefor we make mistakes or maybe there is something we did or didn't do and didn't know. Your fellow packager can point this out to you and you'll keep learning and to assure the packages that are going to be deployed are stable.

There are many more options that can be added to these forms, depending on...