UAC and scripting

[sputnik]

What is Microsofts solution if you run vbscripts for administrative
tasks and these are affected by UAC ?

Swicthing UAC off requires a restart, once to disable and then once to
enable UAC once script has finished running, which hardly makes the
administrative change transparent to the user. Group policies are handy
to do this, and was a good idea but the question is the restart thats
required.

You can turn it off completely and leave it off which sounds like the
best idea, but I'm really curious about Microsoft's take on this ?
There must be some big companies using scripts out there. How do people
get around this ?

cheers

 

[Charlie Russel - MVP]

I get around it by opening a window "As Administrator" and running scripts
that require administrative privileges from there. I don't run VB at all - I
use PowerShell for my scripting. But the requirements should be the same.