Deploying Printers from 2008 R2 Print Server (2003 DC) to xp clients

zemp1212
zemp1212 used Ask the Experts™
on
I am flooded with information, so I need some experts to help me wade through it.

My Environment

2003 native DCs
2008 R2 (x64) Print Server
Clients (x64 and x86) 90% Windows XP

Now I know to deploy using new 2008 GPO I need the new CSEs. The problem is we do not have 2008 DCs, and for now will not be updating the schema. (so can I just throw this option out?)

So what I need is to be able to deploy 64bit or 32bit drivers to existing XP computers from this 2008 R2 print server.


Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
JamesSenior Cloud Infrastructure Engineer

Commented:
You can deploy printers using GPO. Have a look at this link.

Follow the steps here : http://technet.microsoft.com/en-us/library/cc773360(WS.10).aspx
JamesSenior Cloud Infrastructure Engineer

Commented:
Print Management console on the R2 DC to manage your existing print server and deploy printers from that printer server.

More info on the management console : http://www.windowsnetworking.com/articles_tutorials/Managing-Printers-Windows-Server-2003-R2.html

Author

Commented:
The problem is we do not have 2008 DCs, and for now will not be updating the schema.

Thanks for the quick reply, unfortunately, at this point in time, management wants to know our options without updating the schema.

So I can pass along to them... without a single 2008 DC can we even update the schema and get use of the 2008 gpos? I was under the impression we needed at least one 2008 dc in order to create and take use of 2008 deployment features in the updated schema? is that not the case?

(either way for now what I need is options that do not involve updating the schema at this point)
Bootstrap 4: Exploring New Features

Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.

Author

Commented:
Print Management console on the R2 DC to manage your existing print server and deploy printers from that printer server.

unfortunately we have a 2008 R2 server for print services...but the 2003 DCs are not R2.

I will review and add that option to my info though, thanks.


JamesSenior Cloud Infrastructure Engineer

Commented:
If you check my second comment you will see:)

Print Management console on the R2 DC to manage your existing print server and deploy printers from that printer server.

More info on the management console : http://www.windowsnetworking.com/articles_tutorials/Managing-Printers-Windows-Server-2003-R2.html

Author

Commented:
Maybe I am missing something...

We do not have a 2003 R2 DC. We have 2003 Server (don't I need R2 for the print management stuff?)

sorry if I am totally missing this...
JamesSenior Cloud Infrastructure Engineer

Commented:
No, this is correct.

Author

Commented:
I know there are alot of handcuffs here, which is why I need the help. Thanks for the reply.

so are there scripting options or login scripts that can be used from a simple level?
JamesSenior Cloud Infrastructure Engineer

Commented:
Yes you can also use bat scripts or logon scripts to mapped the printers automatically.

Instructions for a simple Printer Logon Script

Copy and paste the script below into notepad.
Change the server name from "\\alan to the name of your print server.
Save the file with .vbs extension e.g. Printers.vbs.
Double click the VBScript and then launch your Printers and Faxes folder.  There should be a new printer icon.

'
' Printers.vbs - Windows Logon Script.
Set objNetwork = CreateObject("WScript.Network")
objNetwork.AddWindowsPrinterConnection "\\alan\Epson."


Author

Commented:
we use "ptool" now in the current scripts.

by doing this in this way with the vbs... will it automatically deploy the proper version of the driver?

For instance I will have a konica 222 printer. Both the 64bit and 32 bit drivers will be installed on the 2008 print server.

will having a vbs script like this deploy the 64bit version to a 64 bit vista laptop, yet a 32bit driver to a 32 bit xp desktop?


Senior Cloud Infrastructure Engineer
Commented:
You will have to configure 2 seperate scripts for this. The other option is to configure logon.bat scripts for the printers and then the PCs can connect to them automatically.

Author

Commented:
In order to set up two separate scripts... (as an FYI we have about 5000 clients)

as it is now we have users getting a .bat in the user object in AD (login script)


would we make a bat that calls a the 34bit vbs, and another that calls the 64 bit vbs, and assign the proper bat depending on what OS the user has?

also in order for that vbs to work, would I need to create 2 seperate printers on the print server...one 64 bit, and one 32 bit, with different names, so that the vbs can call the specific printer properly?

like..

 Printers.vbs - Windows Logon Script.Set objNetwork = CreateObject("WScript.Network") objNetwork.AddWindowsPrinterConnection "\\alan\Epson32."
and

 Printers.vbs - Windows Logon Script.Set objNetwork = CreateObject("WScript.Network") objNetwork.AddWindowsPrinterConnection "\\alan\Epson64."

Thanks.


JamesSenior Cloud Infrastructure Engineer

Commented:
Yes, this would work.

Author

Commented:
ok thanks. I will give it a test whirl and get back.

I appreciate the help!

Author

Commented:
Thanks for running through the options with me.

This will get me where I need to be. Thank you!
JamesSenior Cloud Infrastructure Engineer

Commented:
Your welcome, glad I could help:)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial