R2 printer deployment removal problem
 




IT Certification FAQ

 
|
Home
|
Microsoft
|
CISCO
|
CompTIA
|
Exam/Study FAQ
|
Employment FAQ
| Links  | Forums  |
Book Reviews


FAQFAQ  SearchSearch  MemberlistMemberlist  UsergroupsUsergroups  RegisterRegister  ProfileProfile  Log in to check your private messagesPrivate messages  Log inLog in

R2 printer deployment removal problem

 
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.general
Author Message
Christopher Haydon
Guest





PostPosted: Tue Feb 13, 2007 1:11 pm    Post subject: R2 printer deployment removal problem Reply with quote

Hi
I have been asking this over in the group policy group without much luck, so
I thought I would give this a try over here as it has higher traffic levels.

Basically I have some printers deployed using the Windows 2003 R2 printer
deployment system to XP clients, when I move a client out of an OU the
printers linked to it aren't being removed.



Thanks for the link, did you ever get a resolution (or for that matter a
workaround).

Looks like a simalar symptom as tests 3/4, but this time I am removing the
accounts from the OU the GPO is linked to rather than applying security
filtering (which in my experiance can be a bit of a pain at the best of times)

Yesterday I resorted to a unsatisfactory method of fixing it when I had a
driver issue, when I unlinked the printer from the policy, rebooted and it
removed it but that isn't much good in a production enviroment where several
computers are linked to a single policy - I want to be able to move a
computer out of a OU and the printers linked to that GPO/OU be removed, at
present if I move a computer from one office to another it is a reimage job
to remove the deployed printers, if I take a machine from the OU Ely to the
OU March, I want it to stop applying GPO Ely and start applying GPO March,
instead at the moment it applys both the Ely and March GPOs.

I can't anyway of manaually cleaning up theses extranious deployed printers
or where ppc.exe it is picking up the list of GPOs to process.

Kind regards
Christopher Haydon

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

Quote:
also see:
http://blogs.dirteam.com/blogs/jorge/archive/2005/12/02/203.aspx

--

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
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Christopher Haydon" <ChristopherHaydon@discussions.microsoft.com> wrote in
message news:D417DB20-91A9-415B-B043-EE14F84242E2@microsoft.com...
Hi, hopefully this is the most appropriate group - otherwise shove me in
the
right direction!

I have happily been deploying printers to workstations on a machine basis
using group policy under 2003 R2 and pushprinterconnections.exe, it will
add
printers ok to machine ok but I have hit a snag when removing them - below
is
an extract of what it is logging

It would appear from this that it is still finding and applying the GPO
March Printers despite the fact the machine is no longer in the OU linked
to
it; I have tried forcing GP refreshes to no avail in the hope that this
would
sort.

It is a bit of a pain as the only way I can remove printers is using
System
Restore and restoring to a point before the printers were originally
deployed!!! At present I have machines with printers that are totally
inappropriated for the location they are in and users compaining as their
print jobs end up on printer 30 miles away. Alterantively is there anyway
of
removing them manually as just deleting them they regenerate at next
logging,
I am considering a move to using a scripting at login as a solution if I
would get rid of them for good (although this isn't my prefered option)

Help....
Many thanks
Christopher Haydon


Microsoft Windows Operating System Deploy Printer Connections Utility v1.0
Copyright (C) Microsoft Corporation. All rights reserved.

... Logging enabled by command line switch.
... Logging started at 20:56:40 28/01/2007.
... Found and applied this GPO: wsus.
... Found and applied this GPO: March Printers.
... Found and applied this GPO: Default Domain Policy.
... Found Deployed Printer Connection setting \\Mar-2003-svr\black duplex
in
Active Directory.
... Found Deployed Printer Connection setting \\Mar-2003-svr\black non
duplex in Active Directory.
... Found Deployed Printer Connection setting \\Mar-2003-svr\colour duplex
in Active Directory.
... Found Deployed Printer Connection setting \\Mar-2003-svr\colour non
duplex in Active Directory.
... There are no connections to remove.
... Deploying per machine connection \\Mar-2003-svr\black duplex.
... Deploying per machine connection \\Mar-2003-svr\black non duplex.
... Deploying per machine connection \\Mar-2003-svr\colour duplex.
... Deploying per machine connection \\Mar-2003-svr\colour non duplex.


Back to top
Display posts from previous:   
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.general All times are GMT
Page 1 of 1

 

Copyright © 2002-2006 Web-S-Sense Pty. Ltd. All rights reserved.

Powered by phpBB
Advertising | Policies/Disclaimers | Contact us | Link to us


Featured Sites: Free Antivirus and Antispyware Info | Free PC Support | MCSE Directory