Best posts made by Joseph Hales

Could we have the web interface indicate that a storage node is correctly connected passwords match ect… maybe a green dot like the ping status when its added or listed in the all storage nodes list. A second indicator that all the images are in sync with the main repository.

I second that emotion you guys are awesome.

Don’t forget that around SVN 3410 and up the storage node installer resets the storage password when run. It should display the new password at the end of the install.

We’re not using the new client yet I upgraded to SVN 3463 this morning which fixed the missing client issue.

Chrome has a special enterprise installer available here. Your runwith command is msiexec, the run with argument is /i and the command line switches are /qn.

He has 1.2 he is upgrading to SVN when it happens.

I try and keep a USB drive backup of the images offline as well as the configuration save to permit an easy rebuild from scratch if necessary. Most users update images rarely enough that this is not a huge burden.

It really depends on usage. How many clients, how many images, how large are your images, compression level, number of images sent at a time?

As I understand it 4 things need to match the Operating system password for the fog user, the storage management password and username fog, the tftp password under the web ui in fog settings and finally the storageftpuser / storageftppassword in the /opt/fog/.fogsettings file. After they all match restart the fog services or just reboot the server.

/silent should be in the Snapin Arguments field.

Any chance of torrent cast working anytime soon I just deployed 400+ images this weekend and could have really used it.

check your permissions on the dir that contains your isos if it correctly set ups you should be able to hit it with a web browser like this. http://fog ip/fog/iso

While it doesn’t find all issues it is quick to check and will reduce issues with imaging a bad drive, I certainly haven’t see any false drive failure messages.

svn 3728 fixed this for me.

I believe you will need to upgrade to SVN for that feature but its pretty stable now.

If you are not updating images that often it might be more logical to sneaker-net images to the other site we you make changes.

I see it occasionally the simple fix is to deploy the image expand the partition and run fixparts if needed then reupload.

If the error occurs after you image the machine I really suspect you are having an issue with the hard drive partition table. When I ran into a similar issue we ran the windows repair on the newly imaged pc and then uploaded the fixed image which seemed to solve future issues from then on.

Untold bug fixes, greater speed on upload and download, additional features. It is well worth it in my opinion.

You could run a script task as a snapin drop the pc’s from the domain and then just change your AD settings in fog so they rejoin the new one.