Thank you so much @victorcamp  and @chrismi ! Your detailed instructions helped a lot.  ... View more

If you are using the ISLockPermissions functionality to set permissions, errors encountered while applying object permissions can be suppressed on a per-object basis by adding the undocumented value 4 to the existing value in the Attributes column (from the ISLockPermissions table in the Direct Editor). This will suppress the error dialog but will still log the error in a verbose log. Note that this does not apply for permissions set with the LockPermissions and MsiLockPermissionsEx tables implemented by Windows Installer. Errors generated while applying permissions with these tables cannot be suppressed. ... View more

Well, that certainly puts a crimp in our evaluation. ... View more

(Duplicate post; follow up here...) ... View more

I've found it simple to set such properties to a registry location, then read them back in during deferred. if you want, you can always use another action to delete the registry entry. ... View more

How to solve this problem? In Installshield Express if I set the shortcut target property as: c:\program files\microsoft office 2003\office11\winword.exe and I build the setup file, when I run the setup in a target computer the shortcut created change that target property by: c:\documents and setting\mynameprofile\desktop\winword.exe How is possible. Does anybody have experienced this thing. ... View more