@UWPVIOLATOR the others aren’t concerning. Feel free to fix them though. Google is your friend.

@Tom-Elliott The client is what I suspect is different as I haven’t actually been pushing the client for the last 3 months as I was instructed to remove the client from all but a couple labs. So this is the first attempt for a couple months to have the clients pushed to computers before we image them in order to take full advantage of multicasting from the local nodes. Now it seems that the process used before isn’t working completely together. If I push a client to a computer, it registers with fog, and I see the machine, I suppose (as I haven’t tested) that the snapins and power management will work on these hosts just as they always have. The problem is when I pxe boot the laptops, they show as not registered.

Now I have been running this system here for a couple years since trunk became available so it’s possible I have junk clients registered already, but I didn’t see these machines as I deleted them after removing the clients (at least not in the gui). I can verify this issue does not arise on desktop machines. I just don’t understand why the client would think it wasn’t registered.

I have no idea how any macs could be shared, as we haven’t done anything to initiate that. All clients are currently running Windows 7 so the “randomizing” of any wireless nics isn’t the issue here, but rather in the manner the client registers the hosts.

Quickreg works flawlessly, but it uses different mechanisms to register the nics I’m assuming since it’s still in a pre-boot environment.

Seems to be replicating now! Thanks!

@FiSi said in Blank page on web interface:

Please tell me it is possible to do that with fog 1.4.3

After all of this, sorry its not possible…

Just kidding, yes Win10 is possible both in legacy (bois) mode and uefi modes. UEFI modes are a little problem but is more on the hardware side than win10. Many new win10 systems are not coming with ethernet ports built in, so this means you must use an approved usb ethernet adapter to make it work.

One last comment. It is possible to setup root with a password as long as the password in the .fogsettings file is the same exact as what you set root’s password to. If you change then you need to rerun the fog installer.

@Lenain You are welcome. Does this solve the issue for you?

@x23piracy said in Could not open inode XXXXXX through the library...":

Hi,

before you sysprep try to run chkdsk, if chkdsk was ok run sysprep but don’t use option /reboot or /shutdown just use /quit, then manually shutdown your machine with shutdown -s -t 0 -f, then try to image.

Regards X23

That has worked for the guy here: https://forums.fogproject.org/post/97015

@dwcoleman Do you still see this issue? Have you tried on different devices? Always the same problem?

@x23piracy It works great ! Thanks a lot 😉

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.