Koldov Posted June 10, 2015 Posted June 10, 2015 Hi All, Really going round in circles with this one! I've done this all before about 5 years ago, but must admit I'm stumped now... I've attached a Brother MFC to the network, configured it a static I.P. and it's seen by the server and in the directory and all is good. I deployed it to the SLT via GPP and yet it won't install, on one of their laptops it shows errors in the event log and a manual install just bugs out at the end saying it cannot connect to the printer (on the test pc it at that point asks for admin credentials). Other printers install fine so I think the Group Policy for installing printers is ok. So I was thinking an updated driver so I uninstalled it from the server and although I can get the 64-bit drivers back on the server, I cannot get the x86 drivers on! It tells me it isn't meant for the selected architecture when I tick x86 and I have an x86 driver, I've also tried a reverse install via a 32-bit workstation and using the 'additional drivers' but although it looks like it's doing it gives me a 0x00000244 error. It is strange looking through the inf's it seem to say x86\amd64 so it may be that it isn't telling the server it's the right architecture...? But I can't find a recent 'pure' x86 driver! How do I get it to take the x86 driver? Kol
3s-gtech Posted June 10, 2015 Posted June 10, 2015 Add the driver through the Print Management MMC, Drivers. That gives you the option to add 32 and 64 bit drivers simultaneously.
Koldov Posted June 10, 2015 Author Posted June 10, 2015 Ah yeah, that's where I was doing it from initially. Seems I needed to download a driver for Windows Server 2008 (32-bit) instead of the Windows 7 (32-bit) one.... Even though it will be pushing the driver to Windows 7 clients... Why that isn't the same driver I don't know! But upon further Gooooooogling, it may have been a version number error as it appears it has to be the same for both architectures otherwise it gets a bit sniffy (and the Windows 7 driver had a different version number). Kol.
6Foot2 Posted June 10, 2015 Posted June 10, 2015 I seem to remember some advice about not having PCL5 and PCL6 drivers on the same server as that could cause issues similar to those you describe. Does anyone else recall this?
GuyJD Posted June 10, 2015 Posted June 10, 2015 you also need to make sure that the driver version number is the same for both the 64bit and 32bit driver
Koldov Posted June 11, 2015 Author Posted June 11, 2015 Yes, think it might have been version number... However, still can't get it to deploy via GPP - GP deploys it no problem however! Anybody aware of anything I would need to tweak to get it to deploy via preferences instead? I personally have no 'preference' on how it deploys (pun intended), but it would be nice to know if there might be some reason why preferences won't deploy it but policy does? Kol.
Michael Posted June 11, 2015 Posted June 11, 2015 Deploying via GPP or GPO shouldn't make any difference when it comes to drivers. Certainly in my experience anyway. You always need to install the 64Bit version first, then the 32Bit version. Avoid setup/installation and import the driver files themselves manually.
SHimmer45 Posted June 11, 2015 Posted June 11, 2015 (edited) the driver versions have to match for x64 & x86 i went through alot of pain with this esp if you are mixing PCL / PS / KPDL drivers. so on your server you will need a driver for itself & a driver for the clients your serving (x64 & x86 if you a mixed client environment) GPO will install the printer and the driver as one and will pull the required driver from the server as required has always been my understanding (similar in the way its auto installed if you click connect to a browsed network printer) Edited June 11, 2015 by SHimmer45
Koldov Posted June 11, 2015 Author Posted June 11, 2015 Yup, exactly. However the problem I'm having is I thought it would be a similar process when using GPP to install the printer, but it just doesn't happen! All sorts of reasons, from needing admin credentials (I believe, as this is what it does when trying to install this driver manually) to flat out refusing to do anything (just showing errors in event viewer saying 'the driver isn't installed and will need to download it' duh!) and failing... No matter how much I mess with 'Point and Print' settings, going round in circles trying to find all the entries Point and Print has! Going in to Print Management and selecting it to 'Deploy with Group Policy' on the other hand works like a charm, no fuss, no bother, no credentials asked for - just a smooth and seamless deployment and install... Kol.
GeekyPete Posted June 11, 2015 Posted June 11, 2015 That's fine for the 64bit drivers, if you are still having trouble with the 32 bit drivers try this: On the Windows 7 client, log on as your System Admin. Administrative Tools, Print Management. Expand the Print Servers node in the tree control. Expand the server node under the Print Servers node and select the Printers node. Right-click on the printer in the main list and select Manage Sharing. The Printer Sharing Properties page is displayed. Click the Additional Drivers button. Select the x86 option in the list (the x64 should already be ticked) and click OK. The drivers will be copied up to the server. When the window is displayed again click Close.
Koldov Posted June 11, 2015 Author Posted June 11, 2015 Thanks, but all done now. Just puzzling me why there are no issues at all when deploying to a client via GPO and yet trying to deploy via GPP it is just refusing to install. Kol.
dubsdj Posted June 23, 2015 Posted June 23, 2015 on the server try installing the Windows 2008 R2 64bit driver and then download the Windows 2008 32 bit driver and adding it though additional drivers. I must admit I've had trouble with this before also and have forgotten how i sorted it . I even recall using Windows 7 drivers on the server instead of the 2008 ones.
penfold Posted June 23, 2015 Posted June 23, 2015 (edited) Take a look at this thread Group policy adding printer drivers. You may need to set up the Point & Print restrictions. If this is just a test machine, have you deleted any local drivers? I've noticed when we have had some issues on clients installing it normally means they have a corrupted printer driver on their machine. Deleting all the drivers on the client and getting them to pull down fresh ones seems to be the quickest fix. Edit: Just re-read that you have already looked at Point & print:getmecoat: Edited June 23, 2015 by penfold
Mr_Jiminy Posted July 26, 2015 Posted July 26, 2015 Have you checked event viewer? Might be worth setting up GPO for point and print restrictions... Easy enough to do
Mr_Jiminy Posted July 26, 2015 Posted July 26, 2015 Have you checked event viewer? Might be worth setting up GPO for point and print restrictions... Easy enough to do The joys of reading on a tablet, sorry just spotted this has been said several times before.
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