We solved by doing the following:

On the FOG-Server install Winbind:

sudo apt-get install -y winbind libnss-winbind

Edit the Samba config:

# /etc/samba/smb.conf [global] ... workgroup = <domain/workgroup> ... wins server = <ipofyourwinsserver> ...

Edit the nsswitch config:

# /etc/nsswitch.conf hosts: files dns wins

Reboot your server.

On the Windows 7 clients we had to add the following firewall rule:

netsh advfirewall firewall add rule name="FOG Service" dir=in action=allow remoteip=<ipofyourFOGserver> protocol=tcp localport=445

That worked for us.

@plegrand said in Installing FOG on Debian Stretch fails:

Is it possible to only upgrade debian , or is it better to reinstall everything from scratch ?

You could do either. There are pros and cons for both. That said - I don’t test upgrading Debian that already has FOG installed - I only test installing fog on upgraded Debian. And upgrading always involves some risk.

@dooleyrd What version of FOG are you using?

@Sebastian-Roth This fixed the issue! Thanks and keep up the good work!

@Tom-Elliott

The resolution here was the following…

My image WAS corrupt. It DID image just fine with UniCast. I remade my image and all is happy. I also made an adjustment to the resize option on my image. I set it to be resizeable.

I’m all going good now. All is happy. 🙂

Just in time for my server upgrade!! I’ll be installing Debian here in the next couple days…

Cheers!!!

Joe Gill
Townsend K-12 Schools

@Sebastian-Roth

Thanks for helping me on this one!!

I finally got it!!! I made those adjustments… BOOM! It worked! 🙂

Here is the end of the log file for a newly imaged machine this morning which is still working on downloading a snapin. The 10.24.25.165 IP is our main Fog server. The building where the machine resides local nose is at 10.40.25.165. The image itself deployed correctly from the local node.

----------------------------------------- ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Version: 0.11.11 6/20/2017 10:29 AM Client-Info OS: Windows 6/20/2017 10:29 AM Middleware::Authentication Waiting for authentication timeout to pass 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/management/other/ssl/srvpublic.crt 6/20/2017 10:29 AM Data::RSA FOG Server CA cert found 6/20/2017 10:29 AM Middleware::Authentication Cert OK 6/20/2017 10:29 AM Middleware::Communication POST URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&authorize&newService 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM Middleware::Authentication Authenticated 6/20/2017 10:29 AM Bus Registering ParseBus in channel Power 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&configure&newService&json 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/management/other/SMALL.png 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&mac=98:90:96:BF:CB:76||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/service/getversion.php?clientver&newService&json 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/service/getversion.php?newService&json 6/20/2017 10:29 AM Service Creating user agent cache 6/20/2017 10:29 AM Middleware::Response Invalid time 6/20/2017 10:29 AM Middleware::Response No Printers 6/20/2017 10:29 AM Middleware::Response Module is disabled globally on the FOG server 6/20/2017 10:29 AM Service Initializing modules ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM HostnameChanger Checking Hostname 6/20/2017 10:29 AM HostnameChanger Hostname is correct 6/20/2017 10:29 AM HostnameChanger Attempting to join domain 6/20/2017 10:29 AM HostnameChanger Host is already joined to target domain ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM SnapinClient Snapin Found: 6/20/2017 10:29 AM SnapinClient ID: 86642 6/20/2017 10:29 AM SnapinClient Name: MS Office 2013 6/20/2017 10:29 AM SnapinClient Created: 2017-06-20 09:34:39 6/20/2017 10:29 AM SnapinClient Action: 6/20/2017 10:29 AM SnapinClient Pack: False 6/20/2017 10:29 AM SnapinClient Hide: False 6/20/2017 10:29 AM SnapinClient Server: 6/20/2017 10:29 AM SnapinClient TimeOut: 0 6/20/2017 10:29 AM SnapinClient RunWith: cmd.exe 6/20/2017 10:29 AM SnapinClient RunWithArgs: /c 6/20/2017 10:29 AM SnapinClient Args: 6/20/2017 10:29 AM SnapinClient File: Office2013-32.exe 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/service/snapins.file.php?mac=98:90:96:BF:CB:76||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=86642

@Tom-Elliott
Hi,
It’s ok but just a detail in fog.log we no longer see the list of shutdown/reboot which are programmed.
Have a good day.

@Avaryan Thanks Avaryan. There was nothing in the target computer. Not sure what happened.

Thank you !

Just test and the host are now created

PS : How can I make solved ?

Checking the CentOS repo just now I saw a new package being available since 13th of June - search for rpcbind here. Anyone keen to test? @neodawg

@JJ-Fullmer Don’t worry about this duplicate post. It was just a lucky guess of mine that this could be connected. As well it’s good that you brought up this issue again as I would have forgotten about it. Checking the CentOS repo now I see a new package being available since 13th of June - search for rpcbind here.

@jaoyer said in Image Capture FTP Failure - Could Not Create File:

Yes. Taking the “/” out of the name fixed my issue.

I think we should reconsider, maybe we should filter out the /'s in the image name, but allow them in the image path. If they were in the image name I can see bad things happening. (I haven’t confirmed if they are allowed in the image name or not, I’m only suggesting based on this discussion)

@cjesso said in Unable to register machines to FOG:

I used an older “dumb” switch and i was able to successfully register a host.

If an older / unmanaged switch solved your issue, then have your network engineers look at your switch configuration. Make sure one of the fast spanning tree protocols are enabled (RSTP, Fast-STP, or what ever your switch mfg calls it). This will allow your switch port to start forwarding data right away instead of waiting for the obligatory 27 second timeout of start spanning tree protocol.

@rwakc well, it would be technically possible to set up a method where you could be automatically imaging any device pxe booted from the network, and set up multiple dhcp scopes on different network ports, serving out different pxe boot files with embedded scripts. that way, you’d be able to choose what image the system gets imaged with by choosing what network you plug the device into.

That is correct. I have tried both Chrome and IE. Same result with each.

I’m confused how init.gz was even a thing? Were you building custom init’s (or reworking the original init’s) and re-zipped as .gz?

In case anyone is running into this same iPXE error again. Please read this thread. Old initrd files (init.gz from October 2014 instead of current init.xz) were in place and caused the problem.

Not sure if this was the case here to but I doubt that ubuntu server was the problem!!

@chris.dees If it works for you, then it was the right fix. Run with it.

@Quazz I am using the Ubuntu VM as my FOG server. I don’t want to use the whole server with ESXi for storage also, just for the server portion. That is why the old Xserve is getting Ubuntu installed and set up as the NAS. I can then use it as a storage node as well as storage for files for things like computer backup and storage for files from our art department. Since the Xserve is just going to be a NAS the IPXE thing shouldn’t matter.