• We have a lot of computers, so we created groups to where each set of computers had their own group, and image, specific to the computer we use (i.e. Dell - Teacher Workstations; Lenovo/Acer - Student Laptops). We started to build up groups, had some fussing with it, and eventually squared all of that away.

    The issue behind this is: we need multiple kernels. So, we would download a kernel, name it, apply the name of that kernel to a group of computers that we use. (e,g; KS - Lenovo Image for Student Laptops - Named kernel for the image: LENOVO)
    We tested it, and it worked perfectly fine. We switched over the kernel and still says it found the file even if we remove it from the active task and redeploy it, but when we try to do the same process to the next computer–separate group; made the group kernel name ACER–it will not take it. We remove the group kernel name, and it starts to work perfectly fine.

    Now with that, even though the Acer goes through the imaging process just fine, the Lenovo we had started before will not image. I would make a guess saying it has something to do with the kernel not being what we always use to image with, but my co-worker says it should not matter because we had named the Lenovo kernel before we switched it over to our Acer kernel.

    We would like it to simply route to the kernels we would need, without having to do a flip-flop the entire time; if it can at least make one file, and route to that, then that would make things a whole lot easier. The guy before me said that was not really possible, and that we would need two servers for two kernels at one time.

    So, my main question is: is there a way to create a kernel file for every computer, and have them route in and out of the server without issue?
    *By the way, the Network logic we have here is that every computer that we image goes back to one FOG server that is located inside of our server room. There is nothing else we use to FOG but that server.

    One last question for grouping: Is there an easy way to just wipe the group kernel; set it to nothing? You can do it individually to all the hosts, but when you have 500 computers to go through at one time it isn’t the most effective way to sit there and remove it from each one.

  • Um, what about trying one of my kernels? I try to include as much as possible. I’m guessing you’re running 0.32? Just use the 32bit kernels and name them the normal bzImage. If they don’t work you should be able to switch back relatively easy.

  • We figured it out; just had to mess with the directory.
    Guy who was here before it made it sound like it was next to impossible to create/manage it like that.