@Tom-Elliott we already had FOG_TASK_FORCE_REBOOT set but to no effect. I will try disabling it completely.
Btw. I cannot mark answers of others as correct…

@Tom-Elliott

Yes sir! Things are working well! I’ve multicasted several machines this afternoon without a hitch. Yay! Thanks!!

@Tom-Elliott
i’ts working with the fog server 1.4.4 SVN 6077.

Thanks a lot.

Can you unset the filter after “checking” the boxes to see if they’re all being checked accidentally?

@chief said in Windows 10 Enterprise Fog Client Install:

How do you install the Fog client so that on install it will boot, connect to AD etc?

Install it before going into audit mode.

When I was doing a lot of imaging, I didn’t sysprep. See this older post: https://forums.fogproject.org/topic/8906/to-sysprep-or-not-that-is-the-question

@Tom-Elliott

It was on Raid, so I changed to AHCI. No Joy, still get the same message.

Ok…well not sure why or how I had a couple of machines showing that same error…but I started rebuilding a different machine from the OS up and it captured with no problems. Thanks for your help.

Thanks, it’s clear now.

You can mark it as solved, i will export/import on a fresh install when i will have some times

@Tom-Elliott Dude everyone here gets it and appreciates what you do! Thanks for everything!

@Avaryan That did the trick! I had a feeling it was just a location problem. I can now boot to the ISO. Thanks for the help!

@jlouie.smart that’s too difficult and not supported and I will not help you with it. Just migrate the data and images to a new box, leaving the old box untouched. When done, shutdown the old box. https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@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.