Does the blinking cursor happen after it is done imaging?

@tywyn you realize that all windows snapins run as SYSTEM and not as administrator?

@tywyn troubleshooting dictates we remove fog from the picture entirely and just test multicast on your network to determine if that works or not. Follow these instructions to do that https://wiki.fogproject.org/wik:i/index.php?title=Troubleshoot_Downloading_-_Multicast#Testing_Multicast
Ask us for help if you need it.

These instructions have fixed this problem lots of times: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast#Clear_DB_of_non-essential_multicast_data

@gabbas change is always alittle uncomfortable. But its for the best. Older versions have bugs and will never be corrected or supported (except in newer versions with the new gui).

Is this a pending host? Can you look up this host by mac address?

@cmcgonag sounds a lot like you are in need of a customized embedded linux os to do some sort of jobs. There are better ways to do this than using fog and Ubuntu. You should look into the Yocto project or a customized copy of Debian.

@gabbas Reset the encryption for that host, should fix it. This is done in Host Management.

You can also do this en-mass via Group Management too.

I don’t see any situation in which a ram disk would help a fog server. Disk read/write speeds are usually not the bottleneck for a fog server, normally network throughput is.

@scott-b
These are interesting:

 11/29/2017 11:19 AM PrinterManager Adding printers
 11/29/2017 11:19 AM PrinterManager CutePDF Writer already exists
 11/29/2017 11:19 AM Printer Adding: \\printerservername\Kyocera
 11/29/2017 11:19 AM PrinterManager PrintUI return code = 0
 11/29/2017 11:19 AM Printer Adding: \\printerservername\Xerox
 11/29/2017 11:19 AM PrinterManager PrintUI return code = 0
 11/29/2017 11:19 AM Printer Adding: \\printerservername\Xerox Color

Because the first one says ‘already exists’ but we don’t see the same message on the others, meaning they were not there already. This is strange. Asking @Joe-Schmitt to look at it.

@bc601 There’s only one way to create groups via Host Management - that’s by selecting the hosts you want in the new group, then at the bottom of the page put a group name into the ‘Create new group’ field. Then click Update.

Also, you can add hosts to an existing group via the dropdown at the bottom of host management. You can also create new groups via Group Management.

@unknownhost99 This video on Debian 8 will also work for Debian 9: https://wiki.fogproject.org/wiki/index.php?title=Debian_8
The video is very educational, I take the time to explain Linux partitioning and other things. It’s meant for newcomers to Linux like yourself.

I think the ability to export/import the ssl directory through the web gui would be beneficial. This would help people who use fog 1.3+ and also use the fog client. It’d help them when they want to build a new server. Right now, I have written instructions for this here and here but it’s all manual work.

I think that ‘Configuration Save’ is appropriately named if it really does save all configuration including the ssl directory. Right now, ‘Configuration Save’ only imports/exports the database. If that stays the same, a more appropriate name would be ‘Database Save’, and perhaps we add another item called ‘SSL Save’ ? Lots of ways to do this. I’d like to see ‘Configuration Save’ remain the same so that all the threads/posts about it are still accurate, and just have the SSL exporting/importing added to it.

All, check this out, I appreciate feedback:
https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

@msi said in Fog is stopping deploying at 56%:

it’s a non-master.

In such case, you could try deleting that image’s files on that node - which will cause replication to copy it back. Then see if it’s fixed.

@msi said in Fog is stopping deploying at 56%:

Other client from different node and location are working fine.

Based on that statement, I think you have a multi-node setup and you’re using the location plugin… If so, is this problem node a master or a non-master?

@andrewg78 There’s an example of that very thing here: https://forums.fogproject.org/topic/9779/can-i-use-some-kind-of-script-to-create-image-and-ghost-my-lab-machines/9?page=2

@joseph-hales That article needs overhauled I suppose. Probably re-titled too. I’ll see what I can do.

If you look back in the threads here, theres posts of boot menus that contain 50 items in them.

@jgallo said in FOG UEFI image sync with storage node seems to be looping\failing on UUID info.:

Is it possible that the replication hasn’t finished prior to the next image replication check occurs?

No. I found that bug years ago, I worked with @tom-elliott to resolve it. He changed the replication so that it is aware of lftp processes that it started in the past, and will skip a file that is still in progress from a previous iteration.

@bardwood said in FOG UEFI image sync with storage node seems to be looping\failing on UUID info.:

70GB over a 10mb link

And that’s a large image over a tiny link… it could be possible that the sync isn’t finished… but it may also be having problems.

Basics first:

• Please check free space on the destination node with the command df -h Look for partitions that are full. Do not assume your huge disks are not full, please go run the command and verify there are no full partitions.
• Next, is the destination node’s hard disk failing? Maybe run a disk diagnostic tool to doublecheck.
• Third, is the source node’s hard disk failing? Run a test and find out.