Hi Tom,
I fixed a permission issue I had with the files. However I have found that Fog Server doesn’t relocate the IMAGE file from /images/dev/macaddress to /images/Name-of-Image
If I go into /images/dev/macaddress I see 5 files in there. But I don’t know why they weren’t moved to /images/name-of-image
So when I try to download the image to the host I get a “Cannot find XP Image File” error messages.
Any ideas?
Hi Tom. Finally got to the office and I am able to test. For starters, neither the Full Registration or the Quick Registration are working.
I will try and add the client manually and see if I can image it like that.
Thanks, Tom. I will test this and report back on my findings. I really appreciate you taking the time to do all of this.
Got them. Your server was complaining about the certificate. You should check that out.
Are these files to replace other files in my current installation?
If this is too much, would installing a previous better of FOG would be a better option? I wouldn’t like to do this, as I had a difficult time configuring it the first time around.
Glad you know what the problem is. I’ve been trying to push software guys to move to Win7, but alas that is NOT going to happen anytime soon.
Is there something that could be done? I know you mentioned a possible hack/fix. I would love to try it out.
[quote=“Tom Elliott, post: 37747, member: 7271”]If you enable plugins and install and configure the capone plugin, your auto imaging situation will be complete. YOu simply specify the relevant fields for the image you’re wanting.
As for why the image went wrong, I’m just guessing it’s to do with the XP nature of your system. In 1.2.0 I made many more changes, but forgot to account for the 63s vs. 2048s boot sector and optimal boot sector variants within parted. I’m sorry, but this is what the problem is. I can hack up a quick fix for that problem, and possibly for the one dealing with the image itself. In a way I’m glad that the image isn’t writing to the disk as, in the current state (with the sector problems just described), I’d rather a system fail to image rather than image, but not be bootable.[/quote]
We are deploying about 300+ of the same hardware, and I need to load WinXP on the 300+ machines. This Windows XP has some software preloaded that we will use for testing the machines before shipping out.
I manage to configure my fog server, and I was able to upload an image to the server using a sample of one of the machines. I was unable to download the image back to the machine, I got an error message that said “This is Not a partclone image”. I don’t know what went wrong, I will retest again on Monday. I googled but there is not much information for that error. Anybody here gotten it before?
My other question (related to the title), all these machines are brand new, and they come with NO operating system loaded. The way we handled it before was: connected the machine to an internal network where we had an imaging server. The server would automatically load the default image for that hardware and halt at the end of the imaging process.
The person that was in charge of this system left the company, and took the knowledge with him.
Is it possible to do the same with FOG? I’ve been going around the forums and Google but can’t find an answer.
I know FOG identifies hardware based on the MAC address. How can FOG tell that they are all the same config and autoload the assigned image for that particular hardware version.
At at different point in time there will be other hardware configurations, but for now one single one would be enough.
By the way, I am running FOG on Kubuntu 14.04 VM. It should be the lastest version of FOG