ssx4life

True, the TFTP folder gets wiped out... except on 0.28 which was a request of mine. It now appends it instead of over writing it.

ALWAYS back up your fog server to a 1:1 image using some 3rd party software before you go crazy with upgrades / updates. Not to be paranoid, but I've seen issues @ times.

This has happened to be before with FOG but only once. And it happened because I shut down the imaging before it was completed. Basically FOG backs up SDA1 (partition 1) and compresses it with Gzip. It can then be deployed to any other hard drive regardless of size and expands it. Make sure that your base computer (original) has a full expanded hard drive partition so it "sees" all of the space allowed. Download Gparted and expand your computer's hdd image to 100%. Re-image and let me know what happens. Also please tell us what the make / model is of your pc. Also the hdd make / model / size would be helpful.

Every semester for us. We have roaming profiles, and the students know to back their data up to their network share not the desktop / etc. Give notice 2 weeks in advance (last 2 weeks of the semester) that all data will be wiped from the machines if they don't back it up to the proper locations. Simple fix =)

one more thing... if you have vista / 7 and have a centeralized key that is provided by M$ make sure you specify if you are using a kms or not. (key management server) Failure to do so can be a pita.

Correct. Vista / 7 use scripting for an answer file. Windows Vista Deployment Step-by-Step Guide

If you have a VLK / KMS then you are fine for keys. If not you are playing with fire!!!! be careful and make sure you are with in the terms and limits of your license.

Get the pc set up the way you want before you sysprep it. Sysprep will change the SID and shut down. you then image it and deploy it out. On reboot it will go though the sysprep process. Lots of info out there on MSDN / MSFN.

Before you add any AD intergration make sure the host name changer is working correctly. If this is not AD will also fail. Verify that the name is properly set via the webgui (the mac address for that pc is set to the name you want). On ever restart of the pc the host checks in with the server only once to make sure it has the right name. If not it will restart, if it does it will ignore it. You can speed this process up by going to services.msc ----> fog service ----> restart. Do your testing that way. Once this is working correctly focus on AD... as others have mentioned make sure the password is encrypted using fogcrypt. Also some others have mentioned in the past that md5 packages were not installed correctly on their fog version (check the supplied links above). --ssx--

I assume he sent a .reg file edit to modify the pc's.

I forgot to mention you can also do all sorts of other cool things with FOG, and even incorperate it into your existing setup and deployment methods. For example.... FOG uses a TFTP server which will allow you to boot up and access any 3rd party software over the network if used and set up properly. I've used the fog PXE server to image computers with the following software. Norton Ghost BartPE / WinPE /etc. (cd .iso boot) Acronis True Image (cd .iso boot) Altiris RapiDeploy Clonezilla (cd .iso boot) etc. This is mainly achieved by using netbootdisk and then having that load free-dos which then enables networking capabilities, and launches what ever program I want. I even have my current FOG server set up to launch / execute applications such as DBAN / hardware diagonstics / etc. It's pretty amazing stuff, and if I get any free time I plan on fully documenting this for everyone. If you want to see an example of my fog server in action check out the .zip file attached in this other thread - http://www.edugeek.net/forums/o-s-deployment/42667-usb-ghost-boot-common-nic-drivers.html TFTP will allow you to boot almost anything (possibly even ping? never ever used it so it's up in the air on that one) Again if you need help hit me up on google chat - [email protected]

Doubtful, but I'm sure it would be easy to move them to fog. I've dealt with FOG for the last oh.... 4 months or so and we came from Altiris / Norton Ghost / Acronis (yes all 3 and a mish mash ) First step is to go into your system's bios and enable PXE boot as the first option Also enable Wake on Lan Don't forget to set your computer to use legacy or SATA mode via the bios (ACHI doesn't play nice with fog or linux imaging) Second step is to take the sysprep'ed images in PING or any other format you can image the pc with your software and then TURN the unit off. PXE boot the computer to FOG and do a quick registration. Turn the pc off again (don't let it boot into windows) Go into the FOG console and create a new image and link it to your new pc. Even make a new group if you want to get specific and save time going forward. From the web console you then want to UPLOAD an image to the server on that pc, which will wake on lan the computer, pxe boot linux, and start uploading the image. Vollia! You now have an image that is in FOG. I'm trying to write documentation on FOG and also work on video's for all the cool things that FOG supports. So if you need any help hit me up @ any time via IM / PM / etc. --ssx--

FOG does so much more than PING or any GPL based imaging program. Clonezilla is a close second for standalone 1:1 imaging. FOG :: A Computer Cloning Solution - Home

If your school happens to be using Server 2003 / 2008 may I suggest that you go with a TFTP server as a more automated solution? It's more automated that USB based booting and imaging and require no physical media at all. http://www.fogproject.org (my favorite open source project) TFTPD32 : a opensource TFTP server/service for windows : TFTP server Even if you don't use FOG for full time deployment and management you can at least use the PXE server for launching netbootdisk to ghost systems, and remove the need for USB. I have run into problems using USB netbootdisk versions in the past FYI, but the issue you are having is with not having an automated logon and execution script setup and working correctly. Take a look at your logon.bat file that is located on your usb flash key. Here is my logon.bat file that I use. Your results may vary from network to network, bu the idea is still the same. net use g: \\htpc\images g: dir ghost.exe -rb Let me give you a visual example (did I mention I love camdista studio 6? ) (see attached .zip file) I think the main issue we keep coming back to here is that you are using usb flash media for this that is not fully setup and configured.... or not saving your preferences when it launches. When the app first runs point the login script to logon.bat instead. Don't type net use g: \\server\share in line 4 of the menu. It really is that easy =) I prefer to use the floppy version and get it working exactly the way I want. Then I can use winimage to take an .img of the floppy disk and stick it on my TFTP server and PXE boot it (as shown in that video I just attached) TCP IP 2nd help walkthough.zip

Did you look here? - FOGUserGuide - FOGWiki Looks like other people have the same issue with this model. Check here - https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/3413534 If you can get that kernel or compile your own you should be set. Appears to be a known issue at this time. Perhaps when the new version of Ubuntu comes out (9.10 Ubuntu Home Page | Ubuntu ) it may have an updated kernel you can use. p.s. you can try loading fog 0.28 with the ubuntu beta to see if that kernel offers any update / fix for you. Worth a shot perhaps?

What type of installation are you using? VMWare / Fedora / Ubuntu ?

Hummmm you've got a few good points there when it comes to the domain log in script. Few questions for you #1. Have you been able to successfully map a network drive yet out of the gate? You mentioned you were having problems previously, so I'm just trying to cover all the bases #2. Have you been able to do any ghosting via network yet? Even single restoring? #3. What type of network are we dealing with here? Server 2003 / 2008 RC1 / ? If you still can't connect to any network resources out of the gate look into modifying your LMHOSTS file to auto include the network resource in question. I had to do this for my home network due to lack of AD / WINS support. # LMHOSTS File - UNIVERSAL TCP/IP NETWORK BOOTDISK for M$ Networks # # # *** INSTRUCTIONS *** # # Add your host information to the end of this text file. This file is saved # back to the floppy disk under A:\FILECOPY\LMHOSTS, should you wish to modify # this file externally. # # Use the cursor keys to navigate this file. To SAVE CHANGES made press ALT+X, # otherwise press ALT+Q to discard changes and return to the menu. For futher # inforamtion about this editor, press F1. # # # LMHOSTS Example: # # 149.124.10.4 server1 # main office server # 182.102.93.122 joe3 # joe's database server 127.0.0.1 localhost 192.168.XXX.XXX HTPC #4. If you can't map a drive try doing just a menupref.bat edit and ignore the logon.bat side of things to start **example** @echo off REM The Menu Program reads/writes to this file. Please boot the disk and allow the Menu Software to modify this file. The password field is Encypted! REM *** Do not change the order of the commands in this batch file. (Or the Position of the equal signs!) *** rem NETCARD=EL3c574 Set WORKGROUP=MSHOME Set USERNAME=Administrator ::: PASSWORD=Egvmszhz‚<;<@ (note that it's encrypted) Set DISABLEDHCP=0 Set IPADDRESS0=192 168 0 123 Set SUBNETMASK0=255 255 255 0 Set DEFAULTGATEWAY0=192 168 0 254 Set LOGONSCRIPT=net use g: \\htpc\images rem TIMEOUT=5 Set DNS=192 168 0 253 Set WKSTN=BD2783014 Set PACKET=1 Set DNSENABLE=1 Set MOUSE=1 Set REDIRECTOR=Basic Set NTFS=0 Set CD=0 Set UDMA=0 Set WINS=192 168 0 252 #5. I have had a full ghost netbootdisk working in the past with Active Directory, let me see if I can find an example for you. Your logon.bat looks ok as mentioned previously, but remove it if you are having problems when you start p.s. you can also authenticate to the LOCAL pc instead of the network side of things (a.k.a. Administrator account), not sure if this makes life easier for you or not but that is also a possibility. #4. I have compiled the netbootdisk walk though I had been meaning to create for awhile, check it out and let me know what you think. Once you have the disk working properly go ahead and image it using winimage and convert the floppy into an .img file . You can then PXE boot it using PXE Linux or my favorite open source app FOG (Free Open Source Ghost) FOG :: A Computer Cloning Solution - Home [ame=http://www.youtube.com/watch?v=Yb3YcLDpa8U]YouTube - TCP IP Network Bootdisk[/ame] Best of luck in your endeavors! Keep me posted on your progress.

I can make a .bat file for you. Please tell me EXACTLY what you are wanting to do. 1. Use the default Login name + Password + Domain 2. Use login.bat to map a drive and auto launch ghost.exe I'm assuming 3. ????? p.s. I have a full walkthough on netbootdisk that I have been meaning to upload to youtube for awhile. Here is an example of netbootdisk launching via PXE (take the boot disk floopy and turn it into an .img file, and then put it up on the pxe server ) - [ame=http://www.youtube.com/watch?v=jjDtJtuwIps]YouTube - Fog Project: Modified PXE Boot Menu[/ame] I'll have a full walk though uploaded later today when I get home from work (-6:00 GMT). It's on my laptop which I don't have with me today. **Edit** Youtube video is now up, check the next post down. **edit X2** Have you looked into the menu builder at all? - http://netbootdisk.com/forums/viewforum.php?f=4

I was also going to suggest netbootdisk. Has the most NIC support + you can use it with anything that boots MS DOS (Ghost / Acronis / Altiris / etc.)

Agreed. However what OS are you attempting to push? 7?

Version 0.28 ------------ Release date: September 28th, 2009 *Updated Kernel to version 2.6.31.1 *Fixed issue with multicasting a mutli-part image for windows 7 *Added ajax based active task listing *Added nombr kernel option which will not blow away mbr (Thanks Line Noise) *If storage node MAX_CLIENTS is set to 0, it is no longer a random candidate. *Updated syslinux to version 3.82 *Added client information to pxe menu. *Installation script checks if it is being run as root. *Fixed tftp installation to NOT overwrite customizations. *Fixed HD information on hardware info page (2857507). *Added ability to add custom PXE menu items. *Decreased loading time for login page. *Fixed typo in tasks.advanced.include.php *Replaced append argument "quiet" with loglevel=4 *Added Hidden Menu option to PXE Menu builder *Added primary group to host quick info section. (Thanks sam wilson) Seems like some pretty nice changes. Especially the PXE menu items (which I have been having to manually edit for awhile) I'm building the new version on my VMWare server and testing it out. I'll have screen shots of the changes by lunch today + a review.

You are going to want to get a full oem install disk to reinstall xp (use the SLP method with oembios files) There is no need to change your windows xp product key if you use SLP for your setup. This requires that you have the proper licenses for your hardware and that you follow all the rules on M$ site - Preserving OEM Pre-Activation when Re-installing Windows XP Large oem's do this all the time. No reason why you can't.

p858snake I never said that he shouldn't do that at all. I never said he didn't want to sysprep every pc. Ugh... Please read what I type. As mentioned above... First you install xp and drivers / software / tweaks / etc. Next you make a sysprep.inf using M$ tools and run a mini-setup + reseal which will auto generate a new sid on reboot. Machine shuts down image pc with fog Push image to multiple systems of the same hardware type. Machine reboots and changes name based off of what you have /want. Then reboots and adds system to domain. Good luck

May I suggest checking out the offical Fog documentation as well? It really is well documented when it comes to this kind of thing FOGUserGuide - FOGWiki Knowledge Base - FOGWiki

Nlite + driverpacks don't like to mix well. Make sure you are following the BTS Driverpacks examples letter for letter. I do know for a fact that you can combine Nlite + driver packs + oemscan (oembios) + xp power packer. Read up on it here - Siginet Software Forums - Powered by vBulletin btw. Nlite is powerful in of itself... but is bad ju ju when mixed incorrectly with other software at times.