Have a vb program that generates a db file and security program that when program launched creates a second uncompressed copy of program for execution. Everything worked well until w7 started checking write permissions on folders. XP apppath worked well but w7 where would be the best place to place program and files so that multiple users could have access? Permissions seems to be a problem. Users can't have admin permission.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
w7 best place 4 prog & data files and be shared by different users
- Thread starter 8howdoi8
- Start date
hairlessupportmonkey
IS-IT--Management
Why not a decent NAS with a couple of Drives for redundancy (mirrored set)
Issue solved!
ACSS - SME
General Geek
Issue solved!
ACSS - SME
General Geek
dilettante
MIS
It sounds like you are "side loading" sneakerware onto users' PCs in a managed network though hackish means rather than by running a proper application installer. I'm surprised that anti-virus software isn't triggering on your "dropper" program that self-extracts software onto target machines though.
There are two modes of operation for installers: per-user and per-machine.
A per-machine install to let everyone run the application requires elevation. The users need an admininstrator user/pw they can log on as, or an admin must "push install" it to such machines, or else an admin must provide "over the shoulder" credentials to the UAC prompt when running the install.
A per-user install only lets one user install an application and only that user can run it. There are no conventions for data sharing among users except "owner" style publishing which doesn't result in files fully read/write for anyone logging onto the machine.
Elevated per-machine installs are meant to create an application data folder under [tt]FOLDERID_LocalAppData[/tt] and set the required permissions on it for any shared, per-machine data like global settings files and common application data files. But a non-elevated per-user install cannot do this.
A possible alternative might be to use: [tt]FOLDERID_Public[/tt] which in the degenerate case of an English-language installation of Windows has the default path mapping [tt](%SystemDrive%\Users\Public[/tt] though this special folder does not exist prior to Vista and may actually be somewhere else or named something else on any given target system.
However this doesn't get around the need to install your application on a per-machine basis so anyone logging on can run it.
There are two modes of operation for installers: per-user and per-machine.
A per-machine install to let everyone run the application requires elevation. The users need an admininstrator user/pw they can log on as, or an admin must "push install" it to such machines, or else an admin must provide "over the shoulder" credentials to the UAC prompt when running the install.
A per-user install only lets one user install an application and only that user can run it. There are no conventions for data sharing among users except "owner" style publishing which doesn't result in files fully read/write for anyone logging onto the machine.
Elevated per-machine installs are meant to create an application data folder under [tt]FOLDERID_LocalAppData[/tt] and set the required permissions on it for any shared, per-machine data like global settings files and common application data files. But a non-elevated per-user install cannot do this.
A possible alternative might be to use: [tt]FOLDERID_Public[/tt] which in the degenerate case of an English-language installation of Windows has the default path mapping [tt](%SystemDrive%\Users\Public[/tt] though this special folder does not exist prior to Vista and may actually be somewhere else or named something else on any given target system.
However this doesn't get around the need to install your application on a per-machine basis so anyone logging on can run it.
goombawaho
MIS
Maybe the OP is asking for nefarious purposes.........
- Status
Similar threads
- Locked
- Question