Forum Discussion
More Questions about MMPT remote packaging
The powershell code in the MSIX Toolkit "Batch Conversion" seems to imply that a controller may work with many different worker VMs in parallel. Each parallel thread would invoke a separate instance ...
Thanks for the confirmation.
I am attaching an of the example failure log files. If I rerun the exact same scenario, some of these will work and others fail instead. The failures tend to appear in two places:
- After copying files to the VM, remote execution fails (see AdobeReader example). Both controller and worker VMs, as well as Hyper-V host are domain joined and time sync properly. Sometimes the next attempt on this VM is OK, but at other times that VM will continue to fail on all subsequent passes (reverting to the "known good" snapshot) and I must manually revert the VM, log in and then I can start the automation script over and it is OK.
- After completing the package a similar issue occurs between the file getting saved and the copy back.
Even when this condition exists, I am able to log into the problematic VM remotely or run remote PowerShell commands to it manually, so even if this is an environmental issue, the packaging tool seems to be more sensitive to it.
I have since checked out the environment further and found that one of the AD controllers seems to have had an issue with Patch Tuesday updates. This is being repaired and I'll rerun the tests to see if it solved the issue.
ShakersMSFT Here is that example log file.