Posts made by Blackout

[quote=“CamC, post: 64, member: 34”]Even if using the “Single Partition (NTFS Only, Resizable)”?[/quote]
Yes

Everyone should be running [B]chkdsk /f[/B] on all of their drives before preping the image.

James, it sounds like you are having permission issues.

First, it was unable to remove the PXE file, now it cannot move image files?

The error that said it was unable to move the file told you WHY it couldn’t move the file. What was the full error message?

To fix this one
[LIST=1]
[]I would power off the uploading machine
[]Cancel the task in FOG
[]Manually move the image
[]Find and fix your system issues
[*]Life goes on
[/LIST]

Hyper-VM is shit and slow unless you have particular Linux kernel modules installed. Just needed to get that out of the way.

Log into your FOG server and look at the image files. Are the image files there? Are they the correct size? They should be 1/2 the size of what is on disk.

I really need a lot more information you want any useful help.

Because those 17 are set to boot to Hard Drive? The other 3 are set to boot from NIC?

I’m guessing the snap-in system is perfect! No changes required! :eek:

You should really be starting with Unicast, then working your way up to Multicast. There are so many variables to Multicast (outside of FOG’s control) that can make it unstable and unpredictable.

Uploading is not apart of multicast, so you have another problem there.

Images should be roughly 1/2 the size. So that sounds too small.

Make sure you are running [B]chkdsk /f c:[/B] before you take images up. Filesystem mishaps will cause image uploads to fail unexpectedly.

The machine will reboot, unless you ticked ‘Shutdown after task’

This is a Windows related issue. Moved thread.

Advanced Format drive support has been added in 0.33.

[url]http://fogproject.org/forum/threads/fog-0-33-whats-coming.18/[/url]

The information is out there.

Great to see you got it sorted.

At the end of the image upload, the image get moved via FTP.

For what ever reason, this failed. There are too many variables and not enough information posted to determine why it failed.

If this does fail, you should see on the uploading computer “unable to move /images/dev/blah to /images/foo”. This will continuously scroll on the screen until it can be moved. Did you see this?

[B]Drive[/B]
Unless you are using E-SATA, using an external hard drive for your images is going to create a massive disk bottleneck.

I dont see the reason for the separation of images. There is no added security or performance gain, so the separation is pointless.

Apart from the reasons above (which should trump this), you cannot have 2 separate image directories.

Easy answer: Spend less money, buy internal drives, set them up in RAID, get better performance.

[B]Network[/B]
I would setup DNS in each network that points the hostname ‘fog’ (or what ever your server is called) to the correct IP Address on each network. i.e. Network 1: fog resolves to 192.168.1.1, Network 2: fog resolves to 192.168.2.1

Then configure your Clients and anything else fog related to use the hostname ‘fog’ instead of an IP Address.

[B]RAID[/B]
As long as the kernel image supports the RAID you will have no issues. You may (probably will) need to download the latest kernel.

Need more information Kevin.

What troubleshooting have you done?

It depends on your hardware and how your BIOS is configured.

Intel have ‘vPro’ which allows you to do what you want. (remotely change boot order)

[url]http://en.wikipedia.org/wiki/Intel_Active_Management_Technology#Using_Intel_AMT[/url]

[quote]Remote boot the PC by remotely redirecting the PC’s boot process, causing it to boot from a different image, such as a network share, bootable CD-ROM or DVD, remediation drive, or other boot device.[1][7] This feature supports remote booting a PC that has a corrupted or missing OS.[/quote]

I think this is what you want:
[LIST]
[]PXE boot to capone
[]capone displays a list of images
[]You pick an image
[]FOG images your machine
[/LIST]
Short answer: Out of the box, No
Long answer: Anything is possible if you have enough time

The FOG service can set IP Address and join your machines to your domain.

I would be using this over bat files.

I would recommend a Cisco or HP. They are both standards compliant.
I know that there are Classes / scripts out there to interface with these routers easily.

Please list any problems or feature requests for the snap-in system.

If you have any suggestions, they are more than welcome.

Be short and to the point, list form is more than acceptable.

Layer 3 managed switch

Something that is standards compliant.

You will want the ability to check the devices port status and MAC address via telnet/ssh/webpage.

You will then need to write a script that checks the status, gets the MAC address and then creates the required PXE files.

Here is the wireshark wiki page on WOL.

[url]http://wiki.wireshark.org/WakeOnLAN[/url]

That is what you are looking for. You want to verify the WOL packet is getting to your client.

The log reports HTTP 200, so the page GET was successful and the PHP page was processed. Did the WOL event work?

If not, what happens if you manually go to below, does it work?
[url]http://172.17.14.206/fog/wol/wol.php?wakeonlan=f0f1:9e:d9:10[/url]

It looks like its working as intended. There should be zero difference between you manually requesting that page and FOG requesting (its basically the same thing)

This sounds like some sort of configuration issue.

The next step would to tcpdump and see what the traffic is doing.
You will need to dump from your server and from your client to get a full picture of what is going on.
You want to check if the client is receiving the WOL Magic packet or not.
It should be a broadcast UDP packet to port 7 or 9 with a total of 102 bytes. 6 bytes of nulls, followed by the clients MAC address 16 times.