Printer Manager Windows 7 Service
-
Use code tags when posting log files or anything you don’t want to be interpreted by the forum parser.
-
[CODE] 3/22/2012 2:45 PM FOG::GUIWatcher Message found, attempting to notify GUI!
3/22/2012 2:45 PM FOG::PrinterManager Printer update was request from fog tray…
3/22/2012 2:45 PM FOG::PrinterManager Management level = 2
3/22/2012 2:45 PM FOG::PrinterManager Removing unwanted printers from host…
3/22/2012 2:45 PM FOG::PrinterManager Removal Requested for \printbox\HP_Lab1
3/22/2012 2:45 PM FOG::PrinterManager Printer Removed: \printbox\HP_Lab1
3/22/2012 2:45 PM FOG::PrinterManager Removal Requested for \printbox\Science
3/22/2012 2:45 PM FOG::PrinterManager Printer Removed: \printbox\Science
3/22/2012 2:45 PM FOG::PrinterManager Removal Requested for \printbox\HP_Color
3/22/2012 2:45 PM FOG::PrinterManager Printer Removed: \printbox\HP_Color
3/22/2012 2:45 PM FOG::PrinterManager Server Match: \printbox\journal printer will stay as is
3/22/2012 2:45 PM FOG::PrinterManager Adding new printers to host…
3/22/2012 2:45 PM FOG::PrinterManager 1 found on server side.
3/22/2012 2:45 PM FOG::PrinterManager Printer already installed \printbox\journal
3/22/2012 2:45 PM FOG::PrinterManager Setting Default Printer…
3/22/2012 2:45 PM FOG::PrinterManager Setting default for \printbox\journal
3/22/2012 2:45 PM FOG::PrinterManager Remaining: 6 Sending message to FOG Tray…[/CODE]The steps i took were I added the new printer (Jounal), then removed it. and tried to re add it. This is the log from those steps.
Up until the printers is removed and you try to re-add it, everything is great. Once a printer is removed, the FOG service gets confused, and attempts to continually remove the printer. It will also not re-add the printer that was removed.
attached is the error that pops up with “Sending message to FOG Tray”
[url=“/_imported_xf_attachments/0/78_fog.png?:”]fog.png[/url]
-
I will start experimenting with FOG printers in Windows 7 Pro 32 bit using FOG 0.32.
My plan is to add printers to FOG server.
[LIST=1]
[]Record status of interactive services detection service
[]Assign printers to hosts
[]Verify printers on the host
[]Remove printers from host
[]Add same printers back to host
[]Report my findings.
[/LIST] -
[quote=“chad-bisd, post: 2520, member: 18”]I will start experimenting with FOG printers in Windows 7 Pro 32 bit using FOG 0.32.
My plan is to add printers to FOG server.
[LIST=1]
[]Record status of interactive services detection service
[]Assign printers to hosts
[]Verify printers on the host
[]Remove printers from host
[]Add same printers back to host
[]Report my findings.
[/LIST]
[/quote]That would be great.
Can you also give some information about the print server you are using, as well as the driver you are using.
I am currently using the universal 32/64 bit driver package from HP and Lexmark. I think that may be causing an issue, I am standing up a new 2008R2 print server and will be testing with the basic driver packages for each printer model.I found out that fog checks for printers in the location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3
If you delete any driver entries below there, the printers uninstall and FOG sees they are gone, and allows them to be re-installed.
-
Our print server is Windows Server 2008 R2. Some drivers are Kyocera, some are Brother.
-
Stood up a new 2008R2 print server with 1 printer installed, a single Hp laserjet 1320, the only driver installed was the 64 bit OS driver specific for that printer.
Freshly imaged Dell 790 windows 7 64-bit .
Upon adding to the domain, there was an interactive services logon error, that the printer already existed.Rebooted and the printer is added to devices and printers but then the error from above, “operation could not completed…”
Removed the printer from fog, refreshed printers through the FOG tray. Printer removed from Devices and printers, but stayed in the registry.
Re added the printer in fog, restarted the FOG service,
[CODE] 3/28/2012 11:38 AM FOG::PrinterManager Management level = 2
3/28/2012 11:38 AM FOG::PrinterManager Removing unwanted printers from host…
3/28/2012 11:38 AM FOG::PrinterManager Server Match: \pserver2\TechRoom printer will stay as is
3/28/2012 11:38 AM FOG::PrinterManager Adding new printers to host…
3/28/2012 11:38 AM FOG::PrinterManager 1 found on server side.
3/28/2012 11:38 AM FOG::PrinterManager Printer already installed \pserver2\TechRoom
3/28/2012 11:38 AM FOG::PrinterManager Waiting for tray to load…
3/28/2012 11:38 AM FOG::PrinterManager Setting Default Printer…
3/28/2012 11:38 AM FOG::PrinterManager Setting default for \pserver2\TechRoom
[/CODE]The printer never shows back up in devices and printers.
EDIT:
Confirmed that if I removed the registry key placed for the print driver, restart the print spooler service, and refresh the FOG service, or refresh printers from the FOG Tray, the printer installs back.The issues seems to be with FOG looking in the registry for the installed printer. This will also cause an issue with using the Universal Drivers since it only puts 1 driver in the registry no matter how many different models of that brand you install.
-
[quote=“chad-bisd, post: 2520, member: 18”]I will start experimenting with FOG printers in Windows 7 Pro 32 bit using FOG 0.32.
My plan is to add printers to FOG server.
[LIST=1]
[]Record status of interactive services detection service
[]Assign printers to hosts
[]Verify printers on the host
[]Remove printers from host
[]Add same printers back to host
[]Report my findings.
[/LIST]
[/quote]Have you had a chance to test this yet?
-
[LEFT]No, sorry. been super busy with state mandated testing and getting student laptops ready. It’s still on my to-do list though.[/LEFT]
-
I understand.
Just wanted to give this a bump so no one forgets about it.
-
You dont want to disable “interactive services detection service”. This is a new Windows 7 service that stops bad services from interacting with your desktop.
This is why you need to switch into it to see the popups (errors) from the FOG client.
It does look like either a windows issue, fog service code issue or printer driver issue.
The source code for the Printer Management is included with FOG. I would go through the source code, become familiar with the code, then add more debug information to the log output. You need to know exactly what the FOG service is doing.
-
We seem to be experiencing the same problem. It looks like FOG never removes the printer drivers from the registry. It always seems to state that they are installed, even when they clearly do not show up in the Devices and Printers.
-
Blackout gave me some more information to go on, i’m currently looking into the source of the printer manager.(no promises)
I think it has to do with the prinui commands used for a network printer install which I think it does by an per machine enumerated install.
-
The FOG client code has never been formerly tested on Windows 7 with its “interactive services detection service”.
I have no doubt this is a bug and related to this.
If FOG can add, but not remove it’s either:
A) trying to remove the printer incorrectly (probably not) or
B) being denied permission to remove the printer from the registryTry editing the services properties, make it run as your domains ‘Administrator’ (or an account with Administrator access).
Stop -> Start the service… can it remove the printer?Please report back your findings.
-
Is this still a problem?
