/build/static/layout/Breadcrumb_cap_w.png

Install per machine to per-user folders

I am creating a package. Here's a rundown:

Intended for per-machine GPO install
Two things to install:
1. AAA.BBB file (write as ini file, though it’s acceptable to copy it as a regular file) that goes to %HOMEDRIVE%
2. shortcut that refers to that .BBB file
Once shortcut is dropped onto workstation, it should be configured to initiate self-repair. .BBB files are already associated with another stand-alone application that’s pre-installed.

So far, I tried to place the file into %APPDATA%. That kind of works if initiated through GUI. If pushed through GPO, the file goes to System profile. Validation returned ICE91 warnings.
Is it attainable without resorting to scripting?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: MSIPackager 19 years ago
3rd Degree Black Belt
0
The ICE91 warning information describes the cause of problem you are having - guess you need to resolve the warning by storing the file somewhere other than a per-user directory listed here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/ice91.asp

Do you have a HKCU registry keypath set on the component installing that file? That should force a repair when the shortcut is run and copy the AAA.BBB to current user AppData folder and may get around the problem without resolving the ICE91 warning.

Let us know how you get on...

Regards,
Rob.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ