Quick Question about pulling an image
-
I already pulled my first image, but I was going to pull a second and wanted to make sure of the process. Am I correct in that you create a new image under “Image Management”, then go to “Host Management” and change the image that is associated with the host, to the new “blank” image, then create a task to upload said image to the blank placeholder? The first pull went very smoothly, but I didn’t have any images created yet, and I don’t want to accidentally write over my first image.
On a similar note… are the images supposed to be extremely small?? I pulled a base image of Windows 8.1 and the image size was roughly 350MB… That seems soooo small.
Thanks in advance for the help!
-
Ok, this is odd. Every image I try to pull is only 350MB… I’ve only tried to pull Win8 so far, as that is my current task as work. We’ve always used Ghost Solution Suite, and never had an issue up through Win7. Now that I’ve seen what all FOG can do, I really want to switch all of our imaging over, but they want me to get Win8 working first.
Someone please help!
-
Have you tried redeploying the image?
What’s the Image size being reported by the system?
What version of FOG are you currently using?
-
I haven’t tried deploying yet, but I’ll try it though.
Both images I’ve pulled are saying that they are 350MB each, even though the newest one is almost 2GB larger.
I’m currently using FOG version 0.33b (build 1210)
-
What image type did you set under image management, what disk type did you use?
I recommend using the “Multiple Partition Image - All Disks (not Resizable) - (3)”
You can create multiple image stores aswell, that way you can make a “test” image and a “test2” and so forth, then when you want to switch the image deployed you can do so from the Host management page by selecting the Host and changing the host image from the drop down box.
This way you can try multiple uploads (remember to change the Host Image on the Host Management screen other wise you will over write your current selected image). Honestly I do all my imaging on a Virtual Host and let it upload that way I am only having to change one Host in the management screen to upload a new image and create the task, and I only have to keep track of one Host in the list, I name it MASTER or something along the lines so I remember which one it is.
-
Ok. It seems to be working now. I changed it to “Multiple Partition Image - All Disks (not Resizable) - (3)”.
I also managed to push the original image to another machine, and it works fine. I think what is happening is, the “Image Management” screen is only showing the size of the first partition, not the entire size of the image. In Windows 7 and 8, there is a small 350MB reserved partition that is created as the first partition… Is it possible to fix this to show the entire image size?
lol, I was wondering how the Ubuntu/FOG install and a 350MB image was taking up 3% of a 500GB hard drive :D!
-
I noticed this as well, I thought it odd, but I checked on the server and found the files for both partitions and the second file was a few gigs after I deployed the image it worked fine… May be something for Tom to look into
-
Yeah,
I’m aware of the issue, just don’t know the best approach to correct it yet. Sorry.
-
Just my two cents, but if each individual image (all partitions) was stored in it’s own directory, couldn’t you just output the total size of said directory? So, if there were 3 partitions to a specific image, you have all 3 partitions stored in a single directory that could be named for the image name. You could think of the directory as the logical form of the physical drive, with all the associated partitions stored neatly inside…
-
That’s more or less how it currently works.
That said, the image size would be inaccurate if we’re doing it based on the size it takes on disk. The size you’re seeing in the Image Management, is the physical size of the image as if it were on the Disk. Meaning, if in image size you see 3.7GB, you would need a drive that larger or larger to image onto. If I represented the physical size of the files, it would only be about 1.2GB which is inaccurate. That and for MultiPart Images, freespace compresses very very good, so you might have a partitioning scheme requiring 10GB or more. But your image size would only display 2 GB (or whatever it decides) which would not be any where near close enough.
-
Ah… I forgot to take compression into account.
ok…
Perhaps the software that creates the image, has some sort of log or report output, that could be read and parsed into the image management list?
Sorry… I hate leaving problems unsolved!
My current job has a love/hate relationship with that part of me… They love that I come up with so many ideas, but the ideas usually end with someone saying “it costs too much”!
-
It doesn’t cost anything, I just have to figure out where the bug is and squash it.
