New
#30
Hello how to make usb with provisioning package that will be detected in Out of box experience state?
Hello how to make usb with provisioning package that will be detected in Out of box experience state?
Hi there brylok1981, sorry for delayed response.
I believe the provisioning packages mentioned in this Tutorial, which contain Win32 apps from an installation, can only be applied during the Setup process; I think it won't work during the Out of Box experience (OOBE). I haven't tried it with the latest version of Windows and the latest ADK but I'd be surprised if that has changed.
If you do want to create provisioning packages containing other settings, then I believe Microsoft's recommended approach is to use the Windows Configuration Designer. (This was formerly the Windows Imaging and Configuration Designer, but in version 1703 the Imaging capabilities have been removed.) This tool is found within the Windows ADK.
To apply the package from a USB drive, it should be possible to Insert the USB at the first OOBE screen and it should be detected. The provisioning package needs to be in the root folder of the USB drive. I haven't tried it myself with a recent version though.
https://docs.microsoft.com/en-us/win...-apply-package
Hello All guys,
I have a question for you all. Imagine the following scenario:
I've build a custom Windows 10 OS image, and inserted a custom app.exe in the C:\Windows\System32 directory, then run the scanstate tool. The client will be able to reset the PC and keep that custom App on that directory.
The thing is, imagine that there's a new version of that same App, placed there, if the user resets his OS, the older version will overwrite this new one..
Is there any config file or something like that that i can place on the machine now, in order to prevent this?
I am open to suggestions, please.
Hello Guys: this is a great tutorial.
After creating the usmt .ppkg file how to enable the recovery? in my case after creating the ppkg file recovery is not working.
How can i preapare a master iamge with this .ppkg file? thanks for your reply
Use ScanState to capture and store the resulting PPKG under C:\Recovery\Customizations,
which is restored automatically during PBR.
Thanks, let me summarize:
1. capture usmt.ppkg file
2. ensure its under C:\Recovery\Customizations,
3. ensure Winre.wim file under \Windows\System32\Recovery\Winre.wim
4. enable recovery
Is it correct? is there anything i need to change in the ReAgent.xml to point the Winre recvoery to pick usmt.ppkg file?
Thanks so much for your help
- - - Updated - - -
Hi Again, currently in my recovery is not enabled but the winre.wil file is there; below is the content of reagentc file:
<?xml version='1.0' encoding='utf-8'?>
<WindowsRE version="2.0">
<WinreBCD id="{21cf5f38-a553-11ec-81ed-f9a62f7c7bf2}"/>
<WinreLocation path="\Recovery\WindowsRE" id="3255343060" offset="32256" guid="{00000000-0000-0000-0000-000000000000}"/>
<ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
<PBRImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
<PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
<InstallState state="1"/>
<OsInstallAvailable state="0"/>
<CustomImageAvailable state="0"/>
<IsAutoRepairOn state="1"/>
<WinREStaged state="0"/>
<OperationParam path=""/>
<OperationPermanent state="0"/>
<OsBuildVersion path="19041.1.amd64fre.vb_release.191206-1406"/>
<OemTool state="0"/>
<IsServer state="0"/>
<DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
<IsWimBoot state="0"/>
<NarratorScheduled state="0"/>
<ScheduledOperation state="5"/>
</WindowsRE>
1- Yes (BUT do not enable recovery - if you intend to capture Partition into an Install.wim for deployment)1- Is it correct?
2- is there anything i need to change in the ReAgent.xml to point the Winre recvoery to pick usmt.ppkg file?
2- No - you have no need to mess with that file.......