Any particular reason for not using Group Policy to set the proxy settings?
Anyway, courtesy of Mark Blaskie (
http://groups.google.com/ is great for
finding this stuff).....
Dim Shell
Set Shell = WScript.CreateObject("WScript.Shell")
Shell.RegWrite "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet
Settings\ProxyEnable",1,"REG_DWORD"
Shell.RegWrite "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet
Settings\ProxyServer","proxyserver:8080"
Shell.RegWrite "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet
Settings\ProxyOveride","abc;<local>"
WScript.Quit()
The Exchange/Outlook thing is much more tricky. There are some third-party
tools to do this and also some free Microsoft ones. I would give you names
of the free ones, but to be honest I never had any success with them.
This is the commercial one that springs to mind:
http://www.metastore.be/products_profilemaker.asp
The way I do it is to use the Custom Installation Wizard from the Office
Resource Kit to prespecify the mailbox name and server. The username is
%username% and the server name I set here is simply "exchange". I then
create a DNS A record for "exchange" and point it at my actual Exchange
server (which has a different name). That way I can change the name of my
Exchange server without reinstalling all my workstations!
For Exchange 5.5 (yeah, I know), this relies on having usernames that are
sufficiently long that they don't match a partial display name. It also
relies on the mailbox alias being exactly the same as the NT username. For
example, if my username was something short, like "OR", it would match
George Orwell in the address list and try to connect to the wrong mailbox.
This is because the mailbox alias isn't the first on the list of attributes
to match against.
I don't know the score for Exchange 2000 or 2003 (but I'll be finding out
soon enough).
Cheers
Oli