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.

[quote=“Thomas Rucker, post: 40196, member: 1970”]So, it’s not the GPT or MBR, but FOG has a limitation, because of how Lenovo loads their machines.

I guess I have to live with the RAW image then, correct.

I have to say, it works very well, but it’s very slow, thank you for your thoughts.[/quote]

If you have 6 primary partitions it’s GPT.

[url]http://en.wikipedia.org/wiki/GUID_Partition_Table[/url]

Still did not work. What is odd is that the image was working just fine until I set up fog correctly for renaming the computer and joining it to the domain. Kaspersky is not even attempting to install. It just skips right over it and goes straight into windows. I am at a loss. Need a day to think.

Thanks, that seems to have fixed it.

Since Fog uses several servers and other components that use usernames and passwords, and since it seems that the installation script doesn’t set them all correctly, is there any documentation for Fog that explains how to set them all up correctly?

Hah! I tried your command and got the error Host is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’.

We ran that and voila! Our FOG server is back.

You guys are truly wonderful.

Tom, sorry if this confused you. The initial set up was already tested on local (Ubuntu 13.10 VM) and was working. nothing really has changed besides putting the master Node on a freenas (with FTP & NFS) and giving full control of the loaction to the fog user (which was put as the user to use in the node management on the GUI)

Since then, everything is still working fine, comunication between Fog and the node is fine, image uploads are going to the dev folder then after upload is finished it’s being transfered to the main /images folder. the ONLY issue is whenever we try to proceed a download from the host management page, it fails automatically giving out the error I posted above. BUT using the quick download from the host list in task management works.

Do you need more information?