.Net Framework 3.5 install from WSUS messes printing

Hi,

in my WSUS server I agreed on install ".NET Framework 3.5" on my 1000 PCs.

The problem is that many of them, after installing it, cannot print
anything.

The solution is to remove and to reinstall the default printer.

but how to do it on 1000 PCs automatically?

"96Trap" <> wrote in message
news:...

> in my WSUS server I agreed on install ".NET Framework 3.5" on my 1000 PCs.
>
> The problem is that many of them, after installing it, cannot print
> anything.
>
> The solution is to remove and to reinstall the default printer.
>
> but how to do it on 1000 PCs automatically?

Actually, the first step is to apply the Feb '09 UPDATE that fixes this
known issue.

http://support.microsoft.com/kb/961118



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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

>> in my WSUS server I agreed on install ".NET Framework 3.5" on my 1000
>> PCs.
>>
>> The problem is that many of them, after installing it, cannot print
>> anything.
>>
>> The solution is to remove and to reinstall the default printer.
>>
>> but how to do it on 1000 PCs automatically?
>
> Actually, the first step is to apply the Feb '09 UPDATE that fixes this
> known issue.
>
> http://support.microsoft.com/kb/961118

This screwed me up too. I released 961118 to both clients and servers (peer
sharing), one day after I released .NET to them. (Never thought of testing
_print drivers_.)

Yet I still have a few users contacting me periodically that a "driver
update is required".
I have to supply administrative credientials at the desktop and all is well.
All have been Vista so far.

Is the fault/fix at the client or the server end?

--
Dave Harry

"Dave Harry" <> wrote in
message news:OyHW$...

>>> in my WSUS server I agreed on install ".NET Framework 3.5" on my 1000
>>> PCs.
>>>
>>> The problem is that many of them, after installing it, cannot print
>>> anything.

>> http://support.microsoft.com/kb/961118


> This screwed me up too. I released 961118 to both clients and servers
> (peer sharing), one day after I released .NET to them. (Never thought of
> testing _print drivers_.)
>
> Yet I still have a few users contacting me periodically that a "driver
> update is required".
> I have to supply administrative credientials at the desktop and all is
> well. All have been Vista so far.
>
> Is the fault/fix at the client or the server end?

Actually, I don't know, Dave. Aside from being aware that the update exists
and is designed to fix something that NET35SP1 screws up (which I've opted
to not deploy for several reasons we're all already familiar with), I've
pretty much ignored the update.

From reading the KB article, I note a couple of things...

[1] The KB fix only applies to Win v5 systems (WinXP, Win2003).

[2] The impact appears to be a factor of the unidrv.dll file in the NET35SP1
package being unsigned, which breaks the in-box PCL drivers. KB961118
provides a digital signature for the unidrv.dll file which "fixes" the
in-box PCL drivers.

What might be driving Vista to report needed driver updates, I'm not sure.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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

> [2] The impact appears to be a factor of the unidrv.dll file in the
> NET35SP1 package being unsigned, which breaks the in-box PCL drivers.
> KB961118 provides a digital signature for the unidrv.dll file which
> "fixes" the in-box PCL drivers.
>
> What might be driving Vista to report needed driver updates, I'm not sure.

That's ok, cos I don't know either!
In my case the "servers" are XP and 2003. So perhaps the clients would have
been fine if the fix to the print server had been applied before any Vista
clients contacted it and had their drivers unsigned.

Too late to matter now anyway.

--
Dave Harry

"Dave Harry" <> wrote in
message news:%...

>> [2] The impact appears to be a factor of the unidrv.dll file in the
>> NET35SP1 package being unsigned, which breaks the in-box PCL drivers.
>> KB961118 provides a digital signature for the unidrv.dll file which
>> "fixes" the in-box PCL drivers.
>>
>> What might be driving Vista to report needed driver updates, I'm not
>> sure.

> That's ok, cos I don't know either!
> In my case the "servers" are XP and 2003. So perhaps the clients would
> have been fine if the fix to the print server had been applied before any
> Vista clients contacted it and had their drivers unsigned.

If the Vista clients obtained the drivers from the print servers (XP/2003),
that would explain the unsigned drivers, for sure.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
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