@bmorine Sorry, I lost track of this in the busy time before X-Mas. I found and fixed this issue in the dev-branch so this will be part of the next release. If you want to use it beforehand feel free to switch to the dev-branch.

@Quazz I do the following:

click Images multicast image give session name client count (12) timeout (0) choose image Start!

The strange thing is, sometimes it reaches the client count. Sometimes not.

@dirtrunner21 Almost forgot to tell you that you need to upgrade all your nodes if you go from 1.5.4 to 1.5.5 or dev-branch. See the release notes on 1.5.5!

@Rudy-Delsaut Would you tell us how you solved the issue?

@Sebastian-Roth this can be addressed from the location plugin under the fog configuration. Location adds a fog setting for allowing snapins to be downloaded from the host location or the master storage node the snap in resides within.

@BrentC @fry_p Thanks heaps for reporting this. I just fixed it. You’ll find the very latest kernel at the top of the page again. Version 4.19.6 as of now.

@Tom-Elliott
Thanks Bro. It’s WORKING I JUST CHANGE MY HOSTNAME which one is my computer name in windows 10…
hats off…:-)

@waveydavey Topic Tools->Marked Solved

I took care of that for you.

@Sebastian-Roth thanks. i’ll try this and get back to you with an image of the details if it fails

@agray Yes, you should only have to answer the questions the first time, because the next time you run the setup script it pulls from the /opt/fog/.fogsettings file.

@thegiantcat

I rebooted the server, and recreated / restarted the task. After this it completed without issue.

@Sebastian-Roth on the fog server itself. it is not relevant to the error previosly posted sorry. i saw it when i logged into my vm server.

@agray Best to use the script (see the linked forum post on instructions) to change back your FOG IP to the one you have in the internet network (192.168.105.238). Then re-run the installer - hopefully running through. Now move your server back to the other network and again change its IP (now to 192.168.1.105) using the same script again.

No need for internet after the install. But if you ever need to re-run the installer… same procedure again.

Thank you everyone for your help. I had networking team move to same vlan and it worked fine. Then i had them move to seperate vlan and use wireshark. I found out we had sccm pxe setup. This was done long time ago. No one removed the forwards on the router.

Now we have it working once we removed the entries.

@Baessens Maybe i need to change the UID of my FOG installation? ?
Edit: changed the UDPCAST INTERFACE to eth0, still same problem.

Also, Is this wrong?

ict@fogserver:/images$ ls dev postdownloadscripts Priminfowin10pro lost+found postinitscripts priminfowin10pronewofficekey ict@fogserver:/images$ cd dev ict@fogserver:/images/dev$ ls dev postdownloadscripts

EDIT: re-running the installer seemed to fix the issue.

Hi @NT_Tech ,
The access control Plugin works, but is possible that you need to do some changes manually in the code.

I need to know to help you some things about your server.

Do you use LDAP plugin to validate your students?

@george1421 DUDE it worked after adding imgFormat=0 (for gzip). Thank you again!

For anyone having the same issue I ended up with this GRUB menu item:

set myfogip=10.100.71.8 set myimage=/boot/bzImage set myinits=/boot/init.xz set myloglevel=4 set timeout=-1 set fogimage=2018-07-17Win10-1803UEFI set imageid=9 insmod all_video menuentry "1. FOG Quick Image Deploy $fogimage" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=$myfogip/fog/ storage=$myfogip:/images/ storageip=$myfogip boottype=usb consoleblank=0 rootfstype=ext4 imgPartitionType=all chkdsk=0 capone=1 type=down imgid=$imageid img=$fogimage imgFormat=0 imgType=n osid=9 echo loading the virtual hard drive initrd $myinits echo booting kernel... }

Changing the interface to enp2s0 solved the problem - many thanks George, really appreciate your support.

@lxrsd Now on this part. Its giving you a bitlocker screen when you boot the iso image?

This may show ignorance on my part with bitlocker, but isn’t bitlocker dependent on uefi mode?