The mbr partition should be re-installed when you re-image, make sure you select the correct O/S type when you assign the image to the computer. I am not sure about the “user” settings, you can change the machine name if that is what you mean, from the FOG dashboard under HOSTS you can assign the computer name you need to each host which will then be applied on the first boot. You will also need to [url]http://yourfogserver/client[/url] and install the FOG client to allow it to change the machine hostname.

I know this is going to sound a bit of a odd request of help, as it asking FOG to do something it is not designed to do.

Some background, the idea is to create a dual boot W7 and Ubuntu 11 installation, I have managed to get rid of the 100mb system reserved partition for windows so I now a 4 partition setup, Win 7, Win 7 data, Ubuntu, Swap.

One of the main issues we have in this project is speed of re-image, and there is no budget to improve the network hardware or the client hardware for that matter.

Now as a very quick and dirty experiment, I manually renamed the Windows partition image files on the server leaving just the .mbr and the Ubuntu installation image in place, while FOG did complain slightly as expected about not being able to find some files the image worked on a blank hard disk, grub was re-installed and Ubuntu worked as expected.

So my next though was would it be possible to add a either a submenu to the Quick Image option or additional menu items to offer the following options.

Re-image Win7 only
Re-image Win7 + Data only
Re-image Data only
Re-image Ubuntu only
Full re-image

I guess it comes down to is this possible and if so how would I go about achieving it?

Yet more testing…

FOG 0.32 on Ubuntu 8.04

Machine I am testing for the image is

HP D530 USD
P4, 2gb, 40gb

Started with a base Win 7 install with 2 partitions, 100mb + 20gb image upload and deployed to original disk and another 40, 120 and 160gb drives with out issues.

Next I followed the [URL=‘http://www.fogproject.org/wiki/index.php?title=Client_Setup#Dual_boot_Images’]guide[/URL] for linux

So now the setup was Win 7 100mb + 20gb + 1gb swap + 6gb Ubuntu

This would image up and down fine with the 3 test drives

Next I re-imaged with the base Win 7 Install added a 9gb data partition + 1gb swap + 6gb Ubuntu

The image uploads fine, but I end up with the cant have partition outside disk error on deployment to any of the test drives.

Next test was to revert to base Win 7 image, then create a 1gb swap + 6gb in linux as logical partitions and leave the rest for the windows data partition to be created post install.

Again the image uploads fine, but deployment ends with the same error.

So that leads me to conclude that the issue lies with logical partitions.

I am sort of in the same boat as the original poster, except we are using a 40gb drive to create an image and trying to deploy to a 40gb drive.
What we are trying to achieve is this. Windows 7 32bit (20gb) NTFS Data Partition (9gb) Ubuntu 11.04 (8gb) Swap (1-2gb).
We can create and upload the image with no problems, and it will deploy back to the machine it was created on correctly, trying to deploy to another machine causes the cant have partition outside disk error.

We have tried doing just windows 7 and the data partition, and this will deploy to the other test machine as expected, even with the OS type set to linux. I have spent the last two afternoons trying to nail this one down, I have even made the partitions smaller to ensure there is blank space at the end of the drive, and it still will not deploy, I am clearly missing something, the question is what?

I know this is not really what the snapin feature is designed to do, but as part of a project we are looking to use FOG to deploy images to a number of client machines, a caveat to this is that the client also wants to upload and distribute virtualbox .vdi files to all the clients which of course could be included in the base image easily enough. The client may want to distribute new or updated files at some point in the future. The files they are currently using are 1.5gb - 5gb in size. Now looking round the forums I can see there is a method for uploading the files directly to /opt/fog/snapins folder, what that post does not make clear is how to make fog see the files you have uploaded directly, so how do you make FOG see and use these files?

[quote=“Blackout, post: 417, member: 1”]The problem is that HTTP POST (the method used currently to upload snapins) was never designed to upload large amounts of data. 2mb is the default, this gives you an idea of the sizes it was originally designed to send.

The snapin code needs to be updated to use a modern Flash or HTML5 uploader.

For the time being, you should upload large snapins manually.
[LIST=1]
[]Download FileZilla - [url]http://filezilla-project.org/[/url]
[]Create a profile for your FOG server
[LIST=1]
[]File -> Site Manager
[]Click ‘New Site’
[]Host: [I]<your_server_hostname_or_ip>[/I]
[]Port: 22
[]Protocol: SFTP - SSH File Transfer Protocol
[]Logon Type: Normal
[]Username: root
[]Password: [I]<your_password>[/I]
[]Now click ‘Connect’
[/LIST]
[]Navigate to: /opt/fog/snapins/
[]Upload snapin exe file
[]Profit
[/LIST]
[/quote]

Sorry to jump in on a thread, but you have 99% answered a question I had about large snapins. After getting the file to /opt/fog/snapins
what do I need to do to make FOG do to see the files ?