Natively, no you can’t do this. However, FOG is built on PartImage 0.6.9. If you download the software, [url]http://www.partimage.org/Download[/url], you can put that on a flash drive, and as long as you grab your image from /images on your FOG server, you should be able to accomplish the same task.

[SIZE=4][FONT=Times New Roman][COLOR=#000000]Donna, unfortunately, at this time there is no official FOG training, just a bunch of willing people to help you on the forums if you come across problems. Lots of people on the forums are very knowledgeable when it comes to Linux and FOG itself. A lot of people like Fedora/CentOS for their base install, I personally use Ubuntu Desktop/Server for my installs depending on the factors.[/COLOR][/FONT][/SIZE]

[SIZE=4][FONT=Times New Roman][COLOR=#000000]That being said, i’ve found that it’s much easier to run programs through a batch file rather than trying to get a program to install right from the executable. However, I personally prefer scripts for any automation just because I know exactly what’s going to happen, and if it fails, I’ll know exactly where to begin to look. The one drawback to the current system is that it doesn’t always detect when one application is done installing before it tries to install the next, so at times, it will fail.[/COLOR][/FONT][/SIZE]
[SIZE=4][FONT=Times New Roman][COLOR=#000000]A neat feature that we use to great extents at work is the ability to boot ISO’s right from the FOG menu. We had DBAN, Parted Magic, Diagnostic CD’s, Pre Boot Environments etc all at our fingertips without having to lug around CD’s or flash drives. I also modified the .32 kernel code to be able to image machines without them checking in with FOG. So if you were at a workstation, you’d boot to FOG, select the image you wanted from the FOG menu, hit enter and it’s on it’s way. You didn’t need to set anything up on the web interface, you just selected it and off it went. The fact that you can boot into an antivirus is just that much better as well.[/COLOR][/FONT][/SIZE]

[SIZE=4][FONT=Times New Roman][COLOR=#000000]FOG .33 is in the works, and is a major rewrite of the code, but should be a more modular project to make it easier for others to write add-on’s for it. However, try to find sometime to work with FOG, it’s already pretty user friendly, but don’t hesitate to ask questions on the forums. You’ll get responses very quickly, and everyone is always willing to help![/COLOR][/FONT][/SIZE]

Yes, FOG is still an active project. Version .33 is a major rewrite of the code, so it’s taking some time to complete.

However, I’m glad that you’ve found FOG. If you run into any problems, you can post it to the forum and someone will be able to help you.

THank you for the quick response ! - I am collaborating across town so… wasn’t able to see, but our techs were telling me the machines just blinked a bunch and rebooted. ( attempting registration and inventory ) sounds similar to what I was getting when running the latest versions on ubuntu in my first efforts to get her up and running.

[SIZE=2]Currently running Fog 0.27 on a Fedora 8 Virtualized - purring like a kitten -[/SIZE]
[SIZE=2][/SIZE]
thank you for the helping me out > I’ll check on the boot/EFI and kitchen sync kernel. Hopefully they can send me some of these newer machines to test - I have a feeling its the boot\EFI > maybe need to play around with the BIOS -

Clients are easy. Run a host report that exports all the data into a CSV and you may have to tweak it to match the import format, but I did it on a test install and it was very easy.

This is still an issue for me. I have resolved the disk usage chart issue but still can’t seem to get FOG to use the full amount of available space in the VM.

When I first installed FOG, the VM was 64GB. I later realized I would need more space so I expanded the VM to 128GB. FOG doesn’t seem to be aware of this change. Is there a setting someplace that needs to be updated so it will use the entire VM storage?

Thanks

Restored previous config.php file and fixed the issue.

Nevermind, I was able to restore a config file from a previous snapshot.

Thanks! I will give that a try.

Found a solution that works for me. I deleted all of the computers and reimported them. I added a number string to the description field that I can search by to add them to groups. All of these laptops are stored on shelves with 15 per row and 6 shelves down, so a total of 90 per shelf. I numbered them in groups of 15. So my numbering scheme is: room they are in, shelving unit number, actual shelf then laptop order number. So looks like this: The first computer is E505010101 (E505 is the room). Last computer on bottom shelf unit 1 is: E505010615. This allow me to search for E50501 and pull up all 90 at once, or search in groups of 15. Is working well for me.

Any other ideas for another way of doing?

x23: Thanks, using that seemed to solve my problem - I appreciate the info - I hadn’t even noticed that entry, I’m still really new to FOG 🙂

Thanks a lot for the replies! Certainly a lot to digest but I’m willing! Jaymes, I really appreciate you taking the time it took to write all of that. I may very well take you up on the offer of working together with you on the walk through process.

Some MACs are formatted with dashes, other with colons, others without anything. FOG needs colons. 11:22:33:aa:bb:cc is valid. 11-22-33-aa-bb-cc is invalid, 112233aabbcc is invalid.

I’d go with Chad’s first suggestion. Keep in mind that if the zip file is larger than 1900 MB, then you’ll need to make some changes to the config before the snapin will execute.

You can try to remove them through FTP or NFS. I believe you can get the FOG users password from the webUI and use it to FTP into the machine and delete the images files.

sorry, yes you’re right regarding the process. it is alot of core changes you need to make to include this as you would need to edit the init.gz to include rsync and would also need to include the location patch to determine which storage node to pull it from:
[url]http://fogproject.org/forum/threads/requested-multi-site-location-patch-requested.410/#post-4570[/url]

however this is coded based on 0.31 and it’s not being included in the future releases but may be able to use the new core and hook functionality to include this but this is all on hold really until 0.33 is ready for production.

So to summarize you would need to make alot of changes to use it in this way - maybe someone else has simpler solution to suggest?

Just in case this process would benefit others out there…what I wound up doing is setting up a large samba share on the FOG server and adding an Acronis iso to the pxe menu. That allows us to push a unique disk-to-image-file backup directly from a client system to the FOG server’s samba share without going through the registration process. I was hesitant to go this way because I thought having two processes for imaging would be messy, however it’s turned out to be a great! We use the FOG side for bare metal imaging of new systems and we use the Acronis / Samba side for backing up incoming systems before we work on them. This keeps the FOG server nice and clean and the separation is a better setup for me because when it’s time to purge old client system backups there’s no worry of mistakenly deleting a production image.

Thanks to everyone involved in the fog project. It’s just awesome!

Scott.

I love this actually working with the device instead of just punching buttons…reminds me of the good old days of DOS. I look forward to working with everyone.

btw…after all of that I decided to put it on a different box. I would have loved to troubleshot why it wasn’t working correctly, but a deadline was looming so I killed it and reimaged the workstations again…took far less time than the first.

[quote=“thomas Bollig, post: 12433, member: 4211”]Thanks again for the info. Here is a little more info for you
My etc/export on the FOG server is

/mnt/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/mnt/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

and on the NFS server
/images 10.32.3.27/22 (rw,sync,no_root_squash,)
/mnt/images 10.32.3.27/22 (ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/mnt/images/dev 10.32.3.27/22 (rw,sync,no_wdelay,no_root_squash,insecure)

Fog Server Permission on /mnt/images
drwxrwxrwx 2 nobody nobody 37 May 30 07:06 dev
-rw-r–r-- 1 nobody nobody 0 May 29 11:58 mntcheck
[root@fog ~]#

NFS Server permissions on /images
drwxrwxrwx 2 fog root 37 May 30 09:06 dev
-rw-r–r-- 1 fog root 0 May 29 13:58 mntcheck
-rwxrwxrwx 1 fog root 0 May 29 12:46 .mntcheck
drwxrwxrwx 4 fog root 29 May 29 12:11 .Trash-0[/quote]

Also there is not authentication needed to access the nfs