Copying WIM to the deployment share (MDT share is fine PSD share hangs)

I have the same issue as

#91 - Building boot image gets stuck on "Copying WIM to the deployment share" #91 #132 - Updating deployment share gets stuck at, "Copying WIM to the deployment share". #132

it's not related to the ExecutionPolicy

If i create a new deployment share without PSD it completes successfully If i create a new deployment share with PSD it hangs at "Copying WIM to the deployment share"

Any ideas?

MDT Share

PSD Share

Same DeploymentShare directory for both to rule out permissions

Same problem here. "Friends of MDT" could you lead us to some logs to see what is the problem? Thanks!

Hello and Merry Christmas all!

Any logs you could share and details of your PSD setup please?

The only way to get a log is to use the button "Save Output" and store it to a text file. Also another way to find what's happening is to use the Process Monitor SysInternals tool and monitor the MDT Workbench process. When you hit the error, complete the action and stop the capture, you can create a dump of the capture from Process Monitor, compress it and attach it here. But I would suggest to search for any denied/error entries in the captured data first, you may be able to resolve the issue yourselves. Last but not least, check if you your security solution may be a bit aggressive to MDT/PSD and blocks their actions.

experiencing same problem. trying to troubleshoot currently. just wanted to add to the pile so Devs knew there were others with same issue.

Found a solution

unblock-file C:\PSDProduction\PSDResources\Plugins\OSDToolkit\Set-PSDBootImage2PintEnabled.ps1

Hi @t1t20815,

I think you found a bug, regarding the PSDResources folder content! Thank you for your devotion to find a solution! I just checked the installer code and we don't run an Unblock-File command on the PSDResources folder. I think we have to change the way we unblock the files and remove the "Mark of the Internet" flag from the files and do it after completing the copying of them. Pinging @emarkelis so we work on it.

Hi @t1t20815,

I think you found a bug! Thank you for your devotion to find a solution! I just checked the installer code and we don't run an Unblock-File command on the PSDResources folder. I think we have to change the way we unblock the files and remove the "Mark of the Internet" flag from the files and do it after completing the copying of them. Pinging @emarkelis so we work on it.

I have the same issue as

#91 - Building boot image gets stuck on "Copying WIM to the deployment share" #91 #132 - Updating deployment share gets stuck at, "Copying WIM to the deployment share". #132

it's not related to the ExecutionPolicy

If i create a new deployment share without PSD it completes successfully If i create a new deployment share with PSD it hangs at "Copying WIM to the deployment share"

Any ideas?

MDT Share

PSD Share

Same DeploymentShare directory for both to rule out permissions

@Fma965 @ggarbuglia @turturis Have you checked the solution of setting the PowerShell execution Policy to "RemoteSigned"?

I gave up trying to use this since i didn't get any reply on this issue and the project seemed pretty dead.

@Fma965 I wouldn't say that the project is dead (last release on September 2024) but it's not a full time job for anyone involved, it is progressing as time allows, apologies for being late but that's the way such projects work.

I get that, although at the time i raised this issue there was basically no activity. and after setting everything up i found it didn't even support usb drive deployments, a massive requirement for bad network areas, this really should be made clearer as i have seen other people come to the same conclusion.

Either way appreciate the work you are doing on this but it's simply not ready yet and by the time it is ready it will probably not be useful for me (or rather my company) personally.

EDIT: I have side hustles also, fun coding projects etc, i completely get it, it's just a shame it's not someones full time job as it could be really good :)

I changed a bunch of permissions to get past that issue and ran into others. I was ultimately able to get it to work.

I can second an aspect of FMA965's frustration in that it doesnt seem ready for primetime. And I do appreciate it isnt a full-time job.

I understand that we get what we get.

@Fma965 and @turturis Thank you for the understanding, the team is dispersed around the world, it's not easy to even to have conference calls due to time zone differences. You're right that this could be a full time job for someone, but that person, should make a living too, and this is not something easy to achieve. I'm the last person in the link to decide the direction of this project, actually I have retired from the active development part (which I would love to resume, but life's obligations don't let me do so yet) a while ago but continue to help on the issues handling. The project needs some hands and brains more to become great, lots of testing is required as well. Regarding the USB support, there is a way to do it by transferring an ISO file created by the solution to a flash drive (using a tool like Rufus). The whole solution is a huge hack, if you take a look at the docs, it is mentioned that we're substituting the old VBS Scripts with PowerShell ones, it's a bit of a FrankenStein creation but it works nicely, actually, the solution is used extensively by the creators for large deployments, either for recovery from Ransomware attacks or the usual bare metal deployments -that we know and love-.