Scripting

the software is going to be installed via scriptWhy? If you don't have a fully-fledged deployment mechanism, use an MSI with Group Policy.

If there were some way to bypass UAC in script, you don't think that that might be a teensy-weensy flaw-ette in the whole rationale behind its existence? You could start the EXE via the script as a domain admin but then you run into securing that account's password (as you wouldn't really want it exposed in script...)

Correct me if I am wrong don't you need Active Directory to use group policy?. We are on a Novell Network?

Damn crystal ball, all fogged-up again!

Any thoughts as to what I can do?

Since you are on a Novell network, do you have ZCM or ZFD for software distribution?

Also you could script to turn off the UAC prior to the install and turn it back on when it's done.

no ZCM or ZFD, because we are in the process of changing to AD in the next 4 months.

When you happen to have that script handy to turn of UAC on and OFF?

If your the network is moving to AD, see if the Enterprise Server software from Microsoft is being purchased, I do believe SMS comes part of the package. You'd have to read up on what comes with the Enterprise Server software..

Here are some script examples.

Example 1: 'Import Registry Settings

set oFile = CreateObject("scripting.FileSystemObject")
set oShell = CreateObject("wscript.shell")


oShell.Run("regedit.exe /s "path to registry key to import")

For the above script you'd have to export the registry key (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System ) when UAC on and then of course when UAC is off.



Example 2: Turn off: @Echo off

C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f

exit

Example 3: Turn on: @echo off

C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f

I hope these examples help

Did you try running the VBScript under Local System account?

I have tried the script under local system account and local admin. I have had success both ways.

The batch files work just as good for me as well.