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?
Latest posts made by Eric V. Baker
-
RE: Another unable to move /images/dev problem
-
RE: Another unable to move /images/dev problem
This got me farther along. I will do some more testing this weekend.
-
RE: Another unable to move /images/dev problem
Yes, i did an upgrade to an existing 0.32 server as this is the same as my production environment.
-
RE: Another unable to move /images/dev problem
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.
-
RE: Another unable to move /images/dev problem
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.
-
RE: Another unable to move /images/dev problem
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.
-
RE: Another unable to move /images/dev problem
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.
-
RE: Another unable to move /images/dev problem
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?
-
RE: Another unable to move /images/dev problem
I have not tried the beta. Where do i acquire this version?