| Subject: | Windows Server 2003 R2 x64 |
| Posted by: | david (dav…@discussions.microsoft.com) |
| Date: | Tue, 27 Feb 2007 |
Hi Guys,
I'm looking after a small domain environment and am replacing the ancient
Server2k/Exchange 2k box with a new Server 2003R2 x64/Exchange 2007 box. I've
got the new server onto the domain, AD replicating beautifully, FMSO roles
transferred to the new box, Exchange 2007 is up and running, all mailboxes
transferred over, new send and receive connectors working 100%, data
transferred over from the old server to the new one, login scripts re-done to
point to new shares etc... in fact I'm as happy as Larry with all
that....went smoother than I expected......
All except for one thing!
The bloody printers!!
I've installed the three networked Xerox printers to the new Server 2003
server, they all have the 64 bit drivers installed and print fine to those
printers, I, after a bit of mucking around, managed to install the correct XP
x32 drivers for each printer and they are listed in the print Server applet.
I have shared those printers and they are listed in AD, but the problem is,
it doesn't matter which XP workstation I jump on, when I go through the Add
Printer Wizard, find the printer in AD and try to install it...it keeps
giving me incorrect driver messages. Fine I thought, I'll just manually point
it to the drivers on a shared directory...and it still tells me they are the
incorrect drivers! Which is bollocks! They are the right drivers!
If I go to each XP box and set that printer up as local and setup the TCP/IP
port to point to that printer it accepts those drivers and works fine. If I
install those printers on my existing Windows 2000 server those same drivers
work fine. So I know they are the right drivers.
Through some trawling in these newsgroups and via google I read something
about changing the group policy for the point and print thing. From memory it
said that if the policy was undefined it wouldn't let you connect to printers
- basically giving you the enabled state of that policy. I tracked it down
and set it to disabled with no luck.
Haven't come across anything else that might help me out...any help would be
greatly appreciated....I really want to get rid of that old server
ASAP.....and maybe hit it with a few hammers for an hour or so......