please verify that the fog server is installed on the client computer AND IS RUNNING (check services.msc), and has the correct IP address of the fog server listed in the config.ini file (found under the program files / fog folder).
If you have both running please attach and your fog.log file into your response so we can see what is going on for you. 
thanks!
Andyroo54 would you be kind enough to go back to the original post in the thread and add the DP_Install_Tool.txt to the first entry? This will keep the thread uniform and simple to manage.
Also… if you could please upload an example of your .xml answer file for the community. Just a thought
p.s. i’m working on a tutorial for XP as well for all those legacy users holding out
–ssx–
I can report that if you download the fog VM and use JUST a 5 port switch and designate the fog server for DHCP you can use it as a stand alone imaging solution. Not ideal, but it does work.
Simply upload an image to the mobile unit and turn it loose on the remote locations.
I have VMware Workstation 6.X and I’m able to upload an image just fine using Fog. What version of Workstation are you running?
You updated all 3 lines of the apache config correct? Did you then restart the service / reboot the server after you saved the changes?
You could also use an FTP client to update your files. Use the “pxe boot .iso” guide in the tutorials forum and log into the server using an FTP client and update / transfer the files this way if you are not comfortable with doing it as kevin mentioned.
One last thing to note is that if you plan on deploying server 2003 to different hardware look out for issues with a hardware extraction layer or “HAL” - Server 2003 must adhere to the same imaging rules as Windows XP. - [url]http://support.microsoft.com/kb/309283[/url]
If you image multiple pieces of equipment that don’t have the same server hardware internally you will need to plan for, and work around some bumps.
google around for a good server 2003 imaging guide before you write your sysprep.inf and upload an image. I know MSFN has a guide or 2 out there.
Great guide variable!
One last thing I wanted to point out here to the public is that if you have a computer that won’t support the booting of flash keys you can also use etherboot on a floppy drive or cd rom - [URL=‘http://etherboot.org/wiki/removable’]http://etherboot.org/wiki/removable or Rom-o-Matic which has pre-built builds depending on your NIC - http://rom-o-matic.net/[/URL]
The way fog works with the kernels is that it tries to load as many drivers as possible when booting (so it covers and supports the most hardware). If you wanted to speed up the boot time / load time you could use the kernel argument section to remove the non-operational portion of things (Acer HDF / etc.). I’m not an expert at kernel arguments, but I know this has worked for other users in the past.
–ssx–
[quote=“Josh B, post: 2480, member: 804”]Hello all,
I apologize if this is in the wrong area. This 1 made the most sense 
I have a fog server set up with 0.32 on a make shift PXE network for testing purposes. So far there is a PXE server, a dumb switch and Fog.
I am confused on how to get the 1st image to the Fog server. I built an image of Windows Server 2003 Standard Edition x86 using nlite [never can get the updates to install correctly], installed on a server, fully updated and installed with all of the desired programs; a fully functional image on a server provisioned as it should be for a client. How do I get that to Fog for deployment?[/quote]
You are wanting to upload the image to the fog server. To do so please see below.
#1. You need to register the server / pc you want to upload the image on (the client machine).
PXE boot the computer and do a quick registration
#2. Go into the Web UI and create a new image / name it / set the image type / save it
#3. Go to the clients page of the web UI and designate the computer to the new image name you created. Once this is saved select UPLOAD and send the image from the client to the server.
Lay-men terms you need to register, create an image, assign an image, and upload an image.
This is all in the documentation btw
[quote=“Josh B, post: 2480, member: 804”]
I assume after I get the image on Fog I can PXE the new server [to be installed] to Fog and push the image from the web UI. If I’m wrong on that I can bring that up later if the User Guide doesn’t show me the light.[/quote]
Correct
[quote=“Josh B, post: 2480, member: 804”]
The eventual setup will be a PXE server, a real switch, Fog and an image server for Linux. I believe that Fog can also handle the Linux stuff but our Linux Admins like to do it their way. I’m not sure how all of this will work on the network side for PXE and such but that’s above my pay grade :)[/quote]
Depending on how your network is set up (Vlan’s / layer 2 or 3 / etc.) you may run into issues. Some networks that are not on vlan’s or have other servers running PXE services (voip phones for example) run into problems with fog.
As long as you have a vlan structure you should be fine. There are also work arounds for voip phones and other pxe based services, feel free to ask or check the KB’s.
[quote=“Josh B, post: 2480, member: 804”]
The Fog server will be used to deploy Windows 2003 and Windows 2008 to up to 800 or so servers eventually. Any suggestions on hardware for the production Fog server? Thank for the help in advance.[/quote]
Depending on how much $$$ you are wanting to spend on a setup, I’ve seen very good results running Vmware ESXi server on a raid array with NIC teaming. Raid is almost a necessity, and the more network backbone you have the better. I’ve seen really good transfer speeds in the 4+ Gig/min speeds on some setups, but YMMV.
I also suggest you keep your image size as slim as possible, especially if you are doing multi-casting.
Feel free to ask us any other questions.
thx.[/quote]
To confirm, the machines still do image after the wait correct? do you happen to know what kernel you are running?
Other users seem to be having similar issues as well. Check itninja.com - [url]http://www.itninja.com/question/java-tm-update-fails-to-apply-changes-to-your-system-error-1722[/url]
Did you double check and make sure your default storage group password is also set properly?
As Brycez mentioned turn the sata controller off of ACHI and set it to legacy or SATA
It’s a reported issue for this model. You can also check the forums to see other workarounds using the PXE boot menu if you want.
I don’t know if they have plans to integrate those drivers into the bzimage, but you could roll your own - [url]http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]
It has to do with UAC I believe. It’s a known issue with the current release.
I’m going to see if we can’t get this thread moved to the Dev forum and have them be reminded of this issue now that the old forums are gone.
did you disable the windows firewall using group policy? Is the firewall service stopped?
Double check to make sure —> gpedit.msc —> Computer Configuration —> Windows Settings —> Security Settings —> Windows Firewall and Advanced Security —> Windows Firewall Properties (1/2 way down the page). Verify that Domain / Private / Public profiles are all set to disabled.
Then go to services.msc and stop / veriy that the windows firewall is also set to disabled / manual.
We ran into this issue on our end with windows 7, and even though we had the firewall off and disabled via group policy our Windows update server kept turning it on when a service update / service pack was sent out (SP1 for win 7). Big pain in the @#$@#$ .
Hope this helps.
I’m going to suggest that this get moved to the dev forums. I don’t have an answer but they should be able to help.
thanks!