Forum Discussion

derspinne's avatar
derspinne
Regular Visitor
7 years ago

PowerBI Desktop silent install causing issues with online Publish

Hi,

We're trying to deploy Power BI version (2.62.5222.761) 64bits with the following silent install command line: 


msiexec /i "PBIDesktop_x64.msi" /qn REBOOT=ReallySuppress ACCEPT_EULA=1 INSTALLDESKTOPSHORTCUT=0 ShowLeadGenDialog=0 DISABLE_UPDATE_NOTIFICATION=1 /norestart /L*V "C:\Logs\MicrosoftPowerBIDesktop(x64)_2.62.5222.761_Microsoft.log"

The installation is completed with a return code 0, but the issue we found is when some one who owns a License, tries to log in on the application in order to click on Publish, then it doesn't recognize the user and it sends a pop-up to let the user to subscribe. We tried to subscribe again, but it sends the message that the user is already subscribed. 

So we uninstalled the application and we re-installed manually using the GUI, and after that everything works fine.

Is there's something that I'm missing on the command line? We have being using the same switches for previous versions and now is creating some problems.

If you know a switch that needs to be included or any other clue to this issue, please advise.
Thanks and Kind regards.

Joel E.

4 Replies

    • derspinne's avatar
      derspinne
      Regular Visitor
      Hi Cherie,
      Thanks for your reply, but unfortunately is not my case the thread you've sent; I've already taken care of the Eula acceptance. As you can see my command line the switch is there, so the installation return code is 0, but is not enough to let the users to Publish their documents. They can use normally the application with this installation except for the Publish button that only works when using the full GUI installation process. That's my point.

      With SCCM or even doing it manually in the system context or as Administrator, the same command line with September version msi, we're not able to use the Publish option when installing silently. I can pass the difference between a silent or manual install log files. There are some errors on their custom Actions that i identified but as I said the final return code is 0. So for SCCM or any other deployment tool will concider it as a successful installation.