@falko - Do you have any sort of guide on how to have FOG update bginfo. We currently have to do this manually, and it would be so helpful to have it automated! Right now, we run bginfo, update the date and image name, then have a small batch that uses mini irfanview to change from bmp to jpg, then copies to the oobe folder for the lock screen. (this is for Win7).
Posts made by BigMan99211
-
RE: Bugs in FOG 0.33
-
RE: Quick Question about pulling an image
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”! -
RE: Quick Question about pulling an image
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…
-
RE: Quick Question about pulling an image
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!
-
RE: Quick Question about pulling an image
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)
-
RE: Quick Question about pulling an image
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!
-
RE: Bugs in FOG 0.33
I’ve always been a proponent of making installations easier, or even more customizable through the installer. Ask a bunch of questions at first, and make the setup and configuration a lot more seamless.
-
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!
-
RE: Bugs in FOG 0.33
I can understand that. But, couldn’t you just put in a simple question during install, asking if you have any other websites or software that utilizes Apache? If yes, it skips. If no, it deletes the .html file. Seems pretty simple.
-
RE: Bugs in FOG 0.33
I guess so. I saw where the Fog install adds the index.php with a redirect to “./management/index.php”, but apache2 didn’t recognize it. It just kept showing the default apache “It Works!” page. But, once you remove the default “index.html” page, everything seems to work just fine. Perhaps a Fog installer oversight?
-
RE: Bugs in FOG 0.33
Ok, I see what I did. I tried to modify default in /etc/apache2/sites-available/ to default to [url]http://(ip[/url] or host)/fog, so all I would need to do, is type [url]http://(ip[/url] or host) to get to the Fog login page. It was working, but I was getting the above error…
-
RE: Bugs in FOG 0.33
Hmmm… I’m not sure how it was a config problem. I pretty much used the default settings, other than IP, subnet, etc…
-
RE: Group Management Bug
Wait… I was just reading back through what you said. I have the AD_DEFAULT set to my domain info already. Should that be showing up then?
-
RE: Bugs in FOG 0.33
Oh… Just noticed this thread. Not sure if i’ve found a bug or not, but I just updated to 1210 and now under Disk Information on the Dashboard, I have this error/link that says, “Failed to connect to DefaultMember”. When I click the link, it takes me to the Hardware Information screen and has a message saying, “[FONT=Ubuntu][COLOR=#555555]Unable to pull server information!” [/COLOR][/FONT]
-
RE: Group Management Bug
Ok, good. I like to find bugs, I just don’t want to make too much more work for you!
-
Group Management Bug
Hi,
I found a bug in the Active Directory portion of a created group. By default, the group has DN and OU fields blank, with fog listed as the username and I assume password listed as the password. The bug is, every time I attempt to alter any of the fields and save, it defaults back to the original info as stated above… or is this intended?
-
RE: Invalid hostname?
Ok, I got it updated. Thanks for all the help. Everything looks great now!
-
RE: Invalid hostname?
I don’t really want to run a clean install. Is it worth the effort to set up the subversion client? I’ve already installed subversion, but my install of fog was originally, manually installed.