[huibw]

Hi Doug,
I’ve tried the Remote Execution Context combos but it doesn’t make a difference: the deployment is a success but no output. See screenshots below.

[huibw]

Hi, I’m having the same issue but the above suggestions don’t work: I have (many) deployments that use the ‘Retrieve output’ function. Up until maybe a few months ago this was never an issue but now it shows ‘Could not find file’. When I middle-click on the message it shows me the path, and when I copy it and paste it into Notepad to open, it comes right up. So the file exists and there are no access issues. I’ve tried the 32 bit and 64 bit version of PsExec (v2.34) but that doesn’t make a difference. Should I try an older version? Any idea what the last known good version was?

[huibw]

I concluded that BP tries to download each patch because of the time it took to move on. I did not save the results from the last round, but will do so next time.

I selected all 24 hosts and then selected “download, install, reboot”. Then there was the 1 timeout for the scanfile download & fail. Now all 24 hosts are searching. It was a pretty homogeneous environment, they we’re all done with searching within a few minutes of each other. Then I watched every host wait until the previous one had gotten its patches, there was no concurrency. While waiting their Progress or Upd Msg mentioned something about “download” and just sat there.

I did see I used an older version of BP (March ’17). I have updated BP in that DC and will take screenshots and save the results the next time around in internetless DCs. If it still behaves this way I will report back. I don’t have the ability to test this now, all hosts are on strict schedules. In the mean time thank you for your feedback.

[huibw]

That was too simple 🙂 Many thanks!

[huibw]

Ok, thanks for the pointers. I will follow up on them. Did try the reboot, #1 trick in the handbook 🙂

[huibw]

Hi Doug,

Thank you for your response!

Yes, blush, we have images that are 3+ years behind. Primarily because we didn’t use to update .NET framework because of other dependencies but now we do. Okay, we’ll have to use the “deploy” function. Is there a way to export deployments? I do see I have 12 .NET updates and to recreate 12 deployments in 15 datacenters I also a lot of work.

Thanks

[huibw]

Hi Doug,

Is it possible to reconsider a workaround for this issue? We’ve run into the same issue and it’s not an option for us to go to a newer/different .NET framework. Doing them all one by one for many images in many datacenters is not an really a workable option either.

Thanks,

Huib

[Author]

Posts