Vista Update Loop

We run WSUS on a network to update computers and just now are running into
the problem. Needless to say it is frustrating to spend a day reinstalling
software, calling software companies and asking someone who hardly speaks
English to reactivate software that has alread been activated and convincing
them that you are not stealing their software -- and at the same time try to
make a living. Vista has been a bad experience.
--
RES

[[ Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]

rsiferd wrote:
> We run WSUS on a network to update computers and just now are running into
> the problem. Needless to say it is frustrating to spend a day reinstalling
> software, calling software companies and asking someone who hardly speaks
> English to reactivate software that has alread been activated and
> convincing
> them that you are not stealing their software -- and at the same time try
> to
> make a living. Vista has been a bad experience.

--
RES


"PA Bear [MS MVP]" wrote:

> [[ Right pew, wrong church. Forwarded to WSUS newsgroup
> (microsoft.public.windows.server.update_services) via crosspost as a
> convenience to OP.
>
> On the web:
> http://www.microsoft.com/communities...pdate_services
>
> In your newsreader:
> news://msnews.microsoft.com/microsof...pdate_services
> ]]
>
> rsiferd wrote:
> > We run WSUS on a network to update computers and just now are running into
> > the problem. Needless to say it is frustrating to spend a day reinstalling
> > software, calling software companies and asking someone who hardly speaks
> > English to reactivate software that has alread been activated and
> > convincing
> > them that you are not stealing their software -- and at the same time try
> > to
> > make a living. Vista has been a bad experience.
>
> Sorry pal, but the issue is not WSUS. The issue is the update.

rsiferd wrote:
>> [[ Right pew, wrong church. Forwarded to WSUS newsgroup
>> (microsoft.public.windows.server.update_services) via crosspost as a
>> convenience to OP.
>>
>> On the web:
>> http://www.microsoft.com/communities...pdate_services
>>
>> In your newsreader:
>> news://msnews.microsoft.com/microsof...pdate_services
>> ]]
>>
>> rsiferd wrote:
>>> We run WSUS on a network to update computers and just now are running
>>> into
>>> the problem. Needless to say it is frustrating to spend a day
>>> reinstalling
>>> software, calling software companies and asking someone who hardly
>>> speaks
>>> English to reactivate software that has alread been activated and
>>> convincing
>>> them that you are not stealing their software -- and at the same time
>>> try
>>> to
>>> make a living. Vista has been a bad experience.
>>
>> Sorry pal, but the issue is not WSUS. The issue is the update.

What update? How have you determined that WSUS is not involved with the
problem if it's the default update source? (If you're using WSUS, the
WSUS-specific newsgroup is where you should be seeking help.)

"PA Bear [MS MVP]" <> wrote in message
news:...

> rsiferd wrote:

>> We run WSUS on a network to update computers and just now are running
>> into
>> the problem. Needless to say it is frustrating to spend a day
>> reinstalling
>> software, calling software companies and asking someone who hardly speaks
>> English to reactivate software that has alread been activated and
>> convincing
>> them that you are not stealing their software -- and at the same time try
>> to
>> make a living. Vista has been a bad experience.

> Sorry pal, but the issue is not WSUS. The issue is the update.

> What update? How have you determined that WSUS is not involved with the
> problem if it's the default update source? (If you're using WSUS, the
> WSUS-specific newsgroup is where you should be seeking help.)

I'm not sure how anybody is even supposed to identify the issue -- given
that there isn't a single *question* in the original post! (That would be --
the post that was crossposted into the update_services newsgroup -- which
based on the remainder of this thread appears to have been crossposted
mid-thread, which is certainly no help to those of us in the update_services
newsgroup who have no history on the thread.)

Nor is it even possible to determine what the subject update is in this
instance.


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence Garvin (MVP) wrote:
>> rsiferd wrote:
>
>>> We run WSUS on a network to update computers and just now are running
>>> into
>>> the problem. Needless to say it is frustrating to spend a day
>>> reinstalling
>>> software, calling software companies and asking someone who hardly
>>> speaks
>>> English to reactivate software that has alread been activated and
>>> convincing
>>> them that you are not stealing their software -- and at the same time
>>> try
>>> to
>>> make a living. Vista has been a bad experience.
>
>> Sorry pal, but the issue is not WSUS. The issue is the update.
>
>> What update? How have you determined that WSUS is not involved with the
>> problem if it's the default update source? (If you're using WSUS, the
>> WSUS-specific newsgroup is where you should be seeking help.)
>
> I'm not sure how anybody is even supposed to identify the issue -- given
> that there isn't a single *question* in the original post! (That would
> be --
> the post that was crossposted into the update_services newsgroup -- which
> based on the remainder of this thread appears to have been crossposted
> mid-thread, which is certainly no help to those of us in the
> update_services
> newsgroup who have no history on the thread.)
>
> Nor is it even possible to determine what the subject update is in this
> instance.

My first reply included OP's original post in WU newsgroup. It's quoted
above in its entirety.
--
~Robear

"PA Bear [MS MVP]" <> wrote in message
news:O4$...

>>> rsiferd wrote:
>>
>>>> We run WSUS on a network to update computers and just now are running
>>>> into
>>>> the problem. Needless to say it is frustrating to spend a day
>>>> reinstalling
>>>> software, calling software companies and asking someone who hardly
>>>> speaks
>>>> English to reactivate software that has alread been activated and
>>>> convincing
>>>> them that you are not stealing their software -- and at the same time
>>>> try
>>>> to
>>>> make a living. Vista has been a bad experience.
>>
>>> Sorry pal, but the issue is not WSUS. The issue is the update.
>>
>>> What update? How have you determined that WSUS is not involved with the
>>> problem if it's the default update source? (If you're using WSUS, the
>>> WSUS-specific newsgroup is where you should be seeking help.)
>>
>> I'm not sure how anybody is even supposed to identify the issue -- given
>> that there isn't a single *question* in the original post! (That would
>> be --
>> the post that was crossposted into the update_services newsgroup -- which
>> based on the remainder of this thread appears to have been crossposted
>> mid-thread, which is certainly no help to those of us in the
>> update_services
>> newsgroup who have no history on the thread.)
>>
>> Nor is it even possible to determine what the subject update is in this
>> instance.
>
> My first reply included OP's original post in WU newsgroup. It's quoted
> above in its entirety.

Which *still* does not contain a QUESTION!

What, pray tell, is the *TOPIC* of this thread?

And, to be thorough... based on those six original lines (and thusly
confirmed by the O.P.s subsequent response),
On what information was based the belief that this question related to
WSUS in any fashion at all?

I'd love to answer the question.... I simply don't have a clue what the
question is!

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

rsiferd wrote:

> Sorry pal, but the issue is not WSUS. The issue is the update.

Are you sure? Have you tried installing the update by hand?

We'd have a better shot of addressing your problem if you tell us which update
and what the problem is.

Harry.