Windows 10: Customize Windows 10 Image in Audit Mode with Sysprep

Is it possible to add a HirenBoot & Active Boot Disk Suite LiveCD as Partitation into the Original Sysprep version.
What I mean example:
- C:\ Drive = Microsoft Windows 10 Enterprise X64.
- D:\ Drive Partitation from C:\ = HirenBoot.
- E:\ Drive Partitation from C:\ = Active Boot Disk Suite LiveCD.
And sysprep all the thing as one .wim file.
And if you boot into it you get a Custom Menu:
1. Microsoft Windows 10 Enterprise.
2. HirenBoot.
3. Active Boot Disk Suite LiveCD.
Is it possible to make this with EasyBCD or something else? *Wink

P.S. If it is possible can it also work above but then with multiple Windows example add Windows 8.1 or Windows 7.

Or does this only work as a Computer Full Back-Up, or is this not possible?

 

By following this guide, I could create a custom installation DVD working on any type of computer that, during the normal process of installation of each edition of Windows 10, also allows to create a partition to save the profiles of users? If so, how do I do this using only the Microsoft tools?

Thanks

Bye

 

Nice!

Looks like sysprep and Audit mode remain unchanged, good to have a rundown for 10, this is excellent!

Have you figured out if CopyProfile works in the latest build? I'm going to start cooking my custom 10 image here pretty shortly, hate to have to go through the trial and error like I did to figure out how to get the Start Screen customized.... Ugh.... Just remembered I'm back to square one with 10 and syncing over the Start Screen layout. Balls.

 

GOOD! That was annoying to run updates in 8.1 in Audit mode through PowerShell! *Mad

 

Depending on what you install and how you customize it, yes you can create a DVD install media with a custom image real easy. You would go through Audit mode and all listed in this tutorial. To author the DVD, you'd need a program called ImgBurn, there's a tutorial of how to make a bootable DVD of Windows that will work for 10, even though it's for Windows 7. This won't save partition info, but I THINK there's a way to run a command during sysprep to do that... Not sure.

Also, depending on the install.wim file size, if it's like over 4 gigs (in my custom images of Windows 8.1, the latest one I cooked was about 14 gigs!) it won't work on a UEFI BIOS PC because the USB drive needs to be formatted in FAT32 and there's a file size limit with that. There's a workaround to that, but just so you're aware.

 

There is a new Microsoft tool (part of the ADK download mentioned in this tutorial) called the Windows Imaging and Configuration Designer.

I haven't explored it fully yet, but it looks to be powerful, and includes a function to create Clean Install Media of your customised build, directly onto a USB drive.

I suspect it won't let you customise partitions directly. However you might be able to customise the partitions using the media it produces and using or changing a diskpart script.

Or you could do something like this and edit the diskpart script to create an extra partition:
https://msdn.microsoft.com/en-us/lib...=vs.85%29.aspx

 

Hi Kari,
Since the final version is out, is it possible to update this to final as well?
*Smile

 

I am working on it. Basically there's very little to update, just to check if warnings and workarounds are still needed. I have been testing all the time, not posting any changes until I am sure of the results.

 

I think I may be running into this. I boot to audit mode, make configurations, run Sysprep command including the generalize switch, point to an unattend.xml with copy profile true. When the OS deploys on to a system everything looks great, the copy profile looks to have worked; except the search bar is unresponsive, can't type or click, it's totally dead, no search no Cortana just looks like a broken place holder. Deployed to multiple clients same result. Any thoughts on ways around this?

 

Have you tested without an unattend file?

So far, I haven't tested with an unattend file, and I haven't had the issue you are describing when generalizing with Sysprep. I'm just wondering if it's the unattend file (or more likely, a setting in the unattend file) that's causing this. If you can narrow it down, you should submit it via the Feedback app for sure.

 

Hi Kman, welcome to the Ten Forums.

What kind of users on those clients? Local, domain, Azure AD or MS account? If local or MSA, is the PC later on joined to Azure AD?

 

Not joined to Azure AD, just to our regular domain through SCCM task sequence. No other local accounts created, just Administrator.