This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I include the PowerShell feature in the WinPE deployment share properties, but I need to modify the powershell.exe.config of this feature. Specifically, I need to add this,
<runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
to the .config file, per this post https://stackoverflow.com/questions/18801440/powershell-load-dll-got-error-add-type-could-not-load-file-or-assembly-webdr . I've confirmed that this setting solves a problem in my PowerShell script while in WinPE. The trouble is, I don't know exactly how to change this in the Feature so that it gets added to my boot file automatically. Right now, I have to manually edit the .config file after I boot into WinPE.
A separate issue but similar is, it would be nice to be able to add a .cab file to the Features list to include the PowerShell Active Directory modules to the WinPE boot image. If there was a .cab file that could be added to the C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us directory, then adding the Active Directory modules could just be a feature in the list that could be enabled or disabled easily.
Hi,
We may consider to run a script to edit the .config file in WinPE.
Thanks for the response,
That's what I'm doing now as a work around. I have a command in the task sequence to copy and replace the .config file. Unfortunately, I'm not the only person managing this and I don't want someone else to forget, then all the other processes downstream fail. I'd rather have a way to enforce the change in the boot image to increase the likelihood of success.