Topics created by Frazer

You could write a plugin that could do this for you. Something like an “archive” plugin that moves hosts out of the “main” element and into your “new” element.

I realize writing a plugin can be hard, but I don’t think this is something that should be a part of the “core” of fog.

@Tom-Elliott I didn’t realise it was as easy as that - will give it a whirl next time we get a new batch of computers.

Thanks

In FOG 0.33, the host no longer has an OS. The OS is tied to the image.

I have modified the script in the init.gz to truncate to 15 characters and warn if truncation was necessary. I still have not modified the webUI to limit the field in html, or to truncate the value in the processing of the form data.

I agree this would be nice, and for the most part, I never need over 15 characters. Maybe this could be configurable through the FOG settings for a max host name length in case there was some need to have it longer than 15. There is a limit due to the field size in the datastore also, but that can be queried to make sure the UI or registration scripts are not exceeding that.

I took the WD harddisk from one of the GX745’s that worked, put it in the GX755 that has the issue, then reimaged with the same image, works fine; I then took the Seagate harddisk that was originally in the GX755 and put it in the GX745 and tried to reimage, and it works as well…go figure, am totally confused as to why FOG images the Seagate fine in the GX745, but not in the GX755…