Posts made by SuP3R_Ch1cKeN

Is there anyway to password protect this option. Might be kinda dangerous to leave this unprotected in my live environment

I feel like an idiot now… That was it.

I did put a copy of dban in /var/www/html/fog/service/ipxe/dban however I modified the code to ${boot_url}/service/ipxe/dban/dban.bzi

Also I attempted to do echo ${boot_url} just to see what the variable pulls up and it was blank in the echo.

I also tried [CODE]kernel http://172.16.8.92/fog/service/ipxe/dban/dban.bzi nuke=“dwipe” silent vga=785[/CODE] but that flashed a no such file or directory but when I put [url]http://172.16.8.92/fog/service/ipxe/dban[/url] in a browser I can see all the files in that folder.

Now when I attempt to add what madskillz23 suggests I get the screenshot that has [url]http://172.16.8.92/fog/service/ipxe/bg.png… ok[/url] then it goes back to the ipxe menu.

The other screenshot is if I put just echo hello world in the advanced config option.

[url=“/_imported_xf_attachments/1/1095_Screenshot_2014-06-30-15-20-18.png?:”]Screenshot_2014-06-30-15-20-18.png[/url][url=“/_imported_xf_attachments/1/1096_Screenshot_2014-06-30-15-20-42.png?:”]Screenshot_2014-06-30-15-20-42.png[/url]

This was in 0.32 however it was there for so long that I couldn’t tell you if it was customized in or if it came preloaded.

I was wondering it this could possibly be added in the PXE advanced configuration.

in the PXE menu there was the following option which you could just select and it preformed the wipe. It was helpful incase you needed to wipe many HDs at once.

LABEL fog.wipe
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mac= web=172.16.9.13/fog/ osid=1 wipemode=full mode=wipe shutdown= loglevel=4 consoleblank=0 fdrive=

Is there a way to remotely wipe a HD without actually registering the host? I know this was an option pre 1.0.0 but I cannot find it post 1.0.0.

1. You will most likely have issues unless you’ve done an install before however if you search the forums you should find posts related to your issues.
   a. I think a fresh install is always better then an upgrade but that’s really a preference thing
   b. Yes (kinda)… FOG 1.0.0+ uses PartClone and below 1.0.0 uses PartImage. Now with 1.0.0+ you can still deploy PartImage files however when you reupload the image it will be a PartClone file. It’s kind of a process to migrate all your images to PartClone images if you have a lot but it’s not really hard either. Tom’s post in this thread can help with this ([url]http://fogproject.org/forum/threads/partimage-aborts.10275/#post-24893[/url])

2. and 3) I have no idea on this issue.

FOG works great for real machines. I’m attempting to create a VM image using HyperV. When it PXE boots it gives the following error:

Could not configure console: No such file or directory
Could not boot: No such file or directory
Could not boot: No
[ATTACH]961[/ATTACH]

Then it goes to the VHD

[url=“/_imported_xf_attachments/0/961_Capture.PNG?:”]Capture.PNG[/url]

Can you send a screenshot of what you see

Stolen from Tom’s post on another forum:

VM’s have known “slowness” issues on upload compared to physical systems typically, but as Junkhacker states, the compression affects upload speeds as well. In 0.32 there was no “easy” way to adjust the compression rating, but with 1.X.X, you can specify this in FOG Configuration->FOG Settings->FOG Boot Settings->FOG_PIGZ_COMP slider bar. 9 means MAX compression which basically means it will be the slowest to upload, but compress to the smallest size. 0 means least compression but takes up the most space on the server. You can play with these settings to see if it will help you out.

[url]http://fogproject.org/forum/threads/ipxe-issue.10528/page-2#post-28344[/url]

That usually means the kernel doesn’t have the correct driver for the machine you are trying to image. You can try to update your kernel to a newer one or an unofficial one by going to FOG Configuration > Kernel Update. There is a drop down box to change to unofficial.

You can hide the tray icon before you upload the image and delete the all programs folder. The Fog service will still run and you get the benefits from it however the local user won’t see it.

It could be helpful if you could set a lock on specific hosts individually or via a group. This lock would prevent any changes made to the host definition even if selected to be deleted or modified. Just a thought to prevent accidents which a few times I’ve had to correct. Going around to 50+ computers to reregister them in a call center can be kind of annoying.

I also followed the wiki installation instructions Step-by-Step. FTP was missing from my install and SeLinux didn’t actually disable. I would verify the /etc/selinux/config has SELINUX=disable.

I’ve had this issues a few times randomly. I used a program called fixparts to repair the HD. [url]http://www.rodsbooks.com/fixparts/[/url]. I have it on a LiveCD which in a terminal you type:

[CODE]fixparts /dev/sda[/CODE]

Use option “w” and confirm. Restart and attempt to image again.

You can just verify that the image is genuine before you upload (Press windows key + pause/break then scroll all the way down). You should have an OEM license if it comes preloaded and you use the same OS. We do that for every image my company uses.

A common problem I see people having when moving to 1.0.1 from an earlier version is the username no longer needs the domain prefix. Try checking your AD settings for the host and verify that it shows just the username and domain in the respective fields.

Stole this from Tom’s post in another thread:

The Services that fail to start, when it happens go to [URL=‘http://%3cfog.ip.addy%3e/fog/management’]http://<FOG.IP.ADDY>/fog/management[/URL]
Perform the schema update/install process.

Then reperform the install. It will not hurt anything and should complete successfully.

[url]http://fogproject.org/forum/posts/28323/[/url]