Hi,
we have a problem with our print environment (HP and Ricoh printers).
We have some Windows 8 and 8.1 clients and a Windows Server 2008 R2 printserver.
Windows 8 and 8.1 is showing the printers as offline. Its seems the problem described here ->http://support.microsoft.com/kb/2713128
We already installed the fix on the server but this didn't resolve the issue.
Maybe somebody have the same issues and an alternate solution for this?
Best regardsHi there,
Hoping that someone in here have some knowledge to share J
I am currently working on a design for a global print service within the company where I work.
Despite the issues introduced in April 2014 with the KB2919355 I am still convinced that Windows Server 2012 R2 is the right OS as this gives us some administrative advantages over 2008.
What I would like to do (as Hyper-V is a no go in this company) is to use the Citrix PVS to have a master server image and then load it on to X servers. This would enable us to a) have a Load Balancer in front for spreading the load b) always have a clean server c) push queues to multiple servers without any interaction and d) just add additional servers if the load becomes +75%.
However the one issue I am up against is the spool files. Usually the spool directly resides locally on the server and is not shared with other servers. However as we plan to have multiple servers it would be really neat (well actually required!) to have a shared spool drive for all servers. This would allow the other servers to take over if one crashes.
Would anyone have some information/tricks to share so I can somehow achieve the above?
Thanks,
David
Hello, I have the task of migrating this server.
Right now we have a 2003R2STD SP2 (I believe is x86) and the idea is to install a 2008R2x64STD SP1.
All the users have either Windows XP SP3 or Windows 7x64.
I couldn't get the import to create all the printer queues on 2008R2 (Error 0x80070705. The printer driver is unknown) therefore I'm install each printer manually. When I add the printer on the Print Management MMC only the x64 drivers are being shown; why is this? does this mean that when I map a printer on XP the server will provide the info from the 64-bits driver? could I delete, then, the x86 drivers?
Currently we have HP and Brother printers, is it better to have all the specific drivers for both versions or can I use anUniversal Driver (for HP) / Generic Driver (for Brother)?
Although I have the exported file with all the drivers installed on the 2003 Print Server, can I backup individually the drivers that are being used? how can I identify them?
And to finish: this server will have two roles: Print Server and WSUS, will these roles conflict in any way? do you have any suggestions or things I should look for?
Thanks.
Hi All
I have got script which reads data from CSV file and create print queue using add-printer and Add-PrinterPort on 2012 R2 print server. however when it gets created all printers' status is offline.
any help would be appreciated.
The "Print Spooler" service entry has disappeared from services.msc
However I can still print, access my printers, and run net stop spooler and net start spooler and the service stops and restarts
But it's just not there in the GUI.
I've gone through several attempts to reinstall the service but nothing has changed the situation.
sfc /scannow comes back with no component store corruption.
Any Suggestions?
Hi,
I am trying to deploy a single printer to Windows 8.1 clients in a K-12 environment. We have about 1200 laptops and about 25% of those laptops are installing the printer. Several different users can log on and the printer may or may not be there. The printer
is being deployed to the Computer not the User. If the printer was successfully installed shouldn't the printer be available immediately after logging in with different AD accounts? Sometimes it shows up 10mins later as if it needed to install it again. I
read the changes from v3 to v4 printing in Windows 8, Ive checked the event log errors, printer shares, etc. Deploying Printers to Windows 8.1 clients is poor at best even when it supposed to be easier for IT to manage. Also I was under the impression that
Windows 8.1 clients do not attempt to downloads drivers from a windows print server anymore as they opt to use a v4 print class driver.
Environment Details:
Windows 2012R2 Printer Server all patched, Windows 8.1 all patched, AD users are identical as well as the computers (reside in the same OUs) Printer is deployed to the computers, Point and print restrictions is completely disabled. Restarting the print spooler
on the client has little to no effect. Computers connect wirelessly to the network and print server is in the same building. Started pushing to the user as well to see if it helps. Windows 7 clients are unaffected and get the printer consistently.
Errors:
The print spooler failed to download and import the printer driver from \\Server into the driver store for driver KONICA MINOLTA C652SeriesPS. Error code= 800f0242.
The print spooler failed to import the printer driver that was downloaded from \\Server\print$\x64\PCC\koazca__.inf_amd64_664b51505681ff6d.cab into the driver store for driver KONICA MINOLTA C652SeriesPS. Error code= 800f0242. This can occur if there is a problem with the driver or the digital signature of the driver.
The default printer was changed to \\Server\Konica_Copier,winspool,Ne05:. See the event user data for context information.
We use GPP to deploy TCP/IP printers to a few key workstations. The GPP printers are configured for 'Replace' so when the print server driver(s) are updated, the GPP printers will pick up the new driver and install them on the clients. This does not happen of the GPP printer action is set to 'Create' or 'Update'.
Anyways, happened to be digging through the registry on one of these Win7 PCs and noticed in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\ there are literally hundreds of entries for the same printer. Example:
Control Panels -> Printers & Devices - only shows one printer. Many of the latest Windows printing related hotfixes are installed too. It occurs for multiple printer vendor drivers, so it would appear to be a Windows specific issue.
Anyone seen this before?
Faulting application name: spoolsv.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4e7
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000374
Fault offset: 0x00000000000c4102
Faulting process id: 0xc2b8
Faulting application start time: 0x01cfd732f702f24a
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
and
Faulting application name: spoolsv.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4e7
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000005
Fault offset: 0x0000000000053290
Faulting process id: 0x8ec4
Faulting application start time: 0x01cfd73287b00acd
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c6fd217d-4325-11e4-979b-848f69fd1ad4
We haven't added any printer drivers lately.
Windows 2008 R2
Windows 7 Enterprise
Topology: Central network with about 50 users/computers and 5 servers. 25 remote sites, 2-4 users/computers per site (no servers at the sites). Each site also has one network printer.
Currently all sites have the same IP scheme (we use DirectAccess for file access so unique subnets are not required). All of the printers are the same model and have the same static IP. So no matter what site a roaming user goes to printing works with no confusion.
Some new technology is being implemented that will require us to make unique subnets (which is actually desirable for obvious reasons). At the same time we will be implementing site-to-site VPNs, so there will be full connectivity to AD/central site.
So, here in lies the problem. Our super simple printing solution, now will not work. Some users roam to a dozen sites or more, will they have to have that many printers? Then they have to make sure to print to the one that is online/ready? Is there a GPO setting to hide offline printers or something? I wouldn't care if there were 25 print queues as long as only available printers were displayed. I see that there is some location aware printing features of AD/W7, but I am concerned all the offline printers will confuse users.
Any ideas?
Hi,
We are migrating printservers.
Before we had a single printserver running on Windows Server 2003 32-bit.
We have migrated all printers using printbrm.exe to a printcluster on Windows Server 2008 R1 32-bit.
We have added 64-bit drivers for all printers, and upgraded all existing 32-bit drivers to the latest version. We used the driver versions for Windows Server 2008. Both installed 32-bit and 64-bit drivers have the same version number.
All seemed to work well, so we are moving to the production environment, and switching our client computers from the old printserver to the new printcluster.
While we are deploying the new printcluster to the production environment, we noticed that Ricoh Aficio AP410N printers produceblank pages when printing from several Windows XP 32-bit client machines. There is no text on the pages. We have experienced the same problem with x64 clients.
When printing the "Test Page" directly from the printcluster servers, we have no problems. The page is printed correctly.
We are using a logonscript to remove the printer from the old printserver, and add the same printer on the new printcluster. This script runs only once. No group policy preferences are used to push printers to clients.
To summarize:
Pages are being printed correctly when printing directly from the printserver, but when printing from a client machine through the printserver, blank pages come out of the printer.
We don't have this problem with other printer models.
What could be the problem here?
Thanks!
Hi
I have a Windows 2012 r2 server print server, with 60 shared printers across about 1200 machines running a mixture of Windows 7 (32 and 64bit) using a locked down mandatory profile
All printers are deployed via group policy.
Users are informing me that printers have not installed, even if they were working fine the day before. When I try to add the printers manually, I get the following message
‘Windows cannot connect to the printer. The specified port is unknown’
It seems to be completely random
I have seen suggestions it might be to do with the maximum number of open TCP connections.
Any ideas what this could be and how I can fix it.
Print spooler stops immediate after start. Event log says
The Print Spooler service terminated unexpectedly. It has done this 7 time(s).
No Changes were made except the Windows Update. Below is a copy of event log details. switching users over to an older 2003 server.
Log Name: System
Source: Service Control Manager
Date: 6/18/2012 1:30:25 PM
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mchserv03.MCH.local
Description:
The Print Spooler service terminated unexpectedly. It has done this 7 time(s).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7034</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2012-06-18T18:30:25.316830000Z" />
<EventRecordID>61106</EventRecordID>
<Correlation />
<Execution ProcessID="504" ThreadID="568" />
<Channel>System</Channel>
<Computer>mchserv03.MCH.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Print Spooler</Data>
<Data Name="param2">7</Data>
</EventData>
</Event>
Craig
We have 3 servers set up as RDS Servers and all 3 are identical to each other Running Windows Server 2012 R2. Our DC is running 2008R2 which is also a print server. All employees are using only RDS to work. Nobody work on domain computers.
We have about 10 printers on print server and they are located in 3 different sites. These printers are mapped via group policy preferences of user configuration straight on RDS servers. Nobody can print from domain computers.
Issue 1
When user logs in for the first time, he/she can see every single printer under devices and printers, but when he/she try to print a word (or any) document and goes to file - print, he/she can see only printers that are mapped to their account via Group policy Preferences.
Issue 2
When user goes to file - print, he/she can see 2 printer with same name but one printer named as Printer1 on printservername and second printer is appearing as printer1 on printservername.doaminname.
Issue 3
Intermittently when user try to print it will throw an error message saying there is no printer installed. If user log off and log back on it will print fine. Sometime user may have to log off and log back on few times before it starts printing.
Can someone please suggest anything?
Hi!
I am having trouble adding network printers on my 2008 x64 terminal server:s (9 servers) i get 0x00000002 error.
I have tried the following, Logged on as domain admin adding a network printer i get error 0x00000002, tried to install a local printer on the server gives me error 0x00000002.
Adding local printer with Microsoft shipped drivers i get error 0x00000002
Have tried above as local admin on server, same problem.
Print server: w2k8 x64 Datacenter (all printers have 64/32 bit drivers)
Terminal Servers: w2k8 x64 Standard
Regards
Roger
Hi friends,
Today I added a new driver to our print server which I have done many times before, only this time in adding the new driver, all other printers of the same manufacturer (Canon) stopped working, with the device on everyone's computer showing "Driver update needed".
The new driver was for an iDV-ADV C5250. The printers which stopped working are all C5051's. The driver was added but at this point, no other action was taken, the driver was not used for a printer (hardware hasn't arrived yet) so the very simple step of adding a new driver in preparation for a new printer causes a major issue.
To resolve it on the Windows Server 2008 R2 print server, I selected any one of the existing Canon printers and set the driver to the new driver I added. Of course this did NOT work however then setting the driver back to what it was originally did resolve the issue... kind of. ALL users were then required to delete and re-add the printer(s) on their computers. You can see this was not a popular fault.
Although I resolved it, I really want to understand why this occurred. Can anyone help? I really need to make sure this doesn't happen again. I thought maybe printer isolation might help but you can't set a driver to isolated until after it's added can you?
Thanks.
Hi all,
i have an issue, and i'm not sure what i want is even possible.
We have a application running on a RD server from which users need to print. The problem is that the settings of the application only allow us to select 1 printer for everyone on the server (no per-user settings available).
So i thought: OK, we need to install printers per user under the same name.
User A has been assigned \\printserver\printerA by policy
User B has been assigned \\printserver\printerB by policy
No we need a script that renames the mapped printer on login from "\\printserver\printerA" to "printer" and vice versa for user B.
is this even possible?
Hello everyone :)
We have a Terminal Server running Windows Server 2012 R2 Standard.
On the server we are deploying printers from a Print Server (Windows Server 2008 R2), via Group Policy.
We are having some issues, with the amount of printers being deployed... If a user is member of a Security group they a getting a printer deployed.
But even if the user isnt part of the Group, they are getting the deployed printers - and many of the same!
Even if removing the user from the Security Group, which the GPO is deployed to - and deleting the Roaming profile from Advanced System Properties, and the TSProfile Folder from the netshare - then the problem occurs again!
Why is this happening?
Datatechnician
Title pretty much says it all. I have a print server that has an HP Color LaserJet 4600N printer installed on it, the driver is HP Color LaserJet 4600 PS Class, a type 4 driver I was offered from Windows Update several months back when I installed it. Today I want to move it to another Windows 2012R2 print server, so I tried to add it there, and upon checking Windows Update, I don't see any of the "Class" Type 4 drivers. Looking through the Microsoft Update catalog confirms most are gone.
What's going on here? Are HP type 4 drivers being abandoned and no longer offered?
Hi,
we have a problem with our print environment (HP and Ricoh printers).
We have some Windows 8 and 8.1 clients and a Windows Server 2008 R2 printserver.
Windows 8 and 8.1 is showing the printers as offline. Its seems the problem described here ->http://support.microsoft.com/kb/2713128
We already installed the fix on the server but this didn't resolve the issue.
Maybe somebody have the same issues and an alternate solution for this?
Best regardsHi there,
Hoping that someone in here have some knowledge to share J
I am currently working on a design for a global print service within the company where I work.
Despite the issues introduced in April 2014 with the KB2919355 I am still convinced that Windows Server 2012 R2 is the right OS as this gives us some administrative advantages over 2008.
What I would like to do (as Hyper-V is a no go in this company) is to use the Citrix PVS to have a master server image and then load it on to X servers. This would enable us to a) have a Load Balancer in front for spreading the load b) always have a clean server c) push queues to multiple servers without any interaction and d) just add additional servers if the load becomes +75%.
However the one issue I am up against is the spool files. Usually the spool directly resides locally on the server and is not shared with other servers. However as we plan to have multiple servers it would be really neat (well actually required!) to have a shared spool drive for all servers. This would allow the other servers to take over if one crashes.
Would anyone have some information/tricks to share so I can somehow achieve the above?
Thanks,
David