zag Posted April 29, 2008 Posted April 29, 2008 I'm going to try out 2008 server later and thought I would make a nice test print server. Now I know 2003 R2 has some cool print functionality but how does 2008 compare? I'm a total n00b at this and cant find much information on google.
Geoff Posted April 29, 2008 Posted April 29, 2008 I had a look at the printing on our w2k8 test machine. It doesn't seem amazingly different than w2k3. However the GPO stuff for Printing in 2k8 has been greatly improved. However you would have to upgrade your DC's to w2k8 to get that functionality.
zag Posted April 30, 2008 Author Posted April 30, 2008 Pretty impressed with this one, I added the print manager role, went to the server right clicked to add a new printer. Typed in the IP address and that was it. Found the drivers and made it a shared resource without any other intervention. Slick stuff!
contink Posted April 30, 2008 Posted April 30, 2008 I'd be curious to know how HP's are handled on the 2008 machines... If nothing else I'd like to know if the work-arounds we've had to use in the past (Standard TCP/IP ports instead of HP version, turn off bi-directional, etc.) are a) required and b) possible. Any intel on that side of things would be appreciated.
zag Posted April 30, 2008 Author Posted April 30, 2008 We use HP network printers exclusively here, windows 2008 has an automatic detection option when you add a tcp-ip port. Its worked perfectly on all HP laser printers I have tried including 4100n, 2300n, 1320n and 3052n models. The only thing it hasn't worked on is a Netgear print server with an HP 1320 attached but thats to be expected really. EDIT: all those fixes for bi directional and specific ports are available if needed in the printer config but i've not had any need for them yet. 1
zag Posted May 1, 2008 Author Posted May 1, 2008 I rolled this out as our main printer server and am having troubles with it. Some of my users get "a policy is in place that restricts you connecting to this printer". I've had a look at the permissions but nothing obvious, any idea why some of the users cant connect to printers shared on 2008 server? I recreated them on 2003 server and it worked fine.
techyphil Posted May 12, 2008 Posted May 12, 2008 I've installed Win2k8 x64 with SP1 today and just wondering how you guys go about setting up the print server role. I assume you install the 64bit drivers for the printer then add the 32bit as additional drivers? I've been googling around and read people have problems with it. If it's a problem then i'll try HyperV and install a guest OS 32bit Win2k3 R2 and use that as the print server :S
saundersmatt Posted May 12, 2008 Posted May 12, 2008 I rolled this out as our main printer server and am having troubles with it. Some of my users get "a policy is in place that restricts you connecting to this printer". I've had a look at the permissions but nothing obvious, any idea why some of the users cant connect to printers shared on 2008 server? I recreated them on 2003 server and it worked fine. Is the print server on the same domain as the client machines. I know there is a security policy that can restrict adding printers to domain only. I'll look it up if you need me too. Matt
zag Posted May 16, 2008 Author Posted May 16, 2008 Is the print server on the same domain as the client machines. I know there is a security policy that can restrict adding printers to domain only. I'll look it up if you need me too. Matt Yep all on the same domain, nothing special. The really wierd thing is it works fine on 2003 R2, just not 2008 server.
Michael Posted May 16, 2008 Posted May 16, 2008 Is the print server on the same domain as the client machines. I know there is a security policy that can restrict adding printers to domain only. I'll look it up if you need me too. You're right, the policy I think you're referring to is in: User config > Admin Templates > Control Panel > Printers This only affects users manually searching/adding and deleting printers only. It shouldn't affect R2 or 2008 print management. Yep all on the same domain, nothing special. The really wierd thing is it works fine on 2003 R2, just not 2008 server. It might possibly be because the driver isn't 2008 certified?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now