Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MS08-026 event 534 and "incorrect printer drivers" related problem

1 view
Skip to first unread message

greg...@hotmail.com

unread,
Nov 17, 2008, 9:01:04 AM11/17/08
to
I have having terrible troubles with this situation.

After applying MS patch MS08-026 we are getting the following error
when
trying to add a printer. "The server for "printer" printer does not
have the
correct printer driver installed." When I uninstall this patch, the
problem
clears up.

In addition, and I believe this to be related - we are getting in the
security event log the following:

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 534
Date: 11/17/2008
Time: 7:19:49 AM
User: NT AUTHORITY\SYSTEM
Computer: %mypcname%
Description:
Logon Failure:
Reason: The user has not been granted the requested
logon type at this machine
User Name: server$
Domain: %mydomain%
Logon Type: 3
Logon Process: Kerberos
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Workstation Name: -

We have a clustered print server and I have ensured that "allow log
on
locally" has been set for "Authenticated users" and I have ensured
that on
the SAN drive where the drivers reside "Authenticated Users" have read
access.

I cannot think of what else to do.

Is anyone else having these problems?

-Greg Seeber

greg...@hotmail.com

unread,
Nov 17, 2008, 9:04:13 AM11/17/08
to
BTW, we're having issues that make me look at the "Authenticated
Users" vs. "Everyone" or "Users" ... maybe something with this patch
is now enforcing something that it wasn't enforcing. But, I'm barking
up the tree of something with the "Authenticated Users" group. Maybe
I"m way off though ...

help! : )
-Greg

Greg S

unread,
Dec 4, 2008, 10:53:01 AM12/4/08
to
All I can say is that something with this patch change a permission
somewhere, and I believe that it does having something to do with
AUTHENTICATED USERS. At this time, I have worked around this problem by
reinstalling ALL (yes, all) of my print drivers on the printer server. This
has resolved the errors and has allowed the users to access the printers.
0 new messages