OEM Recovery Partition Creator for Windows

No need a fix is normal

 

can some one help me???
i want to create a custom installation where i am triple booting MacOSX from first partition 2nd partition for windows 10 and 3rd partiton for linux all in uefi mode.i only want to modify my second partition space so it can divide the the space for OEM partition from the second partition space and all the thing nessary

 

Hello, you need to format all partitions, Windows and OEM partitions and reinstall Windows only.

 

so what you are saying that i manually create all 3 partition first then i install macOSX at first partition
and second partition i create one partition for OEM recovery and one for windows leave third partition for for linux
if that so what will be the size of OEM recovery partition for second partition i allocated 500GB space
and what configure i should use the document is saying to use some auto attended configuration so if i use this auto attend file then i am unable to create all the partition i mention above as it already start to format the whole disk and start doing all the partition that are mentioned in auto attended

 

It's pretty hard to explain, because you can try to make a recovery partition in a disk that already has partitions, in order to configure the ReAgentc.exe to target the recovery partition.
Because our project allows to do everything an automatic if the hard disk does not plan to have additional system.

So otherwise I advise to try to add partitions in the response file to automate the formatting of partitions for MacOS and Linux. So I think the script to create the recovery will not disturb to use it in order to create the OEM partition.

 

You need to login to view this posts content.

 

A few things.

Is the software functional with 1709 after the new ScanState are swapped in? ( : Thanks Chibi ANUBIS )

************************************
Base files were copied successfully
************************************
Please copy
ReCreatePartitions.txt
and
ResetConfig.xml
in C:\Recovery\OEM
====================================
Examples files can be found under
C:\Recovery\OEM\Settings
====================================
To complete the installation,
run Sysprep.cmd from
C:\Recovery\OEM
************************************
Press any key to continue . . .

"in C:\Recovery\OEM" should be to C:\Recovery\OEM or maybe into C:\Recovery\OEM .
"run Sysprep.cmd from C:\Recovery\OEM" could be in C:\Recovery\OEM (better, located in). That isn't critical.

Will the software erase external drives, other internal drives, network shares and/or etcetera? Might it be suggested the unique drive/volume identifier be utilized? It might not be difficult to script in a multiple choice "Press the disk number" if multiple viable storage options are present (during pre-install) and then store that identifier to be the only media used. It could be added to the recovery to make sure alternate drives are not erased, should an extra (e. g. software mirror) drive be added later.

The BIOS and UEFI defaults for Win10 have the manual ReCreatePartitions.txt and automated AutoUnattend.xml using varied sizes for the SYSTEM partition, RCP is 150 and AU is 100. Is that by design or an oversight? I understand it doesn't much matter.

Any plans for the project moving forward? Anyone have resources or able to point to sites for customizing installations with the configuration OEM Recovery Partition Creator uses? Keep up the good work. Thanks much for this great code.

 

NEVER have additional disks attached during Windows setup..

Also it cannot delete anything from network shares as long as the network user doesnt have write permissions which it never should anyway.
It cant just automatically delete anything from a network share anyway.

 

Perfect, thanks Anarethos

Am I right when I think scanstate files can be used for Creators update?

 

I have this on VM:

Code:

Starting the migration process
Extracting applications:      4%
Extracting applications:  100%tions

Failed
Software malfunction or Unknown exception
See the log file for more information.

Is begins !!

 

Don't download the update ! ScanScate have a problem, I try the build 15063 and is work with success

 

Still a faithful user of your tool. I still have original 407 so will wait before updating. Got to love win10. lol

 

Ok thanks, the rollback was needed

I wait with patient your feedback, I find nothing at this problem....

 

You need to login to view this posts content.

 

I test and I back for you