i like the idea of using /quit instead of /shutdown and getting sure the shutdown is a real one with shutdown -s -t 0 -f 😉
I never used the chkdsk portion but it would not do any harm 😄 but wasting time :p… well i do a defrag instead.

If there is still a hdd i think it would make sense to defrag before you write cereal to it 😉

@Sebastian-Roth Thanks alot i will try that 🙂

@chris178 Look in the FOG community scripts on git-hub: https://github.com/FOGProject/fog-community-scripts

Wayne wrote an excellent script called MakeFogMobile Download and install that. His script sets up a cron job to check to see if the IP address changes if so then it updates the fog configuration.

@joseska For other fog variables you can make http call to the fog server for the other settings from inside your snapin script.

Here is some info: https://forums.fogproject.org/topic/9613/invoke-hostinfo-php-from-powershell

Hello. I know this is quite an old Post but it is quite close to my issue. I managed to deploy a dualbootloader (grub legacy) with a Ubuntu and a Windows 7 OS. Now i just wanna replace the Windows 7 with another Image but i wanna keep the existing Bootloader and all other OS in it. Is there a way to deploy a single OS into this bootloader or do i have to deploy the whole thing again (Grub+Ubuntu+ Windows 7)? Also is it possible to deploy an OS and then integrate it into the original FOG Bootmenu (Not just an iso i mean the native os)?

@Wayne-Workman Thank you too ! Will work this out 🙂

If i’ve any trouble i’ll come back here !

Nothing you should know other than you’ll be pleasantly surprised when your knowledge about Ubuntu directly applies to Debian while also having fewer problems too.

1.4.4 is the current stable release as of today.

@markus1204 said in FOG SERVER IMAGE TYPE:

.WIM is only used with Windows Image. These files cannot simply be added to the FOG Server and used as the image data on the server. Fog uses Partclone to create its images, and partclone is NOT the same as WDS/MDT/WIM files. We store the files with the .img extension so people know it’s an image file, but these are compressed (typcially). We don’t add the compression extension as users are now able to select their own method of compressing the image.

@Benjamin_D said in Adding FOG database to another FOG database.:

the centralized AWS EC2 FOG server gets up and running.

You will absolutely want to use certbot to configure https on that machine.

have you considered setting up the storage node, disabling replication, and updating the files manually?

@sjensen said in Moving FOG virtual server to a new server.:

@Wayne-Workman is there a specific process you used? Did you export the VM?

No, I migrated. This is a Hyper-V feature.

I feel I should add the only reason FOG doesn’t win on “disk to disk imaging” is because of how it’s configured to operate vs an inability to do such a thing. It can most definitely do Disk to Disk imaging, but it’s written to take advantage of mass imaging particularly over network.

@Maorui2k From your description the issue could still be caused by some of your machines instead of the switch being the bottleneck. Again, I am not saying that switch isn’t causing this. Just want to point out that testing PCs in batches doesn’t cost you money (like a new switch would) but only some time.

Multicast in FOG works pretty similar to how Ghost does it. Although back at my old working place we had strange performance issues which we never had using FOG multicasting!

@Wayne-Workman Is for my institute, I’m peruvian, and my institute is SENATI, is a tesis Technical

@aparker Interface = the interface the node that’s being configured uses. (This is only used for bandwidth page anyway so not really important).
Yes, the management username/password is the linux user and password fog creates for FTP uses.

Look for setupact.log and setuperr.log files under the following paths:

C:\Windows\Panther
C:\Windows\Panther\UnattendGC
C:\Windows\System32\sysprep\Panther

Additional log from this post: https://forums.fogproject.org/post/96860

But now, i know all sysprep logs … :

cbs.log
setup.etl
session.xml
setupact.log in Windows folder
setupact.log in Windows\Panther folder
setupact.log in Windows\Panther\unattendGC folder
setupapt.dev in Windows\inf
setupapt.offline in Windows\inf
setuperr in Windows\Panther …

@cnkpadobi FOG Settings -> FOG Linux Service Sleep settings

Not sure if there’s an easy way to track if replication is finished, to be honest. I don’t use multiple nodes myself, so not an expert on replication specifically.

There’s also this: https://wiki.fogproject.org/wiki/index.php?title=FOG_security

In the reports section there is an imaging log. Go to report management and on left side column there is Imaging Log. It should show all the relevant data and you can even export it to csv or pdf.

It’s possible you need a current version. I am running Fog 1.4.0.

Jason