WSUS 3.0 Client PULL Duggan 59 6/28/2007 3:24:03 PM I tried this post earlier so, sorry for the repetition. We have just deployed a new WSUS 3.0 server and are testing it in an educational facility. We are experiencing about 20% success on the PUSH to clients. With all of issues we are reading about, I am trying to find another option for updating clients without having use Internet bandwidth for the updates. I am wodering if there is a client PULL from WSUS or another way of posting the Windows updates on a local server. Can this be done? Duggan

Re: WSUS 3.0 Client PULL "Ed Amrein" <eamrein[ at ]fujitecamerica.com> 6/28/2007 5:08:15 PM Just a note - WSUS does not push - clients pull.. Important detail when troubleshooting issues..:-} Do you have the WSUS server storing the content locally, or are your clients going to MS for the actual update? If you store the updates locally on the server, client pc's will connect to the server for the updates, saving some internet bandwidth... BigEd "Duggan 59" <duggan59[ at ]hotmail.com> wrote in message news:492C99F0-F7F3-4C72-96F5-23A72D189D33[ at ]microsoft.com... [Quoted Text] >I tried this post earlier so, sorry for the repetition. We have just > deployed a new WSUS 3.0 server and are testing it in an educational > facility. We are experiencing about 20% success on the PUSH to clients. > With > all of issues we are reading about, I am trying to find another option for > updating clients without having use Internet bandwidth for the updates. I > am > wodering if there is a client PULL from WSUS or another way of posting the > Windows updates on a local server. Can this be done? > > Duggan >

Re: WSUS 3.0 Client PULL Duggan 59 6/28/2007 6:26:02 PM The updates are on the local server. The WSUS is new technology for us so, we forced troubleshoot and we are running out of time. Our WSUS server probes the client and then feeds the update to the them. We have tryed clients in the same OU and even ran the GPUPDATE /FORCE. No change. This where I am looking for an option to guide the date to retirve the updates from the local server. Duggan "Ed Amrein" wrote: [Quoted Text] > Just a note - WSUS does not push - clients pull.. Important detail when > troubleshooting issues..:-} > Do you have the WSUS server storing the content locally, or are your clients > going to MS for the actual update? > If you store the updates locally on the server, client pc's will connect to > the server for the updates, saving some internet bandwidth... > > BigEd > > "Duggan 59" <duggan59[ at ]hotmail.com> wrote in message > news:492C99F0-F7F3-4C72-96F5-23A72D189D33[ at ]microsoft.com... > >I tried this post earlier so, sorry for the repetition. We have just > > deployed a new WSUS 3.0 server and are testing it in an educational > > facility. We are experiencing about 20% success on the PUSH to clients. > > With > > all of issues we are reading about, I am trying to find another option for > > updating clients without having use Internet bandwidth for the updates. I > > am > > wodering if there is a client PULL from WSUS or another way of posting the > > Windows updates on a local server. Can this be done? > > > > Duggan > > > > >

Re: WSUS 3.0 Client PULL Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/28/2007 8:26:54 PM Duggan 59 wrote: [Quoted Text] > The updates are on the local server. The WSUS is new technology for us so, we > forced troubleshoot and we are running out of time. Our WSUS server probes > the client and then feeds the update to the them. No, it really doesn't - this isn't how WSUS works. The server is entirely passive; it gives out information to the clients when they request it, and accepts information from the clients when offered it. You need to look at the clients that aren't updating to figure out what is going wrong. There are a number of possible issues; for instance, are they getting the group policy settings correctly? Look in the WindowsUpdate.log file (usually in c:\windows) on the client for clues. You should also run the client diagnostic tool available from here: <http://technet.microsoft.com/en-us/wsus/bb466192.aspx> If this doesn't help you find the problem, post the WindowsUpdate.log and the output from the client diagnostic tool and hopefully somebody will be able to see what is going wrong. A few questions first: you understand that under the normal operation of WSUS it may take a day or more for a client to receive an update? You realise that unless you've configured the clients to use scheduled updates, nothing will happen until an administrator logs in and clicks on the taskbar icon? Harry.

Re: WSUS 3.0 Client PULL Duggan 59 6/28/2007 9:20:04 PM Thanks. Again, this is brand new technology to us. I have one of my engineers working on this so, I am vague as to it's operation. I was not aware of the time frame for updates. That is really good info. I ma have been jumping the gun for progress. I have systems in the same room that clones of both hardware and software. Identical systems, side by side that are cloned and 1 will download right away and thother systems never even accesse the server. I will go back and power the system overnight and check the logs. I will post the results. Thanks, Duggan "Harry Johnston" wrote: [Quoted Text] > Duggan 59 wrote: > > > The updates are on the local server. The WSUS is new technology for us so, we > > forced troubleshoot and we are running out of time. Our WSUS server probes > > the client and then feeds the update to the them. > > No, it really doesn't - this isn't how WSUS works. The server is entirely > passive; it gives out information to the clients when they request it, and > accepts information from the clients when offered it. > > You need to look at the clients that aren't updating to figure out what is going > wrong. There are a number of possible issues; for instance, are they getting > the group policy settings correctly? > > Look in the WindowsUpdate.log file (usually in c:\windows) on the client for > clues. You should also run the client diagnostic tool available from here: > > <http://technet.microsoft.com/en-us/wsus/bb466192.aspx> > > If this doesn't help you find the problem, post the WindowsUpdate.log and the > output from the client diagnostic tool and hopefully somebody will be able to > see what is going wrong. > > A few questions first: you understand that under the normal operation of WSUS it > may take a day or more for a client to receive an update? You realise that > unless you've configured the clients to use scheduled updates, nothing will > happen until an administrator logs in and clicks on the taskbar icon? > > Harry. >

Re: WSUS 3.0 Client PULL "BigEd" <eamrein[ at ]fujitecamerica.com> 6/29/2007 12:20:56 PM If your systems are cloned, that could be a problem if they are not sysprepped properly. Every client must have a unique WSUS ID. If there are duplicate ID's client pc's will come and go from the WSUS server.. "Duggan 59" <duggan59[ at ]hotmail.com> wrote in message news:124F281F-276C-4995-820C-8836AA45C771[ at ]microsoft.com... [Quoted Text] > Thanks. Again, this is brand new technology to us. I have one of my > engineers > working on this so, I am vague as to it's operation. I was not aware of > the > time frame for updates. That is really good info. I ma have been jumping > the > gun for progress. I have systems in the same room that clones of both > hardware and software. Identical systems, side by side that are cloned and > 1 > will download right away and thother systems never even accesse the > server. I > will go back and power the system overnight and check the logs. I will > post > the results. > > Thanks, > Duggan > > "Harry Johnston" wrote: > >> Duggan 59 wrote: >> >> > The updates are on the local server. The WSUS is new technology for us >> > so, we >> > forced troubleshoot and we are running out of time. Our WSUS server >> > probes >> > the client and then feeds the update to the them. >> >> No, it really doesn't - this isn't how WSUS works. The server is >> entirely >> passive; it gives out information to the clients when they request it, >> and >> accepts information from the clients when offered it. >> >> You need to look at the clients that aren't updating to figure out what >> is going >> wrong. There are a number of possible issues; for instance, are they >> getting >> the group policy settings correctly? >> >> Look in the WindowsUpdate.log file (usually in c:\windows) on the client >> for >> clues. You should also run the client diagnostic tool available from >> here: >> >> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx> >> >> If this doesn't help you find the problem, post the WindowsUpdate.log and >> the >> output from the client diagnostic tool and hopefully somebody will be >> able to >> see what is going wrong. >> >> A few questions first: you understand that under the normal operation of >> WSUS it >> may take a day or more for a client to receive an update? You realise >> that >> unless you've configured the clients to use scheduled updates, nothing >> will >> happen until an administrator logs in and clicks on the taskbar icon? >> >> Harry. >>