Be sure to run the below command from Command Promt before sysprepping/uploading (requires a reboot)

chkdsk /f

I want to try and help you out but don’t fully understand your question. You talk about login time and then about imaging. I don’t understand why you would need to turn off pxe booting. If these are two separate questions here is my solution.
[B]Wireless login time:[/B]
I’m not sure what kind of wireless solution you are using but you will need a high quality access point(commercial/enterprise) to handle that many connections. Otherwise you would need multiple access points in the same location. Other than that I can’t think of any ways to modify the login process.
[B]Strategies for imaging:[/B]
Laptops would obviously need to be imaged through a wire. Most laptops don’t need set for pxe booting. If they receive a wake on lan signal they automatically try to boot from the network. If yours don’t then could simply hit f12 or whatever your network boot shortcut key is. Finally if you do set it to boot from the network first, then the hard drive, after you have imaged the laptops they are no longer connected to a physical wire, therefore, PXE booting will see it has no connection and just skip to the next device which is your hard drive. So basically I’m saying there is no reason to turn pxe booting on and off.

When you upload an image to the server it compresses the file, so it’s not raw. This is why the image size is smaller on the server.

When you download the file it should go much faster due to it needing to extract the file, and not needing to use the CPU cycles to compress it.

Your images are rather large in comparison to most images I work with 3-6 GB.

Does it go faster when pulling an image down from the server?

In the Fog UI select other information, then kernel updates. You can try both older and newer kernels.

I may be wrong here, I haven’t worked with Fog in a while and may not be familiar with any new features, but here goes.

If you don’t specify a computer name in your answer file windows will always stop and ask you for a name. If you put a * in for the name, one will automatically be generated by windows and you will not be asked for a name. When the computer reboots, the fog service will kick in and automatically rename the computer to whatever it is in your database.

Your quick reg should be set to 0 unless you are actually using quick registration. Ex, you have 10 new computers but don’t want to give them all names manually. Quickreg will automatically do this for you, but as far as i know it has anything to do with sysprep.

Is your computer name really set to PC-*. If it is that’s not right. The start should be replaced with a number if quick reg worked correctly.

Early name changer - I have not worked with this yet. As far as I know it has to do only with registry and not sysprep. Maybe you have this setting on and the pc’s registry is updated to the name in your database, then sysprep is just getting the name from that.

In summary, turn off quick reg, turn off name change early, and change your answer file computer name to a * You should be fine then.

[quote=“Sk00t3r, post: 1774, member: 430”]First thing I would check is the Network your behind. Do you have 10/100/1000 nics in all the machines (fog and client)? are you behind a router, hub or switch? Uploading I get about 3GiB/min and download is about 4.6 GiB/min[/quote]
client PC is GiB & the FOG server is 100MiB. I am behind an HP network switch 100Mib. My download speed is 273.39 MiB???

Sk00t3r,

I appreciate you taking your time to help me after making sure all my passwords were correct I started looking through my notes. I found one file that i had documented that I had messed with. This file was /etc/mysql/my.cnf. For some reason when i switched my bind address i must have not hit save when i updated my ip address. Once again thank you for you time.

Sorry for the double post I’m not sure what happened.

looks good, articles/tutorials should be posted here [URL=‘http://fogproject.org/forum/forums/tutorials.13/’]http://fogproject.org/forum/forums/tutorials.13/ ;)[/URL]

Its ok now. I’ve nuked the whole server, and started again. I found i was having other problems so it was just easier to start again. thanks for the help. 🙂

This issue has been resolved.

Thank you! I didn’t find this!

Looks like this was posted earlier [url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]

I’m having a similar problem, snapins that deploy and finish fine on windows XP are, well some install but then the task just stays there, and others don’t even deploy. But if I run the SFX manually it works fine. Hmm…

[quote=“andjjru, post: 1598, member: 575”]Pete,

Multicast is only available on the Task Management page. It will show up as an option on groups when you search for them.[/quote]

Cheers for that Andjjru - Yup, I found it this morning when I came into work! You’ve just confimed that I’m doing it correctly.

Many thanks!

-Pete