Ideale FOG omgeving voor Refurbish afdeling
-
Beste Collega’s,
Ik zit met een vraag en ik weet niet of het mogelijk is zoals ik het voor ogen heb. Wellicht weten jullie de oplossing.
Situatie:
Wij hebben een refurbish afdeling waarbij we elke desktop, laptop, thinclients etc. nakijken en eventueel repareren. We installeren een image op de machine die testsoftware bevat. Het nadeel is nu dat je dus elke machine handmatig eerst in de bios secureboot moet uitzetten en legacyboot aan moet zetten. Dan nog een keer opstarten via netwerkboot om zo de test image te installeren. UEFI ondersteunt deze verouderde server niet, vandaar dat ik het wil veranderen.
Mijn ideale situatie:
het aansluiten van alle machines op stroom en UTP en vanuit FOG aanzetten met WOL en het deployen van de testimage. Na de test gaan ze door naar een andere afdeling. En het is een gesloten afdeling qua omgeving dus verder niks spannends.
mijn vraag: is dit mogelijk?
gr
Paul
-
@Paul-0 While FOG can image many machines in UEFI more but it’s not able to handle secureboot.
-
@paul-0 As Sebastian mentioned FOG can’t support secure boot at this time so you will need to disable that if you want to boot into FOG.
Switched back to legacy mode should not be required to work with FOG. FOG supports UEFI booting no problem. You must make sure your image that contains the testing software must support UEFI booting. You can not deploy a BIOS based image to a UEFI computer and make it work. You can only deploy a BIOS captured image to a BIOS based computer and a UEFI captured image to a UEFI based computer.
I should ask what version of FOG is your server? FOG servers since 1.2.0 support uefi booting, you just need to update your dhcp server to send the uefi boot file name of ipxe.efi
If you need to boot both uefi and bios computers and you have a linux or windows 2012 or later dhcp server then its possible to make a dynamic boot so both uefi and bios computers will boot happy into FOG.
-
@george1421 said in Ideale FOG omgeving voor Refurbish afdeling:
t contains the testing software must support UEFI booting. You can not deploy a BIOS based image to a UEFI computer and make it work. You can only deploy a BIOS captured image to
Hi George,
Thanks for the reply.
The issue with UEFI i understand. But is it possible if i connect a laptop to push a image? it must show up in the fog server as a client if im right? But thats the thing. We get a lot of different hardware. So what i want is that if they have a network connection is that i push the test image on them all at the same time from the fog server console.
is that possible?
thanks
-
thanks for your reply.
Thats oke…that leaves me with one manual handeling. So if im correct,can i push an image to the connected devices without manual install fog client on them>?
So i connect the utp then disable secureboot manualy…then on the fog console push an image… that is the most ideal option. But is that possible?
-
oh little ad…
my version is 1.5.9
and have installed it on my desktop on the newest ubuntu…Just for testing.
gr
Paul
-
@paul-0 I think we have a little confusion on how you think FOG works.
You can deploy a single image to a single computer using the FOG Push unicast image.
If your network supports it, you can push a single image to 30 computers all at one using the multicast imaging.
Both ways work but the target computer must be able to take the image you can not mix uefi and bios computers using the multicast method.
Now there is a procedure that system builders can use when using FOG. In this case a system builder will build a computer using FOG and then sell that computer. The FOG server will never see that computer again so there is no need to register the computer with FOG. This procedure is what I call “Load and Go” (load the OS and the target computer Goes some place else).
To use the Load and Go method there are a few requirements.
- The target image must be full contained in that once the FOG server pushes the image, the FOG server will forget about the computer. The target computer will not have the FOG Client installed so no system renaming, or connecting to AD when using Load and Go (unless you are using an unattend.xml file, then the unattend.xml file can do all of those tasks).
- The target image must have all of the needed drivers in the image or have the FOG server transfer the drivers post image push
-
@paul-0 said in Ideale FOG omgeving voor Refurbish afdeling:
So i connect the utp then disable secureboot manualy…then on the fog console push an image… that is the most ideal option. But is that possible?
You can do this using the load and go approach. You would disable secure boot at the target computer then pxe boot into the FOG iPXE menu, then select deploy image from the iPXE menu. You never have to register the computer with FOG. But understand Load and Go method (without registering) means you will not be able to manage the target computer with FOG once the image is deployed.
-
Hi George,
That’s exactly what im looking for! Thanks, this would work for me. When we get hardware on our departmend i connect always mostley one kind of machine, so that works for me.
thank you for your great help and quik respons. Im gonna build further with this in a few weeks, and now it is a lot easier.
gr
Paul
