I understand. I’m looking for a stable option to image devices for my company. We were using clonezilla, but are looking for a solution to be placed at each of our sites so we can have a person local that can image a device via PXE boot and that’s it. I need a tool that will image and add to the domain because I can’t physically be there.
Upon investigating fog, I assumed this was the right tool for me so I’m hoping to educate myself further and get this rolling. I’ll update tomorrow with my progress. Thanks again for the help

@Arrowhead-IT Thanks for the input. That does make sense. Hopefully I can get those back. It will save me some time.

@Tom-Elliott I am attempting to capture another image. Same model LenovoE431. I will post the output.

@Wayne-Workman
@Arrowhead-IT
Pertaining to the images I deleted from the Fog UI, they are still present in the /Images directory. So if I create a new image in the Fog UI and name the file the image name it adds. The file size is 0.0
Will this populate when I attempt to deploy the image to a new host? Just curious as I don’t want to deploy a 0.0 image size to one of my hosts lol

@Arrowhead-IT Well I’m an idiot then because after every revision I was reinstalling Fog. I tested 2 machines. The images were a success and the auto join to AD worked perfectly! This is going to make my life so much easier. Thanks guys for all the help. Thanks for your time. Now I can at least help anyone else that might have AD issues Also for someone like me who is a newbie to Linux, I might compile a write up to help anyone in the future.
Now on to figure out how to store printers and have them map automatically and I will be in serious business!

Once again thank you to everyone that replied to this thread!

@Wayne-Workman honestly you are Absolutely right, but I was so happy to get an image to work also while auto joining I was beside myself. I guess it’s back to the drawing board. I’ll create a baseline tomorrow and load a new client into it and see if I have any luck.

@Wayne-Workman @Arrowhead-IT @Tom-Elliott
Just wanted to update. I noticed the capture on my “golden” image yesterday did not capture or create the 1d.mbr file. I updated Fog today to the latest revision, 6136 (I just noticed there is another) recaptured, and checked for the 1d.mbr file and to my surprise the d1.partions file was there as well. Fog deployed this image to another laptop with success as well as auto joining to AD. I think I am getting the hang of Fog. I want to test a few more platforms. I will update, and if successful we can set this thread as solved!
Once I determine that capturing and deploying is stable I will perform my own write up. I understand that most of the info is in the WIKI, but some of it is outdated. The instructions still list fog 0.32, which if you remember the beginning of this thread, that’s what I started with

@Arrowhead-IT Removing the IP_ was exactly the fix. My printer mapped successfully both ways, locally, and via my samba share. This is good stuff.

@apathetic_admin I’m not sure if this helps you or not but creating TCP/IP definitions has been successful for me. The Samba directions via the Wiki were pretty straight forward. I really didn’t like the idea of placing a ton of printer drivers locally on my “master” images, so the Samba share worked great.

While attempting to create a delayed task I have to go forward 5 hours, so essentially the delayed task thinks it is tomorrow. This is weird. I’m upgrading to Trunk now.

@Tom-Elliott
AHHHHHHHH!!! You are so right, what was I thinking, I apologize. I will update the status after this image is complete. Maybe I can replicate the error? LOL hopefully not in my case. And yes I have been reading these forums for weeks now and you are basically on almost every Fog post Thanks for chiming in.

Wow this thread has a bunch of activity! Thanks for everyones help.
I captured an image late last night and checked /images for the d1.mbr file and it was present. I was able to deploy this image to another Lenovo E431 (this is windows 7 pro btw), however it did not join to AD, and interestingly enough it did not change the hostname either.
This is odd since yesterday Fog was actually successful in changing a hostname and adding one of our laptops to AD. Granted this was a PC we had taken off the domain in order to capture the image. We gave it a generic name LENOVO-E431-I3 and after capturing the image it would not let us change the name of the PC and kept rebooting. This of course was the client service doing it’s job. So in the Fog server we changed the hostname to what we wanted and boom after a reboot the hostname changer did it’s job and also added the laptop to AD.
I am looking at the fog .log and there is an authentication error more specifically this is from a deployed Win 7 image

--------------------------------Authentication--------------------------------

1/21/2016 10:27 AM Client-Info Version: 0.9.10
1/21/2016 10:27 AM Middleware::Communication URL: http://192.168.1.243/fog/management/other/ssl/srvpublic.crt
1/21/2016 10:27 AM Data::RSA FOG Server CA cert found
1/21/2016 10:27 AM Data::RSA ERROR: Certificate validation failed
1/21/2016 10:27 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
1/21/2016 10:27 AM Middleware::Authentication ERROR: Could not authenticate
1/21/2016 10:27 AM Middleware::Authentication ERROR: Certificate is not from FOG CA
1/21/2016 10:27 AM Service Sleeping for 120 seconds

Hello, I was wondering if I might be able to get some feedback regarding multiple servers at remote sites? If anyone has any experience and can explain their setup it would be greatly appreciated. Here is what I am trying to accomplish.
The company I work for has 21 different sites. Our IT Department is very small. I am planning on placing a Fog imaging sever at each site in the Communication Closet. As we cannot be there onsite, if a computer needs to be re-imaged the maintenance director can restart, pxe boot, and walk away.
That being said computers from time to time will have to come into our corporate office for repair and re-image. Here is my question. If I have multiple fog servers that are on their own subnets, when I re-image a pc here on my x.x.1.0 subnet, how can I expect the client service to talk to the remote Fog server once I ship it out and it connects to the remote network? Is it just a matter of changing the client config file to reflect the IP address of the remote Fog server at the location it will be shipped to once imaging is completed?
Is there a way to create a Master Node that all the fog servers can speak to? I understand that we can create a master that would push images from however some of these sites are still on DSL, so pushing an image over the network would crush our circuit. Any and all help/ideas are appreciated!

@Arrowhead-IT Removing the IP_ was exactly the fix. My printer mapped successfully both ways, locally, and via my samba share. This is good stuff.

@apathetic_admin I’m not sure if this helps you or not but creating TCP/IP definitions has been successful for me. The Samba directions via the Wiki were pretty straight forward. I really didn’t like the idea of placing a ton of printer drivers locally on my “master” images, so the Samba share worked great.

@Arrowhead-IT Just saw this. Thanks for the the reply, I’ll check this out.

@Tom-Elliott Thanks for the reply and for helping me understand a bit more. I am still unsuccessful at adding a printer.

I tried placing the driver locally on the client in C:\DRIVERS\lanier64 and placed that path on the “printer INF file” section in fog to C:\DRIVERS\lanier64\OEMSETUP.INF, still no luck. The log output states return code 0. I’m wondering if the Model = LANIER MP 5002 PCL 6 field is my issue? I copied the model syntax right from the .INF file.

I also mapped the client to the samba share Z:\192.168.1.243\printerdrivers\lanier64 Input the path on “printer INF file” to Z:\opt\fog\printerdrivers\lanier64\OEMSETUP.INF

Still no luck. I apologize if your previous explanation went completely over my head, but am I missing something terribly easy?

@Tom-Elliott OK so am I not understanding the WIKI? I set up a Samba share and dumped the driver in /opt/fog/printerdrivers/
I was thinking the Samba share holds the drivers, and you create a printer definition in Fog and the INF file path points to the Samba share directory. I followed this page.

https://wiki.fogproject.org/wiki/index.php?title=Creating_a_Samba_Based_Printer_Store_on_FOG

In order for the printer to be added to the host computer, the printer drivers must be stored in a public area, or included on the host computer. This public area can be a Novell Network share where public has read-only access, a Windows share that is public read-only to everyone, or a Samba share (possibly residing on the FOG server) that is public read-only to everyone. This share must be accessible via a UNC path as the service may attempt to install the printers before drive mapping occurs. In this share the printer drives and .inf file must exist. FOG supports install IP based (Jet-Direct) printers, public access NDS printers, Local printers, windows share based printers, (and we think, but could use a confirmation as it hasn’t been tested) AD based printers.

@Wayne-Workman
My samba share is accessible via windows machines. Directory is \192.168.1.243\printerdrivers

@Tom-Elliott Thanks for the reply, thank you for explaining what that meant. I am not receiving errors, however the printer does not get created. When I navigate to devices and printers, the printer is not installed. Is there a better way to troubleshoot this since I am getting a return code of 0?

Hello,
I don’t mean to hijack but I am also having printer issues. Mine are a little different. I am trying to create tcp/ip port printers. I followed the WIKI and this is the result of my log. Any thoughts on the last line? I searched that output but didn’t find anything. I’m assuming “Return Code 0” is a specific error?

--------------------------------PrinterManager--------------------------------

2/4/2016 5:23 PM Client-Info Version: 0.9.11
2/4/2016 5:23 PM PrinterManager Running…
2/4/2016 5:23 PM Middleware::Communication URL: http://192.168.1.243/fog/service/servicemodule-active.php?moduleid=printermanager&mac=7C:E9:D3:F6:D4:46|B8:88:E3:34:EF:3D||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
2/4/2016 5:23 PM Middleware::Communication Response: Success
2/4/2016 5:23 PM Middleware::Communication URL: http://192.168.1.243/fog/service/Printers.php?mac=7C:E9:D3:F6:D4:46|B8:88:E3:34:EF:3D||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
2/4/2016 5:23 PM Middleware::Communication Response: Success
2/4/2016 5:23 PM PrinterManager Creating list of printers
2/4/2016 5:23 PM PrinterManager Creating printer objects
2/4/2016 5:23 PM Middleware::Communication URL: http://192.168.1.243/fog/service/Printers.php?id=2&mac=7C:E9:D3:F6:D4:46|B8:88:E3:34:EF:3D||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
2/4/2016 5:23 PM Middleware::Communication Response: Success
2/4/2016 5:23 PM PrinterManager Removing extra printers…
2/4/2016 5:23 PM PrinterManager Adding printers
2/4/2016 5:23 PM LocalPrinter Attempting to add printer:
2/4/2016 5:23 PM LocalPrinter --> Name = SAC-Shipping Room
2/4/2016 5:23 PM LocalPrinter --> IP = IP_192.168.1.250
2/4/2016 5:23 PM LocalPrinter --> Port = IP_192.168.1.250
2/4/2016 5:23 PM LocalPrinter --> File = /opt/fog/printerdrivers/lanier64/OEMSETUP.INF
2/4/2016 5:23 PM LocalPrinter --> Model = LANIER MP 5002 PCL 6
2/4/2016 5:23 PM LocalPrinter Return code 0

@Wayne-Workman Update. OK I have been able to test further. Capturing, deploying, and auto join to AD is working fine. Thank you everyone for all your help! This is a pretty powerful program. I am having printer setup issues, however I will either start another thread or jump in on an ongoing printer thread. You can set this thread as solved.

@Wayne-Workman @Arrowhead-IT @Tom-Elliott
Just wanted to update. I noticed the capture on my “golden” image yesterday did not capture or create the 1d.mbr file. I updated Fog today to the latest revision, 6136 (I just noticed there is another) recaptured, and checked for the 1d.mbr file and to my surprise the d1.partions file was there as well. Fog deployed this image to another laptop with success as well as auto joining to AD. I think I am getting the hang of Fog. I want to test a few more platforms. I will update, and if successful we can set this thread as solved!
Once I determine that capturing and deploying is stable I will perform my own write up. I understand that most of the info is in the WIKI, but some of it is outdated. The instructions still list fog 0.32, which if you remember the beginning of this thread, that’s what I started with