Run As Administrator

[neil154]

I am running ver 8.01 and there are many times when I try to do something within Total Commander and it can't do it but then asks me "as Admininstator" and I click okay.

Since I am the only one using the PC can I have Total Commander always use me as a administrator so I do not get that question ever again?

[HolgerK]

AlwaysAsAdmin=0 1: Handle all further operations as admin after confirming the first with "All as administrator"

You will be asked only once per session.
Personally i would not run TC itself always as administrator because otherwise every process started by TC (even f you double click a document) would also be started with admin rights.

Regards
Holger

[Moon]

Still beats having to click away UAC messages during copying and whatnot.

[MVV]

Moon,
There were many topics regarding UAC. You're doing something wrong if you work with documents and trigger UAC messages. Only program folders must be write-protected for non-elevated users. You can open folder properties and add write permission for Users group to get rid of UAC messages for that document folder.

[ghisler(Author)]

You can add
AlwaysAsAdmin=1
to wincmd.ini section [Configuration] to reduce the admin requests.

[Moon]

What are the differences to starting as admin?

[MVV]

What are the differences to starting as admin?

When you start TC as admin, ALL programs are started as admin from TC (including programs that open documents). If you start bad software it will get admin permissions.
When you elevate only file operations, all programs are started with user permissions so won't hurt your OS.

[Moon]

So starting as normal user but setting AlwaysAsAdmin =1 elevates only the file operations?

[MVV]

Yes, it just suppresses further elevate confirmations (after the first one), but doesn't changes other aspects.

[Phred]

Moon,
There were many topics regarding UAC. You're doing something wrong if you work with documents and trigger UAC messages. Only program folders must be write-protected for non-elevated users. You can open folder properties and add write permission for Users group to get rid of UAC messages for that document folder.

More precisely, "...You can, when logged in as an administrator, open folder properties and add write permission for Users group to get rid of UAC messages for that document folder."

Remember, we're NOT all administrators - for our day-to-day operations.

Funnily enough, I've found on a number of machines that the user is prevented from writing/saving to his own desktop, and I'm not alone, among people I know.

What are the differences to starting as admin?

When you start TC as admin, ALL programs are started as admin from TC (including programs that open documents). If you start bad software it will get admin permissions.
When you elevate only file operations, all programs are started with user permissions so won't hurt your OS.

So what file operations would they be?
No-one around here but me can be an administrator, so, from anyone else's log-in, could I delve into other users' file branches when running TC with AlwaysAsAdmin=1?
(I would have to invoke TC with another ini file, of course.)

17th July, 2014

[MVV]

TC has limited functionality in user-restricted folders so even if it will show other users' dirs, it may be more useful to start elevated TC specially for such cases. Anyway, you can try it yourself.

[Phred]

Life's short. I was hoping for a pre-headsup, as they say, before trying it myself.
Christian must have had a reason for creating the switch; I'll hang around to see it anyone else has some insights. Thx.

17th July, 2014