My question directly involves Enabling or Disabling Automatic Updates. 
I'm busy with a roll-out of round 350 - 400 PC's onto XP. I'm using PowerQuest Drive 
Image to Automize my proces. I'm also making use of Wise installs to install all 
my software. That said, I am also disabling Automatic Updates on all PC's, to avoid:
1) Network Traffic when a new update occurs. 
2) Avoiding unstable machines with bad MS updates.

My question however is that I find the concept good, but would much rather put my 
own server down in the local network ,so that I can 
1) Evaluate updates of MS first and 
2) Avoid Network traffic and 
3) Do updates when the network is least used.

My problem however is that MS does not provide me with settings to be able to redirect 
the request to my own designated server.
 Can you help??

[Reply or follow-up to this message]

On Tuesday, April 16, 2002 at 7:00 am, Marinus de Bruyne wrote:

>My question directly involves Enabling or Disabling Automatic Updates. 
>I'm busy with a roll-out of round 350 - 400 PC's onto XP. I'm using PowerQuest Drive 
>Image to Automize my proces. I'm also making use of Wise installs to install all 
>my software. That said, I am also disabling Automatic Updates on all PC's, to avoid:
>1) Network Traffic when a new update occurs. 
>2) Avoiding unstable machines with bad MS updates.
>
>My question however is that I find the concept good, but would much rather put my 
>own server down in the local network ,so that I can 
>1) Evaluate updates of MS first and 
>2) Avoid Network traffic and 
>3) Do updates when the network is least used.
>
>My problem however is that MS does not provide me with settings to be able to redirect 
>the request to my own designated server.
> Can you help??
>

[Reply or follow-up to this message]

On Tuesday, August 13, 2002 at 8:05 am, Wilson wrote:
>On Tuesday, April 16, 2002 at 7:00 am, Marinus de Bruyne wrote:
>My question however is that I find the concept good, but would much rather put my
>own server down in the local network ,so that I can
>1) Evaluate updates of MS first and
>2) Avoid Network traffic and
>3) Do updates when the network is least used.

What you just described is Software Update Services (SUS) and Auto Update (AU). Info is at
http://www.microsoft.com/windows2000/windowsupdate/sus/default.asp

I'm still in the testing phases of my deployment, but it seems pretty nice, you have to do some registry hacking to make it the AU look at your internal server (or bang out a group policy). The MS papers at the above link will do a better job of explaining it that I. Happy reading.

Oh, and if you check that out, maybe you can answer a question for me ;-) how do I force the AU to check its SUS server? I can find a "Update now" feature, I can only change its scheduling... or maybe I'm just slow

[Reply or follow-up to this message]

WOW, I just found out about the SUS today myself. I found an article refering to Window Update Corporate edition, followed the link to Microsoft's site where I found out MS now calls it the SUS. I downloaded the tools and will be evaluating next week. As for the AutoUpdate feature, I believe I read WIN2K with SP3 and WINXP with SP1 will not require the client. Also, these SP's will allow the pc's to automatically update via the SUS service (I THINK). AND, I found a product that will monitor, assess, and distribute any update to any client...but at a cost. The software was nearly $8,600 for an 800 client version. I'll look up the name when I get back to work Monday for you. BUT, the good news is I rembered the link to a GREAT FREE tool...find out more here: http://www.ecora.com/ecora/products/patchmeister/default.asp Till then, take care.


On Friday, August 16, 2002 at 1:23 pm, karl wrote:
>
>
>

[Reply or follow-up to this message]

For those of you who want to redirect Windows Update Automatic Updates to your own SUS server, you do this in Active Directory or Group Policy on your domain controller. (If you don't know what any of those items are, you probably need more help than this info). You will want MSKB article Q328010 (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q328010). I was able to set up these policies in just a few minutes. My issue stems from a different subset of this problem... once I did them, they don't apply because the users don't have administrator rights on their systems to change the automatic update features. You'd think MS would have addressed that in the policy settings.... Good luck to all. Mike


On Friday, August 16, 2002 at 6:04 pm, Wilson wrote:
>WOW,
>
>I just found out about the SUS today myself. I found an article refering to Window
>Update Corporate edition, followed the link to Microsoft's site where I found out
>MS now calls it the SUS.
>
>I downloaded the tools and will be evaluating next week.
>
>As for the AutoUpdate feature, I believe I read WIN2K with SP3 and WINXP with SP1
>will not require the client. Also, these SP's will allow the pc's to automatically
>update via the SUS service (I THINK).
>
>AND, I found a product that will monitor, assess, and distribute any update to any
>client...but at a cost. The software was nearly $8,600 for an 800 client version.
> I'll look up the name when I get back to work Monday for you.
>
>BUT, the good news is I rembered the link to a GREAT FREE tool...find out more here:
>http://www.ecora.com/ecora/products/patchmeister/default.asp
>
>Till then, take care.
>
>

[Reply or follow-up to this message]

I see it works for everyone, but in my case. I've installed a W2K server from a scratch, installed IIS according to SUS deployment guide, update registry for the [test] clients (as I have no AD) - and nothing happens. SUS server denyes everybody's logon. What's the catch? I'll really appreciate any help/hint in this


On Wednesday, November 27, 2002 at 10:42 am, Mike wrote:
>For those of you who want to redirect Windows Update Automatic Updates to your own
>SUS server, you do this in Active Directory or Group Policy on your domain controller.
>(If you don't know what any of those items are, you probably need more help than
>this info).
>
>You will want MSKB article Q328010
>(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q328010).
>
>I was able to set up these policies in just a few minutes. My issue stems from a
>different subset of this problem... once I did them, they don't apply because the
>users don't have administrator rights on their systems to change the automatic update
>features. You'd think MS would have addressed that in the policy settings....
>
>Good luck to all.
>Mike
>
>
>

[Reply or follow-up to this message]

I installed SUS to a fresh install of Win 2K server. I then did the registry edit on several client systems for I do not have active dir. going in my domain. All is working ok, clients with-in and outside of my domain are able to use my SUS server. On the SUS server in the setup section you need to state what the client system will use as a name to point to your SUS server, check this and make sure it matches what you set your WUserver name to in the registry of your client systems. email me if you still have problems and I will supply you with the .reg file I used, should work for you ok. Now I am trying to have my client system download and install patches automatically, the download is working but they still wait for the administrator to install......edelen@ssdd.nrl.navy.mil


On Thursday, November 28, 2002 at 12:50 am, Korkin wrote:
>I see it works for everyone, but in my case. I've installed a W2K server from a scratch,
>installed IIS according to SUS deployment guide, update registry for the [test] clients
>(as I have no AD) - and nothing happens. SUS server denyes everybody's logon. What's
>the catch? I'll really appreciate any help/hint in this
>
>

[Reply or follow-up to this message]

Hi Keech Thanks for your responce. I've re-installed the server ( although I'm 100% sure that the first installation was flawless), and after a day or two it started to work. The error I was recieving was 407:Proxy auth.requiered. Beats me - we don't have proxy inside. About your install-nodownload : I think it happens if a local administrator is logged in. Because I definitely had some clients to install and re-boot - all by themselves. If you have further questions, or have a hint what was wrong in my (and your) case, feel free to e-mail me. Thanks

[Reply or follow-up to this message]

Hello Mike, It seems that you can maybe help me on setting the rights values in my registry for using a sus server.... I've installed sus and it seems to work but I'm not sure in configuring my clients (Win2k in a non AD). I cannot find the following Key : HKeyLocalMachine\Software\Policies\Microsoft\Windows\WindowsUpdate Should I create it ? For your information, I opened my Firewall in order to download the latests SP and Security Patches and I'm up to date with my clients.... Thanks very much for your help Olivier Bourqui / Switzerland....

[Reply or follow-up to this message]

This only explains how to configure the AU client, not how to get the manual Windows 
Update (IE) function to point to the SUS server.  Again even if this did work, the 
users most likely won't (and shouldn't) have rights to install the updates.






On Wednesday, November 27, 2002 at 10:42 am, Mike wrote:
>For those of you who want to redirect Windows Update Automatic Updates to your own 
>SUS server, you do this in Active Directory or Group Policy on your domain controller. 
>(If you don't know what any of those items are, you probably need more help than 
>this info).
>
>You will want MSKB article Q328010
>(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q328010).
>
>I was able to set up these policies in just a few minutes. My issue stems from a 
>different subset of this problem... once I did them, they don't apply because the 
>users don't have administrator rights on their systems to change the automatic update 
>features. You'd think MS would have addressed that in the policy settings....
>
>Good luck to all.
>Mike
>
>
>

[Reply or follow-up to this message]

i want to have a control on enabling and diabling the automatic update message


On Tuesday, April 16, 2002 at 7:00 am, Marinus de Bruyne wrote:
>
>My question directly involves Enabling or Disabling Automatic Updates.
>I'm busy with a roll-out of round 350 - 400 PC's onto XP. I'm using PowerQuest Drive
>Image to Automize my proces. I'm also making use of Wise installs to install all
>my software. That said, I am also disabling Automatic Updates on all PC's, to avoid:
>1) Network Traffic when a new update occurs.
>2) Avoiding unstable machines with bad MS updates.
>
>My question however is that I find the concept good, but would much rather put my
>own server down in the local network ,so that I can
>1) Evaluate updates of MS first and
>2) Avoid Network traffic and
>3) Do updates when the network is least used.
>
>My problem however is that MS does not provide me with settings to be able to redirect
>the request to my own designated server.
> Can you help??

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum