/build/static/layout/Breadcrumb_cap_w.png

Sysprep Wizard & Windows 10

When working with Win7, I would move the executor and the unattend to System32\sysprep\, create a shortcut for the executor that I would place on my desktop, and then run it from there.

Now, I'm using the latest Dell Sysprep Creator for preparation of my first Windows 10 testing image. Following the same steps as outlined above, I would get "windows could not parse or process unattend answer file the specified file does not exist" and I was almost going to post a HELP ME!!! post, but I instead just let it run from the desktop, where it placed it by default.

Sysprep finished, shut down, and I'm currently capturing the image.

But is that normal, or do most people just run it from the desktop in the first place?

And lastly, and just a bit of a rant, is it just me or is the search function on ITNinja horrible? I tried searching Windows 10 & sysprep in a variety of ways, but got pages of results that had absolutely nothing to do with it.

Same if I clicked on the suggested tag/search for "sysprep." Just random results.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: StockTrader 8 years ago
Red Belt
1
A short suggestion...Keep it simple! Run it from the desktop.
Anyway the executor will ''self destruct'' and Sysprep.exe will consume the XML file and remove it from the desktop.
 Kind regards,
Marco - StockTrader
Posted by: SMal.tmcc 8 years ago
Red Belt
1
since I copy my profile to default I still keep the win10 answer file in ..\system32\sysprep and call it with a batch file that is placed in a directory included in the search path.  So when I am ready to sysprep my master I right click on start and click on run type the batch file name in and hit enter.

Note: my batch file does some last second reg deletes and adds an entry to the registry to help us identify the exact image version thru the k1000 software inventory automatically just before calling sysprep.exe

Comments:
  • What kind of deletes are you doing and are they related to included Win10 packages?

    I read about deleting certain packages, like the Windows Store and others, because I really don't want to give my users too many options that I may have to deal with down the road in future migrations or like for like machine replacements.

    Also, if I may ask, how have you dealt with user state migrations? I have two issues currently.

    1. With USMT 10, though I can capture the .MIG in Win7, I cannot redeploy it to another Win7 machine. Easy Transfer says it cannot open the file, despite have a flag in my template for /targetWindows7.

    2. Win10 does not have Easy Transfer at all, it seems. How are admins getting around this problem of using Kace to capture and deploy user states into Win10? - rskwire 8 years ago
    • I delete SUS keys and policy keys plus a few others related to location. See my other ans for link on store apps - SMal.tmcc 8 years ago
Posted by: SMal.tmcc 8 years ago
Red Belt
1
For migration We use the easy transfer yet.  You can steal it from a win7 machine and use it on you win 10 machines.   You need both of these directories ..\system32\migwiz and ..\system32\migration.  Then run the migwiz.exe found in the migwiz directory.

for the store apps see this blog

http://www.itninja.com/blog/view/windows-10-deployment-re-adds-bloatware-tips-and-tricks-to-help-get-rid-of

Comments:
  • We use the k1000 scripts to collect the migration files from the old machines and use the migwiz to place them on the new machines. - SMal.tmcc 8 years ago
    • But could I just zip those files up and use it as a post-install? - rskwire 8 years ago
      • our techs are running migwiz off usb sticks currently, so I would say yes you can. I am testing an updated Win10 image with the files in the same place as they were with win7 and add the migwiz directory to the win10 search path. - SMal.tmcc 8 years ago
      • And you replacing those files (Win7->Win10) or just storing them elsewhere?

        I'm having trouble deleting the WIn10 folders, so looking into that now. - rskwire 8 years ago
      • look at the takeownership.zip i mention in the blog. Just uninstall it prior to sysprep so it is not there for the users to find - SMal.tmcc 8 years ago
    • Is there a trick to this? Or simply swap out the migwiz and migration folders in Win10 with the ones from Win7?

      I did that, using the Take Ownership reg (thank you), Easy Transfer loads, but it still fails on the .MIG file. Actually, it looks like the MIG file itself doesn't have a file association.

      Possible culprit?

      EDIT: I set the file association with Easy Transfer, on Win10, and now it throws the error: "Unknown error loading Windows Easy Transfer. - rskwire 8 years ago
      • did you use the win7 easy tranfers to create the mig file? - SMal.tmcc 8 years ago
      • No, captured it from Kace, and then downloaded it from there. - rskwire 8 years ago
      • which usmt did you use? - SMal.tmcc 8 years ago
      • usmt 10 - rskwire 8 years ago
      • you need usmt 5 for this to work - SMal.tmcc 8 years ago
      • Is it possible to uninstall USMT 10 and go back to 5?

        I tried just uploading USMT 5 back to the kbox and I still have 10. - rskwire 8 years ago
Posted by: SMal.tmcc 8 years ago
Red Belt
0
They do know the built in search function is lacking in some capabilities.  Best thing to do is search google and always include "itninja" in the search criteria.

Windows 10 sysprep itninja

https://www.google.com/search?q=Sysprep+Wizard+%26+Windows+10+itninja&ie=utf-8&oe=utf-8#q=Windows+10++sysprep+itninja

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ