Posts made by djm79

Well since your using a flat network you could try this [URL=‘http://fogproject.org/forum/threads/requested-multi-site-location-patch-requested.410/’]multi site patch[/URL]. Lee is the man on this but the downside is you have to .031 for it to work as there are changes to the coding on .032 that keep this from working. So long story short you create locations and tie them to FOG servers with each computer then add the secondary FOG servers to the main FOG server as part of the default storage group and use DHCP to control which FOG server the computers boot from and the location make the computer pull from that machine.

Then you can setup the replication to happen in off hours or throttle it so that the link between the two sites isn’t overloaded. Look this over and hit me up or ask Lee since he made the patch and hes really nice and walked me through getting it hammered out.

Yes with the help of Lee and his Multi site setup I have my 26 branches running off FOG and deploying software to all of them with snapins.

I have mine running in VMware and it runs great. As for VZ/Proxmox i have not tried this virtual software.

If you chain load them it should clear up the boot loop. I have a batch of dells that would boot loop on me till I just chain loaded all my FOG computers and now no problems.

Yea thats why you need to look in the folder that you used to install fog and there will be a fogcrypt run this on a windows machine from the command prompt and it will output the password encrypted and then input that in your fog settings and test joining.

Is the password FogCrypted? What does the log say when it tries to join to the domain?

Well if you already have a device doing DHCP you could cause a “race” situation were they are both trying to hand out address. The proxy DHCP setup would allow FOG to hand out the PXE boot options to computers without messing with the DHCP device that is doing it now. Does someone else manage the device handing out addresses? If so ask they to add the boot options to the DHCP scope. IF not then proxy is the way to go.

What does the Fog log say? It should be in the root of C:\

I would check the settings in the configuration page and make sure your using domain\username. That one got me and machines were failing to join until I change it.

You don’t have to add them to your FOG server, you add them to your DHCP options so your machines know where to look to PXE boot from and the file to use. Or you can do the proxydhcp option that chad-bsid said. This is the link for setting up a proxydhcp [url]http://www.fogproject.org/wiki/index.php/Setting_up_ProxyDHCP[/url]

I would say its a kernel driver issue. I would try different kernels. It easy to change through the GUI, other information tab at the top and then kernel updates give you a long list to pick from. If one of those doesn’t work I might be able to link a download to a all in one kernel that works great for me.

Ubuntu 10.10 desktop 64bit 8 gigs of ram and bonded 1 gig nics in a VmWare environment. Managing our three building main campus and 26 branch locations. Storage nodes at each location that provide PXE boot and Samba share for snapins. It’s a complete hands off setup. Our helpdesk can image and deploy software to any computer without having to go to the location. All thanks to the FOG team here this is the best solution with great support.

Have you tried Ubuntu 10.10 or less because I have seen post of people saying they had issues but not sure if it was imaging. So one image uploads fine but the other two crap out at different points but never fully upload? Have you thought of trying a different kernel for the PXE upload and download part?

Are you imaging from the same access layer switch all the time or are you moving between two different switches? I only ask because a had a very similar problem with one of our Cisco POE switches. I would take the laptop and move around and check the switches move outward from the FOG server until you get back to your access switch where you are having the slow imaging. Mine was a cheaply done uplink into a a 10/100 port instead of a gig uplink. Try that out and let us know how it goes.

When I update my images I just deploy them and make the changes (IE updates, add or remove software) then just upload it over the old one and your ready to go.

What device is 10.0.0.2? I would think it was your router as its your default gateway too. You need to configure the DHCP scope with the boot server IP and the pxelinux.0 file to get them to PXE boot.

This is a change from 0.31 to 0.32 you have to use 0.31 for this patch to work. It work great on a 0.31 system for me along with some other modifications we can image machines all on the remote network with very little WAN traffic.

Well First you need to figure out what is giving out DHCP addresses on your network. Unless you configured FOG to handle DHCP it more than likely is not doing it. Go to the command line on one of the computers and do an ipconfig /all and look for the DHCP server line and it should tell you the IP address of your DHCP server. Once you have that its part of the DHCP config that hands our the boot server IP and the pxelinux.0 file on boot.

Did you set the options for all the DHCP scopes? Because if they are not all the same some computers won’t know anything about the PXE server. Also with 5 switches are you forwarding DHCP request? Is your network flat or do you have Vlans that separate the network? Sorry just trying to get a handle on how your network is configured.

Do you have another device that is a DHCP server? This could be a computer, router/firewall just depends on how your network is set up.