[quote=“JosephJ, post: 357, member: 156”]I just did something similar, but was on FOG .029. I copied the web root Fog server over and installed fog .029 on the new fog server. I then used the MYSQL create Fog database and import commands to bring in the backed up fog database (these instructions can be found in the Restoring Fog from Backup in theFog user guide.). The FOG linux user account should have the same password as the FOG_TFTP_FTP_PASSWORD in the FOG Settings in the Web UI. This is what I found to fix the que problem. Also make sure to put a blank .mntcheck file in the images folder. I then did the upgrade to Fog 0.32. I am testing out the system now, but all seems to be working. Changing the linux Fog user account password should be done with care.[/quote]

Correct. The ‘fog’ users password MUST MATCH ‘FOG_TFTP_FTP_PASSWORD’

To make sure they do:
[LIST=1]
[]Get the value from FOG_TFTP_FTP_PASSWORD
[]SSH into your FOG server as root (google putty)
[]Type: passwd fog
[]Paste in the value from FOG_TFTP_FTP_PASSWORD (right click once on the console screen)
[*]It will say ‘success’
[/LIST]
Be aware you might also need to update the password in Storage Management for that particular node.

Great work on the screenshot, it provides more information than you know!

What does it say directly after the 30second wait?

I assume its trying to negotiate drivers for a particular piece of hardware… maybe firewire? Did you try disabling firewire in BIOS?

You could try updating your Kernel as this is doing the detecting.

Munin is great! Especially for small, simple setups

[quote=“rixter, post: 350, member: 168”]If you are willing to wait a few mins, fog will reboot those pc’s and they will catch on the second boot. I have some newer HP’s that do that, some pickup right away, others take a couple of mins, then reboot, then pickup.[/quote]
Maybe there are some race conditions in your network?

i.e. FOG has to upload the PXE file to the TFTP server via FTP. If your client boots before this has happened, then there will be no PXE file for it to boot.

You are most welcome

That is not exactly what i meant, more for AD OU placement options.

AD doesnt have enough information for FOG to use… things as simple as MAC Address are not held in AD.

Feel free to make multiple posts.

You need to make sure you have a valid gateway. Use ‘route -n’ to look at your routes.
There should be a default route (0.0.0.0) to your gateway IP (What ever that is)

i.e. mine
[code]fog-2:~# route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 bond0
0.0.0.0 10.10.10.10 0.0.0.0 UG 0 0 0 bond0[/code]

I have static IP settings for my FOG servers, you will probably want this too.

Post away!

In my experience, VM’s never make “great” FOG/WDS/Ghost/etc servers due to their shared nature.

Shem, i dont think you understand how FOG works.
FOG will not (out of the box) deploy ISO’s to your machine. FOG is not designed to work this way.
You are going to need some method of installing windows on to the target machine (USB, CD or other).

The error you are receiving “no boot filename received” is because (im assuimg) you are NOT using FOG’s DHCP server.
Read this: [url]http://fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG[/url]

If that is not the case, then i need a better explanation of how your network and FOG box has been setup.

[quote=“The Dealman, post: 370, member: 53”]But i images are sysprepped before they are uploaded so i dont think a chkdsk matters in that scenario…[/quote]
You should be chkdsk’ing before syspreping. Sysprep does not fix filesystem issues, which can cause images to fail.
This is espically true for resizable images.

[quote=“rixter, post: 371, member: 168”]Defragging before you image can reduce your image size drastically as well, when you have ‘unorganized’ data spanning across 10 gigs, but only are using 4 gigs of space, it picks the last place on the disk there is data and creates the image based on that.[/quote]
This is true.

You should be chkdsk’ing and defragging before taking up any image, [B]even if you arent using FOG[/B].

The PHP upgrade for CentOS is brutal. I have no idea why they have not upgraded to 5.3, or even 5.2.

Please see the comments on CentOS 5.6 (at the bottom) on how to manually upgrade PHP to 5.3
[url]http://fogproject.org/wiki/index.php?title=Installation_on_CentOS_5.3[/url]

If this is your first FOG server, i [I]really[/I] recommend Ubuntu. APT’s package management is far superior to YUM’s.
The package maintainers for APT packages are standards nazis; they adhere to a very strict set of standards.

Checking the packages for PHP5 from Ubuntu/Debian shows 5.3.8 is the latest version.

[code]fog-2:~# apt-cache policy php5

php5:
Installed: 5.2.6.dfsg.1-1+lenny4
Candidate: 5.3.8.0-1
Version table:
5.3.8.0-1 0
500 http://ftp.iinet.net.au testing/main Packages
5.2.6.dfsg.1-1+lenny13 0
500 http://security.debian.org lenny/updates/main Packages
*** 5.2.6.dfsg.1-1+lenny4 0
100 /var/lib/dpkg/status
[/code]

You shouldnt need to put the serial in as long as you syspreped the image with the serial.

The activate might be needed, but windows should try automatically.
After mini setup it will enter a 3 day grace period. During this period, it should try to run out to the internet and activate.

I’m not sure about the proxy, i would assume it will activate through your proxy. But knowing M$…

Actually, you are correct about full duplex. I have edited out the misinformation

Maximum through put for 1x 1000BASE-X is listed at 125mb/sec.

A VLAN isnt required, but will help separate traffic/broadcasts/etc

[LIST=1]
[]Mouse over a link for the particular Image
[]Look at the ID in the URL
[/LIST]
Why do you need the Image ID? Host registration? Type ‘?’ and press enter.

Thanks marvin. I’ve used adldap in the past and it works well.

Implementing the code in to FOG is the hard part. After 0.33, the code will be in a more maintainable state and it will be much easier to implement various authentication schemes.

I also want to create a “Active Directory Explorer” that allows you to look through your OU’s by tree structure

I would be using 802.3ad, make sure both network cables are going into the same switch.
Then i would create a VLAN between the switches to keep the traffic separate.

It would be great if you could report any speeds back for comparison.

The error ‘Unable to connect to tftp server’ is 100% related to being unable to connect to the TFTP FTP server and upload the PXE file.
This error will be triggered if it 1) fails to connect to the FTP server, 2) fails to login.

If the backup data has incorrect passwords in it, then there will defiantly be a problem.

I would be updating all of your passwords to make 100% sure…

[quote=“iprt, post: 312, member: 140”]have you got a solution[/quote]
Have you got 5minutes to write a thread worth responding to?

Read this: [url]http://catb.org/~esr/faqs/smart-questions.html[/url]

Then go do some testing and report back some useful information.

The FTP details in your TFTP settings are not correct.

FOG uses the user ‘fog’ to FTP the TFTP PXE files into place. The ‘fog’ users password will be different from your old setup.
[LIST=1]
[]Go to: Web UI > Other Information > FOG Settings
[]Look for: FOG_TFTP_HOST, FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD
[*]Verify these details are correct
[/LIST]

The scheduled task will be in the ‘scheduledTasks’ table.

Look for ‘stIsGroup’ = 1 and ‘stGroupHostID’ = to the Host or Group ID

Latest rows will have the largest ‘stID’