@x23piracy finally figured out snapin packs and they worked perfectly. Thanks guys

So, worked remotely and was able to help determine part of the problem.

Installed apachetop and took a look, found a lot of things still looking at servicemodule-active.php. We moved away from this call as it had some weird issues on its own. Moved the file and the GUI become much less sluggish. Worked to get phpmyadmin working as well. This wasn’t a problem with php-fpm vs. libapache2-mod-php (though I did make sure phpmyadmin would access using the php-fpm system). Part of the problem that was happening was the rewrite rules that handles api system.

Moved the rewrite rules into the directory stanza of the fog.conf. Made this update in the working-1.5.1 branch as well. I haven’t had time to test whether this move actually still allows the system to work, but it should. Will work on that this weekend (testing to see it works properly).

Also, we are still working to help purge the db of old stuff that’s no longer needed.

@tom-elliott said in Target cannot shutdown if program is open:

You were trying to say MOVE3 was modifying the abilities of the FOG Service.

Right
But MOVE3 has problems of its own. Can’t tell if the key is there or not. Now we have the server room under lock and key (3rd world country lol) so I don’t know what the error was.

@Wayne-Workman that tool helps with TCP/IP printers, not network shared ones.

@BrendoJohnso Can we see a screenshot of the printer config in the GUI (feel free to replace any sensitive information), as well as the C:\fog.log from a machine that is failing to add the printer?

You could also try a shutdown -s -f on the machine, that has helped me in some cases.

In addition to what George asked, what are the image settings for what you’re trying to upload? Does this happen on other machines as well?

[mod note] Marking as solve. I setup a teamviewer session with the OP and helped him fix this and a few other issues. At this point the OP is imaging as designed now.

In the end it wasn’t what FOG was doing, but the OP ran out of disk space on the root partition, and that caused mysql to not start. Flushing some failed uploads provided enough disks space to restart mysql and fog.

Before this thread dies, I just want to mention how much better the newest Fog Client has been. The version offered with v1.4.4 always gave us issues of not restarting the computers correctly after imaging, resulting in needing a few manual restarts. Sometimes it wouldn’t join the domain or change the hostname properly either. v11.15 has been not shown any of these issues and has worked flawlessly for us so far!

@george1421

Since it’s working, I’ll keep it as is.

Thank you for the quick resolution and for everything you do.

Tom

@Wayne-Workman I apologize I meant to say storage group, I figure ‘“default” storage group’ leaves enough context clues for the reader to infer that a “storage account” is a storage group.

@Sebastian-Roth thank you for the speedy response as well!

The solution to the issue was that I had to create a separate storage node to correlate to the storage group being created, and then setting the storage node to the corresponding storage group. The purpose for this was to better organize snap-ins to certain “task groups” like what is present in Norton Ghost, I hope that this helps.

@george1421

I got it working, I had to change the permissions slightly differently.

Cross linking with https://forums.fogproject.org/topic/11573/increased-network-traffic-since-1-5-0-upgrade-snapins , as a replication bug could cause the web GUI slow down.

Can you explain a bit more about how/why you are using grub?

I don’t have my flash drive with me but if I remember correctly you can chainload from grub to tftp://<fog_server_ip>/ipxe.efi to chain from grub into FOS’s iPXE menu.

This has been resolved. I updated to FreePBX 14 (CentOS 7) on the golden image and it correctly sets up the NIC’s on the imaged machines. Thanks for the help

For future readers, this article outlines how to migrate a fog server: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

Yeah I’m really surprised time has anything to do with it?? @Tom-Elliott is time involved anywhere? I know that checksums are not affected by access/modification times at all.

@imagingmaster21 said in Image Not Capturing:

The blue part clone does show up on the client and does act like it went through on the client …

What do you mean by “does act like”. Does it actually read data from the drive. I mean do you see the byte count go up at reasonable speed or does that jump as well? Sorry if this sounds stupid but I just haven’t got an idea yet. Maybe you can take a video of the client screen while this is going on. Possibly there is something that jumps at us.

@tesparza said in Snapin arguments? For EXEs:

Kurzweil 3000 v15

http://support.cambiumtech.com/index.php?pg=kb.page&id=1827#link5

I would think that’s up to the software drivers themselves. Simply doing “IP Printer” would not be sufficient. For this I’d recommend installing the printer fully (via IP_port as possible) and seeing that the driver is likely not pre-installed on all the machines, I’m not sure that you’ll be able to regain the functionality (Maybe if you inject the driver before imaging?). Once you’ve installed the printer and can validate it has printing and scanning capabilities download the PrinterManagerHelper.exe

This should give the exact config you would use for configuring your printer in fog.