that move is done via ftp. make sure that the “fog” user has rights to the files and the directories and that you can log into ftp from another console using the fog username and the password specified in the fog settings.

Are you managing labs/desktop computers or 1-to-1 devices like laptops and tablets?

MPSD images are still compressed when stored on the FOG server. I have NEVER had luck with resizable and most times I have tried it (on FOG 0.32 at least) it has hosed my image up with a problem during the resize and I had to start all over. A windows machine that takes 40GB on a disk will probably take about 15GB after it’s compressed into the /images folder.

After searching through the interface for the EA6400, it doesn’t appear to support PXE boot options. Just use DNSMasq as Jaymes advised. It will let your Linksys router serve DHCP, and just respond with PXE Boot information to those clients that request it, such as next server name and boot file name, no IP info.

And I’d be willing to do a teamviewer type session to look at your setup sometime.

Oh yeah, I see that now. I forgot how to scroll

Could this be an ajax type problem on the client side rather than an error on the server side?

What browser and version are you using (Chrome, Sarfari, Firefox, IE, Opera, etc)?

Choose the system information option from the FOG menu, then check system compatibility. Make sure both network and HDD pass.

Are you deploying the image to a VM on your workstation? I’m a bit confused about your setup.

Yeah. I’m confused. Are you getting these errors when FOG tries to load the bzImage/Init or after the imaging process completes and Windows is trying to boot?

Are you using audit mode to customize your image, then sysprep /generalize , etc before you take the image for FOG?

I’m guessing this is due to DRM changes Steam may have made so you can’t purchase content and then copy it to a bunch of other machines.

What device is serving DHCP for this network segment?

check your apache log to see if you are getting a php error. turn on your developer tools in your browser to see if you are getting a javascript/ajax type error also.

I have a recent post about sysprepping windows 7/8 that includes a download of my setupcomplete.cmd and unattend.xml files. I also include links to the main articles that helped me create the files so I know which options to set to avoid the welcome screen or anything that might cause the installed to pause and ask a question.

You’ll need Windows AIK and the install files for your version of windows so you can pull out the catalog file.

[url]http://fogproject.org/forum/threads/many-will-want-to-rollout-win-8-1-on-new-hardware-well-before-the-expiry-of-xp-in-april-2014.9871/#post-20988[/url]

Eddieduce, please start a new thread and post your relevant setup information such as FOG version, OS version, how many FOG servers you’re setting up and what type of installation you performed (normal or storage node).

I deploy Windows 7 and Windows 8/8.1 in much the same manner. The main difference is in the unattend.xml file. Slightly different options for each OS version. Also, our Windows 8/8.1 clients use ADBA instead of KMS, so I do not try to activate them as part of the setupcomplete.cmd script.

I do not image Windows XP anymore since it is going out of support soon. The basic walkthrough is the same with modifications for the OS version.

Microsoft sysprep videos are really geared towards OEM types that are deploying windows to end-user consumers and those consumers will need to go through the OOBE to name their computers and create accounts, etc.

In the FOG community, we generally deploy computers and want them to auto-name, auto-join domains, and basically be as ready to log into as possible. We don’t want the welcome to windows, pick a computer name, choose your background color crap… I don’t at least. My systems are all frozen before the first end user sees them, so they need to be ready to hit ctrl-alt-del and login and nothing else.

Using the FOG server, the unattend.xml file, and the setupcomplete.cmd file, I can bypass the welcome screen, have local user accounts auto created, rename and join the computer to the domain, activate windows and office, and present a login screen ready to go.

Ricardo, check your PM’s for login info.

The hardest part about sysprep is getting your unattend.xml file prepared and learning some of the finer points of using sysprep with the FOG client and Windows/Office activation.

If you are getting those errors it’s probably your kernel. You can swap out kernels using the Other Information -> Kernel Updates page or by downloading and replacing your bzImage in your /tftpboot/fog/kernel folder. Tom has some kernels available on his site also.