We have run Fog on a virtualbox vm from the first time we used it. Had no troubles at all. It’s been rock-solid. Way easier than setting up a separate box if you already have some sort of VM infrastructure in place. Performance has been fast enough for us.

Not having used FOG to deploy another OS apart from windows, I can at least confirm for you that if you choose multiple partition single disk, it will back up the MBR and restore it too. What I use is 1 Windows 7 64bit OS that joins our domain, and a second Windows 7 32bit that is standalone and I use the multi partition single disk option myself for this.

I also know that if you have just one copy of windows on a drive that the single partition option will do the same, even though windows 7 usually installs a 100meg partition at the start of the disk, this is included in that option.

As for the virus stuff, there is actually an option under task management to set a client pc scanning for viruses using clamAV. When you et it off to scan it reboots the pc, starts in clamav mode and goes looking on the internet for the latest signatures which it downloads and uses on the fly.

Hope this helps.

[quote=“roger.franklin, post: 8964, member: 2627”]Hi guys,

I just recently found this amazing tool for imaging solution and I would like to congratulate the developer’s team and the community for bringing this to public for free. It is really awesome tool.

I am actually planning to leverage this tool for my malware analysis setup. I would like to deploy my “clean” image every time I have finished performing malware analysis. Having said that, what I would like to accomplish is to run a fast wipe and immediately deploy my clean image. My wish is to make this two separate tasks at once and if possible automate it so I will always have a clean image - i.e. MBR is also wiped.

Thank you very much in advance.

Kind regards,
Roger[/quote]

I think i’ve got a good start from the wiki [url]http://www.fogproject.org/wiki/index.php/Modifying_the_Init_Image[/url]
My idea is to play with fog.wipe under /tftpboot/fog/images/init.gz. Hopefully I’m in the right direction. Please advice if you have some alternatives.
Thanks again guys.
Regards,
Roger

[quote=“djm79, post: 8953, member: 1568”]Yea thats why you need to look in the folder that you used to install fog and there will be a fogcrypt run this on a windows machine from the command prompt and it will output the password encrypted and then input that in your fog settings and test joining.[/quote]
Thank yo so much…will try that…

In a separate database import the hosts and inventory tables from all the fog servers. For each table add a new field that contains the server identifier so that host1 from server A can be differentiated from host1 on server B. basically change the index on the hosts and inventory tables from being a single field to be comprised of hostid and serverid. You’ll have to decide on the serverid values and insert them into the reporting tables as you import from each server.

In short: Yes, you can do this for creating the image, but no its not exactly as you have imagined.
and No, you can not use this method to deploy images to a host.
Details: There is an option from the PXE menu that will allow you to do a quick image. But, that is relying on you to have previously created an image and a host.

If you are intimidated by the web UI, don’t be. It may take a short while to familiarize yourself with the options, but once you understand how to A: create an image and B: Create a host; it is really the best way.

Personally, I do not auto register my hosts… I manually enter the hostname and image type in the WebUI, then set the task to do all of the rest. Then, once I reboot the host, the imaging begins automatically.

Everyone here is here to help, so do not hesitate to ask for assistance.
(and check out some video tutorials)

I agree with djm79 (again, promise I’m not stalking ya). You don’t delete the image definition. When you need to update an image, you DEPLOY to proper hardware, make your updates, and then UPLOAD that computer and it overwrite the old version of the image.

Some things to note:
Make sure you prepare the computer before uploading the image. If you make tons of changes, it’s probably wise to defrag again and chksdsk /f

Remove from the domain before you upload.

An image that is being uploaded is stored in /images/dev/, and when complete, is moved to /images/imagename. So you’ll need enough storage available to hold the old image and the new image until the image is completely uploaded and FOG removes the old files and replaces with the new ones.

Sysprep with Windows 7 will not correctly rename and join computers to the domain. It does the join to domain before the rename. Means you get computers in the domain named WIN02349XXDF0S, when the computer is really named BOB.

Install the FOG Client ([url]http://[yourfogserver]/fog/client[/url]) on your image and let fog rename and join the computer to the domain. You’ll need to get FOGCrypt onto a windows machine to encrypt the password you use to authenticate to the domain, but there is info in the wiki on how to do that.

Thanks so much for your quick replies! Yesterday I added that same line to the lftp config file and it worked just fine. This is a great feature since we will be replicating images to 8 of our remote sites, some of which have a slow connection to us (and operate 24/7 so after hours replication isn’t a viable solution). Thanks again!

Set to multiple partitions - worked like a charm.

[url]http://www.fogproject.org/wiki/index.php/Plugins:_Capone[/url]
and
[url]http://www.fogproject.org/wiki/index.php/Capone[/url]

You tell it the DMI field to key on and which image to push based on that DMI value.

Yes. installation is always complex when you want a complex install.

wubba,

Welcome to the forum and FOG in general. While you can use FOG like you intended. It’s not very efficient. FOG is really designed to be a business/enterprise imaging/deployment solution. So you would have 1 master image for desktops, and another for laptops, assuming you’re using XP. Or just having 1 Windows 7 image for everything. While you can make an image for every machine, it would require A LOT of hard drive space. Currently, our server has 7 images, plus bootable iso’s and i’m only using 56 GB of space on my drive. However, if you are looking at doing daily backup’s, I would recommend that you look at Clonezilla. It’s free and relatively easy to use. While FOG can do everything that you want it to, it might be a bit of a hassle and a lot of work to get it to work the way you want.

Please feel free to ask any more questions you may have, or if you have any concerns.

Hi Chad-bisd,

Yes I am setting the setting under the client and I made sure global wasn’t ticked on, it did not work.

I have also tried global ticked on and service settings set under the client.

The only way it will work is if the global setting is set, but this means all the clients will have the same resolution and this does not fix the problem.

Thanks

Lee