|
|
|||||||
Since Vista has certain parts of it locked down even for Administrators, it would be nice if KIX had the ability to have an Elevate macro built in. This could be used to restore the registry commands in KIX back to functionality again. |
||||||||
|
|
|||||||
I agree, (unless someone can tell me how to do it without builtin support) this is a must. |
||||||||
|
|
|||||||
Would one of you mind providing an example of what normally works, and what doesn't under Vista. |
||||||||
|
|
|||||||
Where is doesn't work please make sure that you include any useful information such as @ERROR codes and event log entries. |
||||||||
|
|
|||||||
Here's just one example of where elevation is required... Code: Break On Shell "regsvr32 /s "+%windir%+"\System32\KiXforms.dll" ? @SERROR Get $ When run without elevation, it returns... Code: Access is denied. We need an ability to shell and run elevated as well as elevate processes (including Kix). I propose the following syntax Code: Shell Elevated $cmd Shell Limited $cmd Run Elevated $cmd Run Limited $cmd Elevate @pid Limit @pid |
||||||||
|
|
|||||||
I would also like to suggest a macro @elevated to determine if the process is running as admin. |
||||||||
|
|
|||||||
This is not just Vista. WinXP and Win2K also needed at least local admin privileges to register a DLL. There is an easy fix for this. Just run this kind of stuff in a startup script or deploy KF with a GPO. |
||||||||
|
|
|||||||
The original poster refers to issues with registry access, specifically with the change to Vista. Please start a new thread if you want to request a facility to shell / run processes with local admin or other type of elevated access. It's not a bad request, it's just in the wrong place and there is a danger that the original posters requirement will be lost in the ensuing flood of responses |
||||||||
|
|
|||||||
@Richard - Well he was talking about elevation so I figured it is very closely related and it did not necessitate a new thread; the registry example used is equally relevant to my own. @Mart - Quote: This is not just Vista. WinXP and Win2K also needed at least local admin privileges to register a DLL. There is an easy fix for this. Just run this kind of stuff in a startup script or deploy KF with a GPO. I already do register KiXforms and run other admin requiring scripts via a system scheduled task set up by a group policy start-up script; my example was just one readily recognisable issue. Some scripts need to elevate themselves (or processes they start) to admin within a Vista user environment, otherwise they can't work in such a context. This is unless of course they are launched within an elevated environment, which you can't expect users to know to do, and is generally not a desirable method. I futher disagree that it is not a Vista specific issue because with XP and 2K you can detect if you have the permissions or not. Elevation is an different issue altogether. Regards, Richard |