TexasBanjo
asked on
GPP printers not applying to some Windows 7 Enterprise Computers
While using group policy to install printers we have encountered an issue with some of our computers. We are using Windows Server 2003 applied to Windows 7 Enterprise and Proffessional computers. We are only noticing this problem on Enterprise computers so far. INcidentally we just started deploying Enterprise computers and it is working on some. 4 computers that we had a problem with we re-ghosted with the same image and it worked, others are not. The error we are recieving is..
The computer xxx.xx.xxx.xxx' preference item in the 'HS224 {GUID}' Group Policy object did not apply because it failed with error code '0x8007051b This security ID may not be assigned as the owner of this object.' This error was suppressed.
The print processor is set to Winprint and Raw. We are deploying TCP IP printers by user configuration and by computer configuration. We are not deploying by shared printer. I have attached the policy that is not being applied as well as GPResults in 2 text files one simple and one superverbose.
RSOPresults.txt
HS224.xml
SuperVerboseResults.txt
The computer xxx.xx.xxx.xxx' preference item in the 'HS224 {GUID}' Group Policy object did not apply because it failed with error code '0x8007051b This security ID may not be assigned as the owner of this object.' This error was suppressed.
The print processor is set to Winprint and Raw. We are deploying TCP IP printers by user configuration and by computer configuration. We are not deploying by shared printer. I have attached the policy that is not being applied as well as GPResults in 2 text files one simple and one superverbose.
RSOPresults.txt
HS224.xml
SuperVerboseResults.txt
I have a thought, since you mentioned these are imaged computers, just for test purpose make a Clean Boot & see if it works?
If it works, then it's something to do with the image. I know on some computers its working, but just to check.
A
If it works, then it's something to do with the image. I know on some computers its working, but just to check.
A
ASKER
OK here are the pertinant log information. I do not know how to remove the ip address information from the event log itself so I am unable to upload the actual logs due to security policies we have.
Details-1.txt
Details-2.txt
Details-1.txt
Details-2.txt
Hello, did you try CLEAN BOOT?
ASKER
I appologize for taking so long we are busy. I did a clean install of Windows 7 Enterprise and only added the network drivers joined it to the domain and ran gpupdate /force and I am recieving the same error.
Sorry, but can you clear something?
When you say Clean Install, is that from the image or did you do it from MS installation media?
A
When you say Clean Install, is that from the image or did you do it from MS installation media?
A
ASKER
MS installation media. Nothing added except what I stated above.
k, one more thing...
Do you by any chance have W2k3 R2 or W2k8 machine for print server?
It seems to be an issue with W2K3 machine.
A
Do you by any chance have W2k3 R2 or W2k8 machine for print server?
It seems to be an issue with W2K3 machine.
A
ASKER
W2k3, We haven't started moving to W2k8 yet.
Listen, I am sorry but this is difficult to troubleshoot as I am not seeing the screen so you might think that I am asking many questions.
What I have seen is that these issues are reported mostly when the server version is 2003.
However when the same users used 2003 R2 or 2008 then this was resolved.
Another thing you can try is to put the policy under Computer configuration, however you have written in your description "We are deploying TCP IP printers by user configuration and by computer configuration" which is confusing.
To isolate this issue,
1) put one of the affected machine in a Test OU , block all kind of inheritance , link only the GPO you are trying now & then see, maybe there is something conflicting?
2) if the previous doesn't work, then make a new GPO & try to apply shared printer & see the results.
Please let me know how you want to proceed?
A
What I have seen is that these issues are reported mostly when the server version is 2003.
However when the same users used 2003 R2 or 2008 then this was resolved.
Another thing you can try is to put the policy under Computer configuration, however you have written in your description "We are deploying TCP IP printers by user configuration and by computer configuration" which is confusing.
To isolate this issue,
1) put one of the affected machine in a Test OU , block all kind of inheritance , link only the GPO you are trying now & then see, maybe there is something conflicting?
2) if the previous doesn't work, then make a new GPO & try to apply shared printer & see the results.
Please let me know how you want to proceed?
A
I don't know what stage you are, but I found something interesting:
Please answer if it works for you also on Windows Vista clients or they are using Windows 7 only?
Here is my detailed results. I was configured GP Preferences policy to add Xerox TCP/IP color printer to Windows 7 x64 and Vista x86 clients. The Preference is configured by computer, not per user. Of course I have Windows Server 2008 R2 that shares the printer with x64 and x86 drivers for it and the printer is listed in Active Directory. The x64 driver is built in Windows 2008 R2 by default and the same one is also present in Windows 7 x64 driver store.The x86 driver, which was needed for Windows Vista x86 clients, because of lack of built-in driver, was downloaded from Xerox website and added to print server using standard procedure.
And with this, I think, very common configuration:
1) Windows Vista x86 clients doesn't download the x86 driver and doesn't add TCP/IP printer (If a user runs "Add Printer" wizard locally by hand and choose the printer from AD, the driver is downloaded from the server and the printer is added, however if a user is trying to go to printer properties, the explorer.exe process crashes or if he/she is trying to print on the printer, the application used for printing crashes also.)
2) on Windows 7 x64 clients the TCP/IP printer is added however the driver is installed from Windows 7 store, because it is already there, not from server and the local driver default configuration (duplex, color, paper sizes etc.) for that printer is used, the configuration is not getting from print server. And because the default driver configuration may be useless for the end-users (I know, blame Xerox), it was obvious for me that the printer driver configuration defaults will be always downloaded from print server.
So FOR me GP Preferences for adding TCP/IP printers don't work or work wrong.
If I deploy the same printer from the same printer server as printer share using GP Policy, not Preference, everything works OK with any issues described above.
From the following post:
http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/c94ea362-bc3c-4bc7-9a27-354dc521dd91/
A
Please answer if it works for you also on Windows Vista clients or they are using Windows 7 only?
Here is my detailed results. I was configured GP Preferences policy to add Xerox TCP/IP color printer to Windows 7 x64 and Vista x86 clients. The Preference is configured by computer, not per user. Of course I have Windows Server 2008 R2 that shares the printer with x64 and x86 drivers for it and the printer is listed in Active Directory. The x64 driver is built in Windows 2008 R2 by default and the same one is also present in Windows 7 x64 driver store.The x86 driver, which was needed for Windows Vista x86 clients, because of lack of built-in driver, was downloaded from Xerox website and added to print server using standard procedure.
And with this, I think, very common configuration:
1) Windows Vista x86 clients doesn't download the x86 driver and doesn't add TCP/IP printer (If a user runs "Add Printer" wizard locally by hand and choose the printer from AD, the driver is downloaded from the server and the printer is added, however if a user is trying to go to printer properties, the explorer.exe process crashes or if he/she is trying to print on the printer, the application used for printing crashes also.)
2) on Windows 7 x64 clients the TCP/IP printer is added however the driver is installed from Windows 7 store, because it is already there, not from server and the local driver default configuration (duplex, color, paper sizes etc.) for that printer is used, the configuration is not getting from print server. And because the default driver configuration may be useless for the end-users (I know, blame Xerox), it was obvious for me that the printer driver configuration defaults will be always downloaded from print server.
So FOR me GP Preferences for adding TCP/IP printers don't work or work wrong.
If I deploy the same printer from the same printer server as printer share using GP Policy, not Preference, everything works OK with any issues described above.
From the following post:
http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/c94ea362-bc3c-4bc7-9a27-354dc521dd91/
A
ASKER
If I set it up just through the user configuration and I do not get the error but they still do not show up. I double checked to make sure that they were set to winprint/raw and they are.
I then set it up just through the computer configuration and I got the error but not the printers.
I also set it up with shared printers under user configuration alone and then with tcp/ip under computer configuration. Still no printers showing up.
The reason I was using both configurations in my set-up is because that is the way the instructions I was following were written. And it was working great until the last couple of weeks when we started deploying some Enterprise computers.
As for 64 bit and 32 bit drivers we have 2 seperate print servers for 64 bit and 32 bit. A hold over from the XP days. Very few computers on campus use 64 bit at the moment.
I do not know how to properly set up printers using the deployed printers under policy settings.
I then set it up just through the computer configuration and I got the error but not the printers.
I also set it up with shared printers under user configuration alone and then with tcp/ip under computer configuration. Still no printers showing up.
The reason I was using both configurations in my set-up is because that is the way the instructions I was following were written. And it was working great until the last couple of weeks when we started deploying some Enterprise computers.
As for 64 bit and 32 bit drivers we have 2 seperate print servers for 64 bit and 32 bit. A hold over from the XP days. Very few computers on campus use 64 bit at the moment.
I do not know how to properly set up printers using the deployed printers under policy settings.
ASKER
OK I just talked to my supervisor and He said we are using W2K3 and Not W2K3R2.
Please see in the article, it states that same applies for 2003 also
To take out the confusion:
http://technet.microsoft.com/en-us/library/cc722179(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/cc722179(v=ws.10).aspx
ASKER
There is one problem. I do not have access to the print management console on the print server I will need to get with our print server administrator to go this route. That is one of the reasons we were using preferences and TCP/IP to deploy the printer connections. It will likely be tomorrow before I can get this done.
Don't worry, I m sort of happy that u doing it 2morrow, it's 1AM here now.
Rest 2morrow or my Today ;)
Rest 2morrow or my Today ;)
ASKER
I found some information that may be pertinant.
This is from a Vista Hotfix
•GPP cannot be deployed on a printer when the printer owner is not specified as "System" or "Administrators."
Our printers Owner is set to the printserver administrator so that may be the issue.
I am going to run every update on the test machine I can find. And While that is going on I will see if I can find the appropriate hotfix for Win 7 Enterprise relating to the same thing. I will post back if I find anything.
This is from a Vista Hotfix
•GPP cannot be deployed on a printer when the printer owner is not specified as "System" or "Administrators."
Our printers Owner is set to the printserver administrator so that may be the issue.
I am going to run every update on the test machine I can find. And While that is going on I will see if I can find the appropriate hotfix for Win 7 Enterprise relating to the same thing. I will post back if I find anything.
Do you have SP1 on machine?
ASKER
Maybe not when I did the clean install I did not run updates. However I thought I had run all updates on the machines I have deployed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Downloaded SP1 and updated. At first I was reading every update so maybe I could figure out which article was the fix but when I tried it Friday before we left it still did not work. I ran the rest of the updates today (forgetting to check the details of each update) and re-ran gpupdate, the printers are now showing up normally without errors. So it is likely a SP1 update. I will try to check out which article number is the issue and post it here so anyone else having this issue can resolve it more quickly.
Great!!! I wish everyone follows the same approach of help as you.
A
A
A