Is the PC on the domain at all?Hi Kieferschild - I have the same issue here, pushing the MSI using our RMM platform (script running as the local SYSTEM account). Other MSI files on the same system (mine!) work fine, not a domain member so no GPOs in play.
Looking to push the new client out whilst provisioning 3CX to a customer in a few weeks and having this work would save a considerable amount of time and allow the users to self-provision the client (They cannot install MSIs as they won't have local admin rights).
That's pretty much what we're doing. The RMM drops the files into the C:\temp area and then this little bit of Powershell is run:HAve yo
Is the PC on the domain at all?
Try copying it to C:\temp and run it from there.
What RMM?That's pretty much what we're doing. The RMM drops the files into the C:\temp area and then this little bit of Powershell is run:
Start-Process msiexec.exe -ArgumentList '/I "C:\temp\3CXDesktopApp-18.3.33.msi" /quiet /norestart'
Event Viewer is showing:
Windows Installer installed the product. Product Name: 3CX Desktop App. Product Version: 18.3.33.0. Product Language: 1033. Manufacturer: 3CX Ltd.. Installation success or error status: 1603.
Yet it didn't actually install anything.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.