Converting a Per User install
I'm packaging an app that by default installs to “C:\Users\local-user-name\AppData\Roaming\VendorName\AppName”. Since I need a Per Machine install, I sent an email to the vendor asking if a per machine install was possible. Meanwhile I re-engineered the app in Installshield to install to “C:\Users\Public\AppData\Roaming\VendorName\AppName”. It works fine so far. I then received a response from the vendor suggesting moving the install folder to “C:\Users\Default\AppData\Roaming\VendorName\AppName”.
My question is - Is there really any difference between installing to “C:\Users\Public" or “C:\Users\Default"? I'm kinda looking for a best practice.
Answers (2)
See the answers given below
Is it MSI or Legacy EXE?
Comments:
-
Legacy .exe - robtk 11 years ago
-
Is this application has any shortcut? any registries? - jagadeish 11 years ago
-
Shortcuts and several registry keys. Only one key needed editing to correct the new file path. As I said, I've already got it working. I'just just wondering if I'm using a valid and correct file path. - robtk 11 years ago
-
Why don't you move them to C:\Program Files\VendorName\AppName folder.. Instead of keeping them in Roaming... - jagadeish 11 years ago
-
That may or may not break the whole thing. The path I have now has no spaces in it. - robtk 11 years ago
-
You will have to test the functionality of the applcation once you redirect the path.. if you are worried like this then no application can be packaged.. - jagadeish 11 years ago
http://www.itninja.com/question/windows-7-public-desktop-vs-default-profile-desktop
"In public normal users cannot delete the icons if they do not want them if placed in default they can. On existing machines when placed in public all user get that icon even if they have an existing profile. On an existing machine when placed in default only new users will get that icon."
