Windows 10: Question About Using Sysprep - Third-Party Software Inclusion Into Generalized Image

Hello everyone,


So I just found out about the software, Sysprep, which is used to create a generalized Windows image for deployment on multiple computers.

I'd like to do this but the problem is with the third-party software I want to incorporate into the image.


I desire to include IObit's software IObit Uninstaller, Advanced SystemCare, Driver Booster, etc into the image but I don't know if this is considered

illegally republishing the software. I'm deploying this image to computers that I'm refurbishing and selling off, and not for personal use.


According to IObit's EULA it says:

Section 1. Intellectual Property Rights. ...The Product is only licensed to you, not sold. You may not reproduce, publish, transmit, modify, create derivative works from, publicly display, or publicly perform the Product.

:)

 

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.

 

Windows 10 Update breaks Sysprep?

I am attempting to image a Dell E7470 with Sysprep to upload to my WDS server.

When I run Sysprep /oobe / shutdown, it completes. However, without Generalize, I won't be able to upload it or deploy it.

When I run Sysprep /oobe /generalize / shutdown, it reports that a fatal error has occurred. The setupact.log lists that the Miracastview app cannot be removed.

I have attempted the Remove-appxpackage commands, but it states that it has been provisioned for the user but not all users. It says to attempt removal with Add / Remove Windows features, but it is not listed there.

I have tried the steps in

https://support.microsoft.com/en-us...w-cause-sysprep-error-windows-10-version-1709

but none of this has worked either.

I guess the answer is to not run any Windows updates before Sysprep and avoid 1709? It appears to be bad news.

Anybody else encounter this? Any other solutions available?

 

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.