Hello Krishna,
We apologize for the delayed reply. My colleague Catalin is out of the office and I will pick up this thread.
The only workaround I could think of will be to check within your PowerShell script code the exit code of the related msi installation, and while this exit code is 1618 (another installation in progress) then wait for a few seconds and retry again to launch the related MSI installation.
I have sent you over email a modified version of your ps1 script which I have successfully tested it on a test machine. Just let me know how this worked.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging