@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

@george1421 I completely forgot I have a USB ethernet adapter. I’ll give that a try.

@Tom-Elliott said in How to get FOG to capture while host is logged in?:

Now there are utilities like “DeepFreeze” which allow you to essentially do a “snapshot” of a device, and revert to that snapshot. I don’t know that I would call this an image though.

At my job before my last job, we used a product called Centurion SmartShield that did HDD locking. Really, all they built was a fancy HDD driver that their software installs. But we locked systems before capturing them with Norton Ghost.

I wouldn’t advise locking anymore as it makes patching basically impossible to do, and every single little thing you might be asked to change is a huge P.I.T.A.

@Sebastian-Roth said in Cannot upload image to FOG... log files?:

FOG

I have a postinitscript that sends logs to a share as imaging goes https://github.com/FOGProject/fog-community-scripts/blob/master/fogAutomatedTesting/postinit.sh

@zionda said in Help with Mass Hard drive cloning station:

Wish me luck guys

good luck and don’t forget to report and don’t hesitate to ask if you have any setup problems.

@Wayne-Workman It was capture. I was testing the bits about having a mounted (local) file system under /images This was the first issue I ran into.

@Tom-Elliott Yeah I got that on the mounting.

/images/vol1 (which points to a directory on /dev/sda1) images correctly.
/images/vol1 --> /dev/sdb1 errors out

From FOS with the mount point in place if I stop the script where it errors out. I can move to /images/vol1 no problem. I can’t touch a file in /images/vol1 because /images on the fog server is shared out read only. There must be some conditional check that is failing above where it works when /images/vol1 is a directory and failing when /images/vol1 is a mountpoint. I’m just not seeing it.

@Tom-Elliott @george1421 - Here is the latest news.

I removed the mount points on the server in /etc/exports
so they only show

0_1495714432985_Screen Shot 2017-05-25 at 8.13.42 AM.png

I uploaded an image to /images/vol1/… (and it looks successful

0_1495714471319_IMG_1604.JPG

However, after looking into the restart on the server, the image file copies the name only with 0 kb.

0_1495714500576_IMG_1605.JPG

Then after the temp files remain in /images/dev/macaddress, ect. and don’t move.

0_1495714539402_Screen Shot 2017-05-25 at 8.09.29 AM.png

Now, I am confirming that a “directory” outside of a directory volume in /images/sample do work properly. Where as /images/sample is the directory with the proper rights.

0_1495714617956_Screen Shot 2017-05-25 at 8.16.33 AM.png

Image is complete and computer restarts

0_1495714756696_IMG_1606.JPG

Then the image is moved correctly into the directory /images/sample

0_1495714811668_Screen Shot 2017-05-25 at 8.19.55 AM.png

My other thoughts are that I may try. Is it an ext4 thing or should I go back to ext3, and try it.

Let me know know what you think. I am willing to work with you guys for the success of this project as always! Thank you

@xutianhong I’m glad you have it working. Tom and I are very skilled with FOG. Since fog is built using many other linux parts we know those parts too. iPXE is a great tool if you want to use it.

FOG also has a great pxe boot menu tool built in. I know some people install FOG just for pxe booting and don’t use FOG for computer imaging purposes.

You may ask a question here, we will help if possible.

If you can SSH to your NAS then go ahead and try (after backing up of course)! Quite a few NAS do support an awful lot of things; looking at my own synology, that has a dashboard where you can install web servers, MySQL, bulletin boards - all sorts really so it isn’t too much of a stretch to imagine FOG can be installed on the NAS. It all comes down to what flavour of Linux the NAS is running and how friendly it is to repo’s vs recompiling…

@Avaryan SVN or a package download most likely.

You can safely delete that directory and intialize git in /root where it will create the folders as needed. These are only the installation folders (as in everything needed to install FOG, not where everything is installed), they don’t contain any settings or the like.

Sorry on the late response. Yes to what @Tom-Elliott said, I went to /var/www/fog/lib/hooks/ and set active = true on the aforementioned hooks.