Storing setting in ini file in program folder is good for portable version and for those users who have admin rights. If someone logs in as user, he can't save frecommander settings as he has no permissions to write to program files. May be you can make it like AIMP, that asks what user wants during install: single, or multiuseruser config?
PS
Nice piece of software, by the way. Keep going!
Multiuser FreeCommander
Related Issue with Group Policy deployment of FreeCommander
I have a related problem regarding user credentials.
I want to automatically assign FreeCommander to my users from the MSI package via Active Directory Group Policy. The installation works fine but doesn't allow the user to save settings to the .ini file without elevated credentials. If the installation set the permissions on the .ini file to "modify" for users it would be good.
Also I want to apply a custimized .ini file for my users automatically, located on a network share.
The only work-around I can think of is to make a logon script to change the permissions on the .ini file and copy a shortcut to the desktop with the /ini= switch (which doesn't seem to be working for me at the moment, what is the correct syntax?).
I could also use a script to copy the custom .ini file to the install folder but I want the .ini file off the system drive so as not to lose settings in the event of a re-install.
Otherwise I'm liking the program very much as a replacement for Total Commander.
I want to automatically assign FreeCommander to my users from the MSI package via Active Directory Group Policy. The installation works fine but doesn't allow the user to save settings to the .ini file without elevated credentials. If the installation set the permissions on the .ini file to "modify" for users it would be good.
Also I want to apply a custimized .ini file for my users automatically, located on a network share.
The only work-around I can think of is to make a logon script to change the permissions on the .ini file and copy a shortcut to the desktop with the /ini= switch (which doesn't seem to be working for me at the moment, what is the correct syntax?).
I could also use a script to copy the custom .ini file to the install folder but I want the .ini file off the system drive so as not to lose settings in the event of a re-install.
Otherwise I'm liking the program very much as a replacement for Total Commander.
- EtherealMonkey
- Posts: 22
- Joined: 24.04.2009, 07:56
Re: Related Issue with Group Policy deployment of FreeComman
What is the OS? Vista I presume? I am not sure what the problem it is you are having with this, so consider this part of my response more of a solicitation for information than anything.Paul_F wrote: If the installation set the permissions on the .ini file to "modify" for users it would be good.
Now, I like this idea. And, I just tested it.Paul_F wrote: Also I want to apply a custimized .ini file for my users automatically, located on a network share.
And... it works!!! So, I guess you would like to know the syntax?
{PathToFreeCommanderInstallFolder}\FreeCommander.exe /Ini=\\MachineName\ShareName$\FreeCommander_Test.ini (the $ is optional, I prefer hidden Shares
You are doing backups, right?Paul_F wrote: I could also use a script to copy the custom .ini file to the install folder but I want the .ini file off the system drive so as not to lose settings in the event of a re-install.
Well, either way, the idea you had with the drive share will work. If your users don't have much info on the machines (kiosk, POS, Thin Client, etc), then I guess you should be set...
Who is online
Users browsing this forum: No registered users and 110 guests