[quote=“Lee Rowlett, post: 40352, member: 28”]put it this way, we have 2500 Devices, 23 different models (yes 23!! don’t ask, serious just don’t ask!) 18 sites “large” sites across the stretch of the country (UK) and we can rebuild a machine (with all the software, bells, whistles you name it + more) in under 15 minutes, regardless of what site and it only takes a minute of an engineers time to do (less if device is registered)
just kick it off and check webgui in 15 mins or so.
[/quote]

23 doesn’t sound bad at all to me. we have 33 models in the 800 or so machines currently in fog

Hi Tom,

As it turns out, the problem was a self inflicted wound. Our Apple guy also has ain image server running. He turned it on the other day. I noticed in the logs that the system would ask for an address first from the FOG server and then from the Apple image server immediately after that. It would then invariably die while trying to connect to the Apple server. I unplugged then network card on the apple box and stuff started working again.

Thanks for the help!

John

Finally works.

sudo service ufw disable edit in /etc/dhcp/dhcpd.conf filename from “undionly.kpxe” to “ipxe.pxe” sudo service isc-dhcp-server restart changed from Realtek to Intel 1000 Desktop in Network option Virtualbox
Thank you Tom and jbsclm

You brilliant bastard!

Hah, thanks for the help.
Again… sorry for the noobishness

(summary of resolution)

Edit the /etc/vsftpd.conf and append: seccomp_sandbox=NO and restart the service (sudo service vsftpd restart) Adding password to storage node in the gui Rebooting Fixing schema table with “sudo dpkg-reconfigure mysql-server-5.5” Retry upload tasks

----it now uploads and makes the appropriate folder in IMAGES as intended and not the “dev” folder; aka, it’s working again!!!----

THANKS!!!

That’s actually not bad idea at all, so my main VM OS, (ubuntu) would be on the same VLAN as my main computer. I can use the usb/nic adapter as the second adapter only on linux have have fog on it’s own isolated LAN. The problem is I’m bound to run into many issues with this, but it can be done

You’re right on that, I’ll just use clonezilla live to burn ISO images to use

I still don’t see a reason to sysprep. Why would I want to pre-install the drivers if the drivers are fully loaded already? Every time I have imaged with Fog, I have used syspreped images only because I was taught to do so. However I know a couple of colleagues that do not sysprep at all, yet let me know the biggest problem I would run into is ip conflicts if I’m not careful. (Also told me to make sure the images are obviously not on the domain with the same domain name)

Now for OEM manfucaturer licensing, the laptops coming in all have their own individual license. If I sysprep a laptop, clone it, then deploy it onto another, I will not have an active license. This is going to be my biggest issue and will involve a lot of research, hopefully someone here can point me in the right direction.

No worries about the aircard, I honestly think I’m just going to be activating the air-cards after the imaging.

And for your last paragraph, I as well have colleagues that said it was fine minus the matching dhcp leases and having to change the hostname before joining to a domain.

Thanks Eddie

If you’re running windows7sysprep, but this is setup for Multi-Partition (Non-resizable), I only have one guess as to why your image isn’t deploying. That guess is the disk you’re attempting to push to is smaller than the disk this image was created from.

there is no error - uploads fine etc - only go to images and no image - but in the DEV folder it’s clearly sat there and not processed properly to a folder name in the /images. Thanks

This is the full error that I am getting “could not start download operation not supported”. I am using an intel network card on HP machines. It use to work but now I can’t even get the FOG screen.

the /images location that is hardcoded in fog.upload is just the name of where it has mounted the storage location to in fog.checkin

I’m telling you, it’s already setup in 1.2.0.

Looks like the problem was PEBKAC (seriously I feel like an idiot haha). I had so many Ethernet cables across my desk and didn’t realize one of them was hooked through a 10/100 interface. When I took the original image I was connected to the 10/100 but when I swapped with the HDD I plugged it back into a GigE port. My bad on that.

For what it’s worth it’s blazing fast across the board again 😄

[quote=“TonyB.2871, post: 40293, member: 26980”]Just curious as we were able to image fine on 1.2.0 for quite some time up until recently. I know there was a minor network infrastructure change, but nothing that should have affected the Fog server’s functionality. Given I can access it via HTTP, TFTP, etc… and that it worked before, Im slightly confused why we need to upgrade.[/quote]

Hi,

No new hardware ? : switchs, computers, …
Your server is virtual ?

Regards,
Ch3i.

that worked. i had it set to partimage and switching it to partclone fixed the issue. thanks.

Issue resolved.
Dont ask me how but I tried with two different systems and Ive been able to restore them

I started from scratch this morning, paying extra attention to the proxy dhcp setup process, and it now seems to be working as it should. Have successfully uploaded and multicasted an image. Thanks for your help.

yes it is.

Thanks tried that first part as fix but not the second. Just updated. Thanks, hopefully do the trick. :_)

I’ll see if I can borrow one of our school’s raspberry pi, and see if I can sort this out.

That said, all I’d be testing is the installer and the services to get started, but I would not recommend using it to actually image systems. This is just my thoughts. The Pi is not a very powerful system. While I’m sure it will do what you want, it wouldn’t necessarily be the “best” method to do a “mobile” solution either.

Same thing happens on Lenovo R500’s and Lenovo R61’s. Changed AHCI to compatibility. Its a known issue and its related directly with the hardware and BIOS. This will affect any install of Windows, ghosting, Acronis True Image and FOG. Sorry but not a FOG issue.