Is your fog server on the same network as your workstations to be imaged? I got confused when you responded with the bandwidth of your Internet service. He was asking for your network. The internal network and the devices that run it. Like a router, switch or hub(has nothing to do with the internet service).

Ask your system admin if you have a 10MB network, a 100MB network, a 1GB network or a 10GB network.
That should give us the info to help answer your question.

I have the same model, Vostro 3460, and see the same issue. Did you ever get it resolved?

I recall I had the same problem with an earlier Acer product, however, I upgraded to 3.3.3 kernel, and it worked fine. If I knew which “switch” needed to be done on the kernel, I may be able to compile it.

OK, mess up on my part. I reread Art’s post. It appears to be working now.

Thank You.

[quote=“dahhunter, post: 10887, member: 3244”]Im in the same boat as zbarnes…

any one have any suggestions.[/quote]
solution for me was to use multiple partition single disk image. ssd’s have a hidden partition.

Thanks for your reply. The problem appears during unicast.
But It wasn’t a switch problem but a problem with the client Broadcom NIC driver in the kernel. I compiled a new kernel with a different NIC driver and everything works now.

Well I uploaded and re-imaged first a HP t5710 thin client which has 512MB flash drive. It took 106 sec to upload the image and 204 secs to download the image to it. I was at first a little disappointed with the rates until I thought about the performance of the T5710 flash drive itself.

Next I uploaded an image from the wife’s desktop 640MB drive running Vista of which she is using about 225MB. The image upload speed with the Pogoplug/WD Elements system yielded a average transfer rate of 941 MiB/min or about 15.68 MiB/sec; so it took about 4 hours to upload the image.

After I ran these tests, I remembered that one of the switches between the Fog server and these two system is only 100M not gigabit so there maybe even better performance when using all gigabit network end to end.

This may not be a screaming eagle, but it is not bad either, for a minimal Pogoplug/USB drive system; which costs $112 (Drive=$89, USB Stick $8 and Pogoplug $15) I have a 2TB Fog server which consumes low power. I am a happy camper!!! Thank you folks for your wonderful work!!!

We have no problem with 3.6.9 and imaging the 7010’s.

The kernel published in my previous post does not work for me. I may be doing something wrong, but it did not work on three different computers I tried to PXE boot.

I found this driver that is not upstream yet but this is for the Qualcom/Atheros ALX series.

[url]http://www.orbit-lab.org/kernel/compat-wireless-3-stable/[/url]

It appears that this is for the 3.6.x series kernel. I’m going to download this kernel and compile it with the latest driver listed on the link above.

Wish me luck…

EDIT: well crap, I have to look up how to compile this module into the new kernel. More later…
I also did find that, under ubuntu, there is the “wireless-compat” package(s) which may contain alx drivers.

[quote=“yogipaolo, post: 10395, member: 61”]Another reason why I love this community. I might be using a slightly different gigabyte mobo than you, but your board is likely to have a qualcom/atheros ar8161/8165 chip in it. This chip apparently is bluttooth as well as lan.

A kind soul has posted this link with a direct link to a bzimage download:
[url]http://fogproject.org/forum/threads/dell-2330-all-in-one-network-issue.1054/#post-8470[/url]

I’m going to try this.

I’m also busily compililng a 3.7.5 kernel for the hell of it. I’m going to see if I can use it as an alternative kernel. FOG has the ability to boot specific kernels for specific hosts (I think). This is configurable under host management >> host kernel[/quote]

Unless you’re in a very demanding environment I feel like it would be wasted. If it’s just a matter of load balancing then I’d suggest setting up storage nodes. There are very few circumstances in which I would expect 10Gb to be the only option.

In the follow scenario your bottleneck is probably the HDD:
[COLOR=#999999]HDD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Swtich[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#999999]HDD[/COLOR]

In the follow scenario your bottleneck is probably the 1Gb:
[COLOR=#800080]SSD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Swtich[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#800080]SSD[/COLOR]

In the follow scenario your bottleneck is probably still the 1Gb:
[COLOR=#800080]SSD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#0000ff]–10Gb–[/COLOR] [B]Swtich[/B] [COLOR=#339966]–1Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#800080]SSD[/COLOR]

In the follow scenario your bottleneck is probably the SSD, although you might have reached the 6Gb limit for SATA3:
[COLOR=#800080]SSD[/COLOR] [COLOR=#ff0000]–SATA3–[/COLOR] [B]Server[/B] [COLOR=#0000ff]–10Gb–[/COLOR] [B]Swtich[/B] [COLOR=#0000ff]–10Gb–[/COLOR] [B]Client[/B] [COLOR=#ff0000]–SATA3–[/COLOR] [COLOR=#800080]SSD[/COLOR]

Without upgrading the network connections all the way to the client, the only performance increase you would see from using 10Gb on the server side is from concurrent imaging tasks, which you could easily get by using storage nodes to load balance the tasks.

Hello Jian and Chad,

I am again facing one problem in [B]Think Station S30[/B] machine.
Below is the scenario…

SATA0–> 500gb HDD --> Total 2 Partitions ([COLOR=#ff0000]1st Partition Windows XP[/COLOR] and [COLOR=#0000ff]2nd Partition Windows 7[/COLOR])
SATA1–> 1TB HDD-- Blank Disk

Now I Uploaded the image by selecting [COLOR=#800080][B]Multiple Partition - All Disks. [/B][COLOR=#141414] Image uploaded successfully.[/COLOR][/COLOR]
[COLOR=#800080][COLOR=#141414]Now when I deployed the image on same model machine, below is the scenario.[/COLOR][/COLOR]

SATA0–> 500gb HDD --> Blank Disk
SATA1–> 1TB HDD-- Total 2 Partitions (1st Partition Windows XP and 2nd Partition Windows 7)

Not getting why fog had swapped the hard disk while deploying the image.
I don’t know weather the problem is with Machine or the options I am selecting.
Can anyone please help me.
I have a stock of 200 machines pending due to this issue.

Thanks,

Ok, here are some additional hints, how I proceeded:

First of all, make an (local) image of the whole disk - i.e. with CloneZilla - so that you can recover the original partitions every time. This image takes about 18 GB.

After that install Windows 7 as provided.

In “Computer Management” -> “Disk Management” delete Partition “HP_RECOVERY”

Reboot the Computer

Now you need to delete the small recovery partition (101 MB). It’s not possible with “Disk Management”, so

open a “Command Prompt” window ( -> Start -> Accessories), you need to run it as administrator.
Here you can enter the command “diskpart” (see “diskpart> help” for options) to localize the partition you want to delete. Normally it’s disk “0”, so you have to “select disk 0”. Subsequently enter “list partition” for the selected disk and for HP8300 you will see Partition 3 (Recovery) to delete.

Now “Select partition 3”

Deleting by “delete partition” will not work as long as you don’t use: “[COLOR=#339966]delete partition override[/COLOR]”.
[COLOR=#ff0000]BUT BE CAREFUL and INSURE FIRST TO HAVE A BACKUP.[/COLOR]

Check with “list partition” and enter “exit”

Reboot your system and check whether it works and you deleted the proper partition.

After your HP8300 started Windows 7 normally you should be able to upload your image in a way to deploy it later and in FOG you can even select “Single Partition (NTFS Only, Resizable)” now.

Hope this helps.
Greetings from Bonn, Germany.

Try a USB ethernet connection?

You will need to sysprep. I recommend building a single machine as you want it, uploading that machine’s image to FOG (which will be specific to that machine) i.e. “Machine_A_PreSysprep”, keeping that image in case you need to rehash the sysprep, as from my experience, once a machine is sysprepped, it cannot be sysprepped again (unless of course you erase the sysprepped HDD redeploying the pre-sysprepped image) After sysprepping a PC you like, upload image without reloading into Windows.

Here are some files which may help you, including some answer files with more or less everything stripped out just to get you started. One thing I can recommend regarding the answer files is to use WAIK for Windows 7 (WAIK4W7). I believe you can find it from Microsoft for free as a download.

[url=“/_imported_xf_attachments/0/210_ImagePrep.zip?:”]ImagePrep.zip[/url]

I don’t have any USB dongles for my XPS 13 to test with, but this Dell support pages seems to suggest the BIOS only supports some USB adapters. Perhaps you could manually download the image via linux usb stick over wifi?

[CODE]The XPS 13 with BIOS A05 or higher, supports PXE boot with LAN7500 chipset based USB NICs.[/CODE]
[URL=‘http://en.community.dell.com/techcenter/b/techcenter/archive/2012/07/25/dell-xps-driver-cabs-are-now-available.aspx’]http://en.community.dell.com/techcenter/b/techcenter/archive/2012/07/25/dell-xps-driver-cabs-are-now-available.aspx [/URL]

I believe the part you need on your image is OMCI, which allows WMI access to Dell BIOS level functions.

[CODE]http://search.dell.com/results.aspx?s=biz&c=us&l=en&cs=555&k=OMCI&cat=sup[/CODE]

I have only seen this when there is MAC address filtration active on the network; if you have not added the MAC addresses to the “approved/allowed” list then they will not be given IP addresses and this is the message that you get.

Are you sure that the machines are in fact communicating with the network (DHCP server) correctly? You could test this by just loading into a vanilla Windows installation from DVD (or Linux Live CD) and see if you have an IP address and can get on the network; if you cannot do this then FOG is not the problem.

I seem to remember imaging E6520’s no problem… but perhaps the network adapter is different.