Latest Development FOG
-
It makes sense, but I have no means to know what your password is going to be and whether or not they’re going to contain technically illegal characters.
One of the way’s to help out I suppose is edit your/opt/fog/.fogsettings file and set the password so it’s escaping the $$$ with something like $$$
-
When i go to opt/fog/ there is no .fogsettings file.
-
can you run ls -lhart on the directory /opt/fog?
-
its a hidden file hence the . in the front of the file name. just do a nano .fogsettings or a vi .fogsettings or your favorite text editor
-
My bad i figured it out… hidden file.
-
Pinging issue is still present tho. I have 311 PCs and if I hit list all clients and its in the middle of pinging every client, I cant advance to another screen.
-
Do you require the host pinging?
-
Question… What was the last SVN revision released that didn’t use the new client? And how good of a build is it?
I’m thinking about upgrading but I’m not necessarily wanting to use the new client just yet, we have a lot of computers here running the old one.
Also, another question…
What happens to the old clients out in production when the new client is enabled on the FOG server?
-
[quote=“Tom Elliott, post: 44237, member: 7271”]SVN 3138 released. With this release comes many more things. Specifically the Beta FOG Client is available now and is downloadable from the FOG GUI as normal. There are two links. One for Legacy and one for New. Hopefully this is self explanatory.
[/quote]Both Clients are available still in the latest SVN. You will should not have to do anything using the old client at this point. If you wish to use the new client then you will need to change an option in Settings.
It is [B]NOT[/B] suggested to have both clients in the same environment.
-
Tom,
No I really don’t need the pinging feature , however it worked in previous svns.
-
SVN 3215 released.
This has some changes to how host management works. It also, apparently, better fixes the random mac delete issue. It was working find for the primary, but pending and additional macs might have been lost as well. In this case, it could be bad especially for Laptops with wireless cards checking in, but not wired mac.
It also includes a checker to see if you’re in any of the directories we move during the installation so you don’t suddenly pull the rug under the feet of the script. Hopefully this isn’t a common problem people are running into, but I know we all forget things sometimes. This should help alleviate a momentary laps of how to install FOG when it’s in the tftpboot or fog web GUI folders to run the installs.
-
SVN 3224 released. With this comes some minor bug fixes particularly for green fog and should fix the seemingly random failure of getting the new client. One time all would be fine the next it would fail. To fix I now just tell it exactly what to get so hopefully this will work better.
-
Tom,
I just tried updating to SVN 3241 and during the install to update the database, I try to go to the admin section on the gui to perform the update and it just spins. Cant bring up the gui at all.
Ray
-
Tom,
Disregard I fixed it.
Ray Z
-
What was your fix Ray Z.
-
SVN 3258 released.
This hopefully better handles more random mac deletions and handles pending items a little better from what I can tell. It also adds protection for images and snapins for not only regular delete from the item/shortcut, but also if you decide to delete enmass.
-
SVN 3161 Released. Hopefully it works better for all pages that integrate with hosts as they’re no longer loaded until you implicitly click the membership link. Because of the way the link works the membership links are now right above the delete link. Some pages may have a slight delay in loading as they’re checking associative properties of the related element but it should load significantly faster unless you’re dealing with the memberships directly.
It also implements a hopeful coexistence for both the new and legacy clients.
-
SVN 3262 released.
This release adds a new feature an new FOG Setting category called Non-registered Host Image. In this option comes a FOG_NONREG_DEVICE field that you simply place like you would the kernelDevice on a host. This will then be read during imaging and target that specific device as long as it exists. I believe it fails if that device does not exist. This is a global value, so if it’s set, any Non-registered host regardless of image chosen will attempt to choose this disk. It’s simple enough to fix though in that all you need to do is delete the setting in order to have it choose the device for you.
Hopefully you enjoy,
-
[quote=“Tom Elliott, post: 45656, member: 7271”]SVN 3262 released.
This release adds a new feature an new FOG Setting category called Non-registered Host Image. In this option comes a FOG_NONREG_DEVICE field that you simply place like you would the kernelDevice on a host. This will then be read during imaging and target that specific device as long as it exists. I believe it fails if that device does not exist. This is a global value, so if it’s set, any Non-registered host regardless of image chosen will attempt to choose this disk. It’s simple enough to fix though in that all you need to do is delete the setting in order to have it choose the device for you.
Hopefully you enjoy,[/quote]
Are the OS disks normally all named the same thing, like sda or something?
-
Normally, in a perfect world, they would be. However, this is not a perfect world. Even if everything did come up with /dev/sd{[a-z],[A-Z]{2}} every time, there may be a case you want /dev/sdc to be the drive that’s imaged to, over /dev/sda everytime. People have different setups for their environments all the time.
