Help with Group Policy and printers

I run a small organization with a win2008 print server. I want to install a new network printer and roll it out to all users on Windows XP, 7 and server 2008 where necessary.

There was a login.bat file which mapped printers. But I have found that it is either doing it wrong or being superceded by Group Policy.

In addition, I need to UNINSTALL two old printers and make them stop showing up via Group Policy.

Where do I look and how do I do this? Familiar with ADUC but not so much with GPMC and how it applies (or fails to apply).
LVL 1
Elixir2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Elixir2Author Commented:
In the link you posted, the OP's question was unresolved. But your link led me to this link.
http://support.microsoft.com/kb/234270
0
Elixir2Author Commented:
I still need to know how to find out what existing Group Policies are applied to which existing OUs in my existing domain.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Elixir2Author Commented:
On the print server, I installed the drivers from the internet first using the Print Management console.
I then created a new IP port and chose an IP address outside the DHCP scope.
I installed the new printer, added it to the Directory and most importantly published it via GPO, which was an option when using Print Managment console.

Finally, I updated the login.bat file that is in every users profile in the NETLOGON folder and propagated this change to both DCs.

I feel like I know what I'm doing. Unfortunately, the links you provided had nothing to do with this solution. Sorry!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FlippCommented:
Did you resolve this without the Login Script? I can certainly help you with configuration via GPO and GPP which uses the Print Management console.
0
Elixir2Author Commented:
I would LOVE the extra help. I'm still using the login.bat file. The reason is because even though login.bat is specified in the default domain gpo, some users weren't getting the mappings. I put login.bat back on each users' profile settings in AD.
0
Elixir2Author Commented:
After spending the better part of a day on this, we used the Server 2008's Printer Management console available when the Print Server role is installed. Expert links were partial solutions of other issues.
0
FlippCommented:
From the Print Management console, did you ever try right clicking on installed printer and deploy? You would of had to of created a GPO and linked to appropriate OU depending ob if you are targeting Users or Computers. There are also some point and print restriction settings I use. If users have XP then you will need the pushprinters EXE.
0
Elixir2Author Commented:
Yes, I did that. And it appeared to work. Because of the XP users, I also used the login.bat file.

Now, I'm having problems REMOVING old printers that were published using this method. But that's another question and another 500 points. :)
0
FlippCommented:
You don't need to use the login.bat for XP Users if you simply use the pushprinterconnections.exe utility in the Startup Scripts. I deploy by Computer rather than per User, but works both ways. As long as I have certain drivers installed for all x86, x64 I dont see any issue - this is a good starting point that I am sure you have seen http://technet.microsoft.com/en-us/library/cc722179(v=ws.10).aspx.
As far as cleanup goes, if the printer was deployed using this method then it can easily be removed from client machines, but performing a cleanup for printers installed using other methods I would look to a VBScript.
0
Elixir2Author Commented:
This is the VBScript we're looking for... any idea how to make it do multiple printers?
Option Explicit

Dim objNetwork, objPrinters
Set objNetwork = CreateObject("WScript.Network")
Set objPrinters = objNetwork.EnumPrinterConnections

' ### Delete selected network printer
Dim sPrinterName
sPrinterName = "\\SERVER\ICT_HP4050N"
objNetwork.RemovePrinterConnection sPrinterName, True, True

Open in new window

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.