what if you try
[B]zwsreg -unreg[/B]
then
[B]zwsreg[/B]
then log out and back in

does that fix it for you? That should re-register your computer object to your Novell server.

Which error number do you receive when the TFTP portion times out? Also, what did you specify in 66 and 67 of your DHCP server?

Using FOG’s DHCP server is useful for when FOG is on an isolated network and you want to image PC’s. I would not recommend it at all for a live production network. You can use an existing DHCP server, either your router (if on a home network), Windows Server 2003/8/12, or a Linux server.

With Windows, you need to specify options 66 and 67 in your scope. I’m going from memory, but 66 is the IP of your FOG server, and 67 needs to be pxelinux.0

For Linux you just need to specify FOG in your DHCPD.conf file with [B]next-server x.x.x.x.[/B]

try this [B]sudo service tftpd-hpa restart[/B]

What OS do you have your FOG server built on?

I know FOG supports Linux images, however, you have to upload the image by using the Raw image option (not sure about the multipartition option), and if my memory recalls, FOG only supports Ext2/3.

If you delete the Hibernation file, you just can’t put your computer into hibernate mode. No big deal. However, the page file is a MUCH different story. This is what the hard drive uses if you run out of RAM when multitasking. Very bad things will happen if you remove this from a computer without having a ton of RAM. Personally, I have 16 GB of RAM in my personal computer, and I still keep a small pagefile available just to be on the safe side. All it takes a memory leak, say from Flash or Java (since they’ve never had those before ) and you’ll blue screen in no time.

Sorry, was a typo

Have you tried a Kitchen Sink kernel? If you compile your own kernel you should be able to add your own drivers as well.

3.6.9 is the latest “official” kernel for FOG

I had this working within a test environment. It would boot to our DeployStudio server and it would work like normal. We couldn’t roll this out to production since our network admin didn’t like the thought of modifying the main DHCP table for this. Oh well, not my call, but worked well when testing.

I was never able to have this work on these machines either. However, I no longer have one in my possession, so I can’t test it anymore.

Does FOG stop here? All of our computers show this error but it doesn’t stop the functionality of the software.

Did you register a PC to FOG first? This can be done from the PXE menu, or from the web interface. This will need to be done so you can assign the image to the specific host.

If you get TFTP problems on Ubuntu, you just need to restart the service, and everything should start working again [B]sudo service tftpd-hap restart[/B]

FOG does not like an IP change as you noted. What about running FOG in a VM? Virtualbox works well, and is free. Personally I use VMware Workstation since it integrates into my ESXi Servers, but a VM would be a much easier solution rather than trying to get a dual booting working well.

Short answer: No

Long answer: It has not ceased development, but FOG does not update like regular programs. .33 is a complete rewrite of the code so it’s taking some time. The beta is out that you can download to test out the latest code. What we hope for is users to test the .33 beta and report bugs they come across in the forums. Once bugs are reported, the developers can review the bug posted and will be worked in the official release. Unfortunately, there is no official timeline for the release, but by all means, try the beta and post any bugs you may find.

You will also find that members on this forum are very helpful on a wide variety of issues that you may come across. We also have a wiki setup that covers a lot of ground from basic setup, how-to guides, and a wide variety of information relating to FOG.

You have a lot of drive space on your FOG server 0_0 lol, but good tutorial. I’m going to try this out with FreeNAS, just to see how well it works.

As long as the FOG client has been configured for your server and installed on the computer, it will work.

Voltage spikes and dips will really cause problems, do you have a UPS on them? That should help cleanup the power a bit. We don’t really notice performance issues when we image computers though. We have a 10Gbe running from our data center to the building i’m in, and run gig fiber to our switches from the core of my building. We then run gig to all of our computers as well. So long story short, we run gig from our PC’s to the core, then 10 gig to our DC. Where we do notice a performance hit is when we are trying to image a machine through a VPN. That will cause the network for us to slow to basically dial up speeds. However, most of our sites that run through VPN only have a 10 meg down connection, which would really choke the speeds. Generally though, even at the busiest times during the day, imaging a computer for us has very very minimal impacts, both to the network and the PC imaging speed itself.

Can you elaborate a bit about your network? connection speeds to machines, backbone, VPN’s between sites etc? At the worst, it might bog down the network, but by no means should it take it down.