@UWPVIOLATOR said in Dell Precision 5530 Compatibility:
It does have Legacy Boot BUT NOT for Internal HD. Thus you must deploy a UEFI image to this model.
One additional comment on this point. It is possible with FOG to PXE boot in bios mode and with FOG deploy a UEFI image with a computer running in BIOS mode (I do this on systems where pxe booting in UEFI mode is broken, but pxe booting in BIOS mode works OK). Just be aware that you can not boot a UEFI image on a computer running in BIOS mode.
@andrewhancock91 Asking the internet for “runas password” brings up a huge amount of questions and answers on this. Maybe just use psexec… Or even using a text file as password input.
But that’s just my point of view trying to tackle this as low cost as possible.
@Sebastian-Roth said in Unallocated space:
df -h
Looks like i’m good to go. Thanks very much for all your help. I will save the commands for future reference.
@NeedLessMacs So far we only seemed to have this issue with Sierra and later versions. See here:
It seems as if the ones that came with Sierra (10.12) pre-installed will not work with iPXE while the ones that had El Capitan (10.11) are OK.
Possibly a Sierra update came out that also broke it. Or we are looking at a different issue here. So far I have only heard of onboard NICs having that issue but if it’s the exact same chip could also be a problem with the thunderbold adapter.
Please read the whole iPXE from above and start by compiling your own debug iPXE binary to test.
Hi there,
in an old Forum post I found a way to shedule replicating by disabling the two Services FOGImageReplication and FOGSnipInReplication. Since we have multiple locations and a limited upload WAN I wanted to ask you how can I control how much Replications can be done at the time? On our Internal testing I found out it checks if a replication needs to be done and start to replicate on every location at the same time.
Any Idea out there how to control that? 🤔
Cheers,
Gamie
BTW: I changed IMAGEREPSLEEPTIME to 60, so that after enabling the service via CRON it only takes one minute until it starts replication. Is that correct? And what happens with the replication, wenn I stop it via CRON and systemctl, does it interrupt the replication process aswell or finish it?
