Posts made by Eric V. Baker

A question that has come up here at work is since I am experimenting with the beta, how stable is it and when is the expected release date of a stable release?

This got me farther along. I will do some more testing this weekend.

Yes, i did an upgrade to an existing 0.32 server as this is the same as my production environment.

I am equally frustrated. Right now I have a deployment of HP Z230’s coming in in probably less than a month and no deployment solution. I am probably going to have to go to each machine and image with a #$%^& boot disk and image by hand and also manually rename and add to the domain like I had to do back in the dark ages.

I set up a virtual environment for testing. In my router, I set the boot file to undionly.kpxe. When I boot form the network, I get a new-looking FOG boot menu, but when I choose to do a full register or a quick register, the machine says there is no operating system and reboots. I know there is no operating system on the hard drive, but if I can’t register the machine, how can I image the machine.

As of now, I am disabling FOG Service on the client PC’s so that they are not checking in. I hope to plug the server back into the network later today so I can work with a controlled number of PC’s. I don’t have the luxury of a non production environment so i will just take all the clients off the server for now.

As soon as I upgraded our FOG server to the beta, when the clients checked in, the server told them to reboot for some reason. I did not have the undionly.kpxe line in my DHCP server yet so my clients rebooted and went back into windows and then as soon as the FOG Client timeout came, they checked in with the server and the server told them to reboot again.

I was able to update the server but it did create chaos. As soon as the server came online, it tried to update all of the clients in some way and because my DHCP lines are not changed in the Cisco switches we use for DHCP, all of the client PC’s were stuck in a loop of rebooting to get the client update. I had to pull the plug on the server to stop this. OOPS!Is there a way in the FOG configuration to allow me to determine when the clients get updated?

I shall try it.

I have not tried the beta. Where do i acquire this version?

Due to a lack of a solution here is it safe to assume that FOG will not be able to image these new common hardware types until POSSIBLY a new revision? I know there are a lot of FOG users out there who are now looking for another solution if FOG will not work. I hate to say it but I am having to use a G#### Boot disk to image machines again. This is a sad day for those of us who have enjoyed using FOG to image whole labs from our offices.

Any progress on this issue?

The server has been working with no problems for a couple months now. This is a new PC model for us that we are trying to create an image for. It is an HP Z230.

The size of the file in the folder name the same as the MAC is 4.0K in file d1.mbr

The fog passwords DO match between the FOG_TFTP_FTP_PASSWORD and the storage management password

Hi to all!

I am attempting to upload a Windows 7 image from an HP Z230 to my FOG server 0.32. On upload we are getting the[SIZE=3] “unable to move /images/dev/macaddress to /images/name-of-image” [/SIZE]problem seen before. I did the chown -R fog.root /images and chmod -R 777 /images and are still getting the problem. looking at the /images/dev folder I see the folder of the MAC of the PC being used to create teh image. inside it is a d1.mbr file. In /images there is no folder created for the name of the image file that should be created.

Any ideas?