Install Privledges

[rhosk]

I have a fairly large project (video, flash, audio, etc..) that instead of running from the CD Drive, I created an install for. Obviously, most networks won't allow installs, especially to the Windows folder (ini files). But, they usually have write privledges in the [user] My Docs / Temp folders, right?

With that, my question is: Would it be totally unconventional to install this project underneath the 'My Documents' folder (I just need the hard drive speed / reliability as a sort of temporary parking space)? Has anyone ever performed this knowing that some users won't have the privledges? Would it even work in most cases? And dumb question - is "Install" different from "Copy files" as far as these networks are concerned? Any experience, lessons learned would be great.

[Adam]

Ron,

You may even want to install the files to TempFolder since all users will have a temp folder that their account has permissions for.

Copy vs Install:
Install is different when dealing with dll,ocx ect. If the file is not a registerable file then these two are the same. I would stick with Copy unless you explicitly need to install the file.

Hope this helps

Adam Kapilik

[bnkrazy]

I think that most users that don't have admin access can't install anything period. Even though it is a simple copy process to 'install' the files, you must also have permissions to modify the registry and add the uninstall info, etc. You might be agle to work around that by not including an uninstaller, but I have never tried that approach.

I think the best solution may be to kind of roll your own 'install' with two files on the CD. The first when run simply copies the files to the user's machine, and the second removes them...(or one exe with command line prameters).

Your CD executable could check for the existance of the files on the machine and run the app from there instead...or copy them there on first run...

The only catch would be if it is being installed on a corporate network, Group Policy in AD may restrict a user's permissions further, but not likely on the users folders. Also, here we have user's home folder redirection in place that redirects the user's My Documents folder and a few others to the server...so you may start using lots of server space if a company has lots of users using the app...just a thought.

[Eagle]

I tend to go with Adam here, users _TempFolder or you could go
with the current User's ApplicationDataFolder as alternatives to the
user's _MyDocumentsFolder. (covers redirection possibilites fine)
could do a string.find for "\\\\" to see if target location is network stored

using the shell.getfolder actions or other _constants should cover the
generic location possibilities. Could Do the free-space check thing.

you could do a read\write\delete test with a unique.txt file
(get the system time and name the test file by that name)
if you want to be sure the 'access is working before 'install-copy'.
Using an ini file to the 'install location' may help driving your App.

Maybe give an option to run from the Media or Hdisk.

As far as Corporate networks..security on folders etc, well
someone has to install it, serve it or allow access etc. if they
wish to use your product.

Another thought.. pass on some\all of the responsibility 'where' to install
to end user. If install\copy fails then advise accordingly.

ramble, ramble..my 2 bob.

[rhosk]

Thanks everyone, lots to ponder.

[kk250040]

I have an installer for my client which needs to have uninstall privileges to the current user and the administrator. I mean the user who installs it and just the admin need to have rights to uninstall and no other user should be able to uninstall it.

I know we have 2 options for shortcuts called CurrentUserOnly and AllUsers.
But how far do these support the rights of the users. If the other user(s) try to uninstall from the add/remove programs??

Also we have options to limit the permission to...
User must have administrative privileges
User Notification:
Warn user and continue
Notify user and abort setup
If I select the User must have administrative privileges and opt to Notify user and abort setup then does this help me to do what I exactly need. I mean do these options opted would allow a non-admin user who installs it and the admin to have the Uninstall rights and the rest cannot ?? through the add/remove programs too ??

Please advise...

[kk250040]

I forgot mentioning that I am creating the installer using the SetUpFactory7. Hope I had a way to move this thread to SF7 discussion

[jassing]

I forgot mentioning that I am creating the installer using the SetUpFactory7. Hope I had a way to move this thread to SF7 discussion

So instead of posting in the SF7 forum, you resurrect an unrelated 2 year old thread?

An easy way around it is to store the user who installed in the registry, or uninstall data file. If the uninstall is launched by another user, show a screen to alert "Sorry, you didn't install this"

The obvious problem i see is that if that user is deleted; then the program can not be uninstalled. YOu'll need an override on that.

[kk250040]

sorry for the delayed response, as I said the administrator can always uninstall it if required, it should not be a problem i guess. What I was reported was any user was able to uninstall the setup while only the current user and the admin are expected to uninstall it.
I fixed the issue with the System Requirement settings and the client actually accepted it, but I am still waiting for the testers to give me a green.

Thanks for the response Jassing, what you said is true and I will do it in the next release if the testers still see a problem, I do not know how far the options on that screen really meant to help my point here.