Windows 10: questions about sysprep

I am trying to work out how to sysprep a machine before taking an image with dism and I'm running into a few questions.

- when I setup this image I did not use audit mode. I thought I could work around this by setting in the unattend.xml to copy the customizations of local profile to default profile. But I keep running into "sysprep was not able to validate your windows installation..." and it always ends up being some app package that was 'installed for a user but not provisioned for all users' How do I get past this issue and is this what audit mode is also meant to help you avoid? I have already tried uninstalling the specific app package in powershell and tried uninstalling all app packages thru powershell via the Get-AppPackage | Remove-AppPackage command and still having same issue.

Also I have turned off bitlocker for this drive to make sure encryption is not enabled. will the /oobe switch for sysprep re-enable bitlocker encryption or do I need to do this manually?

Thanks.

:)

 

SysPrep Advice

Hi Joseph,

The topic that you raised is beyond the scope of support for this site which focuses more on home and personal end users. Here's what I found about SysPrep:

• What Is Sysprep?
• How To Sysprep – Sysprep is a Great And powerful tool And Easy
  Too If You Know How (Step-By-Step).

However these are old articles and the process may have been changed already. You may re-post this question in

TechNet Forums for further assistance.

All the best.

 

Questions regarding sysprep and capture in MDT

I have a question regarding the sysprep and capture function in MDT 2013.

I have done a sysprep & capture on a Windows 10x64 machine with software and drivers included using MDT.

So the next step I did was to deploy the captured .iso file onto a new machine which had the usual configuration steps including setting up the computer name, timezone and keyboard layout etc and everything was start up fine and all the software and drivers were also configured & installed properly.

However, the issue is that machine's SID and computer name were completely the same as the one I ran the sysprep & capture on. Was this supposed to be like this? Because I did some research and a sysprep is supposed to change the SID as it is treated as a new machine. Also, I did configure a new computer name for the machine during the deployment setup but I have no idea why its the same name as the other machine.
I would appreciate any answers given. Thank you.

 

Windows 10 1709 sysprep fail

Hi,

I had the same problem, checked the logs and they basically said Windows was unable to remove the Miracast app.

Tried multiple suggestions, nothing worked until I found this:

Failed to sysprep and capture Windows 10 Fall Creators 1709

Basically Microsoft have pushed out their 1709 image without the Miracast app installed, to fix:

• Copy the C:\Windows\MiracastView folder from a working 1703 build into the C:\Windows directory on the 1709 machine
• Restart and then run sysprep

Sysprep should then run successfully!

Josh