Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SUS HELP!! registry entries for windows update missing on XP machines 1

Status
Not open for further replies.

fingaz

IS-IT--Management
Sep 3, 2003
19
0
0
US
I have a sus server setup on windows 2003 server. We want to use this as a way to update new systems that we build for customers so they are up to date when they leave the shop. It will not be running as a PDC. I am currently trying to test the system with xp boxes running sp1 and when I go into the registry to make the changes needed to see the sus server ( HKLS\Software\Policies\Microsoft\Windows\WindowsUpdate\AU) I can get as far as policies\microsoft\windows... The windowsupdate reg folder isn't there. I've looked everywhere for an article or tread about how to fix this and can't find anything.

 
copy this script to the client machines:
Code:
'this script makes the Automatic Updates service look for updates immediately, and download updates every 24 hours at 4:00 am 
'-------------START CODE----------
on error resume next
Set WshShell = WScript.CreateObject("WScript.Shell")
myserver="[URL unfurl="true"]http://sus.yourdomain.com"[/URL]
your SUS server name address here
Code:
starttime="04"
olddate=date
WshShell.Run "net stop wuauserv",0, true
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\WUServer", myserver
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\WUStatusServer", myserver
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\AUOptions", 4,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\NoAutoUpdate", 0,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\ScheduledInstallDay", 0,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\ScheduledInstallTime", starttime,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\RescheduleWaitTime", 1,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\NoAutoRebootWithLoggedOnUsers", 1,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer", 1,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\AUState", 2,"REG_DWORD"
WshShell.RegWrite "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\AUOptions", 4,"REG_DWORD"
WshShell.RegDelete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\LastWaitTimeout"
WshShell.Run "net start wuauserv",0, true
Do While val <> &quot;5&quot;
  i = i + 1
  val=WshShell.RegRead (&quot;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\AUState&quot;)
  WScript.Sleep 1000
if i > 600 then
	exit do
end if
Loop
WshShell.Run &quot;net stop wuauserv&quot;,0, true
WshShell.RegWrite &quot;HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\ScheduledInstallDate&quot;,olddate
WshShell.Run &quot;net start wuauserv&quot;,0, true
'----------END CODE-----------
 
ok can you help me out here... Either I'm doing something really stupid or this script isn't working. I copied the script into a txt file and renamed it testscript.wsh also renamed the server to the correct name. When I run the script I get a windows script host error that says there is no script specified. Do I need to install to make this work?
 
I wasn't able to get the script working but I did make the reg enties manually and they seemed to work. Do the clients access the microsoft windows update page before they talk to the sus server? Here is a copy of a section of the windowsupdate log.

2003-12-16 17:04:39 22:04:39 Success IUENGINE Starting
2003-12-16 17:04:39 22:04:39 Success IUENGINE Determining machine configuration
2003-12-16 17:04:39 22:04:39 Success IUENGINE Determining machine configuration
2003-12-16 17:04:45 22:04:45 Success IUENGINE Querying software update catalog from 2003-12-16 17:04:49 22:04:49 Success IUENGINE Querying software update catalog from 2003-12-16 17:04:52 22:04:52 Success IUENGINE Querying software update catalog from 2003-12-16 17:05:33 22:05:33 Success IUENGINE Querying software update catalog from 2003-12-16 17:05:36 22:05:36 Success IUENGINE Determining machine configuration
2003-12-16 17:05:38 22:05:38 Success IUENGINE Querying software update catalog from 2003-12-16 17:06:00 22:06:00 Success IUENGINE Shutting down
2003-12-16 17:06:00 22:06:00 Success IUCTL Shutting down
2003-12-16 16:44:57 21:44:57 Success IUCTL Starting
2003-12-16 16:44:58 21:44:58 Success IUCTL Downloaded iuident.cab from to C:\Program Files\WindowsUpdate\V4
2003-12-16 16:44:58 21:44:58 Success IUENGINE Starting
2003-12-16 16:44:58 21:44:58 Success IUENGINE Determining machine configuration
2003-12-16 16:44:58 21:44:58 Success IUENGINE Querying software update catalog from 2003-12-16 16:44:58 21:44:58 Success IUENGINE Determining machine configuration
2003-12-16 16:44:59 21:44:59 Success IUENGINE Querying software update catalog from 2003-12-16 16:44:59 21:44:59 Success IUENGINE Determining machine configuration
2003-12-16 16:44:59 21:44:59 Success IUENGINE Querying software update catalog from 2003-12-16 16:44:59 21:44:59 Success IUENGINE Determining machine configuration
2003-12-16 16:45:00 21:45:00 Success IUENGINE Querying software update catalog from 2003-12-16 16:45:01 21:45:01 Success IUENGINE Determining machine configuration
2003-12-16 16:45:01 21:45:01 Error IUENGINE Querying software update catalog from (Error 0x80190194)
2003-12-16 16:45:01 21:45:01 Success IUENGINE Shutting down
2003-12-16 16:45:01 21:45:01 Success IUCTL Shutting down
2003-12-16 23:04:59 04:04:59 Success IUCTL Starting
2003-12-16 23:04:59 04:04:59 Success IUENGINE Starting
2003-12-16 23:04:59 04:04:59 Success IUCTL Starting
2003-12-16 23:04:59 04:04:59 Success IUENGINE Starting
2003-12-16 23:05:00 04:05:00 Success IUENGINE Shutting down
2003-12-16 23:05:00 04:05:00 Success IUCTL Shutting down
2003-12-16 23:05:00 04:05:00 Success IUENGINE Install started

As you can see it queried the windows udate catalog before attempting to talk to the sus server. Do the clients need an internet connection for this to work. Plus any info on what I'm doing wrong with the script would be appreciated.
 
I got the script working and I got the manual entries working Thanks.. I might be note worthy to mention that one of the main issues I was having was that I wasn't stopping and starting the service when I was doing manual entries. Once I started playing with that I was able to get the updates to happen right away

thank you

 
Not really related to the thread but if SUS is running in a domain and the group policies to specify an intranet update server are set, is a reg edit still required to get it to work.
 
No Figaz, the clients have no contact anylonger with windowsupdate anymore they should be directed to the SUS server, the clients don't even need internet connection to get the updates they just have to be in the same LAN (Local Area Network) and if you have AD (Active Directory) and you are using GPO ( Group Policy Object) you can use AD/GPO to do everything from a central location you don't have to do it manually..

cheers for now,
 
No Apedescendant, when you use the group policy in AD you do not need to make the changes to the registry. It will get updated on a Group Policy refresh.
 
agbor,
Where do you set it in the Group policy for SUS? Thanks so much.
 
agbor,
Nevermind, i got the sus working. Group policy directions are in the SUS_Deployguide_sp1.doc from microsoft, i think it was on page 49. Thanks anyways.
 
I'm not using a domain. I am running this in a peer to peer envionment. I may move the server over to be my PDC but at the moment i just want to use this to update brand new systems before we ship them. I have a dial-up connection and we are trying to speed up the process of getting pc's out the door. In my office where we have highspeed I got the server working fine and had the clients updating without any problems. Once I shut down the server and brought it to the shop I got an sus server error when it was starting up. Now I can't get into the susadmin screen through internet explorer and am at a loss. The log files aren't telling me much. Any suggestions?
 
do you reset this back to norm before the customer gets them ?

like will they always be looking for your sus ?
 
if you remove the registry entries I created then it will look to the windows update server not sus
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top