Ok, I was using the wrong driver. I already had the driver on my print server, so I copied it over to my network share and updated my printer in FOG management with the proper inf settings. Looks like it’s working now! Thanks for the help!

Sorry, it is the PCL 5 driver, not PCL 6. I watched the video tutorial on the wiki re: pointing to local inf file, but I can’t find that file in windows 7.

Adding the IP got these results:

8/1/2012 12:56 PM FOG::PrinterManager Printer update was request from fog tray…
8/1/2012 12:56 PM FOG::PrinterManager Management level = 2
8/1/2012 12:56 PM FOG::PrinterManager Removing unwanted printers from host…
8/1/2012 12:56 PM FOG::PrinterManager Adding new printers to host…
8/1/2012 12:56 PM FOG::PrinterManager 1 found on server side.
8/1/2012 12:56 PM FOG::PrinterManager Installation requested for HP Printer (LEDM)
8/1/2012 12:56 PM FOG::PrinterManager Printer Installed: HP Printer (LEDM)
8/1/2012 12:56 PM FOG::PrinterManager Setting Default Printer…
8/1/2012 12:56 PM FOG::PrinterManager Failed: it looks like the local printer is missing.

Specifying the printer IP where?

Sorry, the copy and paste didn’t work that well.

Printer model = HP Printer (LEDM)
Printer Alias = WF Elem Lab
Printer Port = IP_192.168.0.64
Print INF file = [URL=‘http://fogproject.org/forum/file://\192.168.0.16\GP’]\192.168.0.16\GP[/URL] Software\WF Elem Lab Printer\hpbuio45l.inf

Printer Model:
Printer Alias:
Printer Port:
Print INF File:
Print IP (optional):

The printer is HP Laserjet 1320n. I’m using the universal print driver pcl 6 for it. What is meant when FOG gives the error that the local printer is missing?

I did review the wiki, or I never would’ve known to match the model name from the inf file.

I’m trying to add a printer with FOG’s Print Management. I have the drivers located on a network share that everyone has read access to. FOG’s log file on the computer shows the installation is trying to occur, but it fails with this message:

8/1/2012 10:05 AM FOG::PrinterManager Setting Default Printer…
8/1/2012 10:05 AM FOG::PrinterManager Failed: it looks like the local printer is missing.

These are Windows 7 64 bit pc’s. They’re not on my domain so I cannot add printers with group policy, which would be my preferred method. I’m really trying to manage things centrally from now on versus touching each pc and adding the printer manually. I figure it will be worth the effort once it is working.

Anyone have any ideas?

Thanks!

Whether I run fogprep or sysprep or neither, FOG is breaking my master boot record somewhere along the way. I created a bare bones image from a clean install, uploaded it and tried deploying it and it fails. The only other thing I can think of is that I’m selecting the wrong choice for my image partition, but I thought I read in these forums that you don’t have to count the 100mb partition from windows when making that choice. So for my image I selected single partition. It resizes the partition correctly according to the output during the upload process. Do I just have a model of Acer that is completely incompatible with FOG? I’ve tried changing SATA emulation from AHCI to IDE and vice versa with the same results.

I’m struggling with Acer Veriton VZ431G’s here. I had issues similar to yours, but upgrading the kernel to the latest version that said “use at own risk” or whatever solved that problem. Before upgrading the kernel, the machines would either restart during deployment or freeze up at random intervals.

Running fogprep gave me an error about accessing the registry, so I’m not sure if it even ran. I manually deleted the corresponding registry keys.

What do you mean the master image needs to be a full mini-setup? I’ve built images before without issues. I started this latest master over with a clean install, deleting factory partitions and letting Windows build it’s 100mb partition and using the rest of the hard drive for the OS. I specified single partition NTFS only, resizable as my image type. I created a pre-sysprep image that also fails when I tried deploying that back to a machine to make some changes.

I’ve never had partition issues like this using Ghost, or Macrium Reflect. Maybe I’m making the wrong selection in FOG somewhere, but I don’t think I’m creating the Windows 7 “master” image incorrectly.

[quote=“Blackout, post: 675, member: 1”]I personally dont use fogprep on my Windows 7 builds, I’ve never had any problems. Fogprep removes the drive letter assignment <-> UUID registry information. In saying that, some people have had problems with it (on certain hardware sets) and removing the registry information is harmless.

The master Image needs to be able to complete a full mini setup, otherwise the deployed Image will fail. This is sounding more like your problem.

I have personally seen this endless reboot loop you are talking about. There is something wrong with your Image. It could be partition related or mostly likely, Microsoft software related (Windows, sysprep auto unattend, Office, Patches, etc).

Look around the forums for information on partition / MBR related issues.

You should prove it’s something wrong with the current Image. I would install a fresh copy of Windows onto another computer of the same hardware set, sysprep and upload to a new image. Test if the new master mini setup runs correctly, then deploy the image and test it’s mini setup.

Sometimes, unless you know what is causing the problem; a full Image recreation is the fastest route. Don’t you love Windows :)[/quote]