Moved images from FOG 0.32 to FOG 1.2 says not partclone image
-
Hey folks,
We were running FOG 0.32 and setup a new server with FOG 1.2 The network admin copied over the images to the new server with no issues. However when I try to use one of the old images, it gives an error when the client boots saying it’s not a partclone image. Any ideas?
-
@Stephen-Mahar Sorry to be
that guybut you should install the 1.3.0RC series to get the latest hardware support (specifically NVMe drives, GPT disk, and win10 support, plus current hardware).But with that said, I don’t remember much about 1.2.0 but in the image definition (in 1.2.0) you should be able to set a check box to use partclone or the older one used in 0.3x (image clone)? You need to tell fog 1.2.0 these are the older image formats.
-
Well it looks like that setting has been removed from 1.3.0RCx. I can tell you that if you deploy the 0.30 image to a target computer and then recapure it with FOG 1.3.0 your deployment times will be much faster than with FOG 0.30 and its image format. FOG 1.3.0 will be faster even with the older deployment format, but its pretty fast with the fog 1.3.0 native format.
-
@george1421 That checkbox still exists.
It’s under: FOG Configuration Page->FOG Settings->General Settings->FOG_FORMAT_FLAG_IN_GUI
-
@Tom-Elliott Well why the heck would you hide it there? jk.
Thanks, I was sure it was there on my dev box (a few versions ago). That configuration setting just turns on the option in the image management page.
-
@Tom-Elliott said in Moved images from FOG 0.32 to FOG 1.2 says not partclone image:
@george1421 That checkbox still exists.
It’s under: FOG Configuration Page->FOG Settings->General Settings->FOG_FORMAT_FLAG_IN_GUI
Just to clarify for those that don’t know, this setting merely enables you to change what program imaging uses on a per-image basis. It enables a menu that allows you to choose partimage or partclone for each image.
-
Thanks, that did it. I was able to push down the old images. Tks