For what I see, I still ahve to change the settings in the Config.xml file. The migrate option is still set at yes on the latest build.
Are you referring to the config your creating? The samples MS include with scanstate are set to "NO".
I don't use the one provided by M$ but generate one dynamically on the computer. I have to change the setings in that case, so nothing new. Also, everything works out of the box with my current version!
Code: Use default config files when using ScanState to capture customizations: Starting with Windows 10 Version 1703, you have to use the /config option with ScanState when capturing customizations. Use only one of the default configuration files included with the Assessment and Deployment Kit (ADK). These files are: Config_AppsAndSettings.xml – Use this configuration file to specify that both desktop applications and OS settings should be captured by the ScanState tool. Config_AppsOnly.xml – Use this configuration file to specify that only desktop applications should be captured by the ScanState tool. Since desktop applications are not always well-defined, this configuration file does not guarantee that all setting related to desktop applications are captured. Config_SettingsOnly.xml – Use this configuration file to specify that only OS settings should be captured by the ScanState tool. You can modify these configuration files by setting the migrate attribute for specific components to no, but components that are already excluded from capture/migration in the default configuration files must remain excluded. Still the M$ web site ask to use their XML file. Anyone has the 3 XML files in question? I don't want to DL the whole ADK package just for that
Ok, I got the files. I will modify my software to use the M$ XML file and not generate them. I will be able to stop using the FART (Find And Replace Tool) software with my tools. I will let you know when I have finished and new version is out. Still, you can use current version.
4.0.7 is out. Fixed : I use the official XML file for the capture process of Windows 10. I don't need the FART tool anymore and it is removed form my package. Added : Italian language for Windows 7/8/10 Removed : The FART tool (used to search/replace text in the XML file prior to Windows 10 capture) It works perfectly with the new Windows 10 Creator edition.
Kudos and Thanks for the headache relief! Download the tool today. Exactly what I have been looking for. Thank you for putting this together. While going through the process I was also browsing through the files included for the scripting xml files to see about customizing them for the system I am working on. I noticed that all of the supplied Autounattend.xml for Windows 10 refer to a windows 7.wim 32 bit source file. . This is on each one of the Windows 10 Autounattend files. Planing on putting the program and processes tomorrow. But once again thank you for the time you have put into this work. Keep it up!
You can treat that line like a comment for the original source. The actual commands in the unattend are compatible with 10. I'm still using the same unattend's I created for Win 7 for win8 & win10...
I can confirm that. My unattend.xml is from Win 7 era... As I remember there were some commands that got obsolete when W8 came out. For Windows 10 I didn't change them at all. Cheers.
One question, at what point and from what location should the password be applied? I looked at all 63 posts with the word password before asking. Thanks in advance. P. S. The password files have an English typographical error. The last line should be "You used*." I was the guy that provided the re-write last time. Not sure if it was used, if so please indicate it and I will offer other corrections. T. I. A. Edit: The question might answer itself, it appears to be done from the media after the recovery software is copied and before the sysprep.
this is great sir you did great job for windows 7 and 8 for windows 10 like we dont have recovery drive like we had in 7/8 can you do like windows and alos recovery key Thank You
Windows 10 no longer uses a recovery partition. It has built in Reset features. Just type "reset this pc" & you'll see...
Is FART completely unnecessary? Just making sure the attached isn't an oversight. Thank you for your continued good work. RecoveryTools407\Windows 10\Windows 10 Recovery Tools\Recovery\OEM\Scripts\AppsUpdate.cmd Code: ECHO ***************************** ECHO Capturing softwares ECHO ***************************** C: CD \ CD RECOVERY CD OEM CD ScanState CD %PROCESSOR_ARCHITECTURE% REN C:\Recovery\Customizations\Config.xml Config-Old.xml REN C:\Recovery\Customizations\Recovery.ppkg Recovery-Old.ppkg scanstate.exe /apps /genconfig:C:\Recovery\Customizations\Config.xml /o C:\Recovery\OEM\Tools\fart.exe -i C:\Recovery\Customizations\Config.xml "displayname=\"Windows-Defender-AM-Sigs\" migrate=\"yes\"" "displayname=\"Windows-Defender-AM-Sigs\" migrate=\"no\"" C:\Recovery\OEM\Tools\fart.exe -i C:\Recovery\Customizations\Config.xml "displayname=\"Windows-Defender-AM-Engine\" migrate=\"yes\"" "displayname=\"Windows-Defender-AM-Engine\" migrate=\"no\"" C:\Recovery\OEM\Tools\fart.exe -i C:\Recovery\Customizations\Config.xml "displayname=\"Security-Malware-Windows-Defender\" migrate=\"yes\"" "displayname=\"Security-Malware-Windows-Defender\" migrate=\"no\"" scanstate.exe /apps /config:C:\Recovery\Customizations\Config.xml /ppkg C:\Recovery\Customizations\Recovery.ppkg /o /c /v:13
The AutoUnatend.xml-s from the folders in "...\RecoveryTools4.0.7\Windows 8\AutoUnattend\Image on the last partition" and "...\RecoveryTools4.0.7\Windows 10\AutoUnattend\XXX - Recommended..." Is missing, or have I missunderstood something?
This is normal since the partition layout can nont be scripted with XML. You have to manually create the partition layou before installing Windows by using the TXT file and DISKPART command (diskpart /s filename.txt).