Here are some component guidelines which you need to follow in your application MSI. This will solve many issues like installation fix and automatic package repairs.

Always remember,

• HKLM + HKCU in same component are not allowed
• HKCR + HKCU in same component are not allowed
• HKCU + Files in same component are not allowed. (Exception where the files are going to user profiles and key path is HKCU key path)

Also, when you design a custom component having HKCR or HKLM components, do check the Auto increment option; this helps the machine maintain a stable state.

Deployment Solution 6.9 adds a new feature to import/export computers to an XML file.

The XML file contains the computer name, asset tag, serial number, UUID, NICs information. The most useful information is the computer group that the computer is a member.

Importing computers now allows importing an XML file and such file could now be modified to import multiple computers to computer groupings in the Deployment Console.

Import and Export computers is located under the File Menu - Deployment Solution Console.

The following is an example of one computer:

- <?xml version="1.0" encoding="utf-8" ?> 
- <computers ver="14" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" -xsi:noNamespaceSchemaLocation="computers.xsd">
- <computer>
- <name>RACK01C10</...

For some applications which have ODBC drivers, you may question if the application has created an ODBC driver or not? This tip will help you answer that question.

Go to Control Panel > Administrative Tools. Double click ODBC and check User DSN and System DSN and File DSN. If the application used drivers, then there will be entries in any one of the DSN.

OR

After installing the application go to C:\windows \ click ODBC.ini and checks if particular applications need any driver.

Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.

While WISE Script is easy to make, I mean takes less effort, VBScript can be very complicated. People who do not know VBScript often find themselves searching for, and copying code from net. WISE Script can be easily written once you have basic understanding of statements. I give this point as an advantage to WISE Script, but people who know how to code in VBScript, will always choose that as an easy option.

Personally, I prefer VBScript over WISE Script because it has some really good advantages. As you might know, we compile WISE Script to an exe and include that in a package. But in doing this, we lose the code...