Major problem with WSUS

[Guest Gunnertac]

I was out on vacation last week so NOBODY touched the WSUS server. It's my

baby. Apparently MS came out with KB917013 on 10/23. This kb installs Windows

Desktop Search 3.01. We did not have any pc in the company with Desktop

Search installed when I left and virtually everybody has it now upon my

return. Not only that, they also have a hotfix related to Desktop Search 3.01

(kb915800) installed as well. Of course, this bloody thing interferes with

one of our custom databases so now I have to uninstall from every single pc.

 

Two huge things came to light while searching for a smoking gun as to what

went wrong. In WSUS, I found KB917013 in the update database but it is listed

with a status of DECLINED. Also, a thorough search of the update database

yields nothing related to the hotfix--KB915800. This hotfix doesn't appear to

be in WSUS yet it is installed on all my pcs! There are only two people that

even have access to the WSUS server and both swear they didn't touch it in my

absence and I believe them. They wouldn't want to touch it because they don't

know anything about it.

 

Does anyone know how this could happen? Have you seen other instances where

updates are automatically applied prior to being approved? Is this a one time

deal with this particular Windows update? It is making me question the

decision to use WSUS. What other monstrous problems can be pushed down the

pipe? TIA for any help.

 

--

Tim

[Guest Gunnertac]

RE: Major problem with WSUS

 

Also...it's WSUS 3 all by itself on a Win2003 Server. SP2. By the way...the

desktop search engine also got installed on the WSUS server as well.

 

--

Tim

 

 

"Gunnertac" wrote:

> I was out on vacation last week so NOBODY touched the WSUS server. It's my

> baby. Apparently MS came out with KB917013 on 10/23. This kb installs Windows

> Desktop Search 3.01. We did not have any pc in the company with Desktop

> Search installed when I left and virtually everybody has it now upon my

> return. Not only that, they also have a hotfix related to Desktop Search 3.01

> (kb915800) installed as well. Of course, this bloody thing interferes with

> one of our custom databases so now I have to uninstall from every single pc.

>

> Two huge things came to light while searching for a smoking gun as to what

> went wrong. In WSUS, I found KB917013 in the update database but it is listed

> with a status of DECLINED. Also, a thorough search of the update database

> yields nothing related to the hotfix--KB915800. This hotfix doesn't appear to

> be in WSUS yet it is installed on all my pcs! There are only two people that

> even have access to the WSUS server and both swear they didn't touch it in my

> absence and I believe them. They wouldn't want to touch it because they don't

> know anything about it.

>

> Does anyone know how this could happen? Have you seen other instances where

> updates are automatically applied prior to being approved? Is this a one time

> deal with this particular Windows update? It is making me question the

> decision to use WSUS. What other monstrous problems can be pushed down the

> pipe? TIA for any help.

>

> --

> Tim

[Guest Gunnertac]

RE: Major problem with WSUS

 

Sorry for blasting this out so fast. A quick perusal of Google told me what

happened. Sheesh...

 

http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9044239&intsrc=hm_list

 

--

Tim

 

 

"Gunnertac" wrote:

> Also...it's WSUS 3 all by itself on a Win2003 Server. SP2. By the way...the

> desktop search engine also got installed on the WSUS server as well.

>

> --

> Tim

>

>

> "Gunnertac" wrote:

>

> > I was out on vacation last week so NOBODY touched the WSUS server. It's my

> > baby. Apparently MS came out with KB917013 on 10/23. This kb installs Windows

> > Desktop Search 3.01. We did not have any pc in the company with Desktop

> > Search installed when I left and virtually everybody has it now upon my

> > return. Not only that, they also have a hotfix related to Desktop Search 3.01

> > (kb915800) installed as well. Of course, this bloody thing interferes with

> > one of our custom databases so now I have to uninstall from every single pc.

> >

> > Two huge things came to light while searching for a smoking gun as to what

> > went wrong. In WSUS, I found KB917013 in the update database but it is listed

> > with a status of DECLINED. Also, a thorough search of the update database

> > yields nothing related to the hotfix--KB915800. This hotfix doesn't appear to

> > be in WSUS yet it is installed on all my pcs! There are only two people that

> > even have access to the WSUS server and both swear they didn't touch it in my

> > absence and I believe them. They wouldn't want to touch it because they don't

> > know anything about it.

> >

> > Does anyone know how this could happen? Have you seen other instances where

> > updates are automatically applied prior to being approved? Is this a one time

> > deal with this particular Windows update? It is making me question the

> > decision to use WSUS. What other monstrous problems can be pushed down the

> > pipe? TIA for any help.

> >

> > --

> > Tim

[Guest Kerry Brown]

Re: Major problem with WSUS

 

"Gunnertac" <Gunnertac@discussions.microsoft.com> wrote in message

news:2AB439C7-62B4-4430-B370-44BB66215A0F@microsoft.com...

> Sorry for blasting this out so fast. A quick perusal of Google told me

> what

> happened. Sheesh...

>

> http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9044239&intsrc=hm_list

>

 

 

No problem with the venting. It was a huge blunder by Microsoft on top of

the stealth updates recently for XP and Vista. I have seriously taken a

second look at WU and WSUS. I was in the habit of installing WSUS for most

of my SBS clients. I don't know if this will continue in the future. This

cost me both time and more importantly credibility with my customers.

 

--

Kerry Brown

Microsoft MVP - Shell/User

http://www.vistahelp.ca