@Tom-Elliott If I convert the disk to GPT (which wipes over the clone). After I clone the drive again (after converting disk to GPT) I will need to segment the drive in 4TB partitions (excluding OS partition). Since there will be several partitions (ex. (2) 4TB partitions) how will this need to be setup up in FOG regarding images moved across several partitions?

I did do this at my last job for one classroom.

We had mixed models in there, some were Lenovo, some Dell. I hate mixed model rooms. But anyways…

I had three groups for that classroom. One for the whole room, one for the Lenovos, one for the Dells.

Before deployment, I would use the classroom group to ensure exactly and only the snapins I wanted were set for the entire room, the right printers, the right AD Credentials.

Then with the two sub-groups I set the image I wanted each model to have.

Then I would deploy the Lenovos and Dells separately using their groups. Both groups would wake, image, boot, join the domain, deploy snapins and printers.

Like magic.

@Schuede Please check:

FOG Configuration Page->FOG Settings->Web Server->FOG_WEB_ROOT and make sure it’s set to /fog.

There is no function like that in fog. You could create a FOG snapin (deployment package) to do something similar. But the prompting will still be an issue. That capability doesn’t exist today.

@danpbow create a batch script (with .bat extension) to do exactly as you need.

At the end of the wmic command tack on output redirection like > \\x.x.x.x\my_share$\%computername%.txt

Ending a share name with $ in windows makes it undiscoverable, this is a security thing I recommend you do. The share should allow read/write in the share and security tabs for anonymous logon - this is because the fog client runs as system on the local machine.

Once the script is working manually, you would create a new snapin and use the batch template and upload the script. Then just try it out on a few hosts in fog web interface.

Go to Fog Configuration --> Fog Settings --> General Settings --> Check the box next to FOG_FTP_IMAGE_SIZE

This might cause your image page to load slower depending on how many images you have.

@chris.dees I started to create a POC document of what you might be looking for in this tutorial. https://forums.fogproject.org/topic/9449/dynamic-fog-replicator-transfer-rates The mechanics of the script work on my test system.

The idea is to create the ability to change the transfer (bit) rates used by the replicator service based on the time of day. While this isn’t exactly what you want the same concepts can be applied to start and stop the replicator service based on time of day.

The follow commands to stop and start the replicator service.

On a sysv based system
service FOGImageReplicator stop
service FOGImageReplicator start

Or on a systemd based system
systemctl stop FOGImageReplicator.service
systemctl start FOGImageReplicator.service

@Tony-Ayre just wanted to acknowledge that this is definitely a limitation of FOG backend that we were handed when @Tom-Elliott picked up this project. Our current rewrite addresses this problem (and most scaling problems), but it’ll be a quite a bit before FOG 2.0 is ready.

@dureal99d said in How does fog see drives in a system:

Linux sees my drive as /dev/sdc1, however a booting fog sees my same boot drive drive as /dev/sdd1

Make sure you don’t have any SD cards stuck in the system. Also is the hard disk a hybrid drive (flash and mechanical)? Did you install Linux on the system or are you just live booting from a flash drive?

Can we get the output of lsblk please?

Good to know… Thanks

@Tom-Elliott Ok Thank You!!!

I see. Thanks everyone for your help. For this customer, we’ll just use USB’s initially (since they told us yesterday they’d changed their deployment method and we need it by Friday…) and then see if we can work to a better long-term solution after that.

Thanks everyone!

@Wayne-Workman There’s already reports for this. Login History, and Hosts and users.

This would not present the info on the host management page.

A hook can/should be used to perform this if you really feel it necessary though.

@Tom-Elliott

Fantastic!

I use to, had no issue.
I now use turnkey LAMP distribution for fog server deployments, has webmin preinstalled. All works fine

@Wayne-Workman

I have to take back, what I said earlier.
When I first tried to migrate the database, I apparently did something wrong while exporting the db, because the size of the dump wasn’t nearly as big as it is now, when I tried it again. I now was able to successfully import the database and I have hosts, image definitions and users showing up properly in the web interface.

The next step is to perform all of this on my actual FOG server, as this was only a test with a VM.

Thanks for the help everyone!

Many thanks for your reply.
I think, for the beginning, i will try the Quazz’s advice.

I will post my experience in this topic later …

@Wayne-Workman

Of course. I’ll keep you updated with my progress.

@asbenavides I can say these commands install Acrobat Reader DC very well. I don’t use snapins so you may need to translate that into snapin format. We use a different tool, but we deploy using the following commands in a batch file.

start /wait msiexec.exe /i AcroRead.msi TRANSFORMS="AcroRead.mst" ALLUSERS=1 /qn /norestart start /wait msiexec.exe /i FontPack1500720033_XtdAlf_Lang_DC.msi ALLUSERS=1 /qn /norestart

There is a tool “adobe acrobat dc customization wizard” that allows you to customize the Acro Reader install (which creates the transform file used in the above command). It lets you accept the eula, makes customization to the reader install there are quite a few guides on the internet for this, just search. For example: http://www.itninja.com/software/adobe/reader-6/dc
We throw in the APAC font pack file because we do interact with Asian countries.

@lebrun78 said in Choising a storage management:

if i rename /images to /imagesold and create a new /images where is mount //fog032/images and then copy the contents of /imagesold to the new /images, it should works, no ?

It will work. I’ve done a lot of stuff like this before. Dedicating an entire physical partition on a physical disk is the simple way to go about it but it’s not exactly flexible by design. LVM solves those problems. If you’re using logical volume groups and logical volumes, you don’t have to do all of that mess you were talking about (transferring, renaming), you just add space to the volume group, then the logical volume.