Re: GPO Using Pushprinterconnection.exe Not Working



Well, thanks for your help, but I feel like I've tried just about everything.

My PMC says that the printer has been deployed.

The GPMC says that the GP is there and linked to the correct place in the AD.

The .exe is being executed in the logon script because it is producing a log
file on the client computer.

I put the .exe in the NETLOGON Share.

I've reviewed and re-reviewed the How-To articles.

I'm out of ideas.

mm.
---

"Jorge de Almeida Pinto [MVP - DS]" wrote:

When installing R2 on a DC you are required to extend the schema
When installing R2 on a member you are not required to extend the schema.
However if yo want to use R2 features like DFS-R or PMC (with distributing
printer connections) the schema must still be extended!
When using the PMC only the server with the PMC needs to be R2. When the
schema has been extended with the R2 stuff, it will allow to create printer
connection objects under a certain GPO. That is what you will see in the PMC
under Deployed Printers. The .exe just reads from AD to see if it can find
such objects in GPOs in either the computer part or the user part.
If you configure the .exe in the computer part as a startup script it will
read fom AD computer related printer connections during boot of a computer
If you configure the .exe in the user part as a logon script it will read
fom AD user related printer connections during the logon of the user
--

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:DD68BF5E-D0B3-433E-91E6-8D92904C9041@xxxxxxxxxxxxxxxx
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?






.



Relevant Pages

  • Re: Deploy Printers with GP in Win2k3 R2
    ... is that the policy is not reversed when the user is removed from the group. ... I have a print server. ... log in my first post that i am getting when deploying the print without ... You can manage printer connections through a logon script, ...
    (microsoft.public.windows.server.active_directory)
  • Network Tappers, IDS, etc.
    ... I plan on getting a pretty hefty server to use as the ... I was wondering if someone with experience deploying Snort in a medium ... I would like any information available on network taps. ... Test Your IDS ...
    (Focus-IDS)
  • There was a failure executing the receive pipeline
    ... I created the project on an SDK client and deployed it on the server from ... client and deploying to the biztalk server. ...
    (microsoft.public.biztalk.general)
  • Server 2003 Group Policy error - KB830676
    ... to that described in the MS Knowledge Base article 830676. ... information could not be read from the domain controller, ... Server 2003 at a handful of sites and are looking to use ... resort to deploying Win2K Servers so as to provide an ...
    (microsoft.public.windows.server.general)