Discussion Locked

WinXP Imaging and SUS automation

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a problem with Computers built with a sysprep image, not being able to access the SUS server. Network: In a domain with proxy environment.
We nailed the problem down. When you have the Proxy settings in the sysprep.ini file when syspreping and then imaging, the proxy settings transfers to all users that would log into the PC. Yes thats what we want. BUT, AU clients uses the local systems account to run automatically while the user is logged in since they are only power users. Well the system is using proxy settings to access the SUS server. Well, local accounts can't access the network without login into the domain if you bounce of the Proxy. With machines that are built without the proxy setting in the Sysprep.ini file work fine. (It took along time to figure this out) PROBLEM: We cannot find the location it is put in to remove it. Its like there is a main core it was put. We have removed them from the registry. When removed, then rebooted they come back. We have also RE-Syspreped them with no answer files and still the settings come back.Searched INI files. WHERE is this setting located at to remove them from the PCs. Only solution right not is to rebuild those PCs. Well that is Like in the 100's.

3 replies

by mrjay67

try using this reg key location:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"proxyserver"=-

Implement a reg key into the login script that uses this format. You may want to look for a location in hkey local machine.

You can look for your proxy address in the registry and export the value you need to use. May need to use a command in loin script like this: regedit.exe /s X:\folder\proxy.reg
or whatever you decide to name it.

HTH
Jason

by lupster

Already did most of your solutions. Login Script is unacceptable since there are about 300 PCs affected. Scripts are ran with profile. Not PC.
Found the solution.
You install the BITS administrator 2.0, and then go to Start?Programs?Windows Support Tools and start the command prompt.
From there you type in:
bitsadmin /util /setieproxy localsystem NO_PROXY
or
bitsadmin /util /setieproxy networkservice NO_PROXY
or
bitsadmin /util /setieproxy localservice NO_PROXY

This discussion is closed to new replies.