Re: GPO Using Pushprinterconnection.exe Not Working
- From: mamiller34 <mamiller34@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 10 Nov 2006 09:01:01 -0800
Yes, I linked the printer within the PMC.
The .exe is not currently in this particular directory, but I have tried it
there before. I've copied it to several places thinking that it was not
being executed.
I'm thinking that the printer is not getting linked to the GPO because I'm
being validated by the non-R2 server, but I'm not sure. The GPMC shows the
Deployed Printer note on the R2 server, but not the home office server, where
I'm being validated.
"Jorge de Almeida Pinto [MVP - DS]" wrote:
have you linked a printer connection (or a printer) with the GPO using the.
PMC? the log is saying no printer connection exists. check with the PMC
within the node called "Deployed Printers"
place the .exe in the netlogon share and as a path use
\\DOMAIN.COM\NETLOGON\Pushprinterconnection.exe
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"mamiller34" <mamiller34@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9E81450-E790-4186-89DC-5BABF4595D26@xxxxxxxxxxxxxxxx
Hello,
I'm pretty new at this so please pardon my ignorance.
I have a Primary DC at my home office running Windows Server 2003 (Not
R2).
I just installed another DC at a remote site and it is running Windows
Server
2003 R2. I've read some of the recent articles about deploying printers
out
to the desktop using Group Policy. I decided to try this at my remote
site.
The schema at my home office has been updated. I did that when I
installed
R2 at the remote site. I installed the PMC at the remote site.
I followed a few "How to" articles and everything seemed to fall into
place,
but when I login, my "deployed printer" is not pushed to the desktop.
I turned on the -log feature of pushprinterconnection.exe and received the
following three statements in the log after login:
"No GPO with Deployed Printer Connection Setting was Found"
"No Deployed Printer Connection settings were found in Active
Directory."
"Failed to search local GPO. Access is Denied.
So, my question is this: For this to work, do both of my DC's need to be
R2? In other words, if my User account is validated through the home
office
(not R2), should this process fail?
Group Policy in general seems to be working fine. I created another
policy
to map a network drive. It works as expected.
I have GPMC installed at the home office and remote office. The GPMC at
the
remote site shows the Deployed Printers. The GPMC at the home office does
not. However, both show everything else to be the same. My mapped drive
GPO, for example, looks exactly the same on both servers.
Any ideas?
- Follow-Ups:
- Re: GPO Using Pushprinterconnection.exe Not Working
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: GPO Using Pushprinterconnection.exe Not Working
- References:
- Re: GPO Using Pushprinterconnection.exe Not Working
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: GPO Using Pushprinterconnection.exe Not Working
- Prev by Date: network mapping using group policy
- Next by Date: Re: network mapping using group policy
- Previous by thread: Re: GPO Using Pushprinterconnection.exe Not Working
- Next by thread: Re: GPO Using Pushprinterconnection.exe Not Working
- Index(es):
Relevant Pages
|