Posts made by MattPayerle

@Wayne-Workman Ok, great tip on that. I am now up to RC-8.

I went ahead and imaged a machine, and then kicked off the normal wipe. It sat at the same screenshot I sent earlier for about 30 minutes, and then shutdown, but I didn’t see any messages, or might have missed them that it was wiped. Regardless, it does wipe the drive because it doesn’t allow it to boot to the hard drive. Perhaps verbosity could be turned on for this? I can use quick wipes for most other things, but it also seems like the full (4 pass) wipe took about 15 minutes long, so I figured this would take about 1/4th the amount of time, but it took nearly twice. So one or the other must be fouled up somewhere. No major rush for me for a fix, but wanted to illuminate a possible bug. Let me know if there is anything else you can think of or need me to test with it, happy to help out where possible.

@Wayne-Workman 1.3.0 RC 5. I tried doing the update to RC 7 but it isn’t pulling properly from git. Do the git pull and installfog.sh and it does the installation, and completes, but the version doesn’t change. Running on Centos 7.

@Wayne-Workman Ok, I let that process sit overnight on a normal wipe and it never did anything. When I did the Full wipe, the process started right away and moved through the blocks, 4 times. It’s on a VM with a fair amount of RAM and CPU and a small drive, so it didn’t take a long time for the full wipe, but the normal wipe never seemed to start at all. Thanks for any insight.

@Wayne-Workman Ok, so then it is just a learning curve then. It didn’t specify that a reboot was built in. So I can stack tasks against a host (once registered) to do a Normal wipe, and then deploy image. The image below shows the checkbox to shutdown, so I wouldn’t need this, I could leave that unchecked because it would reboot automatically as you say, which is awesome.

Also, there might be an issue with Normal wipe. If I use this basic task (under advanced tasks for each host) OR I create an iPXE menu option as you outline here: https://forums.fogproject.org/topic/7407/dban-booting-into-ad

It halts at this:

This works just fine for a full wipe and fast wipe, I can see it do the work as it does 4 passes, or a quick wipe. But for some reason, normal does this. Thanks again, I appreciate it.

@Wayne-Workman Thanks, really great stuff, and I appreciate your dedication to this project!

I prefer to do a wipe of the drive before deployment, perhaps it is just what I have done or what I am comfortable with. The company I work for uses a paid, enterprise level product that has pre-installation task that take care of things such as this. Even if it is just a quick wipe of the drive, and reconfigure the partition table, I feel slightly better about this. It would be neat if we could daisy chain some of these tasks together, because I really like the boot option to wipe, which I just created and am testing, and then will deploy again to the same box, maybe something to look forward to in a future release

Until then, I think this option will work.

On a side note, it looks like I can somewhat schedule some tasks, but only when the host has been registered with the server. That said, when scheduling a task, the first option is “Schedule Shutdown on completion” Anyway to add another option that is “Schedule reboot”? This would allow me to schedule items one after another, with the auto reboots in the middle and it would be somewhat automated. I am testing this currently so I’m hoping that if I schedule a normal wipe, say at 10pm, and then a deploy image task at 10:05pm, even though the wipe might take longer, it will still do the task, but again, I’m testing and not sure what the intended thought is here.

Thanks again for answering and your support towards a really awesome project. Keep up the hard work!

@Wayne-Workman I found this: https://forums.fogproject.org/topic/6696/fog-and-tasks/3 but the solution wasn’t conclusive in my mind. Were you thinking of another thread?

@Wayne-Workman Thanks! Just found this, appreciate the input. Having trouble getting to RC-7 on Centos, the GIT pull runs but then doesn’t change the version number.

I saw this post : https://forums.fogproject.org/topic/909/disk-wipe-then-re-image but its 4 years old, and didn’t want to try and revive it. However, is there a way to do just that? I would love a PXE option that would do a wipe of the drive, then drop the image selected all in one go. Is there an easy build for this as a PXE option?

I just noticed that there is a “Pending Host” link in the Host management side. Once that is ‘approved’ then it joins the host list, and a full inventory can be taken. (I am on v. 1.3.0 RC5)

Hey all, I used FOG several years ago, then just started up again this past week. I have been impressed with the improvements. I imaged a new machine recently and went to the FOG site and installed the client on the test machine. It did not however take an inventory or create a host on the FOG server.

Is that something that used to exist and doesn’t now? Is it something I’m doing wrong, or perhaps a command I can run on the machines to check into the FOG server once the client is installed, create a Host record and then do an inventory pull, rather than doing it all through the PXE boot menu?

Does this work if I create a sysprepped image with the client installed and the services stopped? Any help would be appreciated, just trying to figure out the most efficient method of creating hosts without having to manually touch all of them.