Software Update Service

I am struggling to get this set up, and I normally get things running pretty
fast. I have the following registry keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\WindowsUpdate]
"WUServer"="http://ESISRSD1.xxx.xxx.com"
"WUStatusServer"="http://ESISRSD1.xxx.xxx.com"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\WindowsUpdate\AU]
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"UseWUServer"=dword:00000001
"RescheduleWaitTime"=dword:00000001
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000002
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000017

My Windows Update.Log shows:
2004-09-16 17:05:58 22:05:58 Success IUCTL Starting
2004-09-16 17:05:59 22:05:59 Success IUCTL Downloaded
iuident.cab from http://www.windowsupdate.com/v4/ to C:\Program
Files\WindowsUpdate\V4
2004-09-16 17:05:59 22:05:59 Success IUCTL Current
iuengine.dll version: 5.4.3790.21
2004-09-16 17:05:59 22:05:59 Success IUCTL Current iuctl.dll
version: 5.4.3790.20
2004-09-16 17:05:59 22:05:59 Success IUENGINE Starting
2004-09-16 17:05:59 22:05:59 Error IUENGINE Library download
error. Will retry. (Error 0x80190191)
2004-09-16 17:05:59 22:05:59 Error IUENGINE Library download
error. Will retry. (Error 0x80190191)
2004-09-16 17:05:59 22:05:59 Error IUENGINE Library download
error. Will retry. (Error 0x80190191)
2004-09-16 17:05:59 22:05:59 Success IUENGINE Determining machine
configuration
2004-09-16 17:06:00 22:06:00 Success IUENGINE Determining machine
configuration
2004-09-16 17:06:04 22:06:04 Success IUENGINE Shutting down
2004-09-16 17:06:04 22:06:04 Success IUCTL Shutting down

So, it doesn't look as if it is communicating with my SUS Server, correct?
Do you need to have the BITS service running. I did turn it on.

I must be missing something big. What could it be? HELPPPPP!!!

Hi

This *might* be your issue, from a previous post in the
microsoft.public.softwareupdatesvcs newsgroup:


From: ("Chris Ard [MSFT]")
Date: Tue, 31 Aug 2004 20:41:04 GMT
Subject: RE: Clients have two log files "Windows Update.log" & "Windowsupda
Message-ID: <>
Newsgroups: microsoft.public.softwareupdatesvcs

</quote>
Check the following registry key. If it does not exist, create it.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\
Auto Update]
"SusServerVersion" = REG_DWORD: 0x00000001 (1)

If this key does not exist or is not set to 1, then the v5 client appears
to use Windowsupdate instead of SUS
</quote>


Fyi, there is a separate newsgroup for SUS:

microsoft.public.softwareupdatesvcs

news://msnews.microsoft.com/microsof...wareupdatesvcs

URL to the group softwareupdatesvcs for those who uses the Web
interface to access the newsgroups:
http://www.microsoft.com/windowsserv...wareupdatesvcs

A Web site about SUS with a FAQ and a SUS forum:
http://www.susserver.com/

More SUS Web sites:
http://www.cites.uiuc.edu/sus/faq.html
http://www.faqshop.com/sus/default.htm



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

What is the difference between Windows Update and SUS? Is it that Windows
Update is when PC's goes directly to Microsoft for updates, and SUS is when
PC's go to an internal web server for updates? I assumed that if you are
using SUS that you still need the Automatic Updates and BITS services
running. Is this correct? Also, how is the registry key mentioned below
supposed to get in the registry for the client PC's? Our client PC's are
running W2K SP3, and I read that this is all you needed to run SUS. Please
unconfuse me. Thanks for all of your help!

"Torgeir Bakken (MVP)" wrote:

> Hi
>
> This *might* be your issue, from a previous post in the
> microsoft.public.softwareupdatesvcs newsgroup:
>
>
> From: ("Chris Ard [MSFT]")
> Date: Tue, 31 Aug 2004 20:41:04 GMT
> Subject: RE: Clients have two log files "Windows Update.log" & "Windowsupda
> Message-ID: <>
> Newsgroups: microsoft.public.softwareupdatesvcs
>
> </quote>
> Check the following registry key. If it does not exist, create it.
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\
> Auto Update]
> "SusServerVersion" = REG_DWORD: 0x00000001 (1)
>
> If this key does not exist or is not set to 1, then the v5 client appears
> to use Windowsupdate instead of SUS
> </quote>
>
>
> Fyi, there is a separate newsgroup for SUS:
>
> microsoft.public.softwareupdatesvcs
>
> news://msnews.microsoft.com/microsof...wareupdatesvcs
>
> URL to the group softwareupdatesvcs for those who uses the Web
> interface to access the newsgroups:
> http://www.microsoft.com/windowsserv...wareupdatesvcs
>
> A Web site about SUS with a FAQ and a SUS forum:
> http://www.susserver.com/
>
> More SUS Web sites:
> http://www.cites.uiuc.edu/sus/faq.html
> http://www.faqshop.com/sus/default.htm
>
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Kathy L. wrote:

> What is the difference between Windows Update and SUS? Is it that
> Windows Update is when PC's goes directly to Microsoft for updates,
> and SUS is when PC's go to an internal web server for updates?

That is pretty much it, but it is more correct to compare Automatic
Updates with SUS, because SUS does not have a GUI front end for the
end user as Windows Updates have.


> I assumed that if you are using SUS that you still need the
> Automatic Updates and BITS services running. Is this correct?

That is correct :-)


> Also, how is the registry key mentioned below supposed to get in
> the registry for the client PC's? Our client PC's are running
> W2K SP3, and I read that this is all you needed to run SUS.

This is a bug introduced with the WU v5 client component I think.
Microsoft have not published any details around this as far as I know.
If the registry value solves your update problem, I am afraid you will
need to deploy that registry value yourself to all the clients, in
some way or another.

If this is a big issue for you, you might want to open a support case
with Microsoft Product Support Services and see what they can come up
with: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

Alternatively, if you need to add this registry value to the registry
to solve the problem, you could post a request for clarification in
the microsoft.public.softwareupdatesvcs group and hope that you get an
answer from a Microsoft person (they pop in there and answers question
now and then).



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Thank you very much!

"Torgeir Bakken (MVP)" wrote:

> Kathy L. wrote:
>
> > What is the difference between Windows Update and SUS? Is it that
> > Windows Update is when PC's goes directly to Microsoft for updates,
> > and SUS is when PC's go to an internal web server for updates?
>
> That is pretty much it, but it is more correct to compare Automatic
> Updates with SUS, because SUS does not have a GUI front end for the
> end user as Windows Updates have.
>
>
> > I assumed that if you are using SUS that you still need the
> > Automatic Updates and BITS services running. Is this correct?
>
> That is correct :-)
>
>
> > Also, how is the registry key mentioned below supposed to get in
> > the registry for the client PC's? Our client PC's are running
> > W2K SP3, and I read that this is all you needed to run SUS.
>
> This is a bug introduced with the WU v5 client component I think.
> Microsoft have not published any details around this as far as I know.
> If the registry value solves your update problem, I am afraid you will
> need to deploy that registry value yourself to all the clients, in
> some way or another.
>
> If this is a big issue for you, you might want to open a support case
> with Microsoft Product Support Services and see what they can come up
> with: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
>
> Alternatively, if you need to add this registry value to the registry
> to solve the problem, you could post a request for clarification in
> the microsoft.public.softwareupdatesvcs group and hope that you get an
> answer from a Microsoft person (they pop in there and answers question
> now and then).
>
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

I guess I have 1 more question. How do I know if I am running the V5 client?

"Torgeir Bakken (MVP)" wrote:

> Kathy L. wrote:
>
> > What is the difference between Windows Update and SUS? Is it that
> > Windows Update is when PC's goes directly to Microsoft for updates,
> > and SUS is when PC's go to an internal web server for updates?
>
> That is pretty much it, but it is more correct to compare Automatic
> Updates with SUS, because SUS does not have a GUI front end for the
> end user as Windows Updates have.
>
>
> > I assumed that if you are using SUS that you still need the
> > Automatic Updates and BITS services running. Is this correct?
>
> That is correct :-)
>
>
> > Also, how is the registry key mentioned below supposed to get in
> > the registry for the client PC's? Our client PC's are running
> > W2K SP3, and I read that this is all you needed to run SUS.
>
> This is a bug introduced with the WU v5 client component I think.
> Microsoft have not published any details around this as far as I know.
> If the registry value solves your update problem, I am afraid you will
> need to deploy that registry value yourself to all the clients, in
> some way or another.
>
> If this is a big issue for you, you might want to open a support case
> with Microsoft Product Support Services and see what they can come up
> with: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
>
> Alternatively, if you need to add this registry value to the registry
> to solve the problem, you could post a request for clarification in
> the microsoft.public.softwareupdatesvcs group and hope that you get an
> answer from a Microsoft person (they pop in there and answers question
> now and then).
>
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Kathy L. wrote:

> I guess I have 1 more question. How do I know if I am
> running the V5 client?
Hi

If you find the folder %windir%\SoftwareDistribution\, you have V5.

(%windir% is typically C:\Windows)

You might want to take a look at this thread as well from the
microsoft.public.softwareupdatesvcs newsgroup:

http://groups.google.com/groups?thre...tngp13.phx.gbl


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx