New
#1
Win7 + Server03R2 + Point and Print
The company I work for has had an issue with deploying printers from windows server 2003 r2 using point and print to our windows 7 workstations. I have researched this issue repeatedly online and I can find no good information on it. We have tried many things such as clearing the print spooler on the server... Removing all drivers, monitors, ports.. etc. Completely rebuilding from scratch. We have the point and print restriction group policy set to disabled so this should allow non administrator users on windows 7 to install the drivers from the server.
I was curious if any of you have come across similar issues. I think part of the reason for the lack of information online is the slow speed in which corporations are "upgrading" to 7.
A few things of note. Before 7 we had Vista. Some machines were directly upgraded some machines we performed a windows depoloyment services (WDS) on.
There are several things in the event logs relating to the HP printers we are attempting to deploy. Specific DLL files are not loading on the client. We have tried both the UPD driver and the windows xp specific one.
The main issue seems to be with the ports and driver information disappearing as they are using the computer during the day. It does not effect everyone... Some people are able to print fine one day and the next day they can not.
The main thing of interest is the TCPIP port information on the client disappearing for all of the shared printers. The eventlogs say this is due to the print spooler not being able to connect back to the server. We are using the built in windows 7 firewall and have made all the necessary exceptions for file and print sharing.
From what I have found there appear to be two main problems. The issue with the HP drivers installing and the ports and information disappearing for all the printers.
A restart of the print spooler will usually get that information back on the client, however the print spooler does not crash it remains running.
I am just curious if any of you have run into a similar situation or have any ideas to help me out.
The main error in the event log seems to say 1722 The RPC Server is unavailable.
Thanks.
Quote