Hi,
Using any of the sample apps, build Compressed Single Self-Installing EXE then make a single file MSI using the Group Policy Wizard.
Start the installation of the MSI, when the Welcome Dialog is displayed cancle the installation. (Note: The left over files and registry keys occur even for successful installations)
There will be a {GUID}.exe file left over in the user temp folder (mine is C:\\Documents and Settings\\User\\Local Settings\\Temp\\).
Also the product will not show in the ARP but it is still linked in the registry; the following keys remain:
HKEY_CURRENT_USER\\Software\\Microsoft\\Installer\\ProductsHKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-21-861567501-152049171-106028\\ProductsHKEY_USERS\\S-1-5-21-861567501-152049171-1060284298-1004\\Software\\Microsoft\\Installer\\ProductsI use Windows Install Cleanup to tidy up at this point.
My company would like to provide one solution to our clients, MSI Installation for our products; this includes the use of Group Policy installation and non GP installations.
I have tried to remove the bootstrap exe with Call DLL Function -> DeleteFileA but it is locked (this is the program that is currently running).
After thinking about this I realized that there is propably no solution for this due to the design of a wrapper MSI for Group Policy deployments.
I am at this point looking for conformation that this is a restriction and I am not doing something wrong.
I read a post from 2006 that said the Group Policy Wizard creates MSI installations that are only intented for GP deployments.
At this time I will inform my IT people that we need to carry two seperate installation packages for each product and educate our clients on the correct one to use.
Thanks
George
P.S. I realy like working with your product... very nice.
