ssx4life

I'm more than happy with helping you out on this one. The best solution I have for you is to repackage the installer as an .msi or check to see what command line switches are available to make it fully silent. (either .msi and commands or .exe and .mst) Also look into app deploy's packager... which is free - AppDeploy.com - The Application Deployment Information Center I use appdeploy as a resource when it comes to installing updates and packing + installing applications which can well... be a bit of a pain in the butt. If you have any application that is "larger" in nature I suggest looking into SFX Maker to package the final contents of the installer and make it a single stand-alone .exe that can be uploaded to the fog snapins. Check my video's on youtube for a guide on how to do this - YouTube - Kanal von SSX4life **edit** Is this software by chance freeware or open source? Any chance I could take a look at the installer for you to see what might be possible with this application for you? If not that's fine, just trying to help

It is either a driver issue or a server issue (sorry for being so vague). What NIC and chipsets come with those Samsungs?

did you do the Ubuntu prep for Fog after it was installed? Sounds like you didn't set the password for TFTP and Default Storage (do this first) FOGUserGuide - FOGProject Wiki and then set the TFTP passwords. Look under Known Issues - Ubuntu 9.04 - FOGProject Wiki fyi the default password for the TFTP server / PXE password / and Storage Node is "password"

What hardware are you trying to pull down What kernel are you using What version of fog are you running?

Well said Sted. There are many ways to skin the cat.

There are several options variable for you....... but the best is to use a VFD to make an .iso with Nero. Universal TCP/IP Network Bootdisk :: View topic - So you don't have a floppy drive? I suggest that you hit up the forums for more help. There are lots of great resources out there on how to automate this process for you, and overall... make your life a lot easier.

Have you thought about using a slightly different method to image the E6400's ? What about using netbootdisk and mapping a drive in MS-Dos and then running Ghost from there? NetBootDisk.com - The Universal TCP/IP Network Bootdisk for M$ Networks I also have documentation on how to do this -

You can specify unique kernel's to computer models if one model is being finicky. This is done though the web console, but requires that you rename your kenel to something slightly different. Let me know if you need more help.

As others have stated, please re-encrypt your AD password with fogcrypt - FOGUserGuide - FOGProject Wiki

There could be a few things here, let me bullet point them first and talk about them as I go along here. #1. Your new image may have a different set of oembios files included in the unit #2. Did you apply any bios updates on the pc since it has been imaged #3. Did you just apply windows updates, or did you change any other hardware out? #4. When you "recaptured" the image did you reset the initial grace period? Did you do a -mini -reseal option? What options did you choose? The first thing to check when it comes systems not passing WGA after sysprep is to look at the base unit and determine which of the 3 parts of SLP 1.0 is busted. We know that your hardware hasn't changed (other than perhaps a bios update, but I doubt you did that). That means either the key is invalid, you forgot to reseal the image properly, or you have the wrong oembios files in the System32 directory. Do me a favor and please run Microsoft's MGADIAG and paste the results here. By default it blots out the key, so you should be fine. Link here - http://www.google.com/url?sa=t&source=web&ct=res&cd=1&ved=0CBUQFjAA&url=http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D52012&ei=PxL8S6DcA5DCMana2KgB&usg=AFQjCNH5Zcs6VID448dqfDkoyf9nzmkx7w&sig2=9NlVVAMU0E8HdZU85ltbAA The second thing to check is your computer's bios CRC check, to validate / make sure that you are using the correct oembios files on your install image. You can check this by running this tool - The Windows XP OEMBIOS Archive It will output a CRC= field and it should be 700A8481 or 717B6EF3 if you are running an acer system. What I would do in your situation is download oemscan and run it on one of the affected boxes. This is the easiest fix going forward..... it will verify your bios and apply the proper files to the system. You can download oemscan here - OEMSCAN_ADDON_MULTIOEM v1.8 - Siginet Software Forums You can download the oembios files here - OEMBIOS Repository There are really good directions on oemscan (I helped write em at one point). If you need help let me know. Once you run oemscan and it finds the correct files and inserts them into your system, restart the box and re-run mgadiag.exe I know that SLP 2.0 and SLP 2.1 hardware is backwards compatible with SLP 1.0 (the bios contain strings that activate XP and Vista depending on the hardware and COA compliance you have. Going forward.... I would check your image, it sounds like something did not get re-sealed properly, or you have the wrong oembios files in your image. Both can be easily fixed, and you can even write a snapin for Fog to push the changes to the computers if you need (write a snapin for oemscan). Hope this helps

They are doing a good job of joining kernels together and improving hardware support.... overall I'm very impressed. I've got less hardware interruptions on the Dell 960's and a speed boost as well when multicasting. Remember that one kernel may not be the magic bullet, and that some models will require custom kernels once they are PXE booted, or entered manually via the .CSV Don't forget to take 2 minutes of your time and update the hardware compatibility list on the wiki - http://www.fogproject.org/wiki/index.php?title=WorkingDevices

Start your downloading! Post your results and comments here

I have more information on this going back as well - [Other] OEM Disks? - dslreports.com Again as always... if you need more help let me know.

Royalty keys are the term used by Microsoft when referring to public OEM keys that are specifically designed to correlate with OEM Hardware and OEM Bios files from large manufacturers. They are also known as SLP keys FYI (System Lock Preinstallation... and they they are also used in downgrade rights - http://download.microsoft.com/download/5/f/4/5f4c83d3-833e-4f11-8cbd-699b0c164182/royaltyoemreferencesheet.pdf I can't link to any royalty keys other than those provided by Microsoft - Preserving OEM Pre-Activation when Re-installing Windows XP Personally I use Fog to re-image client computers. It only works on systems that are OEM and came with the proper COA licensing. If it's home / MCE2K5 / etc. I use my custom DVD installs of Windows XP (XP + SP3 + Driverpacks + oemscan). You can also use FOG (or any imaging software for that matter) to specify a unique windows key on each installation. The easiest way to do this would be to leave the key out of the sysprep answer file so you must type it in manually (which can be a pain in the @ss). You could also write a bart PE script to push a unique .INF based off the service tag / serial # of the unit. But depending on the number of systems you have it can be daunting and also a bit redundant (unless you are not using OEM keys / VLK keys ). Depending on what you want to accomplish there are several ways to get you there. Hope that clears somethings up for you =)

Thanks for the kind word I have been out of the loop for the last 6 months or so due to school, but I'm now done and have some free time to dedicate towards documentation / etc. I haven't spoken with microleaks recently, so I can't comment on if 0.29 is compatible with Ubuntu 10.04, but based off previous releases it will be fixed to make it work with the newer releases. Feel free ask any questions, I'll do my best to help out. I'm not sure if anyone else is going to techfeast in Illinois, but I hope to attend this year.

I think the issue is that Fog 0.28 was released before the switch to 10.04 on Ubuntu. I would hold off until 0.29 comes out and try it then.

yes this is entirely normal. Fog uses compression, so in the upload process it is shrinking the image and uploading it as it goes. The reverse takes less time to process. Glad to see you got it working properly.

Hi, welcome to edugeek.net! =) Deploying Windows XP to multiple machines and different hardware types is possible, you just need to get pointed in the right direction. Personally I suggest reading up on Michael Votaw's XP guide - COE Exchange: Imaging Windows Machines with Sysprep Mike does a good job with the basics, but I would take it one step further! =) #1. Use Sysprep Driver Scanner to load ONLY mass storage drivers into the sysprep setup. (use driverpacks mass storage driver set... see the link in #2) #2. Use Driverpacks (News | DriverPacks.net) for all other drivers. (I still don't load chipset drivers in sysprep due to too many issues with Dell hardware... but I blame Dell for that) #3. Make sure you are staying within the terms and conditions of your EULA from M$. This means using either a VLK license for XP or using Royalty Keys on ONLY oem hardware that came with the came version of XP (COA) Image the system with your favorite imaging software, I still prefer to use FOG... but that's a bit advanced. If you need more help let me know.

Looking at those ranges it does appear to be correct. But I can't say for certain unless I had more information on your network =) As far as adding a second hdd for fog it is very easy to do! FOGUserGuide - FOGProject Wiki That should point you in the right direction. =) Let me know if you need more help

I think I found the root cause of my issues. If the field is null (in the smbios) then it can't apply the field! I was running the script (change name + reboot) on a Dell that had the motherboard replaced. It looks like the tech forgot set the service tag in the bios so it was blank (hense why it failed). I booted up my copy of the dell technician's bios rom CD and manually set the bios field (i'm WPD certified so I am allowed to have one of these). All is fixed now.

We use Spiceworks. It's free and works great.

My apologies in advance for bringing this thread back from the grave, but I can't seem to get the script to work on some of my new computer systems at work. It works fine on the older units but not the new ones! (mostly dell's) Anyone have a new version of this script? Am I missing something?

everyone has a different network setup and configuration. I am by no means an expert, but I can at least point you in the right direction. For testing purposes please download the Fog VM (0.27). I suggest running it on a system that has at LEAST 4gb of memory (2 for the OS and 2 GB for FOG). Check my VM guide here - Installation on VMWare 0.27 - FOGWiki Don't forget that on your WINDOWS machine you will be using a bridged connection, so the IP address of your windows box is the same as your fog box. It also helps as stated earlier to have a reservation set prior to running FOG so it can be easily configured. VM is a little bit crazier because you have no GUI (if you are new to linux), but the nice thing is that all the needed files are already installed on the image so you don't need to connect to the internet to download any files (especially since you are behind a proxy which is a pain). Lemme know how it goes later. --ssx--

I'm willing to bet that I can set ya straight. The FOG guide needs to be rebuilt from the ground up due to it being outdated. Please do me a favor and give it one more shot.... but with a few tweaks. #1. Download the DESKTOP version of Ubuntu 9.10 not the server Another thing to note is that if your network currently allows for mac address reservations you can completely skip this step. =) It's even easier if you are having some other device handle DHCP (windows server or router) #2. If you do not have mac address based DHCP reservations that's fine. The desktop version uses a GUI that is much more friendly. Install Ubuntu Install Updates Set a static IP address - (it's hard to see / follow this guide, but he does go through manually setting a static IP for the server) Install FOG and set the proper gateway / IP / etc. (again this is easier when you have DHCP reservations based off of mac address) I'll be happy to help you further if you wish to pick the project up again. You might also be better off downloading the fog VM (0.27) to play around with. I actually wrote the setup and configuration guide for the VM =) Let me know if you need more help (and to the community, we are aware that we need new documentation, so please join our wiki and help us out!) --ssx--

It could be a number of issues you are running into (most likely driver related). Just a couple of quick questions for you What version of XP are you running sysprep on (XP Pro OEM / VLK / etc.) Are you making an HII (hardware independent image) How many model computers are you wanting to support (relates to question #2) and do you plan on having an individual image per model? Are you trying to integrate any drivers into your sysprep.inf ? Can you please post your .inf (don't forget to X out the key) I'll take a look and see what I can do for you.