dmessmer

Hi all,

We are trying to come up with a script to remove the Automatic Configuration Script proxy address in IE properties on the LAN Settings page.

As is often the case when we want to do something new, we try to take something that worked before and modify it to meet our new purpose. To that end, here is a script that I know works.

'vbscript
On Error Resume Next
Dim objShell
Set objShell = WScript.CreateObject("WScript.Shell")
objShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Location Profiles\Services\{1E6CEEA1-FB73-11CF-BD76-00001B27DA23}\Default\Tab1\Server","","REG_SZ"
WScript.Quit ' Tells the script to stop and exit.

We use this to clear out the Default Netware Server name on computers that have this set and it works great.

But . . .this script does not work.

'vbscript
On Error Resume Next
Dim objShell
Set objShell = WScript.CreateObject("WScript.Shell")
objShell.RegWrite objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr entVersion\Internet Settings\AutoConfigURL","","REG_SZ"
WScript.Quit ' Tells the script to stop and exit.

Only real difference that I can see is that we are writing to the CURRENT USER section but we run this script when a user is logged on and nothing happens.

Any suggestions?

Thanks.

Dave

Brandon

Can you not make a Group Policy to handle this?

If not see this: IE - Automatically Detect Settings - SOLVED

__________________
Brandon

dmessmer

We don't use Group Policies. We use Novell servers (NDS) and don't use Zenworks. We use Deployment Server for as much as we can.

Thanks, I'll try to modify one of those scripts.

Dave

dmessmer

When I run the modified script:

const HKEY_CURRENT_USER = &H80000001
strComputer = "."

Set oReg=GetObject("winmgmts:{impersonationLevel=imper sonate}!\\" &_
strComputer & "\root\default:StdRegProv")

strKeyPath = "Software\Microsoft\Windows\CurrentVersion\Interne t Settings"
strStringValueName = "AutoConfigURL"
oReg.DeleteValue HKEY_CURRENT_USER,strKeyPath,strStringValueName

I get the following messages in the Command Prompt window.

C:\>const HKEY_CURRENT_USER = & H80000001
'const' is not recognized as an internal or external command,
operable program or batch file.
'H80000001' is not recognized as an internal or external command,
operable program or batch file.
C:\>strComputer = "."
'strComputer' is not recognized as an internal or external command,
operable program or batch file.
C:\>Set oReg=GetObject("winmgmts:{impersonationLevel=imper sonate}!\\" & _
'_' is not recognized as an internal or external command,
operable program or batch file.
C:\>strComputer & "\root\default:StdRegProv")
'strComputer' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
C:\>strKeyPath = "Software\Microsoft\Windows\CurrentVersion\Interne t Settings"
'strKeyPath' is not recognized as an internal or external command,
operable program or batch file.
C:\>strStringValueName = "AutoConfigURL"
'strStringValueName' is not recognized as an internal or external command,
operable program or batch file.
C:\>oReg.DeleteValue HKEY_CURRENT_USER,strKeyPath,strStringValueName
'oReg.DeleteValue' is not recognized as an internal or external command,
operable program or batch file.

Is there something else I need to add at the beginning of the script to tell the job to use WMI?

Thanks.

Dave

jenifer.arnold

Check out this post by ksweet -- Set HKEY_CURRENT_USER Registry key via the local system account

__________________
Jenifer Arnold
Information Technology Division
Anchorage Water & Wastewater Utility

andykn

It's still a VBScript so you still need the 'vbscript at the start to tell the AClient to use WScript to run the script.

Wscript will work out when to use WMI from the vbscript.

dmessmer

Thanks, that got it to work when I supplied the specific user name and password in the Run Script Job.

Thanks for that. It's going to take awhile to whittle that down for what I need. I'm not that experienced with vbscript. Gives me a great start though.

Dave

Brandon

Post 13 in the link I provided details how to do this with HKLM instead of HKCU, no VBS requried. I suggest you read that entrie thread for more information.

__________________
Brandon

Brandon

While I would absolutely not reccomend handling this with an MSI, an article on the same thing was posted on juice today. https://www-secure.symantec.com/conn...user-windows-x

__________________
Brandon

dmessmer

Now THAT . . . is slick. Thanks for pointing that out to me . . . again.

That actually works better at what we are trying to accomplish than the HKCU route since in our environment the settings would be machine-based not user-based anyway.

Dave

Brandon

No problem, I hope it works and is a little easier to deploy.

__________________
Brandon