Error returned type 2 after deploy

[Aurel]

Server

• FOG Version: 1.3.4
• OS: Debian 8

Client

• Service Version: 0.11.9
• OS: WIndows 7 X64

Description

Hi all,

When I deploy an image on a windows 7 client with a pre-sysprep , after this deploy, I have the message “error returned type 2 …”

I don’t understand why I have this error on a pre-sysprep image and I have not this error with a classic image.

[Wayne Workman]

Where are you seeing the error? When windows tries to boot? Before then? During imaging? When the system is trying to network boot? What shows before it? We need more information.

Also, saying “Last” for the client service version doesn’t help us help you, and helps nobody else in the future. Two months (or years) from now if someone reads this they may wish you wrote the version. This is why we have open forums, so people can help themselves with reading past threads.

[Aurel]

Hi,

This screen displayed at the end of image deploy. My Windows image deploying correctly, at the end, this screen appear and after few seconds, windows launch normaly. This is not blocking after deploy.

I noticed this error appear with an image pre-sysprep. That is, sysprep is launched with the shutdown mode before image capture. When the computer is down, I boot on the pxe to begin image capture.

[george1421]

@Aurel said in Error returned type 2 after deploy:

I noticed this error appear with an image pre-sysprep.

This phrase confuses me. You mean you get “error returned type 2" before you even sysprep the image. At this point FOG is not involved with the process.

That is, sysprep is launched with the shutdown mode before image capture. When the computer is down, I boot on the pxe to begin image capture.

This is the normal process we use to capture reference images.

Maybe you can include a clear picture of the error so we can see the context of where the error occurs.

[Aurel]

@george1421
Hi,

My screen doesn’t work in my first post, I don’t know why.

His the link of my scren : https://ibb.co/cNNCTv

[Tom Elliott]

I typically see this with permissions issues.

Please try running:

sudo chown -R fog:root /images && sudo chmod -R 777 /images

I suspect your capture will work a lot better after this is performed.

[Aurel]

@Tom-Elliott

Oh yes, it’s works with this permission :). Thanks you