What stop code is it?

If it is 7B then the cause is most likely the storage drivers. (eg imaged as RAID, BIOS settings at new PC set to AHCI)

@joe-gill The rate is just calculated based on the amount of data sent divided by the time spent sending it. Given that it doesn’t continue at a certain point we’d expect the rate to drop indefinitely.

At a guess, I would say it loses connection with the FOG server at some point.

@tom-elliott Cool, that worked perfectly :)

@tom-elliott I tried this because I was curious. It turns out that in PHP 7.2, the mcrypt package is php-pecl-mcrypt as opposed to php-mcrypt. Installation works as the system correctly identifies it anyway, but then FOG update fails because it can’t find php-mcrypt installed.

I’m on FOG 1.5.2 currently, Centos 7.

Would have made a new thread, but this seems relevant enough to keep it in here.

@veresh The commit says the packages were added to enable compilation of iPXE binaries. As far as I understand the compiled iPXE binaries are (still?) pulled from the repository anyway, so I guess it’s to allow for updating (or modifying) the binaries manually without updating FOG

@wayne-workman I stand corrected :)

Aside from what Wayne said, you seem to be having the FOG client on your PC. The FOG Client allows the server admin to push software installations remotely using snapins, force logoff, order imaging, etc.

It cannot see what you’re doing or any passwords/usernames you enter or use. That doesn’t mean you should expect privacy on a library PC though.

@lebrun78 You could try a different disk boot command. You can choose these globally, per group or per host I believe. Default is Sanboot if I’m not mistaken.

There’s different options because different hardware handles it differrently, annoyingly enough.

There are no PHP7 packages in the official Centos repos I believe, so FOG won’t automatically sort it out for you.

On OS that does have official PHP7 packages, FOG will attempt to install those during installation.