Can't download updates from upstream server if they aren't approve

I can't understand why it's taking 3 versions to get this software where it
should of been on the first version. And it still does not seem to be there
yet. Maybe they should charge for this software, then perhaps they will have
more of a reason to make this simple and effective!!!! Anyway, enough
venting...

The problem is this, I have about 21 servers at remote locations running
WSUS 3.0. I have a server at the main office running WSUS 3.0. The server
at the main site I want to be the only server to get the updates directly
from MS website. The other servers are configured to have the server at the
main site be the upstream server, but not replicas. This works good, except,
if I have an update needed on a downstream server and that update was not
needed on the main upstream server, then the update get's approved on the
downstream server, but when it tries to download it, it fails, because the
upstream server never had it downloaded since it never needed it. Someone
then may say I need to make the downstream servers replica servers. Well
this would be fine and dandy if the replica wouldn't download every updated
ever requested by every client in the whole environment!!!! Basically I
would have to upgrade tons of hard disks to accomidate updates to be stored
on servers that don't need them! How can I make the upstream server download
an update that is requested by a downstream server if the downstream server
is not a replica but using the upstream server instead of going to MS website
directly.

Does this make sense?

Thanks,
Louis

Forwarded to WSUS newsgroup via crosspost.
--
~PA Bear

Louis wrote:
> I can't understand why it's taking 3 versions to get this software where
> it
> should of been on the first version. And it still does not seem to be
> there
> yet. Maybe they should charge for this software, then perhaps they will
> have more of a reason to make this simple and effective!!!! Anyway,
> enough
> venting...
>
> The problem is this, I have about 21 servers at remote locations running
> WSUS 3.0. I have a server at the main office running WSUS 3.0. The
> server
> at the main site I want to be the only server to get the updates directly
> from MS website. The other servers are configured to have the server at
> the
> main site be the upstream server, but not replicas. This works good,
> except, if I have an update needed on a downstream server and that update
> was not needed on the main upstream server, then the update get's approved
> on the downstream server, but when it tries to download it, it fails,
> because the upstream server never had it downloaded since it never needed
> it. Someone then may say I need to make the downstream servers replica
> servers. Well this would be fine and dandy if the replica wouldn't
> download every updated ever requested by every client in the whole
> environment!!!! Basically I would have to upgrade tons of hard disks to
> accomidate updates to be stored on servers that don't need them! How can
> I
> make the upstream server download an update that is requested by a
> downstream server if the downstream server is not a replica but using the
> upstream server instead of going to MS website directly.
>
> Does this make sense?
>
> Thanks,
> Louis

Where Do I see that? I thought I was in the WSUS newsgroup. Now I find the
Software Update Services newsgroup and I do not see my post in there. Did it
get forwarded properly?

"PA Bear" wrote:

> Forwarded to WSUS newsgroup via crosspost.
> --
> ~PA Bear
>
> Louis wrote:
> > I can't understand why it's taking 3 versions to get this software where
> > it
> > should of been on the first version. And it still does not seem to be
> > there
> > yet. Maybe they should charge for this software, then perhaps they will
> > have more of a reason to make this simple and effective!!!! Anyway,
> > enough
> > venting...
> >
> > The problem is this, I have about 21 servers at remote locations running
> > WSUS 3.0. I have a server at the main office running WSUS 3.0. The
> > server
> > at the main site I want to be the only server to get the updates directly
> > from MS website. The other servers are configured to have the server at
> > the
> > main site be the upstream server, but not replicas. This works good,
> > except, if I have an update needed on a downstream server and that update
> > was not needed on the main upstream server, then the update get's approved
> > on the downstream server, but when it tries to download it, it fails,
> > because the upstream server never had it downloaded since it never needed
> > it. Someone then may say I need to make the downstream servers replica
> > servers. Well this would be fine and dandy if the replica wouldn't
> > download every updated ever requested by every client in the whole
> > environment!!!! Basically I would have to upgrade tons of hard disks to
> > accomidate updates to be stored on servers that don't need them! How can
> > I
> > make the upstream server download an update that is requested by a
> > downstream server if the downstream server is not a replica but using the
> > upstream server instead of going to MS website directly.
> >
> > Does this make sense?
> >
> > Thanks,
> > Louis
>
>

You originally posted to the Windows Update newsgroup.

I crossposted my reply to the WSUS newsgroup, not your original message.
Replies sent from WSUS newsgroup will be posted to both newsgroups.

The thread subject "Can't download updates from upstream server..." will be
seen in both newsgroups, Louis.
--
~PA Bear


Louis wrote:
> Where Do I see that? I thought I was in the WSUS newsgroup. Now I find
> the
> Software Update Services newsgroup and I do not see my post in there. Did
> it get forwarded properly?
>
> "PA Bear" wrote:
>
>> Forwarded to WSUS newsgroup via crosspost.
>> --
>> ~PA Bear
>>
>> Louis wrote:
>>> I can't understand why it's taking 3 versions to get this software where
>>> it
>>> should of been on the first version. And it still does not seem to be
>>> there
>>> yet. Maybe they should charge for this software, then perhaps they will
>>> have more of a reason to make this simple and effective!!!! Anyway,
>>> enough
>>> venting...
>>>
>>> The problem is this, I have about 21 servers at remote locations running
>>> WSUS 3.0. I have a server at the main office running WSUS 3.0. The
>>> server
>>> at the main site I want to be the only server to get the updates
>>> directly
>>> from MS website. The other servers are configured to have the server at
>>> the
>>> main site be the upstream server, but not replicas. This works good,
>>> except, if I have an update needed on a downstream server and that
>>> update
>>> was not needed on the main upstream server, then the update get's
>>> approved
>>> on the downstream server, but when it tries to download it, it fails,
>>> because the upstream server never had it downloaded since it never
>>> needed
>>> it. Someone then may say I need to make the downstream servers replica
>>> servers. Well this would be fine and dandy if the replica wouldn't
>>> download every updated ever requested by every client in the whole
>>> environment!!!! Basically I would have to upgrade tons of hard disks to
>>> accomidate updates to be stored on servers that don't need them! How
>>> can
>>> I
>>> make the upstream server download an update that is requested by a
>>> downstream server if the downstream server is not a replica but using
>>> the
>>> upstream server instead of going to MS website directly.
>>>
>>> Does this make sense?
>>>
>>> Thanks,
>>> Louis

>> Louis wrote:
>> > I can't understand why it's taking 3 versions to get this software
>> > where
>> > it
>> > should of been on the first version. And it still does not seem to be
>> > there
>> > yet. Maybe they should charge for this software, then perhaps they
>> > will
>> > have more of a reason to make this simple and effective!!!!

Probably not.. it's even harder to get *free* support from *volunteers* when
you wear your attitude on your sleeve.

>> > Anyway, enough venting...

Absolutely! Shucks, I still haven't even read what your *problem* is!

>> > The problem is this, I have about 21 servers at remote locations
>> > running
>> > WSUS 3.0. I have a server at the main office running WSUS 3.0. The
>> > server
>> > at the main site I want to be the only server to get the updates
>> > directly
>> > from MS website. The other servers are configured to have the server
>> > at
>> > the
>> > main site be the upstream server, but not replicas. This works good,
>> > except, if I have an update needed on a downstream server and that
>> > update
>> > was not needed on the main upstream server, then the update get's
>> > approved
>> > on the downstream server, but when it tries to download it, it fails,
>> > because the upstream server never had it downloaded since it never
>> > needed
>> > it.

Yep.. this is by design.... it's documented... and it's been that way since
WSUS was released two years ago.

>> > Someone then may say I need to make the downstream servers replica
>> > servers.

No.. you just need to be patient. The upstream server will request the
content from microsoft, and the downstream server will get it on the next
sychronization. All of which is well documented in the WSUS Deployment
Guide.

>> > Well this would be fine and dandy if the replica wouldn't
>> > download every updated ever requested by every client in the whole
>> > environment!!!!

It only downloads what you have *approved* for installation.... but then
this discussion really isn't about replicas since you don't have one.. so
let's stick to the real scenario, shall we?

>> > Basically I would have to upgrade tons of hard disks to
>> > accomidate updates to be stored on servers that don't need them!

No.. you wouldn't.. but that's also covered in the WSUS Deployment Guide.
(You've not read it, have you? I can tell.)

>> > How can I
>> > make the upstream server download an update that is requested by a
>> > downstream server if the downstream server is not a replica but using
>> > the
>> > upstream server instead of going to MS website directly.

W A I T. That's how you do it.

Now, of course, the *upstream* server also has to be synchronized to get
those products, classifications, and languages that the downstream server
wants, or else they'll *never* be available.

From the Deployment Guide:
Important

When you configure a downstream server, you should make sure that the update
languages it supports are a subset of the languages supported on its
upstream server. If you choose a language on a downstream server that is not
supported on an upstream server, you will not be able to get updates in that
language. To remind you of this issue, a task will appear on the home page
of the downstream server.



--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/pr...2-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....


>>
>>

"Louis" <> wrote in message
news:0E4093A4-E657-4304-BF14-
> [X-Newsreader: Microsoft CDO for Windows 2000]
....

>> Forwarded to WSUS newsgroup via crosspost.


> Where Do I see that?


In the header? <eg>
Hint: click on the name of the newsgroup you want to read from.
Note: results depend on the web portal you are using.
Not all portals contain links to all newsgroup archives.


> I thought I was in the WSUS newsgroup. Now I find the
> Software Update Services newsgroup and I do not see my post in there. Did it
> get forwarded properly?


One of the reasons we cross-post is so the reader won't have to search
for a different newsgroup... ; }


HTH

Robert Aldwinckle
---