J
John Whites
My Setup:
Windows Server 2003 R2 Domain Controllers/Print Server (32-bit)
Windows Vista Client (SP1)(32bit)
All of my windows xp machines work fine when installing printers via the
Client Side Extensions, but some particular printers won't install on the
vista machines. It will hang the vista machine at login. Sometimes
changing the driver on the print server would work, but not always. In most
cases trying to install the printer from a windows 2008 print server instead
worked but not always (i think).
Is there any work around or known fix for this hang up?
Here is an error message from an event log on the vista client
"The user 'MS Room 30 Lab Printer' preference item in the 'Master
Configuration {4684C2EF-697F-4358-BC4F-DED9FEF3D20C}' Group Policy object
did not apply because it failed with error code '0x8000ffff Catastrophic
failure' This error was suppressed"
All of these printers are set to install based on the computer OU membership
that the user is logging in from. Here is another interesting twist as
well...
User A: who is a domain admin would get hung up at login
User B: who is not a domain admin wouldn't get hung up at login, just
wouldn't get the printer installed....
Both users are under the same GPOs etc, only difference is their local
machine rights.
I have all printers set to specifically to run in logged on user's context
because I was getting errors without that checked.
The only solution I have is to install the printer to the machine via the
built in deployed printers on the group policy object, but when I do that I
need to create a GPO for every single computer room who is getting a
different printer, plus I can't set a default and I'd rather not revert to
my old scripts for installing printers.
Windows Server 2003 R2 Domain Controllers/Print Server (32-bit)
Windows Vista Client (SP1)(32bit)
All of my windows xp machines work fine when installing printers via the
Client Side Extensions, but some particular printers won't install on the
vista machines. It will hang the vista machine at login. Sometimes
changing the driver on the print server would work, but not always. In most
cases trying to install the printer from a windows 2008 print server instead
worked but not always (i think).
Is there any work around or known fix for this hang up?
Here is an error message from an event log on the vista client
"The user 'MS Room 30 Lab Printer' preference item in the 'Master
Configuration {4684C2EF-697F-4358-BC4F-DED9FEF3D20C}' Group Policy object
did not apply because it failed with error code '0x8000ffff Catastrophic
failure' This error was suppressed"
All of these printers are set to install based on the computer OU membership
that the user is logging in from. Here is another interesting twist as
well...
User A: who is a domain admin would get hung up at login
User B: who is not a domain admin wouldn't get hung up at login, just
wouldn't get the printer installed....
Both users are under the same GPOs etc, only difference is their local
machine rights.
I have all printers set to specifically to run in logged on user's context
because I was getting errors without that checked.
The only solution I have is to install the printer to the machine via the
built in deployed printers on the group policy object, but when I do that I
need to create a GPO for every single computer room who is getting a
different printer, plus I can't set a default and I'd rather not revert to
my old scripts for installing printers.