Posts made by anthonyglamis

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

@Wayne-Workman I just finished reading your post and the FTP WIKI. I apologize I don’t think I was understanding what you were referring to. So in my storage node settings the FTP path must match, as well as the user name and password. Thanks for the heads up. I have updated all the info. Straight from the WIKI.

Web Interface -> Storage Management -> Your storage node -> Management Username & Management Password

Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD

The local 'fog' user's password on the Linux FOG server

/opt/fog/.fogsettings -> storageftpuser & storageftppass (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)

@Wayne-Workman Currently I am not receiving an error file not found, but I assume I want a password in that field for added security. Thanks again for the input.

Now I am curious. Would FTP mismatch in credentials cause the error “image store corrupt”? I know what happened. The d1.mbr file was not created on that image. Duh…at least I’m starting to recognize some of these issues. Capturing again. This time I am trying Single disk (re sizable)

@Wayne-Workman I updated the .fogsettings file to reflect “yes”;
The ftp credentials were left blank upon install. If I change this does it also have to be changed on the fog server?

@Wayne-Workman Just deployed my image. I unchecked add to domain and it imaged and did not join to AD. The log output states: “Authentication error. CA is not from the fog server”. Any suggestions on next testing steps?
I can attempt to perform a factory reset for my most heavily used model, build an image, install the client service , register the host and capture.

@Wayne-Workman So what if I restore one of my laptops to factory default? The reason I say is we don’t use WAIK, or sysprep. Let’s say I create a master golden image, but it is time to update it for instance adding an additional program. Once the image is created can I manipulate it if I ever had to?

@Wayne-Workman Thanks for the quick response. Yes the image baseline I used was at a certain point on the domain. I removed it from the domain in order to create a baseline as I do not have a volume license with Microsoft so I have nothing else to go off of. I can try a new windows 7 license though. I have one copy. That might be my best bet. Start from scratch.
I am deploying the image now as you suggested. With the new client 0.9.10 do the new clients intended to be deployed and auto joined to the domain need to be created in AD before deployment?

@Wayne-Workman Wayne, thank you for the reply. I apologize but what do you mean by “bound to the domain”? This is what my .fogsettings file looks like.

Created by the FOG Installer

Version: 6124

Install time: Thu 14 Jan 2016 04:05:49 PM CST

ipaddress=“192.168.1.243”;
interface=“eth0”;
routeraddress=" option routers 192.168.1.1;“;
plainrouter=“192.168.1.1”;
dnsaddress=” option domain-name-servers 192.168.20.5; “;
dnsbootimage=“192.168.20.5”;
password=“0ea409”;
osid=“2”;
osname=“Debian”;
dodhcp=“n”;
bldhcp=“0”;
installtype=“N”;
snmysqluser=”"
snmysqlpass=“”;
snmysqlhost=“”;
installlang=“0”;
donate=“0”;
fogupdateloaded=“1”
submask=‘’
blexports=‘1’
storageLocation=‘/images’
storageftpuser=‘’
storageftppass=‘’
docroot=‘/var/www/html/’
webroot=‘fog/’
caCreated=‘’
startrange=‘’
endrange=‘’
bootfilename=‘’
packages=‘apache2 php5 php5-json php5-gd php5-cli php5-curl mysql-server mysql-client tftpd-hpa tftp-hpa nfs-kernel-server vsftpd net-tools wget xinetd sysv-rc-conf tar gzip build-essential cpp gcc g++ m4$
noTftpBuild=’’
notpxedefaultfile=‘’

@Wayne-Workman Is there any way to get this post categorized as “unsolved”? I am still having issues.

Update. Earlier I was successful deploying an image to 3 different laptops. These were for my Austin site. I just tried to deploy the same image to another laptop for my Austin site, and the authentication errors have returned. This is kind of blowing my mind. I am on revision 6124. I’m not really sure why I was successful 3 times and now the CA chain is broken. This is interesting.

More updates. I have 2 images, both are for my Austin sites. 1 is a baseline, the other has printers already set up as TCP/IP ports. The image with the printers is failing. The log is returning Authentication errors as stated above, and the hostname changer did not work either.
I decided to try the baseline image. The hostname changer worked. I have a “switch user” option and my domain is showing up as an option to log into. I try to login and it says “The security database on the server does not have a computer account for this workstation trust relationship”. I did stage the computer in my default directory OU before deploying the image. The log is still stating that the CA cert validation failed. Could not authenticate.

@Wayne-Workman I just updated my revision, reinstalled fog. Tried to deploy the same image that was successful 3 times today and I received an error "no disk passed (runPartprobe)
Thoughts? I checked out this thread however I am not capturing and image, I am attempting to deploy a known good image (at least before a revision upgrade and reinstall of fog).

https://forums.fogproject.org/topic/6535/windows-10-capture-deploy-woes/2