Jump to content

MDT: FAILURE (7002): Computer is a member of a domain, should be in a workgroup


Recommended Posts

Posted

Hi,

 

What I have done is created an image and sysprepped and captured it with WDS. I've then added the WIM to MDT to deploy it. Everything goes well and it looks to have deployed correctly, joins the domain etc but it keeps throwing up this error:

 

FAILURE (7002): Computer is a member of a domain, should be in a workgroup when sysprepping.

Litetouch deployment failed, Return Code = 2147467259 0x80004005

Failed to run the action: Execute Sysprep.

The specified protocol driver is invaled. (Error: 00001B5A; Source: Windows)

The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep: Execution of task sequence failed.

The specified protocol driver is invalid. (Error: 00001B5A; Source: Windows)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

 

I'm not sure what's going on as I'm not trying to execute sysprep again. Any help would be great.

 

Thanks.

Posted
See to me it looks like a problem with the image. When you created the image, did you put it on the domain to configure and then sysprep?
Posted

The reason is because you are trying to sysprep while you are a member of your domain, you need to remove your computer from the domain and add it to a workgroup and then it will work.

 

Hope this helps.

Posted
id try a new task sequence it almost seems to me like its deploying the image and then trying to recapture it for some reason
Posted

It's not part of a domain. Let me try to clear it up.

 

I have a clean windows 10 build, not on the domain, sysprepped and then captured using WDS. I am then deploying this using MDT. I haven't chosen to then sysprep again and neither do I want to. It does look like an issue with the task sequence but I don't know what as I haven't chosen to sysprep and capture at all.

  • 8 months later...
Posted
Sorry to necro this thread, but discovered it while searching and ran into the same problem. Figured out (with info from bald_pig, thanks for that) that I had a imaging section in the deployment task sequence (think its created by default), which was trying todo sysprep after deployment. Removed it and everything worked as expected without errors.
Posted
Sorry to necro this thread, but discovered it while searching and ran into the same problem. Figured out (with info from bald_pig, thanks for that) that I had a imaging section in the deployment task sequence (think its created by default), which was trying todo sysprep after deployment. Removed it and everything worked as expected without errors.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...