Capture is only 2.5MB
-
Have you "watched’ the screens during the capture process?
It seems incredibly odd that you are the only person reporting this problem. A TON of work went into 1.3.5 in regards to resizable images. That said 1.4.0-RC-1 found another issue in regards to aligning the disks, but I’m 99% sure this isn’t the problem you’re seeing either.
Can you watch the system during it’s capture process please? Maybe even capture it in a “debug” mode?
Try to see where, if any, there’s an error?
-
I will try again when I get home from the day job, but the actual imaging part of the process is over before you really get to see much on the screen, the progress bar seems to go from 1% to 100% instantly, then the process continues and the machine restarts/shutsdown depending on the settings etc
-
@KeithDib This is why I ask you to create the tasking in debug.
-
I will do that later today
-
I have ran a capture Debug, and although it looks on the capture machine to be running through the tests the server just sees the task as queued, and stays like that
-
Pictures would really go a long way if you can provide any, or even a video?
-
Also, what is the image defined as in the GUI?
This almost sounds like you have it set to get mbr data only or vsomething.
-
-
@KeithDib said in Capture is only 2.5MB:
0_1491237311506_Windows XP v1.webm
Please retry the upload.
Have your browser in full.
Paste your pic/move.
Look on the right hand side and it will switch from text to media type or pic if that’s what you’re uploading. I got nothing right now
-
-
-
@KeithDib Can we get a screen shot of how you have:
- This target hardware defined in FOG (Host Management -> Host definition)
- For the image referenced in step 1, can you also post a screen shot of the current image definition (Image Management -> image definition).
This would be from the fog web gui
-
Also,
Debug brings you to a command prompt, this is expected.
At the command prompt type:
fogStep through the process, you can grab video or pictures as well.
-
seems to image with the debug running
i have uploaded a couple more videos to same folder, i have cut out the boring parts
-
Are these systems actually 32 bit systems, or are your init’s set to look only at _32 files?
-
It’s XP pro 32bit yeah
-
@KeithDib Not the OS, the Device itself?
-
My host is i7 running Windows 10 pro 64 bit, running virtualbox.
Running FOG on Ubuntu 14.x.x (not in front at the moment for exact version)
VMs are 32bit xp and 64bit win 7
-
@KeithDib So the VM is 32 bit CPU only? The OS doesn’t matter. You can have 64 bit CPU with a 32 bit OS. Sorry if it seems like it should be obvious, but you keep placing the OS as part of it. I don’t care about the OS. Is the system 32 bit?
I’m asking because I’m trying to find out if what you’re seeing is potentially an Architecture issue in the inits. The OS does not tell us the System’s own architecture.
-
It’s 64 bit,
as I say in previous post, an older version of FOG on the pre buit VM has been working fine on same hosts and same VMs
