Posts made by ssx4life

example (see attachment)

[url=“/_imported_xf_attachments/0/115_Windows XP Professional OEM Movie003.zip?:”]Windows XP Professional OEM Movie003.zip[/url]

by booting into debug mode, it will check the NIC and hardware to see if the kernel is compliant

It may be an issue with your kernel not supporting your new hardware. Can you please boot into debug mode and see if your NIC and chipset are supported?

It would increase network traffic, but when testing this with wireshark on my network I didn’t notice too much of an increase in overall traffic.

The pro’s of having this solution is reduced image and deployment time. The con’s being a slight increase in overall network traffic (but marginal on a 450 - 500 networked system here at work.

Let me know what you find in your overall network traffic, I’m curious.

thanks.

Currently you can change the .ini file on the client side to force a reboot if there is an imaging task scheduled. You could also script your standard packages with a .vbs to auto log off + execute.

Just a thought.

I’ll also point out that if your HP’s have a smaller HDD size / space than your image it can cause this issue - [url]http://www.edugeek.net/forums/o-s-deployment/61445-dell-e6410-fog.html[/url]

Just to confirm you are [B]PUSHING[/B] the image to the 4000 sff? Is this a standard windows 7 image (100mb partition + ntfs non resizable)

I helped someone on edugeek.net with a similar issue - [url]http://www.edugeek.net/forums/o-s-deployment/61956-fog-client-error-cant-have-partition-outside-disk.html[/url] . Long story short… there was a partition table that couldn’t be read by fog, so wiping the drive allowed it to be imaged.

Have you tried to run a debug mode test on these models in the PXE menu?

Check to see if the NIC / mass storage controller is currently supported in your kernel release.

There has been some early testing on v 12 but nothing offically supported yet. Version 0.32 came out around the time (and was supported by) 10 and 11. I don’t think 12 works out of the box with 0.32, but I’m sure it will with 0.33.

More info on testing with the latest version of Fedora and Ubuntu can be found on the Dev forum.

Windows XP / Vista or 7?

You can use OPA Tool + an SLP key just fine (and the oem media) with fog.

OPA Tool - [url]http://bit.ly/KtpKua[/url]

If you haven’t yet, make sure you click on the storage nodes icon in the web ui (at the main ui page) and go update the password there.

I’m using a modified snapinclient.dll so it checks in after 20 seconds. [url]http://fogproject.org/forum/threads/how-to-modify-your-snapinclient-dll-file-to-check-in-more-quickly-on-a-reboot.613/[/url]

The real benefit of having the drivers be OUTSIDE of the base image, and why I mentioned it is because Andrew is running into issues with some model computers getting the wrong drivers due to them having similar hardware.

If you separate the drivers from the base OS it gives you the flexibility to add new driver models quickly, the only issue comes in again if you have a NIC that isn’t supported. This would require you to either rebuild your OS image or manually install the driver and continue on with the standard imaging process.

As far as storage size it also cuts down on it due to only pushing the drivers specifically needed for that model. It’s not the best solution, but again I’m trying to find a solution for him based off of his issues with the wrong model getting the wrong driver, this alleviates that.

I was just trying to think outside the box for a solution on this one.

I personally am using this method for Windows XP, but for Windows 7 we have the drivers as part of the image.

The benefit of having them be part of the image again is that they are all auto run and found during installation. I just need to make sure my windows 7 images are built virtually so I can go back into auto mode and add / modify the drivers based off of future hardware.

Have you gone through and updated your TFTP password and default storage password after you installed FOG?

What OS flavor are you running FOG on.

My above statement doesn’t include any drivers into the windows installation, my suggestion was to build a snapin for post imaging that is pushed to the client computer after it has gone through the preboot / sysprep process.

you are correct on the NIC drivers and future models however. There is no quick and easy solution to this, other than have your windows 7 images be built in a VM that you can quickly snapshot to, and re-upload to the fog server.

To pile on here you can also modify the SAD2 script to push only the OEM drivers that came with the pc. I’ve done this for several models.

Simply use method 2 for the driver installation and make a new folder called D / 3 / YOUR DRIVER FOLDER HERE.

Simply copy the oem drivers from an untouched / factory image pc for windows 7 and drop them there. Then use SFX Maker to encapsulate the SAD2 script, and have it auto run the .cmd upon execution.

Now simply use a the .exe as a snapin so you push windows 7 with minimal drivers, and push only the specific drivers for that model to the unit.

It cuts down on overall windows image size, speeds up imaging and deployment, etc.

Again, use method ONE for this. I’ve copied and pasted the readme.txt file. Let me know if you need more help. You are basically not using the pre-built driverpacks and building your own based off of your office / work setting.

[LEFT][I]What goes where?[/I][/LEFT]
[LEFT] [/LEFT]
[LEFT][I]NT5\x86[/I][/LEFT]
[LEFT][I]-Method-1: Use DriverPacks BASE to create a Method-1 SAD disc selecting the packs you want to include. By default, the folder “DriverPacks.net” will be created in C:.[/I][/LEFT]
[LEFT][I]Copy the contents of that DriverPacks.net folder to this folder so that the folder heirarchy looks like this: \NT5\x86\D.[/I][/LEFT]
[LEFT][I]-Method-2 (preferred): 32-bit Win XP/2000/2003 DriverPacks go here in their compressed state. An empty “Example” DriverPack is included for reference. Method 2 will fail if the \NT5\x86\D\ folder exists here, only .7z packs must be present.[/I][/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT][I]NT6\x64[/I][/LEFT]
[LEFT][I]-Method-1: Extract the contents of all DriverPacks to the NT6\x64\D\ folder so that the folder heirarchy looks like this: \NT6\x64\D*. Method 1 will fail if the \NT6\x64\ folder contains any .7z DriverPacks.[/I][/LEFT]
[LEFT][I]-Method-2 (preferred): 64-bit Vista/Win7 DriverPacks go here in their compressed state. An empty “Example” DriverPack is included for reference. Method 2 will fail if the \NT6\x64\D\ folder exists here, only .7z packs must be present.[/I][/LEFT]
[LEFT] [/LEFT]
[LEFT][I]NT6\x86[/I][/LEFT]
[LEFT][I]-Method-1: Extract the contents of all DriverPacks to the NT6\x86\D\ folder so that the folder heirarchy looks like this: \NT6\x86\D*. Method 1 will fail if the \NT6\x86\ folder contains any .7z DriverPacks.[/I][/LEFT]
[LEFT][I]-Method-2 (preferred): 32-bit Vista/Win7 DriverPacks go here in their compressed state. An empty “Example” DriverPack is included for reference. Method 2 will fail if the \NT6\x86\D\ folder exists here, only .7z packs must be present.[/I][/LEFT]

Is the client computer registered on the fog server?

FWIW the user guide for setting up fog on VM Ware is the same as Virtual Box, the only difference is as Teena pointed out. Make sure that you bridge the connections.

I also would suggest using Ubuntu 10.X vs. 11 (11 just didn’t work well for me). I use 10.X desktop due to wanting to have a GUI.

Let me know if you have any other questions or need help

tnoble no problem

FYI I just tested the 0.27 image in Virtual Box and it works great.

Works just fine on my end, and you can quickly upgrade to .032 to test things out.

enjoy

Tnoble I had some time to think about your request over lunch today and instead of re-creating the wheel, have you thought about converting one of the pre-supplied vmware images over to virtualbox? We currently have a VM of 0.29 on sourceforge that should be able to be converted over to virtualbox for you.

I think the VM’s are all x86, and to be honest I haven’t noticed too much of a performance increase or change in overall speed and issues between both distro’s (both ubuntu). Try converting one of the VM’s first - [url]http://zeldor.biz/2010/12/convert-vmware-image-vmdk-to-virtualbox-image-vdi/[/url]

edit
Here is the 0.27 release of fog on sf (which is upgradable) - [url]http://sourceforge.net/projects/freeghost/files/FOG_VM/fog_vm_0.27/[/url]

If I get time I’ll try to throw something together.

In the interim if you could please provide us (the community) with some more information on how your network is set up (VLAN / layer 2 / etc.), what types of equipment you are running, what type of hardware you are running, and what OS you are wanting to image / capture / and deploy. The more information we have on your specific situation the better we can help make sure things get up and running.

Work has got me extremely tied down, but it doesn’t mean I don’t reply to email or the forums, but throwing a quick video together is possible by me… just takes well… time ^_^

Thanks.